Werner

As from what I have learned in the past that sometimes the matching header package is missing. Don't know the reason. @Igor may.

If you are talking about the headers and they are not in the repo I can't tell you, sorry. The easiest way around here is using the build script as written above to create matching packages.

Providing logs is essential for any support request since people sometimes using wrong images, inofficial or unsupported images. Feel free to use the build system for this purpose. You can add userpatches as well as adjusting the config. The script will output debs with the source, the image, matching headers as well as an u-boot package which all can simply be installed by using dpkg -i. https://github.com/armbian/build

You were using an outdated image. This issue has been fixed a while ago.

I guess they rebranded an armbian image which includes alternative drivers for xradio and added the temperature fix....

Hard to tell without further information. What image are you using? armbianmonitor -u

armbianmonitor -u

Odd. You could utilize steamroller tactics and place the symlink into conf-enabled directly and see what happens when you restart apache. Maybe there is something wrong with the config file itselt and therefore it is not detected properly.

Unsupported build Please provide logs via armbianmonitor -u

You are the one who is requesting help, not me.

Best chance to get an idea about the temperature is a laser thermometer I guess...

For other distributions you can always install mesa from source. Also there is a PPA from oibaf which though does not seem to cut it with its the prebuild debs. Had more success with doing the first variant.

armbianmonitor -u

I think these wishes, besides the DE are out of range for Armbian. Armbian provides a usable kernel for many different boards and puts a OS over it with minimal adjustments to provide a mostly untouched experience with that OS. It is up to you to customize your OS as it is in any other distribution. By the way you can customize it even at image level while building. Check https://docs.armbian.com/Developer-Guide_User-Configurations/#user-provided-image-customization-script

Simply build a kernel package and then extract the created source debian package and check that particular file

Feel free to drop an image for the OPi1+ somewhere and I'll test it. I'm just out of time until monday.

1810000 -> 1488000 Did you reload cpufrequtils afterwards?

How?

Also my guess since [ OK is missing before the ] ...

You are way outdated. This old release is not supported anymore. How do you power the board?

Welp, nothing much that can be done about unfortunately...

If anyhow possible always provide the output of armbianmonitor -u along with bug reports.

Of course. The fat "Documentation" button on top between Download and Subscriptions https://docs.armbian.com/ To get some things sorted out beforehand: Check which kernel sources the tinkerboard uses (hangle yourself from the board config to the source config). Then you will also know the patch folder where kernel patches are held and applied to the sources before building.

Maybe PAE is missing in the kernel?

The description is probably outdated.