Re: [zd1211-devs] [zd1211rw] Driver leaving device in bugged state ?
On Thursday 21 September 2006 21:22, Matthieu CASTET wrote: > Hi, > > It seem my first post hasn't got to the mailling list. > > I was saying that if I remove upload_firmware for device that have already > firmware uploaded and weren't reseted with usb_reset_device, there no > errors. > > So I believe instead of relying on usb_reset_device being called at exit > time, we should try to upload the firmware only if it is needed. The > problem is how to detect a device that doesn't need firmware upload (maybe > read firmware version). > > Matthieu > > PS : I don't understand with usb_reset_device before upload_firmware > doesn't seem to work. > Hi, Let me at my bit to the puzzle. The only way I've managed to get the driver loaded properly is to modprobe it manually and then rmmod it. Afterwards I connect the cable. Rafal Here is a relvant part of kernel log: usb 1-3: new high speed USB device using ehci_hcd and address 2 usb 1-3: new device found, idVendor=0ace, idProduct=1211 usb 1-3: new device strings: Mfr=16, Product=32, SerialNumber=0 usb 1-3: Product: USB2.0 WLAN usb 1-3: Manufacturer: ZyDAS usb 1-3: configuration #1 chosen from 1 choice ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation <[EMAIL PROTECTED]> usb 1-3: print_id() 0ace:1211 v4330 high zd1211rw 1-3:1.0: probe() probe start zd1211rw 1-3:1.0: probe() probe switch on speed zd1211rw 1-3:1.0: probe() probe netdev alloc zd1211rw 1-3:1.0: zd_netdev_alloc() netdev->flags 0x1002 zd1211rw 1-3:1.0: zd_netdev_alloc() netdev->features 0x zd1211rw 1-3:1.0: probe() probe upload firmware usb 1-3: request_fw_file() fw name zd1211/zd1211_ub usb 1-3: upload_firmware() firmware device id 0x4330 is equal to the actual device id usb 1-3: request_fw_file() fw name zd1211/zd1211_uphr usb 1-3: upload_code() transfer size 4018 usb 1-3: upload_code() firmware confirm return value 0x01 zd1211rw 1-3:1.0: probe() couldn't reset configuration. Error number -110 zd1211rw 1-3:1.0: probe() probe error usb 1-3: reset high speed USB device using ehci_hcd and address 2 - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
[zd1211-devs] rw : system hang
Hi, for an unknow reason the device becomes crazy [1]. When I tried to remove the module, my system froze. I wonder why the device disconnect like (I didn't do anything special) and why the driver doesn't see that the device is not here. Matthieu PS : I use the snapshot driver with 2.6.18 [1] Sep 22 18:03:55 localhost kernel: usb 4-2: USB disconnect, address 2 Sep 22 18:03:56 localhost kernel: zd1211rw 4-2:1.0: zd_chip_control_leds error - 19 Sep 22 18:04:27 localhost last message repeated 31 times Sep 22 18:05:28 localhost last message repeated 61 times Sep 22 18:06:29 localhost last message repeated 61 times - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
Re: [zd1211-devs] rw : system hang
Matthieu CASTET wrote: > I wonder why the device disconnect like (I didn't do anything special) and > why the driver doesn't see that the device is not here. I'm pretty sure the disconnect is caused by the device firmware bug. ZyDAS haven't fixed this yet. Nevertheless the LED-related hang (infinite loop) that you saw after the disconnect is/was a driver bug. > PS : I use the snapshot driver with 2.6.18 Which snapshot date? > [1] > Sep 22 18:03:55 localhost kernel: usb 4-2: USB disconnect, address 2 > Sep 22 18:03:56 localhost kernel: zd1211rw 4-2:1.0: zd_chip_control_leds > error - > 19 > Sep 22 18:04:27 localhost last message repeated 31 times > Sep 22 18:05:28 localhost last message repeated 61 times > Sep 22 18:06:29 localhost last message repeated 61 times Looks like the housekeeping work functions rescheduled themselves after the disconnect. There was a possible race where this might have happened for a short time, but it is believed to be fixed now. So this all depends on the date of your snapshot. Daniel - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV ___ Zd1211-devs mailing list - http://zd1211.ath.cx/ Unsubscribe: https://lists.sourceforge.net/lists/listinfo/zd1211-devs
