-   Linux - Wireless Networking (
-   -   Same Wireless Wireless Module Doesn't Work in Different Places-IBM Thinkpad T30 (

wkdude18 06-25-2008 06:46 PM

Same Wireless Wireless Module Doesn't Work in Different Places-IBM Thinkpad T30
I have a dual-boot computer Elive Gem 1.0 and Slackware 12.1. Wireless works perfectly in Elive, Slackware it does not. My network card is a Cisco Aironet MPI350 on an IBM Thinkpad T30.

on Elive the output of
ls -l device/driver/module in /sys/class/net/xxx for
eth0: e100 eth1: airo wifi0: no such file or directory

The active interface in Elive is eth1 according to network settings.

iwconfig reports that eth1 and wifi0 have wireless extensions, while lo, eth0, and irda0 have no wireless extensions.

Source Kernel edition in /usr/src is 2.6.18-elive (I doubt it is anything more than a 2.6.18 kernel, unless Elive's developer is also a kernel hacker)

In Slackware 12.1 the output of ls -l device/driver/module in /sys/class/net/xxx
for eth0: airo eth1:e100 wifi0: no such file or directory

Active interface in Slackware is supposed to be eth0, but I'm not sure since I have no connection.

iwconfig reports that eth0 and wifi0 have wireless settings while lo, irda0, and eth1 have no wireless settings.

Source kernel edition/version in /usr/src in Slackware is

My key is 10 charcters long so it is a WEP40, and the iwconfig output for eth1 in elive and eth0 in Slackware is the same.

Nonetheless, I am confused how in two different distros how two different interfaces could switch jobs and drivers. Is this a naming issue, or have they actually switched? I know in an Ubuntu live CD it calls my hard drive /dev/sda but in the GParted Live CD my hard drive is identified as /dev/hda. Do these discrepancies say anything about my problem? Should I try to switch the wireless extensions from eth0 to eth1 in Slackware? Is that even possible?

Greenfuse 06-29-2008 11:59 PM

It is interesting that your wireless device is named eth* ... I thought that naming was usually reserved for the ethernet interface.

You might want to check what the kernel is calling the wireless interface.

cat /proc/net/wireless

wkdude18 07-02-2008 05:54 PM

Sorry for misunderstanding
The computer is calling the wireless interface eth*.

Greenfuse 07-02-2008 07:11 PM

I had a look around and yes some setups will use eth*, sorry my ignorance.

To change the name given to a wireless interface, you can define it in /etc/modprobe.conf or /etc/modprobe.d/<drivername> (different distros might have a different setup)

For my ralink card it is

alias wlan0 rt61

I hope this helps

All times are GMT -5. The time now is 01:04 AM.