610517 – ipw-firmware didn't get installed although hardware requires it

Bug 610517 - ipw-firmware didn't get installed although hardware requires it

Summary: ipw-firmware didn't get installed although hardware requires it

Status:	RESOLVED DUPLICATE of bug 591703

Alias:	None

Product:	openSUSE 11.3
Classification:	openSUSE
Component:	Installation (show other bugs)
Version:	Milestone 7
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Michal Zugec
QA Contact:	Jiri Srain

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2010-06-01 07:18 UTC by Stefan Assmann
Modified:	2010-06-01 19:52 UTC (History)
CC List:	0 users

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

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

Description Stefan Assmann 2010-06-01 07:18:29 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.4) Gecko/20100513 SUSE/3.6.4-1.11 Firefox/3.6.4

ipw-firmware-9-2.6.noarch didn't get installed but is required for 
03:07.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)

Had to install it manually.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1 Jozef Uhliarik 2010-06-01 11:55:12 UTC

Miso I am not sure if yast2-network solves also installation of correct RPMs for network devices. Could you check it please?

Comment 2 Michal Zugec 2010-06-01 12:28:54 UTC

What's your driver (see hwinfo --netcard)?
In YaST, there's following firmware database:


map <string, string> request_firmware = $[
        "atmel_pci" : "atmel-firmware",
        "atmel_cs"  : "atmel-firmware",
        "at76_usb"  : "atmel-firmware",
        "ipw2100" : "ipw-firmware",
        "ipw2200" : "ipw-firmware",
        "ipw3945" : "ipw-firmware",
        "iwl3945" : "iwl3945-ucode",
        "iwl4965" : "iwl4965-ucode",
        "b43"     : "b43-fwcutter",
        "b43-pci-bridge" : "b43-fwcutter",
        "rt73usb" : "ralink-firmware",
        "rt61pci" : "ralink-firmware",
        "bcm43xx" : "",
        "prism54" : "",
        "spectrum_cs" : "",
        "zd1201" : "",
        "zd1211rw" : "",
        "acx" : "",
        "rt73usb" : "",
        "prism54usb":""
    ];

Comment 3 Stefan Assmann 2010-06-01 13:19:34 UTC

Hi Michal,

here's the output

24: PCI 307.0: 0282 WLAN controller
  [Created at pci.318]
  Unique ID: JNkJ.xOYEqLAmyc9
  Parent ID: 6NW+.InKz0bgid89
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:07.0
  SysFS BusID: 0000:03:07.0
  Hardware Class: network
  Model: "Intel Samsung P35 integrated WLAN"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x4220 "PRO/Wireless 2200BG [Calexico2] Network Connection"
  SubVendor: pci 0x8086 "Intel Corporation"
  SubDevice: pci 0x2731 "Samsung P35 integrated WLAN"
  Revision: 0x05
  Driver: "ipw2200"
  Driver Modules: "ipw2200"
  Device File: eth1
  Features: WLAN
  Memory Range: 0xc8010000-0xc8010fff (rw,non-prefetchable)
  IRQ: 20 (275834 events)
  HW Address: 00:15:00:3a:bb:53
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472
  WLAN bitrates: 1 2 5.5 11 6 9 12 18 24 36 48 54
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Requires: ipw-firmware
  Module Alias: "pci:v00008086d00004220sv00008086sd00002731bc02sc80i00"
  Driver Info #0:
    Driver Status: ipw2200 is active
    Driver Activation Cmd: "modprobe ipw2200"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #16 (PCI bridge)

Comment 4 Michal Zugec 2010-06-01 14:05:37 UTC

That means when you configure this wlan via YaST it didn't ask you for installing required package?

Comment 5 Stefan Assmann 2010-06-01 14:18:47 UTC

The ipw firmware package used to get installed during the base installation by some hw detection, no interaction necessary. Now the package doesn't get installed so no interface to configure with YaST in the first place.

Comment 6 Katarina Machalkova 2010-06-01 19:52:09 UTC

Next victim, hwinfo was temporarily unable to detect installation on a laptop thus relevant patterns didn't get selected

*** This bug has been marked as a duplicate of bug 591703 ***