Jump to content

More proper testing - better Armbian experience

Igor

By Igor
in Advanced users - Development

 Share

Recommended Posts

Igor

Igor

Posted
Posted

In order to make armbian better, we need your help with testing. 
 
Why?

  • there are simply too many boards to handle,
  • there are task which can't be automatized,
  • there are bugs which are not seen from our perspective.

What kind of tests?
 
retro_beta_tester1.jpg

  • booting, user creation, updates, upgrades
  • checking if basic supported functions work: video, audio, network, wireless, AP mode
  • do nasty thing to your board and report.

How to test?

and / or

  • change to our daily build developer repository: 
deb http://beta.armbian.com $(lsb_release -cs) main utils $(lsb_release -cs)-desktop

Note: you are entering developer area and things will sometimes be completely broken. Don't use this repository in production!
 
When bug is found?
 
* Provide logs with armbianmonitor -u or type as much data as you can.
 
bug-41.png

 

  Reveal hidden contents

 

3
tkaiser

tkaiser

Posted
Posted

Well, it seems getting feedback on boards that are already working is a bit hard. Why not using boards for this kind of stuff that are officially not supported (read also as 'not meant to be used productive now') but people are keen on trying out Armbian on it?

 

What about adding the NanoPi Air image to the list and posting links to the appropriate threads?

Igor

Igor

Posted
  • Author
Posted

Yes, good idea. Added, will be available in next run. 

Steve Medley

Steve Medley

Posted
Posted

OK. I finally got to boot up the image. Got the following:

U-Boot 2012.07 (Oct 20 2016 - 10:51:36) for Exynos5422

CPU: Exynos5422 Rev0.1 [Samsung SOC on SMP Platform Base on ARM CortexA7]
APLL = 800MHz, KPLL = 800MHz
MPLL = 532MHz, BPLL = 825MHz

Board: HardKernel ODROID
DRAM:  2 GiB
WARNING: Caches not enabled

TrustZone Enabled BSP
BL1 version: /
VDD_KFC: 0x44
LDO19: 0xf2

Checking Boot Mode ... SDMMC
MMC:   S5P_MSHC2: 0, S5P_MSHC0: 1
MMC Device 0: 7.4 GiB
MMC Device 1: 29.1 GiB
MMC Device 2: MMC Device 2 not found
there are pending interrupts 0x00000001
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 

** Unable to use mmc 0:1 for fatload **
Unknown command 'ext4load' - try 'help'
Unknown command 'ext4load' - try 'help'
>>> Load Boot Script from mmc 0:1 <<<

** Unable to use mmc 0:1 for fatload **
>>> Load Boot Script from mmc 0:2 <<<
** Partition 2 not valid on device 0 **

** Unable to use mmc 0:2 for fatload **
>>> Run Default Bootcmd <<<
reading kernel..device 0 Start 1263, Count 16384 
MMC read: dev # 0, block # 1263, count 16384 ... 16384 blocks read: OK
completed
reading RFS..device 0 Start 17647, Count 2048 
MMC read: dev # 0, block # 17647, count 2048 ... 2048 blocks read: OK
completed
Bad Linux ARM zImage magic!
Exynos5422 #

Going to look into it a bit further...

1
Steve Medley

Steve Medley

Posted
Posted
  Quote

 

 

Ext4 support is missing in odroid-specific u-boot config - added with a patch, will need a new test image

 

Thanks. I quickly realised that was the problem when i typed help at the prompt and found the ext4load command missing.

 

Going to download the sources next so i can build my own test images and get a bit more familiar with the build process. I have built my own Armbian images in the past for CB2, but that was before it was even called Armbian and only supported CB2 and cubietruck. A lot has changed since then

1
zador.blood.stained

zador.blood.stained

Posted
Posted

Looks like it crashes due to wrong kernel command line processing in the boot script, so all single partition and ext4 changes are working and only boot script needs to be adjusted.

Also can you please provide output of "env print" from u-boot command prompt?

Steve Medley

Steve Medley

Posted
Posted

env print output:

