<!DOCTYPE html> <html> <head> <title></title> </head> <body><div>On Mon, Jan 26, 2015, at 04:33 PM, Dan Williams wrote:<br></div> <blockquote type="cite"><div>On Mon, 2015-01-26 at 15:53 -0600, Isaac Raway wrote:<br></div> <blockquote><div>On Mon, Jan 26, 2015, at 03:12 PM, Dan Williams wrote:<br></div> <blockquote><div>On Mon, 2015-01-26 at 14:42 -0600, Isaac Raway wrote:<br></div> <blockquote><div>On Mon, Jan 12, 2015, at 09:22 AM, Dan Williams wrote:<br></div> <blockquote><div>On Mon, 2015-01-12 at 07:15 -0600, Isaac Raway wrote:<br></div> <blockquote><div>On Wed, Jan 7, 2015, at 09:55 AM, Dan Williams wrote:<br></div> <blockquote><div>On Tue, 2014-12-30 at 11:37 -0600, Isaac Raway wrote:<br></div> <blockquote><div>One interesting note, this card works perfectly if I boot into<br></div> <div>Windows from a USB drive (Windows was banished from the internal<br></div> <div>SSD on purchase), connect via Dell's "SkyLight" program, then<br></div> <div>warm-boot back to Fedora 20. In that case, the initial power mode<br></div> <div>read from dms-get-operating-mode is "online" rather than<br></div> <div>"low-power".<br></div> </blockquote><div> </div> <div>This smells like rfkill driver issues. What do you get for 'rfkill<br></div> <div>list' run in a terminal under Linux from cold-boot, and does that<br></div> <div>change if you boot windows, then warm-boot to Linux?<br></div> </blockquote><div> </div> <div>Cold boot and wam boot both seem to respond with the same results<br></div> <div>for rfkill list and do not seem to mention the WWAN card. Although<br></div> <div>it is interesting that the ID numbers(?) are different and the<br></div> <div>order has changed. Not sure if that is significant.<br></div> <div> </div> <div>Cold boot:<br></div> <div> </div> <div>1: phy0: Wireless LAN Soft blocked: no Hard blocked: no<br></div> <div>2: hci0: Bluetooth Soft blocked: no Hard blocked: no<br></div> <div> </div> <div> </div> <div>Warm boot:<br></div> <div> </div> <div>: hci0: Bluetooth Soft blocked: no Hard blocked: no<br></div> <div>3: phy0: Wireless LAN Soft blocked: no Hard blocked: no<br></div> </blockquote><div> </div> <div>Is this a Dell 5570 (Sierra 8805)? Also, which specific Windows<br></div> <div>kernel version is this machine using?<br></div> <div> </div> <div>If it is a Sierra 8805, can you run 'minicom -D /dev/ttyUSBx' (where<br></div> <div>'x' is one of the serial ports exposed by the modem, if any) and<br></div> <div>then run "at!pcinfo". Try all the ports, one of them may respond<br></div> <div>even though the modem is usually driven by QMI.<br></div> </blockquote><div> </div> <div>Got this to work after a reboot:<br></div> <div> </div> <div>at!pcinfo? State: LowPowerMode LPM force flags - W_DISABLE:0, User:0,<br></div> <div>Temp:0, Volt:0, BIOS:1, GOBIIM:0 W_DISABLE: 0 Poweroff mode: 0 LPM<br></div> <div>Persistent: 0<br></div> <div> </div> <div>I checked BIOS settings and was able to find only these, none of<br></div> <div>which seem to impact the state of this result:<br></div> <div> </div> <div>Wireless Radio Control -- Control WWAN radio checkbox disabled -- was<br></div> <div>enabled, no change Wireless Device Enable -- WWAN checkbox enabled<br></div> <div>Wireless Switch -- WWAN checkbox disabled -- was enabled, no change<br></div> </blockquote><div> </div> <div>So it's not really something in the BIOS setup that the modem is<br></div> <div>talking about here. It's actually just that BIOS has told the modem<br></div> <div>(somehow) to put itself into airplane mode, and that is actually<br></div> <div>controlled from the OS via special calls. These calls are usually<br></div> <div>ACPI. On Linux, there are special drivers for various vendors (hp-wmi,<br></div> <div>thinkpad-acpi, acer-laptop, etc) that do the same things, but when the<br></div> <div>vendor updates their BIOS then the Linux drivers lag behind.<br></div> <div> </div> <div>So my guess here is that even the BIOS setup doesn't affect anything,<br></div> <div>Windows still has a driver that is poking values into the BIOS/NVRAM<br></div> <div>on the laptop and the BIOS is still using those to disable the WWAN<br></div> <div>card. The next step is to get ACPI dumps so that kernel developers can<br></div> <div>try to update the Linux drivers. Filing a bug on<br></div> <div><a href="https://bugzilla.kernel.org/" defang_rel="noreferrer">https://bugzilla.kernel.org/</a> is probably the best way to do that.<br></div> </blockquote><div> </div> <div>Thanks for your help Dan. Bug filed here if anyone cares to track:<br></div> <div><a href="https://bugzilla.kernel.org/show_bug.cgi?id=92101" defang_rel="noreferrer">https://bugzilla.kernel.org/show_bug.cgi?id=92101</a><br></div> </blockquote><div> </div> <div>Quick check, is 'dell-laptop' loaded for your machine? If not, can you<br></div> <div>"modprobe dell-laptop" and then report the output of "rfkill list"?<br></div> </blockquote><div> </div> <div>Hmm it does change the output:<br></div> <div> </div> <div>(iraway@procyon) [~] $ sudo modprobe dell-laptop<br></div> <div>[sudo] password for iraway: <br></div> <div>(iraway@procyon) [~] $ sudo rfkill list<br></div> <div>1: phy0: Wireless LAN<br></div> <div>Soft blocked: no<br></div> <div>Hard blocked: no<br></div> <div>4: hci0: Bluetooth<br></div> <div>Soft blocked: no<br></div> <div>Hard blocked: no<br></div> <div>5: dell-wifi: Wireless LAN<br></div> <div>Soft blocked: no<br></div> <div>Hard blocked: no<br></div> <div>6: dell-bluetooth: Bluetooth<br></div> <div>Soft blocked: no<br></div> <div>Hard blocked: no<br></div> <div> </div> </body> </html>