Problem with 2.6-testXX and alcatel speedtouch usb modem
Quoted 10 lines
I try to make this modem working.
It works very well on kernel 2.4 series.
It work with some kernel 2.6 until test2-mm1.
But since test2-mm1, the newer kernel doesn't work anymore. There is 2 related drivers for this modem.
The one which is included in the kernel and which can be found here :
http://www.linux-usb.org/SpeedTouch/
and the one which I've always used until now :
speedtouch.sourceforge.net
Quoted 5 lines
when I notice that the old one doesn't work anymore, I try with the driver which included in the kernel, without success.
It crashed when I do "pppd call adsl".
I can load the firmware.
Looks like this is happening to all 2.6.0-test3 users with speedtouch usb modems
And i heard that speedtouch.sf.net developers want to leave 2.6 tree stabilize more a little bit to continue develop drivers with the correct support.
Im sure we can help test drivers with the correct support for 2.6
Signature · 5 lines
______________________________________________ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze
Quoted 13 lines · Luis Medinas
Quoted 12 lines
I try to make this modem working.
It works very well on kernel 2.4 series.
It work with some kernel 2.6 until test2-mm1.
But since test2-mm1, the newer kernel doesn't work anymore. There is 2 related drivers for this modem.
The one which is included in the kernel and which can be found here :
http://www.linux-usb.org/SpeedTouch/
and the one which I've always used until now :
speedtouch.sourceforge.netwhen I notice that the old one doesn't work anymore, I try with the driver which included in the kernel, without success.
Quoted 7 lines
Quoted 2 lines
It crashed when I do "pppd call adsl".
I can load the firmware.Looks like this is happening to all 2.6.0-test3 users with speedtouch usb modems And i heard that speedtouch.sf.net developers want to leave 2.6 tree stabilize more a little bit to continue develop drivers with the correct support.
Um, as you have helped narrow down where the problem happened, I would _really_ suggest they get involved in order to get the 2.6 tree to a "stable" state. Otherwise this bug is not going to get fixed due to the fact that this is the only driver having problems right now.
thanks,
greg k-h