[SOLVED] Nokia CS-15 not functioning under Ubuntu 12.04

achim_59 · 01-13-2014, 01:41 PM

Hi All,

I used to have this dongle working and used it for 2 years. Then somebody stole my laptop along with the CS-15 and a heap of other stuff. I now have a new Ultrabook (Tuxedo with intel i5 processor, 16GB RAM, 250 GB SSD Hard Drive). I Installed Ubuntu 12.04 LTS again, because it struck me a pretty reliable.

I originally tried using a new UMTS dongle but that didn't work (at least not yet). So I paid a horrendous price for another Nokia CS-15. They are supposedly Linux-friendly. I've saved the relevant information from /var/log/syslog and from lsusb.

Firstly lsusb:

Code:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 002 Device 008: ID 0421:0610 Nokia Mobile Phones CS-15 (Internet Stick 3G modem)
Bus 002 Device 003: ID 062a:0000 Creative Labs Optical mouse

Tat seemed promising, so I was disturbed that there was no indication on the device itself, that anything had happened. So I checked in /var/log/syslog:

Code:

Jan 13 05:48:55 achim-W840SU-Series kernel: [  720.135652] usb 2-1: new high-speed USB device number 5 using xhci_hcd
Jan 13 05:48:55 achim-W840SU-Series kernel: [  720.153340] scsi5 : usb-storage 2-1:1.0
Jan 13 05:48:55 achim-W840SU-Series mtp-probe: checking bus 2, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Jan 13 05:48:55 achim-W840SU-Series mtp-probe: bus: 2, device: 5 was not an MTP device
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.151876] scsi 5:0:0:0: CD-ROM            Nokia    Datacard CD-ROM  0001 PQ: 0 ANSI: 0
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.154384] sr0: scsi3-mmc drive: 0x/0x caddy
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.154755] sr 5:0:0:0: Attached scsi CD-ROM sr0
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.155341] sr 5:0:0:0: Attached scsi generic sg1 type 5
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.211480] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.211494] sr: Sense Key : Hardware Error [current] 
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.211499] sr: Add. Sense: No additional sense information
Jan 13 05:48:56 achim-W840SU-Series usb_modeswitch: switching device 0421:0610 on 002/005
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.383449] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.383476] sr: Sense Key : Hardware Error [current] 
Jan 13 05:48:56 achim-W840SU-Series kernel: [  721.383484] sr: Add. Sense: No additional sense information

The usb_modeswitch had been attempted, but obviously failed.

I next tried to get some stuff from some old backups and found the file /etc/udev/rules.d/25-mokulat.rules. It looks like this:

Code:

# udev-rules for switching modems from storage mode to modem mode - anttu - v.091216

# a-link 3gu turbo
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="1e0e", SYSFS{idProduct}=="f000", ACTION=="add", RUN+="/usr/bin/eject -s %N", OPTIONS+="last_rule"
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="1e0e", SYSFS{idProduct}=="9200", ACTION=="add", RUN+="/sbin/modprobe -r option", RUN+="/sbin/modprobe -r usbserial", RUN+="/sbin/modprobe usbserial vendor=0x1e0e product=0x9200", RUN+="/sbin/modprobe option", OPTIONS+="last_rule"

# nokia cs-15
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="0421", SYSFS{idProduct}=="0610", ACTION=="add", RUN+="/usr/bin/eject -s %N", OPTIONS+="last_rule"

# huawei e1762
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="12d1", SYSFS{idProduct}=="1446", ACTION=="add", RUN+="/usr/sbin/usb_modeswitch -v 0x12d1 -p 0x1446 -V 0x12d1 -P 0x1003 -m 0x01 -M '55534243123456780000000000000011060000000000000000000000000000'", OPTIONS+="last_rule"

# siptune lm-75
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="05c6", SYSFS{idProduct}=="f000", ACTION=="add", RUN+="/usr/bin/eject -s %N", OPTIONS+="last_rule"
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="05c6", SYSFS{idProduct}=="9000", ACTION=="add", RUN+="/sbin/modprobe -r option", RUN+="/sbin/modprobe -r usbserial", RUN+="/sbin/modprobe usbserial vendor=0x05c6 product=0x9000", RUN+="/sbin/modprobe option", OPTIONS+="last_rule"

# zte mf-636+
BUS=="usb", SUBSYSTEM=="block", SYSFS{idVendor}=="19d2", SYSFS{idProduct}=="2000", ACTION=="add", RUN+="/usr/bin/eject -s %N", OPTIONS+="last_rule"

I copied that onto my new machine and got the following error messages in /var/log/syslog:

Code:

-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:4
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:4'
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:5
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:5'
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:8
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:8'
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:11
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:11'
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:14
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:14'
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:15
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:15'
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: unknown key 'BUS' in /etc/udev/rules.d/25-mokkulat.rules:18
Jan 13 06:13:41 achim-W840SU-Series udevd[365]: invalid rule '/etc/udev/rules.d/25-mokkulat.rules:18'

However, the messages relating to the CS-15 had now changed:

Code:

-W840SU-Series kernel: [   24.015312] usb 2-5: Device not responding to set address.
Jan 13 06:15:45 achim-W840SU-Series usb_modeswitch: switching device 0421:0610 on 002/002
Jan 13 06:15:45 achim-W840SU-Series kernel: [   24.219022] usb 2-5: device not accepting address 7, error -71
Jan 13 06:15:45 achim-W840SU-Series kernel: [   24.219063] hub 2-0:1.0: unable to enumerate USB device on port 5
Jan 13 06:15:45 achim-W840SU-Series kernel: [   24.243595] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
Jan 13 06:15:45 achim-W840SU-Series kernel: [   24.243620] sr: Sense Key : Hardware Error [current] 
Jan 13 06:15:45 achim-W840SU-Series kernel: [   24.243628] sr: Add. Sense: No additional sense information

In the past on my trusty T43 (the stolen laptop) I sometimes had to insert the CS15 more than once, so I gave that a go. The result in /var/log/syslog:

Code:

-W840SU-Series kernel: [  499.796830] usb 2-1: USB disconnect, device number 2
Jan 13 06:23:46 achim-W840SU-Series kernel: [  505.339486] usb 2-1: new high-speed USB device number 8 using xhci_hcd
Jan 13 06:23:46 achim-W840SU-Series kernel: [  505.357220] scsi5 : usb-storage 2-1:1.0
Jan 13 06:23:46 achim-W840SU-Series mtp-probe: checking bus 2, device 8: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Jan 13 06:23:46 achim-W840SU-Series mtp-probe: bus: 2, device: 8 was not an MTP device
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.355724] scsi 5:0:0:0: CD-ROM            Nokia    Datacard CD-ROM  0001 PQ: 0 ANSI: 0
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.357565] sr0: scsi3-mmc drive: 0x/0x caddy
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.357915] sr 5:0:0:0: Attached scsi CD-ROM sr0
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.358480] sr 5:0:0:0: Attached scsi generic sg1 type 5
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.403391] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.403416] sr: Sense Key : Hardware Error [current] 
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.403424] sr: Add. Sense: No additional sense information
Jan 13 06:23:47 achim-W840SU-Series usb_modeswitch: switching device 0421:0610 on 002/008
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.523362] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.523387] sr: Sense Key : Hardware Error [current] 
Jan 13 06:23:47 achim-W840SU-Series kernel: [  506.523395] sr: Add. Sense: No additional sense information

A reboot and a further attempt yielded the following error in /var/log/syslog:

Code:

-W840SU-Series kernel: [  589.732701] usb 2-1: USB disconnect, device number 8
Jan 13 06:25:14 achim-W840SU-Series kernel: [  593.166638] usb 2-1: new high-speed USB device number 9 using xhci_hcd
Jan 13 06:25:14 achim-W840SU-Series kernel: [  593.184318] scsi6 : usb-storage 2-1:1.0
Jan 13 06:25:14 achim-W840SU-Series mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
Jan 13 06:25:14 achim-W840SU-Series mtp-probe: bus: 2, device: 9 was not an MTP device
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.182810] scsi 6:0:0:0: CD-ROM            Nokia    Datacard CD-ROM  0001 PQ: 0 ANSI: 0
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.185071] sr0: scsi3-mmc drive: 0x/0x caddy
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.185464] sr 6:0:0:0: Attached scsi CD-ROM sr0
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.185679] sr 6:0:0:0: Attached scsi generic sg1 type 5
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.254574] sr0: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.254599] sr: Sense Key : Hardware Error [current] 
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.254608] sr: Add. Sense: No additional sense information
Jan 13 06:25:15 achim-W840SU-Series usb_modeswitch: switching device 0421:0610 on 002/009
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.313911] scsi 6:0:0:0: rejecting I/O to offline device
Jan 13 06:25:15 achim-W840SU-Series kernel: [  594.313924] scsi 6:0:0:0: killing request

One last thing I recall from 2 and a bit years ago ist htat there was some mention of an incorrect device ID. I even saved the page and this is what it says:

Quote:

When you run lsusb you should see something like this:
Bus 001 Device 004: ID 0421:0610 Nokia Mobile Phones

Now you have to run usb_modeswitch command with these parameters:
usb_modeswitch -v 0x0421 -p 0x0610 -m 0x01 -M "5553424312345678000000000000061b000000020000000000000000000000"

This will change that 0610 to 0612 and after that command we can run lsusb again and see if that worked and you should see
something like this:
Bus 001 Device 005: ID 0421:0612 Nokia Mobile Phones

I haven't yet had any success with the usb_modeswitch command and I don't think I should have to run it every time. I cannot remember what exactly happened last time. Somehow I just fiddled with scripts for a few months and eventually it worked. I don't want to have to do that again.

Questions:

Is the device perhaps defective? That seems to be the gist of most of those log messages.

Is the device number wrong and is that causing all the trouble?

Are there any other diagnostics I can run to find out what is happening?

Unfortunately I don't have any private internet access apart from weekends when I'm at home. I'm doing this after hours at work, so I cannot respond promptly to any replies. However, I would be grateful for some help.

Thanks in advance.

Achim

achim_59 · 01-14-2014, 12:31 PM

I have not been idle, I tried the usb_modeswitch command.

Code:

root@achim-W840SU-Series:/home/achim# usb_modeswitch -v 0x0421 -p 0x0610 -m 0x01 -M "5553424312345678000000000000061b000000020000000000000000000000"

The result was not especially encouraging. Here's what I got:

Quote:

Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 003 on bus 002 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached

When I ran lsusb there was basically no change to what I had seen before:

Quote:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 002: ID 8087:07dc Intel Corp.
Bus 002 Device 003: ID 0421:0610 Nokia Mobile Phones CS-15 (Internet Stick 3G modem)
Bus 002 Device 004: ID 062a:0000 Creative Labs Optical mouse

If the device is defective, I need to find out quickly. I've got about 2 days left to send it back. After that I'm sitting on an expensive bit of junk.

Help please... I have no idea what to try next.

Additional information
The device appears not to be broken. I put it into a windows machine and the installation went as planned. I was subsequently able to get an internett connection over the CS-15. I'll have to delete the software from this machine, of course... it's a gross abuse of employer equipment. Still, it does suggest that the problem is with the linux installation.

16.01.2014 Yet more info

I went back to the man page to see what I might have done wrong with the usb_modeswitch command. I then cobbled together a new version. Here is the result:

Code:

achim@achim-W840SU-Series:~$ usb_modeswitch -v 0x0421 -p 0x0610 -P 0x0612 -M "5553424312345678000000000000061b000000020000000000000000000000"

Looking for default devices ...
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Accessing device 000 on bus 002 ...
Getting the current device configuration ...
Error getting the current configuration (error -1). Assuming configuration 1.
Using first interface: 0x00
Using endpoints 0x01 (out) and 0x81 (in)
Inquiring device details; driver will be detached ...
Looking for active driver ...
No driver found. Either detached before or never attached
Could not claim interface (error -1). Skipping device inquiry
Error: could not get description string "manufacturer"
Error: could not get description string "product"
Error: could not get description string "serial number"

USB description data (for identification)
-------------------------
Manufacturer:
Product:
Serial No.:
-------------------------
Looking for active driver ...
No driver found. Either detached before or never attached
Setting up communication with interface 0
Could not claim interface (error -1). Skipping message sending
-> Run lsusb to note any changes. Bye.

achim@achim-W840SU-Series:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 002: ID 8087:07dc Intel Corp.
Bus 002 Device 003: ID 062a:0000 Creative Labs Optical mouse
Bus 002 Device 005: ID 0421:0610 Nokia Mobile Phones CS-15 (Internet Stick 3G modem)

achim_59 · 01-22-2014, 01:48 PM

There hasn't been much response on this thread, but I have had a bit of support from this other forum. I have attempted to be as clear and concise as possible and there have been very clear advances in how to diagnose this type of problem. A solution is not yet available but I expect to get there soon.

It deals with a TP Link MA260, but I also delve into issues with the Nokia CS-15.

Amongst other things, there is a link to a checklist. If you know a bit about these things, this is quite useful, but be warned it is essentially a list of all manner of things that can go wrong without regard for which phase of the attempt you're in... e.g. it is pointless looking at dial up script errors when your dongle is not being recognised.

I will be closing this thread as soon as I get an answer... watch this space, people.

achim_59 · 02-18-2014, 08:23 AM

There is now a work-around for the non-functioning dongle problem I've described how I got there in that other forum. In brief, you can try doing the following:

1. Insert the dongle.
2. Open the disk utility (I use Ubuntu 12.04, but there should be an equivalent application with most distros). In Ubuntu select System > Control Center > Disk Utility.
3. Find the "CD Drive" representing your dongle.
4. Click "Eject".

You can follow the action by opening a console and typing "tail -f /var/log/syslog". If things work out correctly, you should see that a device like "ttyUSB0", "ttyACM0" or something along those lines is registered. If such is the case, I'd suggest trying a wvdial script (regardless of what errors are listed in /var/log/syslog). If it works, then this is your work-around.

I'll be experimenting with some other commands and list the results in the forum mentioned above.