|
Bugzilla – Full Text Bug Listing |
| Summary: | WLAN Card Not Detected Properly | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Rebecca Walter <rwalter> |
| Component: | YaST2 | Assignee: | Steffen Winterfeldt <snwint> |
| Status: | RESOLVED FIXED | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | gchristensen, mvidner, snwint |
| Version: | Alpha 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
Joe? SLES does not contain a driver for this card. Then it is a job for yast to tell the user how to find the driver at madwifi.org. But first hwinfo should identify the card as wifi. There is no packaged driver at madwifi.org for SLES10. Furthermore, I don't think it is wanted that we point users to packages containing binary-only kernel modules. And finally, hwinfo knows about madwifi being a WLAN driver, but when the driver is not installed, the card cannot be assigned to that driver, and that means, hwinfo is not able to detect that this network card is actually a wireless one. To actually achieve that, we would have to maintain vendor and device id lists in hwinfo. I leave it up to Steffen to comment that. I don't think sles should fiddle with madwifi My Netgear WG311TGR was correct identified in openSUSE 10.2 and was running with madwifi without problems. In openSUSE 10.3 it is not shown as a wifi device. YAST is not able to configure this card though madwifi is installed. + The yast message is: Ethernet Network Card (not connected) BusID : 0000:03:00.0 Unable to configure network card because kernel device is not present + hwinfo is showing this: 25: PCI 300.0: 0200 Ethernet controller [Created at pci.301] UDI: /org/freedesktop/Hal/devices/pci_168c_13 Unique ID: svHJ.6YBoXuWNRV3 Parent ID: 6NW+.clCealCK_QA SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:03:00.0 SysFS BusID: 0000:03:00.0 Hardware Class: network Model: "Netgear AR5212/AR5213 Multiprotocol MAC/baseband processor" Vendor: pci 0x168c "Atheros Communications, Inc." Device: pci 0x0013 "AR5212/AR5213 Multiprotocol MAC/baseband processor" SubVendor: pci 0x1385 "Netgear" SubDevice: pci 0x5a00 Revision: 0x01 Memory Range: 0xfeaf0000-0xfeafffff (rw,non-prefetchable) IRQ: 10 (no events) Module Alias: "pci:v0000168Cd00000013sv00001385sd00005A00bc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #19 (PCI bridge) In addition to Comment #3 From Martin Vidner This looks to be the same problem Well, from the log I'd say that there is no driver for it. Joe, do you have any comments? There seems to be no driver, at least it is not loaded. Do you have madwifi installed and does it match your kernel? You can find out calling 'rpm -qa madwifi-kmp-*' and 'uname -r'. I was using the madwifi rpms for openSuse 10.2 as they weren't available for Version 10.3 at madwifi.org Now the madwifi rpms are available for openSuse 10.3 at madwifi.org and they work very well with my wifi card. So, everything is fine now? |
The wireless network card on my T42P isn't recognized properly. mustang:~ # hwinfo --netcard 25: PCI 201.0: 0200 Ethernet controller [Created at pci.305] UDI: /org/freedesktop/Hal/devices/pci_8086_101e Unique ID: rBUF.tqwo9I3YIvF Parent ID: 6NW+.+ISWpD3pbdC SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:01.0 SysFS BusID: 0000:02:01.0 Hardware Class: network Model: "IBM PRO/1000 MT Mobile Connection" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x101e "82540EP Gigabit Ethernet Controller (Mobile)" SubVendor: pci 0x1014 "IBM" SubDevice: pci 0x0549 "PRO/1000 MT Mobile Connection" Revision: 0x03 Driver: "e1000" Device File: eth0 Memory Range: 0xc0220000-0xc023ffff (rw,non-prefetchable) Memory Range: 0xc0200000-0xc020ffff (rw,non-prefetchable) I/O Ports: 0x8000-0x803f (rw) Memory Range: 0xec000000-0xec00ffff (ro,prefetchable,disabled) IRQ: 11 (8756 events) HW Address: 00:11:25:86:c2:99 Link detected: yes Module Alias: "pci:v00008086d0000101Esv00001014sd00000549bc02sc00i00" Driver Info #0: Driver Status: e1000 is active Driver Activation Cmd: "modprobe e1000" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge) 26: PCI 202.0: 0200 Ethernet controller [Created at pci.305] UDI: /org/freedesktop/Hal/devices/pci_168c_1014 Unique ID: LHB6.CgCH_H3+X79 Parent ID: 6NW+.+ISWpD3pbdC SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:02.0 SysFS BusID: 0000:02:02.0 Hardware Class: network Model: "IBM AR5212 802.11abg NIC" Vendor: pci 0x168c "Atheros Communications, Inc." Device: pci 0x1014 "AR5212 802.11abg NIC" SubVendor: pci 0x1014 "IBM" SubDevice: pci 0x057e Revision: 0x01 Memory Range: 0xc0210000-0xc021ffff (rw,non-prefetchable) IRQ: 11 (8756 events) Module Alias: "pci:v0000168Cd00001014sv00001014sd0000057Ebc02sc00i00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge)