Hi Inaky, Here is some new debugging messages. **** the outpt of 'tail -f /var/log/messages' when I connect the card and run wimaxd Nov 19 13:02:24 bronx wimaxd[4132]: wimaxd event: Starting... Nov 19 13:02:24 bronx wimaxd[4132]: daemon starts Nov 19 13:02:24 bronx wimaxd[4133]: pdifile is created Nov 19 13:02:24 bronx wimaxd[4133]: Initializing... Nov 19 13:02:25 bronx wimaxd[4133]: wimaxd event: libwimax[wmx0]: Nov 19 13:02:25 bronx wimaxd[4133]: wimaxd event: E: wimaxll_msg_write: generic netlink ack failed: -110 Nov 19 13:02:25 bronx kernel: [ 561.113572] i2400m_usb 4-6:1.0: firmware: requesting i2400m-fw-usb-1.4.sbcf Nov 19 13:02:25 bronx kernel: [ 561.214210] i2400m_usb 4-6:1.0: WARNING!!! non-signed boot UNTESTED PATH! Nov 19 13:02:26 bronx kernel: [ 561.680823] i2400m_usb 4-6:1.0: firmware interface version 9.1.1 ****When I try RFKILL r...@bronx:/etc/wimax# wimaxll-rfkill wmx0 off I: rfkill status is 0x0 (HW off SW off) r...@bronx:/etc/wimax# wimaxll-rfkill wmx0 on libwimax[wmx0]: E: RFKILL: operation failed: -84 E: wimaxll_rfkill(on): -84 I have also attached the updated /var/log/wimax debug messages. Thanks, Brandon
--- On Thu, 11/19/09, Inaky Perez-Gonzalez <[email protected]> wrote: From: Inaky Perez-Gonzalez <[email protected]> Subject: Re: Intel 5350 Firmware Download Issue To: "Brandon Dell" <[email protected]> Cc: [email protected] Date: Thursday, November 19, 2009, 12:38 PM [sorry, hit enter too soon -- as well, I wanted to CC the mailing list for other people's future reference] On Thu, 2009-11-19 at 09:37 -0800, Inaky Perez-Gonzalez wrote: > On Thu, 2009-11-19 at 07:56 -0800, Brandon Dell wrote: > > Hi Inaky, > > > > Attached are the debug files you requested. Thanks for your help. > > > > Also, I thought I should let you know that I am running Linux > > 2.6.29.6(from kernel.org), Wimax Network Service v1.4, and Intel > > Supplicant Binary v1.4 (from linuxwimax.org). I followed the > > installation instructions exactly for the two latter packages. > > Hmmm -- thanks for the log files. Well, wimaxd1.log doesn't show > anything interesting, it is known for not being reporter friendly. So > let's try upping the debug level. > > In /etc/wimax/config.xml, edit and change in > > <Modules>1007812360</Modules> > <Severities>31</Severities> > > the 1003812360 to 2147483648; that should be a hex mask but it is not, I > don't know the reason. > > After that, the same as before > > $ killall -9 wimaxd > $ rm -f /var/log/wimax/* > $ wimaxd > $ sleep 20s > $ wimaxcu status > Also, before running that, try to run: $ wimaxll -i wmx0 rfkill off $ wimaxll -i wmx0 rfkill on if this works, it confirms that the device is doing ok. Thanks,
{pid:4172, tid: 3085248720} [1258656060] ./iWmxSDK.c:78 Info:
[iWmxSdk_init]Inited cs : (nil)
{pid:4172, tid: 3085248720} [1258656061] ./iWmxSDK.c:96 Info:
[iWmxSdk_fini]About to delete cs: 0x9b321f0
wimaxcu1.log
Description: Binary data
wimaxd1.log
Description: Binary data
_______________________________________________ wimax mailing list [email protected] http://lists.linuxwimax.org/listinfo/wimax
