MrRady Posted January 3, 2018 Share Posted January 3, 2018 Hello, Upgrading uboot 5.25 to 5.35 on Armbian_5.25_Lime2_Ubuntu_xenial_default_3.4.113 fail to boot at next reboot. It's a lime2 Nand with SD card system, last rev hardware I don't find any solutions for the moment, because serial output doesn't output very much ... here is the 5.35 boot U-Boot SPL 2017.09-armbian (Nov 22 2017 - 15:21:35) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.09-armbian (Nov 22 2017 - 15:21:35 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 6944 bytes read in 154 ms (43.9 KiB/s) ### ERROR ### Please RESET the board ### on the original image the boot is fine : U-Boot SPL 2017.01-armbian (Feb 02 2017 - 02:40:37) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.01-armbian (Feb 02 2017 - 02:40:37 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2 I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 Hit any key to stop autoboot: 0 6944 bytes read in 159 ms (42 KiB/s) switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2652 bytes read in 179 ms (13.7 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 114 bytes read in 124 ms (0 Bytes/s) 5072050 bytes read in 535 ms (9 MiB/s) 5607392 bytes read in 582 ms (9.2 MiB/s) ** File not found /boot/.next ** ** File not found .next ** 53488 bytes read in 370 ms (140.6 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5071986 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK Starting kernel ... So i have just downloaded le last prebuilt legacy image with 5.35 already in it and it boot. I will continue devlopment on this image and maybe make a userbuilt image later. Hope it help, here is the boot log of this one : U-Boot SPL 2017.09-armbian (Nov 22 2017 - 15:21:35) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.09-armbian (Nov 22 2017 - 15:21:35 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 230454 bytes read in 193 ms (1.1 MiB/s) Error: 24 bits/pixel bitmap incompatible with current video mode starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 2 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 3708 bytes read in 198 ms (17.6 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 192 bytes read in 150 ms (1000 Bytes/s) 5073641 bytes read in 545 ms (8.9 MiB/s) 5594808 bytes read in 591 ms (9 MiB/s) Found legacy kernel configuration 53488 bytes read in 372 ms (139.6 KiB/s) ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 5073577 Bytes = 4.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK EHCI failed to shut down host controller. Loading Ramdisk to 49b29000, end 49fffaa9 ... OK Starting kernel ... Link to comment Share on other sites More sharing options...
Igor Posted January 3, 2018 Share Posted January 3, 2018 1 hour ago, MrRady said: I will continue devlopment on this image and maybe make a userbuilt image later. It should be fixed upstream - working for me, but it would be good if somebody else also checks. Related: https://github.com/armbian/build/issues/770 Link to comment Share on other sites More sharing options...
kukulo Posted January 14, 2018 Share Posted January 14, 2018 With u-boot 5.35 the lime2 is failing to start in headless mode, moreover when downgraded to u-boot 5.31, the device powers off instead of rebooting. I tried downgrade to 5.23 u-boot from my archive, but the reboot issue still persists. Now I am using the 4.13.16 kernel and before I was using 4.11.6 where the reboot worked. Both these issues were addressed previously in other posts. Is there any work in progress on this issue? Before I am rolling back to my previous backup I would like to know whether it makes sense to wait a bit for fixed packages or not. Link to comment Share on other sites More sharing options...
ZupoLlask Posted January 15, 2018 Share Posted January 15, 2018 @Igor Can you share NEXT linux-headers and linux-image for A20 Lime1, so I can also test that fix? I couldn't find it @ http://beta.armbian.com/pool/main/l/linux-upstream/ Link to comment Share on other sites More sharing options...
Igor Posted January 15, 2018 Share Posted January 15, 2018 Problems were not with NEXT (4.14.y) branch but default 3.4.113 Lime1 U-boot: https://beta.armbian.com/pool/main/l/linux-u-boot-lime-default/linux-u-boot-lime_5.37.180112_armhf.deb Kernel and headers:https://beta.armbian.com/pool/main/l/linux-upstream/linux-image-sun7i_5.37.180112_armhf.deb https://beta.armbian.com/pool/main/l/linux-upstream/linux-headers-sun7i_5.37.180112_armhf.deb Link to comment Share on other sites More sharing options...
ZupoLlask Posted January 15, 2018 Share Posted January 15, 2018 @Igor Don't get me wrong, but are you sure it's not otherwise? After updating my A20-Lime from Armbian 5.25 (mainline) to latest stable version (5.35) through `apt upgrade`, I got precisely the same error as the OP with kernel 4.13.16. If I'm reading well, the problem described in the OP is precisely with mainline kernel @ version 5.35, stating the legacy kernel @ version 5.35 works just fine. Checking your patch @ git, are sure you shouldn't apply that patch also to A20-Lime? You seem to have forgotten that board... Link to comment Share on other sites More sharing options...
Igor Posted January 15, 2018 Share Posted January 15, 2018 5 minutes ago, ZupoLlask said: Don't get me wrong, but are you sure it's not otherwise? No, problems were actually on both kernels, but manifestation was different. Stable branch does not contain a fix yet, while beta should. I tested on my Lime2 and it is booting fine. You need to change u-boot: Lime2https://beta.armbian.com/pool/main/l/linux-u-boot-lime2-next/ or Lime1 https://beta.armbian.com/pool/main/l/linux-u-boot-lime-next/ Link to comment Share on other sites More sharing options...
kukulo Posted January 15, 2018 Share Posted January 15, 2018 I tried the linux-u-boot-next-lime2_5.37.180112_armhf.deb in combination with 4.14.8-sunxi kernel and it is refusing to boot without HDMI attached. 1 Link to comment Share on other sites More sharing options...
Igor Posted January 15, 2018 Share Posted January 15, 2018 Well, I thought this problem was fixed since it was working for me ... Reopening: https://github.com/armbian/build/issues/770 Link to comment Share on other sites More sharing options...
kukulo Posted January 15, 2018 Share Posted January 15, 2018 Strange, now I downgraded u-boot to 5.23 and kernel to 4.11.6 which was rebooting previously and now it is not rebooting. The new u-boot must have updated on the device something.... Link to comment Share on other sites More sharing options...
Igor Posted January 16, 2018 Share Posted January 16, 2018 @kukulo @ZupoLlask @MrRady try those: Lime 2 and this image: https://dl.armbian.com/lime2/nightly/Armbian_5.37.180117_Lime2_Debian_stretch_next_4.14.13.7z boots this way: http://ix.io/EcP Lime 1 and this image: https://dl.armbian.com/lime/nightly/Armbian_5.37.180117_Lime_Ubuntu_xenial_next_4.14.13.7z boots this way: http://ix.io/EcQ HDMI connected or not it boots perfectly fine. Link to comment Share on other sites More sharing options...
MrRady Posted January 16, 2018 Author Share Posted January 16, 2018 Hi, Yes i have encoutered some problem with 5.35 prebuilt image (stop at a dcdc voltage on UART output), so i have finally made a userbuilt image with the last 5.37 and legacy kernel. It's boots fine , thanks My cards have all batteries connected and good power supplys, not HDMI, but parallels RGB screens. Link to comment Share on other sites More sharing options...
kukulo Posted January 17, 2018 Share Posted January 17, 2018 I have tested the linux-u-boot-next-lime2_5.37.180117_armhf.deb package and this u-boot fails to boot without HDMI attached, moreover when attached and performing reboot, the system powers-off. The 5.31 u-boot allows to startup in headless mode, but the reboot - poweroff issue persists. Link to comment Share on other sites More sharing options...
Igor Posted January 21, 2018 Share Posted January 21, 2018 On 17. 1. 2018 at 5:42 PM, kukulo said: I have tested the linux-u-boot-next-lime2_5.37.180117_armhf.deb package and this u-boot fails to boot without HDMI attached, moreover when attached and performing reboot, the system powers-off. The 5.31 u-boot allows to startup in headless mode, but the reboot - poweroff issue persists. I made some research and patch this problem. apt-update & upgrade works. Tested default and next. It seems its related to u-boot fallback video mode when nothing is detected with EDID - there is none now? @jernej This is when booting a mailine kernel, while legacy stops with an error: Spoiler U-Boot SPL 2017.11-armbian (Jan 21 2018 - 13:49:02) DRAM: 1024 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 21 2018 - 13:49:02 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) Model: Olimex A20-OLinuXino-LIME2-eMMC I2C: ready DRAM: 1 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 Card did not respond to voltage select! mmc_init: -95, time 23 *** Warning - MMC init failed, using default environment In: serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) SCSI: SATA link 0 timeout. AHCI 0001.0100 32 slots 1 ports 3 Gbps 0x1 impl SATA mode flags: ncq stag pm led clo only pmp pio slum part ccc apst Net: eth0: ethernet@01c50000 Warning: usb_ether using MAC address from ROM , eth1: usb_ether 230454 bytes read in 149 ms (1.5 MiB/s) Error: 24 bits/pixel bitmap incompatible with current video mode Link to comment Share on other sites More sharing options...
jernej Posted January 21, 2018 Share Posted January 21, 2018 5 hours ago, Igor said: It seems its related to u-boot fallback video mode when nothing is detected with EDID - there is none now? Video drivers didn't change much in last few months. There is only one commit which seems relevant to this issue is this. However, it should be present only in 2018.01. You are using 2017.11, right? Can you do a bisect? It's possible that some change here is responsible too, but nothing stands out. Unfortunately, I don't have this HW, so I can't help further. Link to comment Share on other sites More sharing options...
Recommended Posts