PowerPC Failed to request_firmware

bupt · **Joined:** Thu Dec 04, 2008 8:33 am **Posts:** 8

hi , I am trying wn321g on PPC8349(kernel 2.6.13) , the cross-compile tool is LTIB,and the source-code is the latest version(rt73-CVS-2008120319). I modified the Makefile and rt73.ko was successfully built.
Now is the problem:

### command and output on powerpc ###

~ # mkdir /lib/firmware
~ # mv rt73.bin /lib/firmware

~ # insmod rt73.ko
rt73: init
rt73: idVendor = 0x148f, idProduct = 0x2573
rt73: Failed to request_firmware. Check your firmware file location
rt73: Failed to load Firmware.
rt73: probe of 1-1.1:1.0 failed with error -2
usbcore: registered new driver rt73

~ # iwconfig
eth0 no wireless extensions.
eth1 no wireless extensions.
lo no wireless extensions.
wlan0 RT73 WLAN
Link Quality:0 Signal level:0 Noise level:113
Rx invalid nwid:0 invalid crypt:0 invalid misc:0

~ # ifconfig wlan0 up
rt73: driver version - 1.0.3.6 CVS
rt73: Firmware not load
SIOCSIFFLAGS: Input/output error

but rt73.bin is no doubt in the new folder /lib/firmware, so how should I do next?

btw: I have tried commands:
~ # rmmod rt73.ko
~ # depmod -a
~ # modprobe rt73.ko
FATAL: Module rt73.ko not found.

Vern · **Posted:** Thu Dec 04, 2008 4:37 pm

Hi bupt,

Have you done "make" or "make all", followed by "make install" (as root)?

Thanks,

bupt · **Joined:** Thu Dec 04, 2008 8:33 am **Posts:** 8

Vern wrote:

Hi bupt,

Have you done "make" or "make all", followed by "make install" (as root)?

Thanks,

Hi ,Vern
I have done "make V=1 ARCH=ppc" using ross-compile tool(LTIB fo PowerPC) as root on PC and the Module rt73.ko was built successfully.
As far as I understand, "make install" just do the following jobs: 1. mkdir /lib/firmware 2. cp rt73.bin /lib/firmware ,
I want to use the driver on PowerPC, so I did the same thing on PowerPC(copy rt73.bin to dir /lib/firmware ),
but I do not undestand the reason why it reports
"rt73: Failed to request_firmware. Check your firmware file location".

Thanks

Vern · **Posted:** Fri Dec 05, 2008 3:55 am

Then do "make install" or "make modules_install" as root and see what happens.

wrt.

bupt wrote:

btw: I have tried commands:
~ # rmmod rt73.ko
~ # depmod -a
~ # modprobe rt73.ko
FATAL: Module rt73.ko not found.

What does "ls -l /lib/modules/`uname -r`/extra" say?

Thanks,

bupt · **Joined:** Thu Dec 04, 2008 8:33 am **Posts:** 8

Vern wrote:

Then do "make install" or "make modules_install" as root and see what happens.
FATAL: Module rt73.ko not found.

What does "ls -l /lib/modules/`uname -r`/extra" say?

Thanks,[/quote]

Sorry, Vern, I don't think I know what you mean. I can not do "make" or "make install" on PPC, so I do not
quite understand why you want to make sure the step "make install". Anyway, I did "make install" on PC ,here is the result:

make V=1 ARCH=ppc install
*** Install module in /lib/modules/2.4.20-8/extra ...
make[1]: Entering directory `/usr/local/mpc8349/small/rpm/BUILD/linux-2.6.13'
make -rR -f /usr/local/mpc8349/small/rpm/BUILD/linux-2.6.13/scripts/Makefile.modinst
mkdir -p /lib/modules/2.6.13.4/extra; cp /home/liucheny/working/rt73-cvs-2008120319/Module/rt73.ko /lib/modules/2.6.13.4/extra
make[1]: Leaving directory `/usr/local/mpc8349/small/rpm/BUILD/linux-2.6.13'
/sbin/depmod -a
*** Update /etc/modprobe.d/ralink alias for wlan*
*** Config dir /etc/modprobe.d not found
*** Install firmware in /lib/firmware ...
*** Check old config ...

# ls -l /lib/modules/2.6.13.4/extra
# rt73.ko

Thanks for patience

Vern · **Posted:** Fri Dec 05, 2008 4:13 pm

wrt.

Quote:

# ls -l /lib/modules/2.6.13.4/extra
# rt73.ko

Funny. On my system "ls -l /lib/modules/2.6.26/extra" gives:

Code:

...
-rw-r--r-- 1 root root 218455 Nov 22 12:22 rt73.ko
...

bupt · **Joined:** Thu Dec 04, 2008 8:33 am **Posts:** 8

Vern wrote:

wrt.

Quote:

# ls -l /lib/modules/2.6.13.4/extra
# rt73.ko

Funny. On my system "ls -l /lib/modules/2.6.26/extra" gives:

Code:

...
-rw-r--r-- 1 root root 218455 Nov 22 12:22 rt73.ko
...

Actually, on my system "ls -l /lib/modules/2.6.13.4/extra" gives:"
-rw-r--r-- 1 root root 287339 Nov 14 14:44 rt73.ko

Vern · **Posted:** Sun Dec 07, 2008 4:14 pm

Hi bupt,

Well, everything seems to be as it should. There may be an endian problem - assuming you're running your machine in big endian mode. That has not been very thoroughly checked out for the rt73 driver, due to putative users collapsing in the traces on me.

Could you build and run with debug enabled, then attach a copy of /var/log/debug to a post here?

Thanks,

bupt · **Joined:** Thu Dec 04, 2008 8:33 am **Posts:** 8

OK, here is my steps:

command on PC:

Code:

$ make clean
$ make V=1 ARCH=ppc debug

command and output on powerpc

Code:

# mkdir /lib/firmware
~ # mv rt73.bin /lib/firmware
~ # insmod rt73.ko debug=31
rt73: init
rt73: idVendor = 0x148f, idProduct = 0x2573
rt73: Failed to request_firmware. Check your firmware file location
rt73: Failed to load Firmware.
rt73: probe of 1-1.1:1.0 failed with error -2
usbcore: registered new driver rt73

*** On PowerPC, there are only three files included in dir /var/log,
lastlog、messages and wtmp,
and the only one changed after "insmod rt73.ko debug=31" is file "message"
here is all the information in it ***

Code:

Feb 14 18:10:31 mpc8349itx-min-fs user.info kernel: rt73: init
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73 1-1.1:1.0: usb_probe_interface
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73 1-1.1:1.0: usb_probe_interface - got id
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73: --> usb_rtusb_probe (2.6)
Feb 14 18:10:31 mpc8349itx-min-fs user.info kernel: rt73: idVendor = 0x148f, idProduct = 0x2573 
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73: usb device name wlan0
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73: BulkOutMaxPacketSize  512
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73: rt73_get_ether_stats --->
Feb 14 18:10:31 mpc8349itx-min-fs user.debug kernel: rt73: --> LoadFirmware 
Feb 14 18:10:41 mpc8349itx-min-fs user.debug kernel: rt73: rt73: Failed to request_firmware. Check your firmware file location
Feb 14 18:10:41 mpc8349itx-min-fs user.err kernel: rt73: Failed to request_firmware. Check your firmware file location
Feb 14 18:10:41 mpc8349itx-min-fs user.debug kernel: rt73: <-- LoadFirmware (status: -2, loaded: 0)
Feb 14 18:10:41 mpc8349itx-min-fs user.debug kernel: rt73: - common_probe: Failed to load Firmware.
Feb 14 18:10:41 mpc8349itx-min-fs user.crit kernel: rt73: Failed to load Firmware.
Feb 14 18:10:41 mpc8349itx-min-fs user.debug kernel: rt73: <-- common_probe: Status = -2
Feb 14 18:10:41 mpc8349itx-min-fs user.debug kernel: rt73: <-- usb_rtusb_probe: res=-2
Feb 14 18:10:41 mpc8349itx-min-fs user.warn kernel: rt73: probe of 1-1.1:1.0 failed with error -2
Feb 14 18:10:41 mpc8349itx-min-fs user.info kernel: usbcore: registered new driver rt73

it seems like I can not upload attachment now "The extension is not allowed"

Vern · **Posted:** Mon Dec 08, 2008 4:03 pm

Hi bupt,

According to this thread, firmware is loaded OK on a Mac G3 - which I believe is also big endian.

The -2 return code is -ENOENT: i.e. no such file. It looks like there may be a problem with where your particular kernel firmware facility looks for firmware.

Thanks,

bupt · **Joined:** Thu Dec 04, 2008 8:33 am **Posts:** 8

Vern wrote:

Hi bupt,

According to this thread, firmware is loaded OK on a Mac G3 - which I believe is also big endian.

The -2 return code is -ENOENT: i.e. no such file. It looks like there may be a problem with where your particular kernel firmware facility looks for firmware.

Thanks,

Hi Vern,
I think this is not a big endian problem,too. I noticed that some people come accross the same problem on this forum, do you have any suggestion? I did

Code:

mkdir /lib/firmware

and copied rt73.bin to this dir , but the firmware can not be loaded. I don't know why.
Thanks a lot

IvD · **Posted:** Tue Dec 09, 2008 6:25 am

In those other posts possible solutions where also provided.
* Is /lib/firmware the right firmware folder on your distro
* Is udev/hotplug configured for firmware

rt2x00.serialmonkey.com

Forum rules

PowerPC Failed to request_firmware

Who is online