[Stable vs mainline for Next]

Thanks for the feedback on the testing. Any plans to test the other stuff like AES, SHA1 etc?

 

 

it is a decent prng, impossible to assess anything about being a csprng

[Stable vs mainline for Next]

Hi Igor,

 

A command line parameter to compile.sh would be nice e.g. "./compile.sh mainline"

 

if no parameter is passed in, then it could default to stable. That would make things a lot simpler and not require modifying any of the lib files or having to create separate call scripts to define KERNELTAG.

[Stable vs mainline for Next]

Hi Wilcat,

 

Thanks for the response. The sunxi-ss has a bug... that's primarily the reason I wanted to test 4.3.

 

I emailed the driver developer about that error. He has submitted a patch to fix that problem... here's a link to the patch request:

 

https://lkml.org/lkml/2015/11/5/91

​

[Stable vs mainline for Next]

Igor,

 

I noticed that your build script automatically parses a URL to determine what the current stable release is for "Next".

 

Since 4.3 is now officially released and has a number of features worth checking out, it would be nice if the build script offered an option to pick from stable vs. mainline.

 

For now I am just manually setting the KernelTag to "4.3", but it would be nice not to have to modify any of the scripts manually and have this be an option you can pick from.

 

Just a suggestion...

 

Thanks.

[Error at end of build]

Ok, will do.

 

Thanks Igor!

[Error at end of build]

FYI - seeing the following error on completion of a build... I suspect it's transient since it just seems to be verifying the image...

 

"Re-reading the partition table failed.: Invalid argument​"

 

Image build seems to otherwise complete successfully. Haven't tested the image yet.

 

This was building a BPi image for Jessie using the "next" (latest) kernel.

[CRC failed error extracting Jessie zip]

I cleaned all my folders, synched libs to the latest and kicked off a new build and it seems to be fine now. Not sure what was causing the hiccup before, but all is good now.

[CRC failed error extracting Jessie zip]

I created a Wheezy and Jessie image. Whenever I try extracting the Jessie image, I get a CRC error. I am using 7zip. I tried extracting the zip also using Windows Explorer (Win10) and it also runs into an error.

 

It seems like there might be an issue with the Jessie images being created. I cleaned my output folder and created a new clean image and still run into the same problem. This is using the latest libs and creating a 4.2.3 image (the default settings in the lib config).

 

FYI, the Wheezy image extracts without any problems.

 

Any ideas why the Jessie image is corrupt?

 

Thanks.

[Getting stuck generating image]

I think I got to the bottom of the problem.... I don't believe it is related to Armbian at all or the httpredir URL.

 

I think the problem is related to my upgrading pfsense to the latest 2.3 Alpha and one of the firewall rules for DNS starting behaving strangely. I have removed the rule and the problems seemed to have gone away.

 

Just in case anyone else is running pfsense and running into similar issues....

[Getting stuck generating image]

The fix you mentioned earlier in the thread earlier which shows a change to the debootstrap line.

 

I will try configuring my sources list manually and seeing how that works.

[Getting stuck generating image]

I removed the cached root filesystem and got the latest libs files, and I am still getting the same error on the same 2 files viz.

 

[ error ] Installation failed
Failed to fetch http://httpredir.debian.org/debian/pool/main/libn/libnl/libnl1_1.1-7+b1_armhf.deb Could not resolve 'httpredir.debian.org'
Failed to fetch http://httpredir.debian.org/debian/pool/main/libn/libnl/libnl-dev_1.1-7+b1_armhf.deb Could not resolve 'httpredir.debian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?​

 

 

I noticed the fix you made is for Jessie.... I am running into this problem creating a Wheezy image.

[Getting stuck generating image]

I *think* this problem was related to not seeing the status window when building the image via SSH. If I leave it long enough.. it seems to get past this stage and then aborts due to the "Failed to fetch http://httpredir.debian.org/debian/pool/main/libn/libnl/libnl1_1.1-7+b1_armhf.deb"error (which I posted in another thread about).

[Creating image - httpredir.debian.org name resolution errors]

So I don't think this is due to DNS.... I noticed that the error is occurring on the same 2 files every time i.e.:

 

 

[ o.k. ] Fixing release custom applications. [ wheezy ]
[ error ] Installation failed
Failed to fetch http://httpredir.debian.org/debian/pool/main/libn/libnl/libnl1_1.1-7+b1_armhf.deb Could not resolve 'httpredir.debian.org'
Failed to fetch http://httpredir.debian.org/debian/pool/main/libn/libnl/libnl-dev_1.1-7+b1_armhf.deb Could not resolve 'httpredir.debian.org'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?​

 

It also happens when I changed the apt sources list....

 

Failed to fetch http://mirrors.ocf.berkeley.edu/debian/pool/main/libn/libnl/libnl1_1.1-7+b1_armhf.deb Could not resolve 'mirrors.ocf.berkeley.edu'
Failed to fetch http://mirrors.ocf.berkeley.edu/debian/pool/main/libn/libnl/libnl-dev_1.1-7+b1_armhf.deb Could not resolve 'mirrors.ocf.berkeley.edu'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?​

 

 

Any idea why it's failing at this point, and is there a way I could get around this?

 

Thanks.

[Getting stuck generating image]

Aside from the DNS resolution issue I am having (different thread), I am often getting stuck on the following:

 

Unpacking locales (from .../locales_2.13-38+deb7u8_all.deb) ...
Processing triggers for man-db ...
Setting up locales (2.13-38+deb7u8) ...
Generating locales (this might take a while)...
Generation complete.
Generating locales (this might take a while)...
  en_US.UTF-8... done
Generation complete.​

 

 

