On Sat, 2007-11-24 at 16:02 +0100, Andreas Juch wrote: <snip> > With new version (new modules installed, rebooted, plugged the stick in): > ii rt2x00-modules-2.6.23.8 2.0.12+git20071103-1+2.6.23.8-10. > > lsmod | grep rt > rt2570 219008 0 > rt2500usb 30784 0 > rt2x00usb 16448 1 rt2500usb > rt2x00lib 33792 2 rt2500usb,rt2x00usb > crc_itu_t 4608 1 rt2x00lib > mac80211 151236 2 rt2x00usb,rt2x00lib > parport_pc 42472 0 > parport 45132 3 ppdev,parport_pc,lp > firmware_class 13632 2 rt2x00lib,dvb_ttpci > > dmesg: > usb 6-4: new high speed USB device using ehci_hcd and address 3 > usb 6-4: configuration #1 chosen from 1 choice > phy0 -> rt2500usb_validate_eeprom: EEPROM recovery - NIC: 0xfff0 > phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 1201, rf: 0005, rev: > 00000003. > phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected. <snip>
I can see what's going wrong here. In the previous version of the package I changed the controller (RT) revision checks in rt2500usb and rt73usb so that they would each reject devices that the other should handle. (Normally the device id table determines which driver should be used, but at least one device id has been used for devices with different chipsets.) A similar change was then made upstream, but it looks like the check was initially reversed in rt2500usb, resulting in this error. This has since been fixed upstream. I will probably make a new upstream snapshot, as there are some other significant bug fixes in it. If upstream isn't stable enough I will just patch this in the Debian package. Either way, this should be fixed soon. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
signature.asc
Description: This is a digitally signed message part
