Some wireless cards are not reported as being in the WIRELESS category by udev_resource
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Checkbox |
Fix Released
|
High
|
Sylvain Pineau |
Bug Description
At least on this Samsung N310, I've noticed that the tests in wireless.txt.in have been skipped. Checking their dependencies shows that they depend on a device of the WIRELESS category being detected by udev_resource. If I run udev_resource manually and do a grep for WIRELESS I get nothing. It turns out the Atheros network card is reporting itself as an Ethernet adapter:
02:00.0 Ethernet controller: Atheros Communications Inc. AR242x / AR542x Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: Askey Computer Corp. Device 7130
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f0100000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath5k
Kernel modules: ath5k
I don't know why this is. It might be that udev_resource just has to be less strict on what it classes as a WIRELESS device.
Related branches
- Brendan Donegan (community): Approve
- Sylvain Pineau (community): Needs Resubmitting
-
Diff: 47 lines (+11/-1)2 files modifiedcheckbox/parsers/udevadm.py (+8/-1)
debian/changelog (+3/-0)
- Daniel Holbach: Approve
- Micah Gersten: Needs Fixing
- Ubuntu branches: Pending requested
-
Diff: 4032 lines (+691/-1663)52 files modifiedbackend (+7/-3)
checkbox/parsers/udevadm.py (+8/-1)
data/whitelists/default.whitelist (+1/-0)
debian/changelog (+56/-0)
debian/control (+7/-2)
debian/po/ast.po (+2/-2)
debian/po/cs.po (+2/-2)
debian/po/de.po (+2/-2)
debian/po/en_AU.po (+2/-2)
debian/po/en_GB.po (+2/-2)
debian/po/es.po (+4/-3)
debian/po/fr.po (+13/-13)
debian/po/he.po (+2/-2)
debian/po/hu.po (+2/-2)
debian/po/id.po (+2/-2)
debian/po/it.po (+2/-2)
debian/po/ja.po (+2/-2)
debian/po/nl.po (+2/-2)
debian/po/oc.po (+2/-2)
debian/po/pl.po (+2/-2)
debian/po/pt_BR.po (+2/-2)
debian/po/ro.po (+2/-2)
debian/po/ru.po (+2/-2)
debian/po/tr.po (+2/-2)
debian/po/uk.po (+2/-2)
debian/po/zh_CN.po (+2/-2)
debian/po/zh_TW.po (+2/-2)
jobs/cpu.txt.in (+1/-0)
jobs/esata.txt.in (+0/-6)
jobs/firewire.txt.in (+0/-6)
jobs/mediacard.txt.in (+0/-48)
jobs/optical.txt.in (+90/-52)
jobs/resource.txt.in (+1/-1)
jobs/usb.txt.in (+7/-19)
jobs/wireless.txt.in (+17/-3)
plugins/apport_prompt.py (+0/-280)
plugins/backend_info.py (+60/-21)
plugins/suites_prompt.py (+8/-1)
po/POTFILES.in (+0/-1)
po/ar.po (+13/-12)
po/fi.po (+28/-14)
po/fr.po (+131/-109)
po/pt_BR.po (+5/-5)
qt/checkbox-qt.ui (+0/-935)
qt/frontend/qtfront.cpp (+2/-1)
qt/frontend/qtfront.ui (+8/-5)
scripts/display_resource (+84/-0)
scripts/graphics_driver (+81/-50)
scripts/network_info (+15/-2)
scripts/network_wireless_test (+0/-25)
scripts/optical_write_test (+3/-4)
setup.py (+1/-1)
Changed in checkbox: | |
milestone: | none → 0.13 |
Changed in checkbox: | |
status: | Incomplete → New |
status: | New → Confirmed |
Changed in checkbox: | |
assignee: | Marc Tardif (cr3) → nobody |
Changed in checkbox: | |
assignee: | nobody → Sylvain Pineau (sylvain-pineau) |
status: | Confirmed → In Progress |
Changed in checkbox: | |
status: | In Progress → Fix Committed |
Changed in checkbox: | |
status: | Fix Committed → Fix Released |
There might be no way to get around this other than being less strict with the requires in the wireless tests (i.e. require NETWORK instead of WIRELESS specifically). The PCI_CLASS given by udev is 20000 for the Atheros cards in both Samsung netbooks I've tried this on and 28000 anywhere else. If the devices are reporting the wrong PCI class is there anything more we can do?