OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

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

Just learned the following from InkblotAdmirer --  This will affect those on Shelby for the next build coming out later today.  https://github.com/lede-project/source/ … b97ef7df1d

InkblotAdmirer wrote:
Just an fyi for those dabbling in both OpenWRT and LEDE - the LEDE project just modified the shelby network config so all platforms are now LAN eth0 and WAN eth1.  /etc/config/network must be updated (be sure to fix the switch if VLANs configured!) and a few other possibilities (if you have LEDs configured, firewall rules for a specific interface, etc).
This is one of those areas where "keep settings" will break stuff, and in addition unless OpenWRT follows the same path (this has not been updated yet in OpenWRT git) swapping between builds will be a bit more difficult.

(Last edited by davidc502 on 24 Nov 2016, 18:32)

davidc502 wrote:

Just learned the following from InkblotAdmirer --  This will affect those on Shelby for the next build coming out later today.

InkblotAdmirer wrote:
Just an fyi for those dabbling in both OpenWRT and LEDE - the LEDE project just modified the shelby network config so all platforms are now LAN eth0 and WAN eth1.  /etc/config/network must be updated (be sure to fix the switch if VLANs configured!) and a few other possibilities (if you have LEDs configured, firewall rules for a specific interface, etc).
This is one of those areas where "keep settings" will break stuff, and in addition unless OpenWRT follows the same path (this has not been updated yet in OpenWRT git) swapping between builds will be a bit more difficult.

Any idea why? Seems like it will cause more frustration than anything else.

Redferne wrote:

Have anyone tested /extroot or /overlay on an external USB drive? I'm having serious problems that /overlay is not remounted  after reboot. Need to manually issue PREINIT=1 mnt_root to get my settings back from the USB drive. And mnt_root kills both wifi radios, unable to get the working until reboot. Ding, catch 22.

Fixed by removing .../etc/.extroot file from external USB used for /overlay.

Redferne wrote:

I just updated to HEAD, r2221 and boy did a make a mistake. There's shitton of packages missing. For example, transmission, is there nobody using this anymore? Can't find it in any built repos, argh...

Fixed by frustrated going to bed and wakeup and all missing packages has magically re-appeared.

@davidc502

From where comes the name "Hydra (HEAD, r2221)"? I would like to reproduce something similar to your builds and I just want to make sure I'm building from the correct commit.

Also would you consider sharing your .config with me privately? Just need it for reference.

For your builds, you are cherrypicking the greatest mwlwifi from kaloz?

Thanks!

Redferne wrote:

@davidc502

From where comes the name "Hydra (HEAD, r2221)"? I would like to reproduce something similar to your builds and I just want to make sure I'm building from the correct commit.

Also would you consider sharing your .config with me privately? Just need it for reference.

For your builds, you are cherrypicking the greatest mwlwifi from kaloz?

Thanks!

Add the following to .config and save. Then go back into menuconfig and select "image configuration" and you will see options that weren't there before.

CONFIG_IMAGEOPT=y
CONFIG_VERSIONOPT=y

As for wifi, I will usually try to reference the latest drivers before building. I haven't checked in about a week, so it appears new drivers have been posted. Performance from the previous driver has been excellent, and I'm a little hesitant to changing...  Will look to see what improvements are being addressed.

New images uploaded with a full package repo. However, I usually test before uploading, but my wife is working from home today, so I can't upgrade the router until tonight.

Let me know if there are any problems.

Also, don't forget for folks using ACS ---  Ethernet 0 and 1 have been switched, so if you have VLANS configured or any extra firewall rules, on these interfaces, be sure to check that you are not affected.

This is the committed change --  Supposedly the change was made to simplify the boards.

-armada-385-linksys-shelby)
-    ucidef_set_interfaces_lan_wan "eth1" "eth0"
-    ucidef_add_switch "switch0" \
-        "0:lan:4" "1:lan:3" "2:lan:2" "3:lan:1" "6@eth1" "4:wan" "5@eth0"

