Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. I would put boot and system on the eMMC. Then it will run with or without the SSD, which I would reserve for data. Things like VMs and containers that get a lot of writes can go on the SSD and be symbolically linked to their system folders.
  3. @AHMEDLORI try these the transpeed or x98h image. https://github.com/NickAlilovic/build/releases/tag/20250306
  4. @Luckyisnotcoolest try the x96q images here. https://github.com/NickAlilovic/build/releases/tag/20250306
  5. @emor acid could be your gpio settings for mmc0. Try the x98h image. If that doesn’t work you need to extract your android dts or use the one from the working Ubuntu.
  6. Today
  7. Just wonder if there is a good guide how to make dri work and allt the supported code´s work in wayland / xorg or other / Thanks
  8. Hi Keith, I'm not too familiar with the in and outs of armbian-config. Just navigate around and see what's available. The kernel being Edge makes it easiest to install to a different device (i.e. if that's eMMC), so you're goo there. And remember, if you break the operating system, you can always start again with a clean install. So don't be afraid to experiment. It's how we learn. But I am very careful with the 16 MB SPI-NOR, and not to mess with that. I'm not sure if overwriting that with junk would brick the machine or not. Perhaps someone else who knows more about that can comment. But otherwise just follow your instincts as best you can and do what makes sense to you. Armbian-config is meant to be pretty straight-forward.
  9. The kernel 6.17 release benefits from improvements in the graphics subsystem, hardware enablement, and more! See where Collabora's kernel team contributed to this release. View the full article
  10. So I now got Edge 6.16.4 Kernel on my SD card, and I want to boot from either EMMC or SATA to take advantage of the extra speed. Arbian-config presents several options. Which option is generally recommended, from the 5 shown in Armbian-config?. For me, Option 3 (boot from EMMC, System on SATA, USB or NVMe) seems to be what I want, but I am interested to hear any recommendations or problems, since this is and Edge Kernel. Tanks, Keith
  11. leave a link for other users like @John Taylor to continue your work, also @fedes_gl could give a hand
  12. I already said i cant and dont want to. Anyway, in the meantime, I tried to port to latest version of armbian and didn't managed to finish because of some issues with devicetree. I gave up because no time for the moment (and found nomore fun in debugging for something i dont need) Final goal was to port haos to it anyway. Armbian was only a step for me.
  13. I know an expert in rk3528, his name is @fensoft we are depending on him finding a weekend to dedicate to the community https://github.com/ilyakurdyukov/rk3528-tvbox he will help us by taking this repository and including it in armbian with a wonderful pull request I would like to buy this board and join the fun that you have, but my country has literally started an embargo on all TV boxes
  14. Thanks for that , TallMan. You told me I needed 6.16.4 - and it took me a while to realise that I could probably find it using the Armbian-config. I thought I did pretty much as you describe, but it wouldn't boot, so I guess I did something wrong, (Probably picked up the faulty card mentioned above!). but didn't have time yesterday to try again - so thats for this evening. I'll get there eventually, I hope. At the moment I guess I'm still scared I'm going to do something irrepairable, because up til now I've always been a user, so not too adventurous yet. Keith
  15. @fensoft please make this https://github.com/ilyakurdyukov/rk3528-tvbox as a pull request, you have the dq08 tvbox board, you're embedded in the community, you've tested everything, you seem like the perfect guy
  16. Hi, I tested with the version 25.11.0-trunk.129 and the second network port worked with this. https://paste.armbian.com/hasewoloti
  17. Don't know what to tell you, it is running fine on my boxes and dmesg is clean. Also I cannot see what is your build version since the screenshot is missing the top line of the screen. 🤷‍♂️
  18. This is internal development for our boards, unfortunately, there is no public repository for our kernel. The code is borrowed from reverse-engineered POCs h264 + * Based on https://github.com/jemk/cedrus + * Copyright (c) 2014-2015 Jens Kuske <jenskuske@gmail.com> jpeg + * Based on https://gitorious.org/recedro/jepoc + * Copyright (c) 2014 Manuel Braga <mul.braga@gmail.com>
  19. Please tell me the source of this patch.
  20. Btw, about things turning orange... I had that experience some time ago before I got into Armbian. I did a clean install of Debian Bookworm. Then I tried installing the vendor GPU drivers and packages from the Orange PI company. Their drivers and packages were so horribly hacked / designed that various programs that needed certain SoC features needed to be custom modified to work with those specific vendor drivers. So all versions of those programs needed be held and were non-upgradable if I wanted continued GPU and video acceleration support. Anyway the main GPU driver package, when I installed it myself (instead of whatever secret sorcery their installation did), it turned things orange. Fortunately now, pure Trixie works out of the box on my board (from the Debian installer .iso), except that the kernel needs to be upgraded from their 6.12 to 6.16.3 from trixie-backports. Armbian's edge kernel on an otherwise pure Trixie is even better than Debian's, because it's customized for Rockchip. If you've been doing things like I was trying to before, things have much improved and now simple is better and it works. Also things tend to get really mangled up when upgrading over time - especially major LTS upgrades. Why not try a fresh install of a 25.8.1 Armbian image?
  21. Fix: run armbian-install, then selected “Install/Update the bootloader on SD card (/dev/mmcblk0)”
  22. I have a different board (Orange PI 5 Plus). My experience with the edge is that it works great in Wayland and terribly in X. Also KDE Plasma Wayland is different than Gnome Wayland (and Plasma is buggy in Trixie). So you could try all three combinations and see if one works better than the others. You tried both the stable edge and the rolling edge ...with the same results?
  23. And it did not work out, no sound in the edge 6.16 kernel. I did find : https://lkml.org/lkml/diff/2025/8/7/872/1 to enable HDMI-audio, which is most likely the reason. However the edge also has some graphics distortion (orange glow), so I'm not gaining a lot by applying that patch. Ill let everyone know
  24. U-Boot 2024.01-armbian-2024.01-S866c-Pbc32-Ha9af-V80bb-Bda0a-R448a (Nov 25 2024 - 14:01:12 -0500) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: Transpeed 8K618-T DRAM: 4 GiB Core: 61 devices, 22 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4022000: 1 Loading Environment from FAT... MMC: no card present ** Bad device specification mmc 0 ** In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Net: apply fix for AC300 ephy bb version bug ... using AC300 emac1 ephy default config ... eth0: ethernet@5030000 starting USB... Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 Bus usb@5101400: USB OHCI 1.0 Bus usb@5200000: USB EHCI 1.00 Bus usb@5200400: USB OHCI 1.0 scanning bus usb@5101000 for devices... 1 USB Device(s) found scanning bus usb@5101400 for devices... 1 USB Device(s) found scanning bus usb@5200000 for devices... 1 USB Device(s) found scanning bus usb@5200400 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop MMC: no card present switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... MMC: no card present No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image Device 0: unknown device ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! missing environment variable: pxeuuid Retrieving file: pxelinux.cfg/01-02-00-41-2d-68-a7 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/00000000 ethernet@5030000 Waiting for PHY auto negotiation to complete......... TIMEOUT ! Retrieving file: pxelinux.cfg/0000000 what can i do ? and how to do? 3ks
  25. Yesterday
  26. Describe what you did before to make it work. Show the DTS, the wiring you connected and the linux version that worked. If you used spidev before, I don't have experience in that. I only have experience with these drivers: panel-mipi-dbi-spi, ili9431 and adafrui-xy... The threads I showed you require you to stop using spidev, since the Linux kernel will communicate directly to the LCD, without a user program. Using both will just make them interfere with each other. If the LCD remains white and doesn't even flicker, and you made it work in an older kernel, then keep that wiring. If the /dev/fb0 exists, it means that linux has taken one SPI output port for display, but you need to make sure that: * and SPI parameters in the DTS are correct, * the gpio to handle the command/data, reset parameters are pointing to valid orange pi pins which are not used by anything else * the high/low polarity of those gpio * the wiring is correct, * the initialization bytes are correct
  27. Hmm... i dont think thats in there anymore due to some spring cleaning, all i have is: armbian-add-overlay armbian-install armbian-upgrade So I navigated to : https://github.com/armbian/configng/blob/main/tools/repository/armbian-config.sources Where I found: https://github.armbian.com/configng/ So I did: echo "deb [signed-by=/usr/share/keyrings/armbian.gpg] https://github.armbian.com/configng stable main" | sudo tee /etc/apt/sources.list.d/armbian-development.list > /dev/null sudo apt update sudo apt -y install armbian-config Lets hope it works out I totally understand, this problem will solve itself in what looks to be Linux 6.18 coming December.
  28. Kernel 6.1 is Vendor. Kernel 6.12 is Current / Mainline Kernel 6.16 is Edge. It's simple to change to edge. Just run armbian-config (it's available in the menu, or just type it in the command line using sudo). In armbian-config, as you make the selections, you'll find that you keep pressing ENTER until you get to the long list of kernels. Then scroll down to the latest Edge, which as of I last looked was 6.16.4. It may also say Armbian 25.8.1.
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines