<!DOCTYPE html> <html> <head> <title></title> </head> <body><div>On Mon, Jan 12, 2015, at 09:22 AM, Dan Williams wrote:<br></div> <blockquote type="cite"><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 SSD<br></div> <div>on purchase), connect via Dell's "SkyLight" program, then warm-boot<br></div> <div>back to Fedora 20. In that case, the initial power mode read from<br></div> <div>dms-get-operating-mode is "online" rather than "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 for<br></div> <div>rfkill list and do not seem to mention the WWAN card. Although it is<br></div> <div>interesting that the ID numbers(?) are different and the order has<br></div> <div>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 kernel<br></div> <div>version is this machine using?<br></div> <div> </div> <div>If it is a Sierra 8805, can you run 'minicom -D /dev/ttyUSBx' (where 'x'<br></div> <div>is one of the serial ports exposed by the modem, if any) and then run<br></div> <div>"at!pcinfo". Try all the ports, one of them may respond even though the<br></div> <div>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?<br></div> <div>State: LowPowerMode<br></div> <div>LPM force flags - W_DISABLE:0, User:0, Temp:0, Volt:0, BIOS:1, GOBIIM:0<br></div> <div>W_DISABLE: 0<br></div> <div>Poweroff mode: 0<br></div> <div>LPM Persistent: 0<br></div> <div> </div> <div>I checked BIOS settings and was able to find only these, none of which seem to impact the state of this result:<br></div> <div> </div> <div>Wireless Radio Control -- Control WWAN radio checkbox disabled -- was enabled, no change<br></div> <div>Wireless Device Enable -- WWAN checkbox enabled<br></div> <div>Wireless Switch -- WWAN checkbox disabled -- was enabled, no change<br></div> <div> </div> <blockquote type="cite"><div> </div> <div>Dan<br></div> <div> </div> <blockquote><blockquote><div> </div> <div>The other possibility is firmware incompatibility, if the device you<br></div> <div>have requires loading firmware with gobi_loader. But that's only for<br></div> <div>older non-LTE cards usually so I don't think this is too likely.<br></div> </blockquote><div> </div> <div>I think that the fact we can interrogate the modem means that firmware<br></div> <div>is in fact installed. We believe that it did require installation in<br></div> <div>Windows but that it remains in non-volatile memory. The Windows<br></div> <div>installer did have a long period of activity that looked like a<br></div> <div>firmware flash.<br></div> </blockquote><div> </div> <div> </div> <div> </div> </blockquote><div> </div> </body> </html>