Hi
I am new to linux. I have installed fedora. I see two network cards under network devices. One is the onboard eth0 and the other eth1 Prism 2 chipset ,type wireless.But I can not get the wireless to activate. I have been surffing and reading for a few days now. I have even installed fedora a few times. I would appreciate all the help you can provide in solving this issue.

Thanks

Hello slimlcd101,

This sounds annoying. Let's hope we can help you out. As a starter, please post the outputs from the following commands, as run from a root terminal:

ifup eth1

ifconfig eth1

iwconfig eth1

dmesg | grep eth1

tharfagreinir

Thanks for quick response. I am installing a fresh copy of fedora just incase I screwed somthing up. I will post the info as you requested a.s.a.p.

Sean

tharfagreinir

I am using Fedora core ... kernel 2.4.22-1.2199.nptl

network configuration

Error for wireless request "Set Mode" (8B06) :
SET failed on device eth1 ; Invalid argument.
Error for wireless request "Set Frequency" (8B04) :
SET failed on device eth1 ; Operation not supported.

Determining IP information for eth1...


***************************
[root@localhost root]# ifup eth1
/sbin/ifup: configuration for eth1 not found.
Usage: ifup <device name>
[root@localhost root]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:20:E0:8A:8D:54
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:2376 (2.3 Kb)
Interrupt:11 Base address:0xd000 Memory:ec000000-ec000fff

[root@localhost root]# iwconfig eth1
eth1 IEEE 802.11-DS ESSID:"linksys_SES_46437" Nickname:"localhost.localdomain"
Mode:Managed Frequency:2.437GHz Access Point: 00:13:10:2B:6B:6F
Bit Rate=11Mb/s Tx-Power=15 dBm Sensitivity:1/3
Retry min limit:8 RTS thrff Fragment thrff
Encryption key:4144-4132-4431-3844-3245-0000-00 Security modepen
Power Managementff
Link Quality:84/92 Signal level:-18 dBm Noise level:-148 dBm
Rx invalid nwid:0 Rx invalid crypt:196 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

[root@localhost root]# dmesg | grep eth1
divert: allocating divert_blk for eth1
eth1: Station identity 001f:0003:0001:0003
eth1: Looks like an Intersil firmware version 1.3.3
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:20:E0:8A:8D:54
eth1: Station name "Prism I"
eth1: ready
divert: freeing divert_blk for eth1
divert: allocating divert_blk for eth1
eth1: Station identity 001f:0003:0001:0003
eth1: Looks like an Intersil firmware version 1.3.3
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:20:E0:8A:8D:54
eth1: Station name "Prism I"
eth1: ready
divert: freeing divert_blk for eth1
divert: allocating divert_blk for eth1
eth1: Station identity 001f:0003:0001:0003
eth1: Looks like an Intersil firmware version 1.3.3
eth1: Ad-hoc demo mode supported
eth1: IEEE standard IBSS ad-hoc mode supported
eth1: WEP supported, 104-bit key
eth1: MAC address 00:20:E0:8A:8D:54
eth1: Station name "Prism I"
eth1: ready
eth1: Error -110 setting multicast list.
eth1: Error -110 setting multicast list.
eth1: Error -110 setting multicast list.
eth1: New link status: Connected (0001)


Thanks for the help

This all looks right, except for the '/sbin/ifup: configuration for eth1 not found' part. Looks to me like the configuration file for the eth1 interface is missing. Since you are using Fedora, try running the Network Configuration tool (KDE Menu: System Settings -> Network) and configure eth1 there, then save it. This will create the configuration file for eth1.

I tried that. but I get this when I try to activate it:

[root@localhost root]# ifup eth1
/sbin/ifup: configuration for eth1 not found.
Usage: ifup <device name>

Okay ... this does look pretty weird. Let's see the output from

ls /etc/sysconfig/networking/devices/

and

cat /etc/sysconfig/networking/devices/ifcfg-eth1

here you go:

[root@localhost root]# ls /etc/sysconfig/networking/devices
ifcfg-eth0 ifcfg-eth1 keys-eth1
[root@localhost root]# cat /etc/sysconfig/networking/devices/ifcfg-eth1
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
ONBOOT=no
USERCTL=no
PEERDNS=yes
GATEWAY=
TYPE=Wireless
DHCP_HOSTNAME=
IPADDR=
DEVICE=eth1
HWADDR=00:20:e0:8a:8d:54
BOOTPROTO=dhcp
DOMAIN=
NETMASK=
ESSID=
CHANNEL=6
MODE=Auto
RATE=11Mb/s
[root@localhost root]#


Thanks for helping me
Sean

No problem ...

It seems you have the configuration file in place, so I have no idea what's up with the 'configuration file for eth1 not found' message. But I need notice, while going over the output for iwconfig eth1, the following: 'Rx invalid crypt:196' ... this seems to point to a problem with the WEP key. Also, your WEP key seems pretty long, and looks like a hex representation of a string ... it might be that you are entering the key as a string in the Network Configuration application, rather than a hex sequence. Try putting 0x in front of the key when you enter it there, and see what happens.

Sorry I need to ask. How do get to the place so I can do that . I have done it before but don't seem to remmebrt. Its not in network configuration.

It should be in Network Configuration, if you select eth1 from the list and click Edit. There should be a tab called Wireless Settings.

Failing that, you could just do

iwconfig eth1 key [YOUR KEY]

in a root terminal.

Got it,
but still no cigar my friend;

Error for wireless request "Set Mode" (8B06) :
SET failed on device eth1 ; Device or resource busy.
Error for wireless request "Set Bit Rate" (8B20) :
SET failed on device eth1 ; Device or resource busy.
Error for wireless request "Set Encode" (8B2A) :
SET failed on device eth1 ; Device or resource busy.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device eth1 ; Device or resource busy.

Determining IP information for eth1...

Wow - this is really getting weird. Do these messages occur even after a reboot? I've known this to occur before. Any others on this forum familiar with this?

Hi,

Yes they do.

I can help but to think its something that I am missing or just overlooked. I installed Fedora updated it and thats all.
Is there anything else needs to be done for the wireless to work? Also, why is it that the device shows up as eth1 shouldn't it be something like wlanX?

Thanks again for all your help and input.

Sean

A wise man once told me that %90 of the time the solution to the problem is between the chair and the keyboard as I am embarrassed to admit is the case here. I am not sure if I did anything else to rectify this problem but I now know what I did wrong. My only excuse is that I am a newbie so I say to anyone that spent time trying to solve this issue “I am sorry “for wasting your time.

Tharfagreinir, You were right when you suggested :


It might be that you are entering the key as a string in the Network Configuration application, rather than a hex sequence. Try putting 0x in front of the key when you enter it there……


I bet you already know what I did wrong…. Yes I was putting O instead of ZERO (0) oops MY BAD.

What a strange error message though, why could it not just say invalid WEP KEY?
Please don’t let this stop you from helping me in the future because I have a feeling I will be begging for help with other issues soon.


THANKS for all your help