Werner

Maybe they are still being assembled. Release is planned. Check for server images here and then do apt update/upgrade once its released: https://fi.mirror.armbian.de/archive/orangepi5-plus/archive/

Those which were sent upstream and accepted certainly will. It all depends on how long you want to wait seeing it running in Armbian

edge builds from mainline with these patches on top: https://github.com/armbian/build/tree/main/patch/kernel/rockchip-rk3588-edge Feel free to port some of Sebastians stuff which did not make it into 6.8.

Please share full log.

Just curious. Where did you read something about "run make"?

moved to staging.

There are actual two ways. You can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh KERNEL_CONFIGURE=yes which will continue to assemble an image with the modified config file which is more user friendly. On the other hand there is code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh kernel-config which will export the modified kernel config into code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } output/ folder and stops there which is more developer friendly. If you chose latter route you need to move the exported config to userpatches or overwrite the one in code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } config/kernel/. Once you done that simply execute code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } ./compile.sh and the modified config will be used.

Hi, =y means the driver/functionality is directly compiled into the kernel =m means it will be built and made available as kernel module

moved

Just install docker from Debian/Ubuntu repo. Grabbing directly from docker is overrated imho unless you need very new features.

duplicate

Thought about bumping to rc3 yesterday but figured it wasn't worth it since there were no relevant changes.

moved to tvboxes

1468 ### ip addr: 1469 p default qlen 1000 1471 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 1472 inet XXX.XXX.0.1/8 scope host lo 1473 valid_lft forever preferred_lft forever 1474 inet6 ::1/128 scope host noprefixroute 1475 valid_lft forever preferred_lft forever ult qlen 1000 1477 link/ether 6e:48:1c:02:bd:e7 brd ff:ff:ff:ff:ff:ff 1478 Either the logs are incomplete or the ethernet ports don't show up at all. Odd...

No ETA from our side. Since Collabora is working on this I suggest to ask them

Open as much topics as you need. That is what forums are for. I don't like those multiple pages long mega-threads anyways but for some reason some users seem to be fine with them. As for me at least I don't see how value information can be found within when there is a need to read page by page by page while with multiple topics you immediately see what's going on inside There should be as minimal adjustments needed as possible since this tool is undergoing major rewrite anyways so besides having it as a working proof-of-concept for the new version it would be a waste of time. Haha, true story. Anyway as bad as some rants (not only Igors ) read there is always some truth within and the truth often is either misunderstood or hurts or both. Therefore no further action is taken here besides asking everyone to calm down if necessary and keep it more constructive, alright? -> Oh boy, that was a lot of off-topic

So when UART works you can use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbianmonitor -U to print debug output to serial and then use a pastebin service of your choice to share the whole output.

https://debug.armbian.de

Better method would probably be using debug serial console to grab the output while the crash happens. https://debug.armbian.de

Could be a loose connection/slack joint. Hard to tell remotely Yeah that one should do.

I don't know. You can check by yourself (something like code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt-cache search linux*current-rockchip64) Well that would rather be a downgrade than an upgrade Anyway while switching kernel again would work the module you want to build and need the headers for will not.

You need the kernel headers matching your kernel version. Older headers will not work. However we had (have?) some issues with the repository so you may need to switch to a different kernel version which also has the matching headers in the repo.

There never was a cert since it is just a simple redirect to https://armbian.myspreadshop.net/ so feel free to use this address.

If desktop version supports HDMI then CLI and minimal do as well.

1. Not using CP2102 as it cannot handle 1.5mbaud. CP2104 for example does. 2. not using random UART you find on the GPIO but using the actual debug UART connectors: https://wiki.friendlyelec.com/wiki/images/7/7c/NanoPi_NEO3-layout.jpg 3. @lpirl can be right too. I used to own a Neo3 just like yours but it died on me.