On Fri 06 Jul 2012 at 03:23:33 -0700, John Magolske wrote: > I just installed 3.2.0-3-686-pae, but got a kernel panic when trying > to boot with it. As transcribed from my phone-camera "screenshot" > (there are 10 more lines of output I can transcribe if that'd help): > > [ 0.987169] Kernel panic - not syncing : VFS: Unable to mount root > fs on unknown block(0,0) > > Any thoughts on why this kernel isn't working?
Not any more than might come from a search with the error message you have. Purge and reinstall the new kernel? Generate a new initrd? Have a look and see what you think. > Fortunately I was able to re-boot by selecting 3.2.0-2-686-pae from > the Grub menu. This kernel had been installed explicitly by name: > > # aptitude install linux-image-3.2.0-2-686-pae > > Whereas 3.2.0-3-686-pae was installed using the linux-image-686-pae > meta-package: > > # aptitude install linux-image-686-pae > > So something else I'm wondering...if I had initially installed > 3.2.0-2-686-pae using the meta-package instead, would my recent > upgrade to 3.2.0-3-686-pae using that same meta-package have removed > 3.2.0-2-686-pae? No. Which was fortunate for you. :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120705204002.GG28931@desktop
