LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 04-26-2010, 05:13 PM   #1
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Rep: Reputation: 4
Cannot get AC850 working under Ubuntu (Karmic Koala)


I have a Sierra AC850 wireless UMTS PCMCIA card. I've made multiple attempts to get it working under Linux without success. Now I've come full circle and seem to be back where I was 6 months ago (ummmm make that 16 months ago - and it seemed to get further then). I'm using the same device on my WinXP computer to compile this request... so the card works.

Operating system is Ubuntu Karmic Koala (9.10 if I remember correctly).

The chatscript (/etc/chatscripts/eplus) looks like this:

TIMEOUT 240
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT "ERROR"
ABORT "NO ANSWER"
ABORT "BUSY"
"" "+++atz"
OK "ATE0V1"
OK "AT_OPSYS=3,2"
OK AT+CGDCONT=1,"IP","internet.eplus.de","",0,0
OK "ATD*99***1#"
"CONNECT" ""

The eplus script in /etc/ppp/peers looks like this:

-detach
/dev/umts
460800
debug
defaultroute
usepeerdns
user wapuser1
show-password
crtscts
lock
#idle 300
idle 30
noauth
noipdefault
novj
nomagic
#user eplus
user umts
connect '/usr/sbin/chat -v -f /etc/chatscripts/eplus'

When I enter "pon eplus" I get the following response:

Script /usr/sbin/chat -v -f /etc/chatscripts/eplus finished (pid 2189), status = 0x3
Connect script failed

Checking /var/log/syslog I find nothig helpful:

Apr 26 22:43:06 achim-laptop pppd[2187]: pppd 2.4.5 started by achim, uid 1000
Apr 26 22:43:07 achim-laptop chat[2190]: timeout set to 240 seconds
Apr 26 22:43:07 achim-laptop chat[2190]: abort on (NO CARRIER)
Apr 26 22:43:07 achim-laptop chat[2190]: abort on (NO DIALTONE)
Apr 26 22:43:07 achim-laptop chat[2190]: abort on (ERROR)
Apr 26 22:43:07 achim-laptop chat[2190]: abort on (NO ANSWER)
Apr 26 22:43:07 achim-laptop chat[2190]: abort on (BUSY)
Apr 26 22:43:07 achim-laptop chat[2190]: send (+++atz^M)
Apr 26 22:43:07 achim-laptop chat[2190]: expect (OK)
Apr 26 22:43:59 achim-laptop wpa_supplicant[1017]: CTRL-EVENT-SCAN-RESULTS
Apr 26 22:44:59 achim-laptop wpa_supplicant[1017]: CTRL-EVENT-SCAN-RESULTS
Apr 26 22:45:59 achim-laptop wpa_supplicant[1017]: CTRL-EVENT-SCAN-RESULTS
Apr 26 22:46:59 achim-laptop wpa_supplicant[1017]: CTRL-EVENT-SCAN-RESULTS
Apr 26 22:47:07 achim-laptop chat[2190]: alarm
Apr 26 22:47:07 achim-laptop chat[2190]: Failed
Apr 26 22:47:07 achim-laptop pppd[2187]: Script /usr/sbin/chat -v -f /etc/chatscripts/eplus finished (pid 2189), status = 0x3
Apr 26 22:47:07 achim-laptop pppd[2187]: Connect script failed
Apr 26 22:47:08 achim-laptop pppd[2187]: Exit.

The entries "CTRL-EVENT-SCAN-RESULTS" can be ignored, so I'm wondering what " status = 0x3" actually means. A search on Google has been of no help.

Can anybody help? The Ubuntu Forums have reulted in zero response, so I'm hoping this forum will at least give me something to go on.

Achim

P.S. Replies in German are welcome!

P.P.S. I checked a seemingly unrelated forum. As a result i tried the following...

I changed the script to have "ATZ" in place of "+++atz" and now get (/var/log/syslog):

Apr 27 00:41:52 achim-laptop pppd[2469]: pppd 2.4.5 started by achim, uid 1000
Apr 27 00:41:53 achim-laptop chat[2472]: timeout set to 240 seconds
Apr 27 00:41:53 achim-laptop chat[2472]: abort on (NO CARRIER)
Apr 27 00:41:53 achim-laptop chat[2472]: abort on (NO DIALTONE)
Apr 27 00:41:53 achim-laptop chat[2472]: abort on (ERROR)
Apr 27 00:41:53 achim-laptop chat[2472]: abort on (NO ANSWER)
Apr 27 00:41:53 achim-laptop chat[2472]: abort on (BUSY)
Apr 27 00:41:53 achim-laptop chat[2472]: send (ATZ^M)
Apr 27 00:41:53 achim-laptop chat[2472]: expect (OK)
Apr 27 00:41:53 achim-laptop chat[2472]: ^M
Apr 27 00:41:53 achim-laptop chat[2472]: OK
Apr 27 00:41:53 achim-laptop chat[2472]: -- got it
Apr 27 00:41:53 achim-laptop chat[2472]: send (ATE0V1^M)
Apr 27 00:41:53 achim-laptop chat[2472]: expect (OK)
Apr 27 00:41:53 achim-laptop chat[2472]: ^M
Apr 27 00:41:53 achim-laptop chat[2472]: ATE0V1^M^M
Apr 27 00:41:53 achim-laptop chat[2472]: OK
Apr 27 00:41:53 achim-laptop chat[2472]: -- got it
Apr 27 00:41:53 achim-laptop chat[2472]: send (AT_OPSYS=1,2^M)
Apr 27 00:41:53 achim-laptop chat[2472]: expect (OK)
Apr 27 00:41:53 achim-laptop chat[2472]: ^M
Apr 27 00:41:53 achim-laptop chat[2472]: ^M
Apr 27 00:41:53 achim-laptop chat[2472]: ERROR
Apr 27 00:41:53 achim-laptop chat[2472]: -- failed
Apr 27 00:41:53 achim-laptop chat[2472]: Failed (ERROR)
Apr 27 00:41:53 achim-laptop pppd[2469]: Script /usr/sbin/chat -v -f /etc/chatscripts/eplus finished (pid 2471), status = 0x6
Apr 27 00:41:53 achim-laptop pppd[2469]: Connect script failed
Apr 27 00:41:54 achim-laptop pppd[2469]: Exit.

So now what does "status = 0x6" mean?

Incidentally, I tried "AT_OPSYS=3,2" first. For those that don't know, "AT_OPSYS=3,2" means "try UMTS first and fall back to GPRS". The string "AT_OPSYS=1,2" means "UMTS only". Both give me the same response.

Last edited by achim_59; 04-26-2010 at 06:21 PM. Reason: New information
 
Old 04-28-2010, 10:29 AM   #2
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
When you insert your PCMCIA into the linux box, please in root console type:
lspcmcia
or: pccardctl ls

and: ifconfig -a
and: dmesg | tail -n 50

Post output here please.


Thanks
 
Old 05-04-2010, 04:10 PM   #3
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Hi nimnull22,

Thanks for the reply. I would have replied sooner but I found out that I left my USB stick at home and couldn't transfer data to the WinXP machine. Had to rush out and buy one today.

Here's the data you asked for:
>>>>>>>>>>>>>
Response from "lspcmcia":

Socket 0 Bridge: [yenta_cardbus] (bus ID: 0000:0b:00.0)
Socket 0 Device 0: [serial_cs] (bus ID: 0.0)


Response from "ifconfig -a":

eth0 Link encap:Ethernet HWaddr 00:15:58:2f:32:c2
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:16

eth1 Link encap:Ethernet HWaddr 00:13:ce:e5:e0:f3
inet6 addr: fe80::213:ceff:fee5:e0f3/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:84 (84.0 B)
Interrupt:21 Base address:0x8000 Memory:b4001000-b4001fff

irda0 Link encap:IrLAP HWaddr 00:00:00:00
NOARP MTU:2048 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:8
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)


response from "dmesg | tail -n 50
[ 18.659611] tg3 0000:02:00.0: PME# disabled
[ 18.976531] __ratelimit: 6 callbacks suppressed
[ 18.976535] type=1505 audit(1272910741.112:12): operation="profile_replace" pid=978 name=/usr/share/gdm/guest-session/Xsession
[ 18.994157] type=1505 audit(1272910741.128:13): operation="profile_replace" pid=979 name=/sbin/dhclient3
[ 18.994837] type=1505 audit(1272910741.128:14): operation="profile_replace" pid=979 name=/usr/lib/NetworkManager/nm-dhcp-client.action
[ 18.995208] type=1505 audit(1272910741.128:15): operation="profile_replace" pid=979 name=/usr/lib/connman/scripts/dhclient-script
[ 19.001859] type=1505 audit(1272910741.136:16): operation="profile_replace" pid=980 name=/usr/bin/evince
[ 19.034067] type=1505 audit(1272910741.168:17): operation="profile_replace" pid=980 name=/usr/bin/evince-previewer
[ 19.048831] type=1505 audit(1272910741.184:18): operation="profile_replace" pid=980 name=/usr/bin/evince-thumbnailer
[ 19.057734] type=1505 audit(1272910741.192:19): operation="profile_replace" pid=982 name=/usr/lib/cups/backend/cups-pdf
[ 19.058558] type=1505 audit(1272910741.192:20): operation="profile_replace" pid=982 name=/usr/sbin/cupsd
[ 19.060814] type=1505 audit(1272910741.196:21): operation="profile_replace" pid=983 name=/usr/sbin/tcpdump
[ 19.185907] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 20.150793] [drm] Setting GART location based on new memory map
[ 20.152603] [drm] Loading R300 Microcode
[ 20.152645] [drm] Num pipes: 1
[ 20.152654] [drm] writeback test succeeded in 1 usecs
[ 20.244096] usb 3-1: new low speed USB device using uhci_hcd and address 6
[ 20.364030] usb 3-1: device descriptor read/64, error -71
[ 20.592136] usb 3-1: device descriptor read/64, error -71
[ 20.808143] usb 3-1: new low speed USB device using uhci_hcd and address 7
[ 20.905147] psmouse serio2: ID: 10 00 64
[ 20.932048] usb 3-1: device descriptor read/64, error -71
[ 21.160156] usb 3-1: device descriptor read/64, error -71
[ 21.376159] usb 3-1: new low speed USB device using uhci_hcd and address 8
[ 21.800020] usb 3-1: device not accepting address 8, error -71
[ 21.912058] usb 3-1: new low speed USB device using uhci_hcd and address 9
[ 22.328049] usb 3-1: device not accepting address 9, error -71
[ 22.328073] hub 3-0:1.0: unable to enumerate USB device on port 1
[ 25.273523] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 25.636478] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input8
[ 29.220024] eth1: no IPv6 routers present
[ 4146.392089] usb 3-2: new low speed USB device using uhci_hcd and address 10
[ 4146.546314] usb 3-2: configuration #1 chosen from 1 choice
[ 4146.601223] usbcore: registered new interface driver hiddev
[ 4146.616045] input: HID 062a:0000 as /devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0/input/input9
[ 4146.616238] generic-usb 0003:062A:0000.0001: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0000] on usb-0000:00:1d.1-2/input0
[ 4146.616275] usbcore: registered new interface driver usbhid
[ 4146.616282] usbhid: v2.6:USB HID core driver
[ 4149.952121] usb 3-2: USB disconnect, address 10
[ 4152.400091] usb 3-1: new low speed USB device using uhci_hcd and address 11
[ 4152.554347] usb 3-1: configuration #1 chosen from 1 choice
[ 4152.571632] input: HID 062a:0000 as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input10
[ 4152.571732] generic-usb 0003:062A:0000.0002: input,hidraw0: USB HID v1.10 Mouse [HID 062a:0000] on usb-0000:00:1d.1-1/input0
[ 4670.236106] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 4670.236122] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
[ 4670.236165] pcmcia_socket pcmcia_socket0: cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
[ 4670.244286] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
[ 4670.280119] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
[ 4670.351045] 0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A

To add to the confusion - response from "ls -lha /dev/um*":
crw-rw---- 1 root dialout 4, 66 2010-05-03 21:36 /dev/umts

<<<<<<<<<<<<<<<<

Since nothing has changed, I didn't try to connect again. I hope this stuff helps, I confess that much of it is a complete mystery to me.

Thanks again for taking the time to look at the problem.

Regards

Achim
 
Old 05-04-2010, 05:08 PM   #4
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
[ 4670.236106] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 4670.236122] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
[ 4670.236165] pcmcia_socket pcmcia_socket0: cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
[ 4670.244286] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
[ 4670.280119] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis


It looks like your dongle needs firmware (Card Information Structure): pcmcia 0.0: firmware: requesting SW_8xx_SER.cis.
I suppose you do not have it.

Second, I expected that "lspcmcia or pccardctl ls" should shows a device connected to slot, but it doesn't.
Anyway, first of all, you need firmware. I hope it is the same like any other usb modems, you need to put it where all firmware is. And I hope card will read it.

But other problem - linux did not create any interface for that device. May be you need some additional program which will communicate to /dev/umts through created interface.

I really suggest to search in internet about firmware and umts card + linux.


Look at /etc/pcmcia
And in my Suse there is a doc file, may be it helps you:

PCMCIA Basics
^^^^^^^^^^^^^
PCMCIA stands for 'PC Memory Card International Association'. Despite it is the
name of the organisation it is commonly used for the devices, too. To be able
to connect a PCMCIA card you need a PCMCIA bridge, also called socket. Then
there are two types of cards. At first there were only PC cards, which use a
16bit bus like ISA devices. Later CardBus cards became more important. These
use a 32bit bus and can be viewed as special PCI cards. You can recognize
CardBus cards by the golden stripe above the connector row.

To get the socket working it needs
- a driver
- additional IO and memory ranges for PC cards
After the bridge was successfully initialized, it can detect the presence of a
card. The driver of the bridge will then perform the following steps:
- detemine the type of the card
- supply the proper voltage
- assign IO and memory ranges to the card and a IRQ line
- trigger initialization of the card (load a driver)
- some cards additionally need an upload of the Card Information Structure (CIS)


Bridge/Socket Initialisation
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
PCMCIA Bridges are mostly PCI devices. These are initialized via the hotplug
susbsystem which is now compeletly controlled from udev. For each PCI event
udev calls /sbin/hwup to load drivers. /sbin/hwup will look for a device
configuration file in /etc/sysconfig/hardware or simply call modprobe with the
modalias string provided from the kernel.

This triggers new hotplug events. One for each PCMCIA socket. The pcmcia_socket
events load (also via udev and /sbin/hwup) the 'pcmcia' kernel module, which
provides additional infrastructure (e.g. /sys/bus/pcmcia). Then all IO and
memory ranges from /etc/pcmcia/config.opts are added to the socket. The card
services in the kernel check these ranges. This may crash the machine if the
wrong ranges were added to config.opts. You will see a line in syslog if the
ranges were added:
Sep 4 09:21:08 oran kernel: cs: IO port probe 0x100-0x3af: clean.


Card Initialisation
^^^^^^^^^^^^^^^^^^^
If a card was alreadey plugged before socket initialization or was plugged
later a pcmcia hotplug event will be triggered. For CardBus cards this will be
a 'pci' event, for PC cards a 'pcmcia' event. For both events udev will load a
driver module specified in modalias string (/sys/$devpath/modalias). Also
module loading might trigger a firmware hotplug event. A special firmware
handler looks for a firmware and loads it.

For PC cards there are some specials:
- The firmware is called CIS (card information structure). Normally these cards
have their own CIS inside the card. The CIS provides additional information
about the implementation details of the card. But the CIS is sometimes broken.
Therefore CIS can be loaded from disk via udev firmware event if the cards
CIS seems broken.
- All current linux device drivers contain a device id table. They will operate
only on devices which are listed there. For PC cards it is possible that this
device matching is reduced to the card function. That means that a loaded PC
card networt driver feels responsible for any PC card NIC. This may help in
some cases. This will be used if no module can be loaded via modalias.


Interface Setup
^^^^^^^^^^^^^^^
Depending on the card type there will be different interfaces registered after
card initialization. Again these are set up via udevs hotplug handlers in a
interface specific way. This happens in a common way independent of the type of
the hardware underlying the interface.

P.S. Firmware (Card Information Structure) should be on CD with your dongle, I hope it be used with linux.

Last edited by nimnull22; 05-04-2010 at 05:59 PM.
 
Old 05-05-2010, 04:52 PM   #5
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Quote:
Originally Posted by nimnull22 View Post
[ 4670.236106] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 4670.236122] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
[ 4670.236165] pcmcia_socket pcmcia_socket0: cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
[ 4670.244286] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
[ 4670.280119] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis


It looks like your dongle needs firmware (Card Information Structure): pcmcia 0.0: firmware: requesting SW_8xx_SER.cis.
I suppose you do not have it.

Second, I expected that "lspcmcia or pccardctl ls" should shows a device connected to slot, but it doesn't.
Anyway, first of all, you need firmware. I hope it is the same like any other usb modems, you need to put it where all firmware is. And I hope card will read it.

...
Hi nimnull22,

You are obviously far more clued up on the hardware issues than I am. Still, I don't think that the firmware is the problem, because I do indeed have the firmware. It is installed in /lib/firmware. The ac850 is an odd beastie in that it identifies itself as an ac750. I got this gem of information from another forum (in German).

Quote:
CIS File herunterladen: http://www.sierrawireless.com/softwa...x_Linux.tar.gz

auspacken und das SW_8xx_SER.cis nach SW_7xx_SER.cis umbenennen und anschliessend nach /lib/firmware kopieren.

Dies ist Leider noetig, weil die 750er aircard und die 850 die selben manufacture ID und Product ID am pcmcia bus tragen. (Beschissen gell!?)

Fuer Kernel nach 2.6.13 muessen die pcmciautils installiert sein, und der Cardmanager prozess darf nicht mehr laufen.
...
I did all that and to be on the safe side I kept both versions (i.e. SW_7xx_SER.cis and SW_8xx_SER.cis). The contents are, of course, identical.

Hence I don't think the firmware is the problem. My belief is supported by the fact that the init-string, "ATZ", doesn't give an error but rather "OK".

In addition, when I first upgraded to "karmic koala" I tried inserting the card without changing anything. My system then listed "eplus" as a network connection but told me I needed a password. For eplus the password is "eplus" but that didn't do me any good, because I had nowhere to enter it. Now eplus is still listed but I don't get a password prompt (and no connection, either).

What has changed since my earlier attempts is that I added the following rule to /etc/udev/rules.d/70-persistent-net-rules.

Quote:
# Original suggested script
# BUS=="pcmcia", SYSFS{card_id}=="0x0710", NAME="umts", SYMLINK="tts/umts", RUN+="/usr/local/bin/umtsinit"
# If correct, should add the pin for umts card init
# additioal: NO PIN!! There is no pin script defined. The pin on the aircard has been turned off.
BUS=="pcmcia", SYSFS{card_id}=="0x0710", NAME="umts", SYMLINK="tts/umts", RUN+="/usr/local/bin/umtsinit"
I previously had this in /lib/udev/rules.d/99-aircard-rules. I can't see that this made a great deal of difference. The chatscript still dies at the point where I try to get a UMTS connection. I suspect that it wouldn't make any difference if I tried GPRS, either... the UMTS works fine on Windoze.

Another difference is that I have not installed pcmciautils as suggested by that German (Swiss actually) post. I can't do that until I get an internet connection again, which means waiting until the weekend. At the moment I'm in a hotel in Darmstadt with no reliable internet other than the ac850. I could try the free WLAN here, but it is decidedly "flaky", since it drops out every few minutes and you need to reconnect (yes, I've tried it before and it's a pain).

One last thing. I previously tried the command "pccardctl ident" which should give a response like:

Quote:
Socket 0;
product info: "Sierra Wireless", "AC850", "3G Network Adapter", "R1"
manfid: 0x192, '''0x710'''
function: 6 (network)
However, I got "function: 2 (serial)" instead. I think the other stuff was the same but I'd need to try again to be sure. A colleague told me that this was OK, since the card is a serial device. Now I'm beginning to have doubts.

I will check the other advice you sent and maybe there will be something there that lets me figure out just what the problem is.

If you (or anybody else) have any further ideas, just let me know. I'll be sure to post a solution if I find one.

Achim
 
Old 05-05-2010, 05:22 PM   #6
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
I have farther ideas, of course.
If you have Firmware (Card Information Structure), and card (we hope) reads it so you can try to communicate to it.
Look it tells you:
[ 4670.280119] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
[ 4670.351045] 0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A

So it opens a serial on ttyS2. You can try to connect to it:
/usr/bin/screen /dev/ttyS2 9600

or on different speed: /usr/bin/screen /dev/ttyS2 115200

Then you can check if it actually works.
This page also can give you some help, it is old but, I do not think that was many changes.
http://www.pharscape.org/GlobeTrotterGPRShowto.html

More important part of it is:
Configuration of the pppd - ppp daemon, which connect you to provider.

Last edited by nimnull22; 05-05-2010 at 06:08 PM.
 
Old 05-06-2010, 04:06 PM   #7
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Hi again,

I tried "talking" to the card as you suggested:

Quote:
So it opens a serial on ttyS2. You can try to connect to it:
/usr/bin/screen /dev/ttyS2 9600

or on different speed: /usr/bin/screen /dev/ttyS2 115200
I used 115200 speed and got no response using /dev/ttys2 (actually I got an error which was gone too fast to read), however, when I tried it with /dev/umts (see the /etc/rules.d entry) I got a "conversation" going. I'm not all that good with the "AT" commands but I tried those in my chatscript.

First I typed "ATZ" (which was not echoed, so I couldn't see what I typed) and got the response "OK".

After that my commands were echoed on the screen, so I typed "ATE0V1" and again got "OK". When I then tried "AT OPSYS=1,2" I got the response "NO CARRIER". This is apparently what "status = 0x6" means.

I tried a number of times and got variously "NO CARRIER" or "ERROR". "ATZ" always worked and "AT" also got an "OK", though then the following commands were nolonger echoed and I couldn't see what I was typing. The results were, however, the same.

Finally I had the problem that I couldn't get out of that mode and back to the terminal. I ended up closing the screen, removing the card, and rebooting (apparently it was still running in the background, hence the reboot).

I'll have to see if I can get a handle on the commands in that mode. None the less, I figure the problem seems to lie in addressing the card as a UMTS/GPRS modem. I think that's what "AT OPSYS=1,2" does.

I will continue to consult the link you sent and all that other information in your earlier reply.

Thanks again for your time and effort. If you have any further ideas, I'd be happy to try them out.

Achim
 
Old 05-06-2010, 05:34 PM   #8
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
Important part starts from 2.1.2.1.
So, according to that manual, after you insert your card, you can do:
dmesg | tail -n 20
determine which ttyS pcmcia took.
then as said in manual check if you have: /var/lib/pcmcia/stab and what inside: more /var/lib/pcmcia/stab. If you do not have this file, do not worry.
Then: ls -la /dev/ttyS* - here you should see your ttyS and if it bounds to anything.
You probably should see something like it says that manual:
testlinux:~ # ls -l /dev/modem
lrwxrwxrwx 1 root root 10 Nov 13 15:07 /dev/modem -> /dev/ttyS1
testlinux:~ #
"->" means "soft link". You can find what ttyS was bounded with.
You can also check it like: ls -l /dev/umts.

Second you have to tell this to PPP daemon as it suggested in manual.


Hope it will help.

Also:
Appendix A: Usefull modem (AT) commands:

To find out the manufacturer, type ati and hit enter.
The at+cops? tells you to which provider (Proximus) you are hooked on and to what network type (last digit: 2 = UMTS, 0 = GPRS).
To find out the signal strength, type at+csq. The first value will be between 5 and 22. For reliable connections it should be at least 12. We have 5.
You can set the PIN manually with the command at+cpin="1234". Don't forget to replace "1234" with your PIN and don't send more that twice a wrong PIN to your 3G card or the SIM will be blocked. You can unblock the SIM with the command at+cpin="12345678","5678". Where "12345678" is your PUK and "5678" is the choozen new PIN.
To set your preferred network preferences, use the command at_opsys=3,2. This will set UMTS as the preferred network, 0,2 force to connect to a GPRS network only, 1,2 UMTS only and 2,2 preferred GPRS.
The command at&v gives a listing of all currently active settings. The command at+clac lists all available AT-commands.

Last edited by nimnull22; 05-07-2010 at 05:22 PM.
 
Old 05-10-2010, 03:16 PM   #9
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Hi,

Thanks for the reminder. I completely forgot about the "/var/lib/pcmcia/stab" information. I'll give it a go as well as "ls -l /dev/modem", though I suspect the latter won't provide too much information. The card doesn't seem to know that it's a modem. The command "ls -la /dev/ttys*" probably won't do much either, because the udev rule maps the device to /dev/umts. Still, I'll give it a go, because you never can tell where that final vital piece of information comes from! :-)

I couldn't read your response earlier, because I'm rather busy - "up to my eyeballs" as they say. My Weekends are fully taken up with house renovation and such. It's a bit late to be starting on this right now, since I have an early start tomorrow and today was a long day (Mondays are always hard for me - I've been up since 4:30 after 4 1/2 hours sleep). But maybe I can put in a couple of hours tomorrow evening after my "business dinner" appointment.

Please don't be too disappointed if I can't get back to you before the weekend. The advice you've given me has resulted in my learning more about this problem than in the previous 2 years!

I'll be in touch as soon as...

Achim
 
Old 05-11-2010, 05:09 PM   #10
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
OK, here's the latest:

When I tried "ls -la /dev/ttyS*" I got:
Quote:
root@achim-laptop:/home/achim# ls -la /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 2010-05-11 21:51 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2010-05-11 21:51 /dev/ttyS1
crw-rw---- 1 root dialout 4, 67 2010-05-11 21:51 /dev/ttyS3
root@achim-laptop:/home/achim#
The file /var/lib/pcmcia/stab does not exist. I suspected as much. In fact the directory /var/lib/pcmcia does not exist.

The command "dmesg | tail -n 20" produces:
Quote:
root@achim-laptop:/home/achim# dmesg | tail -n 20
[ 18.199992] type=1505 audit(1273607532.721:19): operation="profile_replace" pid=871 name=/usr/lib/cups/backend/cups-pdf
[ 18.200817] type=1505 audit(1273607532.725:20): operation="profile_replace" pid=871 name=/usr/sbin/cupsd
[ 18.203030] type=1505 audit(1273607532.725:21): operation="profile_replace" pid=872 name=/usr/sbin/tcpdump
[ 18.211827] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 18.460040] intel8x0_measure_ac97_clock: measured 55219 usecs (2660 samples)
[ 18.460044] intel8x0: clocking to 48000
[ 20.727135] psmouse serio2: ID: 10 00 64
[ 21.260246] [drm] Setting GART location based on new memory map
[ 21.262516] [drm] Loading R300 Microcode
[ 21.262558] [drm] Num pipes: 1
[ 21.262567] [drm] writeback test succeeded in 1 usecs
[ 24.703029] IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 24.989553] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio2/input/input9
[ 28.748023] eth1: no IPv6 routers present
[ 795.208086] pcmcia_socket pcmcia_socket0: pccard: PCMCIA card inserted into slot 0
[ 795.208100] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd0000000-0xd7ffffff: excluding 0xd0000000-0xd7ffffff
[ 795.208143] pcmcia_socket pcmcia_socket0: cs: memory probe 0xb4000000-0xbfffffff: excluding 0xb4000000-0xb47fffff 0xb8000000-0xbbffffff
[ 795.214081] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
[ 795.258108] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
[ 795.326704] 0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
root@achim-laptop:/home/achim#
The command "ls -l /dev/modem" gave a response of "No such file or directory", which I also expected.

I then tried "ls -la /dev/um*" and got:
Quote:
root@achim-laptop:/lib/udev/rules.d# ls -la /dev/um*
crw-rw---- 1 root dialout 4, 66 2010-05-11 22:05 /dev/umts
After checking the man page and re-reading my udev/rules.d/99-aircard.rules, I tried
Quote:
root@achim-laptop:/etc/udev/rules.d# ls -l /dev/tts
total 0
lrwxrwxrwx 1 root root 7 2010-05-11 22:31 umts -> ../umts
which is also pretty much as expected.

To be totally obtuse about the whole thing, I tried "pon eplus" again and got the following out of /var/log/syslog:
Quote:
May 11 22:53:23 achim-laptop pppd[2249]: pppd 2.4.5 started by achim, uid 0
May 11 22:53:24 achim-laptop chat[2252]: timeout set to 240 seconds
May 11 22:53:24 achim-laptop chat[2252]: abort on (NO CARRIER)
May 11 22:53:24 achim-laptop chat[2252]: abort on (NO DIALTONE)
May 11 22:53:24 achim-laptop chat[2252]: abort on (ERROR)
May 11 22:53:24 achim-laptop chat[2252]: abort on (NO ANSWER)
May 11 22:53:24 achim-laptop chat[2252]: abort on (BUSY)
May 11 22:53:24 achim-laptop chat[2252]: send (ATZ^M)
May 11 22:53:24 achim-laptop chat[2252]: expect (OK)
May 11 22:53:24 achim-laptop chat[2252]: ATZ^M^M
May 11 22:53:24 achim-laptop chat[2252]: OK
May 11 22:53:24 achim-laptop chat[2252]: -- got it
May 11 22:53:24 achim-laptop chat[2252]: send (ATE0V1^M)
May 11 22:53:25 achim-laptop chat[2252]: expect (OK)
May 11 22:53:25 achim-laptop chat[2252]: ^M
May 11 22:53:25 achim-laptop chat[2252]: ATE0V1^M^M
May 11 22:53:25 achim-laptop chat[2252]: OK
May 11 22:53:25 achim-laptop chat[2252]: -- got it
May 11 22:53:25 achim-laptop chat[2252]: send (AT_OPSYS=1,2^M)
May 11 22:53:25 achim-laptop chat[2252]: expect (OK)
May 11 22:53:25 achim-laptop chat[2252]: ^M
May 11 22:53:25 achim-laptop chat[2252]: ^M
May 11 22:53:25 achim-laptop chat[2252]: ERROR
May 11 22:53:25 achim-laptop chat[2252]: -- failed
May 11 22:53:25 achim-laptop chat[2252]: Failed (ERROR)
May 11 22:53:25 achim-laptop pppd[2249]: Script /usr/sbin/chat -v -f /etc/chatscripts/eplus finished (pid 2251), status = 0x6
May 11 22:53:25 achim-laptop pppd[2249]: Connect script failed
May 11 22:53:26 achim-laptop pppd[2249]: Exit.
As I see it, there is some logical connection between the card and the OS that fails to identify the card as a wireless modem. I could try different combinations in the "AT_OPSYS=1,2" command, I suppose. Something like "AT_OPSYS=0,2", which I haven't tried before. However, random changes aren't really the way to go in my experience.

I'm going to read up on the AT command set but I think the problem lies somewhere else. Probably there needs to be something in the /etc/ppp/peers/eplus script (see my first entry) to let the system know that it's talking to a wireless modem. Either that or there is some obscure configuration setting missing.

Any further ideas are more than welcome.

Achim

P.S. I had a closer look at the response from "ls -la /dev/um*" and noticed that the device is listed as a "dialout" device. Now that would suggest that the device it recognised as a modem (at least on some level). I'm more confused that ever!

Last edited by achim_59; 05-11-2010 at 05:27 PM.
 
Old 05-11-2010, 06:13 PM   #11
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
Forget about "dialout" it is just group name.

The biggest problem, I personally think, is that your PCMCIA does not open ttyS2 for communication.
Even log file has:
pcmcia 0.0: pcmcia: registering new device pcmcia0.0
pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
It looks like card doesn't initialize the serial port. You can use another utility to check this:
setserial -g /dev/ttyS*
It should show you all available serial port. If you wont see ttyS2 that probably can mean that card did something wrong or it does not read SW_8xx_SER.cis at all.

Also please, after reboot WITHOUT card inserted, check: setserial -g /dev/ttyS*, may be something wrong with ttyS2.
Without serial port you wont be able to do anything.
 
Old 05-18-2010, 04:43 PM   #12
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Hi again,

The setserial program is not installed on my machine. I will have to wait until the weekend again to install it.

As for /dev/ttyS2, in the dmesg response from my previous post the following lines were output at the end.

Quote:
[ 795.214081] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
[ 795.258108] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
[ 795.326704] 0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
I tried listing the ttyS* devices without the card and got

Quote:
achim@achim-laptop:~$ ls -la /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 2010-05-18 22:29 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2010-05-18 22:29 /dev/ttyS1
crw-rw---- 1 root dialout 4, 66 2010-05-18 22:29 /dev/ttyS2
crw-rw---- 1 root dialout 4, 67 2010-05-18 22:29 /dev/ttyS3
Then I inserted the card and tried looking at /var/log/syslog. This was the result just the last few lines):

Quote:
May 18 23:05:49 achim-laptop kernel: [ 2198.526283] pcmcia 0.0: pcmcia: registering new device pcmcia0.0
May 18 23:05:50 achim-laptop kernel: [ 2198.913275] pcmcia 0.0: firmware: requesting SW_8xx_SER.cis
May 18 23:05:50 achim-laptop kernel: [ 2199.026084] 0.0: ttyS2 at I/O 0x3e8 (irq = 4) is a 16550A
May 18 23:05:50 achim-laptop modem-manager: (ttyS2) opening serial device...
Then I tried listing the /dev/ttyS* devices again. The result is interesting:

Quote:
achim@achim-laptop:~$ ls -la /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 2010-05-18 22:29 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 2010-05-18 22:29 /dev/ttyS1
crw-rw---- 1 root dialout 4, 67 2010-05-18 22:29 /dev/ttyS3
So what happend to ttyS2? You seem to be onto something here but I confess I'm baffled. Is it a conflict of some sort or is the /dev/ttyS2 being masked by /dev/umts (see earlier post)? Any ideas would be very welcome.
 
Old 05-19-2010, 05:28 PM   #13
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
Please do me a favor. I do not know answer to your question and I do not really like anything made by ubuntu team.

So, please, check if you have on your distribution: udevadm. For it, type on normal user console: man udevadm.
If you will get man page, you have the package.

So, if you have that "udevadm" please reboot, then on root console type:
udevadm monitor --environment

And then insert your pcmcia card, wait a some time, and remove it.
You will get a long output in root console, please save it, and post it here through "http://pastebin.com/" service.

Thanks.
 
Old 05-25-2010, 04:07 PM   #14
achim_59
Member
 
Registered: Jan 2009
Location: Huenfeld, Germany
Distribution: Ubuntu 18.04
Posts: 113

Original Poster
Rep: Reputation: 4
Hi once more,

I did as you asked and posted the "udevadm" reply at the specified address. I gave it an expiry of 1 month... not too short, I hope. The link is: http://pastebin.com/qmqH28hX

Before trying that I also used the setserial command as you suggested. The response was pretty much what I expected (and you probably, too). First without the aircard:
Quote:
achim@achim-laptop:~$ setserial -g /dev/ttyS*
/dev/ttyS0, UART: undefined, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
/dev/ttyS2, UART: unknown, Port: 0x03e8, IRQ: 4
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
I then inserted the card and got:
Quote:
achim@achim-laptop:~$ setserial -g /dev/ttyS*
/dev/ttyS0, UART: undefined, Port: 0x03f8, IRQ: 4
/dev/ttyS1, UART: unknown, Port: 0x02f8, IRQ: 3
/dev/ttyS3, UART: unknown, Port: 0x02e8, IRQ: 3
achim@achim-laptop:~$ setserial -g /dev/um*
/dev/umts, UART: 16550A, Port: 0x03e8, IRQ: 4
achim@achim-laptop:~$
I hope this iformation helps. There is one thing I'm going to try myself, but it will have to wait until tomorrow. It's late and I only got 3 hours sleep last night!

Thanks again for all your effort. 'Bye for now...

Achim
 
Old 05-25-2010, 10:56 PM   #15
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
Ok, I did rearrange in your output a little bit. So it became more readable. More important part of it:
KERNEL[1274819100.661177] add /devices/pci0000:00/0000:00:1e.0/0000:0b:00.0/0.0/tty/ttyS2 (tty)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:0b:00.0/0.0/tty/ttyS2
SUBSYSTEM=tty
DEVNAME=ttyS2
SEQNUM=1537

UDEV [1274819100.688108] add /devices/pci0000:00/0000:00:1e.0/0000:0b:00.0/0.0/tty/ttyS2 (tty)
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:0b:00.0/0.0/tty/ttyS2
SUBSYSTEM=tty
DEVNAME=/dev/umts
SEQNUM=1537
DEVLINKS=/dev/tts/umts

This is mean that kernel and UDEV mapped your device to "/dev/umts". And you can try to connect to it like I suggested before:
/usr/bin/screen /dev/umts 9600.

Next, from your first post about /etc/chatscripts/eplus, type like in it.
"" "+++atz"
OK "ATE0V1"
OK "AT_OPSYS=3,2"
OK AT+CGDCONT=1,"IP","internet.eplus.de","",0,0
OK "ATD*99***1#"

Try, tell please what you will get.

Also please, according to my "man pppd" there should be:
/etc/ppp/options - System default options for pppd, read before user default options or command-line options.

~/.ppprc - User default options, read before /etc/ppp/options.ttyname.

/etc/ppp/options.ttyname - System default options for the serial port being used, read after ~/.ppprc. In
forming the ttyname part of this filename, an initial /dev/ is stripped from the
port name (if present), and any slashes in the remaining part are converted to
dots.

Check all of those, pppd daemon should be pointed to "ttyname"=umts


Unfortunately in your output also presents the follow statement:
KERNEL[1274819163.932770] add /devices/platform/serial8250/tty/ttyS2 (tty)
ACTION=add
DEVPATH=/devices/platform/serial8250/tty/ttyS2
SUBSYSTEM=tty
DEVNAME=ttyS2
SEQNUM=1540

UDEV [1274819163.932653] add /devices/platform/serial8250/tty/ttyS2 (tty)
ACTION=add
DEVPATH=/devices/platform/serial8250/tty/ttyS2
SUBSYSTEM=tty
DEVNAME=/dev/ttyS2
SEQNUM=1540
DEVLINKS=/dev/char/4:66

But I have completely no idea why you do not have it.
May be it is time to fill a BUD to Ubuntu, or may be some one can explain, I do not have a lot of experience with it.
Or may be /dev/umts will be enough.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
upgrading from Ubuntu 9.10 Karmic Koala 32-bit to Ubuntu 9.10 Karmic Koala 64-bit aryan1 Ubuntu 1 01-21-2010 04:20 AM
LXer: Ubuntu 9.10 Karmic Koala LXer Syndicated Linux News 0 12-07-2009 07:30 PM
LXer: The Perfect Server - Ubuntu Karmic Koala (Ubuntu 9.10) [ISPConfig 2] LXer Syndicated Linux News 0 11-08-2009 10:00 AM
LXer: Upgrade Ubuntu 9.04 (Jaunty Jackalope) to Ubuntu 9.10 (Karmic Koala) Beta LXer Syndicated Linux News 0 10-12-2009 07:50 AM
LXer: Install The Proposed Comunity Themes For Ubuntu Karmic Koala, In Ubuntu Jaunty LXer Syndicated Linux News 0 09-17-2009 02:20 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 11:41 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration