Jump to content

Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates

  1. Past hour
  2. https://paste.next.armbian.com/yogopozufa
  3. Today
  4. Hi, if you compile your kernel with "CONFIG_SUN55I_PCK600" set, you'll have the second ethernet port. But you'll loose the wifi adapter, just like in the trunk.129.
  5. @Hqnicolas thanks for your feedback! It's appreciated!
  6. thank you for your work. i have the x96q pro picture attached. i have built the x96q lpddr3 and the w96q lpddr3 v1.3 . both are booting . the problem is with wifi sometimes is not recognised and it needs rebooting few times to work. also i noticed with lpddr3 build the cpu cores are always near 100% but with lpddr3 v1.3 only one core get 100% and not too often.
  7. Hello, idk if this the right place to ask, but, I'm really struggling to get a working driver for the sv6256p, I can't find a repository that compiles on kernel 6.X. My question is, where is the driver source that builds for the rk322x uses? I want to compile it on my installation. I already tried moving the driver files from a rk322x build to my installation, but it didn't work.
  8. I am in the process of installing Armbian on the X88pro13 TV box, which has the RK3528 CPU. https://github.com/joilg/x88pro wifi and ethernet are working
  9. @GmP oook, so now I understand the differences between the two dtso files provided here and in the other thread. Do you spot other differences or peculiarities? Things that are useful are: * the gpio led (do the separate red/blue/green led blinks on both boards?) * wifi reset gpio (do wifi get detected in both boards with base configuration?) * is there a separate PMIC like rk805/rk808 on any of the boards? Things like these go into the dtso for full board support. The PMIC is very important since missing that could cause stability issues.
  10. I followed the "mesa route" without any kind of problem. I cannot following the "libMail route" due to my window manager choice: I installed the Armbian Ubuntu Noble version, but I'm running X Window (not Wayland) in order to get the remote display of the Orange PI Plus running on a local monitor; I tried to do this using Wayland without success. I'im running lightdm and xfce4 now. So the /dev/mail0 is still useful or the mesa-vulkan-drivers are enough ? I read some documentation about the hardware acceleration but in my opinion it is too contradictory. But it is always possible that I'haven't understand anything.....
  11. After wanting to use Debian 13 (Trixie) @Nick A suggested trying to build it myself, and this was my first experience building an Armbian image. I encountered some obstacles, but I got through them. I saw that the model was mentioned branch v20251014. I tried building it (Mate Desktop), which as build smoother than (v20250306) before. I tried booting it with this box (Transpeed 8K618-T) and and found that the wifi was not visible. I followed the troubleshooting methods in the previous thread solved it. I have installed additional IR remote and OpenVFD. Now everything is smooth and happy. The only thing left is the video acceleration, but that would be difficult because it is beyond my ability. Finally, thank you, @Nick A
  12. Even though current is an LTS kernel it probably makes more sense to focus on vendor an edge. vendor because its rockchip bsp and close to being feature-complete. And edge for likely becoming the next LTS kernel which ultimately become current at some point. You can try to see what actually works on current at this time. You can ignore 6.15-6.17 since those patches, if still present, are for archival purposes only and will be remove at some point. In theory it could be re-used but may introduce confusion. If in doubt, copy and rename. Edit: Seems like lots of stuff has been mainlined already. So I suggest shifting your primary focus on edge.
  13. Armbian 25.8.1 Noble XFCE (BSD Kernel: 6.1.115) + PanVk - mesa 25.2.6 (https://launchpad.net/~kisak/+archive/ubuntu/kisak-mesa) + box64 3.9 (https://ryanfortner.github.io/box64-debs/) + wine-10.17-staging-tkg-amd64-wow64 (https://github.com/Kron4ek/Wine-Builds/releases/tag/10.17) + DXVK-sarek-stripped v1.11.0 (https://github.com/pythonlover02/DXVK-Sarek/actions) ~30fps@720p Dark Souls: Remastered
  14. That's probably the boot partition in fat32. You can't read linux partitions in Windows without tools. So it's normal you can't read an armbian image in windows since it doesn't use fat partitions. Why it doesn't boot is another case. I would try to build my own image with either legacy or mainline kernel. I don't have the board so no idea what works on it.
  15. It is nog normal desktop images are not available. You can always install a desktop to server images. I use taskset for desktops that need a lot of dependancies. sudo apt install taskset sudo taskset For the xu4 there should be not much difference with the armbian desktop images except for the background image.
  16. Yesterday
  17. Hi, my feedback with rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp and agressif fancontrol setting like this: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 FCTEMPS=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input MINTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=30 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=30 MAXTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=50 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=50 MINSTART=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINSTOP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINPWM=20 is: All it's Okok Without the tunning file DTB and Fancontrol, the nighmare restart. Today, update, original DTB file restore and CRASH when Luks begin to unciffer my DDs Il restore DTB file and my fancontrol setting and: Return to Okok situation. To conclude, i use my helios without problem when this files is installed. My helios64 always crash if i return to original setting after a update.
  18. I also happened to get an X88pro13 TV box on my desk. Since it promises good performance, I've been experimenting with getting Armbian running.. My first attempts look promising. Armbian-update and armbian-config are working. It could be a good platform for Smart-Home, Console and desktop Armbian is running well. _ _ _ __ __ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ ___ _ _ _ _ ___ / _|/ _(_)__(_)__ _| | / _ \| '_| ' \| '_ \ / _` | ' \___| || | ' \/ _ \ _| _| / _| / _` | | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| \_,_|_||_\___/_| |_| |_\__|_\__,_|_| v25.11 rolling for Hugsun X88pro running Armbian Linux 6.1.115-vendor-rk35xx Packages: Ubuntu stable (noble) Support: DIY (custom image) IPv4: (LAN) 192.168.178.71 (WAN) 130.185.10.185 Performance: Load: 82% Uptime: 0 min Local users: 3 Memory usage: 7% of 3.82G CPU temp: 41°C Usage of /: 10% of 58G RX today: 262 KiB Commands: Configuration : armbian-config Monitoring : htop HDMI output, LAN, Wi-Fi, and USB 2.0 are supported. Audio not tested yet. Bluetooth and USB 3.0 aren't working yet and require further investigation. IR remote control is also not working. I've shared my results and instructions for creating the image at: https://github.com/joilg/x88pro A ready-made image for an Armbian server with a console interface is available at: https://github.com/joilg/x88pro/tags A desktop version can also be easily created. Please try this version and let me know if you encounter any problems. johlnx
  19. i`ll already fried that lcd. So this is the end Because short circuit is been in lcd, orange is a live for now. try to move on hdmi lcd+touch. Thanks for U`r help robertoj.
  20. I confirm this issue. For the purposes of this experiment, I replaced the power supply with a similar one equipped with an LED. The power supply is connected to an electrostatic precipitator equipped with a power button. We turn on the electrostatic precipitator using the button. The power supply LED lights up. The Odroid M1 turns on and boots normally. We shut down the Odroid M1. We turn off the electrostatic precipitator using the button. After 2 seconds, we turn it back on. The Odroid M1 does NOT turn on again. Therefore, replacing the power supply did NOT solve the problem. Experimentally, we have determined that the Odroid M1 does NOT turn on again as long as the power supply LED remains lit, even when the electrostatic precipitator is turned off. Therefore, the issue lies with the residual charge in the power supply capacitors. If, with the electrostatic precipitator turned off, we wait until the power supply capacitors are depleted and the power supply LED goes out, then when we turn on the electrostatic precipitator again, the Odroid M1 turns on normally and boots normally. Meanwhile, the Raspberry Pi doesn't have this power supply issue. Therefore, this is a design flaw in the Odroid M1.
  21. Thank you @Werner it just worked perfectly once disabled. That'll teach me to enable things. Beyond lower CPU usage compared to a USB to SATA adapter, I have some performance benchmarks. // write dd if=/dev/zero of=testfile bs=1M count=3000 oflag=direct 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 11.382 s, 276 MB/s (usb) 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 9.74696 s, 323 MB/s (sata) // read dd if=testfile of=/dev/null bs=1M iflag=direct 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 10.8119 s, 291 MB/s (usb) 3145728000 bytes (3.1 GB, 2.9 GiB) copied, 9.09585 s, 346 MB/s (sata) And some Jellyfin CPU vs Hardware accelerated transcoding usage:
  22. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
  23. It all depends on the GUI apps you want to run. Web browser: at least 4GB Your own Python GUI app: 1GB 16GB storage is fine. "A more advanced build framework" only refers to the laptop you use to compile your own Armbian OS... it doesn't refer to the SBC where you will run it.
  24. Last week
  25. The mainline kernel has currently a shortcoming in USB-TYPEC support. FUKAUMI Naoki demonstrated a workaround for other devices that also works for the ODROID-M2.
  26. https://paste.armbian.com/nesusobaso Thanks, don't know if diags file is complete:
  1. Load more activity
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines