| Author |
Message |
|
|
Post subject: Another Wireless problem - Dell Laptop iwp3945
 Posted: Mar 07, 2007 - 04:38 PM
|
|
Joined: Dec 08, 2006
Posts: 242
Location: Deptford, NJ
Status: Offline
|
|
Hi Folks,
First I did the apt-get install ipw3945d firmware-ipw3945
When I try to bring up my card IFUP eth2 I get the following:
Plus it runs in a loop and pretty much brings my computer to a halt.
I have to stop the daemon in order to use the computer again.
Code:
Error for wireless request "Set Mode" (8B06) :
SET failed on device eth2 ; Invalid argument.
ioctl[SIOCSIWMODE]: Resource temporarily unavailable
Could not configure driver to use managed mode
ioctl[SIOCGIWRANGE]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 7 value 0x1 - ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWENCODEEXT]: Resource temporarily unavailable
ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Resource temporarily unavailable
The interface file looks like this:
Code:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
# automatically added when upgrading
auto lo
iface lo inet loopback
allow-hotplug eth0
iface eth0 inet dhcp
iface eth2 inet dhcp
wireless-mode Master
wireless-essid Joker
wpa-ssid Joker
wpa-psk xxxxxxxxxxxx
Any ideas?
Thanks
RR |
|
|
| |
|
|
|
 |
|
|
|
Post subject: RE: Another Wireless problem - Dell Laptop iwp3945
Posted: Mar 07, 2007 - 05:21 PM
|
|
Joined: Dec 02, 2006
Posts: 312
Location: Muppet Theater
Status: Offline
|
|
Mine looks like this-
Code:
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
# automatically added when upgrading
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
# interface for a hotel I stayed at
iface powell inet dhcp
wireless-mode Managed
wireless-essid Powel Street Hotel
# Interface for school
iface desk inet static
address 134.121.X.X
netmask 255.255.X.X
network 134.121.X.X
gateway 134.121.X.X
# Interace to hook up to whatever I can find
iface any inet dhcp
# Interface for wireless at home
iface home inet static
address 192.168.X.X
netmask 255.255.255.0
gateway 192.168.0.1
wireless-mode Managed
wireless-channel 3
wireless-essid Home
wpa-driver madwifi
wpa-ssid Home
wpa-passphrase somethinglong
wpa-key-mgmt WPA-PSK
iface slemp inet dhcp
wpa-driver madwifi
wpa-ssid slempnet
wpa-passphrase somethinglong
wpa-key-mgmt WPA-PSK
First, these were set up with kanotix a long time ago. I did have to add some of the wpa stuff by hand back when the arguments for wpa_supplicant changed. I assume you used the netcardconfig script that ships with sidux, right?
I would check to make sure that your wireless NIC is really eth2. The labeling I have seen goes eth0, eth1, then eth2. I bet you want eth1, OR there is some special name for the wireless based on how intel module works. For example, madwifi driver calls my wireless nic ath0, NOT eth1. Something similar may be happening to you.
I suspect you might need to change from 'master' to 'managed'. I also think the hot-plug line maybe getting you into trouble. Didn't slam or slh say in another post that hotplug was replaced by udev and that the two couldn't co-exist? |
_________________
Watch it!! I'm the beautiful assistant!
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Mar 08, 2007 - 02:03 AM
|
|
Joined: Dec 08, 2006
Posts: 242
Location: Deptford, NJ
Status: Offline
|
|
Hi UncleDeadley,
Yeah it worked... well it worked and then disconnected and then reconnected and continue that cycle until I stop the daemon.
I tried again later and it won't connect at all to the wireless router.
I added the wpa-key-mgmt WPA-PSK and changed it to managed to the interface file. When it connected the first time I was able to surf the internet (I unplugged the wired network). I also commented out the hot-plug thingy.
Now I am lost at what to try next.
Thanks
RR |
|
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Mar 08, 2007 - 05:01 PM
|
|
Joined: Dec 02, 2006
Posts: 312
Location: Muppet Theater
Status: Offline
|
|
| That sounds like the problem I had when I didn't have the all the wpa lines right and wpa_supplicant was unhappy, or when I am too far from the router. Are you really close to the router? Maybe the signal isn't very good where you were sitting? Have you tried replacing the line wpa-psk ********* with the one that I use: wpa-passphrase plaintextkey ? Also, have you tried using the netcardconfig tool in sidux? Also, are you sure that you know the right interface for the wireless nic (eth1 or 2)? |
_________________
Watch it!! I'm the beautiful assistant!
|
| |
|
|
|
|
|
|
|
Post subject:
Posted: Mar 08, 2007 - 06:14 PM
|
|
Joined: Nov 28, 2006
Posts: 4278
Status: Offline
|
|
| Or the channel you are using might be flooded. You can run the nice tool kismet to check the state of the wifi world around you, then select the channel with either no or the least traffic. That helps a lot, that's what I did with a very weak old router, I just found a channel nobody in my neighborhood uses. |
_________________
sidux Maintenance script: dist-upgrade, kernel install, general utilities: smxi
Backup script [using rdiff-backup]: rd-h2.sh
|
| |
|
|
|
|
|
|
