| Summary: | ath5k wireless does not work on 2.6.35.11-83.fc14.x86_64 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James <james> |
| Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, sgruszka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-04-03 17:42:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
James
2011-02-28 19:54:10 UTC
(In reply to comment #1) > The machine is a Lenovo IdeaPad Y550P. Device: > 06:00.0 Ethernet controller: Atheros Communications Inc. AR5001 Wireless > Network Adapter (rev 01) That doesn't really tell us what the adapter is. Run lspci with the -vnn option and post the output for just that device. Also post the complete contents of /var/log/dmesg after booting each of the working and broken kernels (as separate plaintext attachments.) Working kernel: 06:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5001 Wireless Network Adapter [168c:001c] (rev 01) Subsystem: Foxconn International, Inc. Device [105b:e008] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at d7100000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Count=1 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Kernel driver in use: ath5k Kernel modules: ath5k We have no ath5k specific changes between 35.10 and .35.11, so problem must be in 802.11 stack or pci subsystem,or perhaps somewhere else. Can we get full dmesg output from working and not working kernel? Is possible to get dmesg's? |