Bug 297616

Hi Jörg,
you likes to write long descriptions ;-)

paragraphs 1,2:
this is no supported until that module will be included (replaced ipw3945) in our distribution

par. 3:
yes, this is problem

par. 4:
configuration files based on MAC address are depricated now
that's why you should rename copyed file

NetworkModules.ycp:
this is no important

NetworkDevices.ycp:
yes, here is the problem

You wrote that you was able to write configuration for eth device
Can you try to use old ipw3945 if this works?

No I can't, because it seems that the old ipw3945 driver is no longer included with openSUSE. Although the firmware microcode image of ipw3945 is still included in the 'ipw-firmware' package in the 'Extra' repository. But I can't find a package that contains the ipw3945 kernel module.

Jirko, it seems that we are "between" drivers, right? ;-)

I installed iwlwifi driver, here is output from hwinfo --wlan:
20: PCI 300.0: 0282 WLAN controller
  [Created at pci.296]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4227
  Unique ID: 2nea.kj44mnK68N2
  Parent ID: qTvu.bQ30eTbcr+3
  SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 3945ABG Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4227 "PRO/Wireless 3945ABG Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1011
  Revision: 0x02
  Driver: "iwl3945"
  Driver Modules: "iwl3945"
  Device File: wmaster0
  Device Files: wmaster0, eth1
  Features: WLAN
  Memory Range: 0xedf00000-0xedf00fff (rw,non-prefetchable)
  IRQ: 21 (no events)
  HW Address: 00:18:de:64:b8:0d
  Module Alias: "pci:v00008086d00004227sv00008086sd00001011bc02sc80i00"
  Driver Info #0:
    Driver Status: iwl3945 is active
    Driver Activation Cmd: "modprobe iwl3945"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #5 (PCI bridge)


Steffen, I think this is bogus output:
  Device File: wmaster0
  Device Files: wmaster0, eth1

There should be:
  Device File: eth1
  Device Files: eth1, wmaster0

And this causes all problem. Can you fix it?

For my machine, no interface is shown at all. Apparently loading
iwl3945 is not enough. Joe?

I can see it only from ip (or in /sys/class/net) not in /sbin/ifconfig

For me, it's not even in /sys/class/net.

Loading iwl3945 is in fact not enough, you also require the firmware. And an Intel Wifi 4965 device, of course. The doubled "Device File(s)" output seems weird indeed, is it intended?

But the driver loads the firmware, nothing I have to worry about. Or not?

Ehm, comment 8 is wrong, of course you need an Intel 3945 device. The driver loads the firmware, correct. But Alpha7 packages do not match, you'll need the ucode package from stable.

I'm testing beta1.

Joachim, configuration file should be ifcfg-wmaster0 or ifcfg-eth1?

It should be ifcfg-wlan0. AFAIK you don't configure wmaster0 directly, but several wlanX devices which belong to wmaster0. I'll attach my ifcfg-wlan0 file which I created by hand and which is working fine here. 

In hwinfo (comment #4) there is no such device : wlan0

Created attachment 156410 [details]
ifcfg file of iwl3945 device

Now (after reboot) I'm really confused, hwinfo:

29: PCI 300.0: 0282 WLAN controller
  [Created at pci.296]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4227
  Unique ID: JNkJ.kj44mnK68N2
  Parent ID: qTvu.bQ30eTbcr+3
  SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 3945ABG Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4227 "PRO/Wireless 3945ABG Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1011
  Revision: 0x02
  Driver: "iwl3945"
  Driver Modules: "iwl3945"
  Device File: eth1
  Device Files: eth1, wlan0_rename
  Features: WLAN
  Memory Range: 0xedf00000-0xedf00fff (rw,non-prefetchable)
  IRQ: 21 (300508 events)
  HW Address: 00:18:de:64:b8:0d
  Module Alias: "pci:v00008086d00004227sv00008086sd00001011bc02sc80i00"
  Driver Info #0:
    Driver Status: iwl3945 is active
    Driver Activation Cmd: "modprobe iwl3945"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #14 (PCI bridge)


dmesg:
...
wmaster0: Selected rate control algorithm 'iwl-3945-rs'
wmaster0 renamed to eth1
udev: renamed network interface wmaster0 to eth1
wlan0 renamed to wlanxx0
...
wlanxx0 renamed to wlan0
wlan0 renamed to wlan0_rename

Here's the '# hwinfo --wlan' on my ThinkPad T60p:
20: PCI 300.0: 0282 WLAN controller
  [Created at pci.296]
  UDI: /org/freedesktop/Hal/devices/pci_8086_4227
  Unique ID: 2nea.xxxxxxxxxxx
  Parent ID: qTvu.bQ30eTbcr+3
  SysFS ID: /devices/pci0000:00/0000:00:1c.1/0000:03:00.0
  SysFS BusID: 0000:03:00.0
  Hardware Class: network
  Model: "Intel PRO/Wireless 3945ABG Network Connection"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4227 "PRO/Wireless 3945ABG Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x1011
  Revision: 0x02
  Driver: "iwl3945"
  Driver Modules: "iwl3945"
  Device File: wmaster0
  Device Files: wmaster0, wlan0
  Features: WLAN
  Memory Range: 0xedf00000-0xedf00fff (rw,non-prefetchable)
  IRQ: 17 (no events)
  HW Address: 00:11:22:33:44:55
  Link detected: yes
  Module Alias: "pci:v00008086d00004227sv00008086sd00001011bc02sc80i00"
  Driver Info #0:
    Driver Status: iwl3945 is active
    Driver Activation Cmd: "modprobe iwl3945"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #5 (PCI bridge)

of course, you have "Device Files: wmaster0, wlan0", that's why your config name is ifcfg-wlan0, I have "Device Files: wmaster0, eth1", my configuration is ifcfg-eth1
but YaST always uses "Device File" option - this is the main problem
and there is conflict between "Device File" and udev rules ;-(

Hm, I just upgraded to Beta1 which ships the iwlwifi driver within the iwlwifi-kmp-default package. I don't experience any udev conflicts here. There are also no 'renaming' messages in my dmesg output like you wrote in Comment #16.

The renaming issue appears with you had ipw3945 loaded on the machine before and you now are using iwl3945. The first registered an interface eth1, the second two interfaces wlan0 and wmaster0. As the device is already known to the system, the interface gets renamed to eth1 in that case. Shouldn't be a problem. You can also remove the related entries of /etc/udev/rules.d/77-network.rules to switch to the new naming.

What is status of this in Beta1?
I suppose that it's fixed now

The situation in Beta1 is even worse, at least on my system, hwinfo does not detect any WLAN card anymore (means, hwinfo --wlan showing exactly nothing, neither the internal 3945, nor a PCMCIA card). Steffen?

beta1 is really old, use hwinfo from STABLE

That works better, thanks. It still features the "Device File: wlan0" and "Device Files: wlan0, wmaster0" oddity, but maybe that's intended. But even with that hwinfo package, YaST does not offer to configure the iwl3945 device. And I noticed another bug while trying to adding the card manually: When clicking on "Add" in the main dialog, I can select "wireless" as device type, but the settings seems to be ignored. In the next dialog, the device type is still "ethernet", and the wireless dialog does not appear either.

yast2-network in Beta1 is old too ;-) - this is fixed in STABLE
buf if you want to upgrade id from STABLE, upgrade also yast2-core (changed bytecode)

I don't know what this STABLE tree is you're talking about, but I just upgrated to the latest FACTORY packages. I also use the driver from the iwlwifi-kmp-default package now instead of compiling it own my own.

YaST2-Network detects the device and allows to configure it, but as soon as I finish the configuration and return to the overview dialog, the iwl3945 device is shown as 'not configured' again. If I hit the Configure-Button again, all the changes I did in the previous step are lost. Ergo, YaST2 won't write the config at all.

If I create /etc/sysconfig/network/ifcfg-wlan0 manually and call YaST2-Network afterwards, it gets even stranger. Now YaST2 shows my WLAN device two times. One is shown as 'not configured' but with a MAC address. The other one is shown as 'configured' but as 'not connected' and has the device name 'wlan-wlan0'. I can make configuration changes to that device and it seems that they are written to /etc/sysconfig/network/ifcfg-wlan0 correctly.

*** Bug 301668 has been marked as a duplicate of this bug. ***

fixed and tested in yast2-network-2.15.65

Confirmed that! Works as expected after Factory update to yast2-network-2.15.67. Thanks!

*** Bug 307026 has been marked as a duplicate of this bug. ***