It just sits there and nothing further happens. I have left it for 30 minutes or more, and still nothing. I usually end up killing it... rebooting and then restarting. When it does get past this, I typically end up with the debian sources DNS resolution issue which I documented on a different thread.

 

Any idea what is causing it to get stuck here? I am wondering if this is somehow related to the DNS resolution issue I am having as well.

 

These problems only started occurring over the last couple days... I never had an issue with image generation before that. I did update to the latest libs a while ago, so I am not sure if something changed that is now contributing to this.

 

Thanks.

 

[Creating image - httpredir.debian.org name resolution errors]

I tried changing the defaults to the ones generated by the generator, but no luck.

 

I also tried deleting my VM and creating a new one (I generate my images in a VM) and am still running into the same issue.

 

I am not sure if it's something related to my DNS servers.. I'll try new DNS servers and see if that makes a difference.

[Creating image - httpredir.debian.org name resolution errors]

Anyone?

 

I am still having this problem even after cleaning my folders and trying multiple times. I can ping and browse to the destination folder just fine (the httpredir address), but the installation always seems to fail with the same error.

[Creating image - httpredir.debian.org name resolution errors]

I recently started getting these errors constantly... not sure what's going on. I can ping the address just fine, and even if I modify the lib config sources file to change it to ftp.us.debian.org, I still seem to run into the same errors.

 

Any suggestions on what might be causing the problem?

 

[ error ] Installation failed
Failed to fetch http://httpredir.debian.org/debian/pool/main/libn/libnl/libnl1_1.1-7+b1_armhf.deb Could not resolve 'httpredir.debian.org'​

 

Thanks.

 

[Slow network speed]

Thanks for the feedback... I may have had a faulty Ethernet cable. I swapped cables as well as ports on my switch, and now speed seems much better, and more consistent with my other BPi running 3.4.

[Older image errors on building]

Thanks, it's working now.

[Older image errors on building]

I am trying to build an older image (i.e. not latest / next). I select wheezy and default (3.4 - 3.14 kernel). I did not modify compile.sh in any way.

 

When building, I seem to constantly run into these errors:

 

 

/root/armbian3/lib/boards.sh: line 217: cd: /root/armbian3/output/cache/sdcard/usr/src/linux-headers-: No such file or directory
[ o.k. ] Compile kernel headers scripts
/bin/bash: line 0: cd: /usr/src/linux-headers-: No such file or directory
make: *** No rule to make target `headers_install'.  Stop.
make: *** No rule to make target `scripts'.  Stop.
dpkg-deb: error: failed to read archive `/root/armbian3/output/debs/linux-headers-banana_4.4_armhf.deb': No such file or directory
dpkg-deb: error: failed to read archive `/root/armbian3/output/debs/linux-headers-banana_4.4_armhf.deb': No such file or directory
cp: cannot copy a directory, ‘.’, into itself, ‘/root/armbian3/output/cache/building/repack/usr/src/linux-headers-/.’
dpkg-deb: error: failed to open package info file `/root/armbian3/output/cache/building/repack/DEBIAN/control' for reading: No such file or directory
tar: ./building/linux-cache-banana_4.4_armhf.deb.tgz: file changed as we read it
tar: ./sdcard/run/dbus/system_bus_socket: socket ignored
tar: ./sdcard/run/sdp: socket ignored
tar: ./sdcard/proc/sys/net/ipv4/route/flush: Cannot open: Permission denied
tar: ./sdcard/proc/sys/net/ipv6/route/flush: Cannot open: Permission denied
tar: ./sdcard/proc/sys/vm/compact_memory: Cannot open: Permission denied​

 

 

I don't have a problem building a 4.2 image.. the problem only seems to occur when trying to build an older image (based on 3.4 - 3.14).

 

Any ideas as to what's going on and how I can fix it?

 

Thanks.

[Slow network speed]

I have a BananaPi running 4.2 (with Wheezy) and I am getting poor network speed. When testing download a file from the internet, I am averaging ~500k/s.

 

I have another BananaPi running 3.4 (also with Wheezy) and on that board, I am averaging ~3MB/s downloading the same file from the same location.

 

I tested this multiple times and the results are pretty much the same.

 

Any idea why network performance is so poor on 4.2?

 

Thanks.

[Partition not resizing]

For some reason the first run script didn't run. It went straight to a login prompt with no initial first run. There were a couple errors on startup. Looks like it didn't install all dependent packages e.g. toilet, lsusb and some others I can't remember. This was the second "clean" image I built i.e. I deleted everything and rebuilt from scratch (pulling all source again). Something might be broken in the sources.

 

I can try running it manually next time. I did fix the partition issue for now by deleting the partition and recreating it manually in fdisk and then running resize2fs.

[Network not coming up]

Thanks Igor,

 

I did try power cycling multiple times, with no luck.

 

I'll stick with Wheezy until this is resolved.

[Partition not resizing]

I recently created some new images using the most recent armbian scripts. For some reason my Jessie image is not coming up (see my other thread regarding network not coming up), but I did managed to get a wheezy image up and running on my BananaPi using latest / next.

 

The problem I am having is the partition size is extremely small (about 500-600MB) and does not appear to be resize to fully utilize the SD card. It's been a long while since I created an image, but I vaguely remember the image resizing to maximize the SD card space.

 

I basically had to manually resize the image by deleting and recreating the partition.

 

Is there some way to specify the image size to create or to force resizing on first boot?

 

Thanks.

[Network not coming up]

I created a Jessie image for BananaPi with the latest / next kernel, and when booting the image, it get's stuck on "A start job is running for LSB: Raise network interfaces". It never seems to complete raising the interface, and since there is no time limit, this goes on forever.

 

Creating a Wheezy image seems to work fine (also using latest / next kernel).

 

Any suggestions on how I can get the Jessie image up and running?

 

Thanks.