Hi Edouard, > 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 ?
Correct. I don't have much time available and I chose to spend it on speedbundle. > 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 ? This is due to a usb change in the kernel: it now (since 2.4.2x, x = something) it launches hotplug for every interface, not each device. This is in line with 2.5 behaviour. However, unlike for 2.5, the kernel does not export info about which interface hotplug is being called for. I guess it is possible to work around this using lock files storing pids and all that jazz. One day I will send in a kernel patch to export the extra info, it is on my infinite TODO list... In practice it doesn't matter. > 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 ;-) It is convenient though. You could launch pppd in an init script of course and it wouldn't make much difference, except if you replug the modem. By the way, won't your firewall barf if ppp0 does not exist when you try to do (example) masquerading with it? > 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 ? No, it is not normal. How are you monitoring CPU usage? Just using top, for example, won't show you any info about what's going on in the kernel, because it all happens in softirq's. You need oprofile to do that. Is it pppd that is using up the CPU? Do you have a uhci hc by the way (the driver is inefficient, but that should be the same with pppoax)? I also have an Athlon 2200+, and the speedtouch code comes up pretty far down the list in my profiles (uhci-hcd is much more present though). If you turned on verbose debugging, the logging may be using up CPU. Try decreasing the buffer sizes (this is a module parameter) - if that helps then you are being hit by the uhci hcd's design problems. Also, if you are using multiple urb support (module parameter) with a 2.4 kernel then turn it off - it has never been reliable with 2.4. Which kernel are you running? > Now i can say that it just works. I even measured better ping with my > peer, and the ping variance is smaller. Great - though really the difference with pppoax should be small. > Great work duncan ;-) At least it doesn't crash now... 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] Liste de diffusion modem ALCATEL SpeedTouch USB Pour se d�sinscrire : mailto:[EMAIL PROTECTED]
