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.

nitroshift wrote:

Linksys declined again to send me u-boot.kwb... Waiting for @mmilburn to revive my unit and the RMA to get a new one.
nitroshift

RMA... Does that imply that you will have to return the currently broken unit?

lifehacksback wrote:

1) I got a rig set up with Ubuntu Gnome 14.10 (I wanted to test the early iterations of systemd and I like ubuntu [long story]) I followed the guide in the github repo and installed everything along with cloning the source. While building there were a bunch of [Y/n/?] or [N/y/?] or [Y/m/?] i just allowed the "default" but since I wasnt sure what I was doing I stopped the build. What are those thing? and why werent they set in the makeconfig screen?

You can safely hold down enter for that nonsense.  The original build setup was a little strange.  I'm inclined to think it was a snafu courtesy of Belkin, but I don't really know.

lifehacksback wrote:

3) What version of the kernel will CC use? I wanted to see if maybe file systems could be build so the router could detect my external HDD that may be formatted in btrfs or xfs.

3.14.x, an LTS kernel.  Some things from newer kernels will be backported.  You'll have to watch the 3.14.x changelogs to really know what's getting pushed in.

mmilburn wrote:
nitroshift wrote:

Linksys declined again to send me u-boot.kwb... Waiting for @mmilburn to revive my unit and the RMA to get a new one.
nitroshift

RMA... Does that imply that you will have to return the currently broken unit?

Probably because I live in the opposite side of Europe and the postal fees are too high, Linksys told me I can keep the broken unit.

nitroshift

@mmilburn

Can you dump the mtdo content in bin format? Apparently this can be flashed to another device with kwboot tool.

UPDATE:

The new unit is being shipped today, should be with me within a few days, but still working on getting the old router up and running.

(Last edited by nitroshift on 13 Nov 2014, 13:21)

Non-Openwrt related but anyone know if i can enable on-the-fly compression in btrfs from the Mcwrt?
Here(http://askubuntu.com/questions/129063/will-btrfs-automatically-compress-existing-files-when-compression-is-enabled) the answer says i could enable it by placing the command in fstab. Does Openwrt use fstab? or is there somewhere else I need to apply this command?

Update:

-McWRT v1.0.5 does not support btrfs (at lease not automount)

-Does McWRT support eSata? It should since it is a fork of Mamba, right?

How can I get console access to the router? tftp or do i need the serial cable?

-lifehacksback

(Last edited by lifehacksback on 13 Nov 2014, 14:34)

lifehacksback wrote:

Non-Openwrt related but anyone know if i can enable on-the-fly compression in btrfs from the Mcwrt?
Here(http://askubuntu.com/questions/129063/will-btrfs-automatically-compress-existing-files-when-compression-is-enabled) the answer says i could enable it by placing the command in fstab. Does Openwrt use fstab? or is there somewhere else I need to apply this command?

Update:

-McWRT v1.0.5 does not support btrfs (at lease not automount)

-Does McWRT support eSata? It should since it is a fork of Mamba, right?

How can I get console access to the router? tftp or do i need the serial cable?

-lifehacksback

McWRT supports eSata, I've been using it when my router was OK. For console access you need a USB to TTL adapter. Use this reference to get access to the serial header on the board: https://github.com/Chadster766/McWRT/wi … erial-Port

nitroshift

nitroshift wrote:

I've been using it when my router was OK.

Are you using ssd? hdd? can you tell me the transfer speeds? My Hdd is dying so im going to look into the wd red and just place it in my "case" but i want to know the speeds i mean i might try to plug in an ssd to test but my media or other files easily take up to 1 TB.

Does the processor handle the file transfers? or is there a dedicated hardware moving things along? Transfers between comps have been less than optimal (then again i didnt know what to expect).

Final point btrfs doent work unless kmod-fs-btrfs is installed and there are some dependencies that need to be taken into account. My tty to usb still hasn't arrived so im weary of applying any type of dev software on my router.

-lifehacksback

nitroshift wrote:

Probably because I live in the opposite side of Europe and the postal fees are too high, Linksys told me I can keep the broken unit.

nitroshift

@mmilburn

Can you dump the mtdo content in bin format? Apparently this can be flashed to another device with kwboot tool.

I figured you were somewhere around CET.

mtd0 dump (cat /dev/mtd0 > /tmp/foo [just bytes, so it's a bin]):
http://www.protechs-online.com/download … u-boot.img

belkin image:
http://www.protechs-online.com/download … 1.3.25.bin

The images are identical up until byte 0xdf0ff (around ~892kb), the rest could just be trash.  The mtd0 partition is defined to be 1Mb in size.
https://i.imgur.com/ZXjDVcv.png

There's your requested mtd0 dump, but I really think you need an image designed to boot from serial (UART).

DUH!  I just saw that u-boot integrated kwboot into mainline in September, it's a version designed to work with our board, and it can patch the image to do UART.

(14:44:%) ./kwboot                                                                                                                                                                         (2014/11/13)
Usage: kwboot [-d | -a | -b <image> | -D <image> ] [ -t ] [-B <baud> ] <TTY>

  -b <image>: boot <image> with preamble (Kirkwood, Armada 370/XP)
  -p: patch <image> to type 0x69 (uart boot)
  -D <image>: boot <image> without preamble (Dove)
  -d: enter debug mode
  -a: use timings for Armada XP

  -t: mini terminal

  -B <baud>: set baud rate

I'm putting up the source and my binary (the binary may not work for you).  gcc kwboot.c should build for you.

http://filebin.ca/1hAJVQqY1xFN/kwboot.tar.bz2

Edit: changed location of files.

(Last edited by mmilburn on 14 Nov 2014, 04:50)

mmilburn wrote:
nitroshift wrote:

Probably because I live in the opposite side of Europe and the postal fees are too high, Linksys told me I can keep the broken unit.

nitroshift

@mmilburn

Can you dump the mtdo content in bin format? Apparently this can be flashed to another device with kwboot tool.

I figured you were somewhere around CET.

mtd0 dump (cat /dev/mtd0 > /tmp/foo [just bytes, so it's a bin]):
http://www.protechs-online.com/download … u-boot.img

belkin image:
http://www.protechs-online.com/download … 1.3.25.bin

The images are identical up until byte 0xdf0ff (around ~892kb), the rest could just be trash.  The mtd0 partition is defined to be 1Mb in size.
https://i.imgur.com/ZXjDVcv.png

There's your requested mtd0 dump, but I really think you need an image designed to boot from serial (UART).

Hopefully no one mistakes these binaries for OpenWRT McWRT releases. Remember Google picks up this thread.

Building an image, I enabled kmod-fs-btrfs from the menuconfig. Hopefully it works!

Does CC compile correctly now?

PS. i'm willing to do documentations if you need

-lifehacksback

-------------------------------------------------------------------
Update:

Did not compile with -j flag running again make V=s

(Last edited by lifehacksback on 14 Nov 2014, 03:38)

The OpenWRT DLNA Server does work on McWRT v1.0.5

I've create a Wiki page to help you with the setup:

Minidlna Setup

Which is the exact code for DDR training in this link: https://patchwork.ozlabs.org/project/ub … egate=1696  ? I am making progress building the u-boot file using the u-boot tool from ftp://denx.de/pub/u-boot/ smile At the moment I have a file that gets transferred correctly but doesn't start. The reason I need the code is a file in u-boot tools called binary.o that reads:

"--------
WARNING:
--------
This file should contain the bin_hdr generated by the original Marvell
U-Boot implementation. As this is currently not included in this
U-Boot version, we have added this placeholder, so that the U-Boot
image can be generated without errors.

If you have a known to be working bin_hdr for your board, then you
just need to replace this text file here with the binary header
and recompile U-Boot.

In a few weeks, mainline U-Boot will get support to generate the
bin_hdr with the DDR training code itself. By implementing this code
as SPL U-Boot. Then this file will not be needed any more and will
get removed."

nitroshift

PS. @mmilburn:

Thanks for the dump, still getting errors while transferring.

Update:

I managed to transfer the mtd0 dump, still won't start. I feel we are close, there's only a small glitch we are overseeing.

(Last edited by nitroshift on 15 Nov 2014, 11:39)

I cant manage to get a build going hmm Any help? for example what version of subversion do i need?

lifehacksback wrote:

I cant manage to get a build going hmm Any help? for example what version of subversion do i need?

There is many ways to do this but I like to the latest stable release of Debian.

You need to have installed gcc, binutils, patch, bzip2, flex, make, gettext, pkg-config, unzip, libz-dev, libc headers and Subversion 1.7.

For the Feeds to update (update.sh) from packages_12.09 you will need to have Subversion 1.7 installed. http://sagar.se/svn-1.7-on-wheezy.html


To build the image run "update.sh", "make V=s" and then when prompted press enter a lot of times :-) If successful the image should be in the "bin" directory.

OpenWRT McWRT Building WiKi:
Building

Chadster766 wrote:

For the Feeds to update (update.sh) from packages_12.09 you will need to have Subversion 1.7 installed.

I have Subversion 1.8.8. Is that ok?

Chadster766 wrote:

To build the image run "update.sh", "make V=s" and then when prompted press enter a lot of times :-) If successful the image should be in the "bin" directory.

I just downgraded to Ubuntu 14.04 LTS and have installed the packages. Going to try to compile again!

Thanks!
-lifehacksback

Opened up my router and connected the serial cables. Putty doesn't recognized anything. Can i connect via terminal or do i need putty?

@lifehackisback

Is your router bricked? If not, I would HIGHLY recommend you to STOP at this point.

nitroshift

nitroshift wrote:

@lifehackisback

Is your router bricked? If not, I would HIGHLY recommend you to STOP at this point.

nitroshift

It isn't. May I ask why?

@lifehackisback

If your router isn't bricked you don't need serial access to it, all configuration can be done through web management.

nitroshift

nitroshift wrote:

@lifehackisback

If your router isn't bricked you don't need serial access to it, all configuration can be done through web management.

nitroshift

Right but I wanted to gain access to the console in order to start testing out different configs when I build the source. However I can't even get to the console.

PS there is a disparity between McWRT wiki (https://github.com/Chadster766/McWRT/wiki/WRT1900ac---Gaining-accesss-to-the-UBOOT-console-via-the-TTL-port and https://github.com/Chadster766/McWRT/wi … rial-Port) and Openwrt wiki  (http://wiki.openwrt.org/toh/linksys/wrt1900ac). Under Serial Port Openwrt counts 1-GND 2-? 3-RX 4-? 5-TX 6-?
while Mcwrt both guides say 1-GND 2-RX 3-? 4-TX 5-? 6-?

McWRT guide is the correct one.

nitroshift

nitroshift wrote:

Which is the exact code for DDR training in this link: https://patchwork.ozlabs.org/project/ub … egate=1696  ? I am making progress building the u-boot file using the u-boot tool from ftp://denx.de/pub/u-boot/ smile At the moment I have a file that gets transferred correctly but doesn't start. The reason I need the code is a file in u-boot tools called binary.o that reads:

"--------
WARNING:
--------
This file should contain the bin_hdr generated by the original Marvell
U-Boot implementation. As this is currently not included in this
U-Boot version, we have added this placeholder, so that the U-Boot
image can be generated without errors.

If you have a known to be working bin_hdr for your board, then you
just need to replace this text file here with the binary header
and recompile U-Boot.

In a few weeks, mainline U-Boot will get support to generate the
bin_hdr with the DDR training code itself. By implementing this code
as SPL U-Boot. Then this file will not be needed any more and will
get removed."

nitroshift

PS. @mmilburn:

Thanks for the dump, still getting errors while transferring.

Update:

I managed to transfer the mtd0 dump, still won't start. I feel we are close, there's only a small glitch we are overseeing.

I have renamed the dump to .bin, transferred it OK, now the error is "Invalid Header Checksum"...

nitroshift

Hi!

Wondering if WAN-failover via a 4G-dongle is supported on McWRT 1.0.5? Got a Huawei E3272.

nitroshift wrote:

McWRT guide is the correct one.

nitroshift

yep

smile

just got this router few days ago and i been trying to figure it out if i can install the new barber breaker firmware on it. When i go to downloads it shows lots of chipsets and don't know which one i have to pick for my router. Can someone post a link with direct link to the firmware. thank you !!!