| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <dd18b0c30906191255h7d0c6bcfx58f32d4b34e13c34@mail.gmail.com> Date: Fri, 19 Jun 2009 12:55:20 -0700 From: Justin Mattock <justinmattock@...il.com> To: Michael Tokarev <mjt@....msk.ru> Cc: ronis@...ispc.chem.mcgill.ca, linux-kernel@...r.kernel.org Subject: Re: Panic booting 2.6.30 On Fri, Jun 19, 2009 at 12:32 PM, Michael Tokarev<mjt@....msk.ru> wrote: > David Ronis wrote: >> >> I've just upgraded an older machine (a P3 running slackware 11.0) from >> 2.6.26.5 to 2.6.30; the build was uneventful. However, on reboot (using >> lilo) I get: >> >> VSF: Cannot open root device "hda2" or unknown-block(0,0) >> Please append a correct root= boot option; here are the available >> partions: <====== nothing shows here... >> Kernel-Panic - not syncing. >> >> I had rebooted with and without root=hda2. The old kernel is still >> usable. >> >> Lilo.conf looks like: > > Add large-memory option to lilo.conf > > /mjt > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@...r.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > check /dev/hda* to see if it renamed itself to /dev/sda* (noticed this a few months ago with 2.6.17(I think) to 2.6.24) -- Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists