I have a problem with Suse 7.3 Professional and my USB modem. I installed 7.3 on a new disk today and was impressd with how smoothly everything went e.g. scanner works, CD writer works, UDMA drives are recognised and correct sizes obtained (my previous linux was 7.0 pro). However, I cannot get my USB modem to work at all. Linux can find it, but Yast2 needs two passes as it were to recognise it: first pass through you have to manually configure a modem; second time, the USB modem is recognised and offered as an option. (Yast1 gets it on the first go). My modem is a USB US Robotics 56K Voice Fax Modem which worked with Suse 7.0 prof, and with the later 2.4 kernels. Once recognised, I configure my ISP, and try wvdial from the command line. I get: "Cannot open /dev/modem: Invalid argument" or (depending on my hacking attempts) "Cannot open /dev/ttyACM0: Invalid argument" kinternet also reports this in its log file when connecting that way. There are three invalid argument messages for the device. I've checked the wvdial.conf and cannot see anything immediately wrong with it. I've tried removing the modem and reconfiguring with Yast1 and Yast2, all to no avail. Trying my old wvdial.conf from 7.0 also produces the above errors. /dev/modem correctly points to /dev/ttyACM0, as it did with 7.0, and correct ownerships and permissions are used. The modem is listed in the /proc filesystem as a USB device so Linux is definitely recognising it. The acm module is loaded. The modem is reported as being on /dev/ttyACM0. Yet if I do a wvdialconf /dev/null, all ports are probed but all /dev/ttyACM? ports report "Invalid argument". What's going on? What am I missing? Is wvdial broken? Cheers, Peter
Funny that. I've just had exactly the same problem with an Elsa microlink
USB modem.
JDL
----- Original Message -----
From: "Peter John Cameron"
I have a problem with Suse 7.3 Professional and my USB modem. I installed 7.3 on a new disk today and was impressd with how smoothly everything went e.g. scanner works, CD writer works, UDMA drives are recognised and correct sizes obtained (my previous linux was 7.0 pro).
However, I cannot get my USB modem to work at all. Linux can find it, but Yast2 needs two passes as it were to recognise it: first pass through you have to manually configure a modem; second time, the USB modem is recognised and offered as an option. (Yast1 gets it on the first go).
My modem is a USB US Robotics 56K Voice Fax Modem which worked with Suse 7.0 prof, and with the later 2.4 kernels.
Once recognised, I configure my ISP, and try wvdial from the command line. I get:
"Cannot open /dev/modem: Invalid argument"
or (depending on my hacking attempts)
"Cannot open /dev/ttyACM0: Invalid argument"
kinternet also reports this in its log file when connecting that way. There are three invalid argument messages for the device. I've checked the wvdial.conf and cannot see anything immediately wrong with it.
I've tried removing the modem and reconfiguring with Yast1 and Yast2, all to no avail. Trying my old wvdial.conf from 7.0 also produces the above errors. /dev/modem correctly points to /dev/ttyACM0, as it did with 7.0, and correct ownerships and permissions are used.
The modem is listed in the /proc filesystem as a USB device so Linux is definitely recognising it. The acm module is loaded. The modem is reported as being on /dev/ttyACM0. Yet if I do a wvdialconf /dev/null, all ports are probed but all /dev/ttyACM? ports report "Invalid argument".
What's going on? What am I missing? Is wvdial broken?
Cheers, Peter
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
Funny that. I've just had exactly the same problem with an Elsa microlink USB modem.
There seems to be something wrong with the USB in 7.3. I have two USB devices: the modem and an Epson Perfection scanner. The scanner works with no problems. On the surface all seems well with the modem: it is recognised by Linux and listed in the /proc/bus/usb/devices file, the acm module and the other USB modules are loaded. However, any attempt to read or write to the /dev/ttyACM0 modem device gives an "Invalid argument" error. I checked the /proc/bus/usb/devices file again. The acm driver is not associated with the modem. OTOH, the scanner driver is associated with the scanner. So, the USB subsystem is successfully loading the acm driver but is not associating it with the modem device. No idea why, and no idea how to fix it :( The modem worked with Suse 7.0 and the 2.2 kernels and 2.4 kernels up to 2.4.5, with compiled-in USB support. The USB documentation says that if no driver is associated then it means the modem is not ACM-compliant. I think USB is broken. Peter
participants (2)
-
John D Lamb
-
Peter John Cameron