Modify

Opened 3 years ago

Closed 3 years ago

#18152 closed defect (fixed)

Asus RT-N18U can see only 128 meg RAM (specs say 256 on board)

Reported by: Grrruk Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: RT-N18U Cc:

Description

Just loaded CC on Asus RT-N18U, file openwrt-bcm53xx-bcm47081-asus-rt-n18u-squashfs.trx. Can't see all 256 meg RAM (specs say they have 256 meg ram on board):

root@OpenWrt:/# dmesg|grep Memory
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] Memory: 126264K/131072K available (2490K kernel code, 101K rwdata, 672K rodata, 150K init, 185K bss, 4808K reserved)
root@OpenWrt:/# free

total used free shared buffers

Mem: 126412 18888 107524 0 1520
-/+ buffers: 17368 109044
Swap: 0 0 0
root@OpenWrt:/# uname -a
Linux OpenWrt 3.14.18 #1 SMP Thu Oct 16 18:54:55 CEST 2014 armv7l GNU/Linux

Attachments (1)

rt-n18u-boot.txt (18.4 KB) - added by Grrruk 3 years ago.
Boot log from serial console

Download all attachments as: .zip

Change History (21)

comment:1 follow-up: Changed 3 years ago by anonymous

OpenWRT doesnt support >128Mb ram on that device. NEXT.

comment:2 Changed 3 years ago by Zajec

Can you provide a boot log? Wanted to see some info about this device.

Changed 3 years ago by Grrruk

Boot log from serial console

comment:3 in reply to: ↑ 1 ; follow-ups: Changed 3 years ago by Grrruk

Replying to anonymous:

OpenWRT doesnt support >128Mb ram on that device. NEXT.

Would you care to elaborate why???

comment:4 in reply to: ↑ 3 Changed 3 years ago by Zajec

Replying to Grrruk:

Replying to anonymous:

OpenWRT doesnt support >128Mb ram on that device. NEXT.

Would you care to elaborate why???

I think Linux gets unstable after enabling anything above 128 MiB, that's at least what I've heard. You can try it by yourself by editing bcm47081-asus-rt-n18u.dts and re-compiling the firmware.

comment:5 in reply to: ↑ 3 Changed 3 years ago by Zajec

Grrruk: could you find out which GPIOs control which LEDs/buttons? It would be nice to have LEDs support and buttons support (e.g. failsafe mode available).

http://wiki.openwrt.org/doc/devel/add.new.device#gpios

comment:6 Changed 3 years ago by Grrruk

WPS [GPIO11] value 1 by default, 0 when pressed
Reset [GPIO7] value 1 by default, 0 when pressed

Will try leds a little later, I don't know meaning of some led icons...

comment:7 Changed 3 years ago by Grrruk

LEDs

GPIO0 | POWER | Active low | Blue
GPIO3 | USB 2.0 | Active low | Blue
GPIO6 | WAN | Active low | Blue
GPIO9 | LAN | Active low | Blue
GPIO14 | USB 3.0 | Active low | Blue

Funny, their manual shows more leds (separate led for every LAN port) than it really has (only one LAN led).

comment:8 Changed 3 years ago by Zajec

Added LEDs and buttons in r43010 thanks!

comment:9 Changed 3 years ago by Grrruk

Well... I can't get into failsafe with r43010. Pressing rapidly WPS and Reset buttons during boot results in nothing. BTW, no failsafe packet in tcpdump, too. May be I compiled it improperly, will wait for nightly build.

Network behaves weird, too. Sometimes it works, sometimes it does not.

comment:10 Changed 3 years ago by Grrruk

Note that if I enter failsafe using serial console (f and ENTER) there is no network at all on any interface.

Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
f

  • failsafe -

BusyBox v1.22.1 (2014-10-21 14:15:21 MSK) built-in shell (ash)
Enter 'help' for a list of built-in commands.

ash: can't access tty; job control turned off

_

| |.-----.-----.-----.| | | |.----.| |_

| - |_
_ | -| | | _ _|
|_||| ||

|| W I R E L E S S F R E E D O M

-----------------------------------------------------
CHAOS CALMER (Bleeding Edge, r43010)
-----------------------------------------------------

  • 1 1/2 oz Gin Shake with a glassful
  • 1/4 oz Triple Sec of broken ice and pour
  • 3/4 oz Lime Juice unstrained into a goblet.
  • 1 1/2 oz Orange Juice
  • 1 tsp. Grenadine Syrup

-----------------------------------------------------

================= FAILSAFE MODE active ================
special commands:

  • firstboot reset settings to factory defaults
  • mount_root mount root-partition with config files

after mount_root:

  • passwd change root's password
  • /etc/config directory with config files

for more help see:
http://wiki.openwrt.org/doc/howto/generic.failsafe
=======================================================

root@(none):/etc/config# ifconfig -a
eth0 Link encap:Ethernet HWaddr AC:22:0B:99:C9:BC

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)
Interrupt:179

eth1 Link encap:Ethernet HWaddr 12:5D:F1:A3:FD:C7

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)
Interrupt:180

lo Link encap:Local Loopback

LOOPBACK MTU:65536 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:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

comment:11 Changed 3 years ago by Grrruk

Well, I loaded nightly build and alas, it does not go into failsafe to. Power led is lit and then system boots normally. I can get into failsafe via serial console, but pressing wps or reset does nothing, nothing changes on console output and nothing happens in logs. Just re-checked buttons, Reset button is still GPIO7, WPS is still GPIO11, pressing the button results in 1 going to 0, i.e. active low... For example:

Initial state:

root@OpenWrt:/tmp# ./button.sh | grep GPIO7
[GPIO7] value 1

After pressing Reset:

root@OpenWrt:/tmp# ./button.sh | grep GPIO7
[GPIO7] value 0

After releasing Reset:

root@OpenWrt:/tmp# ./button.sh | grep GPIO7
[GPIO7] value 1

BTW, power led does not behave like it did on N16. On N16 it blinked slow during initial stages of flash setup, but here power led is lit at powerup and then nothing changes.

Network is still faulty, it works about 5 times out of 10 reboots. Sometimes it works, sometimes does not. It does not matter how I reboot -- using reboot command, removing power cord or pushing power button, sometimes it does not work several times in row then it works again, etc. I suspected faulty cable, but it happens with new good ethernet cable too. And nothing like that with shibby or stock firmware.

Last edited 3 years ago by Grrruk (previous) (diff)

comment:12 Changed 3 years ago by Grrruk

Made a script in /etc/hotplug.d/button to log buttons, nothing calls it. No reaction to button presses.

comment:13 Changed 3 years ago by Grrruk

Hmmm, in latest r43032 failsafe works, but a) does not set up eth0 192.168.1.1 as described in wiki and b) does not send UDP packet about failsafe. BTW, now two leds LAN and WAN come up during failsafe prompt, so it's possible to track when to press WPS. But failsafe ends with empty eth0, without IP address.

comment:14 follow-up: Changed 3 years ago by rmilecki

Failsafe support added in r43639

If there are some *bugs* left, please create separated reports. Also please avoid creating reports for missing *features* (like 256 MiB RAM support or sth). Thanks.

comment:15 in reply to: ↑ 14 ; follow-up: Changed 3 years ago by Grrruk

Replying to rmilecki:

Failsafe support added in r43639

If there are some *bugs* left, please create separated reports.

Ugh. I did that on October 27, ticket #18233. Now eth0 is set to 192.168.1.1 in failsafe mode, but I can't test anything because of #18623.

Also please avoid creating reports for missing *features* (like 256 MiB RAM support or sth). Thanks.

Ugh. How do I know what is feature and what is bug if there is no official limit on supported ram? I searched openwrt site and wiki before filling this bug and did not find any information related to this limitation... searching google for "openwrt 128mb ram" does not yield anything too.


comment:16 in reply to: ↑ 15 Changed 3 years ago by rmilecki

Replying to Grrruk:

Ugh. How do I know what is feature and what is bug if there is no official limit on supported ram? I searched openwrt site and wiki before filling this bug and did not find any information related to this limitation... searching google for "openwrt 128mb ram" does not yield anything too.

As you already noticed, OpenWrt has a wiki. Use it. You got into from me, update the wiki, don't be lazy!
http://wiki.openwrt.org/doc/hardware/soc/soc.broadcom.bcm53xx

comment:17 Changed 3 years ago by rmilecki

Should be fixed by r43964 and r43972, can you confirm?

comment:18 Changed 3 years ago by Grrruk

Yep, it works now, free reports 256 megs.

comment:19 Changed 3 years ago by Grrruk

root@OpenWrt:/# free

total used free shared buffers

Mem: 256156 22188 233968 0 2368
-/+ buffers: 19820 236336
Swap: 0 0 0
root@OpenWrt:/# dmesg | grep Memory:
[ 0.000000] Memory: 256004K/262144K available (2642K kernel code, 99K rwdata, 724K rodata, 154K init, 234K bss, 6140K reserved, 131072K highmem)

comment:20 Changed 3 years ago by rmilecki

  • Resolution set to fixed
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.