<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><DIV>Hi Inaky,</DIV>
<DIV> </DIV>
<DIV>Here is some new debugging messages.</DIV>
<DIV> </DIV><SPAN lang=EN>
<DIV>**** the outpt of 'tail -f /var/log/messages' when I connect the card and run wimaxd</DIV>
<DIV>Nov 19 13:02:24 bronx wimaxd[4132]: wimaxd event: Starting...</DIV>
<DIV>Nov 19 13:02:24 bronx wimaxd[4132]: daemon starts</DIV>
<DIV>Nov 19 13:02:24 bronx wimaxd[4133]: pdifile is created</DIV>
<DIV>Nov 19 13:02:24 bronx wimaxd[4133]: Initializing... </DIV>
<DIV>Nov 19 13:02:25 bronx wimaxd[4133]: wimaxd event: libwimax[wmx0]: </DIV>
<DIV>Nov 19 13:02:25 bronx wimaxd[4133]: wimaxd event: E: wimaxll_msg_write: generic netlink ack failed: -110 </DIV>
<DIV>Nov 19 13:02:25 bronx kernel: [ 561.113572] i2400m_usb 4-6:1.0: firmware: requesting i2400m-fw-usb-1.4.sbcf</DIV>
<DIV>Nov 19 13:02:25 bronx kernel: [ 561.214210] i2400m_usb 4-6:1.0: WARNING!!! non-signed boot UNTESTED PATH!</DIV>
<DIV>Nov 19 13:02:26 bronx kernel: [ 561.680823] i2400m_usb 4-6:1.0: firmware interface version 9.1.1</DIV>
<DIV> </DIV>
<DIV>****When I try RFKILL</DIV>
<DIV>root@bronx:/etc/wimax# wimaxll-rfkill wmx0 off</DIV>
<DIV>I: rfkill status is 0x0 (HW off SW off)</DIV>
<DIV>root@bronx:/etc/wimax# wimaxll-rfkill wmx0 on</DIV>
<DIV>libwimax[wmx0]: E: RFKILL: operation failed: -84</DIV>
<DIV>E: wimaxll_rfkill(on): -84</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>I have also attached the updated /var/log/wimax debug messages.</DIV>
<DIV> </DIV>
<DIV>Thanks,</DIV>
<DIV>Brandon</DIV>
<DIV></SPAN><BR>--- On <B>Thu, 11/19/09, Inaky Perez-Gonzalez <I><inaky@linux.intel.com></I></B> wrote:<BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(16,16,255) 2px solid"><BR>From: Inaky Perez-Gonzalez <inaky@linux.intel.com><BR>Subject: Re: Intel 5350 Firmware Download Issue<BR>To: "Brandon Dell" <stymiecc04@yahoo.com><BR>Cc: wimax@linuxwimax.org<BR>Date: Thursday, November 19, 2009, 12:38 PM<BR><BR>
<DIV class=plainMail>[sorry, hit enter too soon -- as well, I wanted to CC the mailing list<BR>for other people's future reference]<BR><BR>On Thu, 2009-11-19 at 09:37 -0800, Inaky Perez-Gonzalez wrote:<BR>> On Thu, 2009-11-19 at 07:56 -0800, Brandon Dell wrote:<BR>> > Hi Inaky,<BR>> > <BR>> > Attached are the debug files you requested. Thanks for your help.<BR>> > <BR>> > Also, I thought I should let you know that I am running Linux<BR>> > 2.6.29.6(from kernel.org), Wimax Network Service v1.4, and Intel<BR>> > Supplicant Binary v1.4 (from linuxwimax.org). I followed the<BR>> > installation instructions exactly for the two latter packages.<BR>> <BR>> Hmmm -- thanks for the log files. Well, wimaxd1.log doesn't show<BR>> anything interesting, it is known for not being reporter friendly. So<BR>> let's try upping the debug level.<BR>> <BR>> In
/etc/wimax/config.xml, edit and change in<BR>> <BR>> <Modules>1007812360</Modules><BR>> <Severities>31</Severities><BR>> <BR>> the 1003812360 to 2147483648; that should be a hex mask but it is not, I<BR>> don't know the reason.<BR>> <BR>> After that, the same as before<BR>> <BR>> $ killall -9 wimaxd<BR>> $ rm -f /var/log/wimax/*<BR>> $ wimaxd <BR>> $ sleep 20s<BR>> $ wimaxcu status<BR>> <BR><BR>Also, before running that, try to run:<BR><BR>$ wimaxll -i wmx0 rfkill off<BR>$ wimaxll -i wmx0 rfkill on<BR><BR>if this works, it confirms that the device is doing ok. <BR><BR>Thanks,<BR><BR></DIV></BLOCKQUOTE></td></tr></table><br>