[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Adrian Midgley wrote: | | pivot_root no such file or directory | /sbin/init 426: can't open /dev/console no such file | Panic.
According to the Google search this may occur if the root filesystem is not loaded. Can you check there are no earlier error messages that may be relevant.
My guess something odd about Lilo, check the labels are different, and manually run "lilo" to confirm it is written to disk.
| Runs fine with the installation kernel, but that lacks a couple of | things I want to add. | | Advice? Which is the critical error, or are they independent?
Don't go backwards (in kernel versions), it really doesn't matter much what (recent) kernel version you use in Debian as long as the hardware drivers exist in it, but moving backwards risks both loosing support for specific hardware and encountering known bugs.
Indeed I'd be tempted to try pushing forward to 2.6, but failing that the latest 2.4 kernel is likely to provide the best experience, at least pain.
You may find the stock kernel works if you fix Lilo, but it is entirely possible there is some hardware driver required that you haven't included, which is why I'd suggest starting the kernel config with the ".config" from the "Debian for DELL" kernel. The worst this will do is include drivers for other DELL hardware that you don't have, but you know it should at least boot your system correctly. i.e. Why recreate the system integration work the Debian for DELL ppl have already done?
I believe the Debian for DELL documentation even explains how to customise a kernel using the Debian kernel-package, and the config file on their website. -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFB4W5eGFXfHI9FVgYRAvIeAKDGGOuzM+rzRcHrlypmVDUyxUzpDwCfVC/c ISFpKjIyyrmxn8/RjeVgchQ= =g5PU -----END PGP SIGNATURE-----
-- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.