Florian Kulzer wrote:
> Udev is responsible for managing the device nodes in /dev and the names
> of the network devices. More information is here:
> /usr/share/doc/udev/writing_udev_rules/index.html
>
Thanks, I will have a look.
> The problem with the broadcom chip appears to be that the firmware is
> not present at the first boot of a Debian system, so only the master
> device is detected and added to z25_persistent-net.rules. This seems
> somehow to block correct name assignment for the "real" (usable) device
> (later, when the firmware has been installed).
>
>
How can I see, that the firmware has been installed?
The firmware, installed with "*fwcutter" is present in
"/lib/firmware/b43" and in "/lib/firmware/b43legacy".

"b43-fwcutter" and "bcm43xx-fwcutter" are importing a firmware version,
which is different from the firmware version used by "ndiswrapper".
"ndiswrapper" can use the latest Firmware
<http://h10025.www1.hp.com/ewfrf/wc/genericSoftwareDownloadIndex?softwareitem=ob-46095-1&cc=us&lc=en&dlc=en&dlc=en&lang=en>
"bcmwl6" and "bcmwl5", which is refused by "fwcutter" because of the
unknown checksums.
> The bugzilla links suggest that you can simply delete or rename the
> persistent-net.rules file and reboot. With the firmware present udev
> obviously creates the rules for the two interfaces at once and
> correctly.
>
> If this does not work then we need to see the content of the rules file
> (after its re-creation with the firmware present during boot) and the
> full output of "/sbin/ifconfig" and "dmesg|grep b43".
>
>
# cat z25_persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:24:aa:41:9d",
NAME="eth0"
----------------------------------------------------------------
That is all, after the renaming of the old "z25_persistent-net.rules"
and a new boot of the Debian 2.6.24 kernel.

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:1b:24:aa:41:9d
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:24ff:feaa:419d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22208 errors:0 dropped:0 overruns:0 frame:0
TX packets:19715 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:20423913 (19.4 MiB) TX bytes:2747911 (2.6 MiB)
Interrupt:19 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:188 errors:0 dropped:0 overruns:0 frame:0
TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:12581 (12.2 KiB) TX bytes:12581 (12.2 KiB)
--------------------------------------------------------------------------------
# dmesg|grep b43 delivers nothing, just like searching through the
entire /var/log for "b43" delivers no result except for aptitude.

Hugo



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org