wildcat_paris

I agree that this is not "core functionality" to the SoC of the board, but it is "core functionality" to the SBC Lamobo R1, whether some people like it or not.
I fully agree with second line above and without your work, help, support so many of us only had a paper weight.
 
Last but not least, can 2 or 3 of us R1 owners test the release candidate before you release it - or what else can be done to keep it 'stable' ?

I made a quick test on Orange Pi One and I could boot into self build kernel 4.7.4 ... network works, but only one CPU is detected. I did not investigate why ...
 
Since we are talking about immature kernel, problems are expected. This kernel is from our point of view still in testing mode and not yet for usage so we don't support it. If it does not work, you are basically on your own. Of course we will try to help and we are happy to get feedback and if it's possible, we will fix it, but not right on the spot.

Yes, we could (formally) engage more people into developing process as testers. It could be helpful and we would be little relieved.
 
Perhaps we start to seek & assign few testers / maintainer for each board? We can provide access to daily upgrades to make things easy on technical level. I can provide extra repository (aptdev.armbian.com) with daily updated deb packages, while creating images takes way too much time for daily builds. I am already working on this for some time and it's not far away from running it daily.
 
Subforum "Development" is not that busy, so we can have those things here.

Except that
This is not "our code", this is wrong configuration for someone else's code This is not "core functionality" and can easily be fixed by replacing a single file We don't have all the boards that are listed on download page, some boards are just assumed to work since they are similar to others Even if we wanted to extensively test all the images, it would probably take several weeks and a box of microSD cards to do it

@Mikhail
 
while this one (generating swconfig*15.04*.deb) seems to be broken
https://github.com/jekader/swconfig
 
this one (also doing debian packaging "debuild -uc -us" and closer to openwrt) works ok
https://github.com/xypron/swconfig
 
edit:
before using debuild -uc -us
./autogen.sh has to be launched (if not there is no binary)

Old swconfig
 
# ldd swconfig
linux-vdso.so.1 (0xbee4d000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6f6b000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6e7a000)
/lib/ld-linux-armhf.so.3 (0x7f601000)
 
new swconfig
 
# ldd swconfig
linux-vdso.so.1 (0xbef88000)
libnl-3.so.200 => /lib/arm-linux-gnueabihf/libnl-3.so.200 (0xb6f11000)
libnl-genl-3.so.200 => /lib/arm-linux-gnueabihf/libnl-genl-3.so.200 (0xb6f04000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6e14000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb6df1000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6d7d000)
/lib/ld-linux-armhf.so.3 (0x7f628000)
 
The pthread library seems out of place here.
 
@goldfish the difference in size is because the new is stripped
 
Even then, after stripping
 
root@ruir:/sbin# ls -la swconfig
-rwxr-xr-x 1 root root 23276 Sep 17 04:30 swconfig
root@ruir:/sbin# ls -la swconfig.new
-rwxr-xr-x 1 root root 11444 Sep 16 20:10 swconfig.new

@goldfish_paris
@Rui Ribeiro
 
Difference in size and used libraries suggests that the old binary was statically linked with libnl* and stuff, the newer one wasn't.

@Rui Ribeiro
Thanks, I hope this will be sorted out in next release, meanwhile we need to find and test working sources for swconfig and use precompiled one before that.

@Rui
Cool, so we have a workaround solution for others Lamobo-R1 Armbian users

@goldfish, your binary restored my switch

@Rui
 
check if you still have the old binary in /usr/local/bin/
whereis swconfig
 
test it then overwrite the /sbin/swconfig
so Zador has spare time to fix this problem

Probably default compiler settings for packaging are wrong, I'll have to tweak these and make some versions for testing.

Hi,
 
Did today a kernel update...upon reboot, has no connectivity. I have lost swconfig; copied the one that comes with the sdcard/img download, it booting the switch by default, but does not allow to do much more...the reset and set operations are giving an error.
 
What could I do?

Here it is Zador. I only have one swconfig, unlike goldfish
 
#swconfig dev eth0 help
switch0: eth0(BCM53125), ports: 9 (cpu @ 8), vlans: 4096
     --switch
        Attribute 1 (int): enable_vlan ((null))
        Attribute 2 (string): ports ((null))
        Attribute 3 (int): reset_mib ((null))
        Attribute 4 (int): enable_jumbo ((null))
        Attribute 5 (int): allow_vid_4095 ((null))
        Attribute 6 (unknown): apply ((null))
        Attribute 7 (unknown): reset ((null))
     --vlan
        Attribute 1 (ports): ports ((null))
     --port
        Attribute 1 (string): mib ((null))
        Attribute 2 (int): pvid ((null))
        Attribute 3 (string): link ((null))

