Modem Not Energizing

Modem Not Energizing

Postby Germ » Nov 25th, '15, 20:01

I have a little annoyance, not exactly a problem.

I have a US Robotics USB modem. When I boot up, the USB modem is not energized. I have to go through the network applet and configure, then it energizes and works normally. I have it set to monitor the connection. Any ideas?

Thanks.
Starting in 1999: Mandrake > Mandriva > Mageia
Linux User #274693
User avatar
Germ
 
Posts: 571
Joined: Mar 30th, '11, 13:16
Location: Chelsea, Oklahoma USA

Re: Modem Not Energizing

Postby doktor5000 » Nov 25th, '15, 20:37

Can you check the logs what happens during bootup, is it at least detected as USB device?
Code: Select all
journalctl -ab | grep -i usb

should show you, but you may need to read through the whole log for one boot from top to bottom.

You may also need to check if the used driver is blacklisted in any of the /etc/modprobe.d/*conf or /etc/modprobe.conf files
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17630
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Modem Not Energizing

Postby Germ » Nov 25th, '15, 22:01

Thanks, I'll check the logs when I get home. I'm at work on a windows box right now
Starting in 1999: Mandrake > Mandriva > Mageia
Linux User #274693
User avatar
Germ
 
Posts: 571
Joined: Mar 30th, '11, 13:16
Location: Chelsea, Oklahoma USA

Re: Modem Not Energizing

Postby Germ » Nov 27th, '15, 04:15

Sorry...a little late.

Code: Select all
Nov 26 19:49:35 localhost kernel: usb 2-3: New USB device found, idVendor=0baf, idProduct=0303
Nov 26 19:49:35 localhost kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov 26 19:49:35 localhost kernel: usb 2-3: Product: USB Modem
Nov 26 19:49:35 localhost kernel: usb 2-3: Manufacturer: U.S.Robotics
Nov 26 19:49:35 localhost kernel: usb 2-3: SerialNumber: 0000002
Nov 26 19:49:35 localhost kernel: usb 7-1: new low-speed USB device number 2 using uhci_hcd
Nov 26 19:49:35 localhost kernel: usb 7-1: config 1 has an invalid interface number: 1 but max is 0
Nov 26 19:49:35 localhost kernel: cdc_acm 2-3:2.0: ttyACM0: USB ACM device
Nov 26 19:49:35 localhost kernel: usbcore: registered new interface driver cdc_acm
Nov 26 19:49:35 localhost kernel: cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters


I checked and the driver is not blacklisted.
Starting in 1999: Mandrake > Mandriva > Mageia
Linux User #274693
User avatar
Germ
 
Posts: 571
Joined: Mar 30th, '11, 13:16
Location: Chelsea, Oklahoma USA

Re: Modem Not Energizing

Postby jiml8 » Nov 27th, '15, 08:17

Network applet should give you a choice to automatically connect to this network when it is available.

What do you mean that you have to reconfigure every time? Seems to me that would mean you are not saving the configuration. If you are saving the configuration, but it is not being saved, then I would guess you have a permissions problem someplace. Take a look at /etc/NetworkManager
jiml8
 
Posts: 1253
Joined: Jul 7th, '13, 18:09

Re: Modem Not Energizing

Postby Germ » Nov 27th, '15, 14:15

I'm on dialup. All the way back through the Mandrake/Mandriva days I have never been able to connect with the network manager. I use kppp. Same thing with Mageia.

With Mageia 5 the modem will not power up until I run through the network applet. I open network applet, click 'Configure', and then the modem powers up. I close network applet then use kppp. I can't use the network applet to actually connect. The configuration of the network applet is not set up to use an actual dialup modem. It always says to make sure my simcard is inserted. GPS/Edge and stuff like that.
Starting in 1999: Mandrake > Mandriva > Mageia
Linux User #274693
User avatar
Germ
 
Posts: 571
Joined: Mar 30th, '11, 13:16
Location: Chelsea, Oklahoma USA

Re: Modem Not Energizing

Postby jiml8 » Nov 27th, '15, 18:13

OK. You are almost certainly missing a required chat script. When you invoke network manager, it is going through the necessary chat procedure to configure the device.

Once configured, kppp can control it.

You need to modify the kppp chatscript to include what is missing.

I have recently been heavily involved in driver development for these modems (though not a USR particularly; I'm mostly working with Sierra wireless chipsets) but this work is on FreeBSD. The chat script I have included here will successfully start an AT&T Netgear 313U device via ppp on FreeBSD. While your required chatscript is without doubt somewhat different than this, this should give you a clue about what is required. The only substantive difference between linux and freebsd here is the device specification; you probably would want /dev/ttyACMn or some such.

Code: Select all
default:
 set log Phase Chat LCP IPCP CCP tun command
 set device /dev/cuaU3
 set timeout 180

provider:
 set speed 921600
 set timeout 0
 set dial "ABORT BUSY TIMEOUT 3 \
 \"\" \
        AT OK-AT-OK \
        AT+CFUN=1 OK-AT-OK \
        AT+CMEE=2 OK-AT-OK \
        AT+CSQ OK \
        AT+CGDCONT=1,\\\"IP\\\",\\\"broadband\\\" OK \
        ATD*99# CONNECT"
 enable dns
 resolv writable
 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255 0.0.0.0
 add default HISADDR


edit: I think you should find the chatscript you need in the networkmanager config directory. Look in /etc/NetworkManager and see what you find.
jiml8
 
Posts: 1253
Joined: Jul 7th, '13, 18:09


Return to Networking

Who is online

Users browsing this forum: No registered users and 1 guest

cron