notes pertaining to 1.1.2 usb firmware.

This commit is contained in:
solomon 2002-09-25 20:57:15 +00:00
parent ae33712937
commit 6ac7a23951
1 changed files with 11 additions and 4 deletions

15
FAQ
View File

@ -164,14 +164,16 @@ Q: My prism2.5-based USB adapter won't come up if it's plugged in at boot!
device reset on initialization. You can perform this by adding
"options prism2_usb prism2_doreset=1" in your /etc/modules.conf
Primary firmware 1.1.0 is known to improve this considerably;
Pester your vendor to release updated firmware.
Intersil has released Primary firmware 1.1.2, which seems to
have resolved this problem, at least on our test machines.
Contact your vendor for a firmware update.
To check the firmware version, run: "dmesg |grep ident"
Q: My PC crashes when the USB device is plugged in at boot!
Q: My PC crashes when the USB device is plugged in!
This is a result of the port reset necessitated by buggy firmware.
This is due to how the driver performs the device reset.
You are probably using the 'usb-uhci' driver with an intel
chipset. Unfortunately, the crashes happen deep within the USB
core, so there's nothing the linux-wlan-ng driver can do.
@ -180,6 +182,11 @@ Q: My PC crashes when the USB device is plugged in at boot!
instead ("alias usb-controller uhci" in /etc/modules.conf), or
plug the USB device into a hub.
Linux kernel 2.4.19 is known to improve the situation somewhat,
but the right way to fix it is to turn off the port reset
(options prism2_usb prism2_doreset=0). The current firmware
from Intersil alleviates the need to perform the reset.
Q: What's with these "Called from within soft interrupt context" messages?
This is the result of a workaround to avoid a kernel oops in