a16bitsysop
-
Posts
39 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by a16bitsysop
-
-
8 hours ago, xiaobao80 said:
Armbian_20.05.0-trunk_Roc-rk3399-pc_stretch_dev_5.5.19_minimal.img
It's basically working
Is that one you compiled yourself, or downloaded?
-
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:
Quote2019.10-armbian
-
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
-
10 minutes ago, Igor said:
Yes. Docker works on all officially supported Armbian builds since a few years. It can be installed via preinstalled armbian-config -> software -> softy -> "Install Docker"
For this particular build I don't know since it is not an official build. Perhaps it will just work ... or not.
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.
-
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. -
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 stopWhich power supply and cable do you use?
Can you log the output from the serial debug port?
Sent from my moto g(7) power using Tapatalk
-
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.
-
17 hours ago, Panzerknacker said:
Which power supply and cable do you use?
Can you log the output from the serial debug port?
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.
-
It's a mikrotik crs326-24g Poe switch, and a cat5e cable I crimped myself. I am not using USBC to power it.Which power supply and cable do you use?
Can you log the output from the serial debug port?
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
-
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 -
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 speedGood morning gentlemen,
I have just discovered that one of the cores on my RockPi4B is faulty and often causes segfaults and crashes,
I can disable the suspect core by issuing the following command
$ sudo echo 0 | sudo tee /sys/devices/system/cpu/cpu2/online
However, this is fine if the machine has booted, but i want to disable the faulty core as early on in the boot process as possible.
Is it possible to disable the core in the uboot environment, or could someone offer me some advice as to the best time to disable the core?
Thanks,
Leon.
Sent from my moto g(7) power using Tapatalk
-
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.
-
On the u-boot website it says the custodian for Rockchip support is:
For the kernel and OS, but what about u-boot support? This is what matters to me, using this board with its intended purpose: u-boot off SPI with nvme support and I am unable to get this going.
philipp.tomsich {AT} theobroma-systems {DOT} com
Have you tried them?
Sent from my moto g(7) power using Tapatalk
-
4 hours ago, Fred St-Pierre said:
Thanks for the info, but it's not compiling the image that's an issue, it's getting a functional u-boot off the SPI NOR with nvme support... I have most of the parts in place, it just does not boot when flashed to SPI. I built an Armbian build just fine and it works on SD, that's not an issue...
There's a lot of info in this thread about progress, as in I'm able to compile a u-boot version with mainline code, I'm able to patch with the files supplied to add nvme support, but none of those u-boot compiled versions end up working when flashed on SPI. There's conflicting information as to what offsets to flash. For example, the package supplied by loverpi flashed idbloader.img at offset 0x00, which is over 900k as opposed to the compiled one which is 236k. Then the package flashes the u-boot.itb at offset 0x4000. I've seen references of offset 0x40000 and 0x200, but none of those combinations work.
Then there's the latest doc supplied by loverpi, which offers NO help whatsoever, as their codebase is almost identical to mainline, which just doesn't work. They do provide an image which covers the entire SPI's 16MB with initramfs and boots. However, it gives little hindsight about what is required to make a bootable image from mainline, just their fork of the u-boot code.
So again, Libre/loverpi/firefly provides little to no support to get this hardware working with mainline, which is what they keep saying they were aiming to do. This board has INSANE potential if only mainline code could be easily used with ALL their hardware without jumping through hoops. The biggest missing part/irritant right now is nvme support for the mezzanine board and SPI NOR booting. If someone, anyone, is able to figure that part out, then this board will have all that's necessary to serve its intended purpose and we won't ever need support from the board designers/supporters. This is my goal, as they are in no way helpful.
**edit** upon hex viewing roc-rk3399-pc-spinor.img from the package supplied by Loverpi, seems like u-boot.itb is in the image at 0x40000 as recommended earlier in the thread. Where it gets complicated is flashing idbloader.img so it works. The image seems to have a bunch of padding I can't make sense of.
nvme support works now, you need a 5.5 kernel and the mezzanine dtb file. There are two dtb files for the rk3399 now.
-
Was just a suggestion, I used to use 'screen' alot but haven't connected via the serial port in a long time.
minicom is a full blown terminal emulator. I had it set to 1500000bps, 8N1.
I should actually correct myself about the behavior I mentioned, actually sometimes one square and sometimes two squares are printed when I press a key.
Sent from my moto g(7) power using Tapatalk
-
If you want to try lots of different versions and distros docker is great for that, you can spin up a container with your source directory mounted into it and install versions of packages you need. Then when you quit your host computer is unchanged.I have to take back my statement that any recent compiler shout be able to build a working u-boot, spl combo. To be self contained I build u-boot, spl on my roc-pc and flashed the result to the spi flash and it doesn't work! Bummer.
I had to debrick the board with the version I have cross-compiled on my Arch Linux PC. At the moment on the distribution my board is a Manjaro Arm Linux.
I am baffled and have to think how to continue.
Sent from my moto g(7) power using Tapatalk
-
Are you using a terminal emulator to connect to the serial port? Some of them let you change settings on the flyAlso I feel like this is a configuration error on my part because behavior seems consistent.. at the "hit any key to stop autoboot" prompt, if I hit the esc key it prints two squares, if I hit enter or a letter it prints one. This doesn't vary.
Sent from my moto g(7) power using Tapatalk
-
7 hours ago, gogoer said:
Hello.
I need to boot armbian without logs and start my application.
I rebuilt and configured uboot and create splash screen with plymouth, so i have no any logs on screen until os boots.
I use autologin by NODM, but after splash screen login string appears for a second. Can i disable this output?
And the next question: how can i start my gui application without starting desktop?
I think kde and gnome both have a kiosk mode which is to just run one app and not allow the user to quit it etc
-
Yes that worked, with fdisk /dev/nvme0n1 I created a partition which is now /dev/nvme0n1p1Shouldn't you actually be partitioning a /dev/nvme0n1 device as /dev/nvme0 is simply a controller?
https://serverfault.com/questions/892134/why-is-there-both-character-device-and-block-device-for-nvme
https://metebalci.com/blog/a-quick-tour-of-nvm-express-nvme/
Thought it was like sata with sda being the first drive etc.
Thanks
Sent from my moto g(7) power using Tapatalk
-
lspci has:What does lspci and lsblk say?
00:00.0 PCI bridge: Fuzhou Rockchip Electronic Co., Ltd RK3399 PCI Express Root Port
01:00.0 Non-Volatile memory controller: Philson Electronics Corporation E12 NVMe Controller (rev 01)
lsblock has it as:
nvme0n1 259:0 0 931.5G 0 disk /mnt
Sent from my moto g(7) power using Tapatalk
-
I got an NVME one now, and it is recognized! Did a dd speed test and got 370mb/s on the nvme drive and 13.8mb/s on the SD card.You need an NVME not a SATA type.
I created an ext4 filesystem on the already existing single partition it had as if I do:
sudo fdisk /dev/nvme0
I get the error Illegal seek and it exits.
If I try:
sudo parted /dev/nvme0
I get
Error: The device /dev/nvme0 is so small it cannot possibly store a filesystem or partition table. Perhaps you are using the wrong device.
But I can create a filesystem on /dev/nvmen1 mount it and dd a1gb file without errors.
Sent from my moto g(7) power using Tapatalk
-
Thanks, didn't actually realize there was 2 kinds of M2 devices! Think I will put that in an enclosure and look for NVME then.You need an NVME not a SATA type.
Sent from my moto g(7) power using Tapatalk
-
I hope it's because it not powered, it's a western digital "green" M2 SSD. It's supposed to be a low power usage one.Probably not.
The 0.9V regulator will come with 5.6 :-) but missing it causes no failure.
Link training can time out when no NVME device is connected or a connected one is not powered.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dtsi?h=v5.6-rc3
Sent from my moto g(7) power using Tapatalk
-
28 minutes ago, Fred St-Pierre said:
I wrote to the firefly team so they could help in fixing USB-C power upstream and received a response on Feb 12th saying they were all remote working due to Corona virus... But the request to get the proper code base would be forwarded to an engineer. No reply on this yet.
I tried 20.02 with kernel 5.5.6 to see if my m2 ssd would be recognised, it’s powered by POE and the switch is saying it is powering it at 52v. I changed the dtb file to the mezzanine one and now I get (when doing a dmesg | grep pci)
[ 1.527318] vcc3v3_pcie: supplied by dc_12v
[ 2.751978] rockchip-pcie f8000000.pcie: no vpcie12v regulator found
[ 2.752081] rockchip-pcie f8000000.pcie: f8000000.pcie supply vpcie0v9 not found, using dummy regulator
[ 3.305332] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 3.305577] rockchip-pcie: probe of f8000000.pcie failed with error -110
maybe it’s the same cause?
ROC-RK3399-PC (Renegade Elite)
in Libre Renegade
Posted
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?