Neil Bothwick <n...@digimed.co.uk> writes: > On Fri, 24 Jun 2011 20:18:57 -0500, Harry Putnam wrote: > >> But now that I tried booting, I think I'm missing some kind of driver >> from the kernel build... boot is not able to find my root on sda3. >> And has a kernel panic. >> >> I remember having a heck of a time about scuzy drivers last time too. >> A couple years ago >> >> I didn't think to get the right wording before rebooting into >> SystemRescueCD and am now chrooted into the vm again. > > Reboot the VM into System Rescue Cd and run lspci -k to see which > controller you have and which driver it uses.
Haa... good idea and I once knew to do that too. But that was before the truly `macro' senility set in ... 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01) 00:02.0 VGA compatible controller: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 00:03.0 Ethernet controller: Intel Corporation 82540EM Gigabit Ethernet Controller (rev 02) 00:04.0 System peripheral: InnoTek Systemberatung GmbH VirtualBox Guest Service 00:05.0 Multimedia audio controller: Intel Corporation 82801AA AC'97 Audio Controller (rev 01) 00:06.0 USB Controller: Apple Computer Inc. KeyLargo/Intrepid USB 00:07.0 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 08) 00:0d.0 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 02) Seemed to have been the PIIX4 item and now I seem to have gotten the drivers that I needed but now the bootup freezes just after finding the drives. Something about write protecting kernel text and read-only data. Then another odd one: atkbd serio0: Spurious NAK on isa0060/serio0. Some program might be trying to access hardware directly. I've never seen those message before. A tail of boot messages posted here: www.jtan.com/~reader/vu2/disp.cgi I thought it was stuck at the `Write protect' lines, but after a hefty wait the last line appeared (quoted above). And now does appear to be truly stuck. Full kernel config here: www.jtan.com/~reader/vu_txt/disp.cgi
