Jump to content


  • Posts

  • Joined

  • Last visited

Other groups


Recent Profile Visitors

7293 profile views
  1. @tommyboy You did not specify if armbian stops working or the multitool. I guess you're talking about the multitool, since you posted the dmesg of that one. Try to substitute rk322x-box.dtb in the multitool partition with this one: rk322x-box.dtb and try again
  2. v2022.07 should work fine either too; the ddrbin was clearly the issue there. It can indeed; the spdif nodes are surely different because the original android rom surely uses kernel 4.4 and in the meantime the syntax on how to declare the sound nodes changed. There may be some different gpios involved though, and the original dtb may help detecting them.
  3. @Dario Murgia It looks like the ddrbin @666Mhz is not working on your board. I was suspecting such bad behaviour from long time because in the past some other people with X88 lamented booting problems but no serial logs were provided, now there are some evidences that frequency is not universally compatible. That's a shame because 333Mhz for the DDR is limiting performances a lot, but I guess I will revert that change and use the ddrbin @333Mhz for the time being; I suggest you to take the previous binary from that commit and use that one to build your images.
  4. @Dario Murgiahello, very glad you had no issues installing the image. About the SPDIF issue, actually I don't remember having really tested it on rk3318, I will check as soon as I can. Perhaps the alsa mixer worth a check, maybe the volume is low or there is some other setting (mute?) preventing the audio from spdif.
  5. 4gb of ram and quad-core cpu are not a guarantee of good performance. The rk3328 armbian branch lacks some DRM kernel optimizations that rk3228 has, and in fact the desktop performance is a bit better on rk3228. You could try KDE Plasma or gnome: despite being fully-featured desktop environments, they work much better than xfce or lxde. Ah, on xfce you should also disable composition from Settings -> Windows Manager Tweaks to improve performance.
  6. Yes, but you have to install armbian on the eMMC because the stock bootloader does not allow USB boot (armbian bootloader does).
  7. Hello, the problem is generally a bad quality software product (the driver) of the chinese wifi chip on the Opi4 LTS
  8. @Eli Ribble Thanks for testing. The missing ethernet is quite strange on that board. I have a sample of that board and it works fine on mine; maybe they are two different revision, but don't know. About the HDMI problem, the 5.19.15 image you probably found here in the forum is an experimental image that uses the libreelec patches: when you upgraded the kernel, you got installed the standard armbian kernel without the libreelec patches and so the issue came back. For now, the discussion to implement those patches is stuck, so don't expect seeing them as in armbian kernels soon. Sorry, but that's not my choice 😕 (see here for reference
  9. I'm not sure I understood what you mean with "normal armbian archive" and "experimental stable" terms What I really would like is one and only one place for public images to be produced and deployed; at the moment this place is the github community repository and it is perfectly fine to have one single place with the images, just missing the stable kernel images for the reason I said above (ie: edge kernel is not guaranteed to always work). The other images you find here and there, especially on users.armbian.com/jock URL, are old or experimental images, but surely unmaintained and prone to be erased sooner or later. For all the other needs, there is always the option to build a custom image, it will receive regular updates via apt just as well as public images do.
  10. Never had particular problems with USB on rk322x/rk3288, but on rockchip 64 bit (in particular rk3328) the USB3 implementation has some issue that makes it quite a bit troublesome. I never investigated very througly in it though.
  11. @MattWestB @SteeMan I've been thinking about that too and I would have liked to ask @Igor in the last release meeting but I did not want to be off-topic. Perhaps the community images are "too edgy", and perhaps it is more savvy to produce images with current kernel, then upgrade to edge via apt install, than starting with edge kernel, that is not guaranteed to work correctly, and then downgrade to current. I just had a very brief test after burning an image with kernel 6.1 and, against all my thoughts because I was sure I already checked kernel 6.1, it does not boot on my rk3318 box, while kernel 6.0 had no troubles in booting (broadcom bluetooth was broken although). Did not have the time and tools at hand to dig into the issue (moving into a new house...), but I hope to check better very soon, perhaps during the weekend. About moving rockchip64 to 6.1 for the next release, I'm a bit reluctant and maybe a bit more testing is required. 32 bit rockchips although seems rather acquainted with 6.1, no issue and no troubles so far (my HA testing rig on rk322x has an uptime of 10 days and doing a variety of jobs that is pretty amazing for the piece of junk it was )
  12. @Serkan Polat no static public address, hundreds of device behind NAT, ... sounds like you should work on network level rather than trying to get access to the devices using some trick that firewalls may intercept. For example, I would consider to let your devices establish a VPN targeting an external public server that acts as a gateway. If your firewall allows free outbound traffic you should have no issues with wireguard/openvpn solution.
  13. Hello, good you finally had the board running happily armbian. It would be nice if you could detail a bit over the non-working images: kernel version, where you did pick them, do you get something on the serial port if you have any, do the led is blinking while you try to boot or it is steady... You should be able to burn a testing image and a sdcard, plug it in and the system should boot from sdcard instead of internal eMMC.
  14. You can read exactly two posts above yours.
  15. @kfj Hello, I imagine you are powering off and on the board when you experience such issue, aren't you? The brand name of the tvbox says nothing about the board itself, so it is not helpful for other digging. Although sometimes it happens on a board of mine that on reboot the board does not boot from sdcard and then requires another power cycle to boot again. Anyway you may want to install armbian on internal eMMC, since it looks it works ok on your board.
  • Create New...