Re: Etch and unstable Belkin wireless problem
Sven Joachim <svenjoac@gmx.de> writes:
> On 2009-01-14 19:41 +0100, Joe Dennigan wrote:
>
>> I installed Etch on a HP Pavilion ZE4900 in June 2008, and have since
>> 'upgraded' to unstable. However, from the beginning there has been a
>> glitch configuring my wireless card. It's a Belkin F5D7010 (RaLink
>> RT2500).
>>
>> If I boot, wait for the login prompt and then insert the card all
>> works as expected. However, if I boot with the card inserted the
>> transmission led turns on and that's it. Trying to bring the card
>> down then up produces the following error messages:
>>
>> ifdown eth1:
>> eth1: unknown hardware address type 801
>> eth1: unknown hardware address type 801
>> [...]
>> [ 16.117934] udev: renamed network interface wmaster0 to eth1
>
> 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>
auto eth1
iface eth0 inet dhcp
# I don't use eth0 often enough to make this worthwhile
#auto eth0
> /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"
> 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. Booting with the card unplugged
disabled the card completely. No network at all.
All most perplexing.
Joe
--
What part of "Ph'nglui mglw'nath Cthulhu R'lyeh wgah'nagl fhtagn" don't
you understand?
Reply to: