I've got an 3Com 3CRPCIN175 installed but when calling iwconfig no
device is listed.
The following dmesg is logged:
[ 14.875549] ACPI: PCI Interrupt 0000:02:0c.0[A] -> GSI 20 (level,
low) -> IRQ 20
[ 14.882920] phy0 -> rt61pci_init_eeprom: Error - Invalid RF chipset
detected.
[ 14.882966] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate
device.
[ 14.883024] ACPI: PCI interrupt for device 0000:02:0c.0 disabled
lspci reports:
02:0c.0 Unclassified device [0080]: RaLink RT2600 802.11 MIMO
hence I suspect that the firmware-ralink should be the correct driver
for this device and it ought to work with the 3Com card.
I've also tested the latest testing build of firmware-ralink (version
0.18) which reports the same dmesg.
kernel: debian-server 2.6.26-2-686
(also tested with latest testing kernel: 2.6.30-2-686)
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Please send the output of:
lspci -vv -n -d 1814:
> hence I suspect that the firmware-ralink should be the correct driver
> for this device and it ought to work with the 3Com card.
Actually, firmware-ralink contains firmware, not a driver. The driver
(rt61pci) is part of the kernel package.
> I've also tested the latest testing build of firmware-ralink (version
> 0.18) which reports the same dmesg.
>
> kernel: debian-server 2.6.26-2-686
> (also tested with latest testing kernel: 2.6.30-2-686)
Please also test 2.6.31-trunk-686 from experimental (this is meant to be
in unstable now, but there is a delay in adding new binary packages to
unstable).
Ben.
--
Ben Hutchings
The generation of random numbers is too important to be left to chance.
- Robert Coveyou
debian-server:~#
>> hence I suspect that the firmware-ralink should be the correct driver
>> for this device and it ought to work with the 3Com card.
>>
>
> Actually, firmware-ralink contains firmware, not a driver. The driver
> (rt61pci) is part of the kernel package.
>
Oh u'r absolutely right of course. :-) Thanks for reassigning the bug to
the proper package.
>> I've also tested the latest testing build of firmware-ralink (version
>> 0.18) which reports the same dmesg.
>>
>> kernel: debian-server 2.6.26-2-686
>> (also tested with latest testing kernel: 2.6.30-2-686)
>>
> Please also test 2.6.31-trunk-686 from experimental (this is meant to be
> in unstable now, but there is a delay in adding new binary packages to
> unstable).
>
I've been trying for an hour now getting the kernel from experimental
but failed. I've tried adding the following entry to the sources.list
file, but aptitude could not find any 2.6.31 version.
deb http://ftp.debian.org/debian/ experimental main contrib non-free
I don't see any listed kernel in
http://packages.debian.org/experimental/kernel/ either.
FYI:
I've also tried manually building the latest driver version available at
the ralink page:
http://www.ralinktech.com/support.php?s=2
RT2501PCI/mPCI/CB(RT61:RT2561/RT2561S/RT2661) - 01/23/2009 - 1.1.2.3
When using this driver, the card showed up iwconfig.
Stefan
You should install linux-image-2.6.31-trunk-686. Upgrading
linux-latest-2.6-686 will not work..
> I don't see any listed kernel in
> http://packages.debian.org/experimental/kernel/ either.
The source package is 'linux-2.6', not 'kernel'.
> FYI:
> I've also tried manually building the latest driver version available at
> the ralink page:
> http://www.ralinktech.com/support.php?s=2
> RT2501PCI/mPCI/CB(RT61:RT2561/RT2561S/RT2661) - 01/23/2009 - 1.1.2.3
> When using this driver, the card showed up iwconfig.
Ralink's official driver has somewhat better hardware support but is so
poorly integrated with the kernel wireless networking system that
external developers ending up writing a completely new driver for
inclusion in the kernel. If it works for you, that's great, but rt61pci
still needs to be fixed.