OpenWrt Forum Archive

Topic: Update on Linksys WRT1900AC support

The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

Post #2126
DavidMcWRT
7 Jan 2015, 01:04
oguzhane wrote:
DavidMcWRT wrote:

Question from me for once smile

Stock has a single button to turn off the LEDs (except for the power).

Can this be done in the current CC Trunk builds?

I know about the LED settings screen, but can only see options for "triggers" and wouldn't know how (if possible) to merely just disable (all) the various lights.

I don't own this router, following very closely and will hopefully purchase one soon.  To change the state of the LEDs in my AR71xx based router, I do the following:

echo 0 > "/sys/class/leds/netgear:green:power/brightness"
echo 0 > /sys/class/leds/ath9k-phy1/brightness
echo 0 > /sys/class/leds/ath9k-phy0/brightness
/sbin/swconfig dev rtl8366s port 1 set led 0

You can probably figure out the various sysfs files for this device's LEDs.

After I found these, I put the commands in my /etc/rc.local

Hope that helps

Thanks for the pointers.

There are 17 files in /sys/class/leds/ for me

Only two are set to 255 (all others are zero), the power and the wan lights.  I can turn them off with:

echo 0 > /sys/class/leds/mamba\:white\:power/brightness
echo 0 > /sys/class/leds/tlc59116\:1/brightness

However, the front led indicators for the ethernet ports and WiFi radios remain on/working and I'm trying to work out how they may be disabled.

/etc/init.d/led
/etc/init.d/rssileds

are the services started that seem to set up the leds.  I've tried disabling both services in the startup section and rebooting (losing my two day uptime hmm) but all leds were working on re-boot even with those services disabled.


I have a feeling the ethernet/WiFi leds must be being run by some other mechanism, because when doing:

rmmod leds_tlc59116

the damn things are still working, while /sys/class/leds/ becomes empty except for the power light LED's settings.

(Last edited by DavidMcWRT on 7 Jan 2015, 02:20)

Post #2127
DavidMcWRT
7 Jan 2015, 01:13
lifehacksback wrote:

@DavidMcWRT

I've done some rearranging and would like to ask you to update the wiki with this url: http://tinyurl.com/CC-lifehacksback-Known-Good

Thanks big_smile

I see that the Wiki's been updated by someone.

I also updated my original post on here with the new link.

(Last edited by DavidMcWRT on 7 Jan 2015, 02:20)

Post #2128
rip057
7 Jan 2015, 01:38
LookingForMyMojo wrote:
rip057 wrote:

well i finally finished getting what i want out of this build... no pivot overlay, but i shrunk it so much that all its good for now is some conf file ...  build ended up being 31MB but its all good, I got EVERY single package i want made and included...

thanks to all that helped... its free for anyone who wants it let me know

I'm very curious to try it, can you post it?

Well just so you know the packages that are in the build
A ton of the coreutils Bash Gawk Sed Grep
Ngrep Nmap ncat Nping Aircrack-ng Gcc Binutils Make Whob Bc Od Wc Sort Uniq Mwan configs Iptables and a lot of the extensions.. im just going to make xtables natively like I did the last time Printf All usb modules Vsftpd Wput Wget Iftop Htop Conntrackd Syslog-ng a bunch of the.luci apps like qos and upnp

Things I stayed away from
Anything ipv6 anything other than extfs utils andno file sharing or torrents packages, no samba no cups no point..

I use all these for my hosts on steam...
Now to get the firewall rules right

I want it set up like
Local eth ETH0
Wan conn. ETH1
Wireless wan 0 WLAN
Wireless 1 WWAN
ETH0 WLAN lanbr
Wwan Lo wwanbr
Lanbr eth1 wanbr

Then its not so confusing all the meat goes in the wan br and no more rats maze and moat... only one set of forward on the wanbr... keep it.simple right

Post #2129
DavidMcWRT
7 Jan 2015, 01:43

brace for incoming!

