On Friday 26 September 2003 12:06 pm, Joe Kelsey wrote:
Brandon Fosdick wrote:Mine doesn't either and the fact it dies in the boot -s phase of updating the system is a verification of the reason to boot to single user mode. I have tried unplugging the USB devices and it will finish the boot. I won't, however, finish the installworld.
Joe Kelsey wrote:I have an ASUS A7S333 which does *not* have an nforce2 chipset.
When I upgraded to fix the OpenSSH problems, the system started hanging at boot time right after the USB/OHCI messages whenever I had devices plugged into the USB ports (mainly a USB mouse). Now, in order to boot, I have to unplug the mouse and wait for the system to pass the USB part of boot before replugging.
There are several threads discussing this ATM. If you have an nforce2 board search for the thread with the subject "fix/workaround for usb probe lockups on nForce2 mbs". Andrew Atrens posted a patch that worked for me. In the same thread Ian Dowse has offered a few other ideas to try. I haven't tried them yet.
boot -s hangs just like normal boot unless I unplug the mouse. After boot -s with ums unplugged, I can fsck if necessary and then mount-a, installworld, etc. with no problems. I can even plug in the mouse, not that it helps because I still have to unplug it when I repoot after mergemaster.
I have never experienced a panic or other crash related to USB devices. Only the boot lockup.
/Joe
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
