1 1
danman

Armbian 20.05.1 Focal images could be broken

Recommended Posts

Hi, I have tried to run Armbian_20.05.1_Orangepizero_focal_current_5.4.43.img.xz but it doesn't work, see here:

U-Boot SPL 2020.04-armbian (May 30 2020 - 18:49:32 +0200)                       
DRAM: 256 MiB                                                                   
Trying to boot from MMC1                                                        
                                                                                
                                                                                
U-Boot 2020.04-armbian (May 30 2020 - 18:49:32 +0200) Allwinner Technology      
                                                                                
CPU:   Allwinner H3 (SUN8I 1680)                                                
Model: Xunlong Orange Pi Zero                                                   
DRAM:  256 MiB                                                                  
MMC:   mmc@1c0f000: 0, mmc@1c10000: 1                                           
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial          
Out:   serial                                                                   
Err:   serial                                                                   
Net:   phy interface0                                                           
eth0: ethernet@1c30000                                                          
starting USB...                                                                 
Bus usb@1c1a000: USB EHCI 1.00                                                  
Bus usb@1c1a400: USB OHCI 1.0                                                   
Bus usb@1c1b000: USB EHCI 1.00                                                  
Bus usb@1c1b400: USB OHCI 1.0                                                   
Bus usb@1c1c000: USB EHCI 1.00                                                  
Bus usb@1c1c400: USB OHCI 1.0                                                   
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found                   
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found                   
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found                   
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found                   
scanning bus usb@1c1c000 for devices... 1 USB Device(s) found                   
scanning bus usb@1c1c400 for devices... 1 USB Device(s) found                   
       scanning usb for storage devices... 0 Storage Device(s) found            
Autoboot in 1 seconds, press <Space> to stop                                    
switch to partitions #0, OK                                                     
mmc0 is current device                                                          
Scanning mmc 0:1...                                                             
Found U-Boot script /boot/boot.scr                                              
3789 bytes read in 4 ms (924.8 KiB/s)                                           
## Executing script at 43100000                                                 
U-boot loaded from SD                                                           
Boot script loaded from mmc                                                     
181 bytes read in 3 ms (58.6 KiB/s)                                             
13650370 bytes read in 1038 ms (12.5 MiB/s)                                     
7236248 bytes read in 552 ms (12.5 MiB/s)                                       
Found mainline kernel configuration                                             
29861 bytes read in 12 ms (2.4 MiB/s)                                           
504 bytes read in 8 ms (61.5 KiB/s)                                             
Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo                      
504 bytes read in 8 ms (61.5 KiB/s)                                             
Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo                      
4185 bytes read in 8 ms (510.7 KiB/s)                                           
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)                   
## Executing script at 44000000                                                 
## Loading init Ramdisk from Legacy Image at 43300000 ...                       
   Image Name:   uInitrd                                                        
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)                      
   Data Size:    13650306 Bytes = 13 MiB                                        
   Load Address: 00000000                                                       
   Entry Point:  00000000                                                       
   Verifying Checksum ... Bad Data CRC                                          
Ramdisk image is corrupt or invalid                                             
SCRIPT FAILED: continuing...                                                    
                                

I tried both torrent and http downloads and two microSD cards, the sha checksum is correct too:

danman@silverhorse:~/Downloads$ sha256sum Armbian_20.05.1_Orangepizero_focal_current_5.4.43.img.xz
12dd233cc434435027e4756ce752b8aad40307eadda613cf2b225cb8b209da9b  Armbian_20.05.1_Orangepizero_focal_current_5.4.43.img.xz
danman@silverhorse:~/Downloads$ cat Armbian_20.05.1_Orangepizero_focal_current_5.4.43.img.xz.sha 
12dd233cc434435027e4756ce752b8aad40307eadda613cf2b225cb8b209da9b *Armbian_20.05.1_Orangepizero_focal_current_5.4.43.img.xz

 

The Armbian_20.05.1_Orangepizero_buster_current_5.4.43.img.xz works without any problem.

Share this post


Link to post
Share on other sites

Confirmed - Focal current on OPi0 is broken

 

Also confirmed that Buster current is booting normally

Bionic is working normal as well.

 

Last login: Sat May 30 22:50:08 UTC 2020 on ttyS0
  ___  ____  _   _____
 / _ \|  _ \(_) |__  /___ _ __ ___
| | | | |_) | |   / // _ \ '__/ _ \
| |_| |  __/| |  / /|  __/ | | (_) |
 \___/|_|   |_| /____\___|_|  \___/

Welcome to Armbian buster with Linux 5.4.43-sunxi

System load:   0.99 0.39 0.14   Up time:       1 min
Memory usage:  15 % of 492MB    IP:
CPU temp:      34°C
Usage of /:    7% of 15G

 

Last login: Sat May 30 22:51:41 UTC 2020 on ttyS0
  ___  ____  _   _____
 / _ \|  _ \(_) |__  /___ _ __ ___
| | | | |_) | |   / // _ \ '__/ _ \
| |_| |  __/| |  / /|  __/ | | (_) |
 \___/|_|   |_| /____\___|_|  \___/

Welcome to Armbian Bionic with Linux 5.4.43-sunxi

System load:   1.10 0.36 0.13   Up time:       1 min
Memory usage:  12 % of 492MB    IP:
CPU temp:      40°C
Usage of /:    6% of 15G

 

 

 

Let me check if trunk has the same issue....Yep, trunk is affected as well....

Share this post


Link to post
Share on other sites

Oh boy, it is getting worse

OrangePi One Focal current is broken as well. I guess all sunxi devices on Focal are affected.

 

Spoiler

U-Boot SPL 2020.04-armbian (May 30 2020 - 18:08:38 +0200)
DRAM: 512 MiB
Trying to boot from MMC1


