multiblitz

Lets say I wish to creat three kernels with different timer settings like 100Hz/250Hz/1000Hz. The name of the generated SDcatd image is always the same which is not helpful. When I want to use them later as well for a multiboot scenario, so swtchable kernels, I need as well different names, so it is not only to rename the image files. USing Menuconfig, I could normally put a localization extension to it...when I do this, the image creation process fails as the system looking into wrong folder names. So, is there an alrernative path ? Or is this a bug ?

Thx...working on it...when I look onto the conf file, there is a default entry which has some more entries than the labels like... label default fdtdir /usr/lib/modules/linux/dtb/ kernel /usr/lib/modules/linux/vmlinuz append loglevel=4 root=PARTUUID=8b029f90-01 cma=896M coherent_pool=2M selinux=0 audit=0 c> cma..cohorent_pool etc ? And I dont have a /usr/lib/modules/linux/dtb/: root@nanopineo3:/usr/lib/modules# ls 5.19.14-rockchip64 Linux_5.19.16_100HZ ..so I guess...i simply copy your stanza im as default, correct ? So we have label default fdtdir /usr/lib/modules/5.19.14-rockchip64/dtb/ kernel /usr/lib/modules/5.19.14-rockchip64/Image initrd /usr/lib/modules/5.19.14-rockchip64/initrd.img-5.19.14-rockchip64 append root=PARTUUID=59d35469-01 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 consoleblank=0 loglevel=1 ubootpart=59d35469-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u consoleblank=0 quiet irqaffinity=0 nosoftlockup nmi_watchdog=0 nohz=on isolcpus=nohz,domain,1-3 nohz_full=1-3 rcu_nocbs=1-3 no_balance_cores=1-3 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 label Linux_5.19.16_100HZ fdtdir /usr/lib/modules/Linux_5.19.16_100HZ/dtb/ kernel /usr/lib/modules/Linux_5.19.16_100HZ/Image initrd /usr/lib/modules/Linux_5.19.16_100HZ/initrd.img-5.19.14-rockchip64 append root=PARTUUID=59d35469-01 rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 consoleblank=0 loglevel=1 ubootpart=59d35469-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u consoleblank=0 quiet irqaffinity=0 nosoftlockup nmi_watchdog=0 nohz=on isolcpus=nohz,domain,1-3 nohz_full=1-3 rcu_nocbs=1-3 no_balance_cores=1-3 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 ? As I will always use only SSH with the NPiNeo3, the default is important for switching... I changed the name of the new copied content of the 100HZ Kernel as you see...i hope that this will not create problems ? I found when I create my own custom kernels and want to give it a local name extension in general settings...the creation of the image fails...so i have the issue that all my Kernel-Images have the same name which is a bit confusing to know who is who...if there is a way how to give a custom configure kernel its own name without messing up sd card image creatiin, please let me know...

THX for your support ! My starting point is a sdcard with Armbian on it lets say 250HZ Kernel. Now, the first question is how to get the second Kernel with 100 HZ Timer onto it....Using ARmbian ./compile.sh again and chose the first option "Build Kernel package and uboot" ? And than copy this to the card ? Or Download from Kernel.org and compile like with a x86 ? Not sure if on an Arm devices the normal Kernel can be created or if the add ons/drivers are missing than...I generated once a Kernel for ARM from Kernel.org...generation was no isse, but than did not know how to teach "uboot" that its there now (like with the x86 and update-grub). So, the current infos are: root@nanopineo3:~# cat /proc/cmdline ls -hal /boot lsblk -o +PARTUUID root=UUID=673c38cb-a7b1-4743-8c7c-8831fa10ce2b rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 consoleblank=0 loglevel=1 ubootpart=59d35469-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u consoleblank=0 quiet irqaffinity=0 nosoftlockup nmi_watchdog=0 nohz=on isolcpus=nohz,domain,1-3 nohz_full=1-3 rcu_nocbs=1-3 no_balance_cores=1-3 cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 total 58M drwxr-xr-x 3 root root 4.0K Oct 13 11:17 . drwxr-xr-x 20 root root 4.0K Oct 10 22:47 .. -rw-r--r-- 1 root root 382 Oct 13 11:17 armbianEnv.txt -rw-r--r-- 1 root root 0 Oct 12 21:33 armbianEnv.txt.out -rw-r--r-- 1 root root 1.5K Oct 9 22:18 armbian_first_run.txt.template -rw-r--r-- 1 root root 38K Oct 9 22:18 boot.bmp -rw-r--r-- 1 root root 3.1K Oct 9 22:15 boot.cmd -rw-rw-r-- 1 root root 3.2K Oct 9 22:20 boot.scr -rw-r--r-- 1 root root 235K Oct 9 22:07 config-5.19.14-rockchip64 lrwxrwxrwx 1 root root 22 Oct 9 22:17 dtb -> dtb-5.19.14-rockchip64 drwxr-xr-x 6 root root 4.0K Oct 9 22:17 dtb-5.19.14-rockchip64 lrwxrwxrwx 1 root root 26 Oct 9 22:17 Image -> vmlinuz-5.19.14-rockchip64 -rw-r--r-- 1 root root 12M Oct 9 22:25 initrd.img-5.19.14-rockchip64 -rw-r--r-- 1 root root 0 Oct 9 22:17 .next -rw-r--r-- 1 root root 6.1M Oct 9 22:07 System.map-5.19.14-rockchip64 lrwxrwxrwx 1 root root 26 Oct 9 22:25 uInitrd -> uInitrd-5.19.14-rockchip64 -rw-r--r-- 1 root root 12M Oct 9 22:25 uInitrd-5.19.14-rockchip64 -rw-r--r-- 1 root root 30M Oct 9 22:07 vmlinuz-5.19.14-rockchip64 NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT PARTUUID mmcblk0 179:0 0 7.5G 0 disk └─mmcblk0p1 179:1 0 7.3G 0 part / 59d35469-01 zram0 252:0 0 990.4M 0 disk [SWAP] zram1 252:1 0 50M 0 disk /var/log When you say in the second link: "First step: prepare kernel package (copy files around)" ...which Kernel package do you mean in my example ? The original one with 250 HZ or the new one with 100 HZ ?

I have a coupleof different boards I would like to try this, but lets start with Rockchip 3328h (NanoPiNeo3). I read through the thread linked...but its a bit beyond my current understanding...can you give me a command-line type of tutorial what to do ? That would be very cool. On x86/grub is was a breath...but uboot is new to me.

I searched the forum, but did not find anything...: I am creating my own Kernel configurations with Armbian, for example I want to observe the effect of 100Hz/250Hz/1000Hz on the timer on osnoise etc. Currently ./ compile.sh can result in two outputs: - Either a SD-Card-Image with one Kernel configuration - or some Kernel-files in "Output" I dont yet understand in their structure or what to do to activate them on an already created running System making it bootable I saw that Armbian-Config offers to switch Kernels, but this loooks more like a long list of standard-kernels from somewhere...how can I use this or a different technique like uboot to set my SD-card up like: Three custom Kernels stored e.g. for the three frequencies switchable for the next boot.

Thanks for the fast reaction...as I said...I am an armbian-beginner and in the process to learn what you provide..and that is already great stuff. In the meantime I learned that armbian-config has the option to install a kernel source...tried that...and BINGO ! Now we have the needed source-files. RTLA install procedure is than: cd /usr/src/linux-source-5.19.14-rockchip64/tools/tracing/rtla apt install python3-docutils -y apt install pkg-config -y apt install git -y git clone git://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git cd libtraceevent/ make sudo make install cd .. git clone git://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git cd libtracefs/ make sudo make install cd .. make sudo make install great stuff.. now I can compare osnoise effects of different kernel configs and software setups on arm as I can already on x86...which is exptremely helpful to observe tickless mode and otimize for PCM-audio-playback in highest quality...

Sorry to ask such a beginner question, but I am still learning about Armbian... When I install debian Kernels from Kernel.org myself, I find this in my source-folder of the distro which I created when unzip/tar the Kernel. But as Armbian does this in the backround for me...where is this folder ? RTLA is a new tool to use osnoise tracer and needs to be compiled from source. https://lwn.net/Articles/869563/ THX