Bugzilla – Bug 119815
Acer W-LAN card not configured
Last modified: 2007-03-19 11:23:15 UTC
I´ve an ACER W-LAN card with 11mBit/s. Hwinfo --netcard returns this: 21: PCI 208.0: 0200 Ethernet controller [Created at pci.277] UDI: /org/freedesktop/Hal/devices/pci_8086_1038 Unique ID: rBUF.SPbcKWAadaA Parent ID: 6NW+.+nd8koiLHvC SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:08.0 SysFS BusID: 0000:02:08.0 Hardware Class: network Model: "Compaq 82801CAM (ICH3) PRO/100 VM (KM) Ethernet Controller" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x1038 "82801CAM (ICH3) PRO/100 VM (KM) Ethernet Controller" SubVendor: pci 0x0e11 "Compaq Computer Corporation" SubDevice: pci 0x0098 Revision: 0x41 Driver: "e100" Device File: eth0 Memory Range: 0x40100000-0x40100fff (rw,non-prefetchable) I/O Ports: 0x2800-0x283f (rw) IRQ: 11 (531 events) HW Address: 00:02:a5:b8:1b:0f Link detected: yes Module Alias: "pci:v00008086d00001038sv00000E11sd00000098bc02sc00i00" Driver Info #0: Driver Status: e100 is active Driver Activation Cmd: "modprobe e100" Driver Info #1: Driver Status: eepro100 is not active Driver Activation Cmd: "modprobe eepro100" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (PCI bridge) 36: USB 00.1: 0282 WLAN controller [Created at usb.122] UDI: /org/freedesktop/Hal/devices/usb_device_967_204_1_if1 Unique ID: iVWJ.rCwbDvswxUE Parent ID: pBe4.aDK4e2xT5QF SysFS ID: /devices/pci0000:00/0000:00:1d.1/usb2/2-1/2-1:1.1 SysFS BusID: 2-1:1.1 Hardware Class: network Model: "WLAN controller" Hotplug: USB Vendor: usb 0x0967 Device: usb 0x0204 Revision: "1.32" Serial ID: "1" Driver: "prism2_usb" Device File: wlan0 Features: WLAN Speed: 12 Mbps Link detected: no Module Alias: "usb:v0967p0204d0132dc00dsc00dp00icFFiscFFipFF" Driver Info #0: Driver Status: prism2_usb is active Driver Activation Cmd: "modprobe prism2_usb" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #35 (Hub) The configuration by YaST2 goes without any errors, but the interface doesn´t work. I see the following messages in the log: Oct 1 23:12:09 michilap kernel: prism2_usb: module not supported by Novell, setting U taint flag. Oct 1 23:12:09 michilap kernel: prism2_usb: no version for "p80211netdev_rx" found: kernel tainted. Oct 1 23:12:09 michilap kernel: prism2usb_init: prism2_usb.o: 0.2.2 Loaded Oct 1 23:12:09 michilap kernel: prism2usb_init: dev_info is: prism2_usb Oct 1 23:12:09 michilap kernel: usbcore: registered new driver prism2_usb Oct 1 23:12:09 michilap kernel: bootsplash: status on console 0 changed to on Oct 1 23:12:09 michilap kernel: IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com> Oct 1 23:12:09 michilap kernel: microcode: CPU0 already at revision 0x1d (current=0x1d) Oct 1 23:12:09 michilap kernel: microcode: No new microcode data for CPU0 Oct 1 23:12:09 michilap kernel: IA-32 Microcode Update Driver v1.14 unregistered Oct 1 23:12:09 michilap kernel: BIOS EDD facility v0.16 2004-Jun-25, 1 devices found Oct 1 23:12:09 michilap kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex Oct 1 23:12:09 michilap kernel: NET: Registered protocol family 17 Oct 1 23:12:11 michilap modify_resolvconf: Service dhcpcd modified /etc/resolv.conf. See info block in this file Oct 1 23:12:12 michilap mDNSResponder (Engineering Build) (Sep 5 2005 22:27:50) [5070]: starting Oct 1 23:12:12 michilap kernel: ACPI: AC Adapter [C1A2] (off-line) Oct 1 23:12:12 michilap /usr/sbin/cron[5105]: (CRON) STARTUP (V5.0) Oct 1 23:12:12 michilap kernel: ACPI: Battery Slot [C19F] (battery present) Oct 1 23:12:12 michilap kernel: ACPI: Battery Slot [C1A0] (battery absent) Oct 1 23:12:12 michilap kernel: NET: Registered protocol family 10 Oct 1 23:12:12 michilap kernel: Disabled Privacy Extensions on device c036b920(lo) Oct 1 23:12:12 michilap kernel: IPv6 over IPv4 tunneling driver Oct 1 23:12:12 michilap kernel: ACPI: Power Button (FF) [PWRF] Oct 1 23:12:12 michilap kernel: ACPI: Sleep Button (CM) [C1A3] Oct 1 23:12:12 michilap kernel: ACPI: Lid Switch [C1A4] Oct 1 23:12:12 michilap sshd[5114]: Server listening on :: port 22. Oct 1 23:12:13 michilap kernel: pcc_acpi: module not supported by Novell, setting U taint flag. Oct 1 23:12:14 michilap kernel: bootsplash: status on console 0 changed to on Oct 1 23:12:14 michilap smpppd[5261]: smpppd version 1.59 started Oct 1 23:12:14 michilap rcpowersaved: enter 'speedstep_ich' into CPUFREQD_MODULE in /etc/sysconfig/powersave/cpufreq. Oct 1 23:12:14 michilap rcpowersaved: this will speed up starting powersaved and avoid unnecessary warnings in syslog. Oct 1 23:12:15 michilap kernel: bootsplash: status on console 0 changed to on Oct 1 23:12:16 michilap kdm: :0[4984]: pam_unix2: session started for user michael, service xdm-np Oct 1 23:12:19 michilap ifup: No configuration found for sit0 Oct 1 23:12:19 michilap hp: unable to open /var/run/hpiod.port: No such file or directory: prnt/hpijs/hplip_api.c 75 Oct 1 23:12:23 michilap kernel: eth0: no IPv6 routers present Oct 1 23:12:24 michilap rename_netiface: all zero mac address for wlan0 Oct 1 23:12:29 michilap dhcpcd[5917]: dhcpStart: ioctl SIOCSIFFLAGS: No such device Oct 1 23:12:34 michilap ifup: Cannot enable interface wlan0. Oct 1 23:12:35 michilap ifup-route: interface wlan0 is not up Oct 1 23:12:36 michilap modprobe: FATAL: Error inserting sonypi (/lib/modules/2.6.13-8-default/kernel/drivers/char/sonypi.ko): No such device I´ve found some linux live cds (e.g. pclinuxOS) where the card was detected and initialized (there´s a red light on it which started to light), so I guess support for linux is possible.
Can you please add /var/log/YaST2 and hwinfo? (http://www.opensuse.org/Bug_Reporting_FAQ#YaST)
Is the above hwinfo output not correct? I´ve attached Y2Logs
Hwinfo is ok, Michael should refine his canned responses :) But you still forgot the y2logs :) Anyway, "Oct 1 23:12:24 michilap rename_netiface: all zero mac address for wlan0" suggests that the card is not fully initialized. Perhaps it needs firmware? Do you have an idea, Joachim?
Created attachment 51412 [details] YaST2 logs
Ups sorry about not attaching the logs but saying I did it. It´s is now the third time this happens :( When I reply to a bug report, I´m sometimes transferred to another completely unrelated bug. Then I attach the logs to the wrong one. IMO this is bugzillas fault, since there´s no category for "bugs in bugzilla" could this please be forwarded to the webmaster?
Comment 3: The Prism2 devices have a non volatile firmware memory, so there should be no firmware image necessary. Michael, could you also attach the output of 'ip a'?
The yast logs also show that no configuration got created for the wireless card (/etc/sysconfig/network/ifcfg-*). Anyway, let's see "ip a".
I reconfigured the card with YaST and after a restart it seems to work. Unfortunately there´s no WLAN in here so I can test it not before thursday. The light on the device lights what it didn´t before and there´s now an ifcfg config file, too. What I don´t understand is why it didn´t work the first time and also why the card works only after a restart (it should work immediately) michael@r098089:~> ip a 1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:02:a5:b8:1b:0f brd ff:ff:ff:ff:ff:ff inet 10.150.98.89/24 brd 10.150.98.255 scope global eth0 inet6 fe80::202:a5ff:feb8:1b0f/64 scope link valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 4: cipsec0: <NOARP> mtu 1356 qdisc noop qlen 1000 link/ether 00:0b:fc:f8:01:8f brd ff:ff:ff:ff:ff:ff 5: sit0: <NOARP> mtu 1480 qdisc noop link/sit 0.0.0.0 brd 0.0.0.0
What I also noticed is that if I unplug the card and replug it it doesn´t work any more It neither works if the system is started without the card and I insert it later.
Reassigning to the new maintainer of yast2-network.
It seems as kernel module problem
prism2_usb is not in the kernel, it's an external unsupported module. Most of drivers in km_wlan package (or wlan-kmp for newer versions of openSUSE) are poor quality, broken on some setups and are unsupportable. The only solution to fix them is to rewrite them completely. Sorry.