coolchip

  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

coolchip's Achievements

  1. A deeper inspection shows, that it has something to do with the file /home/[username]/.config/htop/htoprc. The config parameter "right_meters" is set incorrectly. For my XU4 the proper params are: right_meters=Hostname Tasks LoadAverage Uptime CpuFreq(1) CpuFreq(2) CpuFreq(3) CpuFreq(4) CpuFreq(5) CpuFreq(6) CpuFreq(7) CpuFreq(8) HTOP shows the wrong labels when the params are: right_meters=Hostname Tasks LoadAverage Uptime CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq CpuFreq
  2. Have the same issue with my XU4. I have a workaround for this. Remove all files in /home/[username]/.config/htop and replace it with the files from /root/.config/htop. Then all cores are labeled with "big." and ".LITTLE" as usual. But as soon as you change the configuration (for example toggle "Tree" with F5), everything is broken again.
  3. Try it. I like Arch. They have also images for other boards.
  4. Yes, I use it as headless machine. Linux odroid-u3 4.15.11-1-ARCH #1 SMP Tue Mar 20 00:23:08 UTC 2018 armv7l GNU/Linux
  5. If you like Arch Linux, this could be a thing for you: https://archlinuxarm.org/platforms/armv7/samsung/odroid-u3
  6. Ok... it's alive. Seems that I only had trouble with ipv6. Thank you very much for your efforts and the great explanations. Now I know a bit more about the boot process at ARM Cores.
  7. Thank you, for your reply. Of cause Linux is able to read ext4. But I thought, that the first level bootloader of the H3 can't do that. All other ditributions I know are using a seperate fat partition for the bootloader. Or is the bootloader located in raw format in front of the ext4 partition? This would explain all the free sectors in front of the ext4 partition. Yes, I used Etcher. SD card is fine. At the moment I use the Linux distribution of FriedlyArm which is working fine on the same SD card (with a fat partition). I will try to get the output of the serial console, so we can see what the bootloader is telling us...
  8. If I open the image file for NanoPi NEO, I don't see the FAT32 boot partition. > fdisk -l Armbian_5.38_Nanopineo_Ubuntu_xenial_next_4.14.14.img Medium Armbian_5.38_Nanopineo_Ubuntu_xenial_next_4.14.14.img: 1,4 GiB, 1488977920 Bytes, 2908160 Sektoren Einheiten: sectors von 1 * 512 = 512 Bytes Sektorengröße (logisch/physisch): 512 Bytes / 512 Bytes I/O Größe (minimal/optimal): 512 Bytes / 512 Bytes Typ der Medienbezeichnung: dos Medienkennung: 0xbcf97591 Gerät Boot Start Ende Sektoren Größe Id Typ Armbian_5.38_Nanopineo_Ubuntu_xenial_next_4.14.14.img1 8192 2908159 2899968 1,4G 83 Linux If I flash the image on sd card I can't boot with it.