<?xml version="1.0"?>
<rss version="2.0"><channel><title>Radxa Rock Pi S Latest Topics</title><link>https://forum.armbian.com/forum/248-radxa-rock-pi-s/</link><description>Radxa Rock Pi S Latest Topics</description><language>en</language><item><title>Armbian Trixie/Bluetooth/Pipewire</title><link>https://forum.armbian.com/topic/57394-armbian-trixiebluetoothpipewire/</link><description><![CDATA[<p>
	Can't seem to get bluetooth working with trixie and pipewire.
</p>

<p>
	I can pair &amp; trust, just can't connect.
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Failed to connect: org.bluez.Error.Failed br-connection-profile-unavailable</span></pre>

<p>
	 
</p>

<p>
	Anyone else had this issue?
</p>

<p>
	 
</p>

<p>
	Was working fine on a cubie running bullseye, so next maybe I'll try and older os and see...
</p>
]]></description><guid isPermaLink="false">57394</guid><pubDate>Thu, 15 Jan 2026 06:58:06 +0000</pubDate></item><item><title>The Rock Pi S completely freezes during OOMs</title><link>https://forum.armbian.com/topic/57281-the-rock-pi-s-completely-freezes-during-ooms/</link><description><![CDATA[<p>
	When running PassMark on my Rock Pi S running Armbian 25.11, the system completely freezes, including the serial console. The blue TF card read/write LED stays lit, and OOM events are visible on the serial console. This freeze typically lasts over half an hour before the system recovers as the blue LED turns off. OOM events also occur on the stock kernel 4.4 system, but it doesn't freeze. I really don't want to use the 4.4 kernel system, but how can I optimize it? Below is my system configuration and log output:
</p>

<p>
	Translated with DeepL.com (free version)
</p>

<p>
	 
</p>

<p>
	pi@Pi-s:~$ uname -a<br />
	Linux Pi-s 6.12.58-current-rockchip64 #3 SMP PREEMPT Thu Nov 13 20:34:41 UTC 2025 aarch64 GNU/Linux<br />
	pi@Pi-s:~$ cat /etc/os-release<br />
	PRETTY_NAME="Armbian 25.11.2 trixie"<br />
	NAME="Debian GNU/Linux"<br />
	VERSION_ID="13"<br />
	VERSION="13 (trixie)"<br />
	VERSION_CODENAME=trixie<br />
	DEBIAN_VERSION_FULL=13.2<br />
	ID=debian<br />
	HOME_URL="https://www.armbian.com"<br />
	SUPPORT_URL="https://forum.armbian.com"<br />
	BUG_REPORT_URL="https://www.armbian.com/bugs"<br />
	ARMBIAN_PRETTY_NAME="Armbian 25.11.2 trixie"<br />
	 
</p>

<p>
	pi@Pi-s:~$ cat /sys/class/leds/rockpis\:blue\:user/trigger<br />
	none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock disk-activity disk-read disk-write mtd <abbr title="A type of flash memory">nand</abbr>-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 activity default-on panic usbport [mmc1] mmc2 mmc0 rfkill-any rfkill-none stmmac-0:01:link stmmac-0:01:100Mbps stmmac-0:01:10Mbps bluetooth-power rfkill0 hci0-power rfkill1<br />
	 
</p>

<p>
	===befor run passmark========
</p>

<p>
	pi@Pi-s:~$ free -h<br />
	               total        used        free      shared  buff/cache   available<br />
	Mem:           466Mi       116Mi       145Mi       328Ki       215Mi       350Mi<br />
	Swap:          233Mi        20Mi       212Mi<br />
	 
</p>

<p>
	==running passmark==========
</p>

<p>
	pi@Pi-s:~$<br />
	[  672.734497] systemd-journal invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=-250<br />
	[  672.735618] CPU: 2 UID: 0 PID: 388 Comm: systemd-journal Not tainted 6.12.58-current-rockchip64 #3<br />
	[  672.735638] Hardware name: Radxa ROCK Pi S (DT)<br />
	[  672.735645] Call trace:<br />
	[  672.735650]  dump_backtrace+0x94/0x114<br />
	[  672.735670]  show_stack+0x18/0x24<br />
	[  672.735679]  dump_stack_lvl+0x78/0x90<br />
	[  672.735692]  dump_stack+0x18/0x24<br />
	[  672.735700]  dump_header+0x40/0x1a8<br />
	[  672.735715]  oom_kill_process+0x130/0x358<br />
	[  672.735727]  out_of_memory+0xdc/0x568<br />
	[  672.735738]  __alloc_pages_noprof+0xcbc/0xdcc<br />
	[  672.735752]  alloc_pages_mpol_noprof+0x88/0x23c<br />
	[  672.735762]  alloc_pages_noprof+0x48/0xc0<br />
	[  672.735770]  folio_alloc_noprof+0x14/0x64<br />
	[  672.735778]  filemap_alloc_folio_noprof+0x140/0x154<br />
	[  672.735789]  __filemap_get_folio+0x208/0x394<br />
	[  672.735799]  filemap_fault+0x54c/0x858<br />
	[  672.735809]  __do_fault+0x3c/0x134<br />
	[  672.735821]  __handle_mm_fault+0x9e4/0x17cc<br />
	[  672.735831]  handle_mm_fault+0xe8/0x2e4<br />
	[  672.735839]  do_page_fault+0x100/0x58c<br />
	[  672.735851]  do_translation_fault+0xac/0xc8<br />
	[  672.735860]  do_mem_abort+0x44/0x94<br />
	[  672.735873]  el0_da+0x2c/0x9c<br />
	[  672.735883]  el0t_64_sync_handler+0xe4/0x158<br />
	[  672.735893]  el0t_64_sync+0x190/0x194<br />
	[  672.735904] Mem-Info:<br />
	[  672.745515] active_anon:9385 inactive_anon:40818 isolated_anon:0<br />
	[  672.745515]  active_file:662 inactive_file:777 isolated_file:0<br />
	[  672.745515]  unevictable:0 dirty:0 writeback:0<br />
	[  672.745515]  slab_reclaimable:3237 slab_unreclaimable:8655<br />
	[  672.745515]  mapped:65 shmem:7 pagetables:779<br />
	[  672.745515]  sec_pagetables:0 bounce:0<br />
	[  672.745515]  kernel_misc_reclaimable:0<br />
	[  672.745515]  free:1597 free_pcp:34 free_cma:1<br />
	[  672.748854] Node 0 active_anon:123756kB inactive_anon:77056kB active_file:2736kB inactive_file:2428kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:260kB dirty:0kB writeback:0kB shmem:28kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:0kB writeback_tmp:0kB kernel_stack:2144kB pagetables:3116kB sec_pagetables:0kB all_unreclaimable? no<br />
	[  672.751655] Node 0 DMA free:6336kB boost:0kB min:2684kB low:3352kB high:4020kB reserved_highatomic:0KB active_anon:38576kB inactive_anon:162236kB active_file:3244kB inactive_file:2308kB unevictable:0kB writepending:0kB present:522240kB managed:477808kB mlocked:0kB bounce:0kB free_pcp:436kB local_pcp:0kB free_cma:68kB<br />
	[  672.754668] lowmem_reserve[]: 0 0 0 0<br />
	[  672.755060] Node 0 DMA: 653*4kB (UMEC) 164*8kB (UMEC) 90*16kB (UE) 13*32kB (UE) 5*64kB (E) 4*128kB (E) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 6612kB<br />
	[  672.756372] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB<br />
	[  672.757147] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=32768kB<br />
	[  672.758033] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB<br />
	[  672.758825] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=64kB<br />
	[  672.759562] 1693 total pagecache pages<br />
	[  672.762567] 243 pages in swap cache<br />
	[  672.762925] Free swap  = 212kB<br />
	[  672.763223] Total swap = 238900kB<br />
	[  672.763550] 130560 pages RAM<br />
	[  672.763816] 0 pages HighMem/MovableOnly<br />
	[  672.764163] 11108 pages reserved<br />
	[  672.764453] 4096 pages cma reserved<br />
	[  672.764770] Tasks state (memory values in pages):<br />
	[  672.768270] [  pid  ]   uid  tgid total_vm      rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name<br />
	[  672.769454] [    233]   990   233     5947       81       32       49         0    94208      640             0 systemd-resolve<br />
	[  672.770505] [    234]   988   234    23067       16        0       16         0    81920      256             0 systemd-timesyn<br />
	[  672.771532] [    242]     0   242     8746       96       32       64         0    86016      512         -1000 systemd-udevd<br />
	[  672.772547] [    264]   998   264     6903      236       64      172         0    90112      320             0 systemd-network<br />
	[  672.773662] [    369]     0   369     4570       32       32        0         0    77824      384             0 wpa_supplicant<br />
	[  672.774698] [    388]     0   388     6833       67       32        0        35    81920      256          -250 systemd-journal<br />
	[  672.775746] [    484]   100   484     1445       92       32       60         0    53248       32             0 avahi-daemon<br />
	[  672.776772] [    488]     0   488     2520       32       32        0         0    49152       32             0 cron<br />
	[  672.777768] [    491]   996   491     2064       93       32       61         0    53248      160          -900 dbus-daemon<br />
	[  672.778778] [    518]     0   518    55049      180       96       84         0    73728       96             0 rsyslogd<br />
	[  672.779770] [    519]     0   519     4682       38       32        6         0    81920      256             0 systemd-logind<br />
	[  672.780831] [    544]   100   544     1414       50        6       44         0    53248       32             0 avahi-daemon<br />
	[  672.787179] [    735]     0   735     4358      114       64       50         0    77824      224             0 wpa_supplicant<br />
	[  672.788241] [    787]     0   787     2701       62        0       62         0    49152       32             0 agetty<br />
	[  672.789295] [    788]     0   788     3775       58        0       58         0    65536      128             0 login<br />
	[  672.790457] [    797]     0   797     2863      115       64       51         0    57344      224         -1000 sshd<br />
	[  672.793417] [   1322]  1000  1322     5625       72       32       40         0    81920      512           100 systemd<br />
	[  672.794428] [   1324]  1000  1324     5942       63        2       61         0    77824      384           100 (sd-pam)<br />
	[  672.795407] [   1333]  1000  1333     3109      422      416        6         0    61440      288             0 bash<br />
	[  672.796355] [   1510]     0  1510     5345      186      128       58         0    90112      288             0 sshd-session<br />
	[  672.798743] [   1514]     0  1514     5346      466      416       50         0    77824       32             0 sshd-session<br />
	[  672.804912] [   1928]  1000  1928     5375      211      164       47         0    90112      352             0 sshd-session<br />
	[  672.806021] [   1929]  1000  1929     5410      449      359       90         0    81920      128             0 sshd-session<br />
	[  672.813315] [   1930]  1000  1930      605       75        0       75         0    45056       32             0 sftp-server<br />
	[  672.814361] [   1931]  1000  1931     3042      103       32       71         0    53248      544             0 bash<br />
	[  672.815311] [   2008]  1000  2008     8691       64       64        0         0   106496      384             0 passmark<br />
	[  672.816290] [   2023]  1000  2023    35734    15887    15887        0         0   315392    11584             0 passmark<br />
	[  672.827360] [   2024]  1000  2024    31575     7416     7416        0         0   278528    15904             0 passmark<br />
	[  672.828805] [   2025]  1000  2025    35734    17441    17441        0         0   315392    10016             0 passmark<br />
	[  672.831389] [   2026]  1000  2026    31839     7873     7864        9         0   282624    15680             0 passmark<br />
	[  672.832430] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-8.scope,task=passmark,pid=2023,uid=1000<br />
	[  672.834281] Out of memory: Killed process 2023 (passmark) total-vm:142936kB, anon-rss:63548kB, file-rss:0kB, shmem-rss:0kB, UID:1000 pgtables:308kB oom_score_adj:0<br />
	[  673.170919] systemd-journald[388]: Under memory pressure, flushing caches.<br />
	pi@Pi-s:~$<br />
	pi@Pi-s:~$<br />
	pi@Pi-s:~$<br />
	[ 1406.871962] systemd-journald[388]: Under memory pressure, flushing caches.<br />
	pi@Pi-s:~$ [ 1686.724826] systemd-journald[388]: Under memory pressure, flushing caches.<br />
	[ 2073.973035] systemd-resolve invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0<br />
	[ 2073.975522] CPU: 2 UID: 990 PID: 233 Comm: systemd-resolve Not tainted 6.12.58-current-rockchip64 #3<br />
	[ 2073.975558] Hardware name: Radxa ROCK Pi S (DT)<br />
	[ 2073.975564] Call trace:<br />
	[ 2073.975569]  dump_backtrace+0x94/0x114<br />
	[ 2073.975591]  show_stack+0x18/0x24<br />
	[ 2073.975600]  dump_stack_lvl+0x78/0x90<br />
	[ 2073.975612]  dump_stack+0x18/0x24<br />
	[ 2073.975620]  dump_header+0x40/0x1a8<br />
	[ 2073.975634]  oom_kill_process+0x130/0x358<br />
	[ 2073.975645]  out_of_memory+0xdc/0x568<br />
	[ 2073.975656]  __alloc_pages_noprof+0xcbc/0xdcc<br />
	[ 2073.975671]  alloc_pages_mpol_noprof+0x88/0x23c<br />
	[ 2073.975681]  alloc_pages_noprof+0x48/0xc0<br />
	[ 2073.975689]  folio_alloc_noprof+0x14/0x64<br />
	[ 2073.975697]  filemap_alloc_folio_noprof+0x140/0x154<br />
	[ 2073.975707]  __filemap_get_folio+0x208/0x394<br />
	[ 2073.975717]  filemap_fault+0x54c/0x858<br />
	[ 2073.975727]  __do_fault+0x3c/0x134<br />
	[ 2073.975740]  __handle_mm_fault+0x9e4/0x17cc<br />
	[ 2073.975749]  handle_mm_fault+0xe8/0x2e4<br />
	[ 2073.975758]  do_page_fault+0x100/0x58c<br />
	[ 2073.975769]  do_translation_fault+0xac/0xc8<br />
	[ 2073.975778]  do_mem_abort+0x44/0x94<br />
	[ 2073.975790]  el0_da+0x2c/0x9c<br />
	[ 2073.975800]  el0t_64_sync_handler+0xe4/0x158<br />
	[ 2073.975809]  el0t_64_sync+0x190/0x194<br />
	[ 2073.975821] Mem-Info:<br />
	[ 2073.988269] active_anon:20576 inactive_anon:36197 isolated_anon:0<br />
	[ 2073.988269]  active_file:35 inactive_file:317 isolated_file:0<br />
	[ 2073.988269]  unevictable:0 dirty:0 writeback:0<br />
	[ 2073.988269]  slab_reclaimable:3159 slab_unreclaimable:8656<br />
	[ 2073.988269]  mapped:132 shmem:61 pagetables:814<br />
	[ 2073.988269]  sec_pagetables:0 bounce:0<br />
	[ 2073.988269]  kernel_misc_reclaimable:0<br />
	[ 2073.988269]  free:2209 free_pcp:8 free_cma:0<br />
	[ 2073.995887] Node 0 active_anon:147140kB inactive_anon:79952kB active_file:328kB inactive_file:1060kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:524kB dirty:0kB writeback:0kB shmem:244kB shmem_thp:0kB shmem_pmdmapped:0kB anon_thp:0kB writeback_tmp:0kB kernel_stack:2208kB pagetables:3256kB sec_pagetables:0kB all_unreclaimable? no<br />
	[ 2073.999317] Node 0 DMA free:8424kB boost:0kB min:2684kB low:3352kB high:4020kB reserved_highatomic:0KB active_anon:146860kB inactive_anon:80232kB active_file:100kB inactive_file:1224kB unevictable:0kB writepending:0kB present:522240kB managed:477808kB mlocked:0kB bounce:0kB free_pcp:492kB local_pcp:64kB free_cma:72kB<br />
	[ 2074.004391] lowmem_reserve[]: 0 0 0 0<br />
	[ 2074.004781] Node 0 DMA: 8*4kB (U) 282*8kB (UE) 137*16kB (UE) 57*32kB (UE) 16*64kB (UE) 4*128kB (E) 1*256kB (E) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 8096kB<br />
	[ 2074.006154] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB<br />
	[ 2074.006944] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=32768kB<br />
	[ 2074.007692] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB<br />
	[ 2074.008434] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=64kB<br />
	[ 2074.009158] 1165 total pagecache pages<br />
	[ 2074.009493] 727 pages in swap cache<br />
	[ 2074.010642] Free swap  = 232kB<br />
	[ 2074.010949] Total swap = 238900kB<br />
	[ 2074.011247] 130560 pages RAM<br />
	[ 2074.011508] 0 pages HighMem/MovableOnly<br />
	[ 2074.011847] 11108 pages reserved<br />
	[ 2074.012135] 4096 pages cma reserved<br />
	[ 2074.012444] Tasks state (memory values in pages):<br />
	[ 2074.012859] [  pid  ]   uid  tgid total_vm      rss rss_anon rss_file rss_shmem pgtables_bytes swapents oom_score_adj name<br />
	[ 2074.015540] [    233]   990   233     5918       65       64        1         0    94208      640             0 systemd-resolve<br />
	[ 2074.016593] [    234]   988   234    23036       23        0       23         0    81920      256             0 systemd-timesyn<br />
	[ 2074.017652] [    242]     0   242     8713      162      128       34         0    86016      370         -1000 systemd-udevd<br />
	[ 2074.018665] [    264]   998   264     6903      174       64      110         0    90112      320             0 systemd-network<br />
	[ 2074.019686] [    369]     0   369     4570       39       32        7         0    77824      384             0 wpa_supplicant<br />
	[ 2074.020739] [    388]     0   388     6793      176       96       13        67    81920      192          -250 systemd-journal<br />
	[ 2074.021841] [    484]   100   484     1445       52       32       20         0    53248       32             0 avahi-daemon<br />
	[ 2074.022857] [    488]     0   488     2520       32       32        0         0    49152       32             0 cron<br />
	[ 2074.023800] [    491]   996   491     2064      110       64       46         0    53248      128          -900 dbus-daemon<br />
	[ 2074.024797] [    518]     0   518    55049      115       96       19         0    73728       96             0 rsyslogd<br />
	[ 2074.025805] [    519]     0   519     4642       65       32       33         0    77824      224             0 systemd-logind<br />
	[ 2074.026837] [    544]   100   544     1414       50        6       44         0    53248       32             0 avahi-daemon<br />
	[ 2074.027842] [    735]     0   735     4358       64       64        0         0    77824      224             0 wpa_supplicant<br />
	[ 2074.028858] [    787]     0   787     2701       62        0       62         0    49152       32             0 agetty<br />
	[ 2074.031960] [    788]     0   788     3775       58        0       58         0    65536      128             0 login<br />
	[ 2074.033044] [    797]     0   797     2863      115       64       51         0    57344      224         -1000 sshd<br />
	[ 2074.034056] [   1322]  1000  1322     5625       72       32       40         0    81920      512           100 systemd<br />
	[ 2074.035032] [   1324]  1000  1324     5942       63        2       61         0    77824      384           100 (sd-pam)<br />
	[ 2074.035999] [   1333]  1000  1333     3109      453      416       37         0    61440      288             0 bash<br />
	[ 2074.036933] [   1510]     0  1510     5345       90       32       58         0    90112      352             0 sshd-session<br />
	[ 2074.038232] [   1514]     0  1514     5346      466      416       50         0    77824       32             0 sshd-session<br />
	[ 2074.039257] [   1928]  1000  1928     5375      115       68       47         0    90112      416             0 sshd-session<br />
	[ 2074.040253] [   1929]  1000  1929     5410      449      359       90         0    81920      128             0 sshd-session<br />
	[ 2074.041245] [   1930]  1000  1930      605       75        0       75         0    45056       32             0 sftp-server<br />
	[ 2074.042259] [   1931]  1000  1931     3042      103       32       71         0    53248      544             0 bash<br />
	[ 2074.043190] [   2008]  1000  2008     8691       78       64       14         0   106496      384             0 passmark<br />
	[ 2074.044364] [   2024]  1000  2024    41346    18840    18840        0         0   360448    14272             0 passmark<br />
	[ 2074.045725] [   2025]  1000  2025    47783    14691    14657       34         0   413696    24832             0 passmark<br />
	[ 2074.047090] [   2026]  1000  2026    43327    20702    20664       38         0   376832    14400             0 passmark<br />
	[ 2074.048376] [   2036]     0  2036     2632       63       32       31         0    49152       37             0 cron<br />
	[ 2074.049351] [   2044]     0  2044     2632        2        0        2         0    49152       37             0 cron<br />
	[ 2074.050395] [   2053]     0  2053     2520       47        0       47         0    45056       37             0 cron<br />
	[ 2074.051675] [   2054]     0  2054     2520        1        0        1         0    45056       37             0 cron<br />
	[ 2074.052650] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/user.slice/user-1000.slice/session-8.scope,task=passmark,pid=2025,uid=1000<br />
	[ 2074.054345] Out of memory: Killed process 2025 (passmark) total-vm:191132kB, anon-rss:58628kB, file-rss:136kB, shmem-rss:0kB, UID:1000 pgtables:404kB oom_score_adj:0<br />
	[ 2074.573529] systemd-journald[388]: Under memory pressure, flushing caches.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	==== passmark frozen also (run from ssh)==========
</p>

<p>
	                   PassMark PerformanceTest Linux (11.0.1004)
</p>

<p>
	Radxa ROCK Pi S<br />
	Cortex-A35 (aarch64)<br />
	4 cores @ 1296 MHz  |  466 MiB RAM<br />
	Number of Processes: 4  |  Test Iterations: 1  |  Test Duration: Medium<br />
	--------------------------------------------------------------------------------<br />
	CPU Mark:                          Incomplete<br />
	  Integer Math                     0.0 Million Operations/s<br />
	  Floating Point Math              0.0 Million Operations/s<br />
	  Prime Numbers                    0.0 Million Primes/s<br />
	  Sorting                          0.0 Thousand Strings/s<br />
	  Encryption                       0.0 MB/s<br />
	  Compression                      0.0 KB/s<br />
	  CPU Single Threaded              0.0 Million Operations/s<br />
	  Physics                          0.0 Frames/s<br />
	  Extended Instructions (NEON)     0.0 Million Matrices/s
</p>

<p>
	Memory Mark:                       Incomplete<br />
	  Database Operations              Running (1/1)<br />
	  Memory Read Cached               Queued<br />
	  Memory Read Uncached             Queued<br />
	  Memory Write                     Queued<br />
	  Available RAM                    Queued<br />
	  Memory Latency                   Queued<br />
	  Memory Threaded                  Queued<br />
	--------------------------------------------------------------------------------
</p>

<p>
	Results not submitted
</p>

<p>
	<br />
	Use ESC or CTRL-C to exit<br />
	A: Run All Tests   <span class="ipsEmoji">😄</span> Run CPU Tests   M: Run Memory Tests   U: Upload Test Results<br />
	 
</p>
]]></description><guid isPermaLink="false">57281</guid><pubDate>Wed, 07 Jan 2026 21:50:17 +0000</pubDate></item><item><title>Can't get SPI interface</title><link>https://forum.armbian.com/topic/40816-cant-get-spi-interface/</link><description><![CDATA[<p>
	Hello everybody! I need help: I can't turn on the SPI interface in any way so that /dev/spidev0 or /dev/spidev1 appears. In armbian-config, there are generally only 7 lines in the hardware section, in which there is nothing interesting, an attempt to register spidev in armbianEnv.txt it also does not help, in dmesg and journalctl - silence... Where did the interface go?<img alt="2024-06-0713-29-11.png.ad789c52c112b974429e75ee5713f4b8.png" class="ipsImage ipsImage_thumbnailed" data-fileid="12616" data-ratio="102.39" width="418" src="https://forum.armbian.com/uploads/monthly_2024_06/2024-06-0713-29-11.png.ad789c52c112b974429e75ee5713f4b8.png" />
</p>
]]></description><guid isPermaLink="false">40816</guid><pubDate>Fri, 07 Jun 2024 06:33:38 +0000</pubDate></item><item><title>Rock Pi S no CLK signal on SPI1</title><link>https://forum.armbian.com/topic/50265-rock-pi-s-no-clk-signal-on-spi1/</link><description><![CDATA[<p>
	I am experiencing an issue with my Rock Pi S. When using SPI1, I am not observing any CLK output signal on pin GPIO3_B3, which I have verified with an oscilloscope. Other signals such as MOSI, MISO, and CS are functioning correctly. I have found that this issue does not occur in the older kernel 4.4.143-65-rockchip-g58431d38f8f3. However, when using the latest Armbian 25.2.2 Bookworm Minimal / IOT image, this problem arises. Could someone please assist me in resolving this problem?
</p>
]]></description><guid isPermaLink="false">50265</guid><pubDate>Wed, 05 Mar 2025 12:44:58 +0000</pubDate></item><item><title>RockPi S f2fs install issue</title><link>https://forum.armbian.com/topic/55587-rockpi-s-f2fs-install-issue/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	Stock image from armbian.com; Armbian_25.8.1_Rockpi-s_trixie_current_6.12.41_minimal.img
</p>

<p>
	Here is the armbianmonitor's output: <a href="https://paste.armbian.com/ikodekuzel" rel="external nofollow">https://paste.armbian.com/ikodekuzel</a>
</p>

<p>
	 
</p>

<p>
	The error might be caused by the absence of the f2fs package in the image.
</p>

<p>
	 
</p>

<p>
	root@rockpi-s:~# armbian-install 
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Select filesystem type for eMMC /dev/mmcblk0
2  f2fs 
</span><span class="tag">&lt;OK&gt;</span><span class="pln">

Formating /dev/mmcblk0 to f2fs ... please wait.  

Error: Filesystem tools for f2fs not installed, exiting


root@rockpi-s:~# find / -type f -name f2fs*
root@rockpi-s:~# </span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">55587</guid><pubDate>Wed, 08 Oct 2025 15:29:59 +0000</pubDate></item><item><title>RockPi S Ethernet 10mbps not working</title><link>https://forum.armbian.com/topic/30235-rockpi-s-ethernet-10mbps-not-working/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	I’m trying to get a RockPi S connected by a slow ethernet connection with 10mbps (half or full duplex) but it doesn’t seem to work. If I test with a 100mbps connection, everything works fine and as expected.<br />
	Using 10mbps, it seems to look fine, e.g. ethtool shows a link with 10mpbs, advertised modes look fine but the RockPi S doesn’t even retrieve an IP via DHCP. If configuring a static IP, no ping to any address beside the own IP address is possible.<br />
	I’m using latest debian-based armbian 23.8.1 stable and performed apt-get update &amp; upgrade.
</p>

<p>
	Anyone encountered the same problem and has some hints?<br />
	Unfortunately I’m not a linux pro so unfortunately I’m a bit stuck but I’m happy to provide any missing information or execute commands on the RockPi S and post the results here.
</p>

<p>
	Cheers
</p>
]]></description><guid isPermaLink="false">30235</guid><pubDate>Fri, 15 Sep 2023 14:41:18 +0000</pubDate></item><item><title>Self-build minimal image for RockPI-S too big</title><link>https://forum.armbian.com/topic/54483-self-build-minimal-image-for-rockpi-s-too-big/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	trying to get a bit deeper into Armbian, I tried to create my own minimal Trixie-based image for the RockPI-S. I'm using a Ubuntu Noble VM and I managed to run a successfull build following the quick start guide.
</p>

<p>
	However, creating an image using
</p>

<pre class="ipsCode">./compile.sh build BOARD=rockpi-s BRANCH=current BUILD_MINIMAL=yes KERNEL_CONFIGURE=no RELEASE=trixie </pre>

<p>
	leads to an image with a size around 1.5GB. Compared to the downloadable minimal images, which have 200MB-300MB, this is quite large.
</p>

<p>
	 
</p>

<p>
	Does anyone has any hints on how to proceed in order to self-build images comparable to the ones offered for download?
</p>

<p>
	 
</p>

<p>
	Cheers,
</p>
]]></description><guid isPermaLink="false">54483</guid><pubDate>Thu, 14 Aug 2025 22:55:53 +0000</pubDate></item><item><title>How to change the LED0 behaviour of RTL8201F PHY</title><link>https://forum.armbian.com/topic/54536-how-to-change-the-led0-behaviour-of-rtl8201f-phy/</link><description><![CDATA[<p>
	Hello!
</p>

<p>
	 
</p>

<p>
	Is there a possibility to change the default LED0 behaviour of the RTL8201F PHY?<br />
	Here is the Datasheet: <a href="https://file.elecfans.com/web1/M00/99/0F/o4YBAF0VytaAI7ezABH66fmIRIg854.pdf?filename=RTL8201F-VB-CG.pdf" rel="external nofollow">https://file.elecfans.com/web1/M00/99/0F/o4YBAF0VytaAI7ezABH66fmIRIg854.pdf?filename=RTL8201F-VB-CG.pdf</a>
</p>

<p>
	 
</p>

<p>
	And this is the relevant register:
</p>

<p>
	 
</p>

<p>
	<img alt="image.png.7aab0a3a9c81e98082a5f89be139a73b.png" class="ipsImage ipsImage_thumbnailed" data-fileid="14963" data-ratio="20.33" width="846" src="https://forum.armbian.com/uploads/monthly_2025_08/image.png.7aab0a3a9c81e98082a5f89be139a73b.png" />
</p>

<p>
	 
</p>

<p>
	It states, that "11" is the default - but I think it is changed to "00" during driver initialization - is that possible?<br />
	<br />
	I would like to change it to "01" - is this somehow possible without recompiling the driver?
</p>

<p>
	 
</p>

<p>
	Thank you!<br />
	Best regards,
</p>

<p>
	Manuel
</p>
]]></description><guid isPermaLink="false">54536</guid><pubDate>Sat, 16 Aug 2025 18:51:30 +0000</pubDate></item><item><title>Overlays do not apply even when selected in armbian-config and then rebooting</title><link>https://forum.armbian.com/topic/47793-overlays-do-not-apply-even-when-selected-in-armbian-config-and-then-rebooting/</link><description><![CDATA[<pre class="ipsCode">armbianmonitor -u</pre>

<p>
	<a href="https://paste.next.armbian.com/hoyonuruye" rel="external nofollow">https://paste.next.armbian.com/hoyonuruye</a>
</p>

<p>
	 
</p>

<p>
	I installed the newest fresh debian minimal image for the RockPi-S and no matter what I do overlays do not apply.
</p>

<p>
	I've followed
</p>
<iframe allowfullscreen="" data-controller="core.front.core.autosizeiframe" data-embedauthorid="207777" data-embedcontent="" data-embedid="embed5843930203" src="https://forum.armbian.com/topic/40816-cant-get-spi-interface/?do=embed" style="height:394px;max-width:502px;"></iframe>

<p>
	and compiled spi1 and spi2 rk3308. I've also tested the external antenna device tree as I have installed an external antenna:
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="13577" data-ratio="86.26" width="444" alt="image.png.4a4d2beb12605045c4301f2bf5031e61.png" src="https://forum.armbian.com/uploads/monthly_2024_11/image.png.4a4d2beb12605045c4301f2bf5031e61.png" />
</p>

<p>
	 
</p>

<p>
	However neither the external antenna is being used nor spidev are present.<br />
	I have diffed
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">dtc -I fs -O dts /proc/device-tree</span></pre>

<p>
	and they are identical before and after enabling the overlays in armbian-config and rebooting.
</p>

<p>
	 
</p>

<p>
	I was able to confirm the "overlays" work by manually copypasting their changes in linux's source <abbr title="Device tree source">dts</abbr> and generating a patch file, placing it in armbian's linux patch folder and recompiling from scratch, so if I do change the options spidev works, just I somehow can only do this by editing the source.
</p>

<p>
	 
</p>

<p>
	Here is the `/boot/armbianEnv.txt` file generated:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">verbosity=1
bootlogo=false
console=serial
overlay_prefix=rk3308
fdtfile=rockchip/rk3308-rock-pi-s.dtb
extraargs=cma=16M
rootdev=UUID=036c1484-611d-470e-b2ef-775fe550149b
rootfstype=ext4
fdt_overlays=rk3308-s0-ext-antenna rk3308-spi1-spidev rk3308-spi2-spidev
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u</span></pre>

<p>
	Also after editing the overlays in armbian-config this error pops up:
</p>

<pre class="ipsCode">/boot/armbianEnv.txt: line 9: rk3308-spi1-spidev: command not found</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">47793</guid><pubDate>Sat, 30 Nov 2024 21:22:50 +0000</pubDate></item><item><title>No Audio on Kernel: 6.12.15 and Armbian 25.2.2 Bookworm Minimal</title><link>https://forum.armbian.com/topic/51825-no-audio-on-kernel-61215-and-armbian-2522-bookworm-minimal/</link><description><![CDATA[<p>
	Hello again,<br />
	 
</p>

<p>
	We're already aware of the existing issues with kernel 6 and the audio on the RK3308B. In this case, it fails again in the latest versions... Alsamixer detects the audio card and even shows it in arecord -L or arecord -l, but when trying to record, the error appears:<br />
	 
</p>

<p>
	<strong>"arecord: set_params:1416: unable to install hw params"</strong><br />
	 
</p>

<p>
	The command applied is:
</p>

<p>
	<strong>arecord -c 2 -r 192000 -f S32_LE test.wav</strong><br />
	 
</p>

<p>
	Although if I leave it without parameters to see what it does, it throws the same error, even if I specify the hardware... In the previous kernel (I think it was <strong>6.12.11</strong> (with the u-boot issue in the previous post), the audio worked perfectly).<br />
	<br />
	Thanks for all.
</p>
]]></description><guid isPermaLink="false">51825</guid><pubDate>Wed, 07 May 2025 09:24:07 +0000</pubDate></item><item><title>Audio no longer works after updating to Armbian 24.8.2</title><link>https://forum.armbian.com/topic/45295-audio-no-longer-works-after-updating-to-armbian-2482/</link><description><![CDATA[<p>
	I've been using a few Rock Pi S devices as <a href="https://github.com/badaix/snapcast" rel="external nofollow">snapcast</a> clients and after updating them to Armbian 24.8.2 audio does not work anymore.
</p>

<p>
	 
</p>

<p>
	This seems similar to <a href="https://forum.armbian.com/topic/27626-audio-broken-on-current-builds-2302-jammy/" rel="">this old post</a> (<a href="https://github.com/armbian/build/pull/5088" rel="external nofollow">fix PR</a>).
</p>

<p>
	 
</p>

<p>
	Also, <a href="https://github.com/armbian/build/pull/6886" rel="external nofollow">this PR</a> may be a relevant to the issue.
</p>

<p>
	 
</p>

<p>
	<a href="https://paste.armbian.com/aziwayelen" rel="external nofollow">https://paste.armbian.com/aziwayelen</a>
</p>

<p>
	 
</p>

<pre class="ipsCode">$ snapclient --host [REDACTED]
2024-09-17 09-28-10.435 [Error] (Snapclient) PCM device "default" not found
2024-09-17 09-28-10.436 [Info] (Snapclient) Version 0.26.0
2024-09-17 09-28-10.437 [Info] (Connection) Resolving host IP for: [REDACTED]
2024-09-17 09-28-10.440 [Info] (Connection) Connecting
2024-09-17 09-28-10.442 [Notice] (Connection) Connected to 192.168.0.100
2024-09-17 09-28-10.442 [Info] (Connection) My MAC: "42:00:00:00:80:30", socket: 8
2024-09-17 09-28-10.518 [Info] (Controller) ServerSettings - buffer: 1000, latency: 0, volume: 75, muted: 0
2024-09-17 09-28-10.519 [Info] (Controller) Codec: flac, sampleformat: 48000:16:2
2024-09-17 09-28-10.520 [Info] (Player) Player name: alsa, device: default, description: &lt;none&gt;, idx: -1, sharing mode: unspecified, parameters: &lt;none&gt;
2024-09-17 09-28-10.520 [Info] (Player) Mixer mode: software, parameters: &lt;none&gt;
2024-09-17 09-28-10.520 [Info] (Player) Sampleformat: 48000:16:2, stream: 48000:16:2
2024-09-17 09-28-10.520 [Info] (Alsa) Using default buffer_time: 80 ms, default fragments: 4
ALSA lib confmisc.c:855:(parse_card) cannot find card '0'
ALSA lib conf.c:5180:(_snd_config_evaluate) function snd_func_card_inum returned error: No such file or directory
ALSA lib confmisc.c:422:(snd_func_concat) error evaluating strings
ALSA lib conf.c:5180:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1334:(snd_func_refer) error evaluating name
ALSA lib conf.c:5180:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5703:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2666:(snd_pcm_open_noupdate) Unknown PCM default
2024-09-17 09-28-10.528 [Error] (Alsa) Exception: Can't open default, error: No such file or directory, code: -2
2024-09-17 09-28-10.530 [Fatal] (Snapclient) Exception: Can't open default, error: No such file or directory
2024-09-17 09-28-10.530 [Notice] (Snapclient) Snapclient terminated.</pre>

<p>
	 
</p>

<pre class="ipsCode">$ aplay -l
aplay: device_list:274: no soundcards found...</pre>

<p>
	 
</p>

<p>
	When following the <a href="https://wiki.radxa.com/ROCKPI_S_PoE_HAT#Usage_of_Headphone_jack" rel="external nofollow">instructions on the official wiki to enable the audio jack</a> I get a `Permission denied` error echoing a value to the `/sys/class/<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>/export` (but not gpio15).
</p>

<p>
	 
</p>

<pre class="ipsCode">$ sudo echo 15 &gt; /sys/class/gpio/export
-bash: /sys/class/gpio/export: Permission denied

$ sudo cat /sys/class/gpio/export 
cat: /sys/class/gpio/export: Permission denied

$ ls -Al /sys/class/gpio/
total 0
--w------- 1 root root 4096 Sep 17 09:16 export
lrwxrwxrwx 1 root root    0 Sep 17 09:16 gpio15 -&gt; ../../devices/platform/pinctrl/ff220000.gpio/gpiochip0/gpio/gpio15
lrwxrwxrwx 1 root root    0 Dec 31  1969 gpiochip0 -&gt; ../../devices/platform/pinctrl/ff220000.gpio/gpio/gpiochip0
lrwxrwxrwx 1 root root    0 Dec 31  1969 gpiochip128 -&gt; ../../devices/platform/pinctrl/ff260000.gpio/gpio/gpiochip128
lrwxrwxrwx 1 root root    0 Dec 31  1969 gpiochip32 -&gt; ../../devices/platform/pinctrl/ff230000.gpio/gpio/gpiochip32
lrwxrwxrwx 1 root root    0 Dec 31  1969 gpiochip64 -&gt; ../../devices/platform/pinctrl/ff240000.gpio/gpio/gpiochip64
lrwxrwxrwx 1 root root    0 Dec 31  1969 gpiochip96 -&gt; ../../devices/platform/pinctrl/ff250000.gpio/gpio/gpiochip96
--w------- 1 root root 4096 Sep 17 09:36 unexport</pre>
]]></description><guid isPermaLink="false">45295</guid><pubDate>Tue, 17 Sep 2024 16:40:09 +0000</pubDate></item><item><title>Rock Pi S - Audio Support</title><link>https://forum.armbian.com/topic/30655-rock-pi-s-audio-support/</link><description><![CDATA[<p>
	Hi everyone!
</p>

<p>
	 
</p>

<p>
	I am struggling with audio input.
</p>

<p>
	 
</p>

<p>
	Output audio from LINEOUT pins works fine out-of-the-box!
</p>

<p>
	 
</p>

<p>
	What about the audio input?<br />
	To begin with I have tested the arecord command with these error messages…
</p>

<p>
	 
</p>

<p>
	TEST 1
</p>

<p>
	root@rockpi-s:~# arecord -f S16_LE -d 10 -r 16000 --device=“hw:0,0” test-mic.wav<br />
	Recording WAVE ‘test-mic.wav’ : Signed 16 bit Little Endian, Rate 16000 Hz, Mono<br />
	arecord: set_params:1358: Channels count non available
</p>

<p>
	 
</p>

<p>
	TEST 2
</p>

<p>
	root@rockpi-s:~# arecord -f S16_LE -c 2 -d 10 -r 16000 --device=“hw:0,0” test-mic.wav<br />
	Recording WAVE ‘test-mic.wav’ : Signed 16 bit Little Endian, Rate 16000 Hz, Stereo<br />
	arecord: set_params:1416: Unable to install hw params:<br />
	ACCESS: RW_INTERLEAVED<br />
	FORMAT: S16_LE<br />
	SUBFORMAT: STD<br />
	SAMPLE_BITS: 16<br />
	FRAME_BITS: 32<br />
	CHANNELS: 2<br />
	RATE: 16000<br />
	PERIOD_TIME: 125000<br />
	PERIOD_SIZE: 2000<br />
	PERIOD_BYTES: 8000<br />
	PERIODS: 4<br />
	BUFFER_TIME: 500000<br />
	BUFFER_SIZE: 8000<br />
	BUFFER_BYTES: 32000<br />
	TICK_TIME: 0
</p>

<p>
	 
</p>

<p>
	Any suggestions?
</p>
]]></description><guid isPermaLink="false">30655</guid><pubDate>Mon, 09 Oct 2023 10:53:27 +0000</pubDate></item><item><title>How to change ethernet MAC address on image?</title><link>https://forum.armbian.com/topic/42663-how-to-change-ethernet-mac-address-on-image/</link><description><![CDATA[<p>
	I have installed Armbian on my Rock Pi S, done some setup, and then taken an image of the disk to be duplicated to other devices.<br />
	The problem is that each of these devices get the same permanent MAC address on the ethernet port as the first device. I don't know how Armbian gets the MAC address from the interface but it doesn't seem to depend on unique hardware, or if it does then the hardware ID isn't actually unique between boards.
</p>

<p>
	This leads to problems because my device is meant to be used several in the same network, causing collisions in DHCP assignment etc.
</p>

<p>
	 
</p>

<p>
	I have tried multiple workarounds and none have worked well. I tried spoofing the MAC addr by changing the cloned-mac-address setting in NetworkManager. This worked at changing the MAC address, however it caused an entirely different problem, namely that a fallback connection with a link-local address never gets activated. It previously worked but after changing only this setting, it no longer works. I have no idea why but I have tried for days now to fix this issue and I'm out of new ideas.
</p>

<p>
	 
</p>

<p>
	The other thing I tried was adding ethaddr=[some mac address] in the armbianEnv.txt file, as found in another forum thread. This didn't seem to do anything, the same duplicate MAC address was still used.
</p>

<p>
	 
</p>

<p>
	I also tried using macchanger, but it was difficult to get to work nicely with NetworkManager, I don't think this is a good solution...
</p>

<p>
	 
</p>

<p>
	What else can I try?
</p>
]]></description><guid isPermaLink="false">42663</guid><pubDate>Fri, 19 Jul 2024 11:34:16 +0000</pubDate></item><item><title>USB OTG Networking</title><link>https://forum.armbian.com/topic/50799-usb-otg-networking/</link><description><![CDATA[<p>
	I haven't been able to find a step-by-step for enabling a USB OTG Network on the RockPi-S. Anyone have a link to the steps?
</p>

<p>
	 
</p>

<p>
	I'm referring to the ability to connect a USB cable between the RockPi-S and a computer and be able to ssh or network to it.
</p>

<p>
	My usb port is in peripheral mode and I'm using Network Manager on Armbian Bookworm.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">50799</guid><pubDate>Sat, 29 Mar 2025 21:00:51 +0000</pubDate></item><item><title><![CDATA[Rockpi-S no longer boots with latest Armbian > 24.11.1]]></title><link>https://forum.armbian.com/topic/49744-rockpi-s-no-longer-boots-with-latest-armbian-24111/</link><description><![CDATA[<p>
	Been using 24.11.1 Bookworm for a while, but yesterday did an apt update &amp;&amp; apt upgrade, only to find that the resulting image would no longer boot.
</p>

<p>
	No "activity" light at all on the front on reboot.
</p>

<p>
	Downloaded 25.5.0 Trixie "just to see", but it doesn't boot either.
</p>

<p>
	 
</p>

<p>
	What happened after 24.11.4? Is there something different I should be doing if I want to run a later version of Armbian?
</p>
]]></description><guid isPermaLink="false">49744</guid><pubDate>Mon, 10 Feb 2025 16:39:49 +0000</pubDate></item><item><title>Apt Upgrade causes Rock Pi S not to boot [Armbian 24.11.1]</title><link>https://forum.armbian.com/topic/49377-apt-upgrade-causes-rock-pi-s-not-to-boot-armbian-24111/</link><description><![CDATA[<p>
	Hi everyone,<br />
	 
</p>

<p>
	I've been working with Armbian for a while on my Rock Pi S, I got to a stable situation on version 24.11.1 with kernel 6.6.63 where everything worked perfectly... but recently this last week I applied an <strong>apt upgrade</strong>, which applied strong base modifications <strong>(linux-current-rockchip64 and dtbo going from 24.11.1 to 24.11.3)</strong>, after applying this update and rebooting, I can't get it to boot again, either from the Micro SD or from the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> installation.
</p>

<p>
	<br />
	I wanted to report this bug, but I don't have a TTL cable at hand to be able to do the corresponding debugging...
</p>

<p>
	<br />
	I've tried to flash older versions, or even flash the 24.11.1 version again but<a href="https://forum.armbian.com/topic/45295-audio-no-longer-works-after-updating-to-armbian-2482/" rel=""> I need the audio fix for kernel 6.6.63</a>, which doesn't apply after the last upgrade coincidentally.
</p>

<p>
	<br />
	For work reasons I need to get this <abbr title="Single board computer"><abbr title="Single board computer">SBC</abbr></abbr> up and running...
</p>

<p>
	<br />
	Any solution for this?<br />
	<br />
	Thanks for all.
</p>
]]></description><guid isPermaLink="false">49377</guid><pubDate>Sun, 19 Jan 2025 02:56:32 +0000</pubDate></item><item><title>ROCK Pi S does not boot</title><link>https://forum.armbian.com/topic/29886-rock-pi-s-does-not-boot/</link><description><![CDATA[<p>
	None of the images from <a href="https://www.armbian.com/rockpi-s/" rel="external nofollow">https://www.armbian.com/rockpi-s/</a> work (neither minimal nor cli).
</p>

<p>
	I tried writing minimal image onto SD <abbr title="A type of flash memory">NAND</abbr> and tried booting both cli and minimal from SD card.
</p>

<p>
	 
</p>

<p>
	I tried 2 different SD cards too.
</p>

<p>
	 
</p>

<p>
	Board was connected through UART0 to PC and while I get output when I use rkdeveloptool, there is no output when trying to boot normally.
</p>

<p>
	 
</p>

<p>
	However, latest image from <a href="https://github.com/radxa/rock-pi-s-images-released/releases" rel="external nofollow">https://github.com/radxa/rock-pi-s-images-released/releases</a> works (rockpis_debian_buster_server_arm64_20210924_0412-gpt.img) does boot if I write it to SD <abbr title="A type of flash memory">NAND</abbr> or SD card.
</p>

<p>
	 
</p>

<p>
	I have V1.3 with RK3308 and 1GB SD <abbr title="A type of flash memory">NAND</abbr>.
</p>
]]></description><guid isPermaLink="false">29886</guid><pubDate>Tue, 29 Aug 2023 23:37:42 +0000</pubDate></item><item><title>armbian-install missing device names?</title><link>https://forum.armbian.com/topic/48208-armbian-install-missing-device-names/</link><description><![CDATA[<p>
	running 24.8.3, and Armbian-install's screen looks like this:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Current root: UUID=117b851b-2be0-4bb7-8572-7edce1ef7375
              SD card (/dev/mmcblk1)
1  Boot from SD - system on SATA, USB or NVMe
2  Boot from  - system on
3  Boot from  - system on SATA, USB or NVMe
5  Install/Update the bootloader on SD card (/dev/mmcblk1)</span></pre>

<p>
	 
</p>

<p>
	I have a µSD card inserted and a 4gb <abbr title="embedded MultiMediaCard">eMMC</abbr>, but it looks like the names of these devices are missing?
</p>
]]></description><guid isPermaLink="false">48208</guid><pubDate>Thu, 12 Dec 2024 20:17:38 +0000</pubDate></item><item><title>updating from 24.8.3 to 24.11.x no longer boots from &#xB5;SD card</title><link>https://forum.armbian.com/topic/48205-updating-from-2483-to-2411x-no-longer-boots-from-%C2%B5sd-card/</link><description><![CDATA[<p>
	Currently running 24.8.3 and have copied it to the <abbr title="embedded MultiMediaCard">eMMC</abbr>, working fine on both the µSD image and <abbr title="embedded MultiMediaCard">eMMC</abbr>.
</p>

<p>
	(On the Rock-Pi-S, if you have a bootable image on the µSD card, it boots from that. If not, it boots from the <abbr title="embedded MultiMediaCard">eMMC</abbr>.)
</p>

<p>
	 
</p>

<p>
	Today, running from the µSD, I did an apt update and apt upgrade, and it updated a few packages (here's the list):<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln"># apt list --upgradeable
Listing... Done
armbian-config/unknown 25.2.0-trunk.154.1212.080011 all [upgradable from: 24.11.1]
armbian-firmware/bookworm,bookworm 24.11.2 all [upgradable from: 24.11.1]
base-files/bookworm 24.11.2-12.4+deb12u8-bookworm arm64 [upgradable from: 24.11.1-12.4+deb12u8-bookworm]
linux-dtb-current-rockchip64/bookworm 24.11.1 arm64 [upgradable from: 24.11.1]
linux-image-current-rockchip64/bookworm 24.11.1 arm64 [upgradable from: 24.11.1]
tzdata/stable-updates 2024b-0+deb12u1 all [upgradable from: 2024a-0+deb12u1]</span></pre>

<p>
	 
</p>

<p>
	Now, it no longer boots from the µSD card. So I assume it's done something catastrophic to the image on that card?<br />
	 
</p>
]]></description><guid isPermaLink="false">48205</guid><pubDate>Thu, 12 Dec 2024 19:09:19 +0000</pubDate></item><item><title>armbianmonitor -u broken?</title><link>https://forum.armbian.com/topic/48284-armbianmonitor-u-broken/</link><description><![CDATA[<p>
	I get the following result when trying to run <strong>armbianmonitor -u</strong>. Is it broken or am I doing something wrong?
</p>

<p>
	Armbian 24.8.3 Bookworm CLI on a Rock-Pi S
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln"># armbianmonitor -u
Collecting info and sending to paste.armbian.com, wait...
/usr/bin/armbianmonitor: line 976: iostat: command not found
</span><span class="dec">&lt;!DOCTYPE html&gt;</span><span class="pln">
</span><span class="tag">&lt;html</span><span class="pln"> </span><span class="atn">lang</span><span class="pun">=</span><span class="atv">"en"</span><span class="tag">&gt;</span><span class="pln">
</span><span class="tag">&lt;head&gt;</span><span class="pln">
</span><span class="tag">&lt;meta</span><span class="pln"> </span><span class="atn">charset</span><span class="pun">=</span><span class="atv">"utf-8"</span><span class="tag">&gt;</span><span class="pln">
</span><span class="tag">&lt;title&gt;</span><span class="pln">Error</span><span class="tag">&lt;/title&gt;</span><span class="pln">
</span><span class="tag">&lt;/head&gt;</span><span class="pln">
</span><span class="tag">&lt;body&gt;</span><span class="pln">
</span><span class="tag">&lt;pre&gt;</span><span class="pln">Cannot POST /log</span><span class="tag">&lt;/pre&gt;</span><span class="pln">
</span><span class="tag">&lt;/body&gt;</span><span class="pln">
</span><span class="tag">&lt;/html&gt;</span><span class="pln">
Please post the URL in the forum where you've been asked for.</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">48284</guid><pubDate>Sat, 14 Dec 2024 15:54:32 +0000</pubDate></item><item><title>RockPi-S fails to reboot or halt/shutdown - kernel panic v1.3</title><link>https://forum.armbian.com/topic/33429-rockpi-s-fails-to-reboot-or-haltshutdown-kernel-panic-v13/</link><description><![CDATA[<p>
	On a fresh install from the website on kernel 6.1 bookworm/Jammy when rebooting the board a kernel panic occurs and the device will not boot unless power cycled. This was not the case even a few months ago on a 6.6 edge kernel. I also tried the current edge 6.7 kernel and the board wouldn't boot at all not that I expected it to. The board says 3308B on the chip(samsung memory) and ive also tried two different micro sd.
</p>

<p>
	 
</p>

<p>
	Anyone else having this issue?
</p>

<p>
	 
</p>

<p>
	Serial output is below of the relevant failure
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			[  OK  ] Reached target reboot.target - System Reboot.<br />
			[   95.928742] Unable to handle kernel NULL pointer dereference at virtual address 000000000000013c<br />
			[   95.929580] Mem abort info:<br />
			[   95.929842]   ESR = 0x0000000096000004<br />
			[   95.930191]   EC = 0x25: DABT (current EL), IL = 32 bits<br />
			[   95.930682]   SET = 0, FnV = 0<br />
			[   95.930969]   EA = 0, S1PTW = 0<br />
			[   95.931266]   FSC = 0x04: level 0 translation fault<br />
			[   95.931799] Data abort info:<br />
			[   95.932072]   ISV = 0, ISS = 0x00000004<br />
			[   95.932427]   CM = 0, WnR = 0<br />
			[   95.932709] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000003ea2000<br />
			[   95.933299] [000000000000013c] pgd=0000000000000000, p4d=0000000000000000<br />
			[   95.933944] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP<br />
			[   95.934521] Modules linked in: sunrpc lz4hc lz4 hci_uart btqca btrtl btbcm btintel snd_soc_pcm5102a snd_soc_rk3308 snd_soc_simple_card snd_soc_rockchip_i2s_tdm bluetooth snd_soc_simple_card_utils rockchip_rng rng_core rfkill snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm snd_timer snd soundcore cpufreq_dt zram binfmt_misc dm_mod ip_tables x_tables autofs4 realtek dwmac_rk stmmac_platform stmmac pcs_xpcs<br />
			[   95.938132] CPU: 3 PID: 1 Comm: systemd-shutdow Not tainted 6.1.63-current-rockchip64 #1<br />
			[   95.938873] Hardware name: Radxa ROCK Pi S (DT)<br />
			[   95.939293] pstate: 80000005 (Nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)<br />
			[   95.939937] pc : kobject_get+0x18/0xbc<br />
			[   95.940318] lr : device_shutdown+0xb4/0x260<br />
			[   95.940723] sp : ffff800009d2bc20<br />
			[   95.941032] x29: ffff800009d2bc20 x28: ffff000000588000 x27: 0000000000000000<br />
			[   95.941716] x26: ffff8000094fa130 x25: 0000000000000008 x24: ffff800009c61050<br />
			[   95.942396] x23: ffff000002c81090 x22: ffff800009cd3e18 x21: 0000000000000100<br />
			[   95.943076] x20: ffff000003b0b888 x19: 0000000000000100 x18: ffffffffffffffff<br />
			[   95.943758] x17: 000000040044ffff x16: 00100072b5503510 x15: 000000000013c680<br />
			[   95.944435] x14: 00000000000639c0 x13: ffff000005860300 x12: 0000000000000001<br />
			[   95.945114] x11: 00000000ffffffff x10: ffff000007330420 x9 : ffff0000031cb828<br />
			[   95.945794] x8 : ffff800009d2bb88 x7 : 0000000000000000 x6 : ffff000007330650<br />
			[   95.946473] x5 : ffff8000089ec56c x4 : ffff8000089ec56c x3 : 0000000000000000<br />
			[   95.947149] x2 : 0000000000000001 x1 : ffff800009b7acd8 x0 : 0000000000000100<br />
			[   95.947828] Call trace:<br />
			[   95.948064]  kobject_get+0x18/0xbc<br />
			[   95.948405]  device_shutdown+0xb4/0x260<br />
			[   95.948776]  kernel_restart+0x40/0xa4<br />
			[   95.949137]  __do_sys_reboot+0x1e0/0x264<br />
			[   95.949517]  __arm64_sys_reboot+0x24/0x30<br />
			[   95.949906]  invoke_syscall+0x48/0x114<br />
			[   95.950280]  el0_svc_common.constprop.0+0x44/0xfc<br />
			[   95.950739]  do_el0_svc+0x30/0xd0<br />
			[   95.951071]  el0_svc+0x2c/0x84<br />
			[   95.951385]  el0t_64_sync_handler+0xbc/0x140<br />
			[   95.951801]  el0t_64_sync+0x18c/0x190<br />
			[   95.952174] Code: 910003fd f9000bf3 aa0003f3 b4000160 (3940f000)<br />
			[   95.952738] ---[ end trace 0000000000000000 ]---<br />
			[   95.953228] note: systemd-shutdow[1] exited with preempt_count 1<br />
			[   95.953813] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b<br />
			[   95.954644] Kernel Offset: disabled<br />
			[   95.954969] CPU features: 0x00000,00000080,0000421b<br />
			[   95.955424] Memory Limit: none<br />
			[   95.955722] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---
		</p>
	</div>
</blockquote>

<p>
	Thanks for anyone willing to look.
</p>

<p>
	 
</p>

<p>
	Update: Reboot works fine on rockpi-s ordered more recently late 2023 with non-samsung ram module. I wonder if that is a reason. I will try the last 5.15 firmware created for this board and see if that works.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">33429</guid><pubDate>Wed, 24 Jan 2024 23:25:35 +0000</pubDate></item><item><title>Can rockpi s support 1-wire?</title><link>https://forum.armbian.com/topic/25263-can-rockpi-s-support-1-wire/</link><description><![CDATA[<p>
	I have add user <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>o with "armbian-add-overlay <abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>3308-w1-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>.<abbr title="Device tree source"><abbr title="Device tree source">dts</abbr></abbr>" but it's NOT wo<abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>.Some message is shown as below:
</p>

<p>
	pi@Pi-S:/boot/overlay-user$ dmesg | grep <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr><br />
	[    0.063257] OF: /onewire@0: could not get #<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>-cells for /usb@ff400000<br />
	[    0.096538] rockchip-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> ff220000.<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>: probed /pinctrl/<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>@ff220000<br />
	[    0.097838] rockchip-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> ff230000.<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>: probed /pinctrl/<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>@ff230000<br />
	[    0.099097] rockchip-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> ff240000.<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>: probed /pinctrl/<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>@ff240000<br />
	[    0.100300] rockchip-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> ff250000.<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>: probed /pinctrl/<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>@ff250000<br />
	[    0.101462] rockchip-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> ff260000.<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>: probed /pinctrl/<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>@ff260000<br />
	[    8.818566] <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>-17 (onewire@0): enfo<abbr title="Release candidate"><abbr title="Release candidate">rc</abbr></abbr>ed open drain please flag it properly in DT/ACPI DSDT/board file<br />
	[    8.818683] OF: /onewire@0: could not get #<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>-cells for /usb@ff400000<br />
	[    8.818731] w1-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> onewire@0: <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>_request_one (ext_pullup_enable_pin) failed<br />
	[    8.818742] w1-<abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>: probe of onewire@0 failed with error -22<br />
	[    8.872897] <abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>3308-acodec ff560000.acodec: Don't need hp-ctl <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr><br />
	[    8.872955] <abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>3308-acodec ff560000.acodec: Don't need spk-ctl <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr><br />
	[    8.872984] <abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>3308-acodec ff560000.acodec: Don't need pa-drv <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr><br />
	[    8.873096] <abbr title="Rockchip"><abbr title="Rockchip">rk</abbr></abbr>3308-acodec ff560000.acodec: Don't need micbias-en <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>
</p>

<p>
	What should I do to ?
</p>
]]></description><guid isPermaLink="false">25263</guid><pubDate>Sat, 24 Dec 2022 23:05:26 +0000</pubDate></item><item><title>cpufrequtils not correctly loaded on boot</title><link>https://forum.armbian.com/topic/30403-cpufrequtils-not-correctly-loaded-on-boot/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I have Rock Pi S V13 and Armbian 23.8.1 Bookworm with Linux 6.1.50-current-rockchip64.
</p>

<p>
	 
</p>

<p>
	When I change CPU settings (min frequency, max frequency, scaling governor) using armbian-config, the change works correctly as expected. However, these settings are lost on reboot. When I check the status of cpufrequtils service, it seems that it does not load correctly as it is not able to find the requested governor:
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			~$ systemctl status cpufrequtils.service
		</p>

		<p>
			● cpufrequtils.service - LSB: set CPUFreq kernel parameters<br />
			     Loaded: loaded (/etc/init.d/cpufrequtils; generated)<br />
			     Active: active (exited) since Tue 2023-09-26 15:03:11 CEST; 18h ago<br />
			       Docs: man:systemd-sysv-generator(8)<br />
			    Process: 691 ExecStart=/etc/init.d/cpufrequtils start (code=exited, status=0/SUCCESS)<br />
			        CPU: 122ms
		</p>

		<p>
			zář 26 15:03:10 labircam systemd[1]: Starting cpufrequtils.service - LSB: set CPUFreq kernel parameters...<br />
			zář 26 15:03:10 labircam cpufrequtils[691]: CPUFreq Utilities: Setting ondemand CPUFreq governor...disabled, governor not available...done.<br />
			zář 26 15:03:11 labircam systemd[1]: Started cpufrequtils.service - LSB: set CPUFreq kernel parameters.
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	But if I start it manually later, it seems to load all my settings correctly:
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			~$ sudo systemctl restart cpufrequtils
		</p>

		<p>
			~$ systemctl status cpufrequtils.service
		</p>

		<p>
			● cpufrequtils.service - LSB: set CPUFreq kernel parameters<br />
			     Loaded: loaded (/etc/init.d/cpufrequtils; generated)<br />
			     Active: active (exited) since Wed 2023-09-27 09:04:44 CEST; 9s ago<br />
			       Docs: man:systemd-sysv-generator(8)<br />
			    Process: 1968 ExecStart=/etc/init.d/cpufrequtils start (code=exited, status=0/SUCCESS)<br />
			        CPU: 123ms
		</p>

		<p>
			zář 27 09:04:44 labircam systemd[1]: Starting cpufrequtils.service - LSB: set CPUFreq kernel parameters...<br />
			zář 27 09:04:44 labircam cpufrequtils[1968]: CPUFreq Utilities: Setting ondemand CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done.<br />
			zář 27 09:04:44 labircam systemd[1]: Started cpufrequtils.service - LSB: set CPUFreq kernel parameters.
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	Any ideas to fix the problem except manually reloading it later?
</p>

<p>
	 
</p>

<p>
	armbianmonitor: <a href="https://paste.armbian.com/owolufawif" rel="external nofollow">https://paste.armbian.com/owolufawif</a>
</p>
]]></description><guid isPermaLink="false">30403</guid><pubDate>Wed, 27 Sep 2023 07:12:44 +0000</pubDate></item><item><title>How to check the temperature of Rock Pi S CPU?</title><link>https://forum.armbian.com/topic/28661-how-to-check-the-temperature-of-rock-pi-s-cpu/</link><description><![CDATA[<p>
	Per Radxa <a href="https://forum.radxa.com/t/how-to-check-the-temperature/2024" rel="external nofollow">here</a>, it is possible to obtain CPU temperature via "sudo cat /sys/class/thermal/thermal_zone0/temp".
</p>

<p>
	But the following paths do not exist on Armbian 23.05.1 Bookworm with Linux 6.1.30-rockchip64:
</p>

<ul>
	<li>
		/etc/armbianmonitor/datasources/soctemp
	</li>
	<li>
		/sys/devices/virtual/thermal/thermal_zone0/temp
	</li>
</ul>

<p>
	Running armbianmonitor -M, also does not show the temp:
</p>

<p>
	Time CPU load %cpu %sys %usr %nice %io %irq C.St.<br />
	22:29:52 408 MHz 0.02 0% 0% 0% 0% 0% 0% 0/6
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28661</guid><pubDate>Mon, 05 Jun 2023 15:22:06 +0000</pubDate></item><item><title>Rock Pi S - Virtual WLAN Interface P2P0</title><link>https://forum.armbian.com/topic/29189-rock-pi-s-virtual-wlan-interface-p2p0/</link><description><![CDATA[<p>
	Hi there, 
</p>

<p>
	 
</p>

<p>
	I've been using ARMbian for a couple of years now under a <a href="https://www.alexgoldcheidt.com/other-devices-rock-pi-s-512-mb-ram-sbc/" rel="external nofollow">Rock Pi S board</a>. I'm using an ARMbian OS image based on kernel 4.4x because it have a virtual wlan interface called P2P0, this allow me to use the board as WiFi repeater, <a href="https://www.alexgoldcheidt.com/other-devices-rock-pi-s-ap-sta-mode/" rel="external nofollow">I've written a post about it here</a>. However, in recent ARMbian OS images with kernel 5.x and 6.x that virtual interface isn't there. I see in ARMbian OS image with kernel 6.x that the WiFi Hotspot set up menu in the armbian-config tool show an interface called p2p0-dev, but it doesn't work. My question: why? these newer kernels have limitations on this board? or maybe need to compile the kernel with custom modifications?.
</p>

<p>
	 
</p>

<p>
	Any lead will be appreciated it.
</p>
]]></description><guid isPermaLink="false">29189</guid><pubDate>Mon, 10 Jul 2023 16:36:37 +0000</pubDate></item><item><title>Rock Pi S performance Bullseye vs Bookworm</title><link>https://forum.armbian.com/topic/29100-rock-pi-s-performance-bullseye-vs-bookworm/</link><description><![CDATA[<p>
	I tested boot time and node-red-reboot time and noticed that boot-time is with bookworm ~2 sec and node-red-reboot got from 14sec to 20sec.
</p>

<p>
	I hope you can improve performance so I can upgrade.
</p>

<p>
	https://paste.armbian.com/uhocorarad
</p>
]]></description><guid isPermaLink="false">29100</guid><pubDate>Mon, 03 Jul 2023 17:37:47 +0000</pubDate></item><item><title>Rock Pi S SPI2 pin collides with serial interface</title><link>https://forum.armbian.com/topic/28881-rock-pi-s-spi2-pin-collides-with-serial-interface/</link><description><![CDATA[<p>
	Is there any existing solution how to use SPI2 on Radxa Rock Pi S? In dmesg I found these messages:
</p>

<p>
	 
</p>

<p>
	[    1.619008] rockchip-pinctrl pinctrl: pin gpio1-22 already requested by ff0c0000.serial; cannot claim for ff140000.spi<br />
	[    1.619046] rockchip-pinctrl pinctrl: pin-54 (ff140000.spi) status -22<br />
	[    1.619065] rockchip-pinctrl pinctrl: could not request pin 54 (gpio1-22) from group spi2-miso  on device rockchip-pinctrl<br />
	[    1.619082] rockchip-spi ff140000.spi: Error applying setting, reverse things back
</p>

<p>
	 
</p>

<p>
	Is it somehow possible to disable the serial port which is in collision with the SPI?
</p>

<p>
	 
</p>

<p>
	There is a log from armbian monitor: <a href="http://ix.io/4yF8" rel="external nofollow">http://ix.io/4yF8</a>
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28881</guid><pubDate>Tue, 20 Jun 2023 07:07:36 +0000</pubDate></item><item><title>Cannot get Rock Pi S images to boot, please help.</title><link>https://forum.armbian.com/topic/28664-cannot-get-rock-pi-s-images-to-boot-please-help/</link><description><![CDATA[<p>
	I am working with a Rock Pi S v1.3 and thus far the only image I have been able to get to boot is <strong>Armbian 21.05.9 Focal with Linux 4.4.247-rockpis</strong>. I have tried the recent Arabian Bookworm, Armbian Jammy and a few other variations I have come across on various forum posts here.
</p>

<p>
	 
</p>

<p>
	With the above working image I can communicate with it via UART and get to the terminal. With everything else I don't even get the blinking blue LED; just two solid green LEDs. I have a few of these boards and have confirmed this issue across all of them.
</p>

<p>
	 
</p>

<p>
	I am not sure what next steps to take so any pointers would be greatly appreciated.
</p>

<p>
	 
</p>

<p>
	Thank you very much in advance. 
</p>
]]></description><guid isPermaLink="false">28664</guid><pubDate>Mon, 05 Jun 2023 22:13:31 +0000</pubDate></item><item><title>Recommended gpio library</title><link>https://forum.armbian.com/topic/28558-recommended-gpio-library/</link><description><![CDATA[<p>
	For the Rock PI S, what is the recommended <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr> library?
</p>

<p>
	I tried using Radxa <a href="https://wiki.radxa.com/RockpiS/dev/libmraa" rel="external nofollow">libmraa</a> but encountered the following errors (using bullseye-stable):
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">$ sudo apt-get install -y libmraa
...
The following packages have unmet dependencies:
 libmraa : Depends: libjson-c3 but it is not installable
           Depends: python but it is not installable
           Depends: python2.7 but it is not installable
           Depends: libpython2.7 but it is not installable
           Depends: python3.7 but it is not installable
           Depends: libpython3.7 but it is not installable
E: Unable to correct problems, you have held broken packages.</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28558</guid><pubDate>Sun, 28 May 2023 22:29:22 +0000</pubDate></item><item><title>Changing MAC address for RockpiS - 21.08.2 Focal / Linux 5.14.5-rockchip64</title><link>https://forum.armbian.com/topic/18977-changing-mac-address-for-rockpis-21082-focal-linux-5145-rockchip64/</link><description><![CDATA[
<div class="ipsMargin_top">
    
    
    
</div><p>
	Using the 5.xx kernal I have been changing the eth0 MAC address at  /etc/NetworkManager/system-connections/  'Wired connection 1.nmconnection'.  This has changed a bit as the versions progress - but version  Armbian 21.08.2 Focal / Linux 5.14.5-rockchip64 has now moved the "wired ..." file to the /run/NetworkManager/system-connections/ and suspect the file is recreated at every boot (edits do not stick).  I have tried to set MAC  at /boot/armbianEnv.txt and in the eth config file.  None work.  Any ideas as to how to set the MAC address - and is it now even possible?.
</p>
]]></description><guid isPermaLink="false">18977</guid><pubDate>Mon, 20 Sep 2021 22:02:26 +0000</pubDate></item><item><title>Audio broken on current builds (23.02 Jammy)</title><link>https://forum.armbian.com/topic/27626-audio-broken-on-current-builds-2302-jammy/</link><description><![CDATA[<p>
	armbianmonitor output: <a href="http://ix.io/4s3z" rel="external nofollow">http://ix.io/4s3z</a>
</p>

<p>
	 
</p>

<p>
	I'm testing Armbian 23.02 Jammy on a Rock Pi S with its matching "PoE HAT" (which provides a 3.5mm headphone jack).
</p>

<p>
	No sound cards are available despite the device tree evidently containing sound devices/codecs [<a href="https://github.com/armbian/build/blob/577d0eaa282226a544b497d1e611a14fc1a14338/patch/kernel/archive/rockchip64-6.1/board-rockpis-0001-arm64-dts.patch#L46" rel="external nofollow">1</a>, <a href="https://github.com/armbian/build/blob/577d0eaa282226a544b497d1e611a14fc1a14338/patch/kernel/archive/rockchip64-6.1/board-rockpis-0020-arm64-dts-rockchip-Add-acodec-node-for-rk3308.patch#L29" rel="external nofollow">2</a>].
</p>

<p>
	 
</p>

<p>
	aplay output:
</p>

<pre class="ipsCode">rockpi-s:~:% aplay -l
aplay: device_list:274: no soundcards found...</pre>

<p>
	 
</p>

<p>
	The armbianmonitor/dmesg output contains the following suspicious lines:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[   24.551148] platform acodec-sound: deferred probe pending
[   24.551191] platform sound: deferred probe pending</span></pre>

<p>
	 
</p>

<p>
	Digging into this a bit further, I found this
</p>

<pre class="ipsCode">root@rockpi-s:/home/dale# cat /sys/kernel/debug/devices_deferred
acodec-sound    asoc-simple-card: parse error
sound   asoc-simple-card: parse error
</pre>

<p>
	 
</p>

<p>
	If I were to guess, it looks like a devicetree issue, but unfortunately I have no idea how to debug devicetree issues.
</p>

<p>
	If anyone can provide any pointers on how to capture more detailed devicetree logs to try and figure out this "parse error", I'd appreciate it.
</p>

<p>
	 
</p>

<p>
	Thanks!
</p>
]]></description><guid isPermaLink="false">27626</guid><pubDate>Tue, 28 Mar 2023 14:47:10 +0000</pubDate></item><item><title>Finding out the serial ports</title><link>https://forum.armbian.com/topic/26801-finding-out-the-serial-ports/</link><description><![CDATA[<p>
	I have Rock Pi S V13, that <a href="https://wiki.radxa.com/RockpiS/hardware/gpio#Hardware_V13" rel="external nofollow">has 4 UART ports</a>.
</p>

<p>
	I'm already connecting to the board via serial console on /dev/ttyS0.
</p>

<p>
	 
</p>

<p>
	<strong>How can I find out what are the other ports assignments/paths?</strong>
</p>

<p>
	 
</p>

<p>
	I have tried to use a Python script to detect the output by using an FTDI to USB board with no luck (the voltage and baudrate are correct).
</p>

<p>
	The Python script <a href="https://pythonhosted.org/pyserial/shortintro.html" rel="external nofollow">taken from manual</a>:
</p>

<p>
	<br />
	 
</p>

<pre class="ipsCode prettyprint prettyprinted"><span class="kwd">import</span><span class="pln"> serial
</span><span class="kwd">import</span><span class="pln"> time

</span><span class="com"># I've tried /dev/ttyS2 and /dev/ttyS4</span><span class="pln">
ser </span><span class="pun">=</span><span class="pln"> serial</span><span class="pun">.</span><span class="typ">Serial</span><span class="pun">(</span><span class="pln">port</span><span class="pun">=</span><span class="str">'/dev/ttyS4'</span><span class="pun">,</span><span class="pln"> baudrate</span><span class="pun">=</span><span class="lit">115200</span><span class="pun">,</span><span class="pln"> timeout</span><span class="pun">=</span><span class="lit">0.1</span><span class="pun">)</span><span class="pln">
</span><span class="kwd">print</span><span class="pun">(</span><span class="pln">ser</span><span class="pun">.</span><span class="pln">name</span><span class="pun">)</span><span class="pln">

</span><span class="kwd">try</span><span class="pun">:</span><span class="pln">
        </span><span class="kwd">while</span><span class="pln"> </span><span class="kwd">True</span><span class="pun">:</span><span class="pln">
                ser</span><span class="pun">.</span><span class="pln">write</span><span class="pun">(</span><span class="pln">b</span><span class="str">'hello'</span><span class="pun">)</span><span class="pln">
                time</span><span class="pun">.</span><span class="pln">sleep</span><span class="pun">(</span><span class="lit">0.5</span><span class="pun">)</span><span class="pln">
</span><span class="kwd">except</span><span class="pln"> </span><span class="typ">KeyboardInterrupt</span><span class="pun">:</span><span class="pln">
        ser</span><span class="pun">.</span><span class="pln">close</span><span class="pun">()</span></pre>

<p>
	 
</p>

<p>
	Running
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			ls /sys/class/tty/*/device/driver
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	outputs
</p>

<p>
	<br />
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			 
		</p>

		<p>
			/sys/class/tty/ttyS0/device/driver:<br />
			bind  ff0a0000.serial  ff0c0000.serial  ff0e0000.serial  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS1/device/driver:<br />
			bind  serial8250  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS2/device/driver:<br />
			bind  ff0a0000.serial  ff0c0000.serial  ff0e0000.serial  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS3/device/driver:<br />
			bind  serial8250  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS4/device/driver:<br />
			bind  ff0a0000.serial  ff0c0000.serial  ff0e0000.serial  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS5/device/driver:<br />
			bind  serial8250  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS6/device/driver:<br />
			bind  serial8250  uevent  unbind
		</p>

		<p>
			/sys/class/tty/ttyS7/device/driver:<br />
			bind  serial8250  uevent  unbind
		</p>

		<p>
			 
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	and
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			ls -l /dev/tty* | grep 'dialout'
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	outputs
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			crw-rw---- 1 root dialout 4, 65 Dec 23 11:44 /dev/ttyS1<br />
			crw-rw---- 1 root dialout 4, 66 Dec 23 11:44 /dev/ttyS2<br />
			crw-rw---- 1 root dialout 4, 67 Dec 23 11:44 /dev/ttyS3<br />
			crw-rw---- 1 root dialout 4, 68 Dec 23 11:44 /dev/ttyS4<br />
			crw-rw---- 1 root dialout 4, 69 Dec 23 11:44 /dev/ttyS5<br />
			crw-rw---- 1 root dialout 4, 70 Dec 23 11:44 /dev/ttyS6<br />
			crw-rw---- 1 root dialout 4, 71 Dec 23 11:44 /dev/ttyS7
		</p>
	</div>
</blockquote>

<p>
	 
</p>
]]></description><guid isPermaLink="false">26801</guid><pubDate>Tue, 21 Feb 2023 18:17:39 +0000</pubDate></item><item><title>Missing bluetooth driver for RTL8761</title><link>https://forum.armbian.com/topic/26567-missing-bluetooth-driver-for-rtl8761/</link><description><![CDATA[<p>
	The <strong>Armbian 22.11.4 Jammy</strong> with <strong>Linux 6.0.10-rockchip64</strong> doesn't have the drivers for a USB Bluetooth bought from Amazon.
</p>

<p>
	 
</p>

<p>
	The kernel gives me these errors at boot:
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			feb 10 14:29:24 RockPi kernel: usb 3-1: new full-speed USB device number 2 using ohci-platform<br />
			feb 10 14:29:24 RockPi kernel: usb 3-1: New USB device found, idVendor=0bda, idProduct=8771, bcdDevice= 2.00<br />
			feb 10 14:29:24 RockPi kernel: usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3<br />
			feb 10 14:29:24 RockPi kernel: usb 3-1: Product: Bluetooth Radio<br />
			feb 10 14:29:24 RockPi kernel: usb 3-1: Manufacturer: Realtek<br />
			feb 10 14:29:24 RockPi kernel: usb 3-1: SerialNumber: 00E04C239987<br />
			[ 1362.077700] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761bu_fw.bin not found<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: Core ver 2.22<br />
			feb 10 14:29:25 RockPi kernel: NET: Registered PF_BLUETOOTH protocol family<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: HCI device and connection manager initialized<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: HCI socket layer initialized<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: L2CAP socket layer initialized<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: SCO socket layer initialized<br />
			feb 10 14:29:25 RockPi kernel: usbcore: registered new interface driver btusb<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: hci0: RTL: rom_version status=0 version=1<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin<br />
			feb 10 14:29:25 RockPi kernel: bluetooth hci0: Direct firmware load for rtl_bt/rtl8761bu_fw.bin failed with error -2<br />
			feb 10 14:29:25 RockPi kernel: Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8761bu_fw.bin not found
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	Listing the available bluetooth drivers
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">ls -l /usr/lib/firmware/rtl_bt</span></pre>

<p>
	 
</p>

<p>
	gives me:
</p>

<p>
	 
</p>

<blockquote class="ipsQuote" data-ipsquote="">
	<div class="ipsQuote_citation">
		Quote
	</div>

	<div class="ipsQuote_contents">
		<p>
			-rw-rw-r--  1 root root    68 ian 23 22:50 rtl8723b_config.bin<br />
			-rw-rw-r--  1 root root 46236 ian 23 22:50 rtl8723b_fw.bin<br />
			lrwxrwxrwx  1 root root    19 ian 23 22:50 rtl8723bs_config.bin -&gt; rtl8723b_config.bin<br />
			-rw-rw-r--  1 root root    68 ian 23 22:50 rtl8723bs_config-pine64.bin<br />
			lrwxrwxrwx  1 root root    15 ian 23 22:50 rtl8723bs_fw.bin -&gt; rtl8723b_fw.bin<br />
			lrwxrwxrwx  1 root root    28 ian 23 22:50 rtl8723cs_cg_config.bin -&gt; ../rtlbt/rtl8723cs_cg_config<br />
			lrwxrwxrwx  1 root root    24 ian 23 22:50 rtl8723cs_cg_fw.bin -&gt; ../rtlbt/rtl8723cs_cg_fw<br />
			lrwxrwxrwx  1 root root    28 ian 23 22:50 rtl8723cs_vf_config.bin -&gt; ../rtlbt/rtl8723cs_vf_config<br />
			lrwxrwxrwx  1 root root    24 ian 23 22:50 rtl8723cs_vf_fw.bin -&gt; ../rtlbt/rtl8723cs_vf_fw<br />
			lrwxrwxrwx  1 root root    28 ian 23 22:50 rtl8723cs_xx_config.bin -&gt; ../rtlbt/rtl8723cs_xx_config<br />
			lrwxrwxrwx  1 root root    24 ian 23 22:50 rtl8723cs_xx_fw.bin -&gt; ../rtlbt/rtl8723cs_xx_fw<br />
			-rw-rw-r--  1 root root    47 ian 23 22:50 rtl8723ds_config.bin<br />
			-rw-rw-r--  1 root root 48988 ian 23 22:50 rtl8723ds_fw.bin<br />
			-rw-rw-r--  1 root root    10 ian 23 22:50 rtl8821c_config.bin<br />
			-rw-rw-r--  1 root root 37356 ian 23 22:50 rtl8821c_fw.bin<br />
			-rw-rw-r--  1 root root    14 ian 23 22:50 rtl8822b_config.bin<br />
			-rw-rw-r--  1 root root 51176 ian 23 22:50 rtl8822b_fw.bin<br />
			-rw-rw-r--  1 root root    73 ian 23 22:50 rtl8822cs_config.bin<br />
			-rw-rw-r--  1 root root 66248 ian 23 22:50 rtl8822cs_fw.bin<br />
			-rw-rw-r--  1 root root    55 ian 23 22:50 rtlbt_config<br />
			-rw-rw-r--  1 root root 44504 ian 23 22:50 rtlbt_fw<br />
			-rw-rw-r--  1 root root 51364 ian 23 22:50 rtlbt_fw_new
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	while the latest Linux kernel contains the driver:
</p>

<p>
	 
</p>

<p>
	<a href="https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_bt" rel="external nofollow">https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/rtl_bt</a>
</p>

<p>
	 
</p>

<p>
	<strong>Where can I get it or how can I install the bluetooth driver?</strong>
</p>
]]></description><guid isPermaLink="false">26567</guid><pubDate>Fri, 10 Feb 2023 13:06:54 +0000</pubDate></item><item><title>[HELP] Stuck in U-boot after overlay.dts attempt</title><link>https://forum.armbian.com/topic/25744-help-stuck-in-u-boot-after-overlaydts-attempt/</link><description><![CDATA[<p>
	Hi, everyone
</p>

<p>
	 
</p>

<p>
	I have 2 rockpi s based boards, and I tried to apply an overlay to one.
</p>

<p>
	It actually compiled, I rebooted and the nothing more.
</p>

<p>
	I connected serial, e it was on U-boot, spitting this:
</p>

<p>
	 
</p>

<div class="ipsSpoiler" data-ipsspoiler="">
	<div class="ipsSpoiler_header">
		<span>Spoiler</span>
	</div>

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode">DDR Version V2.06 20211109
CHIP ID = 0x00003308
REG2C: 0x00000034, 0x00000034
In
589MHz
DDR3
Col=10 Bank=3 Row=15 Size=512MB
OUT: sdram_init finish.
Boot1 Release Time: Mar 24 2022 08:28:57, version: 1.36
ROM VER:0x56323030, 19
chip_id:330800,0
ChipType = 0x13, 512
DPLL = 1300 MHz
...nandc_flash_init enter...
No.1 FLASH ID:ff ff ff ff ff ff
DPLL = 1300 MHz
sfc nor id: ff ff ff
DPLL = 1300 MHz
sfc_nand id: ff ff ff
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
mmc2:cmd8,20
mmc2:cmd5,20
mmc2:cmd55,20
DPLL = 1300 MHz
NeedKHz=18000KHz,clock=650000KHz
DPLL = 1300 MHz
NeedKHz=48000KHz,clock=650000KHz
mmc2:cmd19,100
SdmmcInit=2 0
BootCapSize=2000
UserCapSize=7456MB
FwPartOffset=2000 , 2000
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
NeedKHz=200KHz,clock=12000KHz
mmc0:cmd5,20
DPLL = 1300 MHz
NeedKHz=24000KHz,clock=650000KHz
DPLL = 1300 MHz
NeedKHz=40000KHz,clock=650000KHz
SdmmcInit=0 0
BootCapSize=0
UserCapSize=7624MB
FwPartOffset=2000 , 0
StorageInit ok = 168518
SecureMode = 0
Secure read PBA: 0x4
Secure read PBA: 0x404
Secure read PBA: 0x804
Secure read PBA: 0xc04
Secure read PBA: 0x1004
SecureInit ret = 0, SecureMode = 0
atags_set_bootdev: ret:(0)
GPT 0x3306530 signature is wrong
recovery gpt...
GPT 0x3306530 signature is wrong
recovery gpt fail!
LoadTrust Addr:0x4000
No find bl30.bin
No find bl32.bin
Load uboot, ReadLba = 2000
Load OK, addr=0x600000, size=0x994f8
RunBL31 0x40000 @ 253233 us
INFO:    Preloader serial: 0
NOTICE:  BL31: v1.3(release):30f1405
NOTICE:  BL31: Built : 17:08:28, Sep 23 2019
INFO:    Lastlog: last=0x100000, realtime=0x102000, size=0x2000
INFO:    ARM GICv2 driver initialized
INFO:    Using opteed sec cpu_context!
INFO:    boot cpu mask: 1
INFO:    plat_rockchip_pmu_init: pd status 0xe b
INFO:    BL31: Initializing runtime services
WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE init          ialization. SMC`s destined for OPTEE will return SMC_UNK
ERROR:   Error initializing runtime service opteed_fast
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x600000
INFO:    SPSR = 0x3c9


U-Boot 2022.04-armbian (Dec 23 2022 - 09:36:07 +0000)

Model: Radxa ROCK Pi S
DRAM:  510 MiB
Core:  276 devices, 20 uclasses, devicetree: separate
MMC:   dwmmc@ff480000: 1, dwmmc@ff490000: 0
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Model: Radxa ROCK Pi S
rockchip_dnl_key_pressed read board id failed
Net:   eth0: ethernet@ff4e0000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3045 bytes read in 4 ms (743.2 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 0
17 bytes read in 3 ms (4.9 KiB/s)
13956325 bytes read in 594 ms (22.4 MiB/s)
31273472 bytes read in 1325 ms (22.5 MiB/s)
Failed to load '/boot/dtb/'
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr &lt;address&gt;" command.
Aborting!
Failed to load '/boot/dtb/rockchip/overlay/-fixup.scr'
Moving Image from 0x680000 to 0x800000, end=2670000
## Loading init Ramdisk from Legacy Image at 04000000 ...
   Image Name:   uInitrd
   Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
   Data Size:    13956261 Bytes = 13.3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
Speed: 10, half duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
CPU not owner of tx frame

Retry time exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-72-e8-9e-60-82-ef
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00000000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0000000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/000000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/000
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/00
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/0
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-rk3308-evb_rk3308
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-rk3308
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm
Speed: 10, half duplex
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default
Speed: 10, half duplex
*** ERROR: `serverip' not set
Config file not found
starting USB...
No working controllers found
Speed: 10, half duplex
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
BOOTP broadcast 7
BOOTP broadcast 8
BOOTP broadcast 9
BOOTP broadcast 10
BOOTP broadcast 11
BOOTP broadcast 12
BOOTP broadcast 13
BOOTP broadcast 14
BOOTP broadcast 15
BOOTP broadcast 16
BOOTP broadcast 17
CPU not owner of tx frame

Retry time exceeded; starting again
=&gt;
</pre>

		<p>
			 
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	U-boot seems unable to load the device tree, but to my knowledge, a broken overlay shouldn't break anything
</p>

<p>
	Any help is welcome
</p>

<p>
	 
</p>

<p>
	Thx
</p>
]]></description><guid isPermaLink="false">25744</guid><pubDate>Thu, 12 Jan 2023 09:52:57 +0000</pubDate></item><item><title>Unbootable images?  Only old image I am using seems to work</title><link>https://forum.armbian.com/topic/24345-unbootable-images-only-old-image-i-am-using-seems-to-work/</link><description><![CDATA[<p>
	Good morning,
</p>

<p>
	 
</p>

<p>
	I cannot seem to get the the newest image (22.08 Bullseye) to boot.  I've noticed the disk arrangement is significantly different than the known working image I am using.
</p>

<p>
	 
</p>

<p>
	Here is what I see on the known working image...
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">#fdisk -l

Disk /dev/mmcblk0: 28.9 GiB, 30985420800 bytes, 60518400 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 2A33F1A5-75EA-4125-AC19-16C0435D774A

Device          Start      End  Sectors  Size Type
/dev/mmcblk0p1     64     8063     8000  3.9M Linux filesystem
/dev/mmcblk0p2  16384    24575     8192    4M Linux filesystem
/dev/mmcblk0p3  24576    32767     8192    4M Linux filesystem
/dev/mmcblk0p4  32768   262143   229376  112M EFI System
/dev/mmcblk0p5 262144 60518366 60256223 28.7G Linux filesystem</span></pre>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">#cat /etc/debian_version 
9.9</span></pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	The newest image is in has a DOS partition table and only one partition.
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Disk /dev/sdc: 28.91 GiB, 31016878080 bytes, 60579840 sectors
Disk model: STORAGE DEVICE  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x1640add5

Device     Boot Start     End Sectors  Size Id Type
/dev/sdc1       32768 3833855 3801088  1.8G 83 Linux</span></pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	Also may be important to note my rock pi S has no onboard flash, only SD slot. 
</p>

<p>
	 
</p>

<p>
	Am I missing something?  Thank you for your time.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">24345</guid><pubDate>Thu, 10 Nov 2022 09:08:41 +0000</pubDate></item><item><title>Rock Pi S Jammy image fails, Bullseye image works</title><link>https://forum.armbian.com/topic/24329-rock-pi-s-jammy-image-fails-bullseye-image-works/</link><description><![CDATA[<p>
	I just tried the official Jammy image on the Rock Pi S, which does not boot. Looking at serial, it halts after "Starting kernel ...". I've tried redownloading the image, burning it again and on a different SD card. I also tried the bullseye image, which *does* boot (which makes me believe this is not a hardware issue).
</p>

<p>
	 
</p>

<p>
	Anyone with a Rock Pi S that could confirm my observation?
</p>

<p>
	 
</p>

<p>
	This image failed to boot:  Armbian_22.08.7_Rockpi-s_jammy_edge_5.19.16.img
</p>

<p>
	Serial output: <a class="ipsAttachLink" data-fileext="txt" data-fileid="9580" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=9580&amp;key=7803587f984d5e5c21b3cf96319a7ec6" rel="">rock-pi-s-fail.txt</a>
</p>

<p>
	 
</p>

<p>
	This image booted ok: Armbian_22.08.7_Rockpi-s_bullseye_edge_5.19.16.img
</p>

<p>
	Serial output: <a class="ipsAttachLink" data-fileext="txt" data-fileid="9581" href="https://forum.armbian.com/applications/core/interface/file/attachment.php?id=9581&amp;key=d33a879d57072fa0ffbad8562ca10b66" rel="">rock-pi-s-ok.txt</a>
</p>

<p>
	 
</p>

<p>
	Diff of serial output (up to Staring kernel... line):
</p>

<p>
	<br />
	 
</p>

<pre class="ipsCode">--- rock-pi-s-fail.txt  2022-11-09 12:40:03.199949846 +0100
+++ rock-pi-s-ok.txt    2022-11-09 12:58:16.937136391 +0100
@@ -52,7 +52,7 @@
 BootCapSize=0
 UserCapSize=29554MB
 FwPartOffset=2000 , 0
-StorageInit ok = 27839
+StorageInit ok = 27858
 SecureMode = 0
 Secure read PBA: 0x4
 Secure read PBA: 0x404
@@ -70,7 +70,7 @@
 No find bl32.bin
 Load uboot, ReadLba = 2000
 Load OK, addr=0x600000, size=0x9dad0
-RunBL31 0x40000 @ 106200 us
+RunBL31 0x40000 @ 106201 us
 ^AINFO:    Preloader serial: 0
 NOTICE:  BL31: v1.3(release):30f1405
 NOTICE:  BL31: Built : 17:08:28, Sep 23 2019
@@ -108,8 +108,8 @@
 3045 bytes read in 5 ms (594.7 KiB/s)
 ## Executing script at 00500000
 Boot script loaded from mmc 1
-176 bytes read in 5 ms (34.2 KiB/s)
-23219213 bytes read in 986 ms (22.5 MiB/s)
+176 bytes read in 4 ms (43 KiB/s)
+19531454 bytes read in 831 ms (22.4 MiB/s)
 31263232 bytes read in 1328 ms (22.5 MiB/s)
 54638 bytes read in 9 ms (5.8 MiB/s)
 Failed to load '/boot/dtb/rockchip/overlay/rk3308-fixup.scr'
@@ -117,15 +117,33 @@
 ## Loading init Ramdisk from Legacy Image at 04000000 ...
    Image Name:   uInitrd
    Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
-   Data Size:    23219149 Bytes = 22.1 MiB
+   Data Size:    19531390 Bytes = 18.6 MiB
    Load Address: 00000000
    Entry Point:  00000000
    Verifying Checksum ... OK
 ## Flattened Device Tree blob at 02800000
    Booting using the fdt blob at 0x2800000
-   Loading Ramdisk to 0c8fd000, end 0df21bcd ... OK
+   Loading Ramdisk to 0cc81000, end 0df2167e ... OK
 ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0)
-   Loading Device Tree to 000000000c887000, end 000000000c8fcfff ... OK
+   Loading Device Tree to 000000000cc0b000, end 000000000cc80fff ... OK
 
 Starting kernel ...</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">24329</guid><pubDate>Wed, 09 Nov 2022 12:01:41 +0000</pubDate></item><item><title>Updated images for Rockpi S</title><link>https://forum.armbian.com/topic/24063-updated-images-for-rockpi-s/</link><description><![CDATA[<p>
	Thanks to <a contenteditable="false" data-ipshover="" data-ipshover-target="https://forum.armbian.com/profile/203851-brentr/?do=hovercard" data-mentionid="203851" href="https://forum.armbian.com/profile/203851-brentr/" id="ips_uid_8329_4" rel="">@brentr</a> we got new images with several fixes:
</p>

<p>
	 
</p>

<ul>
	<li>
		<a href="https://armbian.atlassian.net/browse/AR-1269" ipsnoembed="true" rel="external nofollow">https://armbian.atlassian.net/browse/AR-1269</a> RockPI WiFi assigned different MAC address on each boot
	</li>
	<li>
		<a href="https://armbian.atlassian.net/browse/AR-1268" ipsnoembed="true" rel="external nofollow">https://armbian.atlassian.net/browse/AR-1268</a> RockPI-S WiFi throughput only 300K bytes/second
	</li>
	<li>
		<a href="https://armbian.atlassian.net/browse/AR-1265" ipsnoembed="true" rel="external nofollow">https://armbian.atlassian.net/browse/AR-1265</a> Rock PI-S images will not boot from internal <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">EMMC</abbr></abbr> (SDNAND)
	</li>
</ul>

<p>
	 
</p>

<p>
	<a href="https://www.armbian.com/rockpi-s/" ipsnoembed="true" rel="external nofollow">https://www.armbian.com/rockpi-s/</a>
</p>
]]></description><guid isPermaLink="false">24063</guid><pubDate>Thu, 20 Oct 2022 10:30:25 +0000</pubDate></item></channel></rss>
