Bug 608966 - Thinkpad X60 and iwl3945-ucode
Summary: Thinkpad X60 and iwl3945-ucode
Status: RESOLVED DUPLICATE of bug 591703
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Factory
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-26 09:42 UTC by Karl Eichwalder
Modified: 2010-05-27 19:33 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Eichwalder 2010-05-26 09:42:53 UTC
From: Karl Eichwalder <ke@suse.de>
Subject: Re: [opensuse-factory] Thinkpad X60 and iwl3945-ucode
To: opensuse-factory@opensuse.org
Date: Wed, 26 May 2010 11:29:45 +0200

Martin Schlander <martin.schlander@gmail.com> writes:

> The iwl3945 ucode seems to be in the 'kernel-firmware' package as it should be 
> on my M7.

I installed the Gnome desktop (and later the KDE4 pattern), but
kernel-firmware were not installed by default.

> If your suggested workflow were indeed to be required to get one of the most 
> widely used chipset working, then we might as well shut down. At least it 
> would set a new benchmark for epic fail.

Later on, NetworkManager displayed "device not ready" and nothing more.

Then, I switch to the traditional networking method and tried to
configure the wireless hardware.  YaST tried to download iwl3945-ucode,
but failed.  Maybe, kernel-firmware does not provide iwl3945-ucode
properly.
Comment 1 Vladimir Botka 2010-05-26 10:01:36 UTC
Would it be possible to post output of "hwinfo --sys". If your laptop is not recognised then the wlan firmware is not installed by default. This could be a duplicate of [1].

[1] https://bugzilla.novell.com/show_bug.cgi?id=591703#c0
Comment 2 Karl Eichwalder 2010-05-26 11:01:44 UTC
Good shot!

hwinfo --sys
02: None 00.0: 10107 System                                     
  [Created at sys.63]
  Unique ID: rdCR.n_7QNeEnh23
  Hardware Class: system
  Model: "System"
  Driver Info #0:
    Driver Status: thermal,fan are active
    Driver Activation Cmd: "modprobe thermal; modprobe fan"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
Comment 3 Vladimir Botka 2010-05-26 12:12:47 UTC
This should be fixed in M8 [1]. If not bnc 591703 shall be reopened.

[1] https://bugzilla.novell.com/show_bug.cgi?id=591703#c14
Comment 4 Peter Puncher 2010-05-26 21:26:29 UTC
Hello,

installed M7 on an Fujitsu P1620 with Intel 3945, but no wlan are found (neither by networkmanager nor by "iwlist scanning").

Dmesg outputs:

iwl3945 0000:05:00.0: firmware: requesting iwlwifi-3945-2.ucode
iwl3945 0000:05:00.0: iwlwifi-3945-2.ucode firmware file req failed: -2
iwl3945 0000:05:00.0: firmware: requesting iwlwifi-3945-1.ucode
iwl3945 0000:05:00.0: iwlwifi-3945-1.ucode firmware file req failed: -2
iwl3945 0000:05:00.0: Could not read microcode: -2

Looks to me like the problem of this bug ? Do i have to wait till MS 8 or is there a workaround ?

Regards, user2304
Comment 5 Vladimir Botka 2010-05-26 22:18:47 UTC
(In reply to comment #4)

> iwl3945 0000:05:00.0: firmware: requesting iwlwifi-3945-2.ucode
> iwl3945 0000:05:00.0: iwlwifi-3945-2.ucode firmware file req failed: -2
> Looks to me like the problem of this bug ? Do i have to wait till MS 8 or is
> there a workaround ?

Just install kernel-firmware, but there seems to be still problem with WPA-EAP encryption.
Comment 6 Vladimir Botka 2010-05-27 06:17:46 UTC
Shell be fixed in MS8.

*** This bug has been marked as a duplicate of bug 591703 ***
Comment 7 Andreas Jaeger 2010-05-27 11:20:11 UTC
Vladimir, in which bug is the WPA-EAP issue tracked?
Comment 8 Vladimir Botka 2010-05-27 12:49:16 UTC
(In reply to comment #7)
> Vladimir, in which bug is the WPA-EAP issue tracked?

For the record. WPA-EAP problem with Intel 3945 in 11.3 is tracked in:
bnc 601501 - connecting to secure wireless network fails most of the time