Bug 4557 - 2_b2 wireless network interface only found when removing driver before shutdown and reinstalling it again upon boot (ipw2200)
Summary: 2_b2 wireless network interface only found when removing driver before shutdo...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 2120 5015
  Show dependency treegraph
 
Reported: 2012-02-17 10:51 CET by Marja Van Waes
Modified: 2015-06-26 12:34 CEST (History)
4 users (show)

See Also:
Source RPM: udev-181
CVE:
Status comment:


Attachments
updates after which wireless failed (37.51 KB, text/plain)
2012-02-17 10:53 CET, Marja Van Waes
Details
updates before 1st time this bug appeared (113.77 KB, text/plain)
2012-02-19 08:31 CET, Marja Van Waes
Details
systemctl -a when wireless won't function (20.30 KB, text/plain)
2012-02-19 12:11 CET, Marja Van Waes
Details
end of /var/log/messages (66.15 KB, text/plain)
2012-03-24 10:13 CET, Marja Van Waes
Details

Description Marja Van Waes 2012-02-17 10:51:01 CET
The first time this occurred was a week ago with Mageia 2 a 3, after a lot of updates wireless seemed dead. Trying to reconfigure the card in MCC gave:

Unable to find network interface for selected device (using ipw2200 driver)

Just now, after installing pre-beta1, I was able to configure and start wireless nicely. After installing some updates and rebooting, wireless was dead again with the same error message in MCC

I'll attach the relevant part of lspcidrake -v and the list of updates later, I'm using another system now
Comment 1 Marja Van Waes 2012-02-17 10:53:30 CET
Created attachment 1582 [details]
updates after which wireless failed

relevant line of lspcidrake -v output:

ipw2200         : Intel Corporation|PRO/Wireless 2200BG [Calexico2] Network Connection [NETWORK_OTHER] (vendor:8086 device:4220 subv:8086 subd:2712) (rev: 05)
Comment 2 Marja Van Waes 2012-02-17 11:31:12 CET
the driver worked, and there was no new kernel

@ Colin

can you think of a cause?

CC: (none) => mageia

Comment 3 Marja Van Waes 2012-02-18 21:05:49 CET
After installing the 2nd pre-release beta, I made sure I had all updates and had rebooted, before configuring my wireless card.

The same thing happened: after getting it to work and rebooting, it was dead again.

So it hasn't got anything to do with the very last updates.

This caused me to find out that removing ipw2200-firmware and rebooting the laptop and then adding the ipw2200-firmware again, makes the wireless card work again :)

I'm only afraid I'll have to keep removing the firmware every time before shutting down and reinstall upon reboot :(

@ Colin

Can this have anything to do with any service that should have been started? Is there anything I can check?

Summary: 2a3 and pre 2b1 Unable to find network interface for selected device (using ipw2200 driver) => 2a3 and pre 2b1 wireless only keeps working when removing driver before shutdown and reinstalling it again upon boot (ipw2200)

Comment 4 Marja Van Waes 2012-02-18 21:16:00 CET
Comment on attachment 1582 [details]
updates after which wireless failed

Those updates have nothing to do with the bug

Attachment 1582 is obsolete: 0 => 1

Comment 5 Marja Van Waes 2012-02-19 08:31:52 CET
Created attachment 1592 [details]
updates before 1st time this bug appeared

now attaching the correct updates after which this problem started

(I saw it at second (re)boot after the updates, but don't remember now whether I didn't need wireless after first (re)boot or whether it still worked, then)

the updates contain, among a lot of others:

kernel-desktop-3.2.5-1.mga2    1            1.mga2        i586    
kernel-desktop-latest          3.2.5        1.mga2        i586   

systemd                        40           2.mga2        i586    
systemd-sysvinit               40           2.mga2        i586    
systemd-units                  40           2.mga2        i586    
udev                           180          1.mga2        i586
Marja Van Waes 2012-02-19 08:33:44 CET

CC: (none) => lists.jjorge, tmb

Comment 6 Marja Van Waes 2012-02-19 09:02:06 CET
@ Colin

I just saw you don't receive a mail about this bug, even though you're in the cc.

So assigning this to systemd and to you, so you'll read it :þ

please tell me how to find out systemd isn't the culprit

CC: (none) => dmorganec
Assignee: bugsquad => mageia
Source RPM: (none) => systemd

Comment 7 Marja Van Waes 2012-02-19 12:11:13 CET
Created attachment 1593 [details]
systemctl -a when wireless won't function

only difference between "systemctl -a" after reinstalling driver and starting wireless again, and "systemctl -a" after having rebooted and seeing wireless is dead, is that this line has disappeared:

sys-devi...et-eth1.device loaded active   plugged       PRO/Wireless 2200BG [Calexico2] Network Connection

so not changed to error, inactive, dead or whatever, just completely gone

attaching output for when wireless doesn't work
Marja Van Waes 2012-02-19 12:20:35 CET

Blocks: (none) => 2120
Source RPM: systemd => systemd-40-3.mga2

Comment 8 Marja Van Waes 2012-03-08 08:37:35 CET
@ Colin

I spent quite some time searching how to "systemctl <start my wireless card service>", but didn't find out.

Is it possible to start a service that is not listed when you do systemctl -a ?

If so, please tell me how start it!
Comment 9 Colin Guthrie 2012-03-08 11:01:40 CET
@ Marja. Sorry for the delay. You should poke me harder - especially if it's an issue you are personally having - you get special attention :)

Anyway, I don't see NetworkManager listed there. I'd generally recommend NetworkManager these days. I have far better luck with it than the native stuff.

Firstly, make sure it's installed and enabled. systemctl status NetworkManager.service should tell you if it's enabled or not:

NetworkManager.service - Network Manager
	  Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
	  Active: active (running) since Thu, 08 Mar 2012 02:12:49 +0000; 7h ago
	Main PID: 1735 (NetworkManager)
	  CGroup: name=systemd:/system/NetworkManager.service
		  â  1735 /usr/sbin/NetworkManager --no-daemon
		  â 15545 /sbin/dhclient -d -4 -sf /usr/lib64/nm-dhcp-client.action -pf /var/run/dhclient-wlan0.pid -lf /...


If it's not installed or enabled, just install and enable it :)

You need to make sure your network interfaces are then managed by network manager. There is a ticky box in draknetcenter to do this.

Then hopefully things will work better for you :)
Comment 10 Marja Van Waes 2012-03-10 13:26:05 CET
Thanks, Colin :)

Network Manager wasn't installed because it gave a lot of problems in Mageia 1, very often it wasn't possible to get a wireless connection without trying (including rebooting) again and again. 
We don't have a maintainer for the package :(

It is now installed:

[marja@denkblok ~]$ systemctl status NetworkManager.service
NetworkManager.service - Network Manager
          Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled)
          Active: active (running) since Sat, 10 Mar 2012 11:43:35 +0100; 12min ago
        Main PID: 529 (NetworkManager)
          CGroup: name=systemd:/system/NetworkManager.service
                  â 529 /usr/sbin/NetworkManager --no-daemon
                  â 726 /sbin/dhclient -d -4 -sf /usr/lib/nm-dhcp-client.action -pf /var/run/dhclient-eth...

[marja@denkblok ~]$ 

And right after installing ipw2200 the network comes up, but the connection fails.
After reboot, NetworkManager.service runs again, but I get the same message as before:

Unable to find network interface for selected device (using ipw2200 driver)

