• Posts

  • Joined

  • Last visited

Reputation Activity

  1. Like
    EtlARM got a reaction from CubieTourist in CubieTruck: File not found /boot/boot.bmp   
    Is this problem back again?
    I also experienced problems with the 5.24 (or was it 5.23?) upgrade made during Christmas. It also bricked the system on NAND, but I don't remember what went wrong. I reinstalled from scratch because no supporting tools where available far away from home.
    With the right tools to hand it should be possible to recreate the boot files on NAND with the help of the linked thread.
    As I have to do the 5.25 upgrade in the next days, I would appreciate when this problem gets sorted out sooner than later...
  2. Like
    EtlARM got a reaction from Jens Bauer in Upgrade Error with Armbian 5.00 on Cubieboard2 running from NAND   
    "Good" to hear other have the same problem... after the workaround went fine on my CubieBoard2 I bricked my production system CubieTruck the same way, you described. The workaround trick went fine on the CubieTruck. But after reboot the system does not start anymore:
     red power LED near power jack is lit  network LEDs show some activity  SATA disk stays off  front LEDs stay off  VGA has no signal  no other reaction observable  
    I had similar NAND boot problems in the past, so I assumed it is the same case again. The last time it was sufficient to leave the board unpowered for some hours (discharging battery a bit), but this time nothing helped. So I migrated my complete system back to SDCARD, and it is working like before.
    After thinking a night about the problem, it might be sufficient to manually update all kernel files on NAND1. I did not test that.
    Do you have a serial cable to watch the boot output? (I don't have one.)
  3. Like
    EtlARM got a reaction from Jens Bauer in Upgrade Error with Armbian 5.00 on Cubieboard2 running from NAND   
    When doing apt-upgrade to get the latest linux-jessie-root-cubieboard2, it fails with this error message:
    # apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded:   linux-jessie-root-cubieboard2 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/1.810 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 51863 files and directories currently installed.) Preparing to unpack .../linux-jessie-root-cubieboard2_5.00_armhf.deb ... Unpacking linux-jessie-root-cubieboard2 (5.00) over (4.81) ... dpkg: error processing archive /var/cache/apt/archives/linux-jessie-root-cubieboard2_5.00_armhf.deb (--unpack):  unable to make backup link of `./boot/bin/cubieboard.bin' before installing new version: Operation not permitted dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for systemd (215-17+deb8u3) ... Errors were encountered while processing:  /var/cache/apt/archives/linux-jessie-root-cubieboard2_5.00_armhf.deb E: Sub-process /usr/bin/dpkg returned an error code (1)
    When /boot is on NAND it is not possible to link files there, maybe that is the problem?
  4. Like
    EtlARM reacted to Igor in Upgrade Error with Armbian 5.00 on Cubieboard2 running from NAND   
    Workaround: manually remove 
    dpkg -r linux-jessie-root-cubieboard2
    and install
    apt-get install linux-jessie-root-cubieboard2
  5. Like
    EtlARM got a reaction from Igor in Boot Order Change? or Nand Boot with SD card inserted.   
    I can prove, that your intended setup is working on my CubieTruck and also on the CubieBoard2:
    I'm booting Armbian from NAND and a SDCARD, a HDD and USB drives can be mounted as expected.