Bug 121955 - TX_POWER failure for ipw2200 on Travelmate 8101
Summary: TX_POWER failure for ipw2200 on Travelmate 8101
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Kernel (show other bugs)
Version: Final
Hardware: i586 SUSE Other
: P5 - None : Major
Target Milestone: ---
Assignee: Jiri Benc
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-10 13:11 UTC by Frank Fischer
Modified: 2007-02-16 14:13 UTC (History)
2 users (show)

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


Attachments
Dmesg with patch and apic (20.23 KB, text/plain)
2005-11-18 21:55 UTC, Frank Fischer
Details
Dmesg without patch and apic (24.50 KB, text/plain)
2005-11-18 21:56 UTC, Frank Fischer
Details
lspci output (2.11 KB, text/plain)
2005-11-18 21:57 UTC, Frank Fischer
Details
/proc/interrupts (681 bytes, text/plain)
2005-11-18 21:58 UTC, Frank Fischer
Details
acer-apic.patch (3.19 KB, patch)
2005-11-21 13:11 UTC, Jiri Benc
Details | Diff
Dmesg with suse apic patch (20.98 KB, text/plain)
2005-11-22 21:24 UTC, Frank Fischer
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Fischer 2005-10-10 13:11:12 UTC
The wlan can't be activated successfully on an Acer Travelmate 8101. The related
dmesg is:
ipw2200: module not supported by Novell, setting U taint flag.
ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.0.6
ipw2200: Copyright(c) 2003-2004 Intel Corporation
ACPI: PCI Interrupt 0000:06:03.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
ipw2200: Detected Intel PRO/Wireless 2915ABG Network Connection
ieee1394: Host added: ID:BUS[0-00:1023]  GUID[00c09f0000423950]
ipw2200: failed to send TX_POWER command
ipw2200: failed to send TX_POWER command
ipw2200: failed to send TX_POWER command
ipw2200: failed to send TX_POWER command
ipw2200: failed to send TX_POWER command
ipw2200: Unable to initialize device after 5 attempts.
ipw2200: failed to register network device
ACPI: PCI interrupt for device 0000:06:03.0 disabled
ipw2200: probe of 0000:06:03.0 failed with error -5

The above error occurs only with HW switch OFF. 
I remember that the same error occurred on my SuSE 9.4. But then I installed
ipw2200 1.0.6 and it worked perfectly including LED. There is a thread about the
same/similar (?) problem on the ipw2200 mailing list: 
http://thread.gmane.org/gmane.linux.drivers.ipw2100.devel/6417
However no solution is given. Btw, OpenSuSE 10.1 Alpha 1 has the same behavior.
Comment 1 Frank Fischer 2005-10-13 00:56:28 UTC
This problem can be fixed with the kernel patch you can find at
http://article.gmane.org/gmane.linux.drivers.ipw2100.devel/6541
In addition loapic needs to be turned on!
Comment 2 Olaf Kirch 2005-11-15 10:28:17 UTC
By "ioapic needs to be turned on" you mean enabled on the kernel command
line?

Jiri and Jiri, can you please look into this?
Comment 3 Frank Fischer 2005-11-16 19:31:40 UTC
I mean I need the following kernel command line:
root=/dev/sda6 vga=0x314 selinux=0 resume=/dev/sda7 splash=silent apic
Comment 4 Jiri Benc 2005-11-18 11:11:35 UTC
Please provide dmesg output without the patch applied, dmesg output with the patch and apic switch, lspci output and /proc/interrupts content.
Comment 5 Frank Fischer 2005-11-18 21:55:58 UTC
Created attachment 57764 [details]
Dmesg with patch and apic
Comment 6 Frank Fischer 2005-11-18 21:56:39 UTC
Created attachment 57765 [details]
Dmesg without patch and apic
Comment 7 Frank Fischer 2005-11-18 21:57:40 UTC
Created attachment 57766 [details]
lspci output
Comment 8 Frank Fischer 2005-11-18 21:58:33 UTC
Created attachment 57767 [details]
/proc/interrupts
Comment 9 Jiri Benc 2005-11-21 13:11:06 UTC
Created attachment 57869 [details]
acer-apic.patch

Could you please test with the attached patch (and with apic switch) and send dmesg output?
Comment 10 Frank Fischer 2005-11-22 21:24:20 UTC
Created attachment 58143 [details]
Dmesg with suse apic patch
Comment 11 Matej Horvath 2007-02-16 14:13:18 UTC
No reaction on this bug for a long time. Closing as CANTFIX.