| Summary: | silo-1.3.1 fails to work and boot with initrd ( ramdisk ) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | a-wall |
| Component: | Current packages | Assignee: | Sparc Porters <sparc> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | Sparc | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
What type of file system is your initrd composed of? Also how big is the initrd? The text of the error message would really help if it can be provided. I'm guessing your problem is the combination of your kernel size and initrd size is too big. themp, you said on irc the other day you had talked to wesolows about this. Can you fill in the details here from that? Need more info before we can proceed with this. |
silo-1.3.1 and perhaps others fails to boot on an ultra60 with initrd ( ramdisk ) enabled. example as follows: image = /boot/vmlinuz-2.4.21 label = linux root=/dev/sda1 read-only initrd="/boot/ramdisk.gz" take out initrd or comment it out and the system will boot could also possible be a kernel issue. Side note: not using modules Reproducible: Always Steps to Reproduce: 1.compile kernel with initrd 2. enable in silo 3. try to boot the kernel with initrd Actual Results: boot error at the sun silo boot prompt cant paste it in. Expected Results: should boot like it used to.