On Fri, 2006-12-22 at 16:10 -0500, Rudolph Pienaar wrote: > Hi all - > > First off, Season's Greetings to all. Things have been getting more and more > quiet on this list lately. Hope there's still some life around! > > I am running a gentoo 64-bit kernel with suspend extensions: 2.6.18-suspend2, > and have been for a month or more, with no problems. > > Earlier today, I wanted to bluetooth some pics from my phone, when I realised > that since my upgrade bluetooth wasn't working. I eventually traced the > problem to the 'rfcomm' module not running. I did a 'modprobe rfcomm' and all > seemed well. To make it more permanent, I also added it to > > /etc/modules.autoload.d/kernel-2.6 > > and, to test properly, rebooted the machine. > > On next boot, none of my network interfaces worked. I soon noticed that > a "new" eth0 had appeared, and my "old" eth0 was now mysteriously eth1. Also, > a "new" eth2 had appeared, and my old wlan0 (ndiswrapper-based) seemed gone. > > The MAC address of the new eth0 was bizarre: > > 4A-3F-02-00-4A-3F-02-00-00-00-00-00-00-00-00-00 > > Also, eth2 appeared as if it were a wireless interface - but I'm guess it is > the bluetooth device since eth2 doesn't connect to anything: > > #iwlist eth2 scan > eth2 Interface doesn't support scanning : No such device > > Can anyone help / suggest anything?! I'm up and running with a wired > connection on eth1, but would like to have my wireless connection back!
Well, eth0 looks like your Firewire / IEEE-1394 IP interface. That's why the MAC looks odd, it isn't Ethernet. I don't know why yours came up as eth0. Mine is eth1. Your wireless card is now eth2, and that is probably because your system is loading the bcm43xx wireless drivers instead of ndiswrapper. You probably updated the udev package at some point. I tried blacklisting modules and other things but nothing udev based worked for me. So what I did to fix the eth2/wlan0 problem is to add: alias bcm43xx off alias ieee80211softmac off to /etc/modules.d/aliases, and rerun modules-update of course. After doing that and rebooting it should load ndiswrapper and be back to wlan0. Fedora and RHEL use the interface MAC address to set the name of the interface so your eth0 never gets moved to eth5. I don't know exactly how Gentoo handles interface renaming but I'll have to find out soon I suppose. Newer Linux kernels are changing to dynamic everything. As soon as they get multi-threaded bus probing to work (probably in 2.6.21 or 22), devices are going to start showing up in nearly random order, especially on multi-core CPUs or SMP systems. Ah, Gentoo's /etc/conf.d/net.example does show how to name based on MAC address, but the comment says udev rules are superior. -- Zan Lynx <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ LinuxR3000 mailing list [email protected] http://lists.pcxperience.com/cgi-bin/mailman/listinfo/linuxr3000 Wiki at http://prinsig.se/weekee/
