<!DOCTYPE html>
<html>
<head>
<title></title>
</head>
<body><div> </div>
<div> </div>
<div> </div>
<div>On Mon, Jan 26, 2015, at 09:45 AM, Isaac Raway wrote:<br></div>
<blockquote type="cite"><div> </div>
<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>
</blockquote><div> </div>
<div>I believe it is a "Dell<span class="highlight" style="background-color: rgb(255, 255, 255)"><span class="colour" style="color:rgb(84, 84, 84)"><span class="font" style="font-family:arial, sans-serif"><span class="size" style="font-size:small"> 5808 Gobi(TM) 4G LTE Mobile Broadband" which appears to actually be a Sierra MC7750 from what I've found online[1]? The lsusb output is:</span></span></span></span><br></div>
<div> </div>
<div>Bus 002 Device 003: ID 413c:81a8 Dell Computer Corp. <br></div>
<div> </div>
<div><span class="highlight" style="background-color: rgb(255, 255, 255)"><span class="colour" style="color:rgb(84, 84, 84)"><span class="font" style="font-family:arial, sans-serif"><span class="size" style="font-size:small">The string obviously isn't terribly useful in identifying it.</span></span></span></span><br></div>
<div> </div>
<div><span class="highlight" style="background-color: rgb(255, 255, 255)"><span class="colour" style="color:rgb(84, 84, 84)"><span class="font" style="font-family:arial, sans-serif"><span class="size" style="font-size:small">Not sure about the Windows kernel - don't have the windows USB disk with me at the moment. It would be the latest patched Windows 7 Pro kernel though.</span></span></span></span><br></div>
</blockquote><div> </div>
<div>Actually it looks like it is identifying as a MC7355. Here is some additional output that I was able to get via AT commands (I don't really know much about this so I'm not sure if this is useful information):<br></div>
<div> </div>
<div>ATI<br></div>
<div>Manufacturer: Sierra Wireless, Incorporated<br></div>
<div>Model: MC7355<br></div>
<div>Revision: SWI9X15C_05.05.39.00 r22582 carmd-fwbuild1 2014/06/14 13:21:08<br></div>
<div>MEID: 35619505057226<br></div>
<div>ESN: 12802831533, 802B34AD<br></div>
<div>IMEI: 356195050572260<br></div>
<div>IMEI SV: 14<br></div>
<div>FSN: ER422300060411<br></div>
<div>+GCAP: +CGSM<br></div>
<div> </div>
<div> </div>
<div>OK<br></div>
<div>AT!CUSTOM?<br></div>
<div>!CUSTOM: <br></div>
<div> GPSENABLE 0x01<br></div>
<div> FASTENUMEN 0x01<br></div>
<div> GPSSEL 0x01<br></div>
<div> NMEAENABLE 0x01<br></div>
<div> UBISTENABLE 0x01<br></div>
<div> GOBIIMEN 0x01<br></div>
<div> USBSERIALENABLE 0x02<br></div>
<div> </div>
<div> </div>
<div>OK<br></div>
<div>AT+CGREG?<br></div>
<div>+CGREG: 2,0<br></div>
<div> </div>
<div>OK<br></div>
<div>AT+CPIN?<br></div>
<div>+CPIN: READY<br></div>
<div> </div>
<div>OK<br></div>
<div>AT+COPS?<br></div>
<div>+COPS: 0<br></div>
<div> </div>
<div>I had set the CGREG mode to 2. The second value there seems to indicate that the modem is not looking for a network -- but I cannot find out how to switch it into a mode where it will actually look for the network.<br></div>
<div> </div>
<div>IJR</div>
<div> </div>
<blockquote type="cite"><div> </div>
<blockquote type="cite"><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>Here's what I get from the port that I had found before:<br></div>
<div> </div>
<div>at!pcinfo<br></div>
<div>ERROR<br></div>
<div> </div>
<div>This is strange, I thought this command had worked fine in the past.<br></div>
</blockquote><div> </div>
</body>
</html>