Re: Etch and unstable Belkin wireless problem
On 2009-01-14 21:31 +0100, Joe wrote:
> Sven Joachim <svenjoac@gmx.de> writes:
>
>> Why is wmaster0 renamed to eth1? And what about wlan0?
>
> Eth0 is the onboard Realtek ethernet. Don't Know why wmaster0 is
> renamed. The configuration is the Debian default setup, except for
> one modification to /etc/network/interfaces - see below - and I really
> don't know about wlan0. If I boot from a Mepis live cd the Belkin
> card does show up as wlan0.
>
>> Please show your /etc/network/interfaces and
> :
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> allow-hotplug eth1
>
> iface eth1 inet dhcp
> wireless-essid TalkTalkcbejc
> wireless-key <deleted for security reasons>
Which type of encryption (if any) do you use?
>> /etc/udev/rules.d/70-persistent-net.rules.
>
> # This file was automatically generated by the /lib/udev/write_net_rules
> # program, probably run by the persistent-net-generator.rules rules file.
> #
> # You can modify it, as long as you keep each rule on a single line.
> # MAC addresses must be written in lowercase.
>
> # PCI device 0x10ec:0x8139 (8139too)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:c0:9f:45:a6:0f", NAME="eth0"
>
> # PCI device 0x1814:0x0201 (rt2500)
> SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:11:50:65:9d:75", NAME="eth1"
This is bad, but it seems to be a common problem when upgrading from
etch. You need to add
, ATTRS{type}=="1"
to these lines. Alternatively, rename it the file and reboot, then udev
will regenerate it (but your wireless card will probably named wlan0).
>> It seems you have both the module in the kernel (rt2500pci) and the one
>> from rt2500-source (rt2500) loaded, this is probably bad. Can you
>> blacklist the rt2500 module and see if that helps?
>
> Blacklisting rt2500 had no effect when booting with the card
> inserted. Lsmod showed it was still loaded, along with rt2500pci et
> al, and the same problems persisted.
That's probably because the rt2500 driver was loaded from initramfs.
You need to update that as well with update-initramfs(8). This is also
necessary if you change the /etc/udev/rules.d/70-persistent-net.rules,
since udev files are also copied to the initramfs.
> Booting with the card unplugged
> disabled the card completely. No network at all.
Does the card even show up then? You have to fix the udev rules first,
I think.
Sven
Reply to: