Jump to content

CryBaby

Members
  • Posts

    110
  • Joined

  • Last visited

Posts posted by CryBaby

  1. I would guess you have fiddled with /etc/fstab or copied your root partition from elsewhere without fiddling with your /etc/fstab. Or maybe /boot/armbianEnv.txt

     

    At any rate, the kernel is looking for a partition with UUID=0b77.... to mount at / but isn't finding it. So you need to either change the UUID it is looking for to the one your root partition has, or change your root partition to have the UUID it is looking for.

  2. You could set up a cron job to reboot it every so often. Log in with PuTTY and type

    sudo crontab -e

    This will open the default crontab in an editor, probably nano. At the end of the file add the line

    0 * * * * systemctl reboot
    

    to reboot every hour on the hour. It needs to have a newline at the end, ie. a blank line at the bottom of the file.

    man 5 crontab

    will tell you more.

  3. I haven't seen modules like those before but I've used the typical 'terminal server' in a metal box. They work, the only caveat I would mention is that they can have old and non-standard web interfaces for configuration. Some of the cheaper ones I've used can only be accessed with Konqueror, not Firefox or other more common browsers. I don't know about VLANs.

  4. The last time I tried using my Cubieboard 2 I wanted to use SPI and had some trouble. This was 2 or 3 years ago. The main reason I gave up though was the 2mm pin spacing. Maybe you found a suitable cable.

     

    I would start by getting a current uboot on to it then watch it boot on the serial port. Inspect the default env, see what env file it is reading, check it is loading the overlays etc.

     

  5. If /boot is not already a separate partition I would think there is not much advantage in making it one. The main problem is machines that need a FAT formatted boot partition, as FAT is so fragile. I don't know if your Tinkerboard is one. If /boot is on an ext4 partition then fscking at boot is going to be adequate protection in most cases.

     

    If you really want to mess with your partitions I think you will have to understand the boot process of your Tinkerboard in some detail. Does boot have to be the first partition? What filesystems are acceptable? What files need to be in it and what should they contain?

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines