cannot finddevconsole error 432 1082
On Fri, 05 May 2006 00:02:04 -0400, Trixx
OK, this explains it all. The suggestions others are making about monkeying around with initrd will not work. The 2.6.8 kernel you have will not recognize the SATAŹdrive. Get the debian package for a 2.6.15, or, better yet, do as I did and wipe&reinstall. A SATA drive is recognized as a different thing with 2.6 kernels (at least new ones; I tried to install a 2.6.8 kernel and got nowhere) than with 2.4 kernels. There are many parts of the configuration that need the drive device; and none of these will work properly with the new kernel, and the old labels. Just changingetc-fstab will not work. I tried that.
What I did, that worked, was to get a new debian etch install disk (daily release rather than the several-week-old one), and start essentially from scratch. BTW, your cdrom drive may also be recognized as scsi now (mine was on the home machine, not on the office, which is a similar box), so you may need to use the boot option
install libata.atapienabled=1
This is mentioned on the debian site.
OK... this is crazy but seems to really freakin work... so do it! This was in the Wall Street Journal... I...
I only re-did my system parbreastions,usrvartmp. I was able to re-configure the system to mount the other parbreastions without re-formatting and losing all information. But you want to re-format the base system to clear everything off.
Here is an example of a wfl program and all it really is doing is running a job taking the information and renaming it at the end and printing it...
Of course, back everything you want to keep up to another machine.
There are many advantages of going to a newer kernel. The drive access is faster, and X acceleration (and in my case, sound) were no longer supported by my 2.4.* kernel after a recent update. Now it is all back better than ever.
--
David L. Johnson
o If all economists were laid end to end, they would not reach a `-(, conclusion. -- George Bernard Shaw ()()
Linux groups from Newsgroups