From: Treeve Jelbert <treeve@scarlet.be>
To: linux-kernel@vger.kernel.org
Subject: [NETWORKING DRIVERS RT2X00] please add support for Asus PCE-N53 (0x1814, 0x5592)
Date: Tue, 23 Jul 2013 12:49:17 +0200 [thread overview]
Message-ID: <2108818.T0lx4Vi2Ui@horos> (raw)
linux-3.10.0 does not support device (0x1814, 0x5592) Asus PCE-N53 which I
would like to use on with 5GHz network.
#lspci
02:00.0 Network controller: Ralink corp. Device 5592
Subsystem: ASUSTeK Computer Inc. Device 851a
# lspci -d :5592 -nn
02:00.0 Network controller [0280]: Ralink corp. Device [1814:5592]
#modprobe rt2x00pci
[ 2724.173984] cfg80211: Calling CRDA to update world regulatory domain
device id (0x1814, 0x5592) 'Asus PCE-N53' not present in rt2800pci.c
After adding this device id , it get the following messages
[ 8.993741] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading
firmware file 'rt2860.bin'
[ 8.994857] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware
detected - version: 0.34
[ 9.073053] NET: Registered protocol family 17
[ 10.438586] ieee80211 phy0: rt2x00lib_rxdone_read_signal: Warning - Frame
received with unrecognized signal, mode=0x0000, signal=0x0000, type=4
[ 69.171225] ieee80211 phy0: rt2x00lib_rxdone: Error - Wrong frame size 0
max 3840
#lsmod
rt2800pci 9514 0
eeprom_93cx6 1913 1 rt2800pci
rt2x00pci 2368 1 rt2800pci
rt2800lib 52747 1 rt2800pci
crc_ccitt 1235 1 rt2800lib
rt2x00mmio 2425 1 rt2800pci
rt2x00lib 30593 4 rt2x00pci,rt2800lib,rt2800pci,rt2x00mmio
led_class 2531 1 rt2x00lib
mac80211 209216 3 rt2x00lib,rt2x00pci,rt2800lib
#ifconfig
wlan0 Link encap:Ethernet HWaddr 30:85:A9:F4:B6:61
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
reply other threads:[~2013-07-23 10:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2108818.T0lx4Vi2Ui@horos \
--to=treeve@scarlet.be \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox