Everything posted by Werner
- Boot from NVME on Nanopim4 v2
- RTC ds1307 is not connecting rockpi4c+
- orangepi 3b 8gb
- OPI 5 HDMI output stops working (no signal) when screen turned off and on or HDMI cable unplugged an plugged back in
- RTC ds1307 is not connecting rockpi4c+
- RTC ds1307 is not connecting rockpi4c+
-
Help Armbian Grow: Support & Join Our Team!
Armbian is evolving rapidly, now supporting an ever-growing list of single-board computers (SBCs) - each with unique hardware, kernels, and configurations. As the variety of supported boards expands, so does the complexity of troubleshooting and providing effective user assistance. To keep up with this demand, we’re raising 5,000 EUR to hire part-time support agents who can help manage this increasing workload and ensure high-quality support for the community. Read more: https://forum.armbian.com/crowdfunding/project/16-help-armbian-grow-support-join-our-team/
- orangepi 3b 8gb
- Armbian_24.11.2_Orangepi5_noble_current_6.12.0-kisak NPU driver version
-
HK1 MAX RK3321 bricked
moved
- Anyone doing anything with the e20c?
-
T95X (S905X) 2/8 + Zabbix = fping error
Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
- Orange PI 5 Plus not booting
-
missing mali0 when setting up jellyfin in docker
moved to userspace
- OrangePi Zero old releases
- Which kernel mod needs to be loaded to get battrey support on cubietruck?
- Using the Armbian Build Environment
- Bananapi BPI-F3 Slow and Glitchy
- Orange Pi 3-LTS how do i enable UART 3
- Missing idiom/Language setup on System Setup.
-
Armbian doesnt seem to see sata harddrives.
It is. We made the best possible support from it. Each new sdk version brings fixes but also regressions. Though you actially have to give credit to rockchip for their rk35xx sdk. We had way worse in the past, not necessarily from rk but others like aml or aw. In comparison its surprisingly good Anyway it will take another few years until it is close to feature-complete in mainline. I think rk3399 still hasn't all its features mainlined but overall it is well matured now. You always have to keep in mind that some smart person have to sit down and write drivers for sometimes poorly, sometimes not at all, documented features of a soc. Either being paid to do so or being an enthusiast where latter are very very rare people and their efforts are often strongly under-appreciated.
-
Kernel oops after zfs module and 6.1.84-vendor-rk35xx
Yes there is some communication happening but this is out of scope for me. I do community Well thats unfortunate...and fortunate the same time. Let me explain real quick. rockchip socs have a built-in fixed boot order which is something like SPI, eMMC, microSD, USB and so on. However u-boot should be configured in a way, even though present on SPI or eMMC, it will check for an OS on microsd and try to boot that. tl;dr: Just write a fresh Armbian image on a microsd, put it into the ITX and power it on. It should boot from microsd. This system then can be used to fix your OS on the soldered eMMC.
- OrangePi 5 Pro
-
Kernel oops after zfs module and 6.1.84-vendor-rk35xx
Hi, first would be to set verbosity to 7 in order to get full boot logs. Excerpts are often useless. Further two things I'd do: For once I'd try to recover by chrooting into the system of the ITX by shoving the microsd into another arm64 machine (x86 can work too but it is far more annoying) and uninstall zfs package to see if this fixes the boot. If it is beyond recovery I'd try a fresh system from sd with a different userspace if the issue persists. Also just for the heck of it you could try this zfs package: https://github.com/zabbly/zfs I personnaly never tried this but it states to support arm64 so....just go for it Mainline is not an option for jellyfin, yes. It is far from being feature-complete while the rockchip sdk got most stuff working but, as correctly noticed, is fragile.
- Odroid M2 16G