Werner

Hi, no official plans as I am aware of. However anyone can step up and try to adopt the newer rk bsp into the build framework.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Double-check that you can reach that IP address through your internet connection.

Hm this is odd. Joshua's and our kernel sources are very close. He did some adjustments for packaging and directly integrated some wifi stuff but that's it...

For now using 5.10 vendor bsp is the way to go. 6.8 is - as the name implies - bleeding edge and problems are to be expected. This will most likely be addressed upstream sooner or later. MAY take a while since there seems to be a general shortage in 32G boards due to the lack of available memory chips.

Probably because nobody ever used it and therefore it never has been activated. Feel free to provide a PR to fix this.

Elaborate

You can always build an image combining the kernel and userspace flavor of your choice. https://github.com/armbian/build

You get is what you pay for. With low price there is no money left for software development. I don't think its worth the wait. There won't be significant improvements anymore in this version but that is up to you. You can always check the diff between the RCs and whole versions:https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/?id=v6.8-rc4&id2=v6.8-rc3&dt=2

Depends on the branch you are on. Mainly used for RK3588 atm are legacy and edge. Latter is following mainline which will probably receive another bump once 6.8 has released and then maybe, if there is enough interesting code, bumped further to 6.9-rc. Legacy is based on vendor bsp and occasionally people try to fix the flaws within this messy code which is then adopted and pushed via apt. Switching branches is possible via armbian-config. Also switching to beta is possible.

This command is provided by Ubuntu userspace and has nothing to do with Armbian. Userspace upgrades are neither tested nor supported.

You're doing great Draft PR usually means it is WIP or the author implies it shall not be merged (yet). So once you think you are done with your adjustments mark it ready for review. It is still possible to do adjustments after that.

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.

These forums automatically grabs RSS/Atom feed from various sources. If you have an idea about what could be added feel free to leave a link here.