hardware data for Broadcom NIC mismatch kernel

Forum: User Feedback
Topic: hardware data for Broadcom NIC mismatch kernel
started by: BV1AL

Posted by BV1AL on Jan. 15 2006,12:01

the kernel module for Broadcom NIC named "b44"
but the hardware data for Broadcom NIC named "bcm4400"
so the Broadcom NIC module can not loaded automatically.
need "modprobe b44" to make it work.

in /usr/share/hwdata/pcitable
"Broadcom Corporation|BCM4401 100Base-T" and
"Broadcom Corporation|BCM4402 Integrated 10/100BaseT"
should be "b44" but not "bcm4400"

Posted by cbagger01 on Jan. 16 2006,06:27

So that must be why the b44.o will not be autodetected.

Thanks for the info.

Posted by roberts on Jan. 16 2006,16:48

BV1AL, Thanks for this. It will be in the next cut.
This should help many.

Posted by Margni on Jan. 23 2006,16:38

I'm trying to fix this myself, and can't get the /KNOPPIX/usr/share/hwdata/pcitable to open for r/w it only wants to be r/o...

Tried sudo beaver /KNOPPIX/usr/share/hwdata/pcitable

but it won't let me change those lines for BCM4400 to b44...

Where am i going wrong? I'm on DSL on a pen drive... so I figure it should write to it?? right??

Thanks in advance...

Posted by cbagger01 on Jan. 23 2006,17:32

Try booting with:

dsl write

and then type the following:

sudo su
rm /usr/share/hwdata/pcitable
cp /KNOPPIX/usr/share/hwdata/pcitable /usr/share/hwdata/pcitable
beaver /usr/share/hwdata/pcitable

and don't forget to add it to your filetool.lst

Posted by margni on Jan. 23 2006,17:50

Thanks! Going to give a shot now... report back in a while...

Does adding it to your filetool.lst put this into startup?

Posted by margni on Jan. 23 2006,18:47

Got the pcitabled edited, saved, rebooted... Nothing...

Help! Thanks in advance...

Posted by cbagger01 on Jan. 24 2006,17:10

The problem is the restoration of the backup happens AFTER the autodetection process.

If you want to re-run the autodetection, you can add:

/etc/init.d/knoppix-autoconfig &

to your /opt/bootlocal.sh

Posted by roberts on Jan. 24 2006,17:57

It probably would be easier to just

modprobe b44

to your /opt/bootlocal.sh

The fix to the pcitable will be in the next build.

Posted by cbagger01 on Jan. 24 2006,18:06

I try to respond to the question as asked.

I usually don't take the time to consider whether or not it is the best way to do it