Wireless no longer working

Paolo Galtieri pgaltieri at gmail.com
Wed Jul 30 01:47:56 UTC 2008


Since the latest updates to F9 my wireless no longer works.  This seems to
be a common theme.  Anyway the following messages appear in
/var/log/messages and I'm curious as to what they mean

Jul 29 18:07:42 localhost kernel: iwl3945: No space for Tx
Jul 29 18:07:42 localhost kernel: iwl3945: Error sending REPLY_LEDS_CMD:
iwl3945_enqueue_hcmd failed: -28
Jul 29 18:07:42 localhost kernel: iwl3945: No space for Tx
Jul 29 18:07:42 localhost kernel: iwl3945: Error sending REPLY_LEDS_CMD:
iwl3945_enqueue_hcmd failed: -28
Jul 29 18:07:42 localhost kernel: iwl3945: No space for Tx
Jul 29 18:07:42 localhost kernel: iwl3945: Error sending REPLY_LEDS_CMD:
iwl3945_enqueue_hcmd failed: -28
Jul 29 18:08:42 localhost kernel: iwl3945: No space for Tx
Jul 29 18:08:42 localhost kernel: iwl3945: Error sending REPLY_LEDS_CMD:
iwl3945_enqueue_hcmd failed: -28
Jul 29 18:08:42 localhost kernel: iwl3945: No space for Tx
Jul 29 18:08:42 localhost kernel: iwl3945: Error sending REPLY_LEDS_CMD:
iwl3945_enqueue_hcmd failed: -28

They occur regularly, probable due to NM managing the device.  When I try to
start it via ifup wlan0 it fails.

My wireless dhcp server showst the following messages:

WLAN client: 00:1B:77:17:F4:7C, associated to wlan network
WLAN client: 00:1b:77:17:f4:7C, disconnected from wlan network. Initiator:
client. Reason: Leaving the ESS

The client side shows

Jul 29 18:25:45 localhost dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255port 67 interval 15
Jul 29 18:26:00 localhost dhclient: DHCPDISCOVER on wlan0 to
255.255.255.255port 67 interval 10
Jul 29 18:26:10 localhost dhclient: No DHCPOFFERS received.



I also have several related questions:

 1) Why does NM even try to do something with the wireless device when it is
not marked to be activated on boot?  I don't need to be active on both the
wired and wireless interfaces at the same time :)

 2) Why are the activate and deactivate buttons greyed out when I start
system-config-network?  This the case for both the wired and wireless
interfaces.

The only way to start the wireless (and have it fail) is to do ifup wlan0.

 3) I have both wired and wireless interfaces.  The system is normally
connected via the wired and gets its address via dhcp from my server.  One
of the pieces of information provided by my dhcp server and received by NM
is the host name

Jul 27 12:10:44 localhost dhclient: DHCPREQUEST on eth0 to 10.0.0.70 port 67
Jul 27 12:10:44 localhost dhclient: DHCPACK from 10.0.0.70
Jul 27 12:10:44 localhost dhclient: bound to 10.0.0.4 -- renewal in 2975
seconds.
Jul 27 12:10:44 localhost NetworkManager: <info>  DHCP: device eth0 state
changed bound -> renew
Jul 27 12:10:44 localhost NetworkManager: <info>    address 10.0.0.4
Jul 27 12:10:44 localhost NetworkManager: <info>    netmask 255.255.255.0
Jul 27 12:10:44 localhost NetworkManager: <info>    gateway 10.0.0.100
Jul 27 12:10:44 localhost NetworkManager: <info>    hostname 'peglaptop10'
Jul 27 12:10:44 localhost NetworkManager: <info>    nameserver '68.2.16.25'
Jul 27 12:10:44 localhost NetworkManager: <info>    domain name 'homenet10'
Jul 27 12:10:45 localhost NetworkManager: <info>  Policy set (eth0) as
default device for routing and DNS.

Yet when I login after booting the system the host name is set to
localhost.  Even if I set the hostname to peglaptop10 using

hostname peglaptop10

the next time I reboot the host name is back to localhost.

 4) How do I fix the following selinux problem which occurs when I do

ifdown eth0

rm: cannot remove `/etc/resolv.conf.predhclient.eth0': Permission denied

I get an alert from selinux which I have attached.  Also when I restart the
interface

ifup eth0

I get the following even though the interface comes up.

[root at localhost opt]# ifup eth0

Determining IP information for eth0...dhclient(21974) is already running -
exiting.

This version of ISC DHCP is based on the release available
on ftp.isc.org.  Features have been added and other changes
have been made to the base software release in order to make
it work better with this distribution.

Please report for this software via the Red Hat Bugzilla site:
    http://bugzilla.redhat.com

exiting.
 failed.

And BTW dhclient is not running after I do the ifdown.  I assume this is
related to NM managing the interface.


Any thoughts and assistance are appreciated.

Thanks.
Paolo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20080729/fcfce8be/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: A
Type: application/octet-stream
Size: 3596 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/fedora-list/attachments/20080729/fcfce8be/attachment-0001.obj>


More information about the fedora-list mailing list