The change in question impacts every device in family except mamba, not just ACS; so cobra,caiman,shelby,rango.

Hey david,

The change has been rolled back:

git[dot]lede-project[dot]org/?p=source.git;a=commit;h=95e7868e7e2c93c832254e4ab15d73294d6e78d3

It introduces a regression for WRT3200.

Also just wanted to draw your attention to the fact that there has been 2 mwlwifi updates in the past two days.

Geezz... I guess I'm glad I didn't flash yet wink   

Will go ahead and get started on a new build including the new wifi driver.

David,
I ran into a tough one. I finally have OpenWRT where i want it but my vizio tv cannot watch plex. I changed my DNS servers on the TV to use google and now everything works fine. You go any suggestions or have you seen this? Also the luci-app-access-control was developed by a parent that wanted to limit internet usage easily. i found int on git hub. https://github.com/k-szuster/luci-access-control. Also you i got the new load from thanksgiving and am seeing this when trying to install sqm.



Installing luci-app-sqm (1.0.9-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … 1_all.ipk.

Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-sqm:
*     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *
* opkg_install_cmd: Cannot install package luci-app-sqm.

(Last edited by iceberg9992004 on 26 Nov 2016, 04:06)

iceberg9992004 wrote:

David,
I ran into a tough one. I finally have OpenWRT where i want it but my vizio tv cannot watch plex. I changed my DNS servers on the TV to use google and now everything works fine. You go any suggestions or have you seen this? Also the luci-app-access-control was developed by a parent that wanted to limit internet usage easily. i found int on git hub. https://github.com/k-szuster/luci-access-control. Also you i got the new load from thanksgiving and am seeing this when trying to install sqm.



Installing luci-app-sqm (1.0.9-1) to root...
Downloading http://downloads.openwrt.org/snapshots/ … 1_all.ipk.

Collected errors:
* satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-sqm:
*     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *     kernel (= 4.4.14-1-62d98ef1d2e76e1c5e767087cda8b772) *
* opkg_install_cmd: Cannot install package luci-app-sqm.

Those are snapshot packages that change daily. When installing OpenWrt from a snapshot, be sure to download ALL packages you will ever need on that same day. 

If you know 100% that it's the same kernel version you can --force-depends or --force-checksum to ignore those type of mismatches.

Keep in mind, there is a risk when forcing a install..

Great work on latest build and I am LOVING the package selection keep it up

Hi

I'm curious what system do you compile on? (cpu, ram..etc).
Also do you do a full feeds compile with every release? must take hours no?

smile

james04 wrote:

Hi

I'm curious what system do you compile on? (cpu, ram..etc).
Also do you do a full feeds compile with every release? must take hours no?

smile

I was compiling on AMD 2 core, but am now doing it on a quad core Intel processor (a bit faster)... I don't rush the compilation... meaning I don't use the -j(x) switch, so it does take a very long time to compile, but I think the results are worth it.

Actually, doing all packages is something new, as in the past I just took requests (like a Disk Jokey lol ). Considering how many requests were coming in, and people who liked the build, but didn't like that they didn't have the packages they wanted, it was best to just figure out how to do them all.

** EDIT **

Some might be wondering about the -j switch.. Essentially, this greatly speeds up compilation, but can introduce compilation errors. So, I just stay away from it.

(Last edited by davidc502 on 26 Nov 2016, 06:02)

davidc502 wrote:
james04 wrote:

Hi

I'm curious what system do you compile on? (cpu, ram..etc).
Also do you do a full feeds compile with every release? must take hours no?

smile

I was compiling on AMD 2 core, but am now doing it on a quad core Intel processor (a bit faster)... I don't rush the compilation... meaning I don't use the -j(x) command, so it does take a very long time to compile, but I think the results are worth it.

Actually, doing all packages is something new, as in the past I just took requests (like a Disk Jokey lol ). Considering how many requests were coming in, and people who liked the build, but didn't like that they didn't have the packages they wanted, it was best to just figure out how to do them all.

Wow.. without -j<num of cores> ?
It must take more than a day then doesn't it?
Btw, I think it was in the old days that issues popped up when using many cores, now the buildsystem is pretty good that it has flags and whatnot, I see people compiling with -j16 and more without any problems..

james04 wrote:
davidc502 wrote:
james04 wrote:

Hi

I'm curious what system do you compile on? (cpu, ram..etc).
Also do you do a full feeds compile with every release? must take hours no?

smile

I was compiling on AMD 2 core, but am now doing it on a quad core Intel processor (a bit faster)... I don't rush the compilation... meaning I don't use the -j(x) command, so it does take a very long time to compile, but I think the results are worth it.

Actually, doing all packages is something new, as in the past I just took requests (like a Disk Jokey lol ). Considering how many requests were coming in, and people who liked the build, but didn't like that they didn't have the packages they wanted, it was best to just figure out how to do them all.

Wow.. without -j<num of cores> ?
It must take more than a day then doesn't it?
Btw, I think it was in the old days that issues popped up when using many cores, now the buildsystem is pretty good that it has flags and whatnot, I see people compiling with -j16 and more without any problems..

You may ask if they are also using the "IGNORE_ERRORS X" switch whilst compiling.

I've tried several times to just the -j, but it was a bit hit or miss for me.  It could be other systems are just more stable, hard to say.

I see. frankly I always get a package or two failing (if ALL from all feeds are selected).. there's always that package with outdated url or sth..:)

You don't get any failures?

I installed .32 about 3 or 4 hours ago, all went well for a while but now after about 20 min it seems to be dropping one adapter then the next about 5 min later even after a reboot, what can I do to help with the diagnosis?

markm12345 wrote:

I installed .32 about 3 or 4 hours ago, all went well for a while but now after about 20 min it seems to be dropping one adapter then the next about 5 min later even after a reboot, what can I do to help with the diagnosis?


BTW this is the Cobra build on obviously an 1900v2 and I disabled all addon packages installed post upgrade so far to being, I will try to plug in when it happens again and grab whatever I can find from kernel and system logs.

Okay... New build r2321 has been uploaded to the server. This build also contains a full package repository.

1. This build reverts a fairly major change.  So if you have r2317 installed (from yesterday), I highly recommend flashing to r2321

2. This build includes the new wifi driver 10.3.2.0-20161124.

3. SNMP has been upgraded from 5.4.4 to 5.7.3. Any collectd users out there? Since collectd is dependent on SNMP, please let me know if this introduces any issues. If it doesn't, I'll try to push the change to lede.

(Last edited by davidc502 on 26 Nov 2016, 16:23)

Hello,

I have installed your latest firmware for the 1900ACS and when I want to go back to the original version of Linksys, it tells me it's impossible.

What does it take to get back to the original firmware?

I read all the wiki and nothing works unfortunately.

Hostname    lede
Model    Linksys WRT1900ACS
Firmware Version    Lede Reboot r2317 / LuCI Master (git-16.324.51057-1c27f6b)
Kernel Version    4.4.32

GsMike wrote:

Hello,

I have installed your latest firmware for the 1900ACS and when I want to go back to the original version of Linksys, it tells me it's impossible.

What does it take to get back to the original firmware?

I read all the wiki and nothing works unfortunately.

Hostname    lede
Model    Linksys WRT1900ACS
Firmware Version    Lede Reboot r2317 / LuCI Master (git-16.324.51057-1c27f6b)
Kernel Version    4.4.32

Did you flash from stock firmware over to Lede?

I'm guessing, in Luci GUI, you went to "Backup/ Flash Firmware" and UNSELECTED "Keep Settings", Chose File (Stock Firmware) and Flashed that image?

Yes I have done since stock firmware to lede

Does not work it tells me

The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform.

I put the following image FW_WRT1900ACS_1.0.0.169041_prod.img

(Last edited by GsMike on 26 Nov 2016, 17:05)

Sorry, posts 551 to 550 are missing from our archive.