Lan Barnes wrote:
I hope the following attachment speaks for itself.
There is a lot of weirdness here.
Do this to see what the real interface names are:
Blacklist all the ethernet and wireless modules. Then reboot the system
into single mode. After the system has rebooted, take a look in the
following directory:
# ls /sys/class/net/
lo
If the blacklisting worked properly the only directory you will see is
for the loopback interface, lo.
Now manually load the orinoco-pci driver:
# modprobe orioco-pci
Now check the /sys/class/net/ directory again. What do you see?
Poke around and you will be able to see all kinds of information about
the network interfaces. Use cat to read the files.
1) There seems to be a difference between wifi0 and wlan0. I'm not sure
why there are two interfaces showing up when there should only be one. I
think that wifi0 is some sort of alias for wlan0. Look at the hardware
address that pops up in ifconfig:
HWaddr 00-05-5D-EE-E7-E1-88-83-00-00-00-00-00-00-00-00
That's not a real hardware address.
2) You seem to be doing everything with wifi0 and nothing with wlan0.
I'm stating to think that wlan0 is actually the right name, especially
since I see more information show up for wlan0. What happens when you
use wlan0 for all your actions? Rename the ifcfg-wifi0 script to
ifcfg-wlan0 and see what happens. It may be that you are inadvertently
aliasing wifi0 to wlan0 and the system is getting confused.
Gus
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
