Tim Wright <[EMAIL PROTECTED]> writes:
> I'm currently having no end of troubles getting the kernel to boot
> correctly. The first set have to do with a complete change around of
> files in the /dev directory. My current ones seem to be that the kernel
> can't open a console screen. Sigh. I've just got the 2.6.0-test8 version
> tho, and hopefully that will go more easily. (was having problems with
> 2.6.0-test7).
The biggest problem I had getting 2.6.0-test6 going was that I'd ended
up with an empty /dev directory, after using devfs for so long, and
then not selecting it for 2.6. This resulted in loud complaints
during the boot process from either the kernel or init trying to open
the console.
A quick bind mount and MAKEDEV from 2.4 later (preceded by much
puzzling and googling) and I was fixed. For getting started apart from
this, I found
http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
very helpful.
A positive effect of the upgrade was that the USB light on my
Speedtouch ADSL modem stopped blinking red when I tried to do large
downloads, and speed improved considerably, so I'm running 2.6
permanently now.
--
"Hanging is too good for a man who makes puns; he should be drawn and quoted."
-- Fred Allen