Exynos5422 # env print
baudrate=115200
bootargs=fb_x_res=1280 fb_y_res=720 vout=hdmi led_blink=1
bootcmd=    cfgload;    mmc rescan 0:1; mmc rescan 0:2;    if run loadbootscript_1;         then run bootscript;     else        if run loadbootscript_2;           then run bootscript;        else            run default_bootcmd;        fi ;    fi ;
bootdelay=1
bootscript=source 40008000
copy_uboot_emmc2sd=emmc open 0;movi r z f 0 40000000;emmc close 0;movi w f 1 40000000;emmc open 0;movi r z b 0 40000000;emmc close 0;movi w b 1 40000000;emmc open 0;movi r z u 0 40000000;emmc close 0;movi w u 1 40000000;emmc open 0;movi r z t 0 40000000;emmc close 0;movi w t 1 40000000;mmc write 1 0x40008000 0x4CF 0x20;
copy_uboot_sd2emmc=movi r f 0 40000000;emmc open 1;movi w z f 1 40000000;emmc close 1;movi r b 0 40000000;emmc open 1;movi w z b 1 40000000;emmc close 1;movi r u 0 40000000;emmc open 1;movi w z u 1 40000000;emmc close 1;movi r t 0 40000000;emmc open 1;movi w z t 1 40000000;emmc close 1;mmc write 1 0x40008000 0x4CF 0x20;
default_bootcmd=echo >>> Run Default Bootcmd <<<;movi read kernel 0 40008000;movi read rootfs 0 41000000 100000;bootz 40008000 41000000
env_erase=mmc write 0 0x40008000 0x4CF 0x20;
loadbootscript_1=echo >>> Load Boot Script from mmc 0:1 <<<;fatload mmc 0:1 40008000 boot.scr
loadbootscript_2=echo >>> Load Boot Script from mmc 0:2 <<<;fatload mmc 0:2 40008000 boot.scr
loadbootscript_3=echo >>> Load Boot Script from mmc 1:1 <<<;fatload mmc 1:1 40008000 boot.scr
loadbootscript_4=echo >>> Load Boot Script from mmc 1:2 <<<;fatload mmc 1:2 40008000 boot.scr
rootfslen= 100000
stderr=serial
stdin=serial
stdout=serial

Environment size: 1657/16380 bytes
Code4Sale LLC

Code4Sale LLC

Posted
Posted

I looked at the spoilers and see folks and boards listed, but don't quite understand. Are they covered? Need more coverage?

 

I have two ODROID C2's that I need to put an OS on (the last odroid updates rendered them useless). I am very time limited, but want to help.

 

I also have XU4's and Pine64's, but would rather take on the C2's (kill two birds - one stone - the C2's are in need).

 

Do you prefer me to use the prebuilt images, or the otherway? I could do either.

 

Is there someone that can coordinate these efforts? I'm thinking that this looks like a "free for all" and is in need of a little direction for a new guy coming in the door wanting to help.

 

Call me stupid, but I am thinking something like really clear "A-B-C" instructions:

 

a) Pick Board

 

--B) Use this image

 

----c)  Do this
 
--------d)  Report results here
 
Just saying, if we could coordinate needs, we could coordinate the incoming offers to help, and you will get coordinated results.
 
It's gotta be fast and easy to figure out what you need, fast and easy to report, fast and easy to update needs, and fast and easy to find.
 
So what can be done to help an idiot like me provide useful help to really smart folks like you  guys?
 
Joe
2
wildcat_paris

wildcat_paris

Posted
Posted
  On 10/24/2016 at 4:03 PM, zador.blood.stained said:

I updated the boot script, though I am not sure why kernel didn't pick up command line from u-boot and whether it is fixed now.

 

@zador.b.s

your latest updates for XU4/next (uboot 2016.09) are working fine on SD, I will check when possible for legacy

 

  Reveal hidden contents

 

edit: for eMMC, the sd_fusing.sh script is needed to wipe out uboot 2012.07 from "boot0" with 2016.09. if not wiped, booting is weird/KO.

1
Code4Sale LLC

Code4Sale LLC

Posted
Posted

The ODROID C2 image as listed below seems to work great! I am very pleased.

 

Sound, video, network are all very good. USB devices (flash drives etc) performed exceptionally well and and as expected.

 

I even tested the PayPal button. It worked fine (tested with 22 Euros). I encourage others to continue testing this very important feature using the same and or other amounts, as my ability to test this important feature testing is not nearly sufficient.

 

