I can confirm this bug really exists on standard initrd kernels. I have
this same problem on two different laptops. I run the standard Debian
kernels (which are initrd kernels.)
I have found the following:
1)
if xdm/gdm etc doesn't start... you can go to a root session and:
/etc/init.d/udev stop
/etc/init.d/udev start
and then (after a really scary warning that I ignored, and 60 seconds)
all the modules loaded and all seems to work.
/etc/init.d/gdm restart
works as expected (as this time a mouse and keyboard are present.)
2)
If as the boot operation is starting you press control-s to see the
error messages (which still scroll by too fast) you:
a) see reference to a Read Only file system over and over for each udev
reference
b) after you finally control-q to continue the boot EVERYTHING WORKS
JUST FINE. Your devices are all seen and gdm starts as normal.
--
Jeffrey Hundstad
PS. It's called unstable for a reason (get over it ;-)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
