Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 390551 - No device created for AR5212 after loading module ath5k.ko
No device created for AR5212 after loading module ath5k.ko
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-11-19 10:48 EST by Joachim Frieben
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-22 01:52:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joachim Frieben 2007-11-19 10:48:22 EST
Description of problem:
After loading kernel module ath5k.ko on a system equipped with a DWL-G520
WLAN adapter sporting an AR5212 chipset, no corresponding device ath0 is

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Boot system into single user mode.
2. Load ath5k.ko [modprobe ath5k].
Actual results:
dmesg reports "ath_pci 0000:01:0a.0: can't get channels
  ACPI: PCI interrupt for device 0000:01:0a.0 disabled
  ath_pci: probe of 0000:01:0a.0 failed with error -22"

Expected results:
  Module ath5k.ko is loaded, and the corresponding device gets created.

Additional info:
  This used to work better for 2.6.23.x kernels, see bug 254192, where
  the device was created correctly, and only DHCP failed to establish a
  working network connection.
Comment 1 Joachim Frieben 2007-11-19 17:09:27 EST
Same behaviour for kernel-2.6.24-0.39.rc3.git1.fc9.
Comment 2 Joachim Frieben 2007-11-22 01:52:49 EST
Fixed in kernel-2.6.24-0.41.rc3.git1.fc9.

Note You need to log in before you can comment on or make changes to this bug.