This image boots fast. Very very fast. I used a sandisk ultra SD card. I plan to try both the samsung and that other brand (ODROID red using with the XU4) of EEMC cards later tonight. Honestly, it run so fast now, I don't know what to think. I often have corruption troubles with EEMC on the C2 using the manufactures images. It would not surprise me to find that armbian would run perfectly stable on EEMC.

 

At Igor's request, I did perform "nasty things" to the board, however, I'm a little embarrassed to publicly admit any testing I did in this area. Let's just put it into the "extreme" category, and call it good (OK, it was great... really really great).

 

I looked over the list of what you need, and saw nothing in particular that needs testing for this image, so IMHO, I would call this image good (great) and ship it! It beats the hell out of the manufacturers image (that rendered itself unbootable on two different devices).

 

If you need me to perform any particular test, please let me know... If it is in the nasty category, it will have to wait, as I am a bit spent at the moment from this exceptional boot.

 

Much thanks go out to Igor and the team! My boards would not boot without you and your fine work!

 

Tested Image: http://image.armbian.com/betaimages/Armbian_5.23.161025_Odroidc2_Ubuntu_xenial_3.14.79_desktop.7z

 

Joe

2
Igor

Igor

Posted
  • Author
Posted

Thanks Joe!

 

The idea is to establish a small team, which would help us test the boards upon request. Within 2-3 weeks before planned update. If we would made more changes, more testing will be required. We want to make sure that upgrade does not break the board's core functionality at first place, than we need to try to find hidden bugs and document them under "known problems" what was found in last moment.

 

Specific details about this process are still adjusting, but roughly this is it. 

 

When I cooked my first image, it was easy and I had a lot of fun trying to find and fix a problem. I like doing that  :) but I simply can not. Today, this task can be done only together.

3
Code4Sale LLC

Code4Sale LLC

Posted
Posted

 

Igor said "Today, this task can be done only together"

 

 

Right you are!

 

I wish to help as best as possible.

 

I posted about the need, and am happy to say it was reposted to various communities at least 6 times in this very short time.

 

I cannot think of a more deserving project - thank you!

2
wildcat_paris

wildcat_paris

Posted
Posted

@zador.blood.stain

logs for legacy XU4

 

  Reveal hidden contents

 

short:

[    7.905185] [c6] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    7.911928] [c6] Please append a correct "root=" boot option; here are the available partitions:
[    7.920718] [c6] b300        31276032 mmcblk0  driver: mmcblk
[    7.926411] [c6]   b301         1214464 mmcblk0p1 01380d35-01
[    7.932109] [c6] 0800       488386576 sda  driver: sd
[    7.937171] [c6]   0801       488383488 sda1 e72d222d-01
[    7.942452] [c6] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
wildcat_paris

wildcat_paris

Posted
Posted

@zador.blood.stain

I have tried uboot 2012.07 & boot.ini, uboot 2016.09 & boot.cmd (with and without UUID, removing ArmbianEnv.txt as well, putting /dev/mmcblk0p1 for root)

but I end always with

[    7.905375] [c6] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
[    7.912127] [c6] Please append a correct "root=" boot option; here are the available partitions:
[    7.920918] [c6] b300        31276032 mmcblk0  driver: mmcblk
[    7.926612] [c6]   b301         1214464 mmcblk0p1 65a81a70-01
[    7.932308] [c6] 0800       488386576 sda  driver: sd
[    7.937370] [c6]   0801       488383488 sda1 e72d222d-01
[    7.942651] [c6] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)

 

  Reveal hidden contents

 

Igor

Igor

Posted
  • Author
Posted

Ideally I would like to see no more than something like this:

                Boot         Network         HDMI         Install           Date          Performed by
------------------------------------------------------------------------------------------------------
Lamobo R1        yes             yes          yes             yes            x.y.2016          JohnDoe
Odroid XU4        no www.link-to-boot-log.com
Odroic C1        yes 
...
...

: 

1
zador.blood.stained

zador.blood.stained

Posted
Posted
  On 10/27/2016 at 1:48 AM, wildcat_paris said:

uboot doesn't seem to be able to pass root= to the kernel

edit:

