bcm43xx & fwcutter

I'm trying to get FC6 x86_64 to work on an nx6125 using the
experimental bcm43xx drivers with fwcutter, and I'm having a bit of
difficulty in figuring out where it is I'm supposed to put the
hacked-out firmware images fwcutter produces. Currently I've got them
in /lib/ somewhere, but when I insmod the bcm43xx module it barfs about
not being able to find the .fw files... trouble is, I haven't a clue
where to put them and there isn't exactly any direction available in
the associated man pages or readmes.

Anyone of any assistance?

Cheers,
-C

C.J. Steele wrote:
> I'm trying to get FC6 x86_64 to work on an nx6125 using the
> experimental bcm43xx drivers with fwcutter, and I'm having a bit of

Where from?

> difficulty in figuring out where it is I'm supposed to put the
> hacked-out firmware images fwcutter produces. Currently I've got them
> in /lib/ somewhere, but when I insmod the bcm43xx module it barfs about

According to mechanism you use, you should place your firmware files. If udev
takes care of fw loading (check its rules, find SUBSYSTEM=="firmware"), then you
probably need to go through the script it calls and find out, how is your
firmware loaded and put firmware in location, where your loader searches for
it... (and check also /var/log/messages)

> not being able to find the .fw files... trouble is, I haven't a clue
> where to put them and there isn't exactly any direction available in
> the associated man pages or readmes.

regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby

On Nov 18, 5:28 am, Jiri Slaby <jirisl...@gmail.com> wrote:
> C.J. Steele wrote:
> > I'm trying to get FC6 x86_64 to work on an nx6125 using the
> > experimental bcm43xx drivers with fwcutter, and I'm having a bit of
>
> Where from?

http://bcm43xx.berlios.de/

<snip>
> According to mechanism you use, you should place your firmware files. If udev
> takes care of fw loading (check its rules, find SUBSYSTEM=="firmware"), then you
> probably need to go through the script it calls and find out, how is your
> firmware loaded and put firmware in location, where your loader searches for
> it... (and check also /var/log/messages)

I guess I would've expected this to be a generic location. Turns out,
its distribution dependent, which leads me to believe there's a config
file somewhere that one must mangle to get this to work properly.

For Gentoo, the magic directory for your firmware files appears to be
/usr/lib/hotplug/firmware while for Fedora Core 6 it appears to be
/lib/firmware.

After I produced the necessary firmware bits using fwcutter, and after
I got them in /lib/firmware (which I found on accident, as it looked
highly suspicious), all I had to do was modprobe bcm43xx and then apply
the appropriate configuration to eth1 (which is the interface that
appeared after modprobing bcm43xx.)

BTW: there was no useful information in either dmesg or
/var/log/messages, or anywhere in /var/log/.

Anywho, all is well now.

Next-stop: power management. If I can get power management to work
properly then I'll have a 64-bit laptop! w00t!

-C

Thought I should point out that the location of where your distro
sticks the bcm43xx fwcutter image files is a direct result of your udev
package. `rpm -qf /lib/firmware` revealed that the directory was owned
by the udev package.

-C

On Nov 18, 5:43 am, "C.J. Steele" <coreyjste...@yahoo.com> wrote:
> On Nov 18, 5:28 am, Jiri Slaby <jirisl...@gmail.com> wrote:
>
> > C.J. Steele wrote:
> > > I'm trying to get FC6 x86_64 to work on an nx6125 using the
> > > experimental bcm43xx drivers with fwcutter, and I'm having a bit of
>
> > Where from?http://bcm43xx.berlios.de/
>
> <snip>
>
> > According to mechanism you use, you should place your firmware files. If udev
> > takes care of fw loading (check its rules, find SUBSYSTEM=="firmware"), then you
> > probably need to go through the script it calls and find out, how is your
> > firmware loaded and put firmware in location, where your loader searches for
> > it... (and check also /var/log/messages)I guess I would've expected this to be a generic location. Turns out,
> its distribution dependent, which leads me to believe there's a config
> file somewhere that one must mangle to get this to work properly.
>
> For Gentoo, the magic directory for your firmware files appears to be
> /usr/lib/hotplug/firmware while for Fedora Core 6 it appears to be
> /lib/firmware.
>
> After I produced the necessary firmware bits using fwcutter, and after
> I got them in /lib/firmware (which I found on accident, as it looked
> highly suspicious), all I had to do was modprobe bcm43xx and then apply
> the appropriate configuration to eth1 (which is the interface that
> appeared after modprobing bcm43xx.)
>
> BTW: there was no useful information in either dmesg or
> /var/log/messages, or anywhere in /var/log/.
>
> Anywho, all is well now.
>
> Next-stop: power management. If I can get power management to work
> properly then I'll have a 64-bit laptop! w00t!
>
> -C