Bugzilla – Bug 386364
Intel PRO/Wireless 3945ABG does not function.
Last modified: 2008-06-18 15:47:12 UTC
Intel PRO/Wireless 3945ABG does not function on setup of networking using the openSUSE 11.0 Beta 2 KDE4 live CD. "iwconfig" shows there is no access point associated. "ifdown wlan0" and "ifup wlan0" fixes this yet there is still no access to the network nor internet. Only the router can be pinged. I suspect a kernel bug in kernels 2.6.24 and above as Ubuntu 8.04 and Mandriva 2008 Spring have similar problems. openSUSE 10.3 seemed to work fine.
Some more details on how you've set up the wireless connection would be nice to have. Did you use NetworkManager or Yast? Could you please provide /var/log/NetworkManager, /var/log/wpa_supplicant and the output of dmesg?
I am using Yast in NetworkManager mode to set up the wireless connection. I once managed to ping the outside world after using a static IP instead of DHCP, but i tried again just now to set up the wireless connection the same way and failed. I had to change to "traditional method" and use "ifdown wlan0" then "ifup wlan0" still access point invalid error when i run iwconfig. I believe the "iwl3945" driver is at fault. /var/log/NetworkManager : May 3 18:44:56 linux NetworkManager: <info> starting... May 3 18:44:56 linux NetworkManager: <info> Trying to start the supplicant... May 3 18:44:56 linux NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch May 3 18:44:56 linux NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'. May 3 18:44:56 linux NetworkManager: <info> Found new Ethernet device 'eth0'. May 3 18:44:56 linux NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_17_08_3b_e9_0b May 3 18:44:56 linux NetworkManager: <info> wlan0: Device is fully-supported using driver 'iwl3945'. May 3 18:44:56 linux NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). May 3 18:44:56 linux NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. May 3 18:44:56 linux NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_18_de_6f_a3_32 May 3 18:44:56 linux NetworkManager: <info> Trying to start the system settings daemon... May 3 18:45:00 linux NetworkManager: <info> Bringing up device eth0 May 3 18:45:01 linux NetworkManager: <info> Deactivating device eth0. May 3 18:45:01 linux NetworkManager: <info> Bringing up device wlan0 May 3 18:45:02 linux NetworkManager: <info> Deactivating device wlan0. May 3 18:45:02 linux NetworkManager: <info> Deactivating device eth0. May 3 18:45:02 linux NetworkManager: <WARN> auto_activate_device(): Connection 'System eth0' auto-activation failed: (2) Device not managed by NetworkManager May 3 18:45:03 linux NetworkManager: <info> (wlan0) supplicant interface is now in state 2 (from 1). May 3 18:53:32 linux NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally. May 3 18:53:32 linux NetworkManager: <info> Bringing down device eth0 May 3 18:53:32 linux NetworkManager: <info> Bringing down device wlan0 May 3 18:53:34 linux NetworkManager: <info> starting... May 3 18:53:34 linux NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch May 3 18:53:34 linux NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'. May 3 18:53:34 linux NetworkManager: <info> Found new Ethernet device 'eth0'. May 3 18:53:34 linux NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_17_08_3b_e9_0b May 3 18:53:34 linux NetworkManager: <info> wlan0: Device is fully-supported using driver 'iwl3945'. May 3 18:53:34 linux NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). May 3 18:53:34 linux NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. May 3 18:53:34 linux NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_18_de_6f_a3_32 May 3 18:53:36 linux NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally. May 3 18:53:37 linux NetworkManager: <info> starting... May 3 18:53:37 linux NetworkManager: <info> Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch May 3 18:53:37 linux NetworkManager: <info> eth0: Device is fully-supported using driver 'tg3'. May 3 18:53:37 linux NetworkManager: <info> Found new Ethernet device 'eth0'. May 3 18:53:37 linux NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_17_08_3b_e9_0b May 3 18:53:37 linux NetworkManager: <info> wlan0: Device is fully-supported using driver 'iwl3945'. May 3 18:53:37 linux NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). May 3 18:53:37 linux NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. May 3 18:53:37 linux NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_18_de_6f_a3_32 May 3 18:53:41 linux NetworkManager: <info> Bringing up device eth0 May 3 18:53:42 linux NetworkManager: <info> Deactivating device eth0. May 3 18:53:42 linux NetworkManager: <info> Bringing up device wlan0 May 3 18:53:42 linux NetworkManager: <info> Deactivating device wlan0. May 3 18:53:42 linux NetworkManager: <info> (wlan0) supplicant interface is now in state 2 (from 1). May 3 18:54:41 linux NetworkManager: <WARN> nm_signal_handler(): Caught signal 15, shutting down normally. May 3 18:54:41 linux NetworkManager: <info> Bringing down device eth0 May 3 18:54:41 linux NetworkManager: <info> Bringing down device wlan0 /var/log/wpa_supplicant : empty dmesg : attery Slot [C1BB] (battery absent) ACPI: LNXTHERM:01 is registered as thermal_zone0 ACPI: Thermal Zone [TZ0] (45 C) ACPI: LNXTHERM:02 is registered as thermal_zone1 ACPI: Thermal Zone [TZ1] (41 C) ACPI: LNXTHERM:03 is registered as thermal_zone2 ACPI: Thermal Zone [TZ2] (32 C) ACPI: LNXTHERM:04 is registered as thermal_zone3 ACPI: Thermal Zone [TZ3] (24 C) ACPI: LNXTHERM:05 is registered as thermal_zone4 ACPI: Thermal Zone [TZ4] (20 C) tg3.c:v3.90 (April 12, 2008) ACPI: PCI Interrupt 0000:02:0e.0[A] -> GSI 16 (level, low) -> IRQ 16 usbcore: registered new interface driver hiddev input: Microsoft Microsoft 3-Button Mouse with IntelliEye(TM) as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/input/input6 eth0: Tigon3 [partno(BCM95788A50) rev 3003 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000Base-T Ethernet 00:17:08:3b:e9:0b eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[0] TSOcap[1] eth0: dma_rwctrl[763f0000] dma_mask[32-bit] ACPI: PCI Interrupt 0000:02:06.1[B] -> GSI 19 (level, low) -> IRQ 19 input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft 3-Button Mouse with IntelliEye(TM)] on usb-0000:00:1d.1-1 ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[19] MMIO=[e8101000-e81017ff] Max Packet=[2048] IR/IT contexts=[4/8] usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver Yenta: CardBus bridge found at 0000:02:06.0 [103c:30aa] Yenta: Enabling burst memory read transactions Yenta: Using INTVAL to route CSC interrupts to PCI Yenta: Routing CardBus interrupts to PCI Yenta TI: socket 0000:02:06.0, mfunc 0x01a61b22, devctl 0x64 sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.23ks iwl3945: Copyright(c) 2003-2007 Intel Corporation ACPI: Transitioning device [C325] to D3 ACPI: PNP0C0B:00 is registered as cooling_device2 ACPI: Fan [C325] (off) ACPI: Transitioning device [C326] to D3 ACPI: PNP0C0B:01 is registered as cooling_device3 ACPI: Fan [C326] (off) input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/input/input7 ACPI: Transitioning device [C327] to D3 ACPI: PNP0C0B:02 is registered as cooling_device4 ACPI: Fan [C327] (off) Yenta: ISA IRQ mask 0x0000, PCI irq 18 Socket status: 30000006 Yenta: Raising subordinate bus# of parent bus (#02) from #03 to #06 pcmcia: parent PCI bridge I/O window: 0x7000 - 0x7fff cs: IO port probe 0x7000-0x7fff: clean. pcmcia: parent PCI bridge Memory window: 0xe8100000 - 0xe83fffff pcmcia: parent PCI bridge Memory window: 0x80000000 - 0x83ffffff sdhci: SDHCI controller found at 0000:02:06.3 [104c:803c] (rev 0) ACPI: PCI Interrupt 0000:02:06.3[C] -> GSI 22 (level, low) -> IRQ 22 ACPI: Transitioning device [C328] to D3 ACPI: PNP0C0B:03 is registered as cooling_device5 ACPI: Fan [C328] (off) mmc0: SDHCI at 0xe8109000 irq 22 PIO ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:08:00.0 to 64 iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection ACPI: Video Device [C083] (multi-head: yes rom: no post: no) iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels phy0: Selected rate control algorithm 'iwl-3945-rs' ACPI: PCI interrupt for device 0000:08:00.0 disabled ACPI: PCI Interrupt 0000:02:06.2[B] -> GSI 19 (level, low) -> IRQ 19 ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 21 (level, low) -> IRQ 21 PCI: Setting latency timer of device 0000:00:1b.0 to 64 cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff: clean. cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. Bluetooth: L2CAP ver 2.9 Bluetooth: L2CAP socket layer initialized Bluetooth: RFCOMM socket layer initialized Bluetooth: RFCOMM TTY layer initialized Bluetooth: RFCOMM ver 1.8 type=1505 audit(1209840264.232:2): operation="profile_load" name="/bin/ping" name2="default" pid=2272 type=1505 audit(1209840264.260:3): operation="profile_load" name="/sbin/klogd" name2="default" pid=2277 type=1505 audit(1209840264.296:4): operation="profile_load" name="/sbin/syslog-ng" name2="default" pid=2283 type=1505 audit(1209840264.336:5): operation="profile_load" name="/sbin/syslogd" name2="default" pid=2284 type=1505 audit(1209840264.376:6): operation="profile_load" name="/usr/sbin/avahi-daemon" name2="default" pid=2285 type=1505 audit(1209840264.416:7): operation="profile_load" name="/usr/sbin/identd" name2="default" pid=2286 type=1505 audit(1209840264.448:8): operation="profile_load" name="/usr/sbin/mdnsd" name2="default" pid=2288 type=1505 audit(1209840264.484:9): operation="profile_load" name="/usr/sbin/nscd" name2="default" pid=2294 type=1505 audit(1209840264.669:10): operation="profile_load" name="/usr/sbin/ntpd" name2="default" pid=2310 type=1505 audit(1209840265.197:11): operation="profile_load" name="/usr/sbin/traceroute" name2="default" pid=2319 bootsplash: status on console 0 changed to on IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk> powernow: This module only works with AMD K7 CPUs Bluetooth: BNEP (Ethernet Emulation) ver 1.2 Bluetooth: BNEP filters: protocol multicast Bridge firewalling registered pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. BIOS EDD facility v0.16 2004-Jun-25, 6 devices found type=1503 audit(1209840296.444:12): operation="capable" name="mknod" pid=3127 profile="/usr/sbin/nscd" ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 16 (level, low) -> IRQ 16 PM: Writing back config space on device 0000:08:00.0 at offset 1 (was 100002, writing 100006) NET: Registered protocol family 17 NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_UP): wlan0: link is not ready [drm] Initialized drm 1.1.0 20060810 ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 PCI: Setting latency timer of device 0000:00:02.0 to 64 [drm] Initialized i915 1.6.0 20060119 on minor 0 bootsplash: status on console 0 changed to on bootsplash: status on console 0 changed to on CPU0 attaching NULL sched-domain. CPU1 attaching NULL sched-domain. CPU0 attaching sched-domain: domain 0: span 00000003 groups: 00000001 00000002 CPU1 attaching sched-domain: domain 0: span 00000003 groups: 00000002 00000001 lspci : 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01) 00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 01) 02:06.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller 02:06.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller 02:06.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) 02:06.3 SD Host controller: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller 02:06.4 Communication controller: Texas Instruments PCIxx12 GemCore based SmartCard controller 02:0e.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5788 Gigabit Ethernet (rev 03) 08:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
Oh yes all distro's lately using "iwl3945" seem to have the same problem.
I sure hope this is fixed prior to release. All us ipw / iwl3945 / 4945 users have been getting screwed the last few releases. I have done a ton of work with the ipw driver, I'll try to load 11.0 B2 on a seperate drive and mess with the iwl driver to see the cause (if I have time)
Marek, I cannot see any connection attempt in your NetworkManager log and dmesg-output. Seems like no wireless connection is configured. Is it correct that you configured your wireless connection using Yast? Or did you use KNetworkManager or nm-applet?
I used Yast, i gave the dmesg output straight after i booted up before configuring the network. I managed to connect once to the internet using Yast to configure the network. But on my third and forth attempts after rebooting i could not. I forget if i gave the NetworkManager log before or after configuring the network with Yast.
"ifdown wlan0" and "ifup wlan0" a couple of times gives me my access point, cannot ping anywhere, only thing i see new in dmesg is this: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: disassociate(reason=3) wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: no IPv6 routers present wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate I am also unable to get a route now "route add default gw x.x.x.x" gives an error.
Could you attach the lines before the part you've posted in comment #7?
The part of "iwlist wlan0 scan" that shows your AP would be nice to have too.
"ifdown wlan0" "ifup wlan0" ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: Initial auth_alg=0 wlan0: authenticate with AP xxxxxxxx wlan0: Initial auth_alg=0 wlan0: authenticate with AP xxxxxxxx wlan0: RX authentication from xxxxxxxx (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP xxxxxxxx wlan0: RX AssocResp from xxxxxxxx (capab=0x431 status=0 aid=1) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: disassociate(reason=3) wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: xxxxxxxxxxxxx ESSID:"" Mode:Master Channel:1 Frequency:2.412 GHz (Channel 1) Quality=73/100 Signal level=-61 dBm Noise level=-127 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=00000102ed66ed48
JFYI: I can't reproduce the bug. Both, YaST and NetworkManager work as expected. All I can see is the following error in /var/log/messages: May 6 22:26:46 linux rcnetwork: Starting the NetworkManagerDispatcher May 6 22:26:46 linux rcnetwork: Starting the NetworkManager May 6 22:26:46 linux nm-system-settings: nm_connection_get_path: assertion `NM_IS_CONNECTION (connection)' failed May 6 22:26:46 linux nm-system-settings: nm_connection_get_path: assertion `NM_IS_CONNECTION (connection)' failed After I configured the network in YaST I can see and select it in KNetworkManager.
14 months ago the HP NC6320 was a SLED certified laptop and the wireless has worked fine till now. Please note i am using the Beta 2 Live CD and have not installed to hard drive.
Lowering severity as the issue does not happen for every iwl3945-user and the reported issue seems to be a special case. Marek, did you already try an other AP or an other security mode?
(In reply to comment #13 from Helmut Schaa) > Lowering severity as the issue does not happen for every iwl3945-user and the > reported issue seems to be a special case. > > Marek, did you already try an other AP or an other security mode? > No, i have been using the same AP and security mode since since openSUSE 10.1 i think it was. Do not want to mess with my router settings on my whole network now.
It is strange that using ipw3945 on openSUSE 10.3, Mandriva 2008.0 and Ubuntu 7.10 the wireless works fine on my laptop. Yet using iwl3945 does not work on opensuse 11.0 Beta 2, Mandriva 2008 Spring and Ubuntu 8.04 LTS.
I recently did a 10.3->11.0 Beta 2 upgrade and lost wireless connectivity. I think my OpenSuse 11.0 is trying to use ipw from what I can tell. For more details, please see Bug 357881. Regards: Bill M
Well looks like my SLED certified laptop is not certified anymore :-) Fedora 9 wireless does not function either. This iwl3945 looks to be the problem. ipw3945 works fine.
(In reply to comment #17 from Marek Pawinski) > Well looks like my SLED certified laptop is not certified anymore :-) Fedora 9 > wireless does not function either. This iwl3945 looks to be the problem. > ipw3945 works fine. > All, please add the version of iwl you are running.
iwl3945 doesn't work for me either. Here's the info: lspci: 0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) modinfo (stripped): filename: /lib/modules/2.6.25-26-default/kernel/drivers/net/wireless/iwlwifi/iwl3945.ko version: 1.2.23ks description: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux srcversion: 4A575718FCF5F831B2E2602 firmware: iwl3945-ucode-2.14.1.5-46
Probably a duplicate of Bug 283724 considering comment #0
iwl3945-ucode-2.14.1.5-45
"ifdown wlan0" and "ifup wlan0" fixes this yet there is still no access to the network nor internet. Only the router can be pinged. This sounds rather like a DNS issue to me. Same behavior here. After DHCLIENT wlan0 I get the connection. iwl3945-ucode-2.14.1.5-47
Yes, this sounds like a invalid or missing route. Marek, can you confirm this behaviour?
This is not a DNS nor route problem, "iwconfig" shows there is no access point associated. Once i run "ifdown wlan0" and "ifup wlan0" a couple of times, sometimes i get an access point.
So your description in Comment #0 was in error ? "Only the router can be pinged. " How can you ping the router if no AP connected ?
(In reply to comment #25 from Casual J. Programmer) > So your description in Comment #0 was in error ? "Only the router can be > pinged. > " How can you ping the router if no AP connected ? > Read Comment #0 again very slowly.
Not sure what this is going to be. In comment #0 you first have no association, then you ifdown / ifup wlan0 and now _have_ associated so nothing wrong with ucode or iwl. you can ping router ( AP ) but no internet IP This is a routing issue fwiw Compare comment #0 and comment #24 _very_slowly_
Same bug with Beta 3
I find it rather strange that i can set up wireless on: openSUSE 10.1 openSUSE 10.2 openSUSE 10.3 but not openSUSE 11.0 Beta 2 nor 3
Marek, you are in good company ;-)
Looks to me like a duplicate of Bug 389759 - DHCP fails after update to Factory, or vice versa if you like..
No, it does not. Bug 389759 is about an invalid flag used when starting dhcpcd. NetworkManager doesn't use ifup scripts to start a dhcp client and it doesn't use dhcpcd either.
openSUSE 11.00 RC1 1. Set up wireless networking with YAST - no access point 2. ifdown wlan0 3. ifup wlan0 4. access point comes up 5. can ping and surf the net 6. almost there :-)
well decided to try WPA2 instead off WEP and bingo wireless works first time, looks like WEP was the problem.
I don't think WEP is the problem. I've the same issue with WPA2-PSK with the RC 2 live CD. NM sees the network, but it keeps asking for the key. Regards, Alberto
As the initial report seems to be fixed in GM I'd like to animate everybody to open new bug reports for the different outstanding issues. Furthermore iwl3945 works like a charm for me :) Please add the following information to the new reports: - wireless setup method (yast or NetworkManager) - which frontend (KNetworkManager or nm-applet) - which security type (WPA-PSK, WPA-EAP or WEP) Thanks a lot. Closing as FIXED.