with uboot 2016.09 & legacy kernel I had to rename /boot/dtb/*xu4* with xu3

U-boot doesn't pass command line to the kernel at all. I'll try to poke at boot script and kernel config more.

wildcat_paris

wildcat_paris

Posted
Posted
  On 10/27/2016 at 4:44 AM, Igor said:

Ideally I would like to see no more than something like this:

 

Board                 Branch        Boot         Network         HDMI                      Install           Date             Performed by      link

-----------------------------------------------------------------------------------------------------------------------------------------------------

Lamobo R1        Legacy        ?              ?                    ?                           ?                  ?                  ?

Lamobo R1        Vanilla         ?              ?                    ?                           ?                  ?                  ?

Odroid XU4        Legacy        No            -                     -                           SD                20161027    wildcat_paris       http://pastebin.com/LA1sUa49

Odroid XU4        Vanilla         Yes           Yes                console only         SD                20161026    wildcat_paris       ?

 

comments:

- I cannot find a proper/easy way to write a result table on the forum +  impossible to use "tab" key to separate elements  (only spaces)

=> is there an extension of the forum to add tables ???

 

I would propose to create a new  "sticky" post:

- first message is the summary of all reports for a beta version (I would propose I do the updates here) from...

- testers can put their latest results in this thread and I would update the messages in the first post (as a summary)

 

- maybe you may reinstall wildcat_paris with proper rights to manage the "testing thread" (& available to help more in forum as previously)

arox

arox

Posted
Posted
  On 10/27/2016 at 4:44 AM, Igor said:

Ideally I would like to see no more than something like this:

 

Boot         Network         HDMI         Install           Date          Performed by
------------------------------------------------------------------------------------------------------
Lamobo R1        yes             yes          yes             yes            x.y.2016          JohnDoe
Odroid XU4        no www.link-to-boot-log.com
Odroic C1        yes 
...
...
:

Well, perhaps provide a html form ouside of the forum. Something very simple at beginning but that could be enhanced to provide more inputs and generate reports.

Igor

Igor

Posted
  • Author
Posted
  Quote
I would propose to create a new  "sticky" post:

 

We are not there yet since I don't know yet how we will do it. And It depends -  if we collect data mostly automatically, than we better provide some html, generated based on auto submitting. If no data went trough for certain boards, than either tester(s) failed to test or it does not boot at all.

 

Let's see how far we can come with automated approach. 

 

I need some days off so I won't jump to coding in any case.

1
zador.blood.stained

zador.blood.stained

Posted
Posted
  On 10/27/2016 at 1:48 AM, wildcat_paris said:

edit:

with uboot 2016.09 & legacy kernel I had to rename /boot/dtb/*xu4* with xu3

So it does boot fine? We can always switch DTB file name by checking /boot/.next, like in sunxi boot script.

arox

arox

Posted
Posted

"If no data went trough for certain boards, than either tester failed to test or it does not boot at all."

 

If no data is auto-submitted, it indicates that network is not fully configured - not that the board doesn't boot. Or that it does not pass threw the firewall as in my case anyway ... In any case, you should explicitly ask permission for reporting.

1
tkaiser

tkaiser

Posted
Posted
  On 10/27/2016 at 12:03 PM, arox said:

If no data is auto-submitted, it indicates that network is not fully configured - not that the board doesn't boot. Or that it does not pass threw the firewall as in my case anyway ... In any case, you should explicitly ask permission for reporting.

I agree and I vote also for collecting feedback prior to start any work. I could imagine a simple HTML form accessible through GET method so a test mechanism can either submit data in an automated way or provide an URL that's ready for copy&paste.

 

Please note that some ideas exist already -- please see https://github.com/igorpecovnik/lib/issues/512 and https://github.com/igorpecovnik/lib/issues/511#issuecomment-256420416. We must ease helping users testing through new releases and upgrade procedure so exactly this sort of feedback has to be collected NOW.

1
wildcat_paris

wildcat_paris

Posted
Posted

@zador.blood.stain

  On 10/27/2016 at 11:59 AM, zador.blood.stained said:

So it does boot fine? We can always switch DTB file name by checking /boot/.next, like in sunxi boot script.

yes it "kind of" boots, but the system cannot go any further with root=<null>

 

Sure the dtb file renaming is a "detail" I can handle.

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept