|
Bugzilla – Full Text Bug Listing |
| Summary: | ipw2100 on nx7010 does not work | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Jozef Sakalos <jsakalos> |
| Component: | Network | Assignee: | Joachim Gleissner <joachim.gleissner> |
| Status: | VERIFIED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | aj |
| Version: | Beta 4 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jozef Sakalos
2005-09-04 11:08:08 UTC
Where did you install the package from? Please provide the output of dmesg. I have installed SUSE Linux 10.0Beta4 from distribution iso images from suse.inode.at as clean new installation. I have downladed the ipw-firmware from ftp://ftp.univie.ac.at/systems/linux/suse/i386/10.0/SUSE-Linux10.0-Beta4-Extra/kernel-modules+firmware/CD1/suse/src/ipw-firmware-5-6.src.rpm and I've built it with rpmbuild -ba ipw-firmware.spec. The /var/log/messages ipw relevant lines are only these: Sep 4 11:52:40 wnbj kernel: ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 1.1.2 Sep 4 11:52:40 wnbj kernel: ipw2100: Copyright(c) 2003-2005 Intel Corporation Sep 4 11:52:40 wnbj kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [C0C5] -> GSI 5 (level, low) -> IRQ 5 Sep 4 11:52:40 wnbj kernel: ipw2100: Detected Intel PRO/Wireless 2100 Network Connection One info more that could help: On SuSE 9.3 it seems like the ipw2100 Tx power is always OFF but the card WORKS. For example: iwconfig eth1 output says: eth1 IEEE 802.11b ESSID:"xxxxxx" Nickname:"wnbj" Mode:Managed Frequency:2.452 GHz Access Point: 00:04:E2:D7:61:B8 Bit Rate=11 Mb/s Tx-Power:off Retry:on RTS thr:off Fragment thr:off Encryption key:xxxxx-xxx.... Security mode:restricted Power Management:off Link Quality=86/100 Signal level=-72 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:1 Invalid misc:58 Missed beacon:0 Or, when I start wlassistant (still on 9.3) it always tries to turn Tx power on. Apparently it stays OFF - BUT THE CARD WORKS FINE. I hope, I've helped. 9.3 had a ipw2100 version which had problems with iwconfig get/set txpower. If I understand your comment correctly, your card is working and the bug can be closed. Please reopen if that's not the case. I haven's stated my comment clearly enough, I guess. So, in 9.3 it works in spite of tx-power but in 10.0 it DOES NOT WORK. Regards, Jozef All my comments that state "it works" belong to SuSE Linux 9.3 Pro. In SuSE Linux 10.0 IT DOES NOT WORK. Ok, and what does not work? Do you have no connection at all? OK, I'll summarize the problem: 1. Clean installation of SuSE Linux 10.0 Beta4 on notebook Compaq nx7010 2. The ipw2100 is detected correctly. 3. Clicking Edit in yast brings dialog that package ipw-firmware must be installed. The ipw-firmware package is not on installation media. This is first proble as it should be if it is needed. 4. I got ipw-firmware from the mentioned ftp server and installed it. 5. I can edit properties of the card now (IP address, mask, etc.) 6. Module ipw2100 loaded correctly with above messages in /var/log/messages. 7. Card does not work at all. No connection, no signal level, nothing. If more info is needed just tell me. Regards Jozef I have some additional info that could help to fix the bug: 1. I have tried to increase debug level for module ipw2100 but the messages stay same. Probably it wasn't compiled with DEBUG flag. 2. The ipw2100 messages are: Sep 5 13:07:07 wnbj kernel: ieee80211_crypt: unregistered algorithm 'NULL' (deinit) Sep 5 13:07:19 wnbj kernel: ieee80211_crypt: module not supported by Novell, setting U taint flag. Sep 5 13:07:19 wnbj kernel: ieee80211_crypt: registered algorithm 'NULL' Sep 5 13:07:19 wnbj kernel: ieee80211: module not supported by Novell, setting U taint flag. Sep 5 13:07:19 wnbj kernel: ieee80211: 802.11 data/management/control stack, 1.0.3 Sep 5 13:07:19 wnbj kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com> Sep 5 13:07:19 wnbj kernel: ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, 1.1.2 Sep 5 13:07:19 wnbj kernel: ipw2100: Copyright(c) 2003-2005 Intel Corporation Sep 5 13:07:19 wnbj kernel: ACPI: PCI Interrupt 0000:02:02.0[A] -> Link [C0C5] -> GSI 5 (level, low) -> IRQ 5 Sep 5 13:07:19 wnbj kernel: ipw2100: Detected Intel PRO/Wireless 2100 Network Connection 3. The iwconfig eth1 output is: # iwconfig eth1 eth1 unassociated ESSID:off/any Nickname:"ipw2100" Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00 Bit Rate=0 kb/s Tx-Power:off Retry min limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 There are no messages saying anything about firmware. Thus, I'm not sure if it gets loaded at all. Regards, Jozef The absence of messages about firmware is usually a good sign. Please attach 'rcnetwork status eth1' and 'rcnetwork start eth1' output. Hi,
here is the requested info:
# rcnetwork start eth1
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
eth1 device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI
Adapter (rev 04)
eth1 configuration: wlan-eth1
eth1 IP address: 192.168.58.105/24 done
SuSEfirewall2: Warning: ip6tables does not support state matching. Extended
IPv6 support disabled.
SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
SuSEfirewall2: batch committing...
SuSEfirewall2: Firewall rules successfully set
# rcnetwork status eth1
eth1 device: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI
Adapter (rev 04)
eth1 configuration: wlan-eth1
eth1 IP address: 192.168.58.105/24
eth1 unassociated ESSID:off/any Nickname:"wnbj"
Mode:Managed Channel=0 Access Point: 00:00:00:00:00:00
Bit Rate=0 kb/s Tx-Power:off
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xx Security
mode:restricted
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
running
Checking service network . . . . . . . . . . . . . . . running
This is additional to your request (NO-CARRIER?):
# ip addr show dev eth1
4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen
1000
link/ether 00:0c:f1:23:2c:4a brd ff:ff:ff:ff:ff:ff
inet 192.168.58.105/24 brd 192.168.58.255 scope global eth1
inet6 fe80::20c:f1ff:fe23:2c4a/64 scope link
valid_lft forever preferred_lft forever
Missing packages are generally no blockers. Sometimes such packages (firmware and commercial software) cannot even be shiped due to copyright problems. You can try the wishlisht, though: http://opensuse.org/index.php/Package_Wishlist Does someone know if this package wasn't included intentionally? And Jozef: Did you install the `normal' or OSS-Version of b4? Addition: The package ``ipw-firmware-5-6.noarch.rpm'' is included in b4. So this problem will be marked es resolved. Please try out _this_ package, if it does not work, create a seperate bug for it. For Michael Gross.
Hi Michael,
I'm not very sure if I expressed myself clearly enough to be understood.
My problem is NOT A MISSING PACKAGE. It's also NOT A BLOCKER.
My problem is that ipw2100 on my notebook DOES NOT WORK. And this fact is also
THE BLOCKER for me. Imagine a notebook without connection to internet...
Then, I didn't even know that there is some NORMAL version of OpenSuSE Linux
10.0 Beta4. I've installed from
ftp://suse.inode.at/opensuse/distribution/SL-10.0-OSS-beta4/iso i386 version.
Then, you're writing that ipw-firmware-5-6.noarch.rpm is included in b4
(Beta4?) but believe me I've searched all 5 CDs at least three times and IT IS
NOT THERE.
I downloaded the package from
ftp://suse.inode.at/pub/i386/10.0/SUSE-Linux10.0-Beta4-Extra/kernel-modules+firmware/CD1/suse/noarch
reinstalled it (rpm -e ipw-firmware && rpm -Uvh ipw-firmware-5-6.noarch.rpm)
and the wireless still DOES NOT WORK.
I'm not going to create the separate bug for it as I still don't know if the
problem is firmware or something else.
The last remark. I've been using SuSE for almost ten years for my servers,
clusters, workstations and notebooks. Therefore I was very excited when I
found the opensuse initiative and I thought this way opensuse will become best
supported Linux distribution ever.
Now, I'm not sure.... This is going to be the way to fix bugs? Really?
I want simple thing get the wireless working again. It worked in previous SuSE
version. So, what the hell is problem?
Regards,
Jozef
see the previous comment Ok, sorrey Jozef, but please understand that this bug is ``major'' at max, problems with specific notebooks do not affect many people, so shortly before the release we must prioritize a little more than usual. Good, this sounds much better. I thought you want to sweep it under the carpet. Jozef Comment 13: Firmware packages are not included in openSUSE because they are not open source. They will be included in the boxed version and can be downloaded by openSUSE users. If this bug is a blocker or not depends on whether the problem you described is a general bug in the driver, or just a bug that occurs only in special cases, or maybe even only a misconfiguration. But I can't tell yet. The information provided by you shows that the configuration for your card is found and applied, but association fails. So it would be useful to know whether your card can see the access point at all. You can scan your environment for access points by calling 'iwlist eth1 scan'. Here is output of iwlist eth1 scan (Cell 02 is my AP):
eth1 Scan completed :
Cell 01 - Address: 00:60:B3:8C:D7:BB
ESSID:"CONNECTED"
Protocol:IEEE 802.11b
Mode:Master
Channel:3
Encryption key:on
Bit Rate:5.5 Mb/s
Extra: Rates (Mb/s): 1 2 5.5
Quality=18/100 Signal level=-87 dBm
Extra: Last beacon: 528ms ago
Cell 02 - Address: 00:04:E2:D7:61:B8
ESSID:"<hidden>"
Protocol:IEEE 802.11bg
Mode:Master
Channel:9
Encryption key:on
Bit Rate:54 Mb/s
Extra: Rates (Mb/s): 1 2 5.5 6 9 11 12 18 24 36 48 54
Quality=62/100 Signal level=-63 dBm
Extra: Last beacon: 1868ms ago
I guess the access point you want to connect to is the one with the hidden id. Could you try to set another scanmode in the ifcfg-file? WIRELESS_AP_SCANMODE='2' may help. BINGOOOOO!
It works.
I had to enter my network name ("jswlan") too - without it it doesn't work.
Now, I'm leaving the bug open as it's to you to prepare such a default
configuration that the ipw2100 works out-of-the-box.
Thank you for your help and cooperation. This is the way of OSS development
I've dreamed about.
For information and to help with default configuration I attach contents of my
working ifcfg file:
BOOTPROTO='static'
BROADCAST=''
IPADDR='192.168.58.105'
MTU=''
NAME='Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter'
NETMASK='255.255.255.0'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
UNIQUE='JNkJ.OhV9FCzNa0E'
USERCONTROL='yes'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='2'
WIRELESS_AUTH_MODE='sharedkey'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_ESSID='jswlan'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0='xxxxxxxxxxxxxxxxxxxxxxxxxx'
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_POWER='yes'
WIRELESS_WPA_IDENTITY=''
WIRELESS_WPA_PASSWORD=''
WIRELESS_WPA_PSK=''
_nm_name='bus-pci-0000:02:02.0'
Well, unlike most other drivers ipw2100 seems to need a non-default scanmode. I'll change the default scanmode for this driver. Fixed package submitted. |