Jump to content

a16bitsysop

Members
  • Posts

    39
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. I Just did a fresh install from a docker build, and copied onto emmc with armbian-config on my renegade elite. I chose btrfs as the format for the emmc, so it has created a btrfs root partition and ext4 boot partition. I tried to upgrade the kernel using apt but it fails, as the boot partition is full. It seems to have been resized to the exact size of the files when it was copied to emmc. Is this a bug in armbian-config? Is there a way to resize without removing emmc?
  2. Is that one you compiled yourself, or downloaded?
  3. I searched and thought updating uboot might help, searching on my system it says: linux-u-boot-roc-rk3399-pc-dev/now 20.05.0-trunk arm64 [installed,local] Uboot loader 2020.01 but message above says:
  4. Renegade Elite fails to boot with mezzanine and dtb > 5.5.11 I finally got my serial dongle working and got some output while booting. U-Boot TPL 2019.10-armbian (Dec 11 2019 - 19:53:44) Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2019.10-armbian (Dec 11 2019 - 19:53:44 +0000) Trying to boot from MMC1 NOTICE: BL31: v2.2(release):a04808c-dirty NOTICE: BL31: Built : 19:53:30, Dec 11 2019 U-Boot 2019.10-armbian (Dec 11 2019 - 19:53:44 +0000) Model: Firefly ROC-RK3399-PC Board DRAM: 3.9 GiB MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... Card did not respond to voltage select! In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Firefly ROC-RK3399-PC Board rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2949 bytes read in 5 ms (575.2 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 211 bytes read in 4 ms (50.8 KiB/s) 10529111 bytes read in 450 ms (22.3 MiB/s) 20505088 bytes read in 871 ms (22.5 MiB/s) 76102 bytes read in 12 ms (6 MiB/s) 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 04000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 10529047 Bytes = 10 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f5514000, end f5f1e917 ... OK Loading Device Tree to 00000000f5499000, end 00000000f5513fff ... OK Starting kernel ... Loading, please wait... Starting version 245.4-4ubuntu3.1 Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. done. Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=b68dafc4-9fb4-477a-bc71-d03817baf081 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 49.287360] reboot: Restarting system UUID=b68dafc4-9fb4-477a-bc71-d03817baf081 is the ext4 / partition on the microSD card
  5. It does work, I have had it running since 20.04 was released with no difference from the official docker build I was using in 18.04. The main reason for me using the official version before was the one in the Ubuntu repo was too old before.
  6. I think docker-ce is only if you have the docker repos added, which may not have 20.04 versions yet. docker-ce-cli is the one from the Ubuntu repos which is version 19.03 which I think is the latest version anyway.
  7. Still waiting for my usb ttl serial dongle, tried 5.6.11 and it successfully booted with the 5.6.11 dtb. Upgraded to 5.6.12 and now after it is powered on a get a 2 blink pulse from the mezzanine green led for approx 20 secs then no LEDs and network is down still. Like previous unsuccessful versions the ethernet interface only comes up once, no change when LEDs stop Sent from my moto g(7) power using Tapatalk
  8. I have installed syslog-ng which removes rsyslog, now I am trying to filter using journald as docker is set to log to journald. If I create docker.conf in /etc/syslog-ng/conf.d with: filter f_dockerd {"${.journald._COMM}" eq "dockerd"}; destination d_docker { file("/var/log/docker.log"); }; log { source(s_src); filter(f_dockerd); destination(d_docker); }; Everything is logged go to docker.log, not just docker logs. The journal source is already setup with system() I think as if I try to add a journald source I get the error there can only be one.
  9. I tried with my usb ttl serial lead and just got question marks with terminal on macOS with 1500000 and 115200, I don't think my lead supports 1.5mbs so have ordered another one.
  10. It's a mikrotik crs326-24g Poe switch, and a cat5e cable I crimped myself. I am not using USBC to power it. Probably going to be very tricky to access the serial pins with the mezzanine on, I will have a look later and see if they can be accessed. Sent from my moto g(7) power using Tapatalk
  11. I have a POE mezzanine and the last dtb that works with is 5.5.11 I think, someone else posted this issue before. Just tried 5.6.10 and it doesn't boot, on my poe switch a normal boot is Ethernet interface up, then down, then up again and that's when networking comes up. The current draw is also around 80mA when running. With a newer dtb it shows interface up, it never goes down and networking doesn't come up. The current draw stays around 40mA after initially going up and down a bit. If I turn it off and remove the SD card and remove the dtb link in /boot and point it back to 5.5.11 as other post suggested it boots the newer kernel, and nvme is working on mezzanine. Sent from my moto g(7) power using Tapatalk
  12. Have you tried reducing the max speed with cpufrequtils, I think you can do it inside armbian config as well. Might be more stable at a lower speed Sent from my moto g(7) power using Tapatalk
  13. Here is some instructions for a raspberry pi https://www.raspberrypi.org/forums/viewtopic.php?t=132674 It has a local and remote network tho, not just a bridge.
  14. On the u-boot website it says the custodian for Rockchip support is: philipp.tomsich {AT} theobroma-systems {DOT} com Have you tried them? Sent from my moto g(7) power using Tapatalk
  15. nvme support works now, you need a 5.5 kernel and the mezzanine dtb file. There are two dtb files for the rk3399 now.
×
×
  • Create New...