2.6.10 and speedtouch usb

2.6.10 and speedtouch usb

[Serge Tchesmeli]

Hi,

i have try the new kernel 2.6.10, compil with exactly the same option from my 
2.6.9 (i have copied the .config) but i notice a high load on my machine, and 
i see that was syslogd.
So, i look at my log and see:

Dec 26 19:40:44 gateway last message repeated 137 times
Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device status
Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on ep0in
Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
modem_run rqt 192 rq 18 len 8 ret -110
Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
not claim interface 0 before use
Dec 26 19:40:49 gateway last message repeated 413 times
Dec 26 19:40:51 gateway kernel: usb 2-1: events/0 timed out on ep0in
Dec 26 19:40:51 gateway kernel: SpeedTouch: Error -110 fetching device status
Dec 26 19:40:51 gateway kernel: usb 2-1: modem_run timed out on ep0in
Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
modem_run rqt 192 rq 18 len 8 ret -110
Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
not claim interface 0 before use
Dec 26 19:40:59 gateway last message repeated 1105 times

The speedtouch modem work, connection is etablished and work well.

Re: 2.6.10 and speedtouch usb

[Andrew Benton]

Serge Tchesmeli wrote:
> Hi,
> 
> i have try the new kernel 2.6.10, compil with exactly the same option from my 
> 2.6.9 (i have copied the .config) but i notice a high load on my machine, and 
> i see that was syslogd.
> So, i look at my log and see:
> 
> Dec 26 19:40:44 gateway last message repeated 137 times
> Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110

Are you using the kernel or userspace driver?

Re: 2.6.10 and speedtouch usb

[Serge Tchesmeli]

Le Lundi 27 Décembre 2004 14:25, Andrew Benton a écrit :
> Serge Tchesmeli wrote:
> > Hi,
> >
> > i have try the new kernel 2.6.10, compil with exactly the same option
> > from my 2.6.9 (i have copied the .config) but i notice a high load on my
> > machine, and i see that was syslogd.
> > So, i look at my log and see:
> >
> > Dec 26 19:40:44 gateway last message repeated 137 times
> > Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
> > Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device
> > status Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on
> > ep0in Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL
> > failed cmd modem_run rqt 192 rq 18 len 8 ret -110
>
> Are you using the kernel or userspace driver?

I'm using the kernel speedtouch driver.

info: i have made "make oldconfig" :) (i say that before some users ask me in 
private)

Re: 2.6.10 and speedtouch usb

[Andrew Benton]

Serge Tchesmeli wrote:
> Le Lundi 27 Décembre 2004 14:25, Andrew Benton a écrit :
> 
>>Serge Tchesmeli wrote:
>>
>>>Hi,
>>>
>>>i have try the new kernel 2.6.10, compil with exactly the same option
>>>from my 2.6.9 (i have copied the .config) but i notice a high load on my
>>>machine, and i see that was syslogd.
>>>So, i look at my log and see:
>>>
>>>Dec 26 19:40:44 gateway last message repeated 137 times
>>>Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
>>>Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device
>>>status Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on
>>>ep0in Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL
>>>failed cmd modem_run rqt 192 rq 18 len 8 ret -110
>>
>>Are you using the kernel or userspace driver?
> 
> 
> I'm using the kernel speedtouch driver.
> 
Well it looks like modem_run is giving you problems. If you want you could do 
without it and  let the kernel load the firmware itself. To try this you will 
need to  prepare the firmware by splitting it into two parts To do that you'll 
need a copy of the speedtouch-1.3.1 driver
http://prdownloads.sourceforge.net/speedtouch/speedtouch-1.3.1.tar.gz?download
untar it and cd into the speedtouch-1.3.1/src folder and then enter

gcc -o firmware firmware.c -DSTANDALONE_EXTRACTER

That will compile a binary called firmware. You can use that to split  the 
modems firmware into two parts. If (for example) the firmware is  called mgmt.o, 
copy it into the speedtouch-1.3.1/src folder and then enter

./firmware mgmt.o
mv boot.bin speedtch-1
mv firmware.bin speedtch-2

That will create two files, boot.bin and firmware.bin. Rename boot.bin  -> 
speedtch-1 and firmware.bin -> speedtch-2. Then you need to copy  these two 
speedtch files into hotplugs firmware folder. You can find  this by reading 
/etc/hotplug/firmware.agent

cat /etc/hotplug/firmware.agent | grep FIRMWARE_DIR=

Make sure you enabled hotplug firmware loading in your kernel config
CONFIG_FW_LOADER=y
and check that hotplug has this line in /etc/hotplug/usb.usermap

speedtouch 0x0003 0x06b9 0x4061 0x0000 0x0000 0x00 0x00 0x00 0x00 0x00  0x00 
0x00000000

Re: 2.6.10 and speedtouch usb

[Serge Tchesmeli]

>
> Well it looks like modem_run is giving you problems. If you want you could
> do without it and  let the kernel load the firmware itself. To try this you
> will need to  prepare the firmware by splitting it into two parts To do
> that you'll need a copy of the speedtouch-1.3.1 driver
> http://prdownloads.sourceforge.net/speedtouch/speedtouch-1.3.1.tar.gz?downl
>oad untar it and cd into the speedtouch-1.3.1/src folder and then enter
>
.../...

Ok i will try this next week end, because this machine is actually at 180km 
away from me and if i do something wrong with the modem, i will not be able 
to reach it :)
Actually i have reboot it on 2.6.9 and it work well.
So i will tell you more next week.

Thanks for all :)

Re: 2.6.10 and speedtouch usb

[Duncan Sands]

> i have try the new kernel 2.6.10, compil with exactly the same option from my 
> 2.6.9 (i have copied the .config) but i notice a high load on my machine, and 
> i see that was syslogd.
> So, i look at my log and see:
> 
> Dec 26 19:40:44 gateway last message repeated 137 times
> Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
> not claim interface 0 before use
> Dec 26 19:40:49 gateway last message repeated 413 times
> Dec 26 19:40:51 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:51 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:51 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110
> Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
> not claim interface 0 before use
> Dec 26 19:40:59 gateway last message repeated 1105 times

Hi Serge, please turn on the kernel config option CONFIG_USB_DEBUG.  Also, change

/*
#define DEBUG
#define VERBOSE_DEBUG
*/

to

#define DEBUG
/*
#define VERBOSE_DEBUG
*/

in drivers/usb/atm/speedtch.c and drivers/usb/atm/usb_atm.c.  You should then
get a bunch of stuff in your system logs.

Ciao,

Duncan.

Re: 2.6.10 and speedtouch usb

[Roman Kagan]

On Wed, Dec 29, 2004 at 04:04:21PM +0000, Serge Tchesmeli wrote:
> i have try the new kernel 2.6.10, compil with exactly the same option from my 
> 2.6.9 (i have copied the .config) but i notice a high load on my machine, and 
> i see that was syslogd.
> So, i look at my log and see:
> 
> Dec 26 19:40:44 gateway last message repeated 137 times
> Dec 26 19:40:46 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:46 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:46 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110
> Dec 26 19:40:46 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
> not claim interface 0 before use
> Dec 26 19:40:49 gateway last message repeated 413 times
> Dec 26 19:40:51 gateway kernel: usb 2-1: events/0 timed out on ep0in
> Dec 26 19:40:51 gateway kernel: SpeedTouch: Error -110 fetching device status
> Dec 26 19:40:51 gateway kernel: usb 2-1: modem_run timed out on ep0in
> Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: USBDEVFS_CONTROL failed cmd 
> modem_run rqt 192 rq 18 len 8 ret -110
> Dec 26 19:40:51 gateway kernel: usb 2-1: usbfs: process 5296 (modem_run) did 
> not claim interface 0 before use
> Dec 26 19:40:59 gateway last message repeated 1105 times
> 
> The speedtouch modem work, connection is etablished and work well.

It looks like the line status monitoring implemented in the driver in
2.6.10 interferes with that in modem_run.  Unless you have a reason to
keep using modem_run, you can let it go and use the line status
monitoring and firmware loading facilities provided by the driver
itself.  Just follow Andrew's advice.

  Roman.

Re: 2.6.10 and speedtouch usb

[Duncan Sands]

> It looks like the line status monitoring implemented in the driver in
> 2.6.10 interferes with that in modem_run.  Unless you have a reason to
> keep using modem_run, you can let it go and use the line status
> monitoring and firmware loading facilities provided by the driver
> itself.  Just follow Andrew's advice.

Hi Roman, yes, but it would be good to understand what is going wrong - the
debug info should help.  It would also be good to know the modem revision.
Serge, what revision do you see in /proc/bus/usb/devices?

All the best,

Duncan.

Re: 2.6.10 and speedtouch usb

[Serge Tchesmeli]

Le Jeudi 30 Décembre 2004 13:00, Duncan Sands a écrit :
> > It looks like the line status monitoring implemented in the driver in
> > 2.6.10 interferes with that in modem_run.  Unless you have a reason to
> > keep using modem_run, you can let it go and use the line status
> > monitoring and firmware loading facilities provided by the driver
> > itself.  Just follow Andrew's advice.
>
> Hi Roman, yes, but it would be good to understand what is going wrong - the
> debug info should help.  It would also be good to know the modem revision.
> Serge, what revision do you see in /proc/bus/usb/devices?
>
> All the best,
>
> Duncan.
> -
I will add debug support, look at modem revision etc.. this weekend and send 
you the informations next week :)
Thanks for all, see you in 2005 for more informations ;)

++

Re: 2.6.10 and speedtouch usb

[Serge Tchesmeli]

Le Jeudi 30 Décembre 2004 13:00, Duncan Sands a écrit :
> > It looks like the line status monitoring implemented in the driver in
> > 2.6.10 interferes with that in modem_run.  Unless you have a reason to
> > keep using modem_run, you can let it go and use the line status
> > monitoring and firmware loading facilities provided by the driver
> > itself.  Just follow Andrew's advice.
>
> Hi Roman, yes, but it would be good to understand what is going wrong - the
> debug info should help.  It would also be good to know the modem revision.
> Serge, what revision do you see in /proc/bus/usb/devices?
>
> All the best,
>
Hi all, HAPPY NEW YEAR 2005!! :)

So, here the informatios asked:

- Modem revision: 

T:  Bus=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=ff(vend.) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=06b9 ProdID=4061 Rev= 0.00
S:  Manufacturer=ALCATEL
S:  Product=Speed Touch USB
S:  SerialNumber=0090D02E7A5A
C:* #Ifs= 3 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=ff(vend.) Sub=00 Prot=00 Driver=usbfs
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=50ms
I:  If#= 1 Alt= 0 #EPs= 0 Cls=ff(vend.) Sub=00 Prot=00 Driver=speedtch
I:  If#= 1 Alt= 1 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=speedtch
E:  Ad=06(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 2 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=speedtch
E:  Ad=06(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 3 #EPs= 3 Cls=ff(vend.) Sub=00 Prot=00 Driver=speedtch
E:  Ad=06(O) Atr=02(Bulk) MxPS=  16 Ivl=0ms
E:  Ad=07(O) Atr=02(Bulk) MxPS=  16 Ivl=0ms
E:  Ad=87(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
E:  Ad=05(O) Atr=02(Bulk) MxPS=   8 Ivl=0ms
E:  Ad=85(I) Atr=02(Bulk) MxPS=   8 Ivl=0ms



- Debug log:

Dec 31 22:53:05 gateway kernel: usb 2-1: bogus endpoint ep7in in 
usb_submit_urb (bad maxpacket 0)<7>divert: not allocating divert_blk for 
non-ethernet device ppp0
Dec 31 22:53:05 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:05 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:08 gateway last message repeated 403 times
Dec 31 22:53:08 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:08 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:11 gateway last message repeated 410 times
Dec 31 22:53:11 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:11 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:14 gateway last message repeated 407 times
Dec 31 22:53:14 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:14 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:17 gateway last message repeated 409 times
Dec 31 22:53:17 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:17 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:20 gateway last message repeated 408 times
Dec 31 22:53:20 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:20 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:23 gateway last message repeated 406 times
Dec 31 22:53:23 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:23 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:26 gateway last message repeated 407 times
Dec 31 22:53:26 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:26 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:29 gateway last message repeated 412 times
Dec 31 22:53:29 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:29 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:32 gateway last message repeated 407 times
Dec 31 22:53:32 gateway kernel: usb 2-1: bogus endpoint ep7out in 
usb_submit_urb (bad maxpacket 0)<4>usb 2-1: usbfs: process 6023 (modem_run) 
did not claim interface 0 before use
Dec 31 22:53:32 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:53:35 gateway last message repeated 409 times
Dec 31 22:53:35 gateway kernel: divert: no divert_blk to free, ppp0 not 
ethernet
Dec 31 22:53:35 gateway kernel: usb 2-1: usbfs: process 6023 (modem_run) did 
not claim interface 0 before use
Dec 31 22:54:05 gateway last message repeated 4089 times


and some other log in messages:

Dec 31 22:53:35 gateway modem_run[6023]: Error reading interrupts
Dec 31 22:54:01 gateway last message repeated 3538 times


Note: 
I don't have try to change modem_run with the kernel firmware loader, i was 
very busy this week end (new year + my grand mother die :( ), i'm still in 
2.6.9 with modem_run and kernel speedtouch.