znoxx

Members
  • Content Count

    95
  • Joined

  • Last visited

About znoxx

  • Rank
    Advanced Member

Recent Profile Visitors

1457 profile views
  1. Hi there. Is there any way to set hostname of freshly installed board with armbian-config not in menu, but from command line ? armbian-config --help gives some examples, but not for this case. And more generic question -- when I "burn" microSD image, first boot comes with questions about root password, new user, etc. Is there a way to do it in unattended mode ? E.g. with ansible. Thanks a lot in advance!
  2. @piter75, many thanks for your explanation. Indeed my "permanent duplicated" mac successfully found in "system connections" folder of original system in "Wired connection 1" file. But my 2 GB "retired" board stayed in drawer for a while and I made a new image with freshly downloaded Armbian - let's say "new sd card". Why in this case MAC was the same ? Unfortunately, I cannot tell you the signs on board -- they covered with heatsink, which I'd prefer not to re-glue back. 2GB board was bought in June-july 2019 4GB board was bought in Feb 2020, but arrived
  3. Hi! Thanks for your reply. This is one from 4GB model, which acts now as server: $xxd /sys/bus/nvmem/devices/rockchip-efuse0/nvmem 00000000: 524b 3382 00fe 2155 524b 5030 3930 3036 RK3...!URKP09006 00000010: 0000 0000 1710 150a 0208 0800 0000 0000 ................ And this one comes from my "old" 2G board, which i want to re-purpose: $ xxd /sys/bus/nvmem/devices/rockchip-efuse0/nvmem 00000000: 524b 3382 00fe 2155 524b 5030 3930 3231 RK3...!URKP09021 00000010: 0000 0000 0f11 2908 0207 0800 0000 0000 ......)......... By the way, "cloned mac address" worked.
  4. Hi! I've 2 rock64 boards -- 4gb and 2gb bought with 1 year difference The problem -- both boards have same MAC address. Changing it with macchanger has no effect, same for cloned mac in nmtui. Also I tried this in armbianEnv.txt: root@rock64:~# cat /boot/armbianEnv.txt verbosity=1 overlay_prefix=rockchip rootdev=UUID=48ad169b-7620-4c84-89fa-6c9a0fcde766 rootfstype=ext4 ethaddr=a7:71:b0:90:17:1f usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u But mac stays the same. I've plugged usb ethernet just to avoid conflict on same network, b
  5. Not sure the same issue here -- but: 1) Burn latest focal image from website with 5.xx -- system boots. Do apt-get update && apt-get upgrade -- never appears on network (kernel is not upgraded, as I see, but network manager does) 2) Burn buster image with legacy kernel, apt-get update && apt-get upgrade -- working. Anybody bumped same ?
  6. Hi All! Is it possible to enable 1.8 Ghz on kernels 5.4.x (stable one) and 5.5-rc2 ? Thanks in advance!
  7. Thanks Igor! Every winter yet another new orange pi becomes usable. Good tradition, so far . Just curious - only one board from several behaves so. Is it different hardware revision? A bug in hardware?
  8. Hi all! First of all thanks to bringing my Opi One Plus back to life. I was stuck to 4.20.x kernel, since all other crashed this board (strange, I have several opi1+, but only one of them did not survived upgrade and I had to rollback). Now it looks pretty stable: zno@nodex:~$ uname -a Linux nodex 5.4.1-sunxi64 #19.11.3.336 SMP Mon Dec 2 02:54:15 CET 2019 aarch64 GNU/Linux But well... This looks strange: zno@nodex:~$ sudo cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kern
  9. Well, my "demand" is quite exotic. Not so many people use wifi dongle inside LXC container. Not sure one should invest his own time into _such_ investigation. Regarding the speed - container runs "TorBox" (http://tbng.ml), and TOR does not give you super-fast connection. But well, indeed it's time for upgrade to something more 2019 related.
  10. Igor, thanks for confirmation. Looks like pure driver issue. I put good old ralink 5370. Works like charm and my macos started to connect to AP, instead of password loop on Realtek 8188EU. One small thing, not indeed rockchip related - diode on ralink usb wifi does not blink =). Bad thing - my heap of unused Realtek 8188eu adapters just got bigger.
  11. Hi all. Need help. Updated today from 4.4.180 -> 4.4.182 Now getting permanent problem with bypassing network interface to LXC container (worked flawlessly on 4.4.180). sudo lxc-device -n tbng add wlx0092d00ddb46 command failed: Operation not supported (-95) lxc-device: tbng: tools/lxc_device.c: main: 172 Failed to add wlx0092d00ddb46 to tbng Same for trying to pass phy0 to network namespace zno@armbox:~/_working_kernel$ sudo iw phy phy0 set netns 7094 command failed: Operation not supported (-95) I will definately try with another no
  12. Yet another answer to myself. According to this (valued opinion of @tkaiser) - USB3@ARM SBC + USB3 Hub is totally bad idea: https://forum.openmediavault.org/index.php/Thread/24145-OMV-rock64-problem-with-USB-Hub/ Still yet another problem with USB2. Both ports works ok with directly connected devices. Attaching usb2 hub to lower USB - still ok. To upper USB - gives a lot of errors in dmesg with periodic device reset. Actually attaching usb voltmeter to hub showed BIG undervoltage (4.4v). Powering USB hub partially resolves situation, but still errors i
  13. Update... It was guilty USB3 hub. I'm willing to have more than one USB3 port on rock64, but look... Hub works fine on standart PC, but adding it to Rock64 gives this weird effect. Can anyone confirm, that USB3 HUB is not recommended to use for connecting boot USB3 SSD ? It's not a question of power - I'm using good PSU. And drive is SSD (consumes not too much). Thanks in advance.
  14. Hi all! I'm having strange issue with Rock64. I downloaded latest Armbian 5.88 with 4.4.180 kernel. Installation and boot are ok, but when I try to do apt-get install lvm2 Package installs, configures and... update-initramfs: Generating /boot/initrd.img-4.4.180-rockchip64 update-initramfs: Converting to u-boot format Then I do root@rock64:~# sudo reboot And I'm getting a boot loop... Same effect, if I move system to SSD. At first I thought it was issue with ssd transferred system... But it clearly reproduced on fresh