Markymark Posted March 7, 2016 Share Posted March 7, 2016 Hi, after upgrading my Cubietruck it failed to boot from SSD. I suspect this has something to do with the causes discussed here: http://forum.armbian.com/index.php/topic/690-upgrade-error-with-armbian-500-on-cubieboard2-running-from-nand/?hl=boot#entry5649 and / or a proper installation of the 'board support packages'. I got the same failure message as mentioned above: FEHLER: unable to make backup link of `./boot/bin/cubieboard.bin' before installing new version: Operation not permitted Directory /boot from nand1 was mounted during upgrade. I thought the solution would be to boot from SD to SSD an fix the issues. So I changed boot.cmd accordingly (root=/dev/sda1) and recompiled it. After this the boot process stoped at booting the kernel: Found U-Boot script /boot/boot.scr 2046 bytes read in 344 ms (4.9 KiB/s) ## Executing script at 43100000 0 bytes read in 262 ms (0 Bytes/s) 30251 bytes read in 474 ms (61.5 KiB/s) 4826984 bytes read in 541 ms (8.5 MiB/s) Kernel image @ 0x46000000 [ 0x000000 - 0x49a768 ] ## Flattened Device Tree blob at 49000000 Booting using the fdt blob at 0x49000000 Using Device Tree in place at 49000000, end 4900a62a Starting kernel ... Uncompressing Linux... done, booting the kernel. At this point I am completely lost because I don't have any idea what to do next. It seems I am missing an important point. Any help apprechiated. Thanks, Mark Link to comment Share on other sites More sharing options...
Igor Posted March 7, 2016 Share Posted March 7, 2016 You made an upgrade to kernel 4.4 and Jessie on system installed to NAND with root filesystem on SATA / sda1? First step is to provide verbose logs. Change loglevel to 7 in boot.cmd (convert it to boot.scr) and console to "console" where you monitor - either serial (perfect) or HDMI. Link to comment Share on other sites More sharing options...
Markymark Posted March 7, 2016 Author Share Posted March 7, 2016 You made an upgrade to kernel 4.4 and Jessie on system installed to NAND with root filesystem on SATA / sda1? Jep, correct. First step is to provide verbose logs. Change loglevel to 7 in boot.cmd (convert it to boot.scr) and console to "console" where you monitor - either serial (perfect) or HDMI. OK, console is TTY1. U-Boot SPL 2016.01-armbian (Feb 28 2016 - 20:07:42) DRAM: 2048 MiB CPU: 912000000Hz, AXI/AHB/APB: 3/2/2 Trying to boot from MMC U-Boot 2016.01-armbian (Feb 28 2016 - 20:07:42 +0100) Allwinner Technology CPU: Allwinner A20 (SUN7I) I2C: ready DRAM: 2 GiB MMC: SUNXI SD/MMC: 0 *** Warning - bad CRC, using default environment Setting up a 1024x768 vga console (overscan 0x0) In: serial Out: vga Err: vga SCSI: SUNXI SCSI INIT Target spinup took 0 ms. 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 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 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 2046 bytes read in 345 ms (4.9 KiB/s) ## Executing script at 43100000 0 bytes read in 262 ms (0 Bytes/s) 30251 bytes read in 474 ms (61.5 KiB/s) 4826984 bytes read in 541 ms (8.5 MiB/s) Kernel image @ 0x46000000 [ 0x000000 - 0x49a768 ] ## Flattened Device Tree blob at 49000000 Booting using the fdt blob at 0x49000000 Using Device Tree in place at 49000000, end 4900a62a Starting kernel ... Uncompressing Linux... done, booting the kernel. The output ist not very different from the snapshot above (as far as I can see). Right after the last message LED4 flickers a few times. Nothing more. Any hint apprechiated. Still lost ... Rgrds, Mark Link to comment Share on other sites More sharing options...
Igor Posted March 7, 2016 Share Posted March 7, 2016 If you remain booting from SD it should work, since you are having root on /dev/sda1 ... but still we don't see anything. Did you change loglevel to some higher number? Put bootargs into " " just to make sure and recompile boot.scr before booting once again. Link to comment Share on other sites More sharing options...
Markymark Posted March 7, 2016 Author Share Posted March 7, 2016 Did you change loglevel to some higher number? Yes, I followed your instructions above (loglevel 7). Put bootargs into " " just to make sure and recompile boot.scr before booting once again. Jep, did this and double-checked everything. I will take a closer look at the bootargs tomorrow and try to gather a deeper understanding. Can you confirm that TTY1 is the correct setting for serial console? I found a reference to "ttyS0" at some point and even tried that value ... but no changes. Thanks so far. Greetings, Mark Link to comment Share on other sites More sharing options...
Igor Posted March 7, 2016 Share Posted March 7, 2016 Serial is ttyS0,115200 Wrote on mobile phone 1 Link to comment Share on other sites More sharing options...
zador.blood.stained Posted March 7, 2016 Share Posted March 7, 2016 Can you confirm that TTY1 is the correct setting for serial console? I found a reference to "ttyS0" at some point and even tried that value ... but no changes. tty1 is display, serial console on most boards is ttyS0, but you also need to set correct speed (console=ttyS0,11520) for it to work. Directory /boot from nand1 was mounted during upgrade. ... I thought the solution would be to boot from SD to SSD an fix the issues. So I changed boot.cmd accordingly (root=/dev/sda1) and recompiled it. After this the boot process stoped at booting the kernel: So you probably have a mismatch between kernel version on SD and kernel modules on SSD rootfs. Link to comment Share on other sites More sharing options...
Markymark Posted March 8, 2016 Author Share Posted March 8, 2016 Just a short reply - need some time for further investigation: console=ttyS0,115200 works fine (stupid me, this should have been a no-brainer). And yes, according to a quick look at the log the kernels are mixed. Will report later. Mark Link to comment Share on other sites More sharing options...
Markymark Posted March 14, 2016 Author Share Posted March 14, 2016 @Igor, zador ... sorry for my late response. I finally got the logging and mixed kernel issue solved. Nevertheless I struggled to boot from nand - and surrendered at last after trying different approaches. Meanwhile I decided to skip the upgrade process and start with a new Ubuntu installation. This will suit my application much better anyway. Thanks again. Rgrds, Mark 1 Link to comment Share on other sites More sharing options...
Recommended Posts