... > yes, I agree that mixing one HOW-TO with another > is not very wise, but that is what you usually > do when things don't work. But isn't true that > modem_run is independent of the connection protocol? > I should be able to run modem_run even if I can't > make a connection after that. I really don't under- > stand why modem_run returns zero if I use the > correct firmware... > > ... > > > "modem_run" right? I don't think this should > > > depend on the extra modules I compiled in the > > kernel. > > > > > it is easier to follow what happen when features are > > compiled as modules. > > You could load/unload modules and not have some > > warning when modules compiled in > > kernel. > > Did you have usb compiled as module? Is this set CONFIG_USB_DEVICEFS=y
Looking in speedtouch Changelog from cvs http://speedtouch.cvs.sourceforge.net/speedtouch/speedtouch/ChangeLog?view=markup your problem may be Suse specific but the fix should be include in 1.3.1 "17/09/2004 -> src/speedtouch-start.in src/speedtouch-stop.in: Benoit PAPILLAULT Handle the /proc/bus/usb/devices_please-use-sysfs-instead used on Suse 9.1" There is a problem for a new feature in speedtouch-1.3.1 with the semaphore "modem_run is now controlled by a mutex and a shared value. Usefull to handle the case where modem_run is run multiple times." This was an attempt to not have modem_run failing to load the firmware when it is already loaded. But it does not correctly work in every case and could be the reason of modem_run silently exiting. modem_run remember the firmware is loaded even it may not actually be true (because modem was unplugged or the usb was reset). You may try with v1.3.0 wich does not have that feature but you may stopped by the /proc/bus/usb/devices_please-use-sysfs-instead in Suse 9.1 Or you could try with a cvs version, I think to recall that the semaphore problem was fixed in cvs but I have not tested. Or you may try with a 2.6 kernel on your Suse and no more use modem_run Gilles Liste de diffusion modem ALCATEL SpeedTouch USB Pour se désinscrire : mailto:[EMAIL PROTECTED]
