After send "ifconfig wlan0 up" two time, I get another log-message
Oct 13 20:33:17 ipcop kernel: rt73: Firmware not load
Is this definitly an indication for rt73.bin is at the wrong place ?
Currently it is place in /lib/firmeware were the make-file has put it.
Do you have a firmware loading rule in your udev config?
I´m running IPCOP with a 2.4.43 Kernel, so no udev.
I habe read and asked a litle bit around and they say that I have to switch "devfs" off in the kernel (means, to bild a new Kernel) und than install udef.
I´m not the LINUX-crack, so I´m a litle confused.
In the IPCOP-Forum they told me to load "hotplug" and I did, but with no success (
You can use hotplug instead of udev, but you will need a small firmware loading script triggered by hotplug.
firmware_class is enabled in the kernel?
Maybe your system has already a firmware loading script but it looks for firmware files in a different path, /usr/lib/hotplug/firmware e.g..
I searched on the IPCOP-Homepage and IPCOP (Kernel 2.4.34) needs hotplug and "firmware_class" can be loaded with modprobe.
But I have found "fxload" und as far as understand, it is possible to load firmware directly into a device.
fxload is a tool that only works for chips manufactured by Cypress Semiconductors, and only for microcontrollers from the EZ-DSP, FX and FX2 series (I own one of these [url10cxhxyv]http://home.arcor.de/henning.paul/gallery/cypress.jpg[/url10cxhxyv], thus I happen to know this tool). But these chips use a proprietary firmware loading mechanism and not firmware_class, so this tool won't work for you.
I don't want to explain the whole mechanism over and over again so please look for instance into this thread [url10cxhxyv]http://rt2x00.serialmonkey.com/phpBB2/viewtopic.php?p=26212[/url10cxhxyv].
Don't you guys never search the forum before starting a new thread?
2. Does the 2.3.34 Kernel know the variable $DETHPATH, like used in
the agent (and in the ones I found) because hotplug seems to deliver
$DEVICE and $PATH
Looks like a bit of a problem. But it would be not a big problem to make the script work with $DEVICE only, if we can be sure that there is this special "loading" pseudofile somewhere in /proc. Could you please look for files called "loading" under /proc?
[code24rw21ri]find /proc -name loading[/code24rw21ri]
I don't have a recent kernel 2.4 system at hand...