I allready tried a new image and that didn't boot, but I should have a uard to usb here somewere.
I try loading a new image file and see were it stops
 
edit: It starts to boot with a fresh image, but than goes into emergency mode asking for the root paswort.
I can use the board then but the openssh-server is dead and can't be startet and I don't get the normal login screen or first time setup
 
edit2: It goes into emergency mode after using 1:30m on A start hob is running fir dev-mmcblk0p1.device
 
edit3: and before that "Failed to start Load Kernel Modules"
and directly after: [DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems. [DEPEND] Dependency failed for File System Check on /dev/mmcblk0p1.   edit4: The entire uart output during boot:  
 
I do not understand why it's trying to load something from mmcblk0 wenn it's not mentions in the boot.ini file. The 2 existing partitions are mmclk1p1 and mmclk1p2

That is what i was doing before. I tried it again just to make sure but it's leads to at not booting system. The line in my bbot.ini is sligtly different btw:
setenv bootcmd "fatload mmc 0:1 0x40008000 zImage; fatload mmc 0:1 0x44000000 dtb/exynos5422-odroidxu3.dtb; bootz 0x40008000 0x44000000" One of the numbers at the end is missing.
I just tried to compile a complitly new image with the current kernel and that image file can't be booted either.

Leak from Xunlung lab:
 

 
Kernel 3.10.x
Some info about H5:
http://www.cnx-software.com/2015/04/15/allwinner-h-series-ott-soc-roadmap-adds-h5-and-h2-processors/

@goldfish_paris
The boot partition seems to be mountet at /boot by default. If I open the sd on another machine (sadly windows) the boot partition contains the same files as /boot while running:
boot.bmp dtb-4.7.3-odroidxu4.old boot.ini System.map-3.10.103-odroidxu4 config-3.10.103-odroidxu4 uInitrd dtb-3.10.103-odroidxu4 vmlinuz-3.10.103-odroidxu4 dtb-3.10.103-odroidxu4.old zImage dtb-4.7.3-odroidxu4 dpkg has aparently created the new dtb folders but not copied the kernel files. That kinda wierd but manualy extracting the deb files and moving the files to there places should have the same effect (or am I missing something)

The /boot (on the second partition after I unmounted the other partition) contained the other kernel files. I tried to copy them but 2 of them are symlinks and the /boot patition is a FAT partition (zImage and dtb).
Without those symlinks the system does not reboot and making a normal copy and rename does not work either.

Current main Armbian build hardware is a desktop based "server" running Ubuntu Xenial - i7 4790 / 16 / SSD. We already made lots's of optimisations within the build process but for 140 images I still need up to 14 hours where kernels were already cached.
 
How is it possible to cut this time down significantly - to few hours, perhaps on a server grade hardware and further code optimisations? Currently I don't have access to any much better hardware to just run "build all" and see.
 
I am looking for specific ideas for a build server upgrade and sponsored rent / exchange for advertisement. I was already advised by a friend, who knows something about server hardware: "Just get an 2 x E5-2667v4 and an ASUS board with onboard M2 ssd" ... but this is (far) out of the reach and rather stupid to own such a costly device for those rear events.

i have listened to the 'cast. promises to be a good series and a decent interviewer to boot

73 minutes of audio about Tech and... Igor's Armbian
 
https://code4sale.com/sbc/?go=2016%2fsbcvps-0001-2016-06-05

Thank you for your reply.
 
I have the build enviroment set up, I did not know about the RT patch for latest kernel. I 'll look in to that and let you know what happens.
The thing is that in kernel menuconfig which is invoked by the build script there is no option to set up tick frequency. There is just one option to setup tickless kernel or not (I 'm wondering what will happen if unchecked since no tick frequency options are available). From a little diging around in varius .config files I could find there are no CONFIG_HZ=100 or 250 or 500 or 1000 lines
neither CONFIG_HZ_100=y or n or not set. I tried to set this up in linux_sunxi/.config but it seems it get overwriten by the script. Could you point me to the proper .config or .config template being used by armbian?
 
Thank you

Hi Goldfish_Paris,
I've downloaded the hardfloat packages and will try to figure out how to get that going on Jessie Headless.   I'm trying to get Ubiquiti's Unifi Controller software running on Odroid.  It runs on Raspbian on the Pi3 and I believe the secret is the Oracle hard float Java.  At least from posts I've seen detailing prior failures (Odroid users) and prior successes (Odroid C1 and Raspberry Pi 2/3 users).
 
Wish me luck haha.

Yes, I did.  Corrected. 
 
Thanks.