Anyone know what pins 2 and 4 are for on the serial port?
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.
prob cts/rts, dunno which order
Not exactly sure what the issue here is yet, but comes up after a couple boots with their precompiled image...
[ 7.425563] jffs2: mtd->read(0x800 bytes from 0xe9d800) returned ECC error
Looks like when ubifs gets hosed it then hoses the jffs2 partition. Their ubifs loading script needs a couple of tweaks to deal with the mount failure. It also unlocks the root fs based on the boot partition in firmware, not the running boot partition (when ubifs is hosed).
Once I added handling the mount failure I haven't seen any jffs2 issues (which I shouldn't given it stays locked).
The repo containing the latest source has now been marked as public: https://github.com/jimmychungbelkin/Mamba
I have also cloned it and checked it out, just in case
Any luck with this release?
Drakia wrote:The repo containing the latest source has now been marked as public: https://github.com/jimmychungbelkin/Mamba
I have also cloned it and checked it out, just in case
Any luck with this release?
That hasn't been touched in two months.
That hasn't been touched in two months.
Oh ok, I thought I saw a few directories updated in the last day or so.
I got this in an email from Linksys last night.
Apparently Marvell isn't playing ball yet.
Old news, shared widely yonks ago, things have evolved further since then.
But can't hurt to share again, for those who haven't been following.
That hasn't been touched in two months.
Geezus, um... why... >.>
Their "2 steps forward 3 steps back" approach is starting to irritate.
(Last edited by jalyst on 6 May 2014, 18:08)
Their sys update scripts are whacked. They back up config files when, ironically, it's not needed due to the ubifs partition. Which then just leaves duplicated crap in the overlay. Guess I'll be fixing that up too. Also a bit weird that they use the same ubifs partition for both the primary and alt firmware-- bit of a pain if you are maintaining two completely different versions-- ala like altitude adjustment and barrier breaker... but I suppose I'm probably an end case
Someone somewhere mentioned that there was a problem with the fan control-- I tested that yesterday and it looks good. No clue if the temp sensors are correct but you can trigger the fan.
Anyone seen any uboot code anywhere?
Anyone seen any uboot code anywhere?
They just posted the bin for uboot an hour ago.. maybe we'll see source soon?
jklap wrote:Anyone seen any uboot code anywhere?
They just posted the bin for uboot an hour ago.. maybe we'll see source soon?
I've requested it already. I'm working on implementing support properly, I'm running 3.14 on mine.
what changed in uboot?
Is the Barrier Breaker image stable enough at this point to work w/o worrying about wireless? I'm looking to put mine in the DMZ for my FiOS router to setup a VPN for a home lab (wired) w/ two VLANs, one connecting to a bridged Airport Extreme (for the wireless for now). Is this use case doable now or am I asking for a headache?
I'm relatively new to this, but to clarify: if I set the image manually via Linksys firmware UI and it blows up, I can use nyt's reset procedure to kick it over to the original factory firmware and try again (so long as I repeat that process exactly)? I can grab a serial connector, but I'd really rather not if I can avoid it (never messed w/ a serial interface before).
I tried the recovery method and it didn't work... I had to use the serial method and I was good...
Is the Barrier Breaker image stable enough at this point to work w/o worrying about wireless?
I think so. Caveat that I'm using my own built image but is based on their patch set. I'm also using wireless (2.4Ghz) but do run into the disconnect every so often.
I can grab a serial connector, but I'd really rather not if I can avoid it (never messed w/ a serial interface before).
I'd just bite the bullet and buy one. Better to have it on-hand then have to order it and wait
My fav: https://www.sparkfun.com/products/718
Or if you don't want to solder:
I tried the recovery method and it didn't work... I had to use the serial method and I was good...
Agreed. I was able to switch partitions when they both worked. When I hosed I had to drop to serial to recover.
DaedalusX wrote:Is the Barrier Breaker image stable enough at this point to work w/o worrying about wireless?
I think so. Caveat that I'm using my own built image but is based on their patch set. I'm also using wireless (2.4Ghz) but do run into the disconnect every so often.
Okay, cool.
I'd just bite the bullet and buy one. Better to have it on-hand then have to order it and wait
My fav: https://www.sparkfun.com/products/718
Or if you don't want to solder:
I don't want to solder, so that second one looks awesome. I ordered one. Thanks!
I tried the recovery method and it didn't work... I had to use the serial method and I was good...
Hi
Anyone having problems with single port forwarding with the Barrier Breaker image?
Thx
m33p wrote:I tried the recovery method and it didn't work... I had to use the serial method and I was good...
Hi
Anyone having problems with single port forwarding with the Barrier Breaker image?
Thx
Did you use Luci to create the rule or iptables directly?
Did you use Luci to create the rule or iptables directly?
Neither, I'm using the OEM firmware (for now)
I need single port forwarding
(Last edited by gufus on 9 May 2014, 23:46)
works fine
Excellent!
Hey nyt and jklap, you're both running custom builds of the Barrier Breaker code from GitHub, right? If so, could you both post your latest .config files?
Last time I tried to flash a build from my own config I had to unbrick via serial, not fun times.
keep in mind i dont use luci
Hmm, the 'master' branch on the Mamba GitHub is giving me a patch conflict on 0085-irqchip-armada-370-xp-fix-IPI-race-condition.patch. Anyone else getting that?
Also, thanks nyt, you're awesome!
(Last edited by Drakia on 11 May 2014, 00:50)