kentAVR

As you known OrangePi PC PLUS with armbian (e.g. Armbian 22.05 Jammy) can't be fully off. (But Xunlong's Ubuntu 16 can be off ok) I suggest change status of board from green "Supported" to yellow "SUITABLE FOR TESTING (WIP)".

I use orangepi 4B. I use console Ubuntu with kernel 4 from Xunlong And my CPU Temperature (by htop) is about 70°C I use console armbian with kernel 5 (Governor = powersave). And my CPU Temperature is about 79°C Why so? I want to get 70°C in armbian too.

Please try this patch on latest kernel https://gitlab.manjaro.org/manjaro-arm/packages/core/linux/-/blob/master/0009-typec-displayport-some-devices-have-pin-assignments-reversed.patch

I suggest allow armbian script put deb-src without comment. For example I want to get system with deb-src packages. Of cause I can add deb-src via userpatches/customize-image.sh but it is not so easy. May be armbian add option like INSTALL_KSRC that allow user to get OS with uncommented deb-src in /etc/apt/sources.list It also helps in customize-image.sh For example: Main() { apt-get install libxcb-xinerama0-dev -y It will Error: You must put some 'deb-src' URIs in your sources.list The solution may be: ./compile.sh REPOSITORY_INSTALL=deb-src general.sh

My Orange Pi 4B has got FUSB302B too. USB Type-C gives power but my keyboard or mouse can't work... Other 2 USB type A works ok. I try Armbian_21.05.1_Orangepi4_focal_current, Armbian_20.05.3_Orangepi4_bionic_current. Thay doesn't work. But USB Type-C works on https://github.com/orangepi-xunlong/orangepi-build Looks like USB Type-C wants old kernel... How I use can @Oleksiipath with Orange Pi 4B ?

I try find $BOOTSOURCE in armbian docs. But nothing. But I know that armbian docs use a lot of words with $! I suggest allow users to find words with $ in armbian docs.

Solution

menuconfig is strange magic! Look! 1) I set my settings of kernel. 2) I save my settings of kernel to file /home/a/Documents/myArmbians/8armbian/linux-rockchip64-current.config 3) I load settings from /home/a/Documents/myArmbians/8armbian/linux-rockchip64-current.config 4) I verify settings and its ok 5) I do Exit, armbian save my settings (and block file) and write me [ o.k. ] Exporting new kernel config [ /home/a/Documents/myArmbians/8armbian/build/output/config/linux-rockchip64-current.config ] 6) I am going to file from 5) and verify and... My settings is reseted! WTF? So right magic way is: 1) I set my settings of kernel. 2) I save my settings of kernel to file /home/a/Documents/myArmbians/8armbian/linux-rockchip64-current.config 3) Exit and STOP (Ctrl+Z) armbian build system. 4) put file from step 2) to /home/a/Documents/myArmbians/8armbian/build/userpatches/linux-rockchip64-current.config 5) wating message from armbian [ o.k. ] Exporting new kernel config [ /home/a/Documents/myArmbians/8armbian/build/output/config/linux-rockchip64-current.config ] 6) do not stop build! Just go to this file and verify. Usually it contains my settings. P.S. I use Orange Pi 4B

I can't see .config file at /home/a/Documents/myArmbians/8armbian/build/cache/sources/u-boot/v2020.10. Ubuntu too... "Negative. Users don't need and should not change build script internals. When you do, also your script will not update anymore. Try to find reasoning for current situation, not adjusting documentation to the use case that will not be supported. At least not this way." Switch off U-Boot input-output capabilities is not supported by armbian build script via editing rockchip.txt in my case?

menuconfig is strange magic! Look! 1) I set my settings of kernel. 2) I save my settings of kernel to file /home/a/Documents/myArmbians/8armbian/linux-rockchip64-current.config 3) I load settings from /home/a/Documents/myArmbians/8armbian/linux-rockchip64-current.config 4) I verify settings and its ok 5) I do Exit, armbian save my settings (and block file) and write me [ o.k. ] Exporting new kernel config [ /home/a/Documents/myArmbians/8armbian/build/output/config/linux-rockchip64-current.config ] 6) I am going to file from 5) and verify and... My settings is reseted! WTF? So right magic way is: 1) I set my settings of kernel. 2) I save my settings of kernel to file /home/a/Documents/myArmbians/8armbian/linux-rockchip64-current.config 3) Exit and STOP (Ctrl+Z) armbian build system. 4) put file from step 2) to /home/a/Documents/myArmbians/8armbian/build/userpatches/linux-rockchip64-current.config 5) wating message from armbian [ o.k. ] Exporting new kernel config [ /home/a/Documents/myArmbians/8armbian/build/output/config/linux-rockchip64-current.config ] 6) do not stop build! Just go to this file and verify. Usually it contains my settings. P.S. I use Orange Pi 4B

So why gnome's settings contains X.org? "I look at /build/config/desktop/hirsute/environments/gnome/config_base/packages xserver-xorg xserver-xorg-video-fbdev gvfs-backends xfonts-base xinit bubblewrap dbus-x11 dictionaries-common evolution-data-server ..."

I want verify that U-Boot use rockchip.txt in my case. Since I run ./compile.sh BOARD=orangepi4 BRANCH=current RELEASE=hirsute BUILD_MINIMAL=no BUILD_DESKTOP=yes KERNEL_ONLY=no KERNEL_CONFIGURE=yes COMPRESS_OUTPUTIMAGE=sha,gpg,img BSPFREEZE=yes REPOSITORY_INSTALL="" EXTERNAL=no EXTRAWIFI=no AUFS=no WIREGUARD=no INSTALL_KSRC=yes OFFLINE_WORK=no BSPFREEZE=yes CREATE_PATCHES=yes DESKTOP_ENVIRONMENT=xfce armbian build U-Boot and I can see in log: 3.2.1. HOSTCC scripts/basic/fixdep HOSTCC scripts/kconfig/conf.o YACC scripts/kconfig/zconf.tab.c LEX scripts/kconfig/zconf.lex.c HOSTCC scripts/kconfig/zconf.tab.o HOSTLD scripts/kconfig/conf # # configuration written to .config # scripts/kconfig/conf --syncconfig Kconfig CFG u-boot.cfg GEN include/autoconf.mk.dep 1) Where I can find this U-Boot's .config ? I try search it but nothing is found... 2) "No. "rockchip.txt" defaults are automatically used if you build Orangepi 4. Defaults were not meant to be user changeable, but you can change them this generic way while building image or manually on the board." I still don't see problem with my suggestion to add to armbian docs something like "If you want change /boot/armbianEnv.txt you should use build/config/bootenv/$LINUXFAMILY.txt. For example if you use Orange Pi 4 you need change build/config/bootenv/rockchip.txt"

After good news about Panfrost support the main question is Does armbian support wayland since hirsute? I thinked -Of cause yes. Ubuntu hirsute is switched to wayland, but I look at /build/config/desktop/hirsute/environments/gnome/config_base/packages xserver-xorg xserver-xorg-video-fbdev gvfs-backends xfonts-base xinit bubblewrap dbus-x11 dictionaries-common evolution-data-server ... I dislike gnome. Let's go to /build/config/desktop/hirsute/environments/xfce/config_base/packages xserver-xorg xserver-xorg-video-fbdev xfonts-base xinit x11-xserver-utils xinit xorg-docs-core x11-apps xscreensaver xfonts-100dpi So Wayland or X.Org? Looks like X.Org...

Is anywhere on aliexpress mipi dsi with touch more than 13" ?

So in armbian docs need add something like "If you want change /boot/armbianEnv.txt you should use build/config/bootenv/LINUXFAMILY.txt. For example if you use Orange Pi 4 you need use build/config/bootenv/rockchip.txt" __________________________________________________ I try to understand why U-Boot ignore my /boot/armbianEnv.txt I try to set bootdelay=-2 1) I use google and people talking about another filename: uEnv.txt not armbianEnv.txt So how U-Boot knows about /boot/armbianEnv.txt ? There is no "/boot/armbianEnv.txt" in U-Boot source code... I try to make uEnv.txt by myself... 2) Is /boot/armbianEnv.txt need to be placed in FAT volume? I build .img for my Orange Pi 4 /boot/armbianEnv.txt and another are in some volume... Orange Pi 4_U-Boot.log