However I can't check whether the "Allow interface to be controlled by NetworkManager" box is still ticked (it should be, of course)
Comment 11 Colin Guthrie 2012-03-10 16:18:46 CET
(In reply to comment #10)
> However I can't check whether the "Allow interface to be controlled by
> NetworkManager" box is still ticked (it should be, of course)

Why can't you check this? Does the interface not show up in draknetcenter? It should be an option right at the bottom of the screen that shows up when you click "Configure" against the interface. I'd advise doing that for both eth0 and wlan0.

If the option just doesn't show up for you (or draknetcetner is otherwise busted), just edit the file /etc/sysconfig/network-scripts/ifcfg-wlan0 and make sure the following two lines are in it:

NM_CONTROLLED=yes
USE_NM=true

Not sure why (or even if) both are needed but I have them and all is well for me.

HTHs
Comment 12 Marja Van Waes 2012-03-10 17:45:40 CET
(In reply to comment #11)
> (In reply to comment #10)
> > However I can't check whether the "Allow interface to be controlled by
> > NetworkManager" box is still ticked (it should be, of course)
> 
> Why can't you check this? Does the interface not show up in draknetcenter? It
> should be an option right at the bottom of the screen that shows up when you
> click "Configure" against the interface. I'd advise doing that for both eth0
> and wlan0.
> 
Because when I click on the configure button, I get the error message about the missing network interface

> If the option just doesn't show up for you (or draknetcetner is otherwise
> busted), just edit the file /etc/sysconfig/network-scripts/ifcfg-wlan0 and make
> sure the following two lines are in it:
> 
> NM_CONTROLLED=yes
> USE_NM=true
> 
I didn't have that file yet, or it was empty, so I pasted the missing line in 
/etc/sysconfig/network-scripts/ifcfg-eth1 and then copied that file to /etc/sysconfig/network-scripts/ifcfg-wlan0

It still doesn't work, though

My ethernet card is eth0 and my wlan card is eth1, should the latter be wlan0?

Feel free to reassign if this hasn't got anything to do with systemd, you'll be having enough systemd related things to do :)
Marja Van Waes 2012-03-18 20:08:38 CET

Blocks: (none) => 5015

Comment 13 Marja Van Waes 2012-03-20 08:29:56 CET
After a fresh Mga2b2 network install, without networkmanager (because networkmanager didn't solve anything for me):
 
* the WPA 4-way handshake fails (and keeps failing, despite entering my password over and over again) I think there is a bug report for this issue 
* after reboot and selecting Wireless in MCC I get the old error message again about the not found net work interface
* and of course, I have bug 4942, too
Marja Van Waes 2012-03-20 08:33:01 CET

Summary: 2a3 and pre 2b1 wireless only keeps working when removing driver before shutdown and reinstalling it again upon boot (ipw2200) => 2_b2 wireless network interface only found when removing driver before shutdown and reinstalling it again upon boot (ipw2200)

Comment 14 Marja Van Waes 2012-03-21 14:38:39 CET
(In reply to comment #13)
> After a fresh Mga2b2 network install, without networkmanager (because
> networkmanager didn't solve anything for me):
> 
> * the WPA 4-way handshake fails (and keeps failing, despite entering my
> password over and over again) I think there is a bug report for this issue
Maybe bug 3344, because sometimes I get the error message that is in the summary of that bug 
> * after reboot and selecting Wireless in MCC I get the old error message again
> about the not found net work interface

In spite of bug 3344, I finally got wireless to work again after fresh install of ipw2200 and before reboot.

After reboot:

[root@localhost marja]# ifup eth1
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] ipw2200 device eth1 does not seem to be present, delaying initialization.
[root@localhost marja]# ifup eth1 boot
ERROR    : [/etc/sysconfig/network-scripts/ifup-eth] ipw2200 device eth1 does not seem to be present, delaying initialization.
[root@localhost marja]# lspcidrake -v | grep ipw2200
ipw2200         : Intel Corporation|PRO/Wireless 2200BG [Calexico2] Network Connection [NETWORK_OTHER] (vendor:8086 device:4220 subv:8086 subd:2712) (rev: 05)

This is exactly the same output as I get when ipw2200-firmware isn't installed 
at all.

For the record, the same card works flawlessly when I use my Mageia 1 partition.

CC'ing zézinho, although his package can't be the culprit


POKING COLLIN (is this hard enough? :þ)
Comment 15 Colin Guthrie 2012-03-23 19:31:42 CET
Hmm, I'm not sure what's going on here I'm afraid :(

What does /etc/sysconfig/network-scripts/ifcfg-eth1 say and what is the contents of both /etc/iftab and /etc/udev/rules.d/70-persistent-net.rules

I ask these questions but I'm really not sure where to look from here.
Comment 16 Marja Van Waes 2012-03-23 21:17:22 CET
(In reply to comment #15)
> Hmm, I'm not sure what's going on here I'm afraid :(
> 
> What does /etc/sysconfig/network-scripts/ifcfg-eth1 say

WLAN working, before reboot: the file is empty
after reboot, WLAN dead: the file is empty

> and what is the
> contents of both /etc/iftab

WLAN working, before reboot: only the *eth0* mac address
after reboot, WLAN dead: only the eth0 mac address

> and /etc/udev/rules.d/70-persistent-net.rules

apart from a line for eth0, it says, both when WLAN works and when it's dead:
# PCI device 0x8086:/sys/devices/pci0000:00/0000:00:1e.0/0000:02:02.0 (ipw2200)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:ce:cf:6f:09", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"


> 
> I ask these questions but I'm really not sure where to look from here.

No problem, I thought systemd was a nice scapegoat, but I'm not sure it is a systemd bug ;)

The updates after which this bug appeared, contained a kernel update, too


@ tmb

Is there a chance that since kernel-desktop-3.2.5-1.mga2 the kernel refuses to do something during boot up and that that causes my wireless to be dead?
Comment 17 D Morgan 2012-03-24 02:51:47 CET
i had this here, it got fixed by installing the ucode rpms 

$ rpm -qa | grep ucode
iwlwifi-3945-ucode-15.32.2.9-2.mga1
iwlwifi-5000-ucode-8.83.5.1-2.mga1

i don't know which one is the good but intalling them and then rebooting fixed the pb and the wifi is now working.
Comment 18 José Jorge 2012-03-24 09:06:45 CET
(In reply to comment #17)
> i had this here, it got fixed by installing the ucode rpms 
> 
> $ rpm -qa | grep ucode
> iwlwifi-3945-ucode-15.32.2.9-2.mga1
> iwlwifi-5000-ucode-8.83.5.1-2.mga1
> 

I had a ipw2200, I am sure this firmwares are not used by it.
Maybe a dmesg could help understanding what driver is taking on the hardware.
Comment 19 Marja Van Waes 2012-03-24 09:13:01 CET
(In reply to comment #17)
> i had this here, it got fixed by installing the ucode rpms 
> 
> $ rpm -qa | grep ucode
> iwlwifi-3945-ucode-15.32.2.9-2.mga1
> iwlwifi-5000-ucode-8.83.5.1-2.mga1
> 
> i don't know which one is the good but installing them and then rebooting fixed
> the pb and the wifi is now working.

Although that doesn't solve it for me (yet), it might lead to the cause :)

I just saw the same issue exists in Mdv cauldron
http://mandriva.598463.n5.nabble.com/Cooker-UNABLE-TO-FIND-NETWORK-INTERFACE-FOR-SELECTED-DEVICE-ipw2200-driver-td5539055.html
Comment 20 Marja Van Waes 2012-03-24 09:15:30 CET
s/cauldron/cooker/
Comment 21 Marja Van Waes 2012-03-24 09:43:12 CET
(In reply to comment #18)
> (In reply to comment #17)
> > i had this here, it got fixed by installing the ucode rpms 
> > 
> > $ rpm -qa | grep ucode
> > iwlwifi-3945-ucode-15.32.2.9-2.mga1
> > iwlwifi-5000-ucode-8.83.5.1-2.mga1
> > 
> 
> I had a ipw2200, I am sure this firmwares are not used by it.
> Maybe a dmesg could help understanding what driver is taking on the hardware.

My WLAN is working atm (installed ipw2200 and before reboot), current dmesg only contains nothing but
[  *.*] [drm:intel_prepare_page_flip] *ERROR* Prepared flip multiple times
Comment 22 Marja Van Waes 2012-03-24 10:13:55 CET
Created attachment 1834 [details]
end of /var/log/messages

The attached file contains a copy from var/log/messages, starting with when I boot without ipw2200-firmware installed, then installing it and getting a working connection. After rebooting and seeing there is no connection, it ends
Marja Van Waes 2012-03-24 10:14:48 CET

Attachment 1834 description: end of var/log/messages => end of /var/log/messages

Comment 23 Colin Guthrie 2012-03-24 16:24:55 CET
OK, just to document this issue a little:

 1. The intel_prepare_page_flip error appears to be the result of a bogus alias entry in /etc/modprobe.conf. Removing it seemed to fix that particular problem.
 2. The wider problem relates to fireware loading with recent udev + libkmod.

Here is some info:
http://www.spinics.net/lists/linux-wireless/msg83448.html

At present, our udev uses libkmod to load modules but our modprobe is from module-init-tools.

So fundamentally, the first time this module is loaded (without relevant firmware in place) it will fail. Simply issuing an "rmmod ipw2200; modprobe ipw2200" will cause it to magically work again.

Even using kmod here as replacements for rmmod and modprobe is fine as the firmware is already loaded (at least I think that's why).

I need to check with Kay Sievers and/or Tom Gundersen who probably have a better understanding of this issue than me.

I was told that Fedora are working around this for now with kernel fixes (whether this is a generic fix that allows udev to work or something specific to individual modules I don't know).

Thomas you might be able to see something in fedora kernel (I couldn't spot anything obvious), but don't look too hard. I'll try and grab Kay or Tom when I can.

Source RPM: systemd-40-3.mga2 => udev-181

Comment 24 Colin Guthrie 2012-03-24 20:26:05 CET
OK, this is fixed in the latest udev :)

Thanks for the help debugging Marja!

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 25 Colin Guthrie 2015-06-25 09:27:58 CEST
Can people affected by this bug, please keep an eye open in latest cauldron? I've removed the patch we restored to work around this, but kernel firmware loading has changed a lot since then and I think it really is no longer needed. If there is an issue, please open a new bug and reference this one! Thanks!
Comment 26 Marja Van Waes 2015-06-26 10:24:45 CEST
Hi Colin,

Thanks a lot for remembering this bug and asking!

In a never updated Mageia5 cauldron, started June 18 2015, I installed the packages you pushed yesterday and the day before. With dependencies, that gave: 


  chkconfig                      1.5          2.mga6        i586    
  elfutils                       0.160        4.mga5        i586    
  libgudev1.0_0                  230          1.mga6        i586    
  libqrencode3                   3.4.4        3.mga5        i586    
  libxkbcommon0                  0.5.0        1.mga6        i586    
  systemd                        221          2.mga6        i586    
  systemd-units                  221          2.mga6        i586

after reboot, wlan still works fine 

[marja@localhost ~]$ lspcidrake -v | grep ireless
ipw2200         : Intel Corporation|PRO/Wireless 2200BG [Calexico2] Network Connection [NETWORK_OTHER] (vendor:8086 device:4220 subv:8086 subd:2712) (rev: 05)
[marja@localhost ~]$
Comment 27 Colin Guthrie 2015-06-26 12:34:21 CEST
(In reply to Marja van Waes from comment #26)
> Thanks a lot for remembering this bug and asking!

svn log and properly referenced commits mean that I didn't need to remember :D

Thanks for looking and keep an eye open should anything crop up.

Cheers!

Note You need to log in before you can comment on or make changes to this bug.