@northbound

I forgot to submit the Kconfig symbol change, jow fixed that.

nitroshift

Thanks much...It's the little  things that get ya. :-)

No disrespect to you or jow intended.

(Last edited by northbound on 14 Feb 2016, 06:59)

What happens to "Kaloz' evolving snapshots"?! No updates since november 27 2015, damn.

Roll your own it is more fun that way. There have been very few commits today and that is a good sign!

Are files placed within the buildroot files directory assigned proper permissions prior to the image being created (such as customized config files for /etc/config)?  I keep getting lua errors when trying to access the web server via HTTP or https, and even though I've also included the authorized_keys file in /etc/dropbear, connection is being refused, stating public key is not what it should be.

Upon opening the sysupgrade tar, I noticed most of my custom files have a double of the same name, but with a " ~ " at the end of the file name.  I'm obviously either missing a step I should be doing, or I'm doing something wrong... Not sure which.

I always set permissions on the files dir. and files before building and they carry over to the build. Check all in the /openwrt/files Dir. Once set in Ubuntu and copied and pasted they will fly. (or whatever case sensitive file system you use)

Edit: ~ in the file name I believe means deleted at least with my setup.

(Last edited by northbound on 14 Feb 2016, 08:00)

We're marching towards 15.05.1 fast. As for Kaloz's builds, they are basically trunk with some packages included.

nitroshift

(Last edited by nitroshift on 14 Feb 2016, 08:15)

that sounds nice, I am looking for an upgrade, because of my wifi issue. Would I be able to upgrade from 15.05 final to kaloz 15.05.1 (if it's available) with keeping all settings and packages?
thx!

so long

Does the trailing ~ mean the specific file with the trailing ~ has been deleted, or that the same named file without the trailing ~ has been deleted?

...that's a bit wordy, and may not come across right, so for example:

If network & network~ exist, does it mean network has been deleted, or that network~ has been deleted?

(Last edited by JW0914 on 14 Feb 2016, 09:24)

15.0.5.1 will most likely be on kernel 4.4 and while settings can be preserved, packages will need to be reinstalled. Also, 15.05.1 will be an official release, not Kaloz's own build.

nitroshift

(Last edited by nitroshift on 14 Feb 2016, 12:42)

For those of you who have tried these builds, do they include the latest fixes (nand, led, etc)? Also, what kernel version does this build use?

Cheers

LE: are ping times still an issue?

(Last edited by Nihilanth on 14 Feb 2016, 11:37)

interesting question, are that fixes included in kaloz build, too?

LED's package has been fixed. Nand issue is different, not fixed yet. At the moment mvebu builds by default with kernel 4.1.xx.

nitroshift

cheers mate!

I know some people have been complaining about high ping times, locks, resets, led issues and whatnot, therefore, what build would you recommend? I know you're quite active and knowledgeable about the WRT builds, hence, I would really appreciate your feedback (wouldn't mind taking your build for a spin if stable and wifi works ok ).

Hi, I'm using the Arokh build in my WRT1900ACS, but I don't know if this happens also in other builds as well. Basically, I have an external overlay partition by my HHD plugged on the router; when I update the firmware, at the first boot after the update, the overlay external partition is not "considered" by the router. I have to reboot one time to get correctly it function as an external overlay

Does this happen only to me because I made something wrong on the configuration or is it normal?

@Nihilanth

I can't advise on any builds as I'm only flashing my own because I'm always testing code that might end upstream (or not) but I will talk to Kaloz tomorrow and if he's OK with me putting up my repo again, I will make my builds available.

nitroshift

(Last edited by nitroshift on 14 Feb 2016, 16:02)

That's normal and will occur unless you build your own firmware with your custom config files.

This will occur on a firmware flash due to one of two reasons, or both:

1. block-mount is not installed and/or

2. fstab is empty or option enabled is set to 0

Also IIRC, once a firmware flash is performed you must redo the extroot root command to copy all overlay files to the extroot overlay partition.  If this is correct, prior to doing so, boot from your extroot overlay partition and perform a backup, either via the gui or via sysupgrade (ensuring you modify the sysupgrade.conf to exclude /etc/config/fstab), as it's probably easiest to perform a rm -Rf on the extroot overlay partition prior to performing the extroot copy, then once booted into it, restore the backup

(Last edited by JW0914 on 14 Feb 2016, 16:09)

If you would make a "V2" image available, I am in !

Has anyone else experienced build errors when not compiling using make -j1?  Shouldn't it build correctly without specifying only one job at a time?

@nitroshift: kaloz image is mostly like the official openwrt image, isn't it? Any idea when he will publish a new version?

arokh mvebu build uses 4.4 kernel, has nand patch, led issue on wrt900acv1 reported as still existing here post.
I have not personally tried any recent arokh builds.

Files with ~ extension maybe a dried muffin remnant (backup) from using vi/vim.

Edit:
Perhaps the led issue from that post is just configuration, as it is a post r48684 build. I am still back at r48679, but another mac80211 patch today so I will probably flash a new image today.

Edit 2:
Just flashed to r48719 and the led issue on v1 certainly has been addressed so I assume post from arokh community build thread to be a configuration issue.

(Last edited by anomeome on 14 Feb 2016, 21:10)

When I've gotten over replacing the server

hey thx I am sorry for my impatience but you are my "last" hope, because of my wifi issues, I want to try your latest build and not that trunk builds.

so long

Yes, that was why I remarked on it in the arokh thread. Even though the build number that he gives is the same as the trunk snapshot that I tested, the internet connection light worked in the trunk snapshot but not in the arokh version. So yes, we're talking configuration *smile*.

Trunk is using 4.1.x kernel, arokh community is using 4.4. The led issue for v1 was in > 4.1 kernel builds, that is why you were not seeing it on trunk/DD. But it is resolved in my latest so I assume same in the current arokh. See my post on that topic.

(Last edited by anomeome on 14 Feb 2016, 21:58)