Topic: Help with RT28000 Invalid RF Chipset

The content of this topic has been archived on 23 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Page 1 of 1

Post #1

doctordbx

8 Apr 2012, 16:05

If you see on This Post I have been busy porting OpenWRT to a cheap Chinese Router I acquired a few of. All is going very well, but for one small issue.

The Wireless.

The issue I am facing is this:

[   10.030000] phy0 -> rt2x00lib_request_eeprom_file: Info - Loading EEPROM data from 'RT305X.eeprom'.
[   10.300000] phy0 -> rt2x00_set_chip: Info - Chipset detected - rt: 2872, rf: 000f, rev: 0200.
[   10.320000] phy0 -> rt2800_init_eeprom: Error - Invalid RF chipset 0x000f detected.
[   10.340000] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.

And apologies for the crossy-kinda-post but I think this aspect is more relevant to development than it is to hardware hacking.

Any ideas?

Post #2

123serge123

9 Apr 2012, 15:33

While porting trunk r30372 to Dlink DIR620 revA (rt3052), I meet the same problem. Check content of the file 'RT305X.eeprom'. For unknown device firstboot may read it from /dev/mtd2 at incorrect offset. My file looks like:

 hexdump -C /lib/firmware/RT305X.eeprom
00000000  52 30 01 01 00 0c 43 30 52 88 ff ff ff ff ff ff
...

Total size of 'RT305X.eeprom' - 272 bytes, first 2 byte - chipset (in your case must be '50 30'). 6 bytes from offset 4 - wifi MAC address. You may dump all /dev/mtd2 to find correct data.

Post #3

doctordbx

9 Apr 2012, 16:25

Hi Serge,

Thanks for the reply, spookily I found out by looking at the mtd partitions that the information is actually contained in the mtd1 (uboot-env) partition. In fact, uboot-env and factory seem switched around... talk about weird, but I guess the source of the board is probably to blame. The woes continued with the chipset identifying as a ver 8 not a ver 5 (8 is for the RT3052 NOT the RT3050), which I can only surmise is because the board is also used for RT3052 chips for 2T2R, but in this case it is only a 3050. Nothing like using the same Flash settings.

So... after hardcoding the right id number in, I am still facing errors where I can only select a transmit power of.... ZERO.

Any idea on what could be going wrong here?

Post #4

123serge123

9 Apr 2012, 17:34

I found correct (?) eeprom for rt3050 (from wive-rtnl firmware source) but fail to attach file.

hexdump -C RT305X.eeprom
00000000  50 30 00 01 00 0c 43 30  50 88 ff ff ff ff ff ff
00000010  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
00000020  ff ff ff ff ff ff ff ff  00 0c 43 30 50 77 00 0c
00000030  43 30 50 66 11 05 24 00  ff ff 2f 01 55 77 a8 aa
00000040  8c 88 ff ff 0c 00 00 00  00 00 00 00 00 00 ff ff
00000050  ff ff 0d 0d 0d 0d 0c 0c  0c 0c 0c 0c 0c 0c 0c 0c
00000060  10 10 11 11 11 12 12 12  13 13 13 14 14 14 ff ff
00000070  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
*
000000d0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff 66 66
000000e0  cc aa 88 66 cc aa 88 66  cc aa 88 66 cc aa 88 66
000000f0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
*
00000110

with this eeprom-file Dlink DIR300 revB1 (rt3050) works. Txpower - see ticket 11160.

Post #5

doctordbx

9 Apr 2012, 17:41

OK here is the hexdump from my firmware

root@OpenWrt:/# hexdump -C /lib/firmware/RT305X.eeprom 
00000000  52 30 01 01 00 0c 43 30  52 83 ff ff ff ff ff ff  |R0....C0R.......|
00000010  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000020  ff ff ff ff ff ff ff ff  00 0c 43 30 52 7a 00 0c  |..........C0Rz..|
00000030  43 30 52 7b 22 08 24 00  ff ff 22 01 55 77 a8 aa  |C0R{".$...".Uw..|
00000040  8c 88 ff ff 0c 00 00 00  00 00 00 00 00 00 ff ff  |................|
00000050  ff ff 0a 0a 0a 0a 0a 0a  0b 0b 0b 0c 0d 0d 0d 0e  |................|
00000060  11 11 11 12 12 12 12 12  13 13 14 14 14 15 ff ff  |................|
00000070  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
000000d0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff 66 66  |..............ff|
000000e0  cc aa 88 66 cc aa 88 66  cc aa 88 66 cc aa 88 66  |...f...f...f...f|
000000f0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|

As for ticket 11160... this is for an RT3052 and is unresolved

I wonder where the problems are arising. Maybe I will go back a few revisions of trunk.. although I cannot see how this could improve things.

Post #6

doctordbx

9 Apr 2012, 17:47

Here is a Hexdump from another RT3050 Board I have here (not the same brand) that does work with OpenWRT.

Note this board works fine, just using it as an example of another RT3050 board

root@OpenWrt:/# hexdump -C /lib/firmware/RT305X.eeprom
00000000  50 30 01 01 c4 93 00 11  0a f0 ff ff ff ff ff ff  |P0..............|
00000010  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
00000020  ff ff ff ff ff ff ff ff  00 11 22 44 46 05 ff ff  |.........."DF...|
00000030  ff ff ff ff 11 05 24 00  ff ff 23 01 55 77 a8 aa  |......$...#.Uw..|
00000040  8c 88 ff ff 0c 00 00 00  00 00 00 00 00 00 ff ff  |................|
00000050  ff ff 16 16 16 17 17 17  17 17 18 18 18 18 18 19  |................|
00000060  10 10 11 11 11 12 12 12  13 13 13 14 14 14 ff ff  |................|
00000070  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
00000090  08 ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
000000a0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*
000000d0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff 66 66  |..............ff|
000000e0  cc aa 88 66 cc aa 88 66  cc aa 88 66 cc aa 88 66  |...f...f...f...f|
000000f0  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  |................|
*

You can see the string on line 30 (at 00000035) where it says 05 and in the one not working it says 08. I assume this to be the version of the RF chip it is reporting through to the eeprom. It is clear this eeprom is not for this chip (yikes!)

How do I fix this? (Can I fix this?) or do you have ideas on how I hack around it?

Post #7

doctordbx

9 Apr 2012, 17:48

Actually, you can see by the ID at the start... 50 30 and 52 30 shows it is for the wrong chip.

(Last edited by doctordbx on 9 Apr 2012, 17:48)

Post #8

123serge123

9 Apr 2012, 18:00

Just copy file from working device. About txpower - driver the same for rt305x. I start on Dlink DIR620 with firmware for Dlink DIR300 and it works.

Post #9

doctordbx

9 Apr 2012, 18:05

Yup, I just copied over and it reports right so that works... however... wireless still 0 TX Power.

Will roll back to an earlier revision and make a build and see what happens.

Any idea of the cause of the 0 TX Power?

Post #10

123serge123

9 Apr 2012, 18:14

Driver report txpower 0 or wireless scanners show no signal from device?

Post #11

doctordbx

9 Apr 2012, 18:17

You can see here how it reports 0 TX.

Cannot change the power, just errors. In Luci, the dropdown shows only one option... 0.

iw list
Wiphy phy0
        Band 1:
                Capabilities: 0x172
                        HT20/HT40
                        Static SM Power Save
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 2 usec (0x04)
                HT RX MCS rate indexes supported: 0-7, 32
                TX unequal modulation not supported
                HT TX Max spatial streams: 1
                HT TX MCS rate indexes supported may differ
                Frequencies:
                        * 2412 MHz [1] (0.0 dBm)
                        * 2417 MHz [2] (0.0 dBm)
                        * 2422 MHz [3] (0.0 dBm)
                        * 2427 MHz [4] (0.0 dBm)
                        * 2432 MHz [5] (0.0 dBm)
                        * 2437 MHz [6] (0.0 dBm)
                        * 2442 MHz [7] (0.0 dBm)
                        * 2447 MHz [8] (0.0 dBm)
                        * 2452 MHz [9] (0.0 dBm)
                        * 2457 MHz [10] (0.0 dBm)
                        * 2462 MHz [11] (0.0 dBm)
                        * 2467 MHz [12] (0.0 dBm) (passive scanning, no IBSS)
                        * 2472 MHz [13] (0.0 dBm) (passive scanning, no IBSS)
                        * 2484 MHz [14] (0.0 dBm) (passive scanning, no IBSS)

Devices simply cannot connect to it. They can see it, but cannot establish a connection.

(Last edited by doctordbx on 9 Apr 2012, 18:19)

Post #12

123serge123

9 Apr 2012, 18:24

Any messages from hostapd?

Post #13

doctordbx

9 Apr 2012, 18:46

no messages at all actually. Doing a full clean and rebuild and see where it takes me.

Post #14

doctordbx

9 Apr 2012, 19:02

This is from the console anyway... nothing seems to be out of the ordinary.

[  458.890000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
[  458.910000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
[  458.930000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
[  458.950000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.
[  459.200000] device wlan0 entered promiscuous mode
[  459.220000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
[  459.240000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
[  459.260000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
[  459.280000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.
[  459.300000] br-lan: port 2(wlan0) entering forwarding state
[  459.310000] br-lan: port 2(wlan0) entering forwarding state
[  459.470000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 2, CWmax: 3, Aifs: 1, TXop: 47.
[  459.550000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 3, CWmax: 4, Aifs: 1, TXop: 94.
[  459.640000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 4, CWmax: 6, Aifs: 3, TXop: 0.
[  459.720000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 4, CWmax: 10, Aifs: 7, TXop: 0.
[  462.230000] device wlan0 left promiscuous mode
[  462.230000] br-lan: port 2(wlan0) entering forwarding state
[  462.450000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 - CWmin: 3, CWmax: 4, Aifs: 2, TXop: 102.
[  462.470000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 - CWmin: 4, CWmax: 5, Aifs: 2, TXop: 188.
[  462.490000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 - CWmin: 5, CWmax: 10, Aifs: 3, TXop: 0.
[  462.510000] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 - CWmin: 5, CWmax: 10, Aifs: 7, TXop: 0.
[  462.890000] device wlan0 entered promiscuous mode
[  462.900000] br-lan: port 2(wlan0) entering forwarding state
[  462.910000] br-lan: port 2(wlan0) entering forwarding state

Post #15

jow

9 Apr 2012, 21:09

killall -9 hostapd; hostapd -dd /var/run/hostapd-phy0.conf

Also make sure to rebuild hostapd with "CONFIG_WPA_MSG_MIN_PRIORITY=0" in your global .config, otherwise most debug logging will be stripped out.

Post #16

doctordbx

10 Apr 2012, 06:29

Ok got time to add in those flags and run the command

root@OpenWrt:/# hostapd -dd /var/run/hostapd-phy0.conf
random: Trying to read entropy from /dev/random
Configuration file: /var/run/hostapd-phy0.conf
nl80211: interface wlan0 in phy phy0
nl80211: Set mode ifindex 9 iftype 2 (STATION)
nl80211: Failed to set interface 9 to mode 2: -16 (Device or resource busy)
nl80211: Interface already in requested mode - ignore error
nl80211: Subscribe to mgmt frames with non-AP handle 0x52b0e8
nl80211: Register frame type=0xd0 nl_handle=0x52b0e8
nl80211: Register frame match - hexdump(len=1): 06
nl80211: Register frame type=0xd0 nl_handle=0x52b0e8
nl80211: Register frame match - hexdump(len=2): [  169.720000] br-lan: port 2(wlan0) entering forwarding state
0a 07
[  169.730000] br-lan: port 2(wlan0) entering forwarding state
netlink: Operstate: linkmode=1, [  169.750000] br-lan: port 2(wlan0) entering forwarding state
operstate=5
nl80211: Using driver-based off-channel TX
nl80211: Interface wlan0 is in bridge br-lan
nl80211: Add own interface ifindex 6
nl80211: Add own interface ifindex 9
nl80211: Set mode ifindex 9 iftype 3 (AP)
nl80211: Unsubscribe mgmt frames handle 0x52b0e8 (start AP)
nl80211: Setup AP - device_ap_sme=0 use_monitor=1
nl80211: Create interface iftype 6 (MONITOR)
nl80211: New interface mon.wlan0 created: ifindex=13
nl80211: Add own interface ifindex 13
[  169.880000] br-lan: port 2(wlan0) entering forwarding state
[  169.890000] br-lan: port 2(wlan0) entering forwarding state
BSS count 1, BSSID mask 00:00:00:00:00:00 (0 bits)
nl80211: Regulatory information - country=00
nl80211: 2402-2472 @ 40 MHz
nl80211: 2457-2482 @ 20 MHz
nl80211: 2474-2494 @ 20 MHz
nl80211: 5170-5250 @ 40 MHz
nl80211: 5735-5835 @ 40 MHz
nl80211: Added 802.11b mode based on 802.11g information
Allowed channel: mode=1 chan=1 freq=2412 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=2 freq=2417 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=3 freq=2422 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=4 freq=2427 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=5 freq=2432 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=6 freq=2437 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=7 freq=2442 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=8 freq=2447 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=9 freq=2452 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=10 freq=2457 MHz max_tx_power=0 dBm
Allowed channel: mode=1 chan=11 freq=2462 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=1 freq=2412 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=2 freq=2417 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=3 freq=2422 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=4 freq=2427 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=5 freq=2432 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=6 freq=2437 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=7 freq=2442 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=8 freq=2447 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=9 freq=2452 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=10 freq=2457 MHz max_tx_power=0 dBm
Allowed channel: mode=0 chan=11 freq=2462 MHz max_tx_power=0 dBm
Completing interface initialization
Mode: IEEE 802.11g  Channel: 11  Frequency: 2462 MHz
nl80211: Set freq 2462 (ht_enabled=1 sec_channel_offset=0)
RATE[0] rate=10 flags=0x1
RATE[1] rate=20 flags=0x1
RATE[2] rate=55 flags=0x1
RATE[3] rate=110 flags=0x1
RATE[4] rate=60 flags=0x0
RATE[5] rate=90 flags=0x0
RATE[6] rate=120 flags=0x0
RATE[7] rate=180 flags=0x0
RATE[8] rate=240 flags=0x0
RATE[9] rate=360 flags=0x0
RATE[10] rate=480 flags=0x0
RATE[11] rate=540 flags=0x0
wlan0: Flushing old station entries
wlan0: Deauthenticate all stations
wpa_driver_nl80211_set_key: ifindex=9 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=9 alg=0 addr=(nil) key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=9 alg=0 addr=(nil) key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_nl80211_set_key: ifindex=9 alg=0 addr=(nil) key_idx=3 set_tx=0 seq_len=0 key_len=0
Using interface wlan0 with hwaddr c4:93:00:11:0a:f0 and ssid 'OpenWrt'
nl80211: Set beacon (beacon_set=0)
wpa_driver_nl80211_set_operstate: operstate 0->1 (UP)
netlink: Operstate: linkmode=-1, operstate=6
wlan0: Setup of interface done.
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
Add randomness: count=1 entropy=0
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x1002 ()
nl80211: Ignore interface down event since interface mon.wlan0 is up
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'mon.wlan0' added
wlan0: Event INTERFACE_STATUS (5) received
Unknown event 5
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11003 ([UP][LOWER_UP])
netlink: Operstate: linkmode=-1, operstate=6
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
nl80211: Add ifindex 6 for bridge br-lan
nl80211: Add own interface ifindex 6
RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP])
RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added
nl80211: if_removed already cleared - ignore event
wlan0: Event TX_STATUS (18) received
mgmt::deauth cb
Add randomness: count=2 entropy=1
Add randomness: count=3 entropy=2
Add randomness: count=4 entropy=3
Add randomness: count=5 entropy=4
Add randomness: count=6 entropy=5
Add randomness: count=7 entropy=6
Add randomness: count=8 entropy=7
Add randomness: count=9 entropy=8
Add randomness: count=10 entropy=9
Add randomness: count=11 entropy=10
Add randomness: count=12 entropy=11
Add randomness: count=13 entropy=12
Add randomness: count=14 entropy=13
Add randomness: count=15 entropy=14
Add randomness: count=16 entropy=15
Add randomness: count=17 entropy=16
Add randomness: count=18 entropy=17
Add randomness: count=19 entropy=18
Add randomness: count=20 entropy=19
Add randomness: count=21 entropy=20
Add randomness: count=22 entropy=21
Add randomness: count=23 entropy=22
Add randomness: count=24 entropy=23
wlan0: Event RX_MGMT (20) received
Add randomness: count=25 entropy=24
Add randomness: count=26 entropy=25
Add randomness: count=27 entropy=26
Add randomness: count=28 entropy=27
Add randomness: count=29 entropy=28
Add randomness: count=30 entropy=29
Add randomness: count=31 entropy=30
Add randomness: count=32 entropy=31
Add randomness: count=33 entropy=32
Add randomness: count=34 entropy=33
Add randomness: count=35 entropy=34
Add randomness: count=36 entropy=35
Add randomness: count=37 entropy=36
Add randomness: count=38 entropy=37
Add randomness: count=39 entropy=38
Add randomness: count=40 entropy=39
Add randomness: count=41 entropy=40
Add randomness: count=42 entropy=41
Add randomness: count=43 entropy=42
Add randomness: count=44 entropy=43
Add randomness: count=45 entropy=44
Add randomness: count=46 entropy=45
Add randomness: count=47 entropy=46
Add randomness: count=48 entropy=47
Add randomness: ^CSignal 2 received - terminating

I've tried a lot of build configs and even other firmwares from routers with similar hardware and still no joy.

Even went back to Trunk r3000 and still no joy.

Post #17

Diptendu

10 Apr 2012, 06:35

[ 10.340000] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device :

Could you insert printk statements (KERN_ALERT) from probe onwards to see whats happening ?

Post #18

doctordbx

10 Apr 2012, 07:13

Can... but have made significant progress in the last hour. The wireless seems to be working now, using trunk 31201 and 'borrowing' a proper RT3050 eeprom and inserting it (crudely) into the /lib/firmware through the buildroot.

However, the wireless TX Power in the logs and selection menus remains fixed at 0... BUT... my own analysis says it seems to be working just fine now, at a guess around 19 ~ 20. Perhaps it is fixed to only one TX Power and the hardware is reporting this back as 0. I did read somewhere about how some devices shift this.

So... at this stage... mostly working... a fair bit of tidying up to do now and some testing to do.

A lot happier now than I was an hour ago.

(Last edited by doctordbx on 10 Apr 2012, 07:24)

Post #19

doctordbx

10 Apr 2012, 07:15

Diptendu wrote:

[ 10.340000] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device :
Could you insert printk statements (KERN_ALERT) from probe onwards to see whats happening ?

Actually, the cause of this is the eeprom handing out the wrong chip configuration.

The discussion might have continued from here.

Page 1 of 1