[speedtouch] Re: pusb_claim_interface 1 failed with 330 modem
> Duncan Sands wrote: > > > From the short time perspective I want to use the driver which works for 2.6.7, > > regardless where it resides. From the long term perspective I guess an existing > > fix or workaround of kernel-mode driver is important, there may be many users > > trying to do same things... > > > >*If* this is *the* cause of failing iface claims, of course -- but this is what I > >really do not know at this moment. > > Hi Pavel, the user-mode (UM) and kernel-mode (KM) drivers both work > fine with 2.6 kernels. As far as I can see your problem is that you are > trying to use them both at the same time! Hi Duncan, First of all -- thank you very much! The reason of "pbus_claim_interface 1 fails" error was indeed mixing both UM and KM drivers in my box. After 'speedtch' KM driver disabled in the 2.6.7 kernel everything works as expected -- I need not even to change a single word in my speedtouch cofiguration which was previously working with the 2.4.46 kernel (i.e. the '-k' seems to be the tolerant option of 'modem_run'). Guessing this problem is not rare (and no solution can be googled out): http://www.mail-archive.com/[EMAIL PROTECTED]/msg06264.html http://www.linuxquestions.org/questions/archive/18/2003/12/4/129014 http://lists.debian.org/debian-user-polish/2003/09/msg00294.html so I would like to suggest a simple addon to otherwise useful SpeedTouch FAQ: --- Q: 4.15 I see "pbus_claim_interface 1 fails" errors in my syslog. I am using 2.6.x kernel with 'speedtch' support module turned on. A: The user-mode (UM) and kernel-mode (KM) drivers both work fine with 2.6 kernels. You may be trying to use them both at the same time. 'pppoa3' is a part of the UM driver. The 'modem_run' program is used by both drivers. --- Some better formulation of this text obviously can be found. And, during my previous tests I have noticed two cosmetic issues: 1. The configuration script uses 'lspci' tool which is quite normal to have installed but is not installed by default in some distributions (e.g. Gentoo 2004.2). Testing of this existence would be easy in script and convenient for an inexperienced user. 2. The configuration requires also /proc/bus/usb/devices. Again, this is usual, but there is at least one distribution which has this renamed by default, for example SUSE Personal 9.1 has instead it something like '/proc/bus/usb/devices_please_do_not_use'. I was not able to symlink it to /proc/bus/usb/devices (because of /proc filesystem). Some $USB_DEVICES variable would be nice. These two details are trivial in comparision with the interface problem, which is not easily solvable by pppoa newbies like me. Many thanks to Duncan again. Wishes, Pavel Suchmann, now the happy speedtouch user. Zbavte se zdarma svojí staré! www.BILEZBOZI.cz V srpnu odvoz starých ledniček ZDARMA. http://ad.seznam.cz/clickthru?spotId=76187 Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: pusb_claim_interface 1 failed with 330 modem
Selon Duncan Sands <[EMAIL PROTECTED]>: > This assume that modem_run lives in /usr/sbin, and that the firmware > is in /usr/lib/speedtouch. You'll probably want to change this line if you > have a recent "two firmware files" modem_run. You can always start > the connection by hand by running modem_run, and then doing > pppd call speedtch when you want to bring the connection up. > > I hope this helps, > > Duncan. > We don't need anymore firmware in two files as Thomson release a 'Embedded Firmware for Linux users' 1.0 MB Rel 3.0.1 http://www.speedtouch.com/driver_upgrade_lx_3.0.1.2.htm with both KQD6 and ZZZL2 firmwares, each in one file No more need to register now for loading firmware, only acknowledge this magic license wich just metamorphoses every linux user as a developper. Gilles Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: pusb_claim_interface 1 failed with 330 modem
> From the short time perspective I want to use the driver which works for 2.6.7, > regardless where it resides. From the long term perspective I guess an existing fix > or workaround of kernel-mode driver is important, there may be many users trying to > do same things... > > *If* this is *the* cause of failing iface claims, of course -- but this is what I > really do not know at this moment. Hi Pavel, the user-mode (UM) and kernel-mode (KM) drivers both work fine with 2.6 kernels. As far as I can see your problem is that you are trying to use them both at the same time! pppoa3 is part of the UM driver. The -k switch is for the KM driver. The modem_run program is used by both drivers. If you want to use the user-mode driver, try adding the following line to /etc/hotplug/blacklist: speedtch (I never tried this myself, but it should work. Otherwise you can delete the file /lib/modules/`uname -r`/kernel/drivers/usb/misc/speedtch.ko) If you want to use the kernel mode driver, then you need a pppd with pppoatm support (most distributions supply one). You need to set some pppd options: create a file /etc/ppp/peers/speedtch containing: # To connect to using this configuration file, do # pppd call speedtch lcp-echo-interval 10 lcp-echo-failure 3 noipdefault defaultroute user "username" noauth noaccomp nopcomp noccp novj holdoff 4 persist maxfail 25 updetach usepeerdns plugin pppoatm.so 0.00 You'll need to replace username with your ADSL username. You'll also need to add a line like this to /etc/ppp/pap-secrets and to /etc/ppp/chap-secrets: username* password where username is the same ADSL username you used above, and password is the password your ISP gave you. Finally, you can launch the connection automatically by creating a file called /etc/hotplug/usb/speedtch containing #!/bin/bash case $ACTION in add) echo "uploading firmware" if /usr/sbin/modem_run -k -f /usr/lib/speedtouch/firmware.bin ; then sleep 10 echo "starting pppd" if ! /usr/sbin/pppd call speedtch ; then echo "failed to start pppd!" fi else echo "firmware upload failed!" fi ;; esac This assume that modem_run lives in /usr/sbin, and that the firmware is in /usr/lib/speedtouch. You'll probably want to change this line if you have a recent "two firmware files" modem_run. You can always start the connection by hand by running modem_run, and then doing pppd call speedtch when you want to bring the connection up. I hope this helps, Duncan. Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: pusb_claim_interface 1 failed with 330 modem
Hi, >From the short time perspective I want to use the driver which works for 2.6.7, >regardless where it resides. From the long term perspective I guess an existing fix >or workaround of kernel-mode driver is important, there may be many users trying to >do same things... *If* this is *the* cause of failing iface claims, of course -- but this is what I really do not know at this moment. Cheers, Pavel Suchmann Duncan Sands wrote: > Do you want to use the user-mode or kernel-mode driver? > > Liste de diffusion modem ALCATEL SpeedTouch USB > Pour se désinscrire : mailto:[EMAIL PROTECTED] Anonymní připojení k internetu od Seznamu http://ad.seznam.cz/clickthru?spotId=74638 Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: pusb_claim_interface 1 failed with 330 modem
Do you want to use the user-mode or kernel-mode driver? Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
[speedtouch] Re: pusb_claim_interface 1 failed with 330 modem
Dear speedtouch developers, Unfortunately, I have to confirm this issue on Gentoo 2004.2 (athlon-xp arch, dev-kernel 2.6.7-r11). My green SpeedTouch USB modem is working fine with 2.4.26 kenel or Win98 on the same box, assuming my PPPoA VPI/VCI and the account configs are correct. I am using kernel-space speedtch module and I think all necessary usb/ppp modules are activated in the kernel as well. My modem seems to want UHCI. Having speedtouch-1.2-beta2 Gentoo package successfully installed and configured I obtain only: pppoa3[3080]: hostname pusb_claim_interface 1 failed and immediate modem hangup in syslog. I use '-k' switch when invoking modem_run (and, also, famous '-e 1' switch for pppoa3) and original alcaudsl.sys firmware. The current 1.3 version of SpeedTouch is not yet packaged for Gentoo distro. (I have tried to configure/make/make install it from the speedtouch-1.3.tar.bz2, but it was harder than using 1.2 package for me -- e.g. there is a silent requirement that lspci tool is present in system, debug info is minimal by default, so I soon gave up. Even my attempt to use pppoa3 1.3 binary instead of 1.2 binary with the same 1.2 config failed.) Could you please help me? Has anybody an experience with a speedtouch 1.2 on 2.6.7 kernel? Which modules to use in user space and/or in kernel space for such versions? Configuration advice? Thank you in advance, Pavel Suchmann > From: K.J. Petrie (Instabook) > Subject: [speedtouch] pusb_claim_interface 1 failed with 330 modem > Date: Wed, 02 Jun 2004 08:17:07 -0700 > > Dear all, > > I'm having trouble connecting to Wanadoo Broadband in the UK using a silver > SpeedTouch 330 under Linux Mandrake 10.0. It works well under Windows, so I > know the VPI and VCI settings are correct, although I'm not sure about > the -e value for pppoa3. > ... Příjemný design. Příjemnější cena. NOKIA 2300 již od 577 Kč http://ad.seznam.cz/clickthru?spotId=76255 Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
