Jump to content

Markymark

Members
  • Posts

    14
  • Joined

  • Last visited

  1. OK, that makes it clear. Many thanks the information. Greetings, Mark
  2. OK, I can perfectly understand that the support has to stop at a certain point. But wouldn't it be an idea to keep the packages available anyway. If I have to step back to and older backup (which I have to from time to time) I could do so easily via apt-get up to the last supported status. Or am I missing something? Rgrds, Mark
  3. Yes, this will exclude the repository. Does this mean that the Trusty package is no longer available / will no longer be supported? Thanks.
  4. Yes, but this is not an option due to the amout of tweaks that are applied. I will be happy to stay with Trusty instead. Is there a way to solve the above issue? Rgrds, Mark
  5. Hi, I tried to safe-upgrade (apt-get upgrade) Trusty today but got the following notice: Failed to fetch http://apt.armbian.com/dists/trusty/main/binary-armhf/Packages It would be OK to dist-upgrade to Xenial anyway as described in the Docs ... apt-get install update-manager-core do-release-upgrade -d # further to xenial apt-get dist-upgrade ... but I think it would be a good idea to start from a proper Trusty. Any suggestions. Thanks in advance Mark
  6. @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
  7. 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
  8. Yes, I followed your instructions above (loglevel 7). 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
  9. Jep, correct. 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
  10. 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
  11. After running the update for the third time, the correct kernel was installed. A good guess might be that this was some kind of dependency issue. The boot log still shows that there are modules missing: FATAL: Module bt_gpio not found. FATAL: Module wifi_gpio not found. FATAL: Module bcmdhd not found. I am not going to dig deeper into this at the moment. If anybody has a hint I will be happy to fix this. Greetings Mark
  12. Igor, first, many thanks for your work! I highly apprechiate your effort. I tried to upgrade from 3.4.105 to 3.4.110 on a Cubietruck (boot from NAND, System on SSD) via update script. The script finished with no recognizable error and everything seems to be fine. But after the reboot kernel 3.4.105 is still active. I am willing to learn. Any hint apprchiated. Best regards, Mark
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines