Hi Steve, > > There's an experimental feature which only works with speedtouch 330s or > > better: download using isochronous urbs, rather than bulk urbs. This > > should improve performance on high speed connections. You can turn it > > on with enable_isoc=1. It may be worth turning on, because one possible > > explanation for your problem is that data is coming into the modem faster > > than it is being extracted by the computer, and some buffers in the modem > > are overflowing. Of course this wouldn't happen in a bug free world... > > Try some recent firmware, such as bin/sachu3/zzzlp2.eni from > > http://www.speedtouch.co.uk/downloads/330/301/UK3012%20Extended.zip > > Interesting. I'm currently using ZZZL_3.012 from > http://www.speedtouchdsl.com/download/drivers/USB/SpeedTouch330_firmware_3012.zip > this being the only file which the firmware extractor at > http://www.linux-usb.org/SpeedTouch/firmware/firmware-extractor.tar.gz > will extract. > > I tried the URL you quoted but it has moved, so I briefly scouted their web > site and came up with a few possibles: > > None of the links on > http://www.speedtouch.co.uk/codepages/content3.asp?c=7&ProductID=471 > work whilst http://www.speedtouch.com/support.htm leads to > http://www.speedtouch.com/download/drivers/USB/SpeedTouch330_firmware_3012.zip > which looks like what I'm running now.
There's also http://www.speedtouch.co.uk/products/faq.asp?ProductID=471. Probably you want the "Driver for 8M lines". > Any ideas where the new firmware is? Do I need a new firmware extractor too? I've no idea where the "extended reach" driver went. Since I downloaded it without having to agree to any licence conditions etc (the download doesn't contain a licence either) I will send the firmware to anyone who asks, unless Thomson asks me to stop. > Here are the results of booting the box with CONFIG_USB_DEBUG on: > > If I boot 2.6.19.1 with the modem is plugged in during the boot the results > are no different to what you've seen already. I assume this is something > to do with klogd not having started at that point in the boot. > > The results do not change if dl_512_first=1 is in modprobe.conf or not. > > If I put enable_isoc=1 in modprobe.conf the boot now proceeds past loading > the speedtch module, allowing other modules to load normally. The messages > are unchanged however. > > But if I unplug the modem during the boot and plug it in after logging in > it all becomes much clearer. Here is an snippet of the relevant messages: ... > #### Modem plugged in > usb usb1: wakeup_rh (auto-start) > hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004 > uhci_hcd 0000:00:07.2: port 2 portsc 0093,00 > hub 1-0:1.0: port 2, status 0101, change 0001, 12 Mb/s > hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x101 > usb 1-2: new full speed USB device using uhci_hcd and address 2 > usb 1-2: ep0 maxpacket = 8 > usb 1-2: default language 0x0409 > usb 1-2: new device strings: Mfr=1, Product=2, SerialNumber=3 > usb 1-2: Product: Speed Touch 330 > usb 1-2: Manufacturer: THOMSON > usb 1-2: SerialNumber: XXXXXXXXXXXX > usb 1-2: uevent > usb 1-2: usb_probe_device > usb 1-2: configuration #1 chosen from 1 choice > usb 1-2: adding 1-2:1.0 (config #1, interface 0) > usb 1-2:1.0: uevent > usb 1-2: usb_probe_device > usb 1-2: configuration #1 chosen from 1 choice > usb 1-2: adding 1-2:1.0 (config #1, interface 0) > usb 1-2:1.0: uevent > usb 1-2: adding 1-2:1.1 (config #1, interface 1) > usb 1-2:1.1: uevent > usb 1-2: adding 1-2:1.2 (config #1, interface 2) > usb 1-2:1.2: uevent > drivers/usb/core/inode.c: creating file '002' > hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004 > drivers/usb/atm/usbatm.c: usbatm_usb_init: driver version 1.10 > drivers/usb/atm/speedtch.c: speedtch_usb_init: driver version 1.10 Module is loaded. > speedtch 1-2:1.0: usb_probe_interface > speedtch 1-2:1.0: usb_probe_interface - got id > speedtch 1-2:1.0: usbatm_usb_probe: trying driver speedtch with vendor=06b9, > product=4061, ifnum 0 > speedtch 1-2:1.0: speedtch_bind entered Probe. > usb 1-2: modprobe timed out on ep0in len=0/1 > speedtch 1-2:1.0: speedtch_bind: firmware not loaded > usb 1-2: reset full speed USB device using uhci_hcd and address 2 Device reset before firmware upload. > usb 1-2: ep0 maxpacket = 8 > usbdev1.2_ep81: ep_device_release called for usbdev1.2_ep81 > usbdev1.2_ep06: ep_device_release called for usbdev1.2_ep06 > usbdev1.2_ep07: ep_device_release called for usbdev1.2_ep07 > usbdev1.2_ep87: ep_device_release called for usbdev1.2_ep87 > usbdev1.2_ep05: ep_device_release called for usbdev1.2_ep05 > usbdev1.2_ep85: ep_device_release called for usbdev1.2_ep85 > speedtch 1-2:1.0: usbatm_usb_probe: using 3840 byte buffer for rx channel > 0xd3d330ac > speedtch 1-2:1.0: usbatm_usb_probe: using 3392 byte buffer for tx channel > 0xd3d330f8 > speedtch 1-2:1.0: speedtch_find_firmware: looking for speedtch-1.bin.4.00 > usbcore: registered new interface driver speedtch > drivers/usb/atm/speedtch.c: speedtch_usb_cleanup Here someone asks for the module to be unloaded. > usbcore: deregistering interface driver speedtch This causes usbcore to disconnect the device. > speedtch 1-2:1.0: usbatm_usb_disconnect entered Disconnect begins... (waiting for firmware loader to finish) > speedtch 1-2:1.0: found stage 1 firmware speedtch-1.bin.4.00 > speedtch 1-2:1.0: speedtch_find_firmware: looking for speedtch-2.bin.4.00 > speedtch 1-2:1.0: found stage 2 firmware speedtch-2.bin.4.00 > speedtch 1-2:1.0: speedtch_upload_firmware entered > speedtch 1-2:1.0: speedtch_upload_firmware: BLOCK1 uploaded (935 bytes) > speedtch 1-2:1.0: speedtch_upload_firmware: BLOCK2 downloaded (511 bytes) > speedtch 1-2:1.0: speedtch_upload_firmware: BLOCK3 uploaded (775545 bytes) > speedtch 1-2:1.0: speedtch_upload_firmware: BLOCK4 downloaded (511 bytes) > usbdev1.2_ep06: ep_device_release called for usbdev1.2_ep06 > usbdev1.2_ep07: ep_device_release called for usbdev1.2_ep07 > usbdev1.2_ep87: ep_device_release called for usbdev1.2_ep87 > usb 1-2: speedtch timed out on ep0out len=0/2 > speedtch 1-2:1.0: speedtch_test_sequence failed on URB147: -110 > ATM dev 0: speedtch_atm_start entered > ATM dev 0: speedtch_start_synchro entered > ATM dev 0: speedtch_start_synchro: modem prodded. 2 bytes returned: 00 00 > usb 1-2: bogus endpoint ep1in in usb_submit_urb (bad maxpacket 0) > ATM dev 0: speedtch_atm_start: submission of interrupt URB failed (-90)! > drivers/usb/atm/usbatm.c: usbatm_get_instance > ATM dev 0: usbatm_complete: urb 0xd7ea1260 failed (-2)! > ATM dev 0: usbatm_complete: urb 0xd7ea1160 failed (-2)! > ATM dev 0: usbatm_complete: urb 0xd7ea1060 failed (-2)! > ATM dev 0: speedtch_atm_stop entered Disconnect continues... > speedtch 1-2:1.0: speedtch_unbind entered Disconnected. > speedtch 1-2:1.1: usbatm_usb_disconnect entered > speedtch 1-2:1.1: usbatm_usb_disconnect: NULL instance! Disconnect on another interface. > usbdev1.2_ep06: ep_device_release called for usbdev1.2_ep06 > usbdev1.2_ep07: ep_device_release called for usbdev1.2_ep07 > usbdev1.2_ep87: ep_device_release called for usbdev1.2_ep87 > speedtch 1-2:1.2: usbatm_usb_disconnect entered > speedtch 1-2:1.2: usbatm_usb_disconnect: NULL instance! All interfaces now disconnected. > usbdev1.2_ep05: ep_device_release called for usbdev1.2_ep05 > usbdev1.2_ep85: ep_device_release called for usbdev1.2_ep85 > drivers/usb/atm/usbatm.c: usbatm_atm_dev_close > drivers/usb/atm/usbatm.c: usbatm_put_instance > drivers/usb/atm/usbatm.c: usbatm_put_instance > drivers/usb/atm/usbatm.c: usbatm_destroy_instance > usbdev1.2_ep81: ep_device_release called for usbdev1.2_ep81 > drivers/usb/atm/usbatm.c: usbatm_usb_exit usbatm module now also unloaded. > speedtch: Unknown symbol usbatm_usb_disconnect > speedtch: Unknown symbol usbatm_usb_probe Mysterious messages. > drivers/usb/atm/usbatm.c: usbatm_usb_init: driver version 1.10 > drivers/usb/atm/speedtch.c: speedtch_usb_init: driver version 1.10 Modules are reloaded and the whole thing repeats. > Any ideas? I'd guess you have some script on your system, maybe a hotplug script, that is removing the modules. One thought is that the device reset may be being misinterpreted by some script as device removal, and is triggering unloading of the modules. Ciao, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
