Downloading the universal CD now, but on my little 800mhz box I'm trying to install gentoo to get a webserver up and running. CD MD5sum checks out fine. It gets basically nowhere unless I load gentoo-nofb. I've tried with various noxxxx options, but still dying with : <0>Kernel panic - not syncing: Attempted to kill init! Reproducible: Always Steps to Reproduce: 1. Boot off of 2005.0 minimal. 2. gentoo-nofb Actual Results: Kernel panic - not syncing: Attempted to kill init! Expected Results: Boot. Any more info needed???
I really need a bit more information than that. Basically, at least 2 or 3 lines above the kernel panic. Also, this doesn't happen with gentoo, just with gentoo-nofb? Sorry, some of your post makes a lot of things ambiguous. Also, don't waste your time on the Universal. It is the exact same kernel, etc as the minimal, it just has more stuff appended to it. I would suggest booting like this: gentoo-nofb nosmp noapic acpi=off
Several lines above panic there was what looked like a small six-line dump of sorts. Then there was "Code:" and three lines of two-character hex values. Then the kernel panic message. Do you need something else? Or do you need all of those hex values?
This happens with both gentoo and gentoo-nofb as far as I can tell. If I just use gentoo, however, I don't get far enough to be able to tell whats going on. The version with FB locks and displays nothing but a greyish blank screen. I'm guessing the kernel paniced and that's why. I'll kill universal and try some other things. Pretty sure I've tried every variation of no options I can, but I will try your gentoo-nofb nosmp noapic acpi=off. Not around the machine right now, but I know this about it: 800mhz p3 i815 chipset intel motherboard not sure yet on video card make and model... Thanks.
The hex dump won't help so much, except it probably gives some cryptic messages on what could have possibly failed. The actual "kernel panic" line is basically a generic message, so it doesn't tell me much. Perhaps if there's anything that looks like an error before the hex dump, or if you see anything in the hex dump that looks useful. Anyway, the option line I gave you tends to work on almost all boards. The only other possibility is a driver being auto-loaded that is causing it, but that should be somewhat visible within the hex dump, and you could use noload=drivername to keep it from loading.
No response... feel free to REOPEN to revisit this...
