You are not logged in.
Pages: 1
got d-link dwa-525, but it is not initializing.
[ska@myhost ska]# lspci -d 1814: -vv
05:00.0 Network controller: Ralink corp. Device 5360
Subsystem: D-Link System Inc Device 3c05
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 32 (500ns min, 1000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 5
Region 0: Memory at f8100000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
I found this info: Linux driver probably rt2800pci , but:
[root@myhost ska]# modprobe rt2800pci
[root@myhost ska]# dmesg | tail -n 4
[ 17.322441] EXT4-fs (sda1): re-mounted. Opts: commit=0
[ 17.324817] EXT4-fs (sda3): re-mounted. Opts: commit=0
[ 21.550016] eth0: no IPv6 routers present
[ 3037.390371] cfg80211: Calling CRDA to update world regulatory domain
[root@myhost ska]# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
I found also
alias pci:v00001814d0000539Fsv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d0000539Asv*sd*bc*sc*i* rt2800pci
alias pci:v00001814d00005390sv*sd*bc*sc*i* rt2800pci
in modules.alias
how to bind 5360 with rt2800pci ?
thanx
Last edited by skazska (2012-03-05 19:24:12)
Offline
You didn't provide the most important piece of info, the pci-id. lspci -nn will tell you that. Only with the id can we figure out if the device is supported.
Offline
05:00.0 Network controller [0280]: Ralink corp. Device [1814:5360]
Offline
Ah, so it's actually 5360, interesting. Unfortunately the kernel isn't aware of this device. This is the relevant part in the source:
/*
* RT2800pci module information.
*/
#ifdef CONFIG_PCI
static DEFINE_PCI_DEVICE_TABLE(rt2800pci_device_table) = {
{ PCI_DEVICE(0x1814, 0x0601) },
{ PCI_DEVICE(0x1814, 0x0681) },
{ PCI_DEVICE(0x1814, 0x0701) },
{ PCI_DEVICE(0x1814, 0x0781) },
{ PCI_DEVICE(0x1814, 0x3090) },
{ PCI_DEVICE(0x1814, 0x3091) },
{ PCI_DEVICE(0x1814, 0x3092) },
{ PCI_DEVICE(0x1432, 0x7708) },
{ PCI_DEVICE(0x1432, 0x7727) },
{ PCI_DEVICE(0x1432, 0x7728) },
{ PCI_DEVICE(0x1432, 0x7738) },
{ PCI_DEVICE(0x1432, 0x7748) },
{ PCI_DEVICE(0x1432, 0x7758) },
{ PCI_DEVICE(0x1432, 0x7768) },
{ PCI_DEVICE(0x1462, 0x891a) },
{ PCI_DEVICE(0x1a3b, 0x1059) },
#ifdef CONFIG_RT2800PCI_RT33XX
{ PCI_DEVICE(0x1814, 0x3390) },
#endif
#ifdef CONFIG_RT2800PCI_RT35XX
{ PCI_DEVICE(0x1432, 0x7711) },
{ PCI_DEVICE(0x1432, 0x7722) },
{ PCI_DEVICE(0x1814, 0x3060) },
{ PCI_DEVICE(0x1814, 0x3062) },
{ PCI_DEVICE(0x1814, 0x3562) },
{ PCI_DEVICE(0x1814, 0x3592) },
{ PCI_DEVICE(0x1814, 0x3593) },
#endif
#ifdef CONFIG_RT2800PCI_RT53XX
{ PCI_DEVICE(0x1814, 0x5390) },
{ PCI_DEVICE(0x1814, 0x539a) },
{ PCI_DEVICE(0x1814, 0x539f) },
#endif
{ 0, }
};
#endif /* CONFIG_PCI */As you can see, 0x5360 isn't there.
There's one thing you can try, no guarantee of success. After modprobe-ing the module, run this command:
echo "1814 5360" > /sys/bus/pci/drivers/rt2800pci/new_idThen run dmesg, see if it shows anything about new wireless devices.
Last edited by Gusar (2012-03-05 20:20:52)
Offline
: (
dmesg gave:
[47526.019309] rt2800pci 0000:05:00.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20
[47526.021185] phy0 -> rt2800_init_eeprom: Error - Invalid RT chipset detected.
[47526.021190] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[47526.021217] rt2800pci 0000:05:00.0: PCI INT A disabled
Offline
Bah, too bad.
You can try Ralink's driver, if it compiles: https://aur.archlinux.org/packages.php?ID=14557. That's a big "if"
Offline
Pages: 1