[Bug 10195] New: rt2500 driver non functional - maybe yenta_socket issue?
bugzilla-daemon at bugzilla.ubuntu.com
bugzilla-daemon at bugzilla.ubuntu.com
Tue Apr 26 17:59:53 UTC 2005
Please do not reply to this email. You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=10195
Ubuntu | linux
Summary: rt2500 driver non functional - maybe yenta_socket issue?
Product: Ubuntu
Version: unspecified
Platform: amd64
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: linux
AssignedTo: fabbione at ubuntu.com
ReportedBy: bugzilla-ubuntu at lbedford.org
QAContact: kernel-bugs at lists.ubuntu.com
I've been trying to get the opensource rt2500-1.1.0-b2 driver to work on Ubuntu
AMD64.
It works fine on x86_32, as that's what I'm using to type this. The driver fails
to probe the
card correctly because ioremap fails.
The issue appears to be that pci_resource_start() and pci_resource_len() both
return 0. I tried the vanilla
linux 2.6.11.7 sources, and had the same issue.
I've also removed pretty much everything from the rt2500 code to see what they
were doing. It's pretty much:
pci_enable_device (pPci_Dev);
pci_request_regions(pPci_Dev, print_name)
ioremap(pci_resource_start(pPci_Dev, 0), pci_resource_len(pPci_Dev, 0))
at this point ioremap fails, and the driver stops processing.
>From lspci on x86_32:
0000:02:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference
Card (rev 01)
Subsystem: RaLink: Unknown device 2560
Flags: bus master, slow devsel, latency 64, IRQ 17
Memory at 40800000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [40] Power Management version 2
on amd64:
0000:02:00.0 Network controller: RaLink Ralink RT2500 802.11 Cardbus Reference
Card (rev 01)
Subsystem: RaLink: Unknown device 2560
Flags: slow devsel, IRQ 17
Memory at <ignored> (32-bit, non-prefetchable) [disabled]
Capabilities: [40] Power Management version 2
If you need anything else, I'll reinstall ubuntu amd64 to test.
L.
--
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
More information about the kernel-bugs
mailing list