Hi I wanted to give a try at the speedtch kernel module as the debian SID now has support for a pppoatm aware ppp daemon. Perhaps Duncan can answer these questions.
NB: I did not download the speedbundle tarball, i just used tools from the debian SID and your doc available on the linux-usb project page. First Question: I guess the doc isn't up2date, is it ? Second question (see [1]): In my logs the hotplug even manager loads the speedtch driver trice. I don't know why. The problem is it fires up 3 modem_run. Thanks to modem_runs design, only one instance finishes the initialization. Isn't there a better solution ? Third question: I'm not sure the pppd launch belongs to the hotplug event manager. Hotplug is run before any network services, so the connection would be done before any firewall would be up... As you see it's not really a question, just a loud thought ;-) Fourth question: I noticed very CPU usage during network load (around 5%[2]) for a 512kbps download. I'm not sure this is correct as pppoa3 does use much less CPU (with 5% CPU, i can read a mpeg4 movie, and i'm _sure_ mpeg4 decoding is much more CPU intensive than simple memoves and usb urbs submissions) Is it normal ? Now i can say that it just works. I even measured better ping with my peer, and the ping variance is smaller. Great work duncan ;-) [1] Sep 30 01:35:04 [kernel] usb.c: registered new driver speedtch Sep 30 01:35:04 [logger] speedtch: uploading microcode. Sep 30 01:35:04 [logger] speedtch: uploading microcode. Sep 30 01:35:04 [logger] speedtch: uploading microcode. Sep 30 01:35:04 [modem_run] modem_run version 1.2-beta2 started by root uid 0 Sep 30 01:35:04 [modem_run] modem_run version 1.2-beta2 started by root uid 0 Sep 30 01:35:04 [modem_run] modem_run version 1.2-beta2 started by root uid 0 Sep 30 01:35:04 [modem_run] Another program/driver is already accessing the modem (interface 2 cannot be claimed)... Sep 30 01:35:04 [modem_run] Another program/driver is already accessing the modem (interface 2 cannot be claimed)... Sep 30 01:35:25 [modem_run] ADSL synchronization has been obtained Sep 30 01:35:25 [modem_run] ADSL line is up (608 kbit/s down | 160 kbit/s up) Sep 30 01:35:26 [kernel] usbdevfs: process 4960 (modem_run) did not claim interface 0 before use [2] My CPU is an AthlonXP 2200+, so 5% of that horse power is quite huge. -- Edouard Gomez Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
