> 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]
