-
Upcoming Events
-
-
Volunteering positions
-
Test Automation Engineer
Position: Software integration test engineerNumber of places: 16Applicants: 8
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
10
Amlogic S905X -- Cannot install Armbian to internal eMMC
Hi pochopsp - I have the same issue on my Vontar X3. The frustrating thing is that it used in the past and now for some reason it doesn't detect the eMMC installation anymore. I haven't done a deep dive but probably (as the other participants in this thread suggest) it's only solvable with a new u-boot. Have you tried something out there? I guess if we get a new build running that new u-boot could be bundled with the releases to solve this issue for other users as well -
10
Radxa rock-3c stuck at login & no hdmi
AFAIK this can mean the ROCK3C (and software running on it) failed on interpreting HDMI info from your specific HDMI monitor (too old, buggy, not according spec, strange timing, too new, maybe more). See things w.r.t. EDID. One can set a certain video= statement on the kernel cmdline, you need to read docs etc what the options are. Easier might be to use an newer kernel, rockchip64 edge kernel is 6.18.x, that one much better RK35xx support than the 6.12.x one in the image. See armbian-config for selecting edge/beta kernel. Or change sources.list yourself so that you can just do apt install linux-image-edge-rockchip64 -
776
How to install armbian in h618?
@Malay delete patch/u-boot/u-boot-aw/99-dump-dram-controller-regs.patch. Using your compiler it causes a fatal error. The compiler I'm using it creates a warning. You don't need it anyways, it's for ram debug messages. I removed it from my repository, -
16
N2+ Impervious to Timekeeping Applications
I assume you are not blind and need some screen to see what data you enter into computers. I am not saying the N2+ is HDMI connected, but sure you do use some serial console cable and terminal program or ssh or maybe even telnet. But jokes aside, I think you do not get the point that it is you yourself who needs to get your own device working if you want Debian (because Armbian is busted according to you). I mean vanilla Debian, so only Debian packages that can be fetched via apt from Debian repositories. So that means no Armbian kernel+DeviceTree and no Armbian U-Boot. That is what I show you essentially. But read info on debian.org. Up to you to jump into the cold water and swim. You already figured out it is something with I2C busses/numbering, so that is DeviceTree and/or DeviceTree overlays. Vanilla Debian is roughly 1 year older than 25.11.1 Armbian Trixie, so if no-one who owns an N2+ (and is willing to do testing/trials for you) is reacting, you are the only. You can send your N2+ to me, maybe I can make it work, but I won't send it back as I need some sort of salary for the work done of course. Other option is Ubuntu Jammy image (with custom/vendor kernel) from odroid.com or so. -
7
Orange PI 5 Armbian 25.8.2 Ubuntu Server 24.04/6.12 does not boot (kernel panic)
I expect 2x the figure: dmesg | grep PCIe pci 0004:41:00.0: 4.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x1 link at 0004:40:00.0 (capable of 15.752 Gb/s with 8.0 GT/s PCIe x2 link) lspci -vv | grep LnkSta LnkSta: Speed 5GT/s (downgraded), Width x1 (downgraded)
-
-
Member Statistics
