I am currently using an ubuntu Linux, using the newest stable release from kernel.org as driver.
Linux daniel-lap 2.6.30-020630-generic #020630 SMP Wed Jun 10 09:04:38 UTC 2009 x86_64 GNU/Linux
In a previous version of the kernel (2.6.28-11 and 2.6.28-12) my WWAN mobile broadband was detected correctly and could be used.
Modules loaded for that where:
Now none of these modules is loaded by default, so no device (usually /dev/ttyACMx) can be found. Manually loading via modprobe doesn't help.
Tell me, what additional information is needed.
"I am currently using an ubuntu Linux, using the newest stable release from
kernel.org as driver."
Sorry, of course i mean that i am using the newest release as kernel...
Daniel: which WWAN modem are you using? (make, model, etc).
Please attach output of lsusb and lspci.
i added the output of lspci and lsusb from the new kernel.
Here, the device doesn't show up.
Tomorrow, i will ran lsusb (here the device is normaly shown) on the "old" kernel and post it.
i can't exactly tell you, which modem i am using.
the laptop (a thinkpad t500) has an integrated mobile modem.
i think it is some kind of ericsson f3507g. at least, i kept using the AT commands for an f3507g to control the device.
Created attachment 21948 [details]
output of lspci on newer kernel
Created attachment 21949 [details]
output of lsusb on newer kernel
Experienced the same on my system when I moved from 2.27.11 to 2.28.11. Same also under 2.28.13.
The following might help debug the problem:
dmesg shows that in fact the card is detected during boot, the proper modules -cdc_acm and cdc_wdm- load and create the appropriate comm ports, but after a while the usb port is disconnected and ehci_hcd appears unhappy.
I have noted that in kernel 2.27.11 in my distribution (Ubuntu) the ehci_hcd was built as a module, whereas from 2.28.11 on it was built into the kernel.
[ 3.920054] usb 2-4: new high speed USB device using ehci_hcd and address 2
[ 4.768172] usb 2-4: configuration #1 chosen from 2 choices
[ 4.816828] cdc_acm 2-4:1.1: ttyACM0: USB ACM device
[ 4.817162] cdc_wdm 2-4:1.5: cdc-wdm0: USB WDM device
[ 4.821853] usb0: register 'cdc_ether' at usb-0000:00:1d.7-4, CDC Ethernet Device, 02:80:37:ec:02:00
[ 4.821869] usbcore: registered new interface driver cdc_ether
[ 4.822052] cdc_acm 2-4:1.3: ttyACM1: USB ACM device
[ 4.822520] cdc_wdm 2-4:1.6: cdc-wdm1: USB WDM device
[ 4.822532] usbcore: registered new interface driver cdc_wdm
[ 4.822668] cdc_acm 2-4:1.9: ttyACM2: USB ACM device
[ 4.823902] usbcore: registered new interface driver cdc_acm
[ 4.823904] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
[ 9.840181] usb 2-4: USB disconnect, address 2
[ 9.841912] ehci_hcd 0000:00:1d.7: dma_pool_free buffer-2048, f5f48000/35f48000 (bad dma)
[ 9.842038] ehci_hcd 0000:00:1d.7: dma_pool_free buffer-2048, f5f48080/35f48080 (bad dma)
Sorry: meant 2.6.27-11, 2.6.28-11, and 2.6.28-13 for the kernel versions.
I managed to get it to work well with 2.6.30
What I had to do was just the following:
sudo sh -c 'echo 1 > /sys/devices/platform/thinkpad_acpi/wwan_enable'
This activates my device, and from then on (has to be executed on every boot/resume) the card is working perfectly.
BUT not with the newest kernel 2.6.31
The wwan_enable is gone there, and I have no idea how to enable the card.
Hard to tell what it is.
For your latest comment, it could be that the BIOS shakes up as the system comes up and decides the device should be off (hard rfkill off) and thus, disconnects it from the system.
On the matter of wwan_enable going out, let me see what my system (x200s) says...oh, old kernel.
In any case, in a new kernel (source), check Documentation/laptop/thinkpad-acpi.txt. It says wwan_enable has been deprecated and the feature integrated into the rfkill framework.
Go to /sys/class/rfkill, find the one that matches the device (cat */name); in my x200 (w/o 3g, but w WiMAX):
$ cd /sys/class/rfkill
$ for file in */name; do echo -n $file:; cat $file; done
so, as root, to turn off a device
$ echo 0 > /sys/class/rfkill0/state
or to turn on
$ echo 1 > /sys/class/rfkill0/state
I bet if you replace rfkill0 with the one matching your wan modem, you will get it to work :)