On Sunday 20 November 2005 09:53, Duncan Sands wrote: > By the way, I somehow managed to commit old files to CVS yesterday. > I've committed the most recent ones now.
I donloaded and compiled new kernel modules, it looks better now: pls, let me know if something is still wrong there. Bellow is the log. Nov 20 10:12:29 bsd usb 1-1: new full speed USB device using uhci_hcd and address 7 Nov 20 10:12:29 bsd speedtch 1-1:1.0: usbatm_usb_probe: trying driver speedtch with vendor=06b9, product=4061, ifnum 0 Nov 20 10:12:29 bsd speedtch 1-1:1.0: speedtch_bind entered Nov 20 10:12:29 bsd speedtch 1-1:1.0: isochronous transfer not supported - using bulk Nov 20 10:12:29 bsd speedtch 1-1:1.0: speedtch_bind: firmware not loaded Nov 20 10:12:30 bsd usb 1-1: reset full speed USB device using uhci_hcd and address 7 Nov 20 10:12:30 bsd speedtch 1-1:1.0: usbatm_usb_probe: using 3392 byte buffer for channel 0xcfc5bea0 Nov 20 10:12:30 bsd speedtch 1-1:1.0: usbatm_usb_probe: using 3392 byte buffer for channel 0xcfc5beec Nov 20 10:12:30 bsd speedtch 1-1:1.0: speedtch_find_firmware: looking for speedtch-1.bin.0.00 Nov 20 10:12:30 bsd speedtch 1-1:1.0: speedtch_find_firmware: looking for speedtch-1.bin.0 Nov 20 10:12:30 bsd speedtch 1-1:1.0: speedtch_find_firmware: looking for speedtch-1.bin Nov 20 10:12:30 bsd speedtch 1-1:1.0: found stage 1 firmware speedtch-1.bin Nov 20 10:12:30 bsd speedtch 1-1:1.0: speedtch_find_firmware: looking for speedtch-2.bin.0.00 Nov 20 10:12:30 bsd speedtch 1-1:1.0: speedtch_find_firmware: looking for speedtch-2.bin.0 Nov 20 10:12:30 bsd speedtch 1-1:1.0: speedtch_find_firmware: looking for speedtch-2.bin Nov 20 10:12:31 bsd speedtch 1-1:1.0: found stage 2 firmware speedtch-2.bin Nov 20 10:12:31 bsd speedtch 1-1:1.0: speedtch_upload_firmware entered Nov 20 10:12:31 bsd speedtch 1-1:1.0: speedtch_upload_firmware: BLOCK1 uploaded (991 bytes) Nov 20 10:12:31 bsd speedtch 1-1:1.0: speedtch_upload_firmware: BLOCK2 downloaded (511 bytes) Nov 20 10:12:33 bsd speedtch 1-1:1.0: speedtch_upload_firmware: BLOCK3 uploaded (526187 bytes) Nov 20 10:12:33 bsd speedtch 1-1:1.0: speedtch_upload_firmware: BLOCK4 downloaded (511 bytes) Nov 20 10:12:34 bsd ATM dev 0: speedtch_atm_start entered Nov 20 10:12:34 bsd ATM dev 0: speedtch_start_synchro entered Nov 20 10:12:34 bsd ATM dev 0: speedtch_start_synchro: modem prodded. 2 bytes returned: 00 00 Nov 20 10:12:34 bsd /root/speedtouch/speedtouch.kernel/speedtouch/usbatm.c: usbatm_get_instance Nov 20 10:12:35 bsd ATM dev 0: speedtch_check_status: line state 0x10 Nov 20 10:12:35 bsd ATM dev 0: ADSL line is synchronising Nov 20 10:12:46 bsd ATM dev 0: speedtch_handle_int entered Nov 20 10:12:46 bsd ATM dev 0: DSL line goes up Nov 20 10:12:46 bsd ATM dev 0: speedtch_check_status: line state 0x20 Nov 20 10:12:46 bsd ATM dev 0: ADSL line is up (6144 kb/s down | 768 kb/s up) Nov 20 10:13:34 bsd ATM dev 0: usbatm_atm_open: vpi 8, vci 48 Nov 20 10:13:34 bsd ATM dev 0: usbatm_atm_open: allocated vcc data 0xd128e8e0 As for the ping the behaviour is still the same if there is no traffic on the line :( > > > > Are your pings better? > > > > Unfortunately this _strange_ ping behaviour stays exactly the same. As > > for the new kernel modules, I've got: > > Nov 18 18:08:31 bsd ATM dev 0: speedtch_atm_start entered > > Nov 18 18:08:31 bsd ATM dev 0: speedtch_start_synchro entered > > Nov 18 18:08:31 bsd ATM dev 0: speedtch_start_synchro: modem prodded. 2 > > bytes returned: 00 00 > > Nov 18 18:08:31 bsd /mnt/data/tmp/speedtouch/usbatm.c: > > usbatm_get_instance Nov 18 18:08:32 bsd ATM dev 0: speedtch_check_status: > > line state 0x10 Nov 18 18:08:32 bsd ATM dev 0: ADSL line is synchronising > > Nov 18 18:08:43 bsd ATM dev 0: speedtch_handle_int entered > > Nov 18 18:08:43 bsd ATM dev 0: DSL line goes up > > Nov 18 18:08:43 bsd ATM dev 0: speedtch_check_status: line state 0x20 > > Nov 18 18:08:43 bsd ATM dev 0: ADSL line is up (6080 kb/s down | 768 kb/s > > up) Nov 18 18:08:48 bsd ATM dev 0: speedtch_handle_int entered > > Nov 18 18:08:48 bsd ATM dev 0: DSL line goes down > > Nov 18 18:08:48 bsd ATM dev 0: speedtch_check_status: line state 0x00 > > Nov 18 18:08:48 bsd ATM dev 0: ADSL line is down > > Nov 18 18:08:48 bsd ATM dev 0: speedtch_start_synchro entered > > Nov 18 18:08:48 bsd ATM dev 0: speedtch_start_synchro: modem prodded. 2 > > bytes returned: 00 00 > > Nov 18 18:09:25 bsd ATM dev 0: speedtch_handle_int entered > > Nov 18 18:09:25 bsd ATM dev 0: DSL line goes up > > Nov 18 18:09:25 bsd ATM dev 0: speedtch_check_status: line state 0x20 > > Nov 18 18:09:25 bsd ATM dev 0: ADSL line is up (6144 kb/s down | 768 kb/s > > up) Nov 18 18:10:05 bsd ATM dev 0: usbatm_atm_open: vpi 8, vci 48 > > Nov 18 18:10:05 bsd ATM dev 0: usbatm_atm_open: allocated vcc data > > 0xdf055ea0 > > > > so, it looks like the line goes up twice in a few seconds, but as far as > > I can see it doesn't (according modem lights). Is this normal? > > No, it's not normal. Does it keep on happening, or is this the only time? > > Duncan. > > Liste de diffusion modem ALCATEL SpeedTouch USB > Pour se dИsinscrire : > mailto:[EMAIL PROTECTED] Liste de diffusion modem ALCATEL SpeedTouch USB Pour se dИsinscrire : mailto:[EMAIL PROTECTED]