U-Boot 2020.04-armbian (May 30 2020 - 18:08:38 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3789 bytes read in 3 ms (1.2 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 3 ms (48.8 KiB/s)
13650328 bytes read in 651 ms (20 MiB/s)
7236248 bytes read in 346 ms (19.9 MiB/s)
Found mainline kernel configuration
29463 bytes read in 6 ms (4.7 MiB/s)
4185 bytes read in 5 ms (817.4 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    13650264 Bytes = 13 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...

Device 0: unknown device
_sun8i_emac_eth_init: Timeout
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-02-81-02-a5-3d-b6
ethernet@1c30000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
*** ERROR: `serverip' not set

 

 

Does not make sense to me since Focal is not involved in the boot process at this time...

Share this post


Link to post
Share on other sites

Some Focal images are broken

 

 

and I have no clue why atm. The other day were fine, yesterday rebuild ... fail. Changed build host, fail. Build manually, failed ... 

 

Share this post


Link to post
Share on other sites
Just now, Werner said:

The only hit I have so far is that I get many qemu unsupported syscall 403 when building Focal...


It is possible that its build host related. I didn't try on Ubuntu 20.04 yet.

Share this post


Link to post
Share on other sites
4 minutes ago, Igor said:


It is possible that its build host related. I didn't try on Ubuntu 20.04 yet.

Me neighter. Also building on 18.04 atm.

 

I'll get a VM running an will try this.

Share this post


Link to post
Share on other sites

Aight, the debug output so far looks way cleaner than on Bionic.... Unfortunatly without success. Same issue when built on Focal...dang it.

 

My next try was switching U-Boot to master but was not successful either...

 

 

So to get this straight: When issuing update initramfs on Focal it does something different than on Bionic.

U-Boot tools (including mkimage) are the same for Bionic with backports and Focal.

initramfs-tools is slightly different on Bionic (0.130ubuntu3.9) than on Focal (0.136ubuntu6)

Share this post


Link to post
Share on other sites
U-Boot 2020.07-rc3-armbian (Jun 01 2020 - 11:41:10 +0000) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi One
DRAM:  512 MiB
MMC:   mmc@1c0f000: 0
Loading Environment from FAT... Unable to use mmc 0:1... In:    serial@1c28000
Out:   serial@1c28000
Err:   serial@1c28000
Net:   phy interface0
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... ERROR: sohci_submit_job: EPIPE
ERROR: sohci_submit_job failed
unable to get device descriptor (error=-1)
failed, error -1
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3789 bytes read in 3 ms (1.2 MiB/s)
## Executing script at 43100000
U-boot loaded from SD
Boot script loaded from mmc
152 bytes read in 2 ms (74.2 KiB/s)
13299155 bytes read in 633 ms (20 MiB/s)
7236248 bytes read in 345 ms (20 MiB/s)
Found mainline kernel configuration
29463 bytes read in 6 ms (4.7 MiB/s)
4185 bytes read in 8 ms (510.7 KiB/s)
Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
## Executing script at 44000000
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    13299091 Bytes = 12.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 43000000
   Booting using the fdt blob at 0x43000000
EHCI failed to shut down host controller.
ERROR: USB HC reset timed out!
device_remove: Device 'usb@1c1a400' failed to remove, but children are gone
ERROR: USB HC TakeOver failed!
device_remove: Device 'usb@1c1b400' failed to remove, but children are gone
   Loading Ramdisk to 49351000, end 49fffd93 ... OK
   Loading Device Tree to 492e1000, end 49350fff ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Armbian 20.08.0-trunk Focal ttyS0

orangepione login: root
Password:
You are required to change your password immediately (administrator enforced)
Changing password for root.
Current password:
New password:
Retype new password:
  ___  ____  _    ___
 / _ \|  _ \(_)  / _ \ _ __   ___
| | | | |_) | | | | | | '_ \ / _ \
| |_| |  __/| | | |_| | | | |  __/
 \___/|_|   |_|  \___/|_| |_|\___|

Welcome to Armbian Focal with Linux 5.4.43-sunxi

No end-user support: built from trunk

System load:   1.71 0.49 0.17   Up time:       0 min
Memory usage:  16 % of 492MB    IP:
CPU temp:      36°C
Usage of /:    7% of 15G

New to Armbian? Check the documentation first: https://docs.armbian.com


Thank you for choosing Armbian! Support: www.armbian.com

Creating a new user account. Press <Ctrl-C> to abort

Please provide a username (eg. your forename): ^C
Disabling user account creation procedure


Armbian 20.08.0-trunk Focal ttyS0

orangepione login:

Nailed it!

 

Basically what I did was plugging the sd card with the broken Focal image with an USB adapter into my OrangePi One Plus running Focal (dev branch but should not matter), chrooted into the sd card and ran update-initramfs -u. Thats it.

 

I guess I can have a beer now after five hours of try n error :P

Share this post


Link to post
Share on other sites
Just now, Igor said:

 

Huh. What is wrong with our method?

 

I wished you would not have asked because I have no freakin clue...

Share this post


Link to post
Share on other sites
2 minutes ago, Werner said:

I wished you would not have asked because I have no freakin clue...

 

Have you recreate image on x86 machine?

Share this post


Link to post
Share on other sites

I just created a VirtualBox VM and built NanoPi Duo and NanoPi M1 fine. Duo working fine, still need to test M1 image.

Share this post


Link to post
Share on other sites

Two things we tried and 2/2 builds were successful. Not sure if this is fix yet, but before I rebuild all focal images, need some tests.

- give more memory for initrd, rebuilding kernel https://github.com/armbian/build/tree/master/config/kernel with changed
+CONFIG_BLK_DEV_RAM_COUNT=16
+CONFIG_BLK_DEV_RAM_SIZE=8192


- creating initrd with
https://github.com/armbian/build/blob/master/lib/debootstrap.sh#L551
QEMU_BINARY="qemu-aarch64-static"

 

 

Share this post


Link to post
Share on other sites

I was able to get the M1 focal image to boot with local build as well. So are you still having issues with automated builds or just this one?

Share this post


Link to post
Share on other sites
9 hours ago, sgjava said:

I was able to get the M1 focal image to boot with local build as well. So are you still having issues with automated builds or just this one?


Yes, it seems like a random problem :wacko: We wasted literally a day on this ... getting nowhere.:(

Share this post


Link to post
Share on other sites

https://github.com/EvilOlaf/build/commit/a2957ca8aa6c89d5af52cfa612aa471f630ed258

 

With this rather ugly workaround and no idea how and why it worked I could build multiple working images (boot confirmed):

  • OrangePi One Focal current  (Bionic build host)
  • OrangePi Zero Focal current  (Bionic build host)
  • OrangePi One Focal current  (Focal build host)

(The build host is just informational, does not make a difference (yet).)

 

If anybody has armhf based boards and got some spare time please use this workaround, build an image for your board with Focal as target OS and let us know if it boots.

 

In short I do the update-initramfs twice, once again after removing all the mounts and force both through the QEMU static emulator binary. Throws tons of "unsupported syscall" errors on Bionic but works.

Share this post


Link to post
Share on other sites

Bullseye should be tested as well since both Focal and Bullseye most likely have nearly identical package versions.

Share this post


Link to post
Share on other sites

@Igor I know you probably tried this, but focal builds were work around mid-May. Can you see any deltas to your build scripts after that?

Share this post


Link to post
Share on other sites
11 hours ago, Werner said:

https://github.com/EvilOlaf/build/commit/a2957ca8aa6c89d5af52cfa612aa471f630ed258

 

If anybody has armhf based boards and got some spare time please use this workaround, build an image for your board with Focal as target OS and let us know if it boots.

 

 

I also experienced this issue on OrangePi boards this week.

 

I just built images (build host Focal) using the @Werner a2957ca8 commit for:

 

OrangePi PC

OrangePi PC+

Olimex Lime 2

 

All booted successfully.  All failed to boot with the images currently on the Armbian download page.

 

Thanks for your work on this.  Let me know if I can help.

Share this post


Link to post
Share on other sites
4 minutes ago, jhcarter said:

 

Thanks for your work on this.  Let me know if I can help.

Thanks!!!

We were not sure if hack actually holds and still not really since nobody can explain (yet) why this seems actually working.

Share this post


Link to post
Share on other sites

OrangePi PC, OrangePi PC+, and Olimex Lime 2 all boot correctly on images built with @Igor fix in trunk-436a5681.

 

Many Thanks.

Share this post


Link to post
Share on other sites

Hello, is this issue fixed now ? I'm using OrangePi One Plus server, and three days ago I did apt -y upgrade. After that, it wont boot -- drops to initramfs ( UUID does not exist ).

I did a peek here, and tried to qemu chroot to sdcard from a Focal running VM, and issued " update-initramfs -u ", but that did not solve my problem -- still wont boot. 
12 hours ago I restored to a month old backup, and it booted fine ofc, but then I tried to upgrade again, as there is no more warning about broken Focal images, but sure enough, dropped to initramfs :(

Is there something else I can try ? :D

  

Share this post


Link to post
Share on other sites

Armbian_20.05.2_Orangepizero_focal_current_5.4.43.img.xz works without any problem. Thank you

 

  ___  ____  _   _____              
 / _ \|  _ \(_) |__  /___ _ __ ___  
| | | | |_) | |   / // _ \ '__/ _ \ 
| |_| |  __/| |  / /|  __/ | | (_) |
 \___/|_|   |_| /____\___|_|  \___/ 
                                    
Welcome to Armbian Focal with Linux 5.4.43-sunxi

System load:   1.03 1.49 0.70  	Up time:       4 min		
Memory usage:  30 % of 239MB  	Zram usage:    19 % of 119Mb  	IP:            192.168.1.129
CPU temp:      56°C           	
Usage of /:    13% of 7.3G   	

[ General system configuration (beta): armbian-config ]

Last login: Fri Jun  5 07:17:01 2020 from 192.168.1.137

 

Share this post


Link to post
Share on other sites

After kernel update to 20.05.3 my cubietruck stopped booting again. 20.05.1 images were broken, 20.05.1 was OK. Does anybody have similar issues?

Share this post


Link to post
Share on other sites
1 hour ago, Stanislav said:

After kernel update to 20.05.3 my cubietruck stopped booting again. 20.05.1 images were broken, 20.05.1 was OK. Does anybody have similar issues?

I assume 20.05.2 was okay?

 

Did you retry with a fresh image on another sd card?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
1 1