On Tue, Jun 16, 2009 at 12:42:27AM +0200, Josip Rodin wrote: > On Tue, Jun 16, 2009 at 12:34:46AM +0200, Josip Rodin wrote: > > > > > I have an integrated wireless setup inside my Lenovo Thinkpad T400 which > > > > > normally works fine and provides WiFi, Bluetooth and WWAN connectivity. > > > > > The wifi card is utilized by the iwlagn driver, and WWAN modem appears > > > > > as cdc_acm device. > > > > > > > > > > I upgraded from 2.6.28.10 to 2.6.30 and that went well as far as iwlagn > > > > > was concerned, however, I noticed that the WWAN function is broken - the > > > > > ttyACM* devices silently disappeared and won't come back - even lsusb > > > > > doesn't show the Ericsson F3507g device any more! > > > > > > > > > > Is this a known problem, or do I need to bisect it? > > > > > > > > It's not a known problem, and yours is not the only report of this. > > > > > > > > Could you bisect it to help us resolve it? > > > > > > I just did a first poor man's bisection - downgrading one notch down to > > > 2.6.29.5 - it doesn't change things, so the problem's in there somewhere. > > > > > > Which subdirectory do I use for git bisection, just drivers/net/usb or > > > the whole drivers/usb/ or? > > > > While git was cloning, I remembered to do a google search with 2.6.29 (my > > previous attempt was with 2.6.30 and that didn't give me anything), and that > > provided a very useful answer: > > > > http://www.nabble.com/Cannot-get-Ericsson-F3507G-to-work-with-the-Option-module-tt21993695.html#a21995246 > > > > So I thought - let me check that wwan_enable thing on 2.6.30: > > > > % cat /sys/devices/platform/thinkpad_acpi/wwan_enable > > 0 > > thinkpad_acpi: deprecated sysfs attribute: access by process with PID 2968 > > thinkpad_acpi: WARNING: sysfs attribute wwan_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010 > > % sudo sh -c 'echo 1 > /sys/devices/platform/thinkpad_acpi/wwan_enable' > > thinkpad_acpi: deprecated sysfs attribute: access by process with PID 2968 > > thinkpad_acpi: WARNING: sysfs attribute wwan_enable is deprecated and will be removed. Please switch to generic rfkill before year 2010 > > usb 8-4: new high speed USB device using ehci_hcd and address 4 > > usb 8-4: configuration #1 chosen from 2 choices > > cdc_acm 8-4:1.1: ttyACM0: USB ACM device > > cdc_acm 8-4:1.3: ttyACM1: USB ACM device > > cdc_wdm 8-4:1.5: cdc-wdm0: USB WDM device > > cdc_wdm 8-4:1.6: cdc-wdm1: USB WDM device > > usb0: register 'cdc_ether' at usb-0000:00:1d.7-4, CDC Ethernet Device, 02:80:37:ec:02:00 > > cdc_acm 8-4:1.9: ttyACM2: USB ACM device > > > > Yay. Now I see that I've been looking at a different scenario - while > > upgrading to 2.6.30, I noticed that iwlagn has RFKILL support, and enabled > > it. I definitely tested it at one point - maybe that tripped off the > > problematic situation. So now I tried using the little physical switch, > > on and off again, and everything seems fine. I'll try it again after a > > reboot, in a minute. > > Oddly enough, it works fine after a reboot - the wwan_enable is still set > to 1. > > So it looks like the remaining problem is that something somewhere seems > to have set that option in a way that disabled the hardware, but nothing > tells the user that there is a problem. Can this be fixed? I really have no idea, it doesn't sound like a USB problem, but a platform issue :( sorry, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