In their coverage of the announcement of the new WRT1200AC (802.11n (2.4 GHz) up to 400 Mbps, 802.11ac (5 GHz): up to 867 Mbps), ZDNet have mixed in reports about the current status of OpenWRT on the WRT1900AC.

Confusingly, they've linked to the trunk snapshot firmware when talking about the driver now being included in OpenWRT, although note against the link that "only Linux and OpenWrt experts should try to work with it".

They later (also) give a link to the Wiki that includes the links to the three builds (Chadster's, lifehacksback's and Kaloz's) and note that these are for "WRT1900AC owners", so we might now get (more) people trying one of the three builds based on that.

Finally, while they've quoted my soundbite-like "It's been a bit of a rocky ride, but we've got there in the end" post in the article, they've regrettably attributed it to "a member of the OpenWRT developers team", which I'm definitely not!

I couldn't find a way of emailing the author to get him to correct the inaccuracies sad

(I'd actually been wondering if Linksys would roll out further routers designed for OpenWRT and it looks like they are indeed following through.  OpenWRT support is supposed to be going to be ready for the WRT1200AC's release...)

Full article:
http://www.zdnet.com/article/ces-2015-l … fi-router/

(Last edited by DavidMcWRT on 7 Jan 2015, 02:22)

Post #2130
DavidMcWRT
7 Jan 2015, 01:58
DavidMcWRT wrote:

I have a feeling the ethernet/WiFi leds must be being run by some other mechanism, because when doing:

rmmod leds_tlc59116

the damn things are still working

And they're still flashing away even when I also rmmod ledtrig_gpio, ledtrig_heartbeat, ledtrig_transient, ledtrig_usbdev and xt_LED

(Last edited by DavidMcWRT on 7 Jan 2015, 02:04)

Post #2131
DavidMcWRT
7 Jan 2015, 02:07

I have some bad blocks on my router as seen in the kernel log:

[    1.004901] Bad block table found at page 65472, version 0x01
[    1.010940] Bad block table found at page 65408, version 0x01

Given that the unit's only a few months old, should this be expected (so soon)?

(Last edited by DavidMcWRT on 7 Jan 2015, 02:07)

Post #2132
lonniereeder
7 Jan 2015, 03:08

I took the plunge and flashed Lifehacks 3.18.1 version onto my WRT1900AC. I can get everything up and running and seems to be performing just fine. There was a little bit of a learning curve to learn where everything was, and I am still not sure I got everything setup yet. But I love the options and flexibility that this firmware gives me.

I need some help, I got the 2.4 ghz wifi to work, but I cannot get the 5.0ghz one to work. Here are the setups I have for both the 2.4/5.0 ghz:

2.4Ghz setup
Operating Freq
- Mode=N, Band=2.4Ghz,Channel=Auto, width=20Mhz
Transmit Power = 20dBm

Under Interfaces
ESSID =bender
Mode = Access Point
Network = LAN is selected

Security - WPAS-PSK, Forced CCMP(AES)

When it is enabled it shows up as Mode=Master
And laptops and Android phones/tablets can connect just fine.

5.0Ghz setup

Operating Freq
- Mode=N, Freq=5.0Ghz, Channel=Auto, Width=40
Transmit Power=17dBm

Under Interface setup
ESSID=mordor
Mode=Access point

Security is setup the same as 2.4ghz, password is different

when it enable this radio it comes up as Mode client and tells me it is either disabled or not associated and will not turn on.

I know I have something setup wrong, just not sure where I went wrong. I don't have a lot of devices that use the 5.0ghz range but I would like to have it available if I can get it working. My first thought is that I have the 2.4 setup incorrectly as an access point, but I could not get it work any other way.

Any help will be greatly appreciated.

Post #2133
tusc
7 Jan 2015, 03:25
DavidMcWRT wrote:
lifehacksback wrote:

@DavidMcWRT

I've done some rearranging and would like to ask you to update the wiki with this url: http://tinyurl.com/CC-lifehacksback-Known-Good

Thanks big_smile

I see that the Wiki's been updated by someone.

I also updated my original post on here with the new link.

It looks like lifehacksback beat me to it which is fine as the wiki is there for everyone to contribute.

Post #2134
tusc
7 Jan 2015, 03:27
DavidMcWRT wrote:

I have some bad blocks on my router as seen in the kernel log:

[    1.004901] Bad block table found at page 65472, version 0x01
[    1.010940] Bad block table found at page 65408, version 0x01

Given that the unit's only a few months old, should this be expected (so soon)?

I have the same exact message in my log too. It seems to be common with other routers if you google the message.

(Last edited by tusc on 7 Jan 2015, 03:29)

Post #2135
raven-au
7 Jan 2015, 03:58
lonniereeder wrote:

I need some help, I got the 2.4 ghz wifi to work, but I cannot get the 5.0ghz one to work. Here are the setups I have for both the 2.4/5.0 ghz:

2.4Ghz setup
Operating Freq
- Mode=N, Band=2.4Ghz,Channel=Auto, width=20Mhz
Transmit Power = 20dBm

Under Interfaces
ESSID =bender
Mode = Access Point
Network = LAN is selected

Security - WPAS-PSK, Forced CCMP(AES)

When it is enabled it shows up as Mode=Master
And laptops and Android phones/tablets can connect just fine.

5.0Ghz setup

Operating Freq
- Mode=N, Freq=5.0Ghz, Channel=Auto, Width=40
Transmit Power=17dBm

Under Interface setup
ESSID=mordor
Mode=Access point

Security is setup the same as 2.4ghz, password is different

when it enable this radio it comes up as Mode client and tells me it is either disabled or not associated and will not turn on.

Interesting, I have pretty much the opposite problem.

My 2.4Ghz band doesn't work and I have tried a number of configurations including what you have above.
I continually get invalid password when trying to connect.

But my 5Ghz is different.
I have Mode set to AC, have selected a specific channel and the width is set to 80.
My N devices connect just fine to it at a lower width so the mode AC seems to cover N.

I noticed that the passphrase can often change to the router password so you need to be careful about that.
I just ssh into the device and check /etc/config/wireless has the correct "option key" setting after changes has been made.

Ian

Post #2136
rip057
7 Jan 2015, 04:20

I got the bad blocks too, but I havent checked my build which is.working absolutely fine... both radios are fine, but something I have noticed is that with firefox luci hangs on previously sent data and gets really confused, so if your having radio issues it could be that you have saved some of the sent data like a password... try going incognito and doing it or switching browsers... it could be that some glitch has your browser and luci not changing it oe changing and then you hit alt back and it undoes it

Post #2137
weedv2
7 Jan 2015, 05:05
lonniereeder wrote:

5.0Ghz setup

Operating Freq
- Mode=N, Freq=5.0Ghz, Channel=Auto, Width=40
Transmit Power=17dBm

Under Interface setup
ESSID=mordor
Mode=Access point

Channel=Auto does not seem to work for 5Ghz, i would recommend manually setting the channel.
You can use a tool like inSSIDer to find what networks arent used/have low usage
http://www.majorgeeks.com/files/details/inssider.html

(Last edited by weedv2 on 7 Jan 2015, 05:05)

Post #2139
rip057
7 Jan 2015, 09:22

my build, not that i really was planning on sharing but something that worked for me at least it will once i have this crazy jacked up iptables ruleset corrected is here very temporarily

ftp://76.72.43.9/openwrt-mvebu-armada-x … actory.img

Post #2140
incorrect
7 Jan 2015, 11:29
lonniereeder wrote:

…

I need some help, I got the 2.4 ghz wifi to work, but I cannot get the 5.0ghz one to work. Here are the setups I have for both the 2.4/5.0 ghz:

….

I had similar problems, and couldn't make it work by configuring via the web UI.

Try logging in via ssh and run the following, it should indicate why it's failing.

/usr/sbin/hostapd -P /var/run/wifi-phy0.pid -B /var/run/hostapd-phy0.conf
/usr/sbin/hostapd -P /var/run/wifi-phy1.pid -B /var/run/hostapd-phy1.conf

The best place to configure what's wrong is in 

/etc/config/wireless

then run 

wifi

to reload the config.

One caveat, and I don't know if it makes any difference, but I also reordered the entries for my config file as such:

config wifi-device 'radio0'
    option type 'mac80211'
    option path 'soc/soc:pcie-controller/pci0000:00/0000:00:02.0/0000:02:00.0'
    option hwmode '11g'
    option htmode 'HT40'
    option txpower '17'
    option country 'AU'
    option channel '13'

config wifi-device 'radio1'
    option type 'mac80211'
    option path 'soc/soc:pcie-controller/pci0000:00/0000:00:03.0/0000:03:00.0'
    option hwmode '11a'
    option channel '36'
    option htmode 'VHT80'
    option txpower '17'
    option country 'AU'

config wifi-iface
    option device 'radio0'
    option mode 'ap'
    option ssid 'blah-diddy'
    option network 'lan'
    option key '+##***###***'
    option encryption 'psk2+ccmp'

config wifi-iface
    option device 'radio1'
    option mode 'ap'
    option ssid 'blah-diddy'
    option network 'lan'
    option key '+##***###***'
    option encryption 'psk2+ccmp'
Post #2141
carlos.quiron
7 Jan 2015, 12:24

Anyone try configure the switch module?
Create interfaces vlan (L3), give them one IP and apply vlan to specific ports ?
I Need to configure 2 networks (one for My home network and other for IPTV stuff) and made some routes between them, but I'm a little confused with the L2 structure/configuration of this router.

Is there any chance to put switch tab working in Luci. My linux knowledge is a bit limited smile

Post #2142
Abitrary
7 Jan 2015, 14:47

I have failed unbrick.
below message is appeared.
I had been used stock img and openwrt img.
Both is the same.
Please, let me know advice for unbrick.
Thank you.

Marvell>> setenv firmware_name openwrt2.img
Marvell>> setenv ipaddr 192.168.1.1
Marvell>> setenv netmask 255.255.255.0
Marvell>> setenv serverip 192.168.1.2
Marvell>> run update_both_images
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt2.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0xa00000, size 0x4000000
Erasing at 0x49e0000 -- 100% complete.
OK

NAND write: device 0 offset 0xa00000, size 0x1e00000
31457280 bytes written: OK
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt2.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0x3200000, size 0x4000000
Erasing at 0x71e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x3200000, size 0x1e00000
31457280 bytes written: OK
Marvell>>
Marvell>> reset
resetting ...

BootROM 1.20
Booting from NAND flash
Step 1: First phase of PEX-PIPE Configuration
Step 2: Configure the desire PIN_PHY_GEN
Step 3 QSGMII enable
Step 4: Configure SERDES MUXes
Step 5: Activate the RX High Impedance Mode
Step 6: [PEX-Only] PEX-Main configuration (X4 or X1)
Step 6.2: [PEX-Only] PCI Express Link Capabilities
Step 7: [PEX-X4 Only] To create PEX-Link
Steps 7,8,9,10 and 11
Steps 12: [PEX-Only] Last phase of PEX-PIPE ConfigurationSteps 13: Wait 15ms before checking resultsSteps 14: [PEX-Only]  In order to configureSteps 15: [PEX-Only]  In order to configureSteps 16: [PEX-Only] Training Enablestep 17: max_if= 0x7
step 17:  PEX0  pexUnit= 0
** Link is Gen1, check the EP capability
--> 0050
mvPexConfigRead: return addr=0x%x0050
--> 7001
--> 7001
--> A005
--> A005
--> 0010
--> 4C12
Gen2 client!
step 17:  PEX1  pexUnit= 0
step 17:  PEX2  pexUnit= 0
** Link is Gen1, check the EP capability
--> 0040
mvPexConfigRead: return addr=0x%x0040
--> 5001
--> 5001
--> 7005
--> 7005
--> 0010
--> DC12
Gen2 client!
step 17:  PEX3  pexUnit= 0
PEX3 : Detected No Link. Status Reg(0x0004DA64) = 0x00000001
step 17:  PEX4  pexUnit= 1
PEX4 : Detected No Link. Status Reg(0x00081A64) = 0x00000001
step 17:  PEX5  pexUnit= 1
PEX5 : Detected No Link. Status Reg(0x00085A64) = 0x00000001
step 17:  PEX6  pexUnit= 1
PEX6 : Detected No Link. Status Reg(0x00089A64) = 0x00000001
                                                            DDR3 Training Sequence - Ver 4.5.DDR3 Training Sequence - Static MC Init
DDR3 Training Sequence - HW Training Procedure
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
BootROM: Image checksum verification PASSED

__   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
** LOADER **


U-Boot 2011.12 (Feb 06 2014 - 17:14:13) Marvell version: v2011.12 2013_Q1.2

Boot version:v1.3.25

Board: RD-AXP-GP rev 1.0
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 600 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  256 MiB

Map:   Code:            0x0fea7000:0x0ff5e2d4
       BSS:             0x0ffefd80
       Stack:           0x0f9a6ef8
       Heap:            0x0f9a7000:0x0fea7000

NAND:  Spansion 1Gb(ID=F101) 128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01


#### auto_recovery ####
[u_env] get auto_recovery == no
[u_env] get auto_recovery == no
[u_env] get boot_part == 2
[u_env] get boot_part_ready == 3
auto_recovery enabled:0, boot_part:2, boot_part_ready:3

PEX 0.0(0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Root Complex Interface, Detected Link X1, GEN 1.1
PEX 0.2(2): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.3(3): Detected No Link.
PEX 1.0(4): Detected No Link.
PEX 1.1(5): Detected No Link.
PEX 1.2(6): Detected No Link.

boot_end Offset: 0x100000
u_env_off Offset: 0x100000
s_env_off Offset: 0x140000
devinfo Offset: 0x900000

===================
total_badCount: 0
boot_badCount: 0
u_env_badCount: 0
s_env_badCount: 0
buff_badCount: 0
===================

FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:
mvEthE6171SwitchBasicInit finished
Net:   mvSysNetaInit enter
set port 0 to rgmii enter
set port 1 to rgmii enter
egiga0 [PRIME], egiga1
modify Phy Status
auto_recovery_check changes bootcmd: run altnandboot
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x3200000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>>

Post #2143
Abitrary
7 Jan 2015, 15:18
Abitrary wrote:

I have failed unbrick.
below message is appeared.
I had been used stock img and openwrt img.
Both is the same.
Please, let me know advice for unbrick.
Thank you.

Marvell>> setenv firmware_name openwrt2.img
Marvell>> setenv ipaddr 192.168.1.1
Marvell>> setenv netmask 255.255.255.0
Marvell>> setenv serverip 192.168.1.2
Marvell>> run update_both_images
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt2.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0xa00000, size 0x4000000
Erasing at 0x49e0000 -- 100% complete.
OK

NAND write: device 0 offset 0xa00000, size 0x1e00000
31457280 bytes written: OK
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt2.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0x3200000, size 0x4000000
Erasing at 0x71e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x3200000, size 0x1e00000
31457280 bytes written: OK
Marvell>>
Marvell>> reset
resetting ...

BootROM 1.20
Booting from NAND flash
Step 1: First phase of PEX-PIPE Configuration
Step 2: Configure the desire PIN_PHY_GEN
Step 3 QSGMII enable
Step 4: Configure SERDES MUXes
Step 5: Activate the RX High Impedance Mode
Step 6: [PEX-Only] PEX-Main configuration (X4 or X1)
Step 6.2: [PEX-Only] PCI Express Link Capabilities
Step 7: [PEX-X4 Only] To create PEX-Link
Steps 7,8,9,10 and 11
Steps 12: [PEX-Only] Last phase of PEX-PIPE ConfigurationSteps 13: Wait 15ms before checking resultsSteps 14: [PEX-Only]  In order to configureSteps 15: [PEX-Only]  In order to configureSteps 16: [PEX-Only] Training Enablestep 17: max_if= 0x7
step 17:  PEX0  pexUnit= 0
** Link is Gen1, check the EP capability
--> 0050
mvPexConfigRead: return addr=0x%x0050
--> 7001
--> 7001
--> A005
--> A005
--> 0010
--> 4C12
Gen2 client!
step 17:  PEX1  pexUnit= 0
step 17:  PEX2  pexUnit= 0
** Link is Gen1, check the EP capability
--> 0040
mvPexConfigRead: return addr=0x%x0040
--> 5001
--> 5001
--> 7005
--> 7005
--> 0010
--> DC12
Gen2 client!
step 17:  PEX3  pexUnit= 0
PEX3 : Detected No Link. Status Reg(0x0004DA64) = 0x00000001
step 17:  PEX4  pexUnit= 1
PEX4 : Detected No Link. Status Reg(0x00081A64) = 0x00000001
step 17:  PEX5  pexUnit= 1
PEX5 : Detected No Link. Status Reg(0x00085A64) = 0x00000001
step 17:  PEX6  pexUnit= 1
PEX6 : Detected No Link. Status Reg(0x00089A64) = 0x00000001
                                                            DDR3 Training Sequence - Ver 4.5.DDR3 Training Sequence - Static MC Init
DDR3 Training Sequence - HW Training Procedure
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
BootROM: Image checksum verification PASSED

__   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
** LOADER **


U-Boot 2011.12 (Feb 06 2014 - 17:14:13) Marvell version: v2011.12 2013_Q1.2

Boot version:v1.3.25

Board: RD-AXP-GP rev 1.0
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 600 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  256 MiB

Map:   Code:            0x0fea7000:0x0ff5e2d4
       BSS:             0x0ffefd80
       Stack:           0x0f9a6ef8
       Heap:            0x0f9a7000:0x0fea7000

NAND:  Spansion 1Gb(ID=F101) 128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01


#### auto_recovery ####
[u_env] get auto_recovery == no
[u_env] get auto_recovery == no
[u_env] get boot_part == 2
[u_env] get boot_part_ready == 3
auto_recovery enabled:0, boot_part:2, boot_part_ready:3

PEX 0.0(0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Root Complex Interface, Detected Link X1, GEN 1.1
PEX 0.2(2): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.3(3): Detected No Link.
PEX 1.0(4): Detected No Link.
PEX 1.1(5): Detected No Link.
PEX 1.2(6): Detected No Link.

boot_end Offset: 0x100000
u_env_off Offset: 0x100000
s_env_off Offset: 0x140000
devinfo Offset: 0x900000

===================
total_badCount: 0
boot_badCount: 0
u_env_badCount: 0
s_env_badCount: 0
buff_badCount: 0
===================

FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:
mvEthE6171SwitchBasicInit finished
Net:   mvSysNetaInit enter
set port 0 to rgmii enter
set port 1 to rgmii enter
egiga0 [PRIME], egiga1
modify Phy Status
auto_recovery_check changes bootcmd: run altnandboot
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x3200000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>>


I have been unbriked.
I'm very stupid.
I have not conect lan cable.

Thanks for all.

Post #2144
DavidMcWRT
7 Jan 2015, 15:22
tusc wrote:
DavidMcWRT wrote:

I have some bad blocks on my router as seen in the kernel log:

[    1.004901] Bad block table found at page 65472, version 0x01
[    1.010940] Bad block table found at page 65408, version 0x01

Given that the unit's only a few months old, should this be expected (so soon)?

I have the same exact message in my log too. It seems to be common with other routers if you google the message.

Thanks for the reassurance.

Post #2145
LookingForMyMojo
7 Jan 2015, 15:59
Abitrary wrote:
Abitrary wrote:

I have failed unbrick.
below message is appeared.
I had been used stock img and openwrt img.
Both is the same.
Please, let me know advice for unbrick.
Thank you.

Marvell>> setenv firmware_name openwrt2.img
Marvell>> setenv ipaddr 192.168.1.1
Marvell>> setenv netmask 255.255.255.0
Marvell>> setenv serverip 192.168.1.2
Marvell>> run update_both_images
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt2.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0xa00000, size 0x4000000
Erasing at 0x49e0000 -- 100% complete.
OK

NAND write: device 0 offset 0xa00000, size 0x1e00000
31457280 bytes written: OK
mvNetaSpeedDuplexSet
Using egiga0 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'openwrt2.img'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again

NAND erase: device 0 offset 0x3200000, size 0x4000000
Erasing at 0x71e0000 -- 100% complete.
OK

NAND write: device 0 offset 0x3200000, size 0x1e00000
31457280 bytes written: OK
Marvell>>
Marvell>> reset
resetting ...

BootROM 1.20
Booting from NAND flash
Step 1: First phase of PEX-PIPE Configuration
Step 2: Configure the desire PIN_PHY_GEN
Step 3 QSGMII enable
Step 4: Configure SERDES MUXes
Step 5: Activate the RX High Impedance Mode
Step 6: [PEX-Only] PEX-Main configuration (X4 or X1)
Step 6.2: [PEX-Only] PCI Express Link Capabilities
Step 7: [PEX-X4 Only] To create PEX-Link
Steps 7,8,9,10 and 11
Steps 12: [PEX-Only] Last phase of PEX-PIPE ConfigurationSteps 13: Wait 15ms before checking resultsSteps 14: [PEX-Only]  In order to configureSteps 15: [PEX-Only]  In order to configureSteps 16: [PEX-Only] Training Enablestep 17: max_if= 0x7
step 17:  PEX0  pexUnit= 0
** Link is Gen1, check the EP capability
--> 0050
mvPexConfigRead: return addr=0x%x0050
--> 7001
--> 7001
--> A005
--> A005
--> 0010
--> 4C12
Gen2 client!
step 17:  PEX1  pexUnit= 0
step 17:  PEX2  pexUnit= 0
** Link is Gen1, check the EP capability
--> 0040
mvPexConfigRead: return addr=0x%x0040
--> 5001
--> 5001
--> 7005
--> 7005
--> 0010
--> DC12
Gen2 client!
step 17:  PEX3  pexUnit= 0
PEX3 : Detected No Link. Status Reg(0x0004DA64) = 0x00000001
step 17:  PEX4  pexUnit= 1
PEX4 : Detected No Link. Status Reg(0x00081A64) = 0x00000001
step 17:  PEX5  pexUnit= 1
PEX5 : Detected No Link. Status Reg(0x00085A64) = 0x00000001
step 17:  PEX6  pexUnit= 1
PEX6 : Detected No Link. Status Reg(0x00089A64) = 0x00000001
                                                            DDR3 Training Sequence - Ver 4.5.DDR3 Training Sequence - Static MC Init
DDR3 Training Sequence - HW Training Procedure
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
BootROM: Image checksum verification PASSED

__   __                      _ _
|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
** LOADER **


U-Boot 2011.12 (Feb 06 2014 - 17:14:13) Marvell version: v2011.12 2013_Q1.2

Boot version:v1.3.25

Board: RD-AXP-GP rev 1.0
SoC:   MV78230 B0
       running 2 CPUs
       Custom configuration
CPU:   Marvell PJ4B (584) v7 (Rev 2) LE
       CPU 0
       CPU    @ 1200 [MHz]
       L2     @ 600 [MHz]
       TClock @ 250 [MHz]
       DDR    @ 600 [MHz]
       DDR 32Bit Width, FastPath Memory Access
       DDR ECC Disabled
DRAM:  256 MiB

Map:   Code:            0x0fea7000:0x0ff5e2d4
       BSS:             0x0ffefd80
       Stack:           0x0f9a6ef8
       Heap:            0x0f9a7000:0x0fea7000

NAND:  Spansion 1Gb(ID=F101) 128 MiB
MMC:   MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01


#### auto_recovery ####
[u_env] get auto_recovery == no
[u_env] get auto_recovery == no
[u_env] get boot_part == 2
[u_env] get boot_part_ready == 3
auto_recovery enabled:0, boot_part:2, boot_part_ready:3

PEX 0.0(0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1): Root Complex Interface, Detected Link X1, GEN 1.1
PEX 0.2(2): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.3(3): Detected No Link.
PEX 1.0(4): Detected No Link.
PEX 1.1(5): Detected No Link.
PEX 1.2(6): Detected No Link.

boot_end Offset: 0x100000
u_env_off Offset: 0x100000
s_env_off Offset: 0x140000
devinfo Offset: 0x900000

===================
total_badCount: 0
boot_badCount: 0
u_env_badCount: 0
s_env_badCount: 0
buff_badCount: 0
===================

FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Device Mode
Modules Detected:
mvEthE6171SwitchBasicInit finished
Net:   mvSysNetaInit enter
set port 0 to rgmii enter
set port 1 to rgmii enter
egiga0 [PRIME], egiga1
modify Phy Status
auto_recovery_check changes bootcmd: run altnandboot
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x3200000, size 0x400000
4194304 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Marvell>>


I have been unbriked.
I'm very stupid.
I have not conect lan cable.

Thanks for all.

Don't worry about it, it's hard to remember everything when trying to recover !

Post #2146
lonniereeder
7 Jan 2015, 16:03
weedv2 wrote:
lonniereeder wrote:

5.0Ghz setup

Operating Freq
- Mode=N, Freq=5.0Ghz, Channel=Auto, Width=40
Transmit Power=17dBm

Under Interface setup
ESSID=mordor
Mode=Access point

Channel=Auto does not seem to work for 5Ghz, i would recommend manually setting the channel.
You can use a tool like inSSIDer to find what networks arent used/have low usage
http://www.majorgeeks.com/files/details/inssider.html

That worked great, was able to get my 5Ghz up and running. I live on a street with very few houses, and no one on my street has anything above 2.4ghz, so I had free choice of any channel. I was also able to choose an unused band for by 2.4ghz and it seems be work fairly stable. Thanks for the tip.

Post #2147
jklap
7 Jan 2015, 17:09
DavidMcWRT wrote:

I have some bad blocks on my router as seen in the kernel log:

[    1.004901] Bad block table found at page 65472, version 0x01
[    1.010940] Bad block table found at page 65408, version 0x01

Given that the unit's only a few months old, should this be expected (so soon)?

Having bad blocks in flash out of the gate is not unusual. I have 2 that have been there since the unboxing.

Post #2148
lifehacksback
7 Jan 2015, 17:17

Is openwrt wiki down? or is it just me?

Post #2149
dpdurst
7 Jan 2015, 17:23

Yep appears down

Post #2150
digitalgeek
7 Jan 2015, 18:23
LookingForMyMojo wrote:

My 2.5 cents worth............

I have tried every image since day 1 of Chadster's first release. I have NEVER had to use my ttl cable. I NEVER flash an image without flashing Linksys Stock first. I am running Life's 2nd latest release, when I update to the most recent, I will flash Linksys stock and let it setup, find the internet....etc....etc., before I flash any alternative image. I NEVER flash from one OpenWrt/Custom image to another. Everyone needs to realize that these are all in new/testing stage, if you can't recover the router from doorstop status, I would suggest not trying any alternative image until a stable proven release.  It is "use at your own risk" after all.

I even reset factory defaults before flashing or configuring for my network...

Sorry, posts 2151 to 2150 are missing from our archive.