Nokia CS-17 mobile broadband doesn't work anymore

Bug #1071014 reported by Jussi Lind
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Low
Unassigned

Bug Description

What should happen is that when one plugs in the Nokia CS-17 USB mobile broadband the modem should be detected and the user should be able to configure the mobile broadband connection.

What happens instead is absolutely nothing.

WORKAROUND: Set DisableSwitching=1 in /etc/usb_modeswitch.conf
eject /dev/sr1

Kernel log when the device is connected:
[381116.274532] usb 1-1.1: new high-speed USB device number 7 using ehci_hcd
[381116.368757] scsi8 : usb-storage 1-1.1:1.0
[381117.365941] scsi 8:0:0:0: CD-ROM Nokia Datacard CD-ROM 0001 PQ: 0 ANSI: 0
[381117.368396] sr1: scsi3-mmc drive: 0x/0x caddy
[381117.368906] sr 8:0:0:0: Attached scsi CD-ROM sr1
[381117.369211] sr 8:0:0:0: Attached scsi generic sg3 type 5
[381117.449772] sr1: CDROM (ioctl) error, command: Get event status notification 4a 01 00 00 10 00 00 00 08 00
[381117.449799] sr: Sense Key : Hardware Error [current]
[381117.449807] sr: Add. Sense: No additional sense information
[381117.553411] sr1: CDROM (ioctl) error, command: Get event status notification 4a 01 00 00 10 00 00 00 08 00
[381117.553446] sr: Sense Key : Hardware Error [current]
[381117.553457] sr: Add. Sense: No additional sense information

Output of sudo usb-devices:

T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 6 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=0421 ProdID=0622 Rev=00.01
S: Manufacturer=Nokia
S: Product=Nokia Datacard
S: SerialNumber=4CC03614CA2E62E7498AB72726150A37EB8BB978
C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=(none)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: usb-modeswitch 1.2.3+repack0-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu14
Architecture: amd64
Date: Wed Oct 24 23:25:16 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: usb-modeswitch
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: jussil 10080 F.... pulseaudio
 /dev/snd/controlC1: jussil 10080 F.... pulseaudio
 /dev/snd/controlC0: jussil 10080 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=298e5f46-7d22-4a06-816c-cadf70fc84ca
InstallationDate: Installed on 2013-10-20 (7 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: System manufacturer P5QL PRO
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=3994646e-c97d-4297-827b-08d422953a14 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
RfKill:

Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 07/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1004
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5QL PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd07/01/2009:svnSystemmanufacturer:pnP5QLPRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QLPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5QL PRO
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Jussi Lind (jussi-lind) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in usb-modeswitch (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Jussi Lind, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

affects: usb-modeswitch (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
penalvch (penalvch)
tags: added: needs-kernel-logs needs-upstream-testing regression-potential
Revision history for this message
Jussi Lind (jussi-lind) wrote :

I now tested with up-to-date 13.10 and the problem persists:

[ 4188.004314] usb 2-1.1: new high-speed USB device number 10 using ehci-pci
[ 4188.096938] usb 2-1.1: New USB device found, idVendor=0421, idProduct=0622
[ 4188.096943] usb 2-1.1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[ 4188.096946] usb 2-1.1: Product: Nokia Datacard
[ 4188.096949] usb 2-1.1: Manufacturer: Nokia
[ 4188.096953] usb 2-1.1: SerialNumber: 4CC03614CA2E62E7498AB72726150A37EB8BB978
[ 4188.097245] usb-storage 2-1.1:1.0: USB Mass Storage device detected
[ 4188.097582] scsi7 : usb-storage 2-1.1:1.0
[ 4189.096717] scsi 7:0:0:0: CD-ROM Nokia Datacard CD-ROM 0001 PQ: 0 ANSI: 0
[ 4189.098457] sr1: scsi3-mmc drive: 0x/0x caddy
[ 4189.098773] sr 7:0:0:0: Attached scsi CD-ROM sr1
[ 4189.099376] sr 7:0:0:0: Attached scsi generic sg7 type 5
[ 4189.184952] sr1: CDROM (ioctl) error, command: Get event status notification 4a 01 00 00 10 00 00 00 08 00
[ 4189.184969] sr: Sense Key : Hardware Error [current]
[ 4189.184973] sr: Add. Sense: No additional sense information
[ 4189.289079] sr1: CDROM (ioctl) error, command: Get event status notification 4a 01 00 00 10 00 00 00 08 00
[ 4189.289091] sr: Sense Key : Hardware Error [current]
[ 4189.289094] sr: Add. Sense: No additional sense information
[ 4190.312957] sr1: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
[ 4190.312973] sr: Sense Key : Hardware Error [current]
[ 4190.312977] sr: Add. Sense: No additional sense information

I'll try with the upstream kernel next.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
penalvch (penalvch) wrote :

Jussi Lind, if the issue remains in Saucy, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: saucy
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Expired → Incomplete
Revision history for this message
Jussi Lind (jussi-lind) wrote :

My 13.10 got trashed so I'll try to test this once I get my system up and running again.

Revision history for this message
Jussi Lind (jussi-lind) wrote :

Hmm...this is weird. The CS-17 now works, but not immediately when I plug it in. It was finally detected and the led was on after *several* hours without me doing anything.

This happens when I plug the device in:

[397538.092282] usb 2-1.1: new high-speed USB device number 9 using ehci-pci
[397538.184903] usb 2-1.1: New USB device found, idVendor=0421, idProduct=0622
[397538.184908] usb 2-1.1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[397538.184912] usb 2-1.1: Product: Nokia Datacard
[397538.184915] usb 2-1.1: Manufacturer: Nokia
[397538.184919] usb 2-1.1: SerialNumber: 4CC03614CA2E62E7498AB72726150A37EB8BB978
[397539.813928] usb-storage 2-1.1:1.0: USB Mass Storage device detected
[397539.814596] scsi6 : usb-storage 2-1.1:1.0
[397539.814689] usbcore: registered new interface driver usb-storage
[397540.812549] scsi 6:0:0:0: CD-ROM Nokia Datacard CD-ROM 0001 PQ: 0 ANSI: 0
[397540.814991] sr1: scsi3-mmc drive: 0x/0x caddy
[397540.815119] sr 6:0:0:0: Attached scsi CD-ROM sr1
[397540.815181] sr 6:0:0:0: Attached scsi generic sg3 type 5
[397541.345038] sr1: CDROM (ioctl) error, command: Get event status notification 4a 01 00 00 10 00 00 00 08 00
[397541.345054] sr: Sense Key : Hardware Error [current]
[397541.345058] sr: Add. Sense: No additional sense information
[397541.437040] sr1: CDROM (ioctl) error, command: Xpwrite, Read disk info 51 00 00 00 00 00 00 00 02 00
[397541.437057] sr: Sense Key : Hardware Error [current]
[397541.437061] sr: Add. Sense: No additional sense information

Much later there was:

[401326.565754] usb 2-1.1: USB disconnect, device number 9
[401330.736267] usb 2-1.1: new high-speed USB device number 10 using ehci-pci
[401330.830006] usb 2-1.1: New USB device found, idVendor=0421, idProduct=0623
[401330.830013] usb 2-1.1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[401330.830015] usb 2-1.1: Product: Nokia Datacard
[401330.830017] usb 2-1.1: Manufacturer: Nokia
[401330.830019] usb 2-1.1: SerialNumber: 4CC03614CA2E62E7498AB72726150A37EB8BB978
[401331.010103] cdc_acm 2-1.1:1.1: ttyACM0: USB ACM device
[401331.010722] cdc_acm 2-1.1:1.3: ttyACM1: USB ACM device
[401331.012854] usbcore: registered new interface driver cdc_acm
[401331.012857] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters

Revision history for this message
Jussi Lind (jussi-lind) wrote :

This behavior was with current 13.10.

tags: added: apport-collected
description: updated
Revision history for this message
Jussi Lind (jussi-lind) wrote : AlsaInfo.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : BootDmesg.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : CRDA.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : IwConfig.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : Lspci.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : Lsusb.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : ProcEnviron.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : ProcModules.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : UdevDb.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : UdevLog.txt

apport information

Revision history for this message
Jussi Lind (jussi-lind) wrote : WifiSyslog.txt

apport information

Revision history for this message
penalvch (penalvch) wrote :

Jussi Lind, as per http://www.asus.com/Motherboards/P5QL_PRO/#support an update is available for your BIOS (1004). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

tags: added: bios-outdated-1004
Revision history for this message
Jussi Lind (jussi-lind) wrote :

I think BIOS cannot be the root cause, because CS-17 has worked on this same machine before 12.04.

However, this seems to be a USB modeswitch problem/conflict. I'm now able to make the device work like this:

1) Set DisableSwitching=1 in /etc/usb_modeswitch.conf
2) $ eject /dev/sr1

For some reason ejecting the device makes it recognized and I can configure Mobile Broadband via the network menu.

In the kernel log there's now:

[506024.529864] usb 2-1.1: USB disconnect, device number 26
[506028.624240] usb 2-1.1: new high-speed USB device number 27 using ehci-pci
[506028.716868] usb 2-1.1: New USB device found, idVendor=0421, idProduct=0623
[506028.716874] usb 2-1.1: New USB device strings: Mfr=2, Product=1, SerialNumber=3
[506028.716878] usb 2-1.1: Product: Nokia Datacard
[506028.716881] usb 2-1.1: Manufacturer: Nokia
[506028.716884] usb 2-1.1: SerialNumber: 4CC03614CA2E62E7498AB72726150A37EB8BB978
[506028.717682] cdc_acm 2-1.1:1.1: ttyACM0: USB ACM device
[506028.718259] cdc_acm 2-1.1:1.3: ttyACM1: USB ACM device

penalvch (penalvch)
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.