<?xml version="1.0"?>
<rss version="2.0"><channel><title>Odroid XU4 Latest Topics</title><link>https://testforum.armbian.com/forum/171-odroid-xu4/</link><description>Odroid XU4 Latest Topics</description><language>en</language><item><title>OOM invokes after ~300 seconds</title><link>https://testforum.armbian.com/topic/62011-oom-invokes-after-~300-seconds/</link><description><![CDATA[<p>
	Hello,  after upgrading my xu4 to trixie I have begun seeing the oom killer wrecking havoc!
</p>

<p>
	 
</p>

<p>
	I had 1Gb of swap and have upgraded it to have 6Gb of swap but it does not seem to help.
</p>

<p>
	 
</p>

<p>
	I have set vm.panic_on_oom = 1 as without this it just keeps killing tasks and then says deadlocked on memory
</p>

<p>
	 
</p>

<p>
	here are 2 seperate boots of the os
</p>

<p>
	 
</p>

<p>
	any help would be appreciated
</p>

<p>
	 
</p>

<p>
	[  304.195611] dnsmasq invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=0, oom_score_adj=0<br />
	[  304.202725] CPU: 2 PID: 1322 Comm: dnsmasq Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  304.210252] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  304.216332]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  304.221515]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  304.226541]  dump_stack_lvl from dump_header+0x4c/0x208<br />
	[  304.231740]  dump_header from out_of_memory+0x2a8/0x344<br />
	[  304.236940]  out_of_memory from __alloc_pages+0xcd4/0x122c<br />
	[  304.242398]  __alloc_pages from __get_free_pages+0x14/0x24<br />
	[  304.247857]  __get_free_pages from __pollwait+0xa8/0xf8<br />
	[  304.253056]  __pollwait from datagram_poll+0x28/0xfc<br />
	[  304.257996]  datagram_poll from udp_poll+0x10/0x88<br />
	[  304.262762]  udp_poll from sock_poll+0x50/0xd0<br />
	[  304.267181]  sock_poll from do_sys_poll+0x350/0x5e8<br />
	[  304.272033]  do_sys_poll from sys_poll+0x40/0x110<br />
	[  304.276711]  sys_poll from ret_fast_syscall+0x0/0x54<br />
	[  304.281648] Exception stack(0xf2795fa8 to 0xf2795ff0)<br />
	[  304.286680] 5fa0:                   00000000 00000000 00551a40 00000018 ffffffff 00000000<br />
	[  304.294829] 5fc0: 00000000 00000000 00000000 000000a8 00000019 ffffffff 00545430 bea589e8<br />
	[  304.302972] 5fe0: 000000a8 bea58958 b6bdeb49 b6b9f736<br />
	[  304.308091] Mem-Info:<br />
	[  304.310257] active_anon:1897 inactive_anon:70334 isolated_anon:0<br />
	[  304.310257]  active_file:11947 inactive_file:40757 isolated_file:0<br />
	[  304.310257]  unevictable:4754 dirty:3 writeback:0<br />
	[  304.310257]  slab_reclaimable:5012 slab_unreclaimable:178269<br />
	[  304.310257]  mapped:27742 shmem:4819 pagetables:1382<br />
	[  304.310257]  sec_pagetables:0 bounce:0<br />
	[  304.310257]  kernel_misc_reclaimable:0<br />
	[  304.310257]  free:183203 free_pcp:3 free_cma:31735<br />
	[  304.350026] Node 0 active_anon:7588kB inactive_anon:281336kB active_file:47552kB inactive_file:163464kB unevictable:19016kB isolated(anon):0kB isolated(file):0kB mapped:110968kB dirty:12kB writeback:0kB shmem:19276kB writeback_tmp:0kB kernel_stack:2936kB pagetables:5528kB sec_pagetables:0kB all_unreclaimable? yes<br />
	[  304.377596] Normal free:3908kB boost:0kB min:3416kB low:4268kB high:5120kB reserved_highatomic:8192KB active_anon:0kB inactive_anon:0kB active_file:1620kB inactive_file:0kB unevictable:0kB writepending:0kB present:786432kB managed:748292kB mlocked:0kB bounce:0kB free_pcp:12kB local_pcp:0kB free_cma:0kB<br />
	[  304.404303] lowmem_reserve[]: 0 10064 10064<br />
	[  304.408439] Normal: 260*4kB (UME) 187*8kB (UME) 58*16kB (UME) 7*32kB (UE) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 3688kB<br />
	[  304.421806] 59668 total pagecache pages<br />
	[  304.425500] 0 pages in swap cache<br />
	[  304.428884] Free swap  = 6011596kB<br />
	[  304.432169] Total swap = 6011596kB<br />
	[  304.435552] 518656 pages RAM<br />
	[  304.438528] 322048 pages HighMem/MovableOnly<br />
	[  304.442657] 9535 pages reserved<br />
	[  304.445778] 32768 pages cma reserved<br />
	[  304.449473] Unreclaimable slab info:<br />
	[  304.452883] Name                      Used          Total<br />
	[  304.458357] nf_conntrack             128KB        128KB<br />
	[  304.463465] rpc_buffers              256KB        256KB<br />
	[  304.468815] RAWv6                    159KB        159KB<br />
	[  304.473856] UDPv6                    256KB        256KB<br />
	[  304.479150] tw_sock_TCPv6             39KB         39KB<br />
	[  304.484252] request_sock_TCPv6         47KB         47KB<br />
	[  304.489632] TCPv6                    248KB        248KB<br />
	[  304.494742] btrfs_delayed_ref_head         59KB         59KB<br />
	[  304.500498] btrfs_ordered_extent         39KB         39KB<br />
	[  304.505975] btrfs_extent_map         179KB        179KB<br />
	[  304.511028] bio-240                    8KB          8KB<br />
	[  304.516319] bio-288                   78KB         78KB<br />
	[  304.521419] btrfs_path                31KB         31KB<br />
	[  304.526676] bio-304                    7KB          7KB<br />
	[  304.531817] bio-336                    7KB          7KB<br />
	[  304.537068] scsi_sense_cache          16KB         16KB<br />
	[  304.542219] bio-96                    32KB         32KB<br />
	[  304.547473] bio-208                    8KB          8KB<br />
	[  304.552613] mqueue_inode_cache         31KB         31KB<br />
	[  304.557951] fuse_request               3KB          3KB<br />
	[  304.563100] ecryptfs_headers        1760KB       1760KB<br />
	[  304.568351] ecryptfs_file_cache          8KB          8KB<br />
	[  304.573679] audit_tree_mark           43KB         43KB<br />
	[  304.578913] posix_timers_cache         15KB         15KB<br />
	[  304.584156] ip4-frags                172KB        179KB<br />
	[  304.589416] RAW                       15KB         15KB<br />
	[  304.594557] UDP                      252KB        252KB<br />
	[  304.599801] tw_sock_TCP               23KB         23KB<br />
	[  304.604955] request_sock_TCP          31KB         31KB<br />
	[  304.610197] TCP                      246KB        246KB<br />
	[  304.615351] bio-192                    8KB          8KB<br />
	[  304.620607] ep_head                   32KB         32KB<br />
	[  304.625750] sgpool-128                30KB         30KB<br />
	[  304.630989] sgpool-64                218KB        218KB<br />
	[  304.636223] sgpool-32                109KB        109KB<br />
	[  304.641351] sgpool-16                 62KB         62KB<br />
	[  304.646672] request_queue            111KB        111KB<br />
	[  304.651754] bio-144                  145KB        145KB<br />
	[  304.657027] biovec-max               480KB        480KB<br />
	[  304.662148] biovec-128                63KB         63KB<br />
	[  304.667417] biovec-64                126KB        126KB<br />
	[  304.672547] user_namespace            63KB         63KB<br />
	[  304.677842] skbuff_small_head        312KB        375KB<br />
	[  304.682946] skbuff_fclone_cache         63KB         63KB<br />
	[  304.688370] skbuff_head_cache        208KB        228KB<br />
	[  304.693514] exynos-iommu-lv2table         32KB         32KB<br />
	[  304.699140] file_lock_cache           40KB         40KB<br />
	[  304.704266] file_lock_ctx             32KB         32KB<br />
	[  304.709547] fsnotify_mark_connector         31KB         31KB<br />
	[  304.715184] taskstats                109KB        109KB<br />
	[  304.720452] proc_dir_entry           236KB        236KB<br />
	[  304.725576] pde_opener                31KB         31KB<br />
	[  304.730837] seq_file                  31KB         31KB<br />
	[  304.736035] sigqueue                  39KB         39KB<br />
	[  304.741180] shmem_inode_cache       2004KB       2030KB<br />
	[  304.746442] kernfs_iattrs_cache       3146KB       3146KB<br />
	[  304.751753] kernfs_node_cache       6333KB       6343KB<br />
	[  304.757073] filp                     864KB       1019KB<br />
	[  304.762151] names_cache              256KB        256KB<br />
	[  304.767419] net_namespace            125KB        125KB<br />
	[  304.772549] lsm_file_cache            67KB         72KB<br />
	[  304.777824] key_jar                   70KB         70KB<br />
	[  304.782940] uts_namespace             63KB         63KB<br />
	[  304.788213] nsproxy                   31KB         31KB<br />
	[  304.793346] vm_area_struct          1081KB       1173KB<br />
	[  304.798581] files_cache               72KB         72KB<br />
	[  304.803737] signal_cache             598KB        598KB<br />
	[  304.808983] sighand_cache            661KB        661KB<br />
	[  304.814138] task_struct             1235KB       1320KB<br />
	[  304.819399] cred_jar                 180KB        216KB<br />
	[  304.824542] anon_vma_chain           468KB        528KB<br />
	[  304.829773] anon_vma                 426KB        463KB<br />
	[  304.834931] pid                       68KB         68KB<br />
	[  304.840203] trace_event_file         151KB        151KB<br />
	[  304.845344] maple_node               464KB        808KB<br />
	[  304.850612] task_group               128KB        128KB<br />
	[  304.855731] mm_struct                158KB        158KB<br />
	[  304.861015] vmap_area                366KB        370KB<br />
	[  304.866166] kmalloc-cg-4k            448KB        448KB<br />
	[  304.871325] kmalloc-cg-2k            384KB        384KB<br />
	[  304.876563] kmalloc-cg-1k            704KB        768KB<br />
	[  304.881725] kmalloc-cg-512           374KB        432KB<br />
	[  304.886969] kmalloc-cg-256            72KB         72KB<br />
	[  304.892123] kmalloc-cg-192            51KB         51KB<br />
	[  304.897382] kmalloc-cg-128            60KB         60KB<br />
	[  304.902525] kmalloc-cg-64            170KB        180KB<br />
	[  304.907768] kmalloc-8k              7424KB       7424KB<br />
	[  304.912923] kmalloc-4k               928KB        928KB<br />
	[  304.918165] kmalloc-2k              1268KB       1344KB<br />
	[  304.923325] kmalloc-1k              2926KB       3008KB<br />
	[  304.928567] kmalloc-512             2050KB       2080KB<br />
	[  304.933723] kmalloc-256             1158KB       1168KB<br />
	[  304.938971] kmalloc-192              478KB        492KB<br />
	[  304.944136] kmalloc-128             1194KB       1260KB<br />
	[  304.949372] kmalloc-64            653364KB     653364KB<br />
	[  304.954516] kmem_cache_node           28KB         28KB<br />
	[  304.959773] kmem_cache                47KB         47KB<br />
	[  304.964916] Tasks state (memory values in pages):<br />
	[  304.969653] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name<br />
	[  304.978284] [    290]     0   290     6504     2244    24576        0          -250 systemd-journal<br />
	[  304.987251] [    345]     0   345     7622     2112    26624        0         -1000 systemd-udevd<br />
	[  304.996090] [    621]   109   621     1262      576    10240        0             0 rpcbind<br />
	[  305.004345] [    743]     0   743      904      288    10240        0             0 blkmapd<br />
	[  305.012710] [    758]     0   758      882      544     8192        0             0 nfsdcld<br />
	[  305.021023] [    773]   121   773     4490     1888    22528        0             0 systemd-network<br />
	[  305.030040] [    855]   108   855     1839      800    14336        0             0 avahi-daemon<br />
	[  305.038786] [    871]   107   871     2123     1112    14336        0          -900 dbus-daemon<br />
	[  305.047449] [    886]     0   886      840      576     8192        0             0 fsidd<br />
	[  305.055556] [    908]     0   908    13970     1141    36864        0             0 rsyslogd<br />
	[  305.064019] [    911]     0   911     3738     1664    20480        0             0 systemd-logind<br />
	[  305.072933] [    913]     0   913     2821      342    16384        0             0 saslauthd<br />
	[  305.081425] [    914]     0   914     2821      279    16384        0             0 saslauthd<br />
	[  305.089915] [    916]     0   916     2821      247    16384        0             0 saslauthd<br />
	[  305.098397] [    917]     0   917     2821      247    16384        0             0 saslauthd<br />
	[  305.106909] [    918]     0   918     2821      247    16384        0             0 saslauthd<br />
	[  305.115348] [    920]     0   920    19395     2560    47104        0             0 udisksd<br />
	[  305.123721] [    957]     0   957     6717      352    18432        0         -1000 lxcfs<br />
	[  305.131860] [    970]   108   970     1767      384    14336        0             0 avahi-daemon<br />
	[  305.140671] [   1030]     0  1030    65798     8690   180224        0             0 fail2ban-server<br />
	[  305.149628] [   1037]     0  1037     1172      416    10240        0             0 lxc-monitord<br />
	[  305.158389] [   1050]   124  1050    22565     1024    40960        0             0 memcached<br />
	[  305.166886] [   1066]   995  1066    11986     1408    32768        0             0 polkitd<br />
	[  305.175142] [   1114]     0  1114   174702     8288    94208        0          -999 containerd<br />
	[  305.183780] [   1116]     0  1116     1733      640    12288        0             0 upsmon<br />
	[  305.192014] [   1140]     0  1140     2278     1504    14336        0         -1000 sshd<br />
	[  305.200056] [   1147]   113  1147     2410      960    16384        0             0 upsmon<br />
	[  305.208300] [   1255]     0  1255     1053      480    10240        0             0 rpc.idmapd<br />
	[  305.216896] [   1282]     0  1282    35552    31715   151552        0             0 spamd<br />
	[  305.224966] [   1287]     0  1287     1531      288    12288        0             0 rpc.mountd<br />
	[  305.233616] [   1322]   100  1322     3657      389    18432        0             0 dnsmasq<br />
	[  305.241923] [   1362]   132  1362     2994     1568    18432        0             0 mosquitto<br />
	[  305.250414] [   1379]   100  1379     3657      388    18432        0             0 dnsmasq<br />
	[  305.258749] [   1396]   103  1396      964      321    10240        0             0 rpc.statd<br />
	[  305.267220] [   1422]   116  1422     5139     4580    28672        0             0 ntpd<br />
	[  305.275223] [   1434]     0  1434    19324     3328    59392        0             0 nmbd<br />
	[  305.283345] [   1763]     0  1763     2426      704    16384        0             0 cron<br />
	[  305.291378] [   1832]     0  1832    20931     3936    63488        0             0 winbindd<br />
	[  305.299784] [   1834]     0  1834     1269      512    12288        0             0 atd<br />
	[  305.307758] [   1931]     0  1931    47640     6003    73728        0             0 apache2<br />
	[  305.316081] [   1956]     0  1956    21539     3594    65536        0             0 wb[ODROID]<br />
	[  305.324617] [   1961]    33  1961      710      289     8192        0             0 htcacheclean<br />
	[  305.333415] [   1969]     0  1969     1370      384    12288        0             0 agetty<br />
	[  305.341649] [   1973]     0  1973     3951     1088    22528        0             0 login<br />
	[  305.349791] [   1986]    33  1986    48082     4379    69632        0             0 apache2<br />
	[  305.358116] [   1988]    33  1988    48083     4379    69632        0             0 apache2<br />
	[  305.366428] [   1989]    33  1989    48079     4251    69632        0             0 apache2<br />
	[  305.374702] [   1991]    33  1991    48092     4475    69632        0             0 apache2<br />
	[  305.383071] [   1992]    33  1992    48082     4379    69632        0             0 apache2<br />
	[  305.391397] [   2065]   102  2065     8415     3959    43008        0             0 exim4<br />
	[  305.399558] [   2103]   110  2103     3610     1708    18432        0             0 fetchmail<br />
	[  305.408046] [   2110]     0  2110    10755     8126    51200        0             0 python3<br />
	[  305.416377] [   2134]     0  2134      415      352     6144        0         -1000 watchdog<br />
	[  305.424705] [   2248]     0  2248    13064     6624    51200        0             0 python3<br />
	[  305.433077] [   2257]     0  2257    10755     6785    51200        0             0 python3<br />
	[  305.441398] [   2491]     0  2491    35552    29712   151552        0             0 spamd child<br />
	[  305.450056] [   2492]     0  2492    35552    29712   151552        0             0 spamd child<br />
	[  305.458762] [   2613]     0  2613     3790     2176    20480        0           100 systemd<br />
	[  305.467036] [   2616]     0  2616     4926      721    24576        0           100 (sd-pam)<br />
	[  305.475396] [   2649]     0  2649     2656     1088    16384        0             0 bash<br />
	[  305.483514] [   2767]    33  2767    48077     4443    69632        0             0 apache2<br />
	[  305.491835] [   2888]     0  2888    20931     1664    59392        0             0 wb-idmap<br />
	[  305.500254] [   2896] 61789  2896    14074     1088    34816        0             0 cockpit-tls<br />
	[  305.508883] [   2906] 63714  2906    11447     1309    28672        0             0 cockpit-ws<br />
	[  305.517460] [   2915]     0  2915     2736      992    18432        0             0 cockpit-session<br />
	[  305.526480] [   2921]  1000  2921     1487      769    10240        0             0 ssh-agent<br />
	[  305.534926] [   2926]  1000  2926     3827     2240    22528        0           100 systemd<br />
	[  305.543291] [   2928]  1000  2928     5028      755    24576        0           100 (sd-pam)<br />
	[  305.551705] [   2948]  1000  2948     1305      576    10240        0           200 mpris-proxy<br />
	[  305.560357] [   2950]  1000  2950     1979      992    14336        0           200 dbus-daemon<br />
	[  305.569021] [   2951]  1000  2951    16036     5811    53248        0             0 cockpit-bridge<br />
	[  305.577953] [   2953]  1000  2953     5086     1472    26624        0             0 sudo<br />
	[  305.586020] [   2967]     0  2967     8712     5425    40960        0             0 cockpit-bridge<br />
	[  305.594891] [   2974]     0  2974     2995     1280    18432        0             0 systemd-timedat<br />
	[  305.603990] [   2986]     0  2986    22409     5029    67584        0             0 packagekitd<br />
	[  305.612624] [   3002]     0  3002     1615      448    12288        0             0 dmesg<br />
	[  305.620765] Kernel panic - not syncing: Out of memory: system-wide panic_on_oom is enabled<br />
	[  305.628949] CPU: 7 PID: 1322 Comm: dnsmasq Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.636569] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.642638]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.647836]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.652862]  dump_stack_lvl from panic+0x118/0x32c<br />
	[  305.657628]  panic from out_of_memory+0x2d0/0x344<br />
	[  305.662308]  out_of_memory from __alloc_pages+0xcd4/0x122c<br />
	[  305.667769]  __alloc_pages from __get_free_pages+0x14/0x24<br />
	[  305.673221]  __get_free_pages from __pollwait+0xa8/0xf8<br />
	[  305.678425]  __pollwait from datagram_poll+0x28/0xfc<br />
	[  305.683364]  datagram_poll from udp_poll+0x10/0x88<br />
	[  305.688134]  udp_poll from sock_poll+0x50/0xd0<br />
	[  305.692548]  sock_poll from do_sys_poll+0x350/0x5e8<br />
	[  305.697401]  do_sys_poll from sys_poll+0x40/0x110<br />
	[  305.702079]  sys_poll from ret_fast_syscall+0x0/0x54<br />
	[  305.707017] Exception stack(0xf2795fa8 to 0xf2795ff0)<br />
	[  305.712045] 5fa0:                   00000000 00000000 00551a40 00000018 ffffffff 00000000<br />
	[  305.720196] 5fc0: 00000000 00000000 00000000 000000a8 00000019 ffffffff 00545430 bea589e8<br />
	[  305.728336] 5fe0: 000000a8 bea58958 b6bdeb49 b6b9f736<br />
	[  305.733371] CPU1: stopping<br />
	[  305.733393] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.733407] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.733420]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.733455]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.733475]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.733495]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.733515]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.733539]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.733566]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.733590]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.733608]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  305.733634]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  305.733653] Exception stack(0xf08b9f50 to 0xf08b9f98)<br />
	[  305.733666] 9f40:                                     000846d4 00000001 00000001 00000000<br />
	[  305.733678] 9f60: c1963200 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  305.733690] 9f80: c1355390 f08b9fa0 c0c875e4 c0c884fc 60070013 ffffffff<br />
	[  305.733698]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  305.733718]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  305.733743]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  305.733765]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  305.733787]  secondary_start_kernel from 0x40101340<br />
	[  305.733835] CPU0: stopping<br />
	[  305.733844] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.733855] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.733863]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.733887]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.733904]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.733923]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.733942]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.733962]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.733985]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.734007]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.734025]  generic_handle_arch_irq from __irq_svc+0x88/0xc8<br />
	[  305.734042] Exception stack(0xc1201f20 to 0xc1201f68)<br />
	[  305.734057] 1f20: 0042009c 00000001 00000000 00000000 c1207900 c13379c4 c1203e54 c1203eb0<br />
	[  305.734070] 1f40: 00000000 00000000 10c5387d 00000000 c1355390 c1201f70 c0c875e4 c0c884fc<br />
	[  305.734078] 1f60: 600d0013 ffffffff<br />
	[  305.734084]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  305.734103]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  305.734124]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  305.734145]  cpu_startup_entry from rest_init+0xcc/0xd0<br />
	[  305.734166]  rest_init from arch_post_acpi_subsys_init+0x0/0x8<br />
	[  305.734193] CPU3: stopping<br />
	[  305.734202] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.734214] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.734222]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.734245]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.734262]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.734281]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.734300]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.734320]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.734343]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.734366]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.734384]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  305.734405]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  305.734424] Exception stack(0xf08c1f50 to 0xf08c1f98)<br />
	[  305.734435] 1f40:                                     0007e27c 00000001 00000003 00000000<br />
	[  305.734448] 1f60: c1964600 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  305.734459] 1f80: c1355390 f08c1fa0 c0c875e4 c0c884fc 60030013 ffffffff<br />
	[  305.734467]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  305.734486]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  305.734506]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  305.734528]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  305.734551]  secondary_start_kernel from 0x40101340<br />
	[  305.734574] CPU6: stopping<br />
	[  305.734581] CPU: 6 PID: 437 Comm: btrfs-cleaner Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.734586] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.734591]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.734602]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.734609]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.734616]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.734623]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.734632]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.734641]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.734650]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.734656]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  305.734665]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  305.734672] Exception stack(0xf1341550 to 0xf1341598)<br />
	[  305.734677] 1540:                                     c5437c4c 00000000 0000385e 0000385e<br />
	[  305.734682] 1560: c5437c38 c5437c4c f13416f0 00000001 f134184c eef94d28 f1341738 c1f17000<br />
	[  305.734685] 1580: 00000000 f13415a0 bf1c71f4 bf1c71f4 600d0013 ffffffff<br />
	[  305.734688]  __irq_svc from try_release_extent_buffer+0x64/0x310 [btrfs]<br />
	[  305.734807]  try_release_extent_buffer [btrfs] from btree_release_folio+0x2c/0x48 [btrfs]<br />
	[  305.734970]  btree_release_folio [btrfs] from shrink_folio_list+0x674/0xac0<br />
	[  305.735056]  shrink_folio_list from shrink_lruvec+0x638/0xc04<br />
	[  305.735063]  shrink_lruvec from shrink_node+0x374/0x808<br />
	[  305.735069]  shrink_node from do_try_to_free_pages+0x150/0x588<br />
	[  305.735076]  do_try_to_free_pages from try_to_free_pages+0x130/0x2d4<br />
	[  305.735082]  try_to_free_pages from __alloc_pages+0x4d8/0x122c<br />
	[  305.735090]  __alloc_pages from __filemap_get_folio+0xc8/0x2dc<br />
	[  305.735106]  __filemap_get_folio from pagecache_get_page+0xc/0x3c<br />
	[  305.735117]  pagecache_get_page from alloc_extent_buffer+0x220/0x620 [btrfs]<br />
	[  305.735204]  alloc_extent_buffer [btrfs] from read_tree_block+0x20/0x8c [btrfs]<br />
	[  305.735365]  read_tree_block [btrfs] from read_block_for_search+0x234/0x334 [btrfs]<br />
	[  305.735526]  read_block_for_search [btrfs] from btrfs_search_slot+0x2f4/0xc08 [btrfs]<br />
	[  305.735685]  btrfs_search_slot [btrfs] from find_parent_nodes+0x104/0x2034 [btrfs]<br />
	[  305.735845]  find_parent_nodes [btrfs] from btrfs_find_all_roots_safe+0x88/0x130 [btrfs]<br />
	[  305.736005]  btrfs_find_all_roots_safe [btrfs] from btrfs_qgroup_trace_extent_post+0x78/0xb4 [btrfs]<br />
	[  305.736166]  btrfs_qgroup_trace_extent_post [btrfs] from btrfs_qgroup_trace_leaf_items+0x118/0x14c [btrfs]<br />
	[  305.736326]  btrfs_qgroup_trace_leaf_items [btrfs] from btrfs_qgroup_trace_subtree+0x1c4/0x314 [btrfs]<br />
	[  305.736486]  btrfs_qgroup_trace_subtree [btrfs] from do_walk_down+0x648/0x6cc [btrfs]<br />
	[  305.736646]  do_walk_down [btrfs] from walk_down_tree+0xc8/0x110 [btrfs]<br />
	[  305.736805]  walk_down_tree [btrfs] from btrfs_drop_snapshot+0x1bc/0xa48 [btrfs]<br />
	[  305.736963]  btrfs_drop_snapshot [btrfs] from btrfs_clean_one_deleted_snapshot+0x9c/0xe0 [btrfs]<br />
	[  305.737122]  btrfs_clean_one_deleted_snapshot [btrfs] from cleaner_kthread+0x7c/0x15c [btrfs]<br />
	[  305.737281]  cleaner_kthread [btrfs] from kthread+0x110/0x12c<br />
	[  305.737368]  kthread from ret_from_fork+0x14/0x28<br />
	[  305.737374] Exception stack(0xf1341fb0 to 0xf1341ff8)<br />
	[  305.737378] 1fa0:                                     00000000 00000000 00000000 00000000<br />
	[  305.737382] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000<br />
	[  305.737386] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000<br />
	[  305.737390] CPU2: stopping<br />
	[  305.737400] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.737412] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.737420]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.737444]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.737461]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.737479]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.737499]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.737518]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.737541]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.737564]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.737582]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  305.737603]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  305.737622] Exception stack(0xf08bdf50 to 0xf08bdf98)<br />
	[  305.737633] df40:                                     00083ad4 00000001 00000002 00000000<br />
	[  305.737646] df60: c1963c00 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  305.737657] df80: c1355390 f08bdfa0 c0c875e4 c0c884fc 600d0013 ffffffff<br />
	[  305.737665]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  305.737684]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  305.737704]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  305.737726]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  305.737749]  secondary_start_kernel from 0x40101340<br />
	[  305.737772] CPU4: stopping<br />
	[  305.737777] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.737782] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.737786]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.737795]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.737802]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.737809]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.737816]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.737824]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.737832]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.737841]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.737847]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  305.737855]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  305.737862] Exception stack(0xf08c5f50 to 0xf08c5f98)<br />
	[  305.737867] 5f40:                                     000ee534 00000001 00000004 00000000<br />
	[  305.737872] 5f60: c1965000 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  305.737876] 5f80: c1355390 f08c5fa0 c0c875e4 c0c884fc 60000013 ffffffff<br />
	[  305.737878]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  305.737886]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  305.737895]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  305.737904]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  305.737912]  secondary_start_kernel from 0x40101340<br />
	[  305.737935] CPU5: stopping<br />
	[  305.737938] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  305.737944] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  305.737947]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  305.737957]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  305.737963]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  305.737970]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  305.737977]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  305.737985]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  305.737993]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  305.738002]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  305.738009]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  305.738016]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  305.738024] Exception stack(0xf08c9f50 to 0xf08c9f98)<br />
	[  305.738028] 9f40:                                     000e6c5c 00000001 00000005 00000000<br />
	[  305.738033] 9f60: c1965a00 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  305.738036] 9f80: c1355390 f08c9fa0 c0c875e4 c0c884fc 600d0013 ffffffff<br />
	[  305.738039]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  305.738046]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  305.738055]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  305.738064]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  305.738072]  secondary_start_kernel from 0x40101340<br />
	[  306.802472] ---[ end Kernel panic - not syncing: Out of memory: system-wide panic_on_oom is enabled ]---
</p>

<p>
	[  279.613717] f2b/f.ADSL-sysl invoked oom-killer: gfp_mask=0xcc0(GFP_KERNEL), order=2, oom_score_adj=0<br />
	[  279.621431] CPU: 4 PID: 5055 Comm: f2b/f.ADSL-sysl Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  279.629697] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  279.635770]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  279.640972]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  279.646004]  dump_stack_lvl from dump_header+0x4c/0x208<br />
	[  279.651194]  dump_header from out_of_memory+0x2a8/0x344<br />
	[  279.656399]  out_of_memory from __alloc_pages+0xcd4/0x122c<br />
	[  279.661856]  __alloc_pages from __get_free_pages+0x14/0x24<br />
	[  279.667314]  __get_free_pages from pgd_alloc+0x14/0x138<br />
	[  279.672512]  pgd_alloc from mm_init+0xfc/0x274<br />
	[  279.676930]  mm_init from alloc_bprm+0x88/0x2b0<br />
	[  279.681439]  alloc_bprm from do_execveat_common+0x6c/0x1d8<br />
	[  279.686896]  do_execveat_common from sys_execve+0x30/0x38<br />
	[  279.692267]  sys_execve from ret_fast_syscall+0x0/0x54<br />
	[  279.697378] Exception stack(0xf3115fa8 to 0xf3115ff0)<br />
	[  279.702409] 5fa0:                   00000001 00000000 b1200a50 b0f86f00 beb4dd28 004a9640<br />
	[  279.710552] 5fc0: 00000001 00000000 00000000 0000000b 00000000 b0f86f00 b1200a30 b1200af0<br />
	[  279.718697] 5fe0: b6dfc2e9 aabfe464 0020585d b6dfc308<br />
	[  279.723875] Mem-Info:<br />
	[  279.725983] active_anon:6164 inactive_anon:88963 isolated_anon:0<br />
	[  279.725983]  active_file:24159 inactive_file:59714 isolated_file:0<br />
	[  279.725983]  unevictable:4754 dirty:0 writeback:0<br />
	[  279.725983]  slab_reclaimable:6042 slab_unreclaimable:176972<br />
	[  279.725983]  mapped:29134 shmem:2208 pagetables:1687<br />
	[  279.725983]  sec_pagetables:0 bounce:0<br />
	[  279.725983]  kernel_misc_reclaimable:0<br />
	[  279.725983]  free:127704 free_pcp:185 free_cma:26532<br />
	[  279.765847] Node 0 active_anon:24656kB inactive_anon:355852kB active_file:96336kB inactive_file:238908kB unevictable:19016kB isolated(anon):0kB isolated(file):0kB mapped:116536kB dirty:0kB writeback:0kB shmem:8832kB writeback_tmp:0kB kernel_stack:3200kB pagetables:6748kB sec_pagetables:0kB all_unreclaimable? no<br />
	[  279.793274] Normal free:3648kB boost:0kB min:3416kB low:4268kB high:5120kB reserved_highatomic:0KB active_anon:4kB inactive_anon:0kB active_file:1236kB inactive_file:312kB unevictable:0kB writepending:0kB present:786432kB managed:748292kB mlocked:0kB bounce:0kB free_pcp:164kB local_pcp:0kB free_cma:0kB<br />
	[  279.819959] lowmem_reserve[]: 0 10064 10064<br />
	[  279.824059] Normal: 350*4kB (UME) 166*8kB (UME) 39*16kB (UME) 1*32kB (U) 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 3384kB<br />
	[  279.837362] 88139 total pagecache pages<br />
	[  279.841129] 14 pages in swap cache<br />
	[  279.844507] Free swap  = 6006988kB<br />
	[  279.847927] Total swap = 6011596kB<br />
	[  279.851268] 518656 pages RAM<br />
	[  279.854125] 322048 pages HighMem/MovableOnly<br />
	[  279.858418] 9535 pages reserved<br />
	[  279.861492] 32768 pages cma reserved<br />
	[  279.865046] Tasks state (memory values in pages):<br />
	[  279.869806] [  pid  ]   uid  tgid total_vm      rss pgtables_bytes swapents oom_score_adj name<br />
	[  279.878471] [    290]     0   290     5804     1410    24576        0          -250 systemd-journal<br />
	[  279.887405] [    344]     0   344     7617     1841    24576        0         -1000 systemd-udevd<br />
	[  279.896248] [    661]   109   661     1262      576    12288        0             0 rpcbind<br />
	[  279.904482] [    683]     0   683      904      288    10240        0             0 blkmapd<br />
	[  279.912871] [    685]     0   685      882      512     8192        0             0 nfsdcld<br />
	[  279.921175] [    745]   121   745     4490     1856    24576        0             0 systemd-network<br />
	[  279.930190] [    819]   108   819     1801      800    14336        0             0 avahi-daemon<br />
	[  279.938933] [    840]   107   840     2130     1054    14336        0          -900 dbus-daemon<br />
	[  279.947607] [    867]     0   867      840      576    10240        0             0 fsidd<br />
	[  279.955696] [    911]     0   911    13970      928    32768        0             0 rsyslogd<br />
	[  279.964160] [    928]     0   928     3738     1696    20480        0             0 systemd-logind<br />
	[  279.973082] [    932]     0   932     2821      359    14336        0             0 saslauthd<br />
	[  279.981646] [    935]     0   935     2821      296    14336        0             0 saslauthd<br />
	[  279.990189] [    936]     0   936     2821      264    14336        0             0 saslauthd<br />
	[  279.998636] [    937]     0   937     2821      264    14336        0             0 saslauthd<br />
	[  280.007156] [    938]     0   938     2821      264    14336        0             0 saslauthd<br />
	[  280.015498] [    939]     0   939    19396     2464    47104        0             0 udisksd<br />
	[  280.023942] [    978]     0   978     6717      352    18432        0         -1000 lxcfs<br />
	[  280.032095] [    993]   108   993     1767      384    14336        0             0 avahi-daemon<br />
	[  280.040824] [   1006]   995  1006    11986     1440    32768        0             0 polkitd<br />
	[  280.049235] [   1037]     0  1037    58269     7051   163840        0             0 fail2ban-server<br />
	[  280.058147] [   1057]     0  1057     1172      416    10240        0             0 lxc-monitord<br />
	[  280.066966] [   1078]   124  1078    22565      960    43008        0             0 memcached<br />
	[  280.075291] [   1142]     0  1142   176942     8185   100352        0          -999 containerd<br />
	[  280.084044] [   1144]     0  1144     1733      608    14336        0             0 upsmon<br />
	[  280.092243] [   1154]     0  1154     2278     1504    14336        0         -1000 sshd<br />
	[  280.100190] [   1175]   113  1175     2410     1088    16384        0             0 upsmon<br />
	[  280.108456] [   1388]     0  1388     1053      480    10240        0             0 rpc.idmapd<br />
	[  280.117011] [   1418]     0  1418    35543    31476   151552        0             0 spamd<br />
	[  280.125098] [   1423]     0  1423     1531      288    12288        0             0 rpc.mountd<br />
	[  280.133731] [   1454]   105  1454   135555    28997   221184        0         -1000 mariadbd<br />
	[  280.142135] [   1477]   100  1477     3657      389    18432        0             0 dnsmasq<br />
	[  280.150447] [   1507]   132  1507     2967     1568    18432        0             0 mosquitto<br />
	[  280.158955] [   1526]     0  1526    19324     3296    57344        0             0 nmbd<br />
	[  280.167004] [   1541]   100  1541     3657      388    18432        0             0 dnsmasq<br />
	[  280.175272] [   1570]   103  1570      964      321    10240        0             0 rpc.statd<br />
	[  280.183816] [   1584]   116  1584     5139     4578    30720        0             0 ntpd<br />
	[  280.191876] [   1671]     0  1671     2426      704    16384        0             0 cron<br />
	[  280.199930] [   1809]     0  1809     1269      512    10240        0             0 atd<br />
	[  280.207910] [   1997]     0  1997    20931     3872    67584        0             0 winbindd<br />
	[  280.216326] [   2040]     0  2040    47654     5944    73728       96             0 apache2<br />
	[  280.224584] [   2094]     0  2094     1370      416    12288        0             0 agetty<br />
	[  280.232993] [   2100]     0  2100     3951     1024    24576        0             0 login<br />
	[  280.241025] [   2119]    33  2119      710      257     8192        0             0 htcacheclean<br />
	[  280.249786] [   2144]     0  2144    21539     3530    67584        0             0 wb[ODROID]<br />
	[  280.258373] [   2260]   102  2260     8415     3872    38912        0             0 exim4<br />
	[  280.266518] [   2304]   110  2304     3610     1676    18432        0             0 fetchmail<br />
	[  280.274929] [   2375]     0  2375    10755     7998    51200        0             0 python3<br />
	[  280.283323] [   2390]     0  2390      415      352     8192        0         -1000 watchdog<br />
	[  280.291731] [   2588]     0  2588    13064     6496    51200      128             0 python3<br />
	[  280.300073] [   2590]     0  2590    10755     6625    49152      128             0 python3<br />
	[  280.308401] [   2685]     0  2685    35543    29400   147456       32             0 spamd child<br />
	[  280.317029] [   2687]     0  2687    35543    29464   147456        0             0 spamd child<br />
	[  280.325620] [   2912]     0  2912     3790     2240    20480        0           100 systemd<br />
	[  280.333993] [   2918]     0  2918     4926      743    24576       32           100 (sd-pam)<br />
	[  280.342393] [   2990]     0  2990     2656     1088    16384        0             0 bash<br />
	[  280.350448] [   3088]     0  3088    20931     1631    61440        0             0 wb-idmap<br />
	[  280.358852] [   3102] 61789  3102    14586     1152    40960        0             0 cockpit-tls<br />
	[  280.367522] [   3128] 63714  3128     9111     1142    24576        0             0 cockpit-ws<br />
	[  280.376105] [   3169]     0  3169     2736      992    18432        0             0 cockpit-session<br />
	[  280.385062] [   3175]  1000  3175     1487      769    10240        0             0 ssh-agent<br />
	[  280.393651] [   3180]  1000  3180     3827     2272    20480        0           100 systemd<br />
	[  280.401926] [   3182]  1000  3182     5028      689    28672       64           100 (sd-pam)<br />
	[  280.410324] [   3202]  1000  3202     1305      576    10240        0           200 mpris-proxy<br />
	[  280.418987] [   3204]  1000  3204     1979      960    14336        0           200 dbus-daemon<br />
	[  280.427649] [   3205]  1000  3205    18073     5453    55296        0             0 cockpit-bridge<br />
	[  280.436583] [   3208]  1000  3208     5086     1472    28672        0             0 sudo<br />
	[  280.444593] [   3215]     0  3215     8655     5263    40960        0             0 cockpit-bridge<br />
	[  280.453562] [   3233]     0  3233     2995     1280    18432        0             0 systemd-timedat<br />
	[  280.462676] [   3241]     0  3241    22428     5185    67584        0             0 packagekitd<br />
	[  280.471488] [   3275]     0  3275    17523     2243    71680        0             0 journalctl<br />
	[  280.479932] [   3318]    33  3318    48092     4351    65536      102             0 apache2<br />
	[  280.488222] [   3319]    33  3319    48092     4351    65536      102             0 apache2<br />
	[  280.496550] [   3320]    33  3320    48092     4415    65536      102             0 apache2<br />
	[  280.504750] [   3321]    33  3321    48092     4319    65536      102             0 apache2<br />
	[  280.513206] [   3322]    33  3322    48092     4383    65536      102             0 apache2<br />
	[  280.521512] [   3350]     0  3350     1552      320    10240        0             0 sync<br />
	[  280.529561] [   4572]    33  4572    48078     3621    65536      153             0 apache2<br />
	[  280.537858] [   4580]     0  4580    21222     2851    63488        0             0 samba-dcerpcd<br />
	[  280.546792] [   4600]     0  4600    22362     4288    73728        0             0 rpcd_lsad<br />
	[  280.555100] [   4608]     0  4608    22362     4224    75776        0             0 rpcd_lsad<br />
	[  280.563734] [   5054]     0  5054    17521     2720    73728        0             0 journalctl<br />
	[  280.572303] [   5055]     0  5055    58269     3624    86016        0             0 f2b/f.ADSL-sysl<br />
	[  280.581480] Kernel panic - not syncing: Out of memory: system-wide panic_on_oom is enabled<br />
	[  280.589396] CPU: 4 PID: 5055 Comm: f2b/f.ADSL-sysl Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.597710] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.603777]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.608973]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.613999]  dump_stack_lvl from panic+0x118/0x32c<br />
	[  280.618764]  panic from out_of_memory+0x2d0/0x344<br />
	[  280.623442]  out_of_memory from __alloc_pages+0xcd4/0x122c<br />
	[  280.628904]  __alloc_pages from __get_free_pages+0x14/0x24<br />
	[  280.634361]  __get_free_pages from pgd_alloc+0x14/0x138<br />
	[  280.639560]  pgd_alloc from mm_init+0xfc/0x274<br />
	[  280.643981]  mm_init from alloc_bprm+0x88/0x2b0<br />
	[  280.648486]  alloc_bprm from do_execveat_common+0x6c/0x1d8<br />
	[  280.653946]  do_execveat_common from sys_execve+0x30/0x38<br />
	[  280.659317]  sys_execve from ret_fast_syscall+0x0/0x54<br />
	[  280.664436] Exception stack(0xf3115fa8 to 0xf3115ff0)<br />
	[  280.669457] 5fa0:                   00000001 00000000 b1200a50 b0f86f00 beb4dd28 004a9640<br />
	[  280.677604] 5fc0: 00000001 00000000 00000000 0000000b 00000000 b0f86f00 b1200a30 b1200af0<br />
	[  280.685749] 5fe0: b6dfc2e9 aabfe464 0020585d b6dfc308<br />
	[  280.690784] CPU0: stopping<br />
	[  280.690804] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.690817] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.690829]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.690861]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.690880]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.690898]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.690915]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.690937]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.690961]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.690982]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.690999]  generic_handle_arch_irq from __irq_svc+0x88/0xc8<br />
	[  280.691014] Exception stack(0xc1201f20 to 0xc1201f68)<br />
	[  280.691028] 1f20: 003d9b44 00000001 00000000 00000000 c1207900 c13379c4 c1203e54 c1203eb0<br />
	[  280.691039] 1f40: 00000000 00000000 10c5387d 00000000 c1355390 c1201f70 c0c875e4 c0c884fc<br />
	[  280.691047] 1f60: 600f0013 ffffffff<br />
	[  280.691053]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  280.691071]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  280.691093]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  280.691113]  cpu_startup_entry from rest_init+0xcc/0xd0<br />
	[  280.691131]  rest_init from arch_post_acpi_subsys_init+0x0/0x8<br />
	[  280.691178] CPU2: stopping<br />
	[  280.691187] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.691197] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.691205]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.691227]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.691242]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.691259]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.691276]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.691294]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.691314]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.691334]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.691350]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  280.691373]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  280.691390] Exception stack(0xf08bdf50 to 0xf08bdf98)<br />
	[  280.691400] df40:                                     0007df7c 00000001 00000002 00000000<br />
	[  280.691412] df60: c1963c00 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  280.691422] df80: c1355390 f08bdfa0 c0c875e4 c0c884fc 600d0013 ffffffff<br />
	[  280.691429]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  280.691445]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  280.691464]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  280.691483]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  280.691504]  secondary_start_kernel from 0x40101340<br />
	[  280.691525] CPU1: stopping<br />
	[  280.691534] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.691544] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.691552]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.691573]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.691588]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.691604]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.691621]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.691639]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.691659]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.691679]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.691695]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  280.691714]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  280.691731] Exception stack(0xf08b9f50 to 0xf08b9f98)<br />
	[  280.691742] 9f40:                                     0007daa4 00000001 00000001 00000000<br />
	[  280.691753] 9f60: c1963200 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  280.691763] 9f80: c1355390 f08b9fa0 c0c875e4 c0c884fc 600d0013 ffffffff<br />
	[  280.691770]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  280.691787]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  280.691805]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  280.691825]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  280.691845]  secondary_start_kernel from 0x40101340<br />
	[  280.691866] CPU3: stopping<br />
	[  280.691874] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.691884] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.691892]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.691913]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.691928]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.691945]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.691962]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.691980]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.692000]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.692020]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.692037]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  280.692055]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  280.692072] Exception stack(0xf08c1f50 to 0xf08c1f98)<br />
	[  280.692082] 1f40:                                     0007401c 00000001 00000003 00000000<br />
	[  280.692094] 1f60: c1964600 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  280.692104] 1f80: c1355390 f08c1fa0 c0c875e4 c0c884fc 600d0013 ffffffff<br />
	[  280.692111]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  280.692127]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  280.692146]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  280.692165]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  280.692185]  secondary_start_kernel from 0x40101340<br />
	[  280.692206] CPU6: stopping<br />
	[  280.692212] CPU: 6 PID: 438 Comm: btrfs-cleaner Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.692218] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.692222]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.692234]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.692241]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.692249]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.692257]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.692267]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.692278]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.692287]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.692294]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  280.692304]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  280.692312] Exception stack(0xf10b1750 to 0xf10b1798)<br />
	[  280.692317] 1740:                                     cb9d4028 2dc3d000 00319e67 0000b8b5<br />
	[  280.692322] 1760: c1184030 00000004 f10b181c 00000084 00000001 00000004 f10b194c 00000000<br />
	[  280.692326] 1780: c1283464 f10b17a0 c0300d68 c0c926c8 600d0013 ffffffff<br />
	[  280.692329]  __irq_svc from _raw_spin_unlock_irq+0x1c/0x44<br />
	[  280.692341]  _raw_spin_unlock_irq from shrink_lruvec+0x610/0xc04<br />
	[  280.692353]  shrink_lruvec from shrink_node+0x374/0x808<br />
	[  280.692360]  shrink_node from do_try_to_free_pages+0x150/0x588<br />
	[  280.692368]  do_try_to_free_pages from try_to_free_pages+0x130/0x2d4<br />
	[  280.692375]  try_to_free_pages from __alloc_pages+0x4d8/0x122c<br />
	[  280.692384]  __alloc_pages from __filemap_get_folio+0xc8/0x2dc<br />
	[  280.692396]  __filemap_get_folio from pagecache_get_page+0xc/0x3c<br />
	[  280.692408]  pagecache_get_page from alloc_extent_buffer+0x220/0x620 [btrfs]<br />
	[  280.692537]  alloc_extent_buffer [btrfs] from read_tree_block+0x20/0x8c [btrfs]<br />
	[  280.692715]  read_tree_block [btrfs] from find_parent_nodes+0x300/0x2034 [btrfs]<br />
	[  280.692894]  find_parent_nodes [btrfs] from btrfs_find_all_roots_safe+0x88/0x130 [btrfs]<br />
	[  280.693071]  btrfs_find_all_roots_safe [btrfs] from btrfs_qgroup_trace_extent_post+0x78/0xb4 [btrfs]<br />
	[  280.693249]  btrfs_qgroup_trace_extent_post [btrfs] from btrfs_qgroup_trace_leaf_items+0x118/0x14c [btrfs]<br />
	[  280.693427]  btrfs_qgroup_trace_leaf_items [btrfs] from btrfs_qgroup_trace_subtree+0x1c4/0x314 [btrfs]<br />
	[  280.693605]  btrfs_qgroup_trace_subtree [btrfs] from do_walk_down+0x648/0x6cc [btrfs]<br />
	[  280.693783]  do_walk_down [btrfs] from walk_down_tree+0xc8/0x110 [btrfs]<br />
	[  280.693959]  walk_down_tree [btrfs] from btrfs_drop_snapshot+0x1bc/0xa48 [btrfs]<br />
	[  280.694135]  btrfs_drop_snapshot [btrfs] from btrfs_clean_one_deleted_snapshot+0x9c/0xe0 [btrfs]<br />
	[  280.694312]  btrfs_clean_one_deleted_snapshot [btrfs] from cleaner_kthread+0x7c/0x15c [btrfs]<br />
	[  280.694490]  cleaner_kthread [btrfs] from kthread+0x110/0x12c<br />
	[  280.694586]  kthread from ret_from_fork+0x14/0x28<br />
	[  280.694592] Exception stack(0xf10b1fb0 to 0xf10b1ff8)<br />
	[  280.694596] 1fa0:                                     00000000 00000000 00000000 00000000<br />
	[  280.694601] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000<br />
	[  280.694604] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000<br />
	[  280.694609] CPU5: stopping<br />
	[  280.694614] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.694620] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.694623]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.694634]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.694641]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.694649]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.694657]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.694665]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.694675]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.694684]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.694691]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  280.694700]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  280.694708] Exception stack(0xf08c9f50 to 0xf08c9f98)<br />
	[  280.694713] 9f40:                                     000c49ac 00000001 00000005 00000000<br />
	[  280.694718] 9f60: c1965a00 c13379c4 c1203e54 c1203eb0 00000000 00000000 00000000 00000000<br />
	[  280.694722] 9f80: c1355390 f08c9fa0 c0c875e4 c0c884fc 60030013 ffffffff<br />
	[  280.694725]  __irq_svc from default_idle_call+0x50/0x110<br />
	[  280.694733]  default_idle_call from do_idle+0x28c/0x2f0<br />
	[  280.694744]  do_idle from cpu_startup_entry+0x28/0x2c<br />
	[  280.694753]  cpu_startup_entry from secondary_start_kernel+0x190/0x220<br />
	[  280.694763]  secondary_start_kernel from 0x40101340<br />
	[  280.694786] CPU7: stopping<br />
	[  280.694791] CPU: 7 PID: 90 Comm: kswapd0 Not tainted 6.6.141-current-odroidxu4 #1<br />
	[  280.694797] Hardware name: Samsung Exynos (Flattened Device Tree)<br />
	[  280.694800]  unwind_backtrace from show_stack+0x10/0x14<br />
	[  280.694811]  show_stack from dump_stack_lvl+0x40/0x4c<br />
	[  280.694818]  dump_stack_lvl from do_handle_IPI+0x1e8/0x210<br />
	[  280.694826]  do_handle_IPI from ipi_handler+0x18/0x20<br />
	[  280.694834]  ipi_handler from handle_percpu_devid_irq+0x8c/0x238<br />
	[  280.694842]  handle_percpu_devid_irq from handle_irq_desc+0x50/0x80<br />
	[  280.694851]  handle_irq_desc from gic_handle_irq+0x88/0xa8<br />
	[  280.694861]  gic_handle_irq from generic_handle_arch_irq+0x34/0x44<br />
	[  280.694868]  generic_handle_arch_irq from call_with_stack+0x18/0x20<br />
	[  280.694877]  call_with_stack from __irq_svc+0x98/0xc8<br />
	[  280.694885] Exception stack(0xf0cb1d30 to 0xf0cb1d78)<br />
	[  280.694890] 1d20:                                     cd500828 2dc4f000 2dc4f000 00007907<br />
	[  280.694895] 1d40: c11840bc 00000020 f0cb1dfc 00000000 00000001 00000020 f0cb1f10 00000000<br />
	[  280.694900] 1d60: c1283464 f0cb1d80 c0300e20 c0c926c8 600d0013 ffffffff<br />
	[  280.694903]  __irq_svc from _raw_spin_unlock_irq+0x1c/0x44<br />
	[  280.694914]  _raw_spin_unlock_irq from shrink_lruvec+0x6c8/0xc04<br />
	[  280.694924]  shrink_lruvec from shrink_node+0x374/0x808<br />
	[  280.694931]  shrink_node from kswapd+0x4c8/0xae0<br />
	[  280.694938]  kswapd from kthread+0x110/0x12c<br />
	[  280.694945]  kthread from ret_from_fork+0x14/0x28<br />
	[  280.694951] Exception stack(0xf0cb1fb0 to 0xf0cb1ff8)<br />
	[  280.694956] 1fa0:                                     00000000 00000000 00000000 00000000<br />
	[  280.694960] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000<br />
	[  280.694964] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000<br />
	[  281.758837] ---[ end Kernel panic - not syncing: Out of memory: system-wide panic_on_oom is enabled ]---
</p>
]]></description><guid isPermaLink="false">62011</guid><pubDate>Tue, 08 Sep 2026 07:43:31 +0000</pubDate></item><item><title>bug:  btrfs hits 16T page cache limit on 1T drive</title><link>https://testforum.armbian.com/topic/59928-bug-btrfs-hits-16t-page-cache-limit-on-1t-drive/</link><description><![CDATA[<p>
	I attempted to file a bug using `reportbug`, but since the kernel package is from Armbian and the report went to Debian, I assume that is a dead end.
</p>

<p>
	 
</p>

<p>
	<a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137721" rel="external nofollow">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1137721</a>
</p>

<p>
	 
</p>

<p>
	I will mostly copy/paste from that report, here, but I also ran `armbianmonitor -u`.
</p>

<p>
	 
</p>

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

<p>
	 
</p>

<p>
	 
</p>

<p>
	I run a home backup server with a 1TB SSD attached to an ODroid HC1 board. There is no redundancy, but I do keep a limited history of snapshots, taken hourly and trimmed down to a small number of hourly, daily, weekly, monthly, and yearly snapshots. There should be at most about 20 snapshots existing at a time. I have a daily cron job to run a balance operation. The mount point is `/backup` . Relevant line from /etc/fstab:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">/dev/mapper/backup /backup btrfs noatime,noauto,nodev,nosuid,noexec,compress=zlib:9 0 0</span></pre>

<p>
	 
</p>

<p>
	Command used for daily balance:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">btrfs balance start --full-balance '/backup'</span></pre>

<p>
	 
</p>

<p>
	The filesystem only seems to be about half full:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">ansible@backup:~ $ sudo btrfs filesystem df --si /backup
Data, single: total=430.57GB, used=428.24GB
System, DUP: total=67.11MB, used=81.92kB
Metadata, DUP: total=3.22GB, used=2.48GB
GlobalReserve, single: total=536.87MB, used=49.15kB
ansible@backup:~ $</span></pre>

<p>
	 
</p>

<p>
	My best understanding is that the messages that follow indicate that something is attempting to address space beyond 16TB, and that seems like a bug because my disk is only 1TB total. I would appreciate anyone with a firmer grasp of the topic at least confirming whether that is an accurate reading of the warnings and errors. If not, I might suggest that the warnings and errors could be improved, but I am open to correction if I just failed to understand what they are telling me.
</p>

<p>
	 
</p>

<p>
	The problem seems to be triggered by any attempt to rebalance metadata or system data with a usage limit of 1 or higher. Excerpt from a command session:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">ansible@backup:~ $ time sudo btrfs balance start -musage=1 /backup; echo $?
ERROR: error during balancing '/backup': Read-only file system
There may be more info in syslog - try dmesg | tail

real    0m0.304s
user    0m0.040s
sys     0m0.082s
1
ansible@backup:~ $ sudo umount /backup &amp;&amp; sudo mount -o skip_balance /backup &amp;&amp; sudo btrfs balance cancel /backup
ansible@backup:~ $ time sudo btrfs balance start -f -susage=1 /backup; echo $?
ERROR: error during balancing '/backup': Read-only file system
There may be more info in syslog - try dmesg | tail

real    0m0.321s
user    0m0.023s
sys     0m0.096s
1
ansible@backup:~ $ </span></pre>

<p>
	 
</p>

<p>
	Excerpt from dmesg from that time:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">[114023.693265] BTRFS info (device dm-0): balance: start -musage=1 -susage=1
[114023.695656] BTRFS error (device dm-0): extent buffer 18905857064960 is beyond 32bit page cache limit
[114023.695669] BTRFS error (device dm-0): reached 32bit limit for logical addresses
[114023.695677] BTRFS error (device dm-0): due to page cache limit on 32bit systems, metadata beyond 16T can't be accessed
[114023.695686] BTRFS error (device dm-0): please consider upgrading to 64bit kernel/hardware
[114023.695699] ------------[ cut here ]------------
[114023.695706] WARNING: CPU: 4 PID: 30371 at fs/btrfs/space-info.h:208 btrfs_space_info_update_bytes_may_use+0x9c/0x1c0 [btrfs]
[114023.695813] Modules linked in: aes_arm_bs crypto_simd dm_crypt cpufreq_conservative cpufreq_userspace cpufreq_powersave sunrpc zram zsmalloc binfmt_misc evdev sg nfnetlink ip_tables x_tables ipv6 autofs4 btrfs blake2b_generic xor xor_neon raid6_pq li
bcrc32c sd_mod t10_pi crc64_rocksoft uas usb_storage scsi_mod scsi_common gpio_keys
[114023.695959] CPU: 4 PID: 30371 Comm: btrfs Tainted: G        W          6.6.122-current-odroidxu4 #1
[114023.695969] Hardware name: Samsung Exynos (Flattened Device Tree)
[114023.695980]  unwind_backtrace from show_stack+0x10/0x14
[114023.696000]  show_stack from dump_stack_lvl+0x40/0x4c
[114023.696014]  dump_stack_lvl from __warn+0x78/0x154
[114023.696025]  __warn from warn_slowpath_fmt+0x1b4/0x1bc
[114023.696035]  warn_slowpath_fmt from btrfs_space_info_update_bytes_may_use+0x9c/0x1c0 [btrfs]
[114023.696127]  btrfs_space_info_update_bytes_may_use [btrfs] from btrfs_block_rsv_release+0x1f4/0x2f4 [btrfs]
[114023.696300]  btrfs_block_rsv_release [btrfs] from btrfs_alloc_tree_block+0x118/0x6b4 [btrfs]
[114023.696465]  btrfs_alloc_tree_block [btrfs] from btrfs_force_cow_block+0x148/0xa60 [btrfs]
[114023.696628]  btrfs_force_cow_block [btrfs] from btrfs_cow_block+0xe4/0x2bc [btrfs]
[114023.696792]  btrfs_cow_block [btrfs] from btrfs_search_slot+0x6dc/0xc08 [btrfs]
[114023.696957]  btrfs_search_slot [btrfs] from btrfs_update_device+0xa4/0x248 [btrfs]
[114023.697122]  btrfs_update_device [btrfs] from btrfs_chunk_alloc_add_chunk_item+0xcc/0x638 [btrfs]
[114023.697287]  btrfs_chunk_alloc_add_chunk_item [btrfs] from reserve_chunk_space+0xec/0x180 [btrfs]
[114023.697451]  reserve_chunk_space [btrfs] from check_system_chunk+0x6c/0x74 [btrfs]
[114023.697615]  check_system_chunk [btrfs] from btrfs_inc_block_group_ro+0x228/0x234 [btrfs]
[114023.697780]  btrfs_inc_block_group_ro [btrfs] from btrfs_relocate_block_group+0x94/0x48c [btrfs]
[114023.697945]  btrfs_relocate_block_group [btrfs] from btrfs_relocate_chunk+0x3c/0x180 [btrfs]
[114023.698108]  btrfs_relocate_chunk [btrfs] from btrfs_balance+0x864/0x13b8 [btrfs]
[114023.698272]  btrfs_balance [btrfs] from btrfs_ioctl+0x248c/0x28c4 [btrfs]
[114023.698436]  btrfs_ioctl [btrfs] from sys_ioctl+0x288/0xc60
[114023.698533]  sys_ioctl from ret_fast_syscall+0x0/0x54
[114023.698547] Exception stack(0xf2575fa8 to 0xf2575ff0)
[114023.698556] 5fa0:                   00000000 00000003 00000003 c4009420 bebe7fd0 bebe7f70
[114023.698565] 5fc0: 00000000 00000003 bebe7fd0 00000036 005bfb78 bebe86f4 00000001 0058b190
[114023.698572] 5fe0: 00000036 bebe7f58 b6d718b1 b6cdf736
[114023.698580] ---[ end trace 0000000000000000 ]---
[114023.698802] BTRFS error (device dm-0): extent buffer 18905857064960 is beyond 32bit page cache limit
[114023.698821] ------------[ cut here ]------------
[114023.698827] WARNING: CPU: 4 PID: 30371 at fs/btrfs/block-group.c:2783 btrfs_create_pending_block_groups+0x674/0x67c [btrfs]
[114023.698925] BTRFS: Transaction aborted (error -75)
[114064.918054] Modules linked in: aes_arm_bs crypto_simd dm_crypt cpufreq_conservative cpufreq_userspace cpufreq_powersave sunrpc zram zsmalloc binfmt_misc evdev sg nfnetlink ip_tables x_tables ipv6 autofs4 btrfs blake2b_generic xor xor_neon raid6_pq libcrc32c sd_mod t10_pi crc64_rocksoft uas usb_storage scsi_mod scsi_common gpio_keys
[114064.918234] CPU: 5 PID: 30410 Comm: btrfs Tainted: G        W          6.6.122-current-odroidxu4 #1
[114064.918245] Hardware name: Samsung Exynos (Flattened Device Tree)
[114064.918256]  unwind_backtrace from show_stack+0x10/0x14
[114064.918272]  show_stack from dump_stack_lvl+0x40/0x4c
[114064.918284]  dump_stack_lvl from __warn+0x78/0x154
[114064.918296]  __warn from warn_slowpath_fmt+0x130/0x1bc
[114064.918307]  warn_slowpath_fmt from btrfs_create_pending_block_groups+0x674/0x67c [btrfs]
[114064.918399]  btrfs_create_pending_block_groups [btrfs] from __btrfs_end_transaction+0x38/0x2a0 [btrfs]
[114064.918567]  __btrfs_end_transaction [btrfs] from btrfs_inc_block_group_ro+0x1f0/0x234 [btrfs]
[114064.918733]  btrfs_inc_block_group_ro [btrfs] from btrfs_relocate_block_group+0x94/0x48c [btrfs]
[114064.918899]  btrfs_relocate_block_group [btrfs] from btrfs_relocate_chunk+0x3c/0x180 [btrfs]
[114064.919065]  btrfs_relocate_chunk [btrfs] from btrfs_balance+0x864/0x13b8 [btrfs]
[114064.919231]  btrfs_balance [btrfs] from btrfs_ioctl+0x248c/0x28c4 [btrfs]
[114064.919397]  btrfs_ioctl [btrfs] from sys_ioctl+0x288/0xc60
[114064.919491]  sys_ioctl from ret_fast_syscall+0x0/0x54
[114064.919505] Exception stack(0xf26b9fa8 to 0xf26b9ff0)
[114064.919516] 9fa0:                   00000000 00000003 00000003 c4009420 beae9fc0 beae9f60
[114064.919527] 9fc0: 00000000 00000003 beae9fc0 00000036 0057fb78 beaea6f1 00000001 0054b190
[114064.919537] 9fe0: 00000036 beae9f48 b6d118b1 b6c7f736
[114064.919614] ---[ end trace 0000000000000000 ]---
[114064.919632] BTRFS: error (device dm-0: state A) in btrfs_create_pending_block_groups:2783: errno=-75 unknown
[114064.919647] BTRFS info (device dm-0: state EA): forced readonly
[114064.920025] ------------[ cut here ]------------
[114064.920039] WARNING: CPU: 5 PID: 30410 at fs/btrfs/space-info.h:208 btrfs_space_info_update_bytes_may_use+0x9c/0x1c0 [btrfs]
[114064.920182] Modules linked in: aes_arm_bs crypto_simd dm_crypt cpufreq_conservative cpufreq_userspace cpufreq_powersave sunrpc zram zsmalloc binfmt_misc evdev sg nfnetlink ip_tables x_tables ipv6 autofs4 btrfs blake2b_generic xor xor_neon raid6_pq libcrc32c sd_mod t10_pi crc64_rocksoft uas usb_storage scsi_mod scsi_common gpio_keys
[114064.920385] CPU: 5 PID: 30410 Comm: btrfs Tainted: G        W          6.6.122-current-odroidxu4 #1
[114064.920398] Hardware name: Samsung Exynos (Flattened Device Tree)
[114064.920409]  unwind_backtrace from show_stack+0x10/0x14
[114064.920426]  show_stack from dump_stack_lvl+0x40/0x4c
[114064.920441]  dump_stack_lvl from __warn+0x78/0x154
[114064.920454]  __warn from warn_slowpath_fmt+0x1b4/0x1bc
[114064.920466]  warn_slowpath_fmt from btrfs_space_info_update_bytes_may_use+0x9c/0x1c0 [btrfs]
[114064.920559]  btrfs_space_info_update_bytes_may_use [btrfs] from btrfs_block_rsv_release+0x1f4/0x2f4 [btrfs]
[114064.920729]  btrfs_block_rsv_release [btrfs] from btrfs_trans_release_chunk_metadata+0x2c/0x40 [btrfs]
[114064.920900]  btrfs_trans_release_chunk_metadata [btrfs] from __btrfs_end_transaction+0x38/0x2a0 [btrfs]
[114064.921070]  __btrfs_end_transaction [btrfs] from btrfs_inc_block_group_ro+0x1f0/0x234 [btrfs]
[114064.921239]  btrfs_inc_block_group_ro [btrfs] from btrfs_relocate_block_group+0x94/0x48c [btrfs]
[114064.921406]  btrfs_relocate_block_group [btrfs] from btrfs_relocate_chunk+0x3c/0x180 [btrfs]
[114064.921572]  btrfs_relocate_chunk [btrfs] from btrfs_balance+0x864/0x13b8 [btrfs]
[114064.921741]  btrfs_balance [btrfs] from btrfs_ioctl+0x248c/0x28c4 [btrfs]
[114064.921913]  btrfs_ioctl [btrfs] from sys_ioctl+0x288/0xc60
[114064.922009]  sys_ioctl from ret_fast_syscall+0x0/0x54
[114064.922024] Exception stack(0xf26b9fa8 to 0xf26b9ff0)
[114064.922036] 9fa0:                   00000000 00000003 00000003 c4009420 beae9fc0 beae9f60
[114064.922046] 9fc0: 00000000 00000003 beae9fc0 00000036 0057fb78 beaea6f1 00000001 0054b190
[114064.922057] 9fe0: 00000036 beae9f48 b6d118b1 b6c7f736
[114064.922067] ---[ end trace 0000000000000000 ]---
[114064.922111] BTRFS info (device dm-0: state EA): balance: ended with status: -30</span></pre>

<p>
	 
</p>

<p>
	I tried balancing data, starting with low usage limits and moving up to no limit. That all went smoothly. The problem still occurred when trying to balance metadata, but the extent buffer number named in dmesg errors changed. I do not know whether that is significant or whether balancing data should be expected to be of any benefit in this situation. I did not keep full context from dmesg, but these are the commands issued:
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">btrfs balance start -dusage=1 /backup
btrfs balance start -dusage=10 /backup
btrfs balance start -dusage=50 /backup
btrfs balance start -dusage=75 /backup
btrfs balance start -dusage=85 /backup
btrfs balance start -dusage=95 /backup
btrfs balance start -d /backup</span></pre>

<p>
	 
</p>

<p>
	Most of those were pretty fast. The last one took several hours.
</p>

<p>
	 
</p>

<p>
	I also checked my SSD for SMART errors, running a short self test and then a long one. No errors are reported.
</p>

<p>
	 
</p>

<p>
	I do not know whether this is an architecture specific bug. It may be specific to 32 bit systems, or to ARM 32 bit, or it may not.
</p>

<p>
	 
</p>

<p>
	I do not know whether this is an upstream bug, but it seems likely. The behavior in question seems to be related to the btrfs kernel component.
</p>

<p>
	 
</p>

<p>
	The recommended fix is to attach the SSD to a 64 bit system to complete any operations requiring addresses that cannot be handled by the 32 bit system. I have not done that, yet, and I will hold off for a while, as it seems like that will only be a temporary fix.
</p>

<p>
	 
</p>

<p>
	If I can gather any more relevant information while the system is still in this state, please let me know.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">-- System Information:
Debian Release: 13.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: armhf (armv7l)

Kernel: Linux 6.6.122-current-odroidxu4 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">59928</guid><pubDate>Tue, 26 May 2026 22:26:18 +0000</pubDate></item><item><title>Partitions not visible after update to 26.2.1</title><link>https://testforum.armbian.com/topic/58592-partitions-not-visible-after-update-to-2621/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I have updated my Odroid HC1 to 26.2.1 - just the kernel, u-boot and such. I have been running a self-built 6.6.128 prior so kernel version itself is unlikely the issue. After rebooting, my SATA drive seems dead - no partitions are detected, only the main sda device. This is what the journal said before:
</p>

<pre class="ipsCode">Mar 05 15:51:31 kernel: usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
Mar 05 15:51:31 kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.02
Mar 05 15:51:31 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 05 15:51:31 kernel: usb 4-1: Product: USB to ATA/ATAPI Bridge
Mar 05 15:51:31 kernel: usb 4-1: Manufacturer: JMicron
Mar 05 15:51:31 kernel: usb 4-1: SerialNumber: 0123456789ABCDEF
Mar 05 15:51:31 kernel: SCSI subsystem initialized
Mar 05 15:51:31 kernel: usbcore: registered new interface driver usb-storage
Mar 05 15:51:31 kernel: scsi host0: uas
Mar 05 15:51:31 kernel: usbcore: registered new interface driver uas
Mar 05 15:51:31 kernel: scsi 0:0:0:0: Direct-Access     JMicron  Generic          3102 PQ: 0 ANSI: 6
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] 4096-byte physical blocks
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Write Protect is off
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Mode Sense: 53 00 00 08
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Disabling FUA
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
Mar 05 15:51:31 kernel:  sda: sda1
Mar 05 15:51:31 kernel: sd 0:0:0:0: [sda] Attached SCSI disk</pre>

<p>
	This is what it says now:
</p>

<pre class="ipsCode">Mar 19 09:36:34 kernel: usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.02
Mar 19 09:36:34 kernel: usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 19 09:36:34 kernel: usb 4-1: Product: USB to ATA/ATAPI Bridge
Mar 19 09:36:34 kernel: usb 4-1: Manufacturer: JMicron
Mar 19 09:36:34 kernel: usb 4-1: SerialNumber: 0123456789ABCDEF
Mar 19 09:36:34 kernel: SCSI subsystem initialized
Mar 19 09:36:34 kernel: usbcore: registered new interface driver usb-storage
Mar 19 09:36:34 kernel: scsi host0: uas
Mar 19 09:36:34 kernel: usbcore: registered new interface driver uas
Mar 19 09:36:34 kernel: scsi 0:0:0:0: Direct-Access     JMicron  Generic          3102 PQ: 0 ANSI: 6
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Unit Not Ready
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] ASC=0x44 &lt;&lt;vendor&gt;&gt;ASCQ=0x81 
Mar 19 09:36:34 kernel: r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
Mar 19 09:36:34 kernel: r8152 6-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
Mar 19 09:36:34 kernel: r8152 6-1:1.0 eth0: v1.12.13
Mar 19 09:36:34 kernel: r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] ASC=0x44 &lt;&lt;vendor&gt;&gt;ASCQ=0x81 
Mar 19 09:36:34 kernel: r8152 6-1:1.0: load rtl8153a-3 v2 02/07/20 successfully
Mar 19 09:36:34 kernel: r8152 6-1:1.0 eth0: v1.12.13
Mar 19 09:36:34 kernel: r8152 6-1:1.0 enx001e06326076: renamed from eth0
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x07 driverbyte=DRIVER_OK
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] ASC=0x44 &lt;&lt;vendor&gt;&gt;ASCQ=0x81 
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] 0-byte physical blocks
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Asking for cache data failed
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes)
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
Mar 19 09:36:34 kernel: sd 0:0:0:0: [sda] Attached SCSI disk</pre>

<p>
	I will try attaching the drive to another PC to exclude a poorly timed hardware failure.
</p>
]]></description><guid isPermaLink="false">58592</guid><pubDate>Thu, 19 Mar 2026 08:45:33 +0000</pubDate></item><item><title>XU4 cpu speed configurability?</title><link>https://testforum.armbian.com/topic/56726-xu4-cpu-speed-configurability/</link><description><![CDATA[<p>
	I decided to klipperize an old 3d printer and found some of my orange pi boards dead, so i ended up selecting my XU4 for the task. 
</p>

<p>
	 
</p>

<p>
	Fast forward 24 hours and i'm fighting MCU timeouts. Klipper doesn't know what happened just that the mcu stopped responding.  And their knowledge base article is basically "gosh it could be anything". 
</p>

<p>
	 
</p>

<p>
	One seat of the pants observation i made was that the XU4 idles along at 600mhz with a load average of about 0.1 and it seemed like the load average increased maybe before the mcu stopped responding. 
</p>

<p>
	 
</p>

<p>
	The MCU in question is an SKR Pico, aka rp2040 with a usb connection. The mcu is not receiving power from the xu4 (there's a jumper) - I've tried both usb3 and usb2 ports on the XU4 with no difference. 
</p>

<p>
	 
</p>

<p>
	I recall that many years ago i resolved a similar issue with an H2+ based board and Octoprint by switching the cpufreq governor to "performance" which of course just pegs it at the top speed. 
</p>

<p>
	 
</p>

<p>
	But on that board, armbian-config lets me select what that maximum speed is, so as to avoid overheating. 
</p>

<p>
	 
</p>

<p>
	My XU4 is equipped with the flat little fan. I do have some large heatsinks and thermal adhesive. I'm a little worried that it might run too hot if it's at 1.4ghz all the time. 
</p>

<p>
	 
</p>

<p>
	sysfs tells me there are a ton of scaling frequencies available, but it appears that i can't just, select one. 
</p>

<p>
	 
</p>

<p>
	Any hints? 
</p>
]]></description><guid isPermaLink="false">56726</guid><pubDate>Sun, 14 Dec 2025 21:57:16 +0000</pubDate></item><item><title><![CDATA[Installing Armbian SD --> eMMc boots frpm eMMc [soLved]]]></title><link>https://testforum.armbian.com/topic/56214-installing-armbian-sd-emmc-boots-frpm-emmc-solved/</link><description><![CDATA[<p>
	Armbian Bookworm 25.8.1. (minimal)<br />
	Odroid XU4 with 32GB <abbr title="embedded MultiMediaCard">eMMc</abbr>
</p>

<p>
	 
</p>

<p>
	After lots of searching and trying 2017 Hardkernel solutions and github etc - And this forum suggestions - I could never get get it to boot. I think this is partly because things have changed since 2016/17.
</p>

<p>
	 
</p>

<p>
	I did not have my <abbr title="embedded MultiMediaCard">eMMc</abbr> on an usb adapter. Just installed, brand new (untouched from China) <abbr title="embedded MultiMediaCard">eMMc</abbr> and a imaage  install on MicroSD of Armbian.
</p>

<p>
	 
</p>

<p>
	The method  I believed should work was "armbian-install".  But, it had errors while using mkpartimage.<br />
	I put debug statements in the script and found the particular instance of invoking mkpartimage.<br />
	Actually the issue is; 2 files are missing from /boot folder.
</p>

<p>
	Current SD installation image of Armbian minimal only creates one fdisk (MBR) partition on which /boot is a folder.<br />
	I tried for ages to create a separate /boot partition. Maybe, since I have now succeeded with an <abbr title="embedded MultiMediaCard">eMMc</abbr> install, I might try doing a separate root and boot.<br />
	<br />
	The 2 missing files are <br />
	armbianEnv.txt and boot.cmd
</p>

<p>
	 
</p>

<p>
	If one "touch"es armbianEnv.txt then - if it doesn't exist it will be created -  if it does then no harm done. 
</p>

<p>
	If one copies boot.ini to boot.cmd then these two things will satisfy armbian-install.
</p>

<p>
	 
</p>

<p>
	Amrbian-install correctly changes the R/O of mmcblkXboot1 (where X is <abbr title="embedded MultiMediaCard">emmc</abbr> device number) write the boot stuff and markit back R/O.
</p>

<p>
	It also ensures that armbianEnv.txt has got correct entries in it.
</p>

<p>
	<strong><span style="font-size:14px;">In summary</span></strong>
</p>

<ol>
	<li>
		Install <abbr title="embedded MultiMediaCard">eMMc</abbr> and Micro SD in XU4
	</li>
	<li>
		Ensure SD/<abbr title="embedded MultiMediaCard">eMMc</abbr> switch set to SD and boot armbian from SD
	</li>
	<li>
		Login as root or use sudo
	</li>
	<li>
		<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">touch /boot/armbianEnv.txt
cp /boot/boot.ini  /boot/boot.cmd
armbian-install</span></pre>
	</li>
	<li>
		choose the install and boot from <abbr title="embedded MultiMediaCard">eMMc</abbr> option
	</li>
	<li>
		shutdown
	</li>
	<li>
		change switch to boot armbian from <abbr title="embedded MultiMediaCard">eMMc</abbr>
	</li>
	<li>
		boot
	</li>
</ol>

<p>
	 
</p>
]]></description><guid isPermaLink="false">56214</guid><pubDate>Fri, 14 Nov 2025 07:02:21 +0000</pubDate></item><item><title>Negative Temps on ODroid XU4</title><link>https://testforum.armbian.com/topic/55914-negative-temps-on-odroid-xu4/</link><description><![CDATA[<p>
	I recently noticed my ODroid XU4 was reporting weird temperature readings:
</p>

<p>
	 
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">cat /sys/class/thermal/thermal_zone0/temp
-22000</span></pre>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="15275" width="578" alt="image.png.efaed96630766fc4cbeee59744969dae.png" src="https://testforum.armbian.com/uploads/monthly_2025_10/image.png.efaed96630766fc4cbeee59744969dae.png" loading="lazy" height="508.64">
</p>

<p>
	 
</p>

<p>
	Is this a software issue or maybe hardware failing?
</p>

<p>
	 
</p>

<p>
	Also, I would like to upgrade, is there another board I could just transfer my <abbr title="embedded MultiMediaCard">EMMC</abbr>  to and be up and running?
</p>

<p>
	 
</p>

<p>
	Thanks
</p>
]]></description><guid isPermaLink="false">55914</guid><pubDate>Sat, 25 Oct 2025 11:52:57 +0000</pubDate></item><item><title>Request to update distro:  park heads of hard disk(s) before shutdown....</title><link>https://testforum.armbian.com/topic/55809-request-to-update-distro-park-heads-of-hard-disks-before-shutdown/</link><description><![CDATA[<p>
	 
</p>

<p>
	 
</p>

<p>
	A known issue with the Odroid XU4, HC1, and HC2 is that it (uboot?) does not properly park the hard disk heads before/during shutdown or power cycle/off.
</p>

<p>
	So, the disk drive is forced to emergency hard retract the heads when power is shutdown/cycled.
</p>

<p>
	This is of course a violent action for the HDD and should be avoided.
</p>

<p>
	Use this odroid.shutdown script and install into /lib/systemd/system-shutdown/.
</p>

<p>
	<a href="https://wiki.odroid.com/odroid-xu4/troubleshooting/shutdown_script" rel="external nofollow">https://wiki.odroid.com/odroid-xu4/troubleshooting/shutdown_script</a>
</p>

<p>
	 
</p>

<p>
	Recommend adding to armbian for XU4 distros.
</p>
]]></description><guid isPermaLink="false">55809</guid><pubDate>Mon, 20 Oct 2025 01:09:24 +0000</pubDate></item><item><title>nand-sata-install hoses XU4 rev 1</title><link>https://testforum.armbian.com/topic/55619-nand-sata-install-hoses-xu4-rev-1/</link><description><![CDATA[<p>
	Using Armbian_25.8.1_Odroidxu4_noble_current_6.6.102.img I can boot off SD. Then when I run <abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install it sharts and comes up with initramfs prompt. I'll try to fix it there next time, but I'm just using a 3.5" SATA laptop disk with USB controller.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">.oading, please wait..
.tarting systemd-udevd version 255.4-1ubuntu0.11
.begin: Loading essential drivers ... done.
.begin: Running /scripts/init-premount ... done.
.begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
.begin: Running /scripts/local-premount ... done.
.begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
done.
Save up waiting for root file system device. Common problems:
 - Boot args (cat /proc/cmdline)
 - Check rootdelay=(did the system wait long enough?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=546a0798-29c9-4f3c-beea-1563d848abd0 does not exist. Dropping to a shell!

BusyBox v1.36.1 (Ubuntu 1:1.36.1-6ubuntu3.1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) _</span></pre>

<p>
	 
</p>

<p>
	I had old image Armbian_23.11.1_Odroidxu4_jammy_current_6.1.63.img and it works fine.
</p>
]]></description><guid isPermaLink="false">55619</guid><pubDate>Thu, 09 Oct 2025 20:19:12 +0000</pubDate></item><item><title>base-files is missing for noble 25.8.1</title><link>https://testforum.armbian.com/topic/55076-base-files-is-missing-for-noble-2581/</link><description><![CDATA[<p>
	Try to upgrade from 25.5.1 but base-files not present in repository. Missed again.
</p>

<p>
	<a contenteditable="false" data-ipshover="" data-ipshover-target="https://testforum.armbian.com/profile/1-igor/?do=hovercard" data-mentionid="1" href="https://testforum.armbian.com/profile/1-igor/" rel="">@Igor</a> can you fix it?
</p>
]]></description><guid isPermaLink="false">55076</guid><pubDate>Mon, 08 Sep 2025 08:53:34 +0000</pubDate></item><item><title>running without interweb</title><link>https://testforum.armbian.com/topic/54830-running-without-interweb/</link><description><![CDATA[<p>
	i've been using armbian for a whole hour now
</p>

<p>
	i figure i've mastered this thing <span>:)</span>
</p>

<p>
	i loaded Armbian_25.5.1_Odroidxu4_bookworm_current_6.6.88_minimal.img on a sd and fired up an old xu4
</p>

<p>
	according to the instruction the first thing to do is run armbian-config
</p>

<p>
	but it hangs because i don't have an interweb connection
</p>

<p>
	is there a way around that
</p>
]]></description><guid isPermaLink="false">54830</guid><pubDate>Thu, 28 Aug 2025 02:44:15 +0000</pubDate></item><item><title>Does Armbian (Debian) support GPU acceleration on the XU4?</title><link>https://testforum.armbian.com/topic/30438-does-armbian-debian-support-gpu-acceleration-on-the-xu4/</link><description><![CDATA[<p>
	Hi guys,
</p>

<p>
	 
</p>

<p>
	this is something that I would like to achieve if feasible.
</p>

<p>
	I remember that other OS like "RetroPie Arena" support <abbr title="Graphic processing unit (3D acceleration)">GPU</abbr> acceleration, thanks.
</p>

<p>
	 
</p>

<p>
	Any documentation to read? Thanks! <span class="ipsEmoji">🙏</span>
</p>
]]></description><guid isPermaLink="false">30438</guid><pubDate>Thu, 28 Sep 2023 20:09:45 +0000</pubDate></item><item><title>Cannot run weston</title><link>https://testforum.armbian.com/topic/51114-cannot-run-weston/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I'm trying to run weston on Odroid XU4, but it does not start. Seems something is wrong with <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr> drivers.
</p>

<p>
	 
</p>

<p>
	I have installed "Armbian 25.2.1 Bookworm Minimal" image and then installed weston via apt.
</p>

<p>
	 
</p>

<p>
	Then, trying to run the weston fails with error:
</p>

<pre class="ipsCode">Date: 2025-04-13 UTC
[13:47:44.248] weston 10.0.1
               https://wayland.freedesktop.org
               Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/
               Build: 10.0.1
[13:47:44.249] Command line: weston
[13:47:44.249] OS: Linux, 6.6.81-current-odroidxu4, #1 SMP PREEMPT Mon Dec 30 15:59:39 UTC 2024, armv7l
[13:47:44.249] Flight recorder: enabled
[13:47:44.249] Starting with no config file.
[13:47:44.250] Output repaint window is 7 ms maximum.
[13:47:44.250] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-10/drm-backend.so'
[13:47:44.265] initializing drm backend
[13:47:44.265] Trying logind launcher...
[13:47:44.280] logind: session control granted
[13:47:44.290] using /dev/dri/card0
[13:47:44.291] DRM: supports atomic modesetting
[13:47:44.291] DRM: supports GBM modifiers
[13:47:44.291] DRM: supports picture aspect ratio
[13:47:44.291] Loading module '/usr/lib/arm-linux-gnueabihf/libweston-10/gl-renderer.so'
MESA-LOADER: failed to open exynos: /usr/lib/dri/exynos_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load driver: exynos
MESA-LOADER: failed to open zink: /usr/lib/dri/zink_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load driver: zink
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
failed to load swrast driver
[13:47:44.301] failed to initialize egl
[13:47:44.302] fatal: failed to create compositor backend
Internal warning: debug scope 'drm-backend' has not been destroyed.</pre>

<p>
	 
</p>

<p>
	Runing weston in pixman mode with "weston --use-pixman" succeeds, but I need accelerated weston.
</p>

<p>
	 
</p>

<p>
	Any idea how I can install the missing <abbr title="Graphic processing unit (3D acceleration)"><abbr title="Graphic processing unit (3D acceleration)">GPU</abbr></abbr> drivers?
</p>
]]></description><guid isPermaLink="false">51114</guid><pubDate>Sun, 13 Apr 2025 13:52:36 +0000</pubDate></item><item><title>Which ARM? (Docker images on HC2)</title><link>https://testforum.armbian.com/topic/22660-which-arm-docker-images-on-hc2/</link><description><![CDATA[<p>
	Looking at various Docker images on Docker Hub, I see images for armv6, armv7, and armhf. Which are the right ones to use on an XU4/HC2?
</p>
]]></description><guid isPermaLink="false">22660</guid><pubDate>Fri, 29 Jul 2022 13:31:45 +0000</pubDate></item><item><title>Odroid HC2 Should I Change armbianEnv.txt or boot.ini</title><link>https://testforum.armbian.com/topic/50716-odroid-hc2-should-i-change-armbianenvtxt-or-bootini/</link><description><![CDATA[<p>
	I recently installed:Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img on my Odroid HC2. 
</p>

<p>
	 
</p>

<p>
	Ran the configuration. I'm currently trying to resolve an issue with warm booting and losing the hard drive.
</p>

<p>
	 
</p>

<p>
	I've read this: <a href="https://forum.odroid.com/viewtopic.php?f=97&amp;t=44865" rel="external nofollow">https://forum.odroid.com/viewtopic.php?f=97&amp;t=44865</a> on the Odriod forum.
</p>

<p>
	 
</p>

<p>
	And this: <a href="https://testforum.armbian.com/topic/15611-odroid-hc1-and-kernel-54-soft-reset-makes-the-sata-drive-disappear/" rel="">https://forum.armbian.com/topic/15611-odroid-hc1-and-kernel-54-soft-reset-makes-the-sata-drive-disappear/</a>  here
</p>

<p>
	 
</p>

<p>
	JMCC said:
</p>

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

	<div class="ipsQuote_contents">
		<p>
			I can confirm that, at least in 4.14 kernel, the method that armbian-config uses has no effect on selecting the HC1 device tree. As a matter of fact, nothing that you put on armbianEnv.txt has any effect, it is completely ignored. You need to manually set the parameters in /boot/boot.ini.
		</p>

		<p>
			 
		</p>

		<p>
			IMO that is not a bad thing. boot.ini has comments and explanations about the different parameters. So I think we could just stick with boot.ini, and make armbianEnv.txt just a symlink, in case we want to keep uniformity with other boards with regards to the name of the boot env config file.
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	Just curious if this still applies today with that build of Armbian?
</p>

<p>
	 
</p>

<p>
	Also if the solution of changing the boot.ini is still valid today to fix the soft reset error?
</p>

<p>
	 
</p>

<p>
	Finally as an aside it doesn't look like "hdparm" was installed? Is that possible? If so why?
</p>

<p>
	 
</p>

<p>
	Thanks for all the help.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">50716</guid><pubDate>Sun, 23 Mar 2025 19:47:25 +0000</pubDate></item><item><title>Booting with a HC1 overlay</title><link>https://testforum.armbian.com/topic/47782-booting-with-a-hc1-overlay/</link><description><![CDATA[<p>
	I've been running Armbian on an Odroid HC1 board for some time now. We've just had a kernel upgrade and it now boots as an XU4
</p>

<p>
	according to the motd. This used to be changeable with armbian-config (I did this regularly on kernel updates).
</p>

<p>
	But, with the new armbian-config I can't find a way to do this any more.
</p>

<p>
	 
</p>

<p>
	*edit
</p>

<p>
	A bit more info
</p>

<p>
	Running SY017 in armbian-config gives an empty list, and I get this error:
</p>

<p>
	 
</p>

<p>
	ls: cannot access '/boot/<abbr title="Device tree blob">dtb</abbr>/overlay/*.dtbo': No such file or directory
</p>

<p>
	 
</p>

<p>
	In fact /boot/<abbr title="Device tree blob">dtb</abbr>/overlay/ does not exist
</p>
]]></description><guid isPermaLink="false">47782</guid><pubDate>Sat, 30 Nov 2024 10:06:00 +0000</pubDate></item><item><title>Odroid HC2 not booting with several releases.</title><link>https://testforum.armbian.com/topic/49882-odroid-hc2-not-booting-with-several-releases/</link><description><![CDATA[<p>
	Hi, hope you're all doing well.
</p>

<p>
	I have this Odroid HC2 (XU4 without video output) that was running an old Armbian version. I intended to update to the latest one (o something close to it) but it seems it won't boot with the newer releases.
</p>

<p>
	 
</p>

<p>
	The board seems to power up ok, leds apparently blinking in a normal fashion, but it seems it gets stuck somewhere. It doesn't acquire any IP address.
</p>

<p>
	 
</p>

<p>
	Not having video output leaves me with little to no way of knowing what is failing.
</p>

<p>
	No logs seem to be created in the sdcard.
</p>

<p>
	 
</p>

<p>
	I also tried DietPi images, which I believe are based on Armbian but the same thing happens.
</p>

<p>
	 
</p>

<p>
	I does, however, boot the previous Armbian installation and an Ubuntu image I got from somewhere (but it's a desktop version which doesn't seem to include remote ssh access by default).
</p>

<p>
	 
</p>

<p>
	So my guess is that I can mostly rule hardware or sdcard issues.
</p>

<p>
	 
</p>

<p>
	I created "armbianEnv.txt" to include "board_name=hc2 # or xu4, xu3, hc1, hc2"
</p>

<p>
	 
</p>

<p>
	boot.ini didn't show anything suspicious and the UUID in there matches the one of the sdcard I'm using.
</p>

<p>
	 
</p>

<p>
	These are all the images I tried (with Etcher) (in no specific order) <span>:</span>
</p>

<p>
	- Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img
</p>

<p>
	- Armbian_25.2.1_Odroidxu4_ubuntu_noble_current_6.6.75_minimal.img
</p>

<p>
	- Armbian_24.8.1_Odroidxu4_bookworm_current_6.6.47_minimal.img
</p>

<p>
	 
</p>

<p>
	- DietPi_2025-02-17_OdroidXU4-ARMv7-Bookworm.img
</p>

<p>
	- DietPi_2025-02-17_OdroidXU4-ARMv7-Bullseye.img
</p>

<p>
	- DietPi_2025-02-17_OdroidXU4-ARMv7-Trixie.img
</p>

<p>
	 
</p>

<p>
	This is the only new image that did boot: 
</p>

<p>
	- ubuntu-24.04-6.6-minimal-odroid-xu4-20240911.img
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	Any ideas about what could be happening?
</p>

<p>
	 
</p>

<p>
	Also, I couldn't find an older image to try out, i.e. something with a 5.X kernel, is there anywhere I could get one? 
</p>

<p>
	 
</p>

<p>
	Thanks in advance.
</p>

<p>
	MO
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">49882</guid><pubDate>Mon, 17 Feb 2025 21:56:16 +0000</pubDate></item><item><title>base-files_24.8.3-13ubuntu10-noble_armhf missing</title><link>https://testforum.armbian.com/topic/45596-base-files_2483-13ubuntu10-noble_armhf-missing/</link><description><![CDATA[<p>
	Title says it all. "_amd64" and "_arm64" are in the apt repository "_armhf" is missing.
</p>
]]></description><guid isPermaLink="false">45596</guid><pubDate>Sun, 29 Sep 2024 05:22:45 +0000</pubDate></item><item><title>armbian-bsp-cli-odroidxu4-current held back</title><link>https://testforum.armbian.com/topic/50161-armbian-bsp-cli-odroidxu4-current-held-back/</link><description><![CDATA[<p>
	armbian-bsp-cli-odroidxu4-current is held back because  base-files_25.2.2-13ubuntu10-noble_armhf does not exist (<a href="https://testforum.armbian.com/topic/45596-base-files_2483-13ubuntu10-noble_armhf-missing/" rel="">again</a>).
</p>

<p>
	 
</p>

<p>
	<a href="https://testforum.armbian.com/topic/45367-base-files-missing-for-2481-armhf/#findComment-202257" rel="">As before</a>, the fix seems to be
</p>

<p>
	 
</p>

<pre class="ipsCode">wget https://apt.armbian.org/apt/pool/noble-utils/b/base-files/base-files_25.2.2-13ubuntu10-noble_amd64__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb
wget https://apt.armbian.org/apt/pool/noble-utils/b/base-files/base-files_25.2.2-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb
dpkg-deb -x base-files_25.2.1-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb armhf
dpkg-deb -x base-files_25.2.2-13ubuntu10-noble_amd64__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb armhf_new
diff -qr armhf armhf_new
cp armhf/bin/locale-check armhf_new/bin/locale-check
rmdir $(readlink -f armhf_new/lib64)
rm armhf_new/lib64
dpkg-deb --control base-files_25.2.2-13ubuntu10-noble_amd64__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb armhf_new/DEBIAN
vi armhf_new/DEBIAN/control (replace amd64 by armhf on line 4)
grep -nrw  armhf_new/DEBIAN -e lib64
(remove all instances of lib64 in files below)
vi armhf_new/DEBIAN/postinst
vi armhf_new/DEBIAN/postrm
vi armhf_new/DEBIAN/preinst
md5sum armhf_new/usr/bin/locale-check
vi armhf_new/DEBIAN/md5sums  (fix md5sum for usr/bin/locale-check)
chown -R root:root armhf_new/*
sudo dpkg-deb -b armhf_new base-files_25.2.2-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb
sudo dpkg -i base-files_25.2.2-13ubuntu10-noble_armhf__1-noble-1armbian1-Baa17-U13ubuntu10-R55fa.deb
sudo apt update
sudo apt upgrade</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">50161</guid><pubDate>Sat, 01 Mar 2025 04:42:51 +0000</pubDate></item><item><title>Unattended Updates ODroid XU4 Bootloop</title><link>https://testforum.armbian.com/topic/49783-unattended-updates-odroid-xu4-bootloop/</link><description><![CDATA[<p>
	Today unattended upgrades ran and installed the following:
</p>

<p>
	 
</p>

<p>
	libtasn1-6 linux-<abbr title="Device tree blob">dtb</abbr>-current-odroidxu4 linux-image-current-odroidxu4
</p>

<p>
	linux-u-boot-odroidxu4-current
</p>

<p>
	 
</p>

<p>
	Afterward, the system automatically rebooted and went into a boot loop.  I had a backup I was able to copy to the <abbr title="embedded MultiMediaCard">emmc</abbr> and get back up and running but it is from October 2024 and I am not really sure what to do.
</p>

<p>
	 
</p>

<p>
	coming here to see if anyone else has experienced the same.  I tried to run armbianmonitor -U and it had some weird html.  I am pretty good with Linux but everything is self taught. <br />
	 
</p>

<p>
	thank you in advance for any help
</p>

<p>
	Dan
</p>
]]></description><guid isPermaLink="false">49783</guid><pubDate>Wed, 12 Feb 2025 00:34:40 +0000</pubDate></item><item><title>apt upgrade &#x2192; Size + hash Sum mismatches &#x2192;  Mirror sync in progress?</title><link>https://testforum.armbian.com/topic/49735-apt-upgrade-%E2%86%92-size-hash-sum-mismatches-%E2%86%92-mirror-sync-in-progress/</link><description><![CDATA[<p>
	<strong>My hardware: Odroid HC2</strong><br />
	<br />
	<strong>Armbian 24.5.1 Bookworm with Linux 6.6.31-current-odroidxu4</strong> <span><span>:</span> </span>My backup restoration → Has other issues too → But <strong>apt upgrade</strong> results in <span style="color:#e74c3c;">various size and hash mismatches</span>.
</p>

<ul>
	<li>
		Offtopic: <strong>apt upgrade</strong> or <strong>sudo dpkg --configure -a</strong> always crash the system (since summer 2024, troubleshooting without success since christmas 2024)

		<ul>
			<li>
				Ruled out HW failure 80-90%.
			</li>
			<li>
				My local apt/dpg cache was corrupted, thus at <strong>/var/lib/dpkg/</strong> backed up <strong>info/</strong> to <strong>info.bak/</strong>  and <strong>mkdir info/</strong> afresh.
			</li>
		</ul>
	</li>
	<li>
		And now <strong>sudo dpkg --configure -a</strong> completed successfully the very first time!
	</li>
	<li>
		But 2025-02-09 ca. 12:00 CET and also later the afternoon <strong>apt upgrade</strong> results in various size and hash mismatches. <span style="color:#e67e22;">Mirror sync in progress?</span>
	</li>
</ul>

<p>
	 
</p>

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

	<div class="ipsSpoiler_contents">
		<p>
			$ sudo mv /var/lib/dpkg/info /var/lib/dpkg/info.bak
		</p>

		<p>
			$ sudo mkdir /var/lib/dpkg/info
		</p>

		<p>
			$ sudo dpkg --configure -a
		</p>

		<p>
			# Completed
		</p>

		<p>
			<br />
			$ sudo apt update<br />
			<br />
			# Starts normal
		</p>

		<p>
			Get:1 <a href="http://packages.openmediavault.org/public" rel="external nofollow">http://packages.openmediavault.org/public</a> sandworm/main armhf salt-minion all 3006.0+ds-1+225.1 [126 kB]
		</p>

		<p>
			Get:2 <a href="http://security.debian.org" rel="external nofollow">http://security.debian.org</a> bookworm-security/main armhf git armhf 1:2.39.5-0+deb12u2 [6,060 kB]
		</p>

		<p>
			[...]
		</p>

		<p>
			<br />
			# But then some hash mismatches occur
		</p>

		<p>
			Get:5 <a href="http://apt.armbian.com" rel="external nofollow">http://apt.armbian.com</a> bookworm/bookworm-utils armhf base-files armhf 25.2.1-12.4+deb12u9-bookworm [53.0 kB]
		</p>

		<p>
			Err:5 <a href="http://apt.armbian.com" rel="external nofollow">http://apt.armbian.com</a> bookworm/bookworm-utils armhf base-files armhf 25.2.1-12.4+deb12u9-bookworm
		</p>

		<p>
			  Hash Sum mismatch
		</p>

		<p>
			  Hashes of expected file:
		</p>

		<p>
			   - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc
		</p>

		<p>
			   - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297
		</p>

		<p>
			   - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak]
		</p>

		<p>
			   - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak]
		</p>

		<p>
			   - Filesize:52960 [weak]
		</p>

		<p>
			  Hashes of received file:
		</p>

		<p>
			   - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a
		</p>

		<p>
			   - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2
		</p>

		<p>
			   - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak]
		</p>

		<p>
			   - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak]
		</p>

		<p>
			   - Filesize:52960 [weak]
		</p>

		<p>
			  Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000<br />
			<br />
			 
		</p>

		<p>
			Err:9 <a href="http://apt.armbian.com" rel="external nofollow">http://apt.armbian.com</a> bookworm/main armhf armbian-zsh all 25.2.1                             
		</p>

		<p>
			  File has unexpected size (10829720 != 10829716). Mirror sync in progress? [IP: 152.53.15.45 80]<br />
			<br />
			 
		</p>

		<p>
			Err:8 <a href="http://apt.armbian.com" rel="external nofollow">http://apt.armbian.com</a> bookworm/main armhf armbian-firmware all 25.2.1                        
		</p>

		<p>
			  File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 65.21.120.247 80]<br />
			<br />
			 
		</p>

		<p>
			kB]
		</p>

		<p>
			Get:143 <a href="http://deb.debian.org/debian" rel="external nofollow">http://deb.debian.org/debian</a> bookworm/main armhf rfkill armhf 2.38.1-5+deb12u3 [32.3 kB]    
		</p>

		<p>
			Fetched 211 MB in 1min 7s (3,171 kB/s)                                                              
		</p>

		<p>
			E: Failed to fetch <a href="http://netcup.armbian.com/apt/pool/bookworm-utils/b/base-files/base-files_25.2.1-12.4+deb12u9-bookworm_armhf__1-bookworm-1armbian1-Baa17-U12.4--deb12u9-R55fa.deb" rel="external nofollow">http://netcup.armbian.com/apt/pool/bookworm-utils/b/base-files/base-files_25.2.1-12.4+deb12u9-bookworm_armhf__1-bookworm-1armbian1-Baa17-U12.4--deb12u9-R55fa.deb</a> Hash Sum mismatch
		</p>

		<p>
			   Hashes of expected file:
		</p>

		<p>
			    - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc
		</p>

		<p>
			    - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297
		</p>

		<p>
			    - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak]
		</p>

		<p>
			    - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak]
		</p>

		<p>
			    - Filesize:52960 [weak]
		</p>

		<p>
			   Hashes of received file:
		</p>

		<p>
			    - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a
		</p>

		<p>
			    - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2
		</p>

		<p>
			    - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak]
		</p>

		<p>
			    - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak]
		</p>

		<p>
			    - Filesize:52960 [weak]
		</p>

		<p>
			   Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000
		</p>

		<p>
			E: Failed to fetch <a href="http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb" rel="external nofollow">http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb</a> File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 65.21.120.247 80]
		</p>

		<p>
			E: Failed to fetch <a href="http://apt.armbian.com/pool/main/a/armbian-zsh/armbian-zsh_25.2.1_all__1-SAbfee-B6e0d-R448a.deb" rel="external nofollow">http://apt.armbian.com/pool/main/a/armbian-zsh/armbian-zsh_25.2.1_all__1-SAbfee-B6e0d-R448a.deb</a> File has unexpected size (10829720 != 10829716). Mirror sync in progress? [IP: 152.53.15.45 80]
		</p>

		<p>
			E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	 
</p>

<p>
	Then decided to flash a fresh image and start fresh (in all cases the SHA checksum matched, and BalenaEtcher checked the flash as identical to the image)
</p>

<p>
	 
</p>

<ul>
	<li>
		<strong>Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60-omv_minimal</strong> →  <span style="color:#e74c3c;">Status LED flashes, but SSH never reachable</span>. No idea at what level it fails.
	</li>
	<li>
		<strong>Armbian_25.2.1_Odroidxu4_bookworm_current_6.6.75_minimal.img.xz</strong> →  <span style="color:#e74c3c;">Status LED flashes, but SSH never reachable</span>. No idea at what level it fails.
	</li>
	<li>
		As recommended by the FAQs "Image does not boot" --&gt; check previous images from archive
	</li>
	<li>
		<strong>Armbian_24.11.1_Odroidxu4_bookworm_current_6.6.60_minimal</strong> → <span style="color:#16a085;">Boots, SSH works, went through initial setup (root pw, locale, timezone, username, etc)</span>.
		<ul>
			<li>
				→ But apt update ; <span style="color:#e74c3c;">apt upgrade fails with size and hash mismatches </span>at 2025-02-09 22:30 CET.
			</li>
		</ul>
	</li>
</ul>

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

	<div class="ipsSpoiler_contents">
		<p>
			Err:5 <a href="http://apt.armbian.com" rel="external nofollow">http://apt.armbian.com</a> bookworm/bookworm-utils armhf base-files armhf 25.2.1-12.4+deb12u9-bookworm
		</p>

		<p>
			  Hash Sum mismatch
		</p>

		<p>
			  Hashes of expected file:
		</p>

		<p>
			   - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc
		</p>

		<p>
			   - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297
		</p>

		<p>
			   - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak]
		</p>

		<p>
			   - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak]
		</p>

		<p>
			   - Filesize:52960 [weak]
		</p>

		<p>
			  Hashes of received file:
		</p>

		<p>
			   - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a
		</p>

		<p>
			   - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2
		</p>

		<p>
			   - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak]
		</p>

		<p>
			   - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak]
		</p>

		<p>
			   - Filesize:52960 [weak]
		</p>

		<p>
			  Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000
		</p>

		<p>
			 
		</p>

		<p>
			E: Failed to fetch <a href="http://fi.mirror.armbian.de/apt/pool/bookworm-utils/b/base-files/base-files_25.2.1-12.4+deb12u9-bookworm_armhf__1-bookworm-1armbian1-Baa17-U12.4--deb12u9-R55fa.deb" rel="external nofollow">http://fi.mirror.armbian.de/apt/pool/bookworm-utils/b/base-files/base-files_25.2.1-12.4+deb12u9-bookworm_armhf__1-bookworm-1armbian1-Baa17-U12.4--deb12u9-R55fa.deb</a> Hash Sum mismatch
		</p>

		<p>
			   Hashes of expected file:
		</p>

		<p>
			    - SHA512:2e2823fa52355f70ed4a8a5d34a26528dbf27d12fcec1d873e7bfb67c7019bdefe25bfa053c857e904fc6e681be0ae92eeaa2d6342e5548e59b7c6426b4c65dc
		</p>

		<p>
			    - SHA256:96e7ca7a69ef8fae4a52311d14115c288e05d98bbbfe1b7a7304573798f14297
		</p>

		<p>
			    - SHA1:6f217dc12471a8f79a87c6711be6c40f602e0888 [weak]
		</p>

		<p>
			    - MD5Sum:049413cb0eb2fbf97f04e56f1f3d4ba9 [weak]
		</p>

		<p>
			    - Filesize:52960 [weak]
		</p>

		<p>
			   Hashes of received file:
		</p>

		<p>
			    - SHA512:f5bc6012293b6516d7f74e71d6c7697e961c76c265d5b81976c18f809787db9968c88f2385adb82d6bd6f39357239950a27740a90593f365737a0bb9ce3cf32a
		</p>

		<p>
			    - SHA256:5495bf319ec88106001cc15fad3f315626752a083044db60e7bd3829b593f4d2
		</p>

		<p>
			    - SHA1:ba43b5b711d7a210bcf1a8c7776760b19757ba19 [weak]
		</p>

		<p>
			    - MD5Sum:7623285eddd888a9f5dd10f3de441438 [weak]
		</p>

		<p>
			    - Filesize:52960 [weak]
		</p>

		<p>
			   Last modification reported: Sat, 08 Feb 2025 22:47:38 +0000
		</p>

		<p>
			E: Failed to fetch <a href="http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb" rel="external nofollow">http://apt.armbian.com/pool/main/a/armbian-firmware/armbian-firmware_25.2.1_all__1-SAe75d-B6c7f-R448a.deb</a> File has unexpected size (91589632 != 91589640). Mirror sync in progress? [IP: 46.102.157.202 80]
		</p>

		<p>
			E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
		</p>
	</div>
</div>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">49735</guid><pubDate>Sun, 09 Feb 2025 22:00:27 +0000</pubDate></item><item><title>keeping previous kernel for recovery?</title><link>https://testforum.armbian.com/topic/49794-keeping-previous-kernel-for-recovery/</link><description><![CDATA[<p>
	Please forgive me if it is a stupid question, but what is preventing us from keeping n previous kernels installed in case an update is broken and does not boot? Fedora does it, Ubuntu does too. In general it should be simpler to boot a previous kernel than to try to pull the SD card and fix it in a second machine.
</p>
]]></description><guid isPermaLink="false">49794</guid><pubDate>Wed, 12 Feb 2025 12:21:28 +0000</pubDate></item><item><title>Debian Trixie brick after kernel update</title><link>https://testforum.armbian.com/topic/49086-debian-trixie-brick-after-kernel-update/</link><description><![CDATA[<p>
	I've flashed: Armbian_25.2.0-trunk.193_Odroidxu4_trixie_current_6.6.65_minimal.img to my <abbr title="embedded MultiMediaCard">eMMC</abbr>.<br />
	It boots  fine, but after a "armbian-upgrade" it will give a kernel panic upon reboot.<br />
	I think the new kernel is borked.<br />
	 
</p>
]]></description><guid isPermaLink="false">49086</guid><pubDate>Thu, 02 Jan 2025 13:55:12 +0000</pubDate></item><item><title>Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable - Kernel 6.6.60-current-odroidxu4</title><link>https://testforum.armbian.com/topic/48352-spectre-v2-firmware-did-not-set-auxiliary-control-register-ibe-bit-system-vulnerable-kernel-6660-current-odroidxu4/</link><description><![CDATA[<p>
	I used the Armbian 24.11.1 Bookworm Minimal / IOT  Image from https://www.armbian.com/odroid-xu4/.
</p>

<p>
	When i checked the boot messages with journalctl -b, then i can see the message -&gt; "system vulnerable"
</p>

<p>
	Later i can read the message "Spectre BHB: enabling loop workaround for all CPUs".
</p>

<p>
	Is this a fix for the first warning message, or is my system vulnerable?
</p>

<p>
	 
</p>

<pre class="ipsCode">Dec 16 20:32:58 odroidxu4 kernel: smp: Bringing up secondary CPUs ...
Dec 16 20:32:58 odroidxu4 kernel: CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
Dec 16 20:32:58 odroidxu4 kernel: CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
Dec 16 20:32:58 odroidxu4 kernel: CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
Dec 16 20:32:58 odroidxu4 kernel: CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
Dec 16 20:32:58 odroidxu4 kernel: CPU4: detected I-Cache line size mismatch, workaround enabled
Dec 16 20:32:58 odroidxu4 kernel: CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
Dec 16 20:32:58 odroidxu4 kernel: CPU4: Spectre BHB: enabling loop workaround for all CPUs
Dec 16 20:32:58 odroidxu4 kernel: CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
Dec 16 20:32:58 odroidxu4 kernel: CPU5: detected I-Cache line size mismatch, workaround enabled
Dec 16 20:32:58 odroidxu4 kernel: CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
Dec 16 20:32:58 odroidxu4 kernel: CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
Dec 16 20:32:58 odroidxu4 kernel: CPU6: detected I-Cache line size mismatch, workaround enabled
Dec 16 20:32:58 odroidxu4 kernel: CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
Dec 16 20:32:58 odroidxu4 kernel: CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
Dec 16 20:32:58 odroidxu4 kernel: CPU7: detected I-Cache line size mismatch, workaround enabled
Dec 16 20:32:58 odroidxu4 kernel: CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
Dec 16 20:32:58 odroidxu4 kernel: smp: Brought up 1 node, 8 CPUs
Dec 16 20:32:58 odroidxu4 kernel: SMP: Total of 8 processors activated (384.00 BogoMIPS).
Dec 16 20:32:58 odroidxu4 kernel: CPU: All CPU(s) started in HYP mode.
Dec 16 20:32:58 odroidxu4 kernel: CPU: Virtualization extensions available.</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">48352</guid><pubDate>Mon, 16 Dec 2024 21:21:22 +0000</pubDate></item><item><title>Installation of Wireguard</title><link>https://testforum.armbian.com/topic/9282-installation-of-wireguard/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	 
</p>

<p>
	I have been struggling with this for a while, found some replies on the other communities but I simply cannot get Wireguard up and running on my Odroid HC2 with Armbian.
</p>

<p>
	 
</p>

<p>
	Running...
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">echo "deb http://deb.debian.org/debian/ unstable main" &gt; /etc/apt/sources.list.d/unstable-wireguard.list
printf 'Package: *\nPin: release a=unstable\nPin-Priority: 90\n' &gt; /etc/apt/preferences.d/limit-unstable
apt update
apt install -y linux-headers-odroidxu4 wireguard</span></pre>

<p>
	yields...
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">Loading new wireguard-0.0.20181218 DKMS files...
dpkg: warning: version '3.10.106-odroidxu4
4.19.14' has bad syntax: invalid character in revision number
Building for 4.19.14-odroidxu4
Module build for kernel 4.19.14-odroidxu4 was skipped since the
kernel headers for this kernel does not seem to be installed.</span></pre>

<p>
	 
</p>

<p>
	Do I really need to compile Wireguard from source? <span>:-(</span>
</p>
]]></description><guid isPermaLink="false">9282</guid><pubDate>Fri, 11 Jan 2019 17:20:59 +0000</pubDate></item><item><title>armbian and OMV upgrade 6 to 7 - package held back on HC1</title><link>https://testforum.armbian.com/topic/43114-armbian-and-omv-upgrade-6-to-7-package-held-back-on-hc1/</link><description><![CDATA[<p>
	Hello community!
</p>

<p>
	 
</p>

<p>
	I have performed an update from armbian 11 to 12 and OMV 6 to 7 and completed it successfully so far. Unfortunately just the package armbian-bsp-cli-odroidxu4 was not upgraded due to a missing dependency:
</p>

<p>
	 
</p>

<p>
	+++
</p>

<p>
	 
</p>

<p>
	The following packages have unmet dependencies:<br />
	 <strong>armbian-bsp-cli-odroidxu4-current</strong> : Depends: base-files (&gt;= 24.5.1) but <strong>12.4+deb12u6</strong> is to be installed<br />
	E: Unable to correct problems, you have held broken packages.
</p>

<p>
	 
</p>

<p>
	root@omv:~# sudo apt install 12.4+deb12u6<br />
	Reading package lists... Done<br />
	Building dependency tree... Done<br />
	Reading state information... Done<br />
	E: Unable to locate package 12.4+deb12u6<br />
	E: Couldn't find any package by glob '12.4+deb12u6'
</p>

<p>
	 
</p>

<p>
	ok, let‘s try:
</p>

<p>
	 
</p>

<p>
	root@omv:~# sudo apt install 12.4+deb12u6-current<br />
	Reading package lists... Done<br />
	Building dependency tree... Done<br />
	Reading state information... Done<br />
	E: Unable to locate package 12.4+deb12u6-current<br />
	E: Couldn't find any package by glob '12.4+deb12u6-current'
</p>

<p>
	 
</p>

<p>
	+++
</p>

<p>
	 
</p>

<p>
	Is this package simply not available in the armbian repository or did I something fundamental wrong?
</p>
]]></description><guid isPermaLink="false">43114</guid><pubDate>Mon, 29 Jul 2024 06:20:17 +0000</pubDate></item><item><title>Issue with CPU frequency after update to 24.5.1 with Kernel 6.6.31-current-odroid-xu4</title><link>https://testforum.armbian.com/topic/40907-issue-with-cpu-frequency-after-update-to-2451-with-kernel-6631-current-odroid-xu4/</link><description><![CDATA[<p>
	Hi, I'm running OMV on Odroid HC2.
</p>

<p>
	 
</p>

<p>
	I updated to OMV 7.7.1. Armbian to 24.5.1 with Linux kernel 6.6.31-current-odroid-xu4.
</p>

<p>
	 
</p>

<p>
	After reboot the server started to act very slow. I tried to reapply the DBT for HC1/2 via armbian-config but this did not help.
</p>

<p>
	armbian-config says I'm on ondemand governor between 200-200 MHz.
</p>

<p>
	 
</p>

<p>
	What could be the issue?
</p>

<p>
	 
</p>

<p>
	Actually my system says I should run 
</p>

<p>
	 
</p>

<pre class="ipsCode">dpkg --configure -a</pre>

<p>
	 
</p>

<p>
	but this command hang here and the system reboots after few seconds...
</p>

<p>
	 
</p>

<pre class="ipsCode">steakhutzeee@dk:~$ sudo dpkg --configure -a
[sudo] password for steakhutzeee:
Setting up containerd.io (1.6.33-1) ...</pre>

<p>
	 
</p>

<p>
	EDIT: From armbian-config -&gt; CPU (deprecated) I applied the max I could find. Now armbian-config states I'm running 1800-1800 MHz. I was able to successfully run the dpkg command and update my system.
</p>

<p>
	 
</p>

<pre class="ipsCode">steakhutzeee@dk:~$ grep . /sys/devices/system/cpu/cpu0/cpufreq/*
/sys/devices/system/cpu/cpu0/cpufreq/affected_cpus:0 1 2 3
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq:1400000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq:1400000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_min_freq:200000
/sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency:155000
/sys/devices/system/cpu/cpu0/cpufreq/related_cpus:0 1 2 3
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies:200000 300000 400000 500000 600000 700000 800000 900000 1000000 1100000 1200000 1300000 1400000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors:userspace powersave conservative ondemand performance schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq:1400000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver:cpufreq-dt
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor:ondemand
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq:1400000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq:1400000
/sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed:&lt;unsupported&gt;
grep: /sys/devices/system/cpu/cpu0/cpufreq/stats: Is a directory</pre>

<p>
	 
</p>

<p>
	I did:
</p>

<p>
	 
</p>

<p>
	echo 1400000 | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_max_freq<br />
	echo 200000 | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_min_freq
</p>

<p>
	 
</p>

<p>
	If this issue with frequencies has to be fixed with an update, how can I set a correct frequency manually now? I'm afraid this high freq could cause damage actually.
</p>

<p>
	 
</p>

<p>
	Thank you!
</p>
]]></description><guid isPermaLink="false">40907</guid><pubDate>Sat, 08 Jun 2024 19:49:59 +0000</pubDate></item><item><title>CPU clock too low / Odroid HC1</title><link>https://testforum.armbian.com/topic/40628-cpu-clock-too-low-odroid-hc1/</link><description><![CDATA[<p>
	Hi
</p>

<p>
	<br>
	The problem with Odroid HC1 is that BIG cores cannot go higher than 1.50Ghz and LITTLE cores cannot go higher than 900Mhz!<br>
	 <br>
	Why is the CPU so throttled now? This <abbr title="Single board computer"><abbr title="Single board computer">sbc</abbr></abbr> can and could work at higher clock speeds without any problems.<br>
	Forcing 2Ghz and 1.50Ghz via cpupower does not help...
</p>

<p>
	 
</p>

<p>
	Bullseye
</p>

<p>
	A 23.8.27<br>
	K 6.6.31
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<a class="ipsAttachLink ipsAttachLink_image" href="https://testforum.armbian.com/uploads/monthly_2024_06/hc1.png.2a770cf234ae3c66237d583670fdbba1.png" data-fileid="12590" data-fileext="png" rel=""><img alt="hc1.png" class="ipsImage ipsImage_thumbnailed" data-fileid="12590" width="952" src="https://testforum.armbian.com/uploads/monthly_2024_06/hc1.png.2a770cf234ae3c66237d583670fdbba1.png" loading="lazy" height="199.92"></a>
</p>
]]></description><guid isPermaLink="false">40628</guid><pubDate>Mon, 03 Jun 2024 21:36:33 +0000</pubDate></item><item><title>Boot error</title><link>https://testforum.armbian.com/topic/36110-boot-error/</link><description><![CDATA[<p>
	When I run the Linux kernel on the Odroid XU4 board, it enters a loop with this error during boot:
</p>

<pre class="ipsCode">U-Boot 2017.05-00008-g6a9ddb8303-dirty (May 19 2020 - 19:48:01 +0900) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  xu4
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 29.7 GiB
mmc_init: -5, time 4
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0
reading /boot.ini
2401 bytes read in 4 ms (585.9 KiB/s)
## Executing script at 43e00000
reading config.ini
6911 bytes read in 5 ms (1.3 MiB/s)
ini: Imported macaddr as 00:1e:06:61:7a:39
ini: Imported vout as hdmi
ini: Imported HPD as true
ini: Imported cecenable as false
ini: Imported disable_vu7 as false
ini: Imported ddr_freq as 825
ini: Imported overlay_resize as 16384
ini: Imported overlay_profile as
ini: Imported overlays as spi0 i2c0 i2c1 uart0
No FDT memory address configured. Please configure
the FDT address via "fdt addr &lt;address&gt;" command.
Aborting!
reading zImage
7299952 bytes read in 490 ms (14.2 MiB/s)
reading exynos5422-odroidxu4.dtb
88559 bytes read in 11 ms (7.7 MiB/s)
reading overlays/spi0.dtbo
691 bytes read in 5 ms (134.8 KiB/s)
reading overlays/i2c0.dtbo
224 bytes read in 5 ms (43 KiB/s)
reading overlays/i2c1.dtbo
226 bytes read in 5 ms (43.9 KiB/s)
reading overlays/uart0.dtbo
227 bytes read in 6 ms (36.1 KiB/s)
Kernel image @ 0x40008000 [ 0x000000 - 0x6f6370 ]
## Flattened Device Tree blob at 44000000
   Booting using the fdt blob at 0x44000000
   reserving fdt memory region: addr=44000000 size=2c000
   Using Device Tree in place at 44000000, end 4402efff

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x100
[    0.000000] Linux version 6.1.77+ (odroid@odroid) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PREEMPT Wed Mar  6 17:56:35 -03 2024
[    0.000000] CPU: ARMv7 Processor [410fc073] revision 3 (ARMv7), cr=30c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Hardkernel ODROID XU4
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] cma: Reserved 128 MiB at 0x00000000b6800000
[    0.000000] Samsung CPU ID: 0xe5422001
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000040000000-0x000000006fffffff]
[    0.000000]   HighMem  [mem 0x0000000070000000-0x00000000be9fffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000be9fffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000be9fffff]
[    0.000000] Running under secure firmware.
[    0.000000] percpu: Embedded 17 pages/cpu s39124 r8192 d22316 u69632
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516928
[    0.000000] Kernel command line: console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes net.ifnames=0  HPD=true vout=hdmi e
[    0.000000] hdmi: using HDMI mode
[    0.000000] Unknown kernel command line parameters "false HPD=true vout=hdmi", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 1903668K/2074624K available (12288K kernel code, 1139K rwdata, 2940K rodata, 2048K init, 363K bss, 39884K reserved, 131072K cma-reserved, 1157120K highmem)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=8, Nodes=1
[    0.000000] trace event string verifier disabled
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000]  Trampoline variant of Tasks RCU enabled.
[    0.000000]  Tracing variant of Tasks RCU enabled.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[    0.000000] Switching to timer-based delay loop, resolution 41ns
[    0.000000] clocksource: mct-frc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000002] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000032] genirq: irq_chip COMBINER did not update eff. affinity mask of irq 57
[    0.001509] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.001535] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.001555] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.001572] Ignoring duplicate/late registration of read_current_timer delay
[    0.002351] Console: colour dummy device 80x30
[    0.003109] printk: console [tty1] enabled
[    0.003176] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=240000)
[    0.003223] CPU: Testing write buffer coherency: ok
[    0.003313] pid_max: default: 32768 minimum: 301
[    0.003464] LSM: Security Framework initializing
[    0.003658] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.003711] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.005467] CPU0: thread -1, cpu 0, socket 1, mpidr 80000100
[    0.006882] cblist_init_generic: Setting adjustable number of callback queues.
[    0.006928] cblist_init_generic: Setting shift to 3 and lim to 1.
[    0.007116] cblist_init_generic: Setting adjustable number of callback queues.
[    0.007151] cblist_init_generic: Setting shift to 3 and lim to 1.
[    0.007359] Setting up static identity map for 0x40200000 - 0x40200060
[    0.007711] ARM CCI driver probed
[    0.008305] Exynos MCPM support installed
[    0.008707] rcu: Hierarchical SRCU implementation.
[    0.008734] rcu:     Max phase no-delay instances is 1000.
[    0.010012] smp: Bringing up secondary CPUs ...
[    0.011171] CPU1: thread -1, cpu 1, socket 1, mpidr 80000101
[    0.012478] CPU2: thread -1, cpu 2, socket 1, mpidr 80000102
[    0.013707] CPU3: thread -1, cpu 3, socket 1, mpidr 80000103
[    0.014902] CPU4: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.014919] CPU4: detected I-Cache line size mismatch, workaround enabled
[    0.014927] CPU4: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.015018] CPU4: Spectre BHB: enabling loop workaround for all CPUs
[    0.016286] CPU5: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.016300] CPU5: detected I-Cache line size mismatch, workaround enabled
[    0.016307] CPU5: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.017624] CPU6: thread -1, cpu 2, socket 0, mpidr 80000002
[    0.017638] CPU6: detected I-Cache line size mismatch, workaround enabled
[    0.017645] CPU6: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.018922] CPU7: thread -1, cpu 3, socket 0, mpidr 80000003
[    0.018937] CPU7: detected I-Cache line size mismatch, workaround enabled
[    0.018945] CPU7: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
[    0.019180] smp: Brought up 1 node, 8 CPUs
[    0.019244] SMP: Total of 8 processors activated (384.00 BogoMIPS).
[    0.019276] CPU: All CPU(s) started in HYP mode.
[    0.019297] CPU: Virtualization extensions available.
[    0.020752] devtmpfs: initialized
[    0.042523] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.042807] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.042850] futex hash table entries: 2048 (order: 5, 131072 bytes, linear)
[    0.045974] pinctrl core: initialized pinctrl subsystem
[    0.048866] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.052562] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.054296] audit: initializing netlink subsys (disabled)
[    0.054571] audit: type=2000 audit(0.050:1): state=initialized audit_enabled=0 res=1
[    0.055157] thermal_sys: Registered thermal governor 'step_wise'
[    0.055436] cpuidle: using governor menu
[    0.055910] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.055941] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.185987] EXYNOS5420 PMU initialized
[    0.292725] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[    0.294707] fbcon: Taking over console
[    0.296476] iommu: Default domain type: Translated
[    0.296501] iommu: DMA domain TLB invalidation policy: lazy mode
[    0.296909] usbcore: registered new interface driver usbfs
[    0.296979] usbcore: registered new interface driver hub
[    0.297050] usbcore: registered new device driver usb
[    0.297807] s3c-i2c 12c70000.i2c: slave address 0x00
[    0.297837] s3c-i2c 12c70000.i2c: bus frequency set to 378 KHz
[    0.298170] s3c-i2c 12c70000.i2c: i2c-0: S3C I2C adapter
[    0.298383] s3c-i2c 12c80000.i2c: slave address 0x00
[    0.298412] s3c-i2c 12c80000.i2c: bus frequency set to 65 KHz
[    0.298719] s3c-i2c 12c80000.i2c: i2c-2: S3C I2C adapter
[    0.299209] mc: Linux media interface: v0.10
[    0.299295] videodev: Linux video capture interface: v2.00
[    0.299921] Advanced Linux Sound Architecture Driver Initialized.
[    0.301010] clocksource: Switched to clocksource mct-frc
[    0.301481] VFS: Disk quotas dquot_6.6.0
[    0.301559] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.315803] NET: Registered PF_INET protocol family
[    0.316073] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.317886] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    0.317937] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.318036] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.318132] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[    0.318434] TCP: Hash tables configured (established 8192 bind 8192)
[    0.318557] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.318617] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[    0.318871] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.318931] NET: Registered PF_XDP protocol family
[    0.320817] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[    0.322010] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[    0.324097] Initialise system trusted keyrings
[    0.324437] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    0.333908] romfs: ROMFS MTD (C) 2007 Red Hat, Inc.
[    0.421548] NET: Registered PF_ALG protocol family
[    0.421584] Key type asymmetric registered
[    0.421605] Asymmetric key parser 'x509' registered
[    0.421839] bounce: pool size: 64 pages
[    0.421992] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    0.422397] io scheduler mq-deadline registered
[    0.422425] io scheduler kyber registered
[    0.422681] io scheduler bfq registered
[    0.424520] samsung-pinctrl 13400000.pinctrl: Failed to create device link (0x180) with soc
[    0.426837] samsung-usb2-phy 12130000.phy: supply vbus not found, using dummy regulator
[    0.427839] exynos5_usb3drd_phy 12100000.phy: supply vbus not found, using dummy regulator
[    0.428032] exynos5_usb3drd_phy 12100000.phy: supply vbus-boost not found, using dummy regulator
[    0.428460] exynos5_usb3drd_phy 12500000.phy: supply vbus not found, using dummy regulator
[    0.428634] exynos5_usb3drd_phy 12500000.phy: supply vbus-boost not found, using dummy regulator
[    0.436864] dma-pl330 3880000.dma-controller: Loaded driver for PL330 DMAC-241330
[    0.436898] dma-pl330 3880000.dma-controller:        DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    0.439976] dma-pl330 121a0000.dma-controller: Loaded driver for PL330 DMAC-241330
[    0.440008] dma-pl330 121a0000.dma-controller:       DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.443083] dma-pl330 121b0000.dma-controller: Loaded driver for PL330 DMAC-241330
[    0.443116] dma-pl330 121b0000.dma-controller:       DBUFF-32x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
[    0.444270] dma-pl330 10800000.dma-controller: Loaded driver for PL330 DMAC-241330
[    0.444300] dma-pl330 10800000.dma-controller:       DBUFF-64x8bytes Num_Chans-8 Num_Peri-1 Num_Events-32
[    0.461998] dma-pl330 3880000.dma-controller: PM domain MAU will not be powered off
[    0.533568] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    0.536218] 12c00000.serial: ttySAC0 at MMIO 0x12c00000 (irq = 124, base_baud = 0) is a S3C6400/10
[    0.536771] 12c20000.serial: ttySAC2 at MMIO 0x12c20000 (irq = 125, base_baud = 0) is a S3C6400/10
[    1.553526] printk: console [ttySAC2] enabled
[    1.560131] exynos-trng 10830600.rng: Exynos True Random Number Generator.
[    1.567245] exynos-mixer 14450000.mixer: Adding to iommu group 0
[    1.574772] exynos-drm-g2d 10850000.g2d: Adding to iommu group 1
[    1.581147] exynos-rotator 11c00000.rotator: Adding to iommu group 2
[    1.587248] exynos-scaler 12800000.scaler: Adding to iommu group 3
[    1.593888] exynos-scaler 12810000.scaler: Adding to iommu group 4
[    1.600295] exynos-scaler 12820000.scaler: Adding to iommu group 5
[    1.607009] exynos-drm-gsc 13e00000.video-scaler: Adding to iommu group 6
[    1.613211] exynos-drm-gsc 13e00000.video-scaler: drm gsc registered successfully.
[    1.620298] exynos-drm-gsc 13e10000.video-scaler: Adding to iommu group 7
[    1.627466] exynos-drm-gsc 13e10000.video-scaler: drm gsc registered successfully.
[    1.652020] brd: module loaded
[    1.654773] usbcore: registered new device driver r8152-cfgselector
[    1.659902] usbcore: registered new interface driver r8152
[    1.665405] usbcore: registered new interface driver cdc_ether
[    1.671186] usbcore: registered new interface driver cdc_subset
[    1.677065] usbcore: registered new interface driver r8153_ecm
[    1.685749] phy phy-12130000.phy.6: phy_power_on was called before phy_init
[    1.691276] exynos-ehci 12110000.usb: EHCI Host Controller
[    1.696714] exynos-ehci 12110000.usb: new USB bus registered, assigned bus number 1
[    1.704845] exynos-ehci 12110000.usb: irq 133, io mem 0x12110000
[    1.731064] exynos-ehci 12110000.usb: USB 2.0 started, EHCI 1.00
[    1.735818] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[    1.743876] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.751068] usb usb1: Product: EHCI Host Controller
[    1.755880] usb usb1: Manufacturer: Linux 6.1.77+ ehci_hcd
[    1.761370] usb usb1: SerialNumber: 12110000.usb
[    1.766665] hub 1-0:1.0: USB hub found
[    1.769693] hub 1-0:1.0: 3 ports detected
[    1.774988] phy phy-12130000.phy.6: phy_power_on was called before phy_init
[    1.780583] exynos-ohci 12120000.usb: USB Host Controller
[    1.786000] exynos-ohci 12120000.usb: new USB bus registered, assigned bus number 2
[    1.793806] exynos-ohci 12120000.usb: irq 133, io mem 0x12120000
[    1.865293] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.01
[    1.872132] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.879280] usb usb2: Product: USB Host Controller
[    1.884074] usb usb2: Manufacturer: Linux 6.1.77+ ohci_hcd
[    1.889502] usb usb2: SerialNumber: 12120000.usb
[    1.894774] hub 2-0:1.0: USB hub found
[    1.897855] hub 2-0:1.0: 3 ports detected
[    1.904077] UDC core: dbgp: couldn't find an available UDC
[    1.908531] mousedev: PS/2 mouse device common for all mice
[    1.915382] i2c_dev: i2c /dev entries driver
[    1.943247] vdd_ldo9: Bringing 3300000uV into 3000000-3000000uV
[    1.960292] vddq_mmc2: Bringing 3300000uV into 2800000-2800000uV
[    1.979785] vdd_sd: Bringing 3300000uV into 2800000-2800000uV
[    2.049199] s5m-rtc s2mps14-rtc: registered as rtc0
[    2.054487] s5m-rtc s2mps14-rtc: setting system clock to 2000-01-01T00:00:08 UTC (946684808)
[    2.061844] s2mps11-clk s2mps11-clk: DMA mask not set
[    2.076557] exynos-tmu 10060000.tmu: More trip points than supported by this TMU.
[    2.082622] exynos-tmu 10060000.tmu: 2 trip points should be configured in polling mode.
[    2.092426] exynos-tmu 10064000.tmu: More trip points than supported by this TMU.
[    2.098440] exynos-tmu 10064000.tmu: 2 trip points should be configured in polling mode.
[    2.108348] exynos-tmu 10068000.tmu: More trip points than supported by this TMU.
[    2.114407] exynos-tmu 10068000.tmu: 2 trip points should be configured in polling mode.
[    2.124320] exynos-tmu 1006c000.tmu: More trip points than supported by this TMU.
[    2.130338] exynos-tmu 1006c000.tmu: 2 trip points should be configured in polling mode.
[    2.140250] exynos-tmu 100a0000.tmu: More trip points than supported by this TMU.
[    2.146302] exynos-tmu 100a0000.tmu: 6 trip points should be configured in polling mode.
[    2.155544] s3c2410-wdt 101d0000.watchdog: watchdog inactive, reset disabled, irq disabled
[    2.163331] device-mapper: uevent: version 1.0.3
[    2.167537] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[    2.191451] sdhci: Secure Digital Host Controller Interface driver
[    2.196199] sdhci: Copyright(c) Pierre Ossman
[    2.201064] Synopsys Designware Multimedia Card Interface Driver
[    2.208067] dwmmc_exynos 12220000.mmc: IDMAC supports 32-bit address mode.
[    2.208115] dwmmc_exynos 12200000.mmc: IDMAC supports 32-bit address mode.
[    2.220477] dwmmc_exynos 12220000.mmc: Using internal DMA controller.
[    2.224492] s5p-secss 10830000.sss: s5p-sss driver registered
[    2.226796] dwmmc_exynos 12220000.mmc: Version ID is 250a
[    2.232750] dwmmc_exynos 12200000.mmc: Using internal DMA controller.
[    2.234102] hid: raw HID events driver (C) Jiri Kosina
[    2.238124] dwmmc_exynos 12220000.mmc: DW MMC controller at irq 144,64 bit host data width,64 deep fifo
[    2.244291] dwmmc_exynos 12200000.mmc: Version ID is 250a
[    2.264162] dwmmc_exynos 12200000.mmc: DW MMC controller at irq 145,64 bit host data width,64 deep fifo
[    2.268759] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.275936] dwmmc_exynos 12200000.mmc: allocated mmc-pwrseq
[    2.292675] exynos-nocp: new NoC Probe device registered: 10ca1000.nocp
[    2.297970] exynos-nocp: new NoC Probe device registered: 10ca1400.nocp
[    2.304571] exynos-nocp: new NoC Probe device registered: 10ca1800.nocp
[    2.305514] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    2.312086] exynos-nocp: new NoC Probe device registered: 10ca1c00.nocp
[    2.327451] exynos-ppmu: new PPMU device registered 10d00000.ppmu (ppmu-event3-dmc0-0)
[    2.335102] exynos-ppmu: new PPMU device registered 10d10000.ppmu (ppmu-event3-dmc0-1)
[    2.342974] exynos-ppmu: new PPMU device registered 10d60000.ppmu (ppmu-event3-dmc1-0)
[    2.350839] exynos-ppmu: new PPMU device registered 10d70000.ppmu (ppmu-event3-dmc1-1)
[    2.361081] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_0 not found
[    2.367518] exynos5-dmc 10c20000.memory-controller: error -ENXIO: IRQ drex_1 not found
[    2.375591] exynos5-dmc 10c20000.memory-controller: DMC initialized, in irq mode: 0
[    2.384755] mmc_host mmc0: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    2.394797] samsung-i2s 3830000.i2s-sec: DMA channels sourced from device 3830000.i2s
[    2.397011] mmc0: new ultra high speed SDR104 SDHC card at address aaaa
[    2.407340] NET: Registered PF_PACKET protocol family
[    2.409624] mmcblk0: mmc0:aaaa SE32G 29.7 GiB
[    2.412797] NET: Registered PF_KEY protocol family
[    2.422627] Key type dns_resolver registered
[    2.426187]  mmcblk0: p1 p2
[    2.426754] Registering SWP/SWPB emulation handler
[    2.434051] registered taskstats version 1
[    2.437817] Loading compiled-in X.509 certificates
[    2.443116] Key type .fscrypt registered
[    2.446464] Key type fscrypt-provisioning registered
[    2.457336] Key type encrypted registered
[    2.588749] exynos-chipid 10000000.chipid: cpu0 opp0, freq: 1500 missing
[    2.594193] exynos-chipid 10000000.chipid: cpu4 opp0, freq: 2100 missing
[    2.600762] exynos-chipid 10000000.chipid: Exynos: CPU[EXYNOS5800] PRO_ID[0xe5422000] REV[0x1] Detected
[    2.617722] OF: graph: no port node found in /soc/hdmi@14530000
[    2.624147] [drm] Exynos DRM: using 14450000.mixer device for DMA mapping operations
[    2.630520] exynos-drm exynos-drm: bound 14450000.mixer (ops 0xc0e7bc8c)
[    2.637165] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0e7c26c)
[    2.643884] exynos-drm-g2d 10850000.g2d: The Exynos G2D (ver 4.1) successfully registered.
[    2.651958] exynos-drm exynos-drm: bound 10850000.g2d (ops 0xc0e7d27c)
[    2.658441] exynos-rotator 11c00000.rotator: The exynos rotator has been probed successfully
[    2.666855] exynos-drm exynos-drm: bound 11c00000.rotator (ops 0xc0e7db08)
[    2.673723] exynos-scaler 12800000.scaler: The exynos scaler has been probed successfully
[    2.681842] exynos-drm exynos-drm: bound 12800000.scaler (ops 0xc0e7e250)
[    2.688607] exynos-scaler 12810000.scaler: The exynos scaler has been probed successfully
[    2.696755] exynos-drm exynos-drm: bound 12810000.scaler (ops 0xc0e7e250)
[    2.703526] exynos-scaler 12820000.scaler: The exynos scaler has been probed successfully
[    2.711662] exynos-drm exynos-drm: bound 12820000.scaler (ops 0xc0e7e250)
[    2.718396] exynos-drm-gsc 13e00000.video-scaler: The exynos gscaler has been probed successfully
[    2.727314] exynos-drm exynos-drm: bound 13e00000.video-scaler (ops 0xc0e7eb24)
[    2.734594] exynos-drm-gsc 13e10000.video-scaler: The exynos gscaler has been probed successfully
[    2.743425] exynos-drm exynos-drm: bound 13e10000.video-scaler (ops 0xc0e7eb24)
[    2.791131] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    2.838676] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    2.878753] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
[    2.907827] Console: switching to colour frame buffer device 180x56
[    2.973325] exynos-drm exynos-drm: [drm] fb0: exynosdrmfb frame buffer device
[    2.984476] [drm] Initialized exynos 1.1.0 20180330 for exynos-drm on minor 0
[    3.004351] mali 11800000.gpu: GPU identified as 0x0620 r0p1 status 0
[    3.010719] mali 11800000.gpu: Protected mode not available
[    3.018316] mali 11800000.gpu: Probed as mali0
[    3.026735] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller
[    3.030849] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 3
[    3.039677] xhci-hcd xhci-hcd.8.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[    3.048138] xhci-hcd xhci-hcd.8.auto: irq 153, io mem 0x12000000
[    3.054235] xhci-hcd xhci-hcd.8.auto: xHCI Host Controller
[    3.059294] xhci-hcd xhci-hcd.8.auto: new USB bus registered, assigned bus number 4
[    3.066981] xhci-hcd xhci-hcd.8.auto: Host supports USB 3.0 SuperSpeed
[    3.073679] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[    3.081733] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.088855] usb usb3: Product: xHCI Host Controller
[    3.093692] usb usb3: Manufacturer: Linux 6.1.77+ xhci-hcd
[    3.099147] usb usb3: SerialNumber: xhci-hcd.8.auto
[    3.105733] hub 3-0:1.0: USB hub found
[    3.108240] hub 3-0:1.0: 1 port detected
[    3.113412] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.120627] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[    3.128666] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.135843] usb usb4: Product: xHCI Host Controller
[    3.140461] usb usb4: Manufacturer: Linux 6.1.77+ xhci-hcd
[    3.148036] usb usb4: SerialNumber: xhci-hcd.8.auto
[    3.153685] hub 4-0:1.0: USB hub found
[    3.157741] hub 4-0:1.0: 1 port detected
[    3.169399] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[    3.175224] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 5
[    3.183781] xhci-hcd xhci-hcd.9.auto: hcc params 0x0220f04c hci version 0x100 quirks 0x0000000002010010
[    3.193572] xhci-hcd xhci-hcd.9.auto: irq 154, io mem 0x12400000
[    3.200100] xhci-hcd xhci-hcd.9.auto: xHCI Host Controller
[    3.205886] xhci-hcd xhci-hcd.9.auto: new USB bus registered, assigned bus number 6
[    3.213785] xhci-hcd xhci-hcd.9.auto: Host supports USB 3.0 SuperSpeed
[    3.220664] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.01
[    3.229213] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.236762] usb usb5: Product: xHCI Host Controller
[    3.241897] usb usb5: Manufacturer: Linux 6.1.77+ xhci-hcd
[    3.247575] usb usb5: SerialNumber: xhci-hcd.9.auto
[    3.253145] hub 5-0:1.0: USB hub found
[    3.257072] hub 5-0:1.0: 1 port detected
[    3.261543] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[    3.269904] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.01
[    3.278421] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    3.285801] usb usb6: Product: xHCI Host Controller
[    3.290803] usb usb6: Manufacturer: Linux 6.1.77+ xhci-hcd
[    3.292505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    3.294925] usb usb6: SerialNumber: xhci-hcd.9.auto
[    3.314476] hub 6-0:1.0: USB hub found
[    3.318373] hub 6-0:1.0: 1 port detected
[    3.324905] s3c-rtc 101e0000.rtc: rtc disabled, re-enabling
[    3.330709] s3c-rtc 101e0000.rtc: registered as rtc1
[    3.340796] exynos-bus: new bus device registered: soc:bus-wcore ( 88700 KHz ~ 532000 KHz)
[    3.345656] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    3.348273] exynos-bus: new bus device registered: soc:bus-noc ( 66600 KHz ~ 111000 KHz)
[    3.370263] exynos-bus: new bus device registered: soc:bus-fsys-apb (111000 KHz ~ 222000 KHz)
[    3.379488] exynos-bus: new bus device registered: soc:bus-fsys2 ( 75000 KHz ~ 200000 KHz)
[    3.388608] exynos-bus: new bus device registered: soc:bus-mfc ( 83250 KHz ~ 333000 KHz)
[    3.397524] exynos-bus: new bus device registered: soc:bus-gen ( 88700 KHz ~ 266000 KHz)
[    3.406667] exynos-bus: new bus device registered: soc:bus-peri ( 66600 KHz ~  66600 KHz)
[    3.411109] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[    3.419851] exynos-bus: new bus device registered: soc:bus-g2d ( 83250 KHz ~ 333000 KHz)
[    3.431814] exynos-bus: new bus device registered: soc:bus-g2d-acp ( 66500 KHz ~ 266000 KHz)
[    3.440249] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    3.440969] exynos-bus: new bus device registered: soc:bus-jpeg ( 75000 KHz ~ 300000 KHz)
[    3.460397] exynos-bus: new bus device registered: soc:bus-jpeg-apb ( 83250 KHz ~ 166500 KHz)
[    3.469573] exynos-bus: new bus device registered: soc:bus-disp1-fimd (120000 KHz ~ 200000 KHz)
[    3.478997] exynos-bus: new bus device registered: soc:bus-disp1 (120000 KHz ~ 300000 KHz)
[    3.487932] exynos-bus: new bus device registered: soc:bus-gscl-scaler (150000 KHz ~ 300000 KHz)
[    3.497582] exynos-bus: new bus device registered: soc:bus-mscl ( 84000 KHz ~ 666000 KHz)
[    3.508589] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
[    3.535680] ALSA device list:
[    3.539420]   #0: ODROID-XU4
[    3.544075] Waiting for root device UUID=e139ce78-9841-40fe-8823-96a304a09859...
[    3.605856] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=22.23
[    3.615230] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.623491] usb 3-1: Product: USB2.0 Hub
[    3.628491] usb 3-1: Manufacturer: GenesysLogic
[    3.682358] hub 3-1:1.0: USB hub found
[    3.689564] hub 3-1:1.0: 2 ports detected
[    3.751499] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[    3.794759] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616, bcdDevice=22.23
[    3.805887] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    3.815965] usb 4-1: Product: USB3.0 Hub
[    3.822775] usb 4-1: Manufacturer: GenesysLogic
[    3.858309] hub 4-1:1.0: USB hub found
[    3.863915] hub 4-1:1.0: 2 ports detected
[    4.061238] usb 3-1.1: new low-speed USB device number 3 using xhci-hcd
[    4.206144] usb 3-1.1: New USB device found, idVendor=046d, idProduct=c077, bcdDevice=72.00
[    4.221958] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.233307] usb 3-1.1: Product: USB Optical Mouse
[    4.238474] usb 3-1.1: Manufacturer: Logitech
[    4.371238] usb 6-1: new SuperSpeed USB device number 2 using xhci-hcd
[    4.391069] usb 3-1.2: new low-speed USB device number 4 using xhci-hcd
[    4.412822] usb 6-1: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00
[    4.422627] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[    4.431336] usb 6-1: Product: USB 10/100/1000 LAN
[    4.437514] usb 6-1: Manufacturer: Realtek
[    4.443094] usb 6-1: SerialNumber: 000001000000
[    4.536824] usb 3-1.2: New USB device found, idVendor=1a2c, idProduct=2d23, bcdDevice= 1.10
[    4.549773] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.559722] usb 3-1.2: Product: USB Keyboard
[    4.564096] usb 3-1.2: Manufacturer: USB
[    4.677461] r8152-cfgselector 6-1: reset SuperSpeed USB device number 2 using xhci-hcd
[    4.733246] r8152 6-1:1.0: Direct firmware load for rtl_nic/rtl8153a-3.fw failed with error -2
[    4.742982] r8152 6-1:1.0: unable to load firmware patch rtl_nic/rtl8153a-3.fw (-2)
[    4.793138] r8152 6-1:1.0 eth0: v1.12.13
[    4.939315] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    5.000498] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    5.060339] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    5.119528] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
[    5.459354] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    5.522765] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    5.578951] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    5.635751] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
[    5.979379] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    6.042260] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    6.098485] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    6.157505] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
[    6.498761] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    6.556671] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    6.612113] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    6.668707] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
[    7.009370] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    7.070667] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 300000Hz, actual 297619HZ div = 84)
[    7.126100] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 200000Hz, actual 200000HZ div = 125)
[    7.183829] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 100000Hz, actual 100000HZ div = 250)
</pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">36110</guid><pubDate>Wed, 13 Mar 2024 18:43:33 +0000</pubDate></item><item><title>Odroid XU-4 NAS Hard drives automatically in standby</title><link>https://testforum.armbian.com/topic/33415-odroid-xu-4-nas-hard-drives-automatically-in-standby/</link><description><![CDATA[<p>
	Hello, I use an Odroid XU with Armbian and Webmin as a NAS drive. I have 6 hard drives (GPT format) connected. Under an old Linux version I was able to put the hard drives into standby with /etc/ <abbr title="Release candidate">rc</abbr>.local (hdparm -S). Since I started running the system with Armbian, standby no longer works. A query via hdparm says "Standby", but the disks are still spinning. Am I fundamentally doing something wrong? Thank you!
</p>
]]></description><guid isPermaLink="false">33415</guid><pubDate>Wed, 24 Jan 2024 13:22:33 +0000</pubDate></item><item><title>Odroid HC1/HC2/XU Kernel issues with fstrim on Kernel 6.1.x</title><link>https://testforum.armbian.com/topic/33200-odroid-hc1hc2xu-kernel-issues-with-fstrim-on-kernel-61x/</link><description><![CDATA[<p>
	I had to roll back and use apt hold on the 2 corresponding packages to remain on the "good" <abbr title="Long term support">LTS</abbr> kernel 5.4.253 that supports fstrim on extremely popular Crucial SSDs that support it.<br />
	It's impossible to get the maintainer Joe to reply. Is there a triage way to have someone contact him and make him aware of this issue?
</p>

<p>
	 
</p>

<p>
	I have zero complaints about his work, but SATA TRIM commands are a must have on SBCs that have drive bays. It dramatically increases lifetime of <abbr title="A type of flash memory">NAND</abbr> based storage devices.
</p>

<p>
	 
</p>

<p>
	Please tell me what to do. I found filing a simple bug report would be counter productive as I want to investigate why later Kernels are either compiled without support for it or what causes later Kernels to break.<br />
	We are talking about a feature here that is available in every Desktop *NIX OS.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">33200</guid><pubDate>Sun, 14 Jan 2024 12:32:05 +0000</pubDate></item><item><title>Latest Jammy on XU-4 slow after nand-sata-install</title><link>https://testforum.armbian.com/topic/32798-latest-jammy-on-xu-4-slow-after-nand-sata-install/</link><description><![CDATA[<p>
	I just installed latest Jammy on XU-4 and it was running fine off SD. Then I did <abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install and you can see below what happened. This used to work fine with older versions.
</p>

<p>
	 
</p>

<pre class="ipsCode">sudo hdparm -Tt /dev/sda

/dev/sda:
 Timing cached reads:     2 MB in  5.54 seconds = 369.48 kB/sec
 Timing buffered disk reads:   2 MB in 10.33 seconds = 198.19 kB/sec</pre>

<p>
	<br />
	 
</p>
]]></description><guid isPermaLink="false">32798</guid><pubDate>Sat, 23 Dec 2023 17:53:12 +0000</pubDate></item><item><title>Trying to install Wireguard plugin with OMV6 results in Odroid HC2 being stuck in bootloader</title><link>https://testforum.armbian.com/topic/32052-trying-to-install-wireguard-plugin-with-omv6-results-in-odroid-hc2-being-stuck-in-bootloader/</link><description><![CDATA[<p>
	I already posted the question in the <a href="https://forum.odroid.com/viewtopic.php?f=99&amp;p=378029" rel="external nofollow">Odroid forum</a>. I decided to post it here too since it may be more inherent to the Armbian OS.
</p>

<p>
	 
</p>

<p>
	I used both <strong>Armbian_23.02.3_Odroidxu4_bullseye_current_5.4.239.img</strong> from the <a href="https://fi.mirror.armbian.de/archive/odroidxu4/archive/" rel="external nofollow">odroidxu4 archive</a> and <strong>Armbian-unofficial_23.11.0-trunk_Odroidxu4_bullseye_current_6.1.63</strong> generated from the Armbian build script. (Base CLI Image).
</p>

<p>
	 
</p>

<p>
	After flashing the former image and then installing OMV6, this is the output that OMV6 gives me when installing the <strong>openmediavault-wireguard</strong> plugin:<br />
	 
</p>

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

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode">Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  linux-image-6.1.0-0.deb11.13-rt-armmp linux-image-rt-armmp wireguard
  wireguard-tools
Suggested packages:
  linux-doc-6.1 debian-kernel-handbook openresolv | resolvconf
Recommended packages:
  firmware-linux-free apparmor
The following NEW packages will be installed:
  linux-image-6.1.0-0.deb11.13-rt-armmp linux-image-rt-armmp
  openmediavault-wireguard wireguard wireguard-tools
0 upgraded, 5 newly installed, 0 to remove and 8 not upgraded.
Need to get 41.4 MB of archives.
After this operation, 203 MB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main armhf wireguard-tools armhf 1.0.20210223-1 [78.1 kB]
Get:2 http://httpredir.debian.org/debian bullseye-backports/main armhf linux-image-6.1.0-0.deb11.13-rt-armmp armhf 6.1.55-1~bpo11+1 [41.3 MB]
Get:3 http://deb.debian.org/debian bullseye/main armhf wireguard all 1.0.20210223-1 [8164 B]
Get:4 https://openmediavault-plugin-developers.github.io/packages/debian shaitan/main armhf openmediavault-wireguard all 6.3.7 [19.2 kB]
Get:5 http://httpredir.debian.org/debian bullseye-backports/main armhf linux-image-rt-armmp armhf 6.1.55-1~bpo11+1 [1500 B]
Fetched 41.4 MB in 2s (23.0 MB/s)
Selecting previously unselected package linux-image-6.1.0-0.deb11.13-rt-armmp.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 45551 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-0.deb11.13-rt-armmp_6.1.55-1~bpo11+1_armhf.deb ...
Unpacking linux-image-6.1.0-0.deb11.13-rt-armmp (6.1.55-1~bpo11+1) ...
Selecting previously unselected package linux-image-rt-armmp.
Preparing to unpack .../linux-image-rt-armmp_6.1.55-1~bpo11+1_armhf.deb ...
Unpacking linux-image-rt-armmp (6.1.55-1~bpo11+1) ...
Selecting previously unselected package wireguard-tools.
Preparing to unpack .../wireguard-tools_1.0.20210223-1_armhf.deb ...
Unpacking wireguard-tools (1.0.20210223-1) ...
Selecting previously unselected package wireguard.
Preparing to unpack .../wireguard_1.0.20210223-1_all.deb ...
Unpacking wireguard (1.0.20210223-1) ...
Selecting previously unselected package openmediavault-wireguard.
Preparing to unpack .../openmediavault-wireguard_6.3.7_all.deb ...
Unpacking openmediavault-wireguard (6.3.7) ...
Setting up linux-image-6.1.0-0.deb11.13-rt-armmp (6.1.55-1~bpo11+1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-5.4.239-odroidxu4
I: /initrd.img.old is now a symlink to boot/initrd.img-5.4.239-odroidxu4
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-0.deb11.13-rt-armmp
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-0.deb11.13-rt-armmp
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-0.deb11.13-rt-armmp:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-0.deb11.13-rt-armmp
update-initramfs: Converting to u-boot format
Setting up wireguard-tools (1.0.20210223-1) ...
wg-quick.target is a disabled or a static unit, not starting it.
Setting up linux-image-rt-armmp (6.1.55-1~bpo11+1) ...
Setting up wireguard (1.0.20210223-1) ...
Setting up openmediavault-wireguard (6.3.7) ...
Updating configuration database ...
net.ipv4.ip_forward = 1
modprobe: FATAL: Module wireguard not found in directory /lib/modules/5.4.239-odroidxu4
Processing triggers for man-db (2.9.4-2) ...
Processing triggers for openmediavault (6.9.8-1) ...
Updating workbench configuration files ...
Restarting engine daemon ...

END OF LINE</pre>
	</div>
</div>

<p>
	 
</p>

<p>
	Then, after rebooting, here is the output of <strong>minicom</strong>:
</p>

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

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode">U-Boot 2017.05-armbian (Apr 04 2023 - 04:20:05 +0000) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  unknown
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 12
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 
** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
13433 bytes read in 40 ms (327.1 KiB/s)
## Executing script at 43e00000
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
** File not found armbianEnv.txt **
7386616 bytes read in 594 ms (11.9 MiB/s)
35334161 bytes read in 2680 ms (12.6 MiB/s)
0 bytes read in 34 ms (0 Bytes/s)
Found mainline kernel configuration
87881 bytes read in 90 ms (953.1 KiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Kernel image @ 0x40008000 [ 0x000000 - 0x70b5f8 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    35334097 Bytes = 33.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
** File not found /boot.scr **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
mmc_init: -110, time 100
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... XHCI timeout on event type 33... cannot recover.
BUG: failure at drivers/usb/host/xhci-ring.c:467/xhci_wait_for_event()!
BUG!
resetting ...


U-Boot 2017.05-armbian (Apr 04 2023 - 04:20:05 +0000) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  unknown
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 
** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
13433 bytes read in 41 ms (319.3 KiB/s)
## Executing script at 43e00000
** File not found /boot/armbianEnv.txt **
** Unrecognized filesystem type **
** File not found armbianEnv.txt **
7386616 bytes read in 599 ms (11.8 MiB/s)
35334161 bytes read in 2699 ms (12.5 MiB/s)
0 bytes read in 34 ms (0 Bytes/s)
Found mainline kernel configuration
87881 bytes read in 90 ms (953.1 KiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Kernel image @ 0x40008000 [ 0x000000 - 0x70b5f8 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    35334097 Bytes = 33.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
** File not found /boot.scr **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
mmc_init: -110, time 101
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 04 44 81
2 USB Device(s) found
scanning bus 2 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 1 Ethernet Device(s) found

USB device 0: 
    Device 0: not available
Waiting for Ethernet connection... done.
BOOTP broadcast 1</pre>
	</div>
</div>

<p>
	And the ODROID doesn't go further. It stays stuck at  "<strong>BOOTP broadcast 1</strong>".
</p>

<p>
	 
</p>

<p>
	Next, I tried to repeat the same steps with the image generated from the <em>Armbian build script</em>. Here is the output of OMV6 when installing <strong>openmediavault-wireguard</strong>:
</p>

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

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode">Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  linux-image-6.1.0-0.deb11.13-rt-armmp linux-image-rt-armmp wireguard
Suggested packages:
  linux-doc-6.1 debian-kernel-handbook
Recommended packages:
  firmware-linux-free apparmor
The following NEW packages will be installed:
  linux-image-6.1.0-0.deb11.13-rt-armmp linux-image-rt-armmp
  openmediavault-wireguard wireguard
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 41.3 MB of archives.
After this operation, 203 MB of additional disk space will be used.
Get:1 http://httpredir.debian.org/debian bullseye-backports/main armhf linux-image-6.1.0-0.deb11.13-rt-armmp armhf 6.1.55-1~bpo11+1 [41.3 MB]
Get:2 http://deb.debian.org/debian bullseye/main armhf wireguard all 1.0.20210223-1 [8164 B]
Get:3 https://openmediavault-plugin-developers.github.io/packages/debian shaitan/main armhf openmediavault-wireguard all 6.3.7 [19.2 kB]
Get:4 http://httpredir.debian.org/debian bullseye-backports/main armhf linux-image-rt-armmp armhf 6.1.55-1~bpo11+1 [1500 B]
Armbian live patch apt
gpg: keyblock resource '/usr/share/keyrings/armbian.gpg': No such file or directory
Fetched 41.3 MB in 2s (23.3 MB/s)
Selecting previously unselected package linux-image-6.1.0-0.deb11.13-rt-armmp.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 45649 files and directories currently installed.)
Preparing to unpack .../linux-image-6.1.0-0.deb11.13-rt-armmp_6.1.55-1~bpo11+1_armhf.deb ...
Unpacking linux-image-6.1.0-0.deb11.13-rt-armmp (6.1.55-1~bpo11+1) ...
Selecting previously unselected package linux-image-rt-armmp.
Preparing to unpack .../linux-image-rt-armmp_6.1.55-1~bpo11+1_armhf.deb ...
Unpacking linux-image-rt-armmp (6.1.55-1~bpo11+1) ...
Selecting previously unselected package wireguard.
Preparing to unpack .../wireguard_1.0.20210223-1_all.deb ...
Unpacking wireguard (1.0.20210223-1) ...
Selecting previously unselected package openmediavault-wireguard.
Preparing to unpack .../openmediavault-wireguard_6.3.7_all.deb ...
Unpacking openmediavault-wireguard (6.3.7) ...
Setting up linux-image-6.1.0-0.deb11.13-rt-armmp (6.1.55-1~bpo11+1) ...
I: /vmlinuz is now a symlink to boot/vmlinuz-6.1.0-0.deb11.13-rt-armmp
I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-0.deb11.13-rt-armmp
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.1.0-0.deb11.13-rt-armmp:.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.1.0-0.deb11.13-rt-armmp
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.0-0.deb11.13-rt-armmp
Image Name:   uInitrd
Created:      Tue Nov 28 12:16:27 2023
Image Type:   ARM Linux RAMDisk Image (gzip compressed)
Data Size:    35322329 Bytes = 34494.46 KiB = 33.69 MiB
Load Address: 00000000
Entry Point:  00000000
update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.0-0.deb11.13-rt-armmp to /boot/uInitrd
'/boot/uInitrd' -&gt; 'uInitrd-6.1.0-0.deb11.13-rt-armmp'
update-initramfs: Armbian: done.
Setting up linux-image-rt-armmp (6.1.55-1~bpo11+1) ...
Setting up wireguard (1.0.20210223-1) ...
Setting up openmediavault-wireguard (6.3.7) ...
Updating configuration database ...
net.ipv4.ip_forward = 1
Processing triggers for openmediavault (6.9.8-1) ...
Updating workbench configuration files ...

** CONNECTION LOST **</pre>
	</div>
</div>

<p>
	 
</p>

<p>
	And here is the output of <strong>minicom</strong>:
</p>

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

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode">U-Boot 2017.05-armbian (Nov 03 2023 - 07:18:59 +0000) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  unknown
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 
** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
13433 bytes read in 43 ms (304.7 KiB/s)
## Executing script at 43e00000
64 bytes read in 49 ms (1000 Bytes/s)
8421056 bytes read in 680 ms (11.8 MiB/s)
35322393 bytes read in 2694 ms (12.5 MiB/s)
0 bytes read in 39 ms (0 Bytes/s)
Found mainline kernel configuration
83327 bytes read in 96 ms (846.7 KiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Kernel image @ 0x40008000 [ 0x000000 - 0x807ec0 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    35322329 Bytes = 33.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
** File not found /boot.scr **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
mmc_init: -110, time 100
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... XHCI timeout on event type 33... cannot recover.
BUG: failure at drivers/usb/host/xhci-ring.c:467/xhci_wait_for_event()!
BUG!
resetting ...


U-Boot 2017.05-armbian (Nov 03 2023 - 07:18:59 +0000) for ODROID-XU4

CPU:   Exynos5422 @ 800 MHz
Model: Odroid XU4 based on EXYNOS5422
Board: Odroid XU4 based on EXYNOS5422
Type:  unknown
DRAM:  2 GiB
MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
MMC Device 0 ( SD ): 59.5 GiB
Card did not respond to voltage select!
mmc_init: -95, time 11
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Press quickly 'Enter' twice to stop autoboot:  0 
** File not found /boot.ini **
## Executing script at 43e00000
Wrong image format for "source" command
13433 bytes read in 50 ms (261.7 KiB/s)
## Executing script at 43e00000
64 bytes read in 56 ms (1000 Bytes/s)
8421056 bytes read in 688 ms (11.7 MiB/s)
35322393 bytes read in 2706 ms (12.4 MiB/s)
0 bytes read in 46 ms (0 Bytes/s)
Found mainline kernel configuration
83327 bytes read in 103 ms (790 KiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Kernel image @ 0x40008000 [ 0x000000 - 0x807ec0 ]
## Loading init Ramdisk from Legacy Image at 42000000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    35322329 Bytes = 33.7 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
** File not found /boot.scr **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
** Invalid partition 2 **
## Executing script at 43e00000
Wrong image format for "source" command
mmc_init: -110, time 101
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
starting USB...
USB0:   USB EHCI 1.00
USB1:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB2:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... Device NOT ready
   Request Sense returned 04 44 81
2 USB Device(s) found
scanning bus 2 for devices... cannot reset port 1!?
1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
       scanning usb for ethernet devices... 0 Ethernet Device(s) found

USB device 0: 
    Device 0: not available
No ethernet found.
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-exynos
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
No ethernet found.
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
No ethernet found.
Config file not found
No ethernet found.
No ethernet found.
mmc block read, dev 0, addr 0x40008000, blk start 2047, blk cnt 16384
Bad Linux ARM zImage magic!
Exynos5422 # 
</pre>
	</div>
</div>

<p>
	 
</p>

<p>
	What could be the issue?
</p>

<p>
	Thanks in advance for your help.
</p>
]]></description><guid isPermaLink="false">32052</guid><pubDate>Tue, 28 Nov 2023 11:19:49 +0000</pubDate></item><item><title>Root user not available after ncp install</title><link>https://testforum.armbian.com/topic/30954-root-user-not-available-after-ncp-install/</link><description><![CDATA[<p>
	On a fresh armbian bullseye debian install on an odroidhc2, the only change is I installed NCP through armbian softy and a reboot.
</p>

<p>
	My sudo account works, but if I try to sign into root it says account unavailable. How can I fix this?<a class="ipsAttachLink ipsAttachLink_image" data-fileext="jpg" data-fileid="11197" href="https://testforum.armbian.com/uploads/monthly_2023_10/Screenshot_20231023_175200_RaspController.jpg.a0a797c6861637e36cba5f47ba96ad8b.jpg" rel=""><img alt="Screenshot_20231023_175200_RaspController.thumb.jpg.2d0fad0ab8827d2da870e95d5c51b003.jpg" class="ipsImage ipsImage_thumbnailed" data-fileid="11197" width="347" src="https://testforum.armbian.com/uploads/monthly_2023_10/Screenshot_20231023_175200_RaspController.thumb.jpg.2d0fad0ab8827d2da870e95d5c51b003.jpg" loading="lazy" height="749.52"></a>
</p>
]]></description><guid isPermaLink="false">30954</guid><pubDate>Mon, 23 Oct 2023 22:54:03 +0000</pubDate></item><item><title>Armbian hangs at boot because of fstab mount</title><link>https://testforum.armbian.com/topic/30551-armbian-hangs-at-boot-because-of-fstab-mount/</link><description><![CDATA[<p>
	I am using an odroid HC2 as home NAS for some years now. Software is armbian/XU4 in debian flavour. At the moment I am running bookworm (which was updated from buster to bullseye and then to bookworm - I know its not supported but it worked fine. And the problem described here started only some month after the last update).<br />
	<br />
	Some days ago I wanted to reboot the unit but it was stuck in the boot process. Not available by ssh or any other services. I then found out that the boot stopped because my hard disk could not be mounted from ftsab (while the sd card as root file system could be mounted). After commenting out the line it boots normally. And when logged in by ssh I can mount the hard disk without any problem.
</p>

<p>
	 
</p>

<p>
	As a workaround I put the "noauto" option in fstab and mount the drive after a sleep of some seconds from <abbr title="Release candidate"><abbr title="Release candidate">rc</abbr></abbr>.local. That works fine but I am wondering what is causing the problem?
</p>

<p>
	 
</p>

<p>
	Has something in armbian changed so that mounting on boot time doesnt work anymore? Maybe some problem with initializing the sata controller?
</p>

<p>
	 
</p>

<p>
	Or is this a sign of degrading hardware?
</p>

<p>
	 
</p>

<p>
	Any hints welcome.
</p>

<p>
	 
</p>

<p>
	Juergen
</p>
]]></description><guid isPermaLink="false">30551</guid><pubDate>Wed, 04 Oct 2023 15:54:38 +0000</pubDate></item><item><title>Odroid HC2 suddenly keeps crashing/isn't reachable via ssh etc.. after a while</title><link>https://testforum.armbian.com/topic/28731-odroid-hc2-suddenly-keeps-crashingisnt-reachable-via-ssh-etc-after-a-while/</link><description><![CDATA[<p>
	Hello, my Odroid HC2 was working flawlessly for years but since 1-2 weeks it keeps crashing/freezing and I don't know why.
</p>

<p>
	If I cut power and repower it, it works fine for a while but then trying to reach it via ssh, or accessing the harddrive via smb share, or opening a webinterface fails.
</p>

<p>
	I checked the microsd card with 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">armbianmonitor -c "$HOME"</span></pre>

<p>
	and it showed it's fine. I can only provide the logs: <a href="https://paste.armbian.com/cibowaquyi" rel="external nofollow">https://paste.armbian.com/cibowaquyi</a> and hope someone can check them and reply <span class="ipsEmoji">🙏</span>.
</p>

<p>
	I don't know what to look for in the logs that could be wrong...
</p>

<p>
	One last thing I noticed, after I ssh to it amongst other things I'm greeted with this: RX today: Error: Unable to read database "/var/lib/vnstat/veth1251466": No such file or directory. I never noticed that all the time before.
</p>
]]></description><guid isPermaLink="false">28731</guid><pubDate>Sun, 11 Jun 2023 12:38:53 +0000</pubDate></item><item><title>Trying to install OMV6 on Odroid HC1</title><link>https://testforum.armbian.com/topic/29364-trying-to-install-omv6-on-odroid-hc1/</link><description><![CDATA[<p>
	Is there a repository with older Armbian images available?  I'm looking to install OMV6 on my Odroid HC1 (XU4), when I get Armbian Bookworm installed OMV scripts says to use Buster or Bullseye, but I cannot find an Armbian Bullseye image anywhere.  I'm not super proficient with Linux (I know enough to get myself in trouble) so compiling my own image is not something I think I can do. 
</p>

<p>
	 
</p>

<p>
	Any help would be greatly appreciated.
</p>

<p>
	 
</p>

<p>
	Edit:  Nevermind...I'm an idiot...didn't  notice the GIANT button for Archived Images.  Apologies.
</p>

<p>
	 
</p>

<p>
	Thanks,
</p>

<p>
	Robert
</p>
]]></description><guid isPermaLink="false">29364</guid><pubDate>Sun, 23 Jul 2023 16:04:23 +0000</pubDate></item><item><title>XU4, Armbian 23.02.3 Bullseye, HDMI CEC not working</title><link>https://testforum.armbian.com/topic/28261-xu4-armbian-23023-bullseye-hdmi-cec-not-working/</link><description><![CDATA[<p>
	Greetings, 
</p>

<p>
	 
</p>

<p>
	As the subject says...
</p>

<p>
	CEC not detected in kernel, cec-client throws errors, nothing I tried worked.
</p>

<p>
	 
</p>

<p>
	root@odroidxu4:~# uname -a<br />
	Linux odroidxu4 5.4.239-odroidxu4 #1 SMP PREEMPT Thu Mar 16 15:52:54 UTC 2023 armv7l GNU/Linux<br />
	 
</p>

<p>
	root@odroidxu4:~# cec-client -l<br />
	libCEC version: 6.0.2, compiled on Linux-4.19.0-14-armmp-lpae ... , features: P8_USB, DRM, P8_detect, randr, Exynos, Linux, AOCEC<br />
	Found devices: 1
</p>

<p>
	device:              1<br />
	com port:            Linux<br />
	vendor id:           0000<br />
	product id:          0000<br />
	firmware version:    0<br />
	type:                Linux<br />
	 
</p>

<p>
	root@odroidxu4:~# cec-client<br />
	No device type given. Using 'recording device'<br />
	CEC Parser created - libCEC version 6.0.2<br />
	no serial port given. trying autodetect:<br />
	 path:     /dev/cec0<br />
	 com port: Linux
</p>

<p>
	opening a connection to the CEC adapter...<br />
	DEBUG:   [             468]     Broadcast (F): osd name set to 'Broadcast'<br />
	DEBUG:   [             468]     CLinuxCECAdapterCommunication::Open - m_fd=3 bStartListening=1<br />
	DEBUG:   [             468]     CLinuxCECAdapterCommunication::Open - ioctl CEC_ADAP_G_PHYS_ADDR - addr=ffff<br />
	WARNING: [             468]     CLinuxCECAdapterCommunication::Open - physical address is invalid<br />
	DEBUG:   [             468]     CLinuxCECAdapterCommunication::Open - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0<br />
	DEBUG:   [             468]     CLinuxCECAdapterCommunication::Open - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=1<br />
	NOTICE:  [             469]     connection opened<br />
	DEBUG:   [             469]     &lt;&lt; Broadcast (F) -&gt; TV (0): POLL<br />
	TRAFFIC: [             469]     &lt;&lt; f0<br />
	ERROR:   [             469]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	TRAFFIC: [             469]     &lt;&lt; f0<br />
	ERROR:   [             469]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	DEBUG:   [             469]     &gt;&gt; POLL not sent<br />
	DEBUG:   [             469]     TV (0): device status changed into 'not present'<br />
	DEBUG:   [             469]     registering new CEC client - v6.0.2<br />
	DEBUG:   [             469]     SetClientVersion - using client version '6.0.2'<br />
	NOTICE:  [             469]     setting HDMI port to 1 on device TV (0)<br />
	DEBUG:   [             469]     &lt;&lt; Broadcast (F) -&gt; TV (0): POLL<br />
	TRAFFIC: [             469]     &lt;&lt; f0<br />
	ERROR:   [             469]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	TRAFFIC: [             469]     &lt;&lt; f0<br />
	ERROR:   [             469]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	DEBUG:   [             469]     &gt;&gt; POLL not sent<br />
	DEBUG:   [             469]     SetConfiguration: double tap timeout = 200ms, repeat rate = 0ms, release delay = 500ms<br />
	DEBUG:   [             469]     detecting logical address for type 'recording device'<br />
	DEBUG:   [             469]     trying logical address 'Recorder 1'<br />
	DEBUG:   [             469]     &lt;&lt; Recorder 1 (1) -&gt; Recorder 1 (1): POLL<br />
	DEBUG:   [             469]     CLinuxCECAdapterCommunication::Process - CEC_DQEVENT - CEC_EVENT_STATE_CHANGE - log_addr_mask=0000 phys_addr=ffff<br />
	TRAFFIC: [             469]     &lt;&lt; 11<br />
	ERROR:   [             470]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	TRAFFIC: [             470]     &lt;&lt; 11<br />
	ERROR:   [             470]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	DEBUG:   [             470]     &gt;&gt; POLL not sent<br />
	DEBUG:   [             470]     using logical address 'Recorder 1'<br />
	DEBUG:   [             470]     Recorder 1 (1): device status changed into 'handled by libCEC'<br />
	DEBUG:   [             470]     Recorder 1 (1): power status changed from 'unknown' to 'on'<br />
	DEBUG:   [             470]     Recorder 1 (1): vendor = Pulse Eight (001582)<br />
	DEBUG:   [             470]     Recorder 1 (1): CEC version 1.4<br />
	DEBUG:   [             470]     AllocateLogicalAddresses - device '0', type 'recording device', LA '1'<br />
	DEBUG:   [             470]     CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=0<br />
	DEBUG:   [             470]     CLinuxCECAdapterCommunication::SetLogicalAddresses - ioctl CEC_ADAP_S_LOG_ADDRS - log_addr_mask=0000 num_log_addrs=1<br />
	DEBUG:   [             470]     Recorder 1 (1): osd name set to 'CECTester'<br />
	DEBUG:   [             470]     Recorder 1 (1): menu language set to 'eng'<br />
	NOTICE:  [             470]     setting HDMI port to 1 on device TV (0)<br />
	DEBUG:   [             470]     &lt;&lt; Recorder 1 (1) -&gt; TV (0): POLL<br />
	TRAFFIC: [             470]     &lt;&lt; 10<br />
	ERROR:   [             470]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	TRAFFIC: [             470]     &lt;&lt; 10<br />
	ERROR:   [             470]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	DEBUG:   [             470]     &gt;&gt; POLL not sent<br />
	DEBUG:   [             470]     Recorder 1 (1): physical address changed from ffff to 1000<br />
	DEBUG:   [             470]     &lt;&lt; Recorder 1 (1) -&gt; broadcast (F): physical address 1000<br />
	TRAFFIC: [             470]     &lt;&lt; 1f:84:10:00:01<br />
	ERROR:   [             470]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	TRAFFIC: [             470]     &lt;&lt; 1f:84:10:00:01<br />
	ERROR:   [             470]     CLinuxCECAdapterCommunication::Write - ioctl CEC_TRANSMIT failed - tx_status=00 errno=64<br />
	 
</p>

<p>
	 
</p>

<p>
	root@odroidxu4:~# lsmod<br />
	Module                  Size  Used by<br />
	rfkill                 24576  1<br />
	cpufreq_powersave      16384  0<br />
	cpufreq_userspace      16384  0<br />
	cpufreq_conservative    16384  0<br />
	zstd                   16384  8<br />
	joydev                 20480  0<br />
	input_leds             16384  0<br />
	exynos_gsc             32768  0<br />
	s5p_mfc               135168  0<br />
	s5p_jpeg               45056  0<br />
	v4l2_mem2mem           20480  2 s5p_jpeg,exynos_gsc<br />
	videobuf2_dma_contig    20480  3 s5p_jpeg,s5p_mfc,exynos_gsc<br />
	mali_kbase            364544  0<br />
	videobuf2_memops       16384  1 videobuf2_dma_contig<br />
	videobuf2_v4l2         24576  4 s5p_jpeg,s5p_mfc,exynos_gsc,v4l2_mem2mem<br />
	videobuf2_common       40960  5 s5p_jpeg,s5p_mfc,exynos_gsc,v4l2_mem2mem,videobuf2_v4l2<br />
	s5p_cec                16384  0<br />
	evdev                  24576  4<br />
	exynos_gpiomem         16384  0<br />
	zram                   28672  2<br />
	sunrpc                315392  1<br />
	ip_tables              24576  0<br />
	ipv6                  462848  42<br />
	autofs4                36864  2<br />
	usbhid                 49152  0<br />
	gpio_keys              20480  0<br />
	 
</p>

<p>
	 
</p>

<p>
	root@odroidxu4:~# zgrep CEC /proc/config.gz<br />
	CONFIG_TABLET_USB_ACECAD=m<br />
	CONFIG_CEC_CORE=y<br />
	CONFIG_CEC_NOTIFIER=y<br />
	CONFIG_MEDIA_CEC_SUPPORT=y<br />
	# CONFIG_MEDIA_CEC_RC is not set<br />
	# USB HDMI CEC adapters<br />
	# CONFIG_USB_PULSE8_CEC is not set<br />
	# CONFIG_USB_RAINSHADOW_CEC is not set<br />
	# CONFIG_VIDEO_VIVID_CEC is not set<br />
	CONFIG_CEC_PLATFORM_DRIVERS=y<br />
	# CONFIG_VIDEO_CROS_EC_CEC is not set<br />
	# CONFIG_CEC_GPIO is not set<br />
	CONFIG_VIDEO_SAMSUNG_S5P_CEC=m<br />
	# CONFIG_DRM_DP_CEC is not set<br />
	 
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	Please help!
</p>

<p>
	Thanks in advance.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28261</guid><pubDate>Wed, 10 May 2023 23:07:24 +0000</pubDate></item><item><title>odroid + adc</title><link>https://testforum.armbian.com/topic/28355-odroid-adc/</link><description><![CDATA[<p>
	Hi, I want to make adc pcm1804(simple adc clock + i2s) work with odroid, and manage it by alsa.<br />
	<br />
	As I understand, I should add a codec for pcm1804, driver to work with alsa, and device tree overlay.<br />
	<br />
	Please, tell me where can I get an example of this, or at least smth to use as a reference ?
</p>
]]></description><guid isPermaLink="false">28355</guid><pubDate>Sat, 20 May 2023 09:55:00 +0000</pubDate></item><item><title>Armbian Bookworm minimal CLI - Alsa not working anymore</title><link>https://testforum.armbian.com/topic/28353-armbian-bookworm-minimal-cli-alsa-not-working-anymore/</link><description><![CDATA[<p>
	HC2 here.
</p>

<p>
	Two last 6.1 kernels broke alsa <span>: hw not accessible anymore. Aplay -l lists audio outputs but none may be used. Looks like an omission on kernel flags..</span>
</p>

<p>
	<span>Reverted to Armbian Bullseye : exact same config, but working.</span>
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">28353</guid><pubDate>Sat, 20 May 2023 05:12:08 +0000</pubDate></item><item><title>Odroid HC1 - Armbian Bullseye Minimal - Unable to boot</title><link>https://testforum.armbian.com/topic/27724-odroid-hc1-armbian-bullseye-minimal-unable-to-boot/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	<br />
	I've several Odroid HC1 boards (forming a kubernetes cluster of 8 nodes) currently running Armbian Buster Minimal image.
</p>

<p>
	I would like to upgrade the cluster (node by node) to Armbian Bullseye Minimal but I faced the following issue when I tried to reinstall the 1st node:
</p>

<p>
	<br />
	- Used image: <a href="https://mirrors.dotsrc.org/armbian-dl/odroidxu4/archive/Armbian_23.02.1_Odroidxu4_bullseye_current_5.4.232_minimal.img.xz" rel="external nofollow">https://mirrors.dotsrc.org/armbian-dl/odroidxu4/archive/Armbian_23.02.1_Odroidxu4_bullseye_current_5.4.232_minimal.img.xz</a>
</p>

<p>
	- Image flashed on SD card using BalenaEtcher
</p>

<p>
	- SD card plugged into the board + power up --&gt; the OS is not booting (and not answering to ping)
</p>

<p>
	<br />
	Here are the different tries I did:
</p>

<p>
	- I've tried to flash the image several times even using different SD cards and boards --&gt; same issue, unable to boot
</p>

<p>
	- I've tried a rollback and flash the previous version Armbian Buster minimal --&gt; OK, able to boot (so I don't think the issue is at SD card or board level)
</p>

<p>
	- I've tried to flash the Armbian Bullseye non-minimal image (<a href="https://mirrors.dotsrc.org/armbian-dl/odroidxu4/archive/Armbian_23.02.1_Odroidxu4_bullseye_current_5.4.232.img.xz" rel="external nofollow">https://mirrors.dotsrc.org/armbian-dl/odroidxu4/archive/Armbian_23.02.1_Odroidxu4_bullseye_current_5.4.232.img.xz</a>) --&gt; with this image, I'm able to boot but after installing the OS on the SATA drive (using armbian-config : System / Install / Boot on SD, system on SATA), the OS is not booting anymore.
</p>

<p>
	<br />
	Unfortunately, I don't have an USB UART adapter to provide logs.
</p>

<p>
	<br />
	I'm suspecting an issue at image level as:
</p>

<p>
	After flashing the image on the SD card, I noticed that a file "qemu_fstype_20230226-211008_10215.core" is present at the root of the SD card ... maybe a sign showing that the image build failed or something like this !?<br />
	 <br />
	Thank you for your support. I would be happy to provide additional information if needed.<br />
	Adrien
</p>
]]></description><guid isPermaLink="false">27724</guid><pubDate>Mon, 03 Apr 2023 21:23:00 +0000</pubDate></item><item><title>Unable to start docker after update, due to apparmor</title><link>https://testforum.armbian.com/topic/26473-unable-to-start-docker-after-update-due-to-apparmor/</link><description><![CDATA[<p>
	Unable to start docker after update, due to apparmor
</p>

<p>
	 
</p>

<p>
	I used armbian-config's "edit boot-enviroment", added "extraargs=apparmor=0" and after a reboot I still get:
</p>

<p>
	<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">docker start portainer

Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `apparmor_parser apparmor_parser --version` failed with output:

error: exec: "apparmor_parser": executable file not found in $PATH

Error: failed to start containers: portainer</span></pre>

<p>
	 
</p>

<p>
	armbianmonitor:
</p>

<p>
	<a href="https://paste.armbian.com/ebuburoxeh" rel="external nofollow">https://paste.armbian.com/ebuburoxeh</a>
</p>
]]></description><guid isPermaLink="false">26473</guid><pubDate>Sun, 05 Feb 2023 22:50:51 +0000</pubDate></item><item><title>Odroid-XU4 how to handle updates?</title><link>https://testforum.armbian.com/topic/26287-odroid-xu4-how-to-handle-updates/</link><description><![CDATA[<p>
	Hi there,
</p>

<p>
	 
</p>

<p>
	I'd like to understand the best way to handle updates on Armbian…
</p>

<p>
	 
</p>

<p>
	My OS is:
</p>

<pre class="ipsCode">odroid ) uname -a
Linux odroidxu4 5.4.225-odroidxu4 #22.11.1 SMP PREEMPT Wed Nov 30 10:55:16 UTC 2022 armv7l GNU/Linux
odroid ) lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye
</pre>

<p>
	 
</p>

<p>
	And APT says:
</p>

<pre class="ipsCode">The following packages have been kept back:
  linux-dtb-current-odroidxu4 linux-headers-current-odroidxu4
  linux-image-current-odroidxu4 linux-u-boot-odroidxu4-current</pre>

<p>
	 
</p>

<p>
	The habits tell me to update however the experience taught that I could breaking something, some packages are on hold for a  goodreason...
</p>

<p>
	 
</p>

<p>
	<strong>What do you recommend?</strong>
</p>

<p>
	 
</p>

<p>
	Thanks in advance <span class="ipsEmoji">🙏</span>
</p>

<p>
	 
</p>

<p>
	F.
</p>
]]></description><guid isPermaLink="false">26287</guid><pubDate>Fri, 27 Jan 2023 14:58:11 +0000</pubDate></item><item><title>RX today:      Error: Interface "--oneline" not found in database.</title><link>https://testforum.armbian.com/topic/23732-rx-today-error-interface-oneline-not-found-in-database/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	A strange error appeared with the last kernel update on an Odroid HC2. From the home in the terminal displays this error under RX totay: 
</p>

<pre class="ipsCode">RX today:      Error: Interface "--oneline" not found in database.</pre>

<p>
	<br />
	The board is hosting an OMV instance under Armbian Bullseye Linux version 5.4.212-odroidxu4.
</p>

<p>
	Does anyone have any idea about the origin of this message which does not seem to disrupt the NAS operation.
</p>

<p>
	thanks
</p>

<p>
	konki
</p>
]]></description><guid isPermaLink="false">23732</guid><pubDate>Mon, 03 Oct 2022 21:29:15 +0000</pubDate></item><item><title>[SOLVED] Can flash the ISO directly into the eMMC?</title><link>https://testforum.armbian.com/topic/24925-solved-can-flash-the-iso-directly-into-the-emmc/</link><description><![CDATA[<p>
	Dear All,
</p>

<p>
	 
</p>

<p>
	I don't have much experience with the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr>, and I wonder if I can flash this image: Armbian_22.11.1_Odroidxu4_bullseye_current_5.4.225.img.xz directly into the <abbr title="embedded MultiMediaCard"><abbr title="embedded MultiMediaCard">eMMC</abbr></abbr> through Etcher, or do you recommend DD instead?
</p>

<p>
	 
</p>

<p>
	Thanks... <span class="ipsEmoji">🙏</span>
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">24925</guid><pubDate>Fri, 09 Dec 2022 05:37:23 +0000</pubDate></item><item><title>Odroid HC1: logrotate failure</title><link>https://testforum.armbian.com/topic/24838-odroid-hc1-logrotate-failure/</link><description><![CDATA[<p>
	$ systemctl status  <br />
	● henry<br />
	   State: degraded<br />
	    Jobs: 0 queued<br />
	  Failed: 1 units<br />
	   Since: Sat 2022-12-03 10:19:04 GMT; 24h ago<br />
	<br />
	$ systemctl list-units --failed<br />
	 UNIT              LOAD   ACTIVE SUB    DESCRIPTION<br />
	● logrotate.service loaded failed failed Rotate log files<br />
	<br />
	$ journalctl -u logrotate.service  <br />
	Journal file /var/log/journal/c87d7c4913d949949100f089ec48b092/system.journal is truncated, ignoring file.<br />
	-- Journal begins at Sun 2022-12-04 00:00:06 GMT, ends at Sun 2022-12-04 10:33:57 GMT. --<br />
	Dec 04 00:00:06 henry armbian-ramlog[2714]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2715]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2716]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2717]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2718]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2719]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2720]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2721]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry armbian-ramlog[2722]: /usr/lib/armbian/armbian-ramlog: line 153: /var/log/./journal-20220019-00:00:05/c8&gt;<br />
	Dec 04 00:00:06 henry systemd[1]: logrotate.service: Control process exited, code=exited, status=1/FAILURE<br />
	Dec 04 00:00:06 henry systemd[1]: logrotate.service: Failed with result 'exit-code'.<br />
	Dec 04 00:00:06 henry systemd[1]: Failed to start Rotate log files.<br />
	Dec 04 00:00:06 henry systemd[1]: logrotate.service: Consumed 5.879s CPU time.<br />
	 
</p>
]]></description><guid isPermaLink="false">24838</guid><pubDate>Sun, 04 Dec 2022 10:44:08 +0000</pubDate></item><item><title>Having trouble starting docker daemon</title><link>https://testforum.armbian.com/topic/24563-having-trouble-starting-docker-daemon/</link><description><![CDATA[<p>
	Hello.
</p>

<p>
	 
</p>

<p>
	I freshly installed bullseye from the other supported variant links for an odroid XU4.  When trying to get docker daemon running, it looked like the ip_tables module and br_netfilter modules weren't available in the kernel.
</p>

<p>
	 
</p>

<p>
	I think I have sorted out ip_tables (modprobe doesn't return any problems now), but docker's daemon is still showing a problem when running dockerd (with debug level info in the daemon.json file):<br />
	Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module bridge not found in directory /lib/modules/5.19.10-armmp-lpae
</p>

<p>
	 
</p>

<p>
	When executing
</p>

<p>
	systemctl status docker.service
</p>

<p>
	 
</p>

<p>
	... too see if the daemon is running I get:
</p>

<p>
	<br />
	● docker.service - Docker Application Container Engine<br />
	     Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)<br />
	     Active: failed (Result: exit-code) since Sun 2022-11-20 00:24:34 UTC; 4s ago<br />
	TriggeredBy: ● docker.socket<br />
	       Docs: <a href="https://docs.docker.com" rel="external nofollow">https://docs.docker.com</a><br />
	    Process: 8266 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)<br />
	   Main PID: 8266 (code=exited, status=1/FAILURE)<br />
	        CPU: 1.868s
</p>

<p>
	Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.<br />
	Nov 20 00:24:34 odroid-bullseye systemd[1]: Stopped Docker Application Container Engine.<br />
	Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Consumed 1.868s CPU time.<br />
	Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Start request repeated too quickly.<br />
	Nov 20 00:24:34 odroid-bullseye systemd[1]: docker.service: Failed with result 'exit-code'.<br />
	Nov 20 00:24:34 odroid-bullseye systemd[1]: Failed to start Docker Application Container Engine.
</p>
]]></description><guid isPermaLink="false">24563</guid><pubDate>Sun, 20 Nov 2022 00:30:03 +0000</pubDate></item><item><title>Odroid HC1 - OS / Armbian on hdd ?</title><link>https://testforum.armbian.com/topic/24253-odroid-hc1-os-armbian-on-hdd/</link><description><![CDATA[<p>
	Is it possible to transfer the entire Armbian system from SD card to HDD? ... it is known that the SD card has a lower endurance than such a HDD dist (write, read etc.)<br />
	I tried to transfer the system in such a way that I first upgraded the kernel to the newest one on the SD card and then moved the system files to a partition on the HDD:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">mount /dev/sda1 /mnt</span></pre>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">time tar --one-file-system -cpf - / | (cd /mnt &amp;&amp; tar -xpf -)</span></pre>

<p>
	then knowing the sda1 partition information and ID
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">lsblk -f</span></pre>

<p>
	then knowing the sda1 partition information and ID<br />
	I changed the UUID / HDD number in two locations
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">nano /boot/boot.ini</span></pre>

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

	<div class="ipsQuote_contents">
		<p>
			# default settings, will be overwritten from armbianEnv.txt<br />
			setenv macaddr "01:1b:06:77:7a:44"<br />
			setenv rootdev "UUID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxxxxxxxx"<br />
			setenv rootfstype "ext4"<br />
			setenv console "both"<br />
			setenv bootlogo "false"<br />
			setenv verbosity "1"
		</p>
	</div>
</blockquote>

<p>
	and
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">nano /etc/fstab</span></pre>

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

	<div class="ipsQuote_contents">
		<p>
			UUID=xxxxx-xxxxx-xxxxx-xxxxx-xxxxxxxxxxx / ext4 defaults,noatime,commit=600,errors=remount-ro 0 1<br />
			tmpfs /tmp tmpfs defaults,nosuid 0 0
		</p>
	</div>
</blockquote>

<p>
	after rebooting the system ... surprisingly it works OK, but actually the samba / ftp network (server vsftpd).<br />
	The update also seems to work OK, i.e.<br />
	apt update / apt upgrade ...<br />
	However, there are programs that cause the Armbian system to stop working completely, eg transmission when downloading files to the HDD? ... restarting the system helps, but is it the fault of the transmission program itself copied from the SD card or maybe the Armbian system cannot work properly on the HDD? ...<br />
	or maybe something else needs to be done to correctly transfer the system from the SD card to the HDD?
</p>

<p>
	if I restore the settings and boot from the SD card, Armbian / transmission / download works OK? I haven't checked the option of uninstalling transmission from the system to HDD yet and setting everything up again ... but will it help? 
</p>
]]></description><guid isPermaLink="false">24253</guid><pubDate>Thu, 03 Nov 2022 20:21:09 +0000</pubDate></item><item><title>Odroid HC2 boot failure bullseye_current_5.4.218 Oct 27, 2022</title><link>https://testforum.armbian.com/topic/24463-odroid-hc2-boot-failure-bullseye_current_54218-oct-27-2022/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I was unable to boot the latest flavor of armbian for odroid xu4 (Armbian_22.08.7_Odroidxu4_bullseye_current_5.4.218_minimal.img). My Odroid HC2 card shuts down quickly and no ssh connection is possible.
</p>

<p>
	The card stays on if the network cable is physically disconnected but stops immediately when reconnected.<br />
	The /etc/default/armbian-motd configuration file seems to be at fault?
</p>

<p>
	 
</p>

<p>
	it should contain something like this <span>:</span><br />
	PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -v lo | egrep "enp|eth|enx" | head -1)"
</p>

<p>
	maybe not <span>:</span>
</p>

<p>
	<span>PRIMARY_INTERFACE="$(ls -1 /sys/class/net/ | grep -v lo | egrep "en|eth ...</span>
</p>

<p>
	 
</p>

<p>
	I finally took an older image file, as I didn't have much more time to work on it (Armbian_22.05.4_Odroidxu4_bullseye_current_5.4.199.img)
</p>

<p>
	 
</p>

<p>
	konki
</p>
]]></description><guid isPermaLink="false">24463</guid><pubDate>Wed, 16 Nov 2022 22:59:23 +0000</pubDate></item><item><title>Odroid HC1: daily email from armbian-truncate-logs</title><link>https://testforum.armbian.com/topic/19629-odroid-hc1-daily-email-from-armbian-truncate-logs/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	I have recently upgraded OMV to version 6 and armbian to bullseye alongside it:
</p>

<p>
	<a href="https://forum.openmediavault.org/index.php?thread/41361-odroid-hc1-armbian-update-report/" rel="external nofollow">https://forum.openmediavault.org/index.php?thread/41361-odroid-hc1-armbian-update-report/</a>
</p>

<p>
	Since the upgrade, I am getting daily emails from armbian-truncate-logs with the following content:
</p>

<p>
	 
</p>

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

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode">[0;1;38;5;185mJournal file /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@8682aaf9b65f4db593fdb2f01a8b3fbc-0000000000000501-0005d513e7226c26.journal is truncated, ignoring file.[0m
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e63fd8387-4776da5b1e9dd6f3.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e31a4a51b-87ba53078992bfa5.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e31a4a140-b35ae9abf787edae.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e31a3258e-c7aba7539735db3b.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e31a32012-ca3c7661c922afba.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e31a30ac0-aedc088d247a140d.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e31a30681-a55dcd06694596c8.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2ea709fb-9ed166ca6e53c2ff.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2ea70533-d499487ff39624c0.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e341a38-b58dae80ccbb7c87.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e3417f6-7a9fec1bb8a1b3f7.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e3412b5-c7fb31d00135222b.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e341019-934fb8415cd40f91.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e2fb49c-7cf988dd2f664e3f.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e2fb270-66dc045e95d36496.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e2fae48-f3f01a9cb62d8b1c.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e2fabca-bb27481fdfb1f890.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d52e2e2f9349-700a878c5b79152d.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@0005d52e2e2f9242-fe8248d773b88d8a.journal~ (4.0K).
Deleted empty archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@8682aaf9b65f4db593fdb2f01a8b3fbc-0000000000000000-0000000000000000.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@8ba2ff0171204efb96c424e2acb591c7-000000000000b19a-0005d4fded950953.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@8ba2ff0171204efb96c424e2acb591c7-000000000000b38c-0005d4ffb75b9065.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@8ba2ff0171204efb96c424e2acb591c7-000000000000b572-0005d50161433b92.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@8ba2ff0171204efb96c424e2acb591c7-000000000000b75c-0005d502f8a68305.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@8ba2ff0171204efb96c424e2acb591c7-000000000000b94f-0005d504c2631f64.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-0000000000000001-0005d505f297fe4e.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-000000000000bd79-0005d50705c4e189.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-000000000000bf66-0005d508d6a665bc.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-000000000000c15b-0005d50ab24a1923.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-000000000000c348-0005d50c7885cebb.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-000000000000c539-0005d50e3782286a.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@c7688876310f4cfda2d405c789c7758c-000000000000c729-0005d510014ec802.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@baf75df6e52d418c8c04ceed18842c30-000000000000c756-0005d510197fd60b.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@4f0997a2acb742f380e3d276192ae4c8-0000000000000001-0005d5107aa56535.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d5107aaa3489-a8751f0289eed60a.journal~ (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@4f0997a2acb742f380e3d276192ae4c8-00000000000002c5-0005d5107aab2059.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@4f0997a2acb742f380e3d276192ae4c8-000000000000042d-0005d5107af9965d.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@87e66865628244fdbc41665a50089cb4-00000000000004d7-0005d5107f970502.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@4a4d1f4fa87145c48c93599e81c0dd8f-0000000000000001-0005d510908cae71.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d5109091a7db-6ee4991a90d609e3.journal~ (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@4a4d1f4fa87145c48c93599e81c0dd8f-00000000000002c9-0005d5109092920d.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@0005d51090929e1e-584ca9aa3dbfe3df.journal~ (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@4a4d1f4fa87145c48c93599e81c0dd8f-0000000000000433-0005d51090e347b5.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@ceee62826fcf4169aed887af96d8a622-0000000000000507-0005d510971971cb.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@7fdca15447094d63ba9b8b6af38287dc-0000000000000001-0005d510999e4b9e.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@7fdca15447094d63ba9b8b6af38287dc-00000000000002c8-0005d51099a387a0.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@7fdca15447094d63ba9b8b6af38287dc-000000000000045d-0005d5109fb54784.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@f2914651d4de4c5393ae4ebd7b57bab2-00000000000004f9-0005d510a75d59c2.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@7fdca15447094d63ba9b8b6af38287dc-000000000000063d-0005d5118e3dfb01.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@f2914651d4de4c5393ae4ebd7b57bab2-00000000000006c9-0005d5120ae34980.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@7fdca15447094d63ba9b8b6af38287dc-000000000000080c-0005d512c1ceb772.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@f2914651d4de4c5393ae4ebd7b57bab2-0000000000000875-0005d51319748bab.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@f9b13bd7e51c4934806113bf4000ec30-0000000000000001-0005d513b76dc4c7.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d513b7737844-b633ccf7eb74d687.journal~ (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@f9b13bd7e51c4934806113bf4000ec30-00000000000002cf-0005d513b7763a61.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@0005d513b7765fe2-32d72f86dd595ef1.journal~ (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@f9b13bd7e51c4934806113bf4000ec30-0000000000000478-0005d513b7f5f7dc.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@d9e92d67191948fbb44fe1afc4fa0d9b-00000000000004ae-0005d513b9fbc39f.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-0000000000000001-0005d513be8d3d75.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-00000000000002d1-0005d513be9222f1.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@0005d513be92247e-bc989cbce4d1503e.journal~ (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-0000000000000466-0005d513dea5d241.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/user-1000@8682aaf9b65f4db593fdb2f01a8b3fbc-0000000000000501-0005d513e7226c26.journal (564.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-000000000000063f-0005d514cbf6f439.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-0000000000000853-0005d5161fbae3eb.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-0000000000000a47-0005d517f4303b95.journal (640.0K).
Deleted archived journal /var/log/journal/1ded17e370994bc2bfab08257042ce4c/system@80ee9256fd7547bd9d9e324129f1ce5c-00000000000012ec-0005d51f82ff598e.journal (640.0K).
Vacuuming done, freed 30.0M of archived journals from /var/log/journal/1ded17e370994bc2bfab08257042ce4c.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
Vacuuming done, freed 0B of archived journals from /run/log/journal.</pre>

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

<p>
	 
</p>

<p>
	I am not sure if this is expected or not, but I was not getting these with OMV 5.
</p>
]]></description><guid isPermaLink="false">19629</guid><pubDate>Mon, 10 Jan 2022 15:26:55 +0000</pubDate></item><item><title>Odroid xu4 usb sata SSD drive random disconnect</title><link>https://testforum.armbian.com/topic/20582-odroid-xu4-usb-sata-ssd-drive-random-disconnect/</link><description><![CDATA[<p>
	Odroid XU4 / Armbian 22.02 Bullseye<br />
	USB3 sata drive gets randomly disconnected: (every 8 hours or so when constantly reading / writing)
</p>

<p>
	 
</p>

<p>
	[44676.709229] sd 0:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN<br />
	[44676.709252] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x28 28 00 49 a5 1b d8 00 00 08 00<br />
	[44681.728962] xhci-hcd xhci-hcd.8.auto: xHCI host not responding to stop endpoint command.<br />
	[44681.749158] xhci-hcd xhci-hcd.8.auto: xHCI host controller not responding, assume dead<br />
	[44681.749210] usb 4-1.2: cmd cmplt err -108<br />
	[44681.749509] xhci-hcd xhci-hcd.8.auto: HC died; cleaning up<br />
	[44681.749696] usb 3-1: USB disconnect, device number 2<br />
	[44681.751626] sd 0:0:0:0: [sda] tag#20 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD<br />
	[44681.751666] sd 0:0:0:0: [sda] tag#20 CDB: opcode=0x2a 2a 00 3e a6 aa f0 00 00 08 00
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	root@btcfn:~# uname -a<br />
	Linux btcfn 5.4.181-odroidxu4 #22.02.1 SMP PREEMPT Sun Feb 27 08:55:42 UTC 2022 armv7l GNU/Linux
</p>

<p>
	 
</p>

<p>
	USB sata bridge JMicron (the official Hardkernel thingie)
</p>
]]></description><guid isPermaLink="false">20582</guid><pubDate>Wed, 04 May 2022 19:29:47 +0000</pubDate></item><item><title>linux-image-edge-odroidxu4 kernel not rebooting?</title><link>https://testforum.armbian.com/topic/23457-linux-image-edge-odroidxu4-kernel-not-rebooting/</link><description><![CDATA[<p>
	Hey guys!
</p>

<p>
	 
</p>

<p>
	I am running Armbian 22.05.3 on my Odroid XU4. Very happy with it. I just installed linux-image-edge-odroidxu4 (kernel 5.17) and rebooted. Everything hunky dory. However, once I'm on 5.17 I am unable to reboot by using the 'reboot' or 'shutdown -r now' commands, which worked on the default 5.4 kernel. Is this a known issue? Any hints on how to debug or any known workarounds?
</p>

<p>
	 
</p>

<p>
	Thank you
</p>
]]></description><guid isPermaLink="false">23457</guid><pubDate>Fri, 09 Sep 2022 19:40:18 +0000</pubDate></item><item><title>Odroid Xu4 fan, kernel 5.4.215-odroidxu4 #22.08.4 &#xBF;Fan on?, &#xBF;how to?</title><link>https://testforum.armbian.com/topic/24054-odroid-xu4-fan-kernel-54215-odroidxu4-22084-%C2%BFfan-on-%C2%BFhow-to/</link><description><![CDATA[<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">Estoy perdido, despues de buscar y buscar soluciones, soy nuevo en este foro. </font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">He probado xu4fan, fancontrol, incluso un script que está en este foro, y no puedo iniciar el ventilador con armbian, ni siquiera puedo hacer que el ventilador se mueva. </font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">he intentado esto </font></font>
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">PUNTO_VIAJE_0=25000 </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">PUNTO_VIAJE_1=30000 </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">PUNTO_VIAJE_2=40000</font></font>
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_0 &gt; /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp$ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_0 &gt; /sys/devices/virtual/thermal/thermal_zone1/trip_point_0_temp$ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_0 &gt; /sys/devices/virtual/thermal/thermal_zone2/trip_point_0_temp $ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_0 &gt; /sys/devices/virtual/thermal/thermal_zone3/trip_point_0_temp$</font></font>
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_1 &gt; /sys/devices/virtual/thermal/thermal_zone0/trip_point_1_temp$ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_1 &gt; /sys/devices/virtual/thermal/thermal_zone1/trip_point_1_temp$ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_1 &gt; /sys/devices/virtual/thermal/thermal_zone2/trip_point_1_temp $ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_1 &gt; /sys/devices/virtual/thermal/thermal_zone3/trip_point_1_temp$</font></font>
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_2 &gt; /sys/devices/virtual/thermal/thermal_zone0/trip_point_2_temp$ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_2 &gt; /sys/devices/virtual/thermal/thermal_zone1/trip_point_2_temp$ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_2 &gt; /sys/devices/virtual/thermal/thermal_zone2/trip_point_2_temp $ </font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo $TRIP_POINT_2 &gt; /sys/devices/virtual/thermal/thermal_zone3/trip_point_2_temp$</font></font>
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;"># Velocidad objetivo del ventilador (PWM): 0, 60 180, 240, 255</font></font><br />
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">echo "0 60 180 240 255" &gt; /sys/devices/platform/pwm-fan/hwmon/hwmon0/fan_speed</font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">y la respuesta </font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;"> no se puede crear /sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp$: Permiso denegado</font></font>
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">he intentado esto </font></font>
</p>

<p>
	 
</p>

<p>
	<a href="https://github.com/lbseale/odroid-fan%C2%A0" rel="external nofollow"><font style="vertical-align:inherit;"><font style="vertical-align:inherit;">https://github.com/lbseale/odroid-fan</font></font></a> 
</p>

<p>
	 
</p>

<p>
	<font style="vertical-align:inherit;"><font style="vertical-align:inherit;">en teoria se arranca el servicio, pero, se acumula calor, como puedo hacer para que funcione?</font></font><br />
	 
</p>
]]></description><guid isPermaLink="false">24054</guid><pubDate>Wed, 19 Oct 2022 18:45:55 +0000</pubDate></item><item><title>Odroid Wifi Dongle 5 not working with recent Armbian releases</title><link>https://testforum.armbian.com/topic/22869-odroid-wifi-dongle-5-not-working-with-recent-armbian-releases/</link><description><![CDATA[<p>
	Hi all,<br />
	<br />
	The grey wifi Dongle 5 I bought direct from Odroid seems to have stopped working with recent Debian releases.<br />
	After much troubleshooting, I downgraded to Buster and it works fine - until I run apt update/upgrade.
</p>

<p>
	 
</p>

<p>
	lsusb info is:<br />
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">Bus 003 Device 010: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter</span></pre>

<p>
	<br />
	What's also interesting is that post upgrade, the device's name also changes to @_____, and its mac address changes to 00:00:00:00:00:00. The blue wifi light on the dongle won't even flash after upgrade.<br />
	After apt upgrade:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">root@odroidxu4:~# iwconfig
enx001e06361f54  no wireless extensions.

docker0   no wireless extensions.

veth099d042  no wireless extensions.

@�����    unassociated  ESSID:""  Nickname:"</span><span class="tag">&lt;WIFI</span><span class="pln">@</span><span class="atn">REALTEK</span><span class="tag">&gt;</span><span class="pln">"
          Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated
          Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

veth51d95a5  no wireless extensions.

root@odroidxu4:~# ifconfig
@�����: flags=4163</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">BROADCAST</span><span class="pln">,</span><span class="atn">RUNNING</span><span class="pln">,</span><span class="atn">MULTICAST</span><span class="tag">&gt;</span><span class="pln">  mtu 2312
        ether 00:00:00:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
</span></pre>

<p>
	Latest that I can get wifi to work (before running apt update) is Armbian_20.11.10_Odroidxu4_buster_current_5.4.91_minimal<br />
	When it's working, pre upgrade, the info I get is:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">root@odroidxu4:~# iwconfig
veth59fc9ec  no wireless extensions.

docker0   no wireless extensions.

vethfe1f602  no wireless extensions.

wlx40a5efd5d9c5  IEEE 802.11AC  ESSID:"WiFi-T7JR-5G"  Nickname:"</span><span class="tag">&lt;WIFI</span><span class="pln">@</span><span class="atn">REALTEK</span><span class="tag">&gt;</span><span class="pln">"
          Mode:Managed  Frequency:5.18 GHz  Access Point: CC:32:E5:0E:8B:AE
          Bit Rate:867 Mb/s   Sensitivity:0/0
          Retry:off   RTS thr:off   Fragment thr:off
          Encryption key:****-****-****-****-****-****-****-****   Security mode:open
          Power Management:off
          Link Quality=98/100  Signal level=64/100  Noise level=0/100
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

enx001e06361f54  no wireless extensions.

root@odroidxu4:~# ifconfig
docker0: flags=4163</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">BROADCAST</span><span class="pln">,</span><span class="atn">RUNNING</span><span class="pln">,</span><span class="atn">MULTICAST</span><span class="tag">&gt;</span><span class="pln">  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 172.17.255.255
        inet6 fe80::42:76ff:fea1:e649  prefixlen 64  scopeid 0x20</span><span class="tag">&lt;link&gt;</span><span class="pln">
        ether 02:42:76:a1:e6:49  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 76  bytes 13510 (13.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enx001e06361f54: flags=4099</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">BROADCAST</span><span class="pln">,</span><span class="atn">MULTICAST</span><span class="tag">&gt;</span><span class="pln">  mtu 1500
        ether 00:1e:06:36:1f:54  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">LOOPBACK</span><span class="pln">,</span><span class="atn">RUNNING</span><span class="tag">&gt;</span><span class="pln">  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10</span><span class="tag">&lt;host&gt;</span><span class="pln">
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

veth59fc9ec: flags=4163</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">BROADCAST</span><span class="pln">,</span><span class="atn">RUNNING</span><span class="pln">,</span><span class="atn">MULTICAST</span><span class="tag">&gt;</span><span class="pln">  mtu 1500
        inet6 fe80::701c:e5ff:fe55:5335  prefixlen 64  scopeid 0x20</span><span class="tag">&lt;link&gt;</span><span class="pln">
        ether 72:1c:e5:55:53:35  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 91  bytes 17422 (17.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

vethfe1f602: flags=4163</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">BROADCAST</span><span class="pln">,</span><span class="atn">RUNNING</span><span class="pln">,</span><span class="atn">MULTICAST</span><span class="tag">&gt;</span><span class="pln">  mtu 1500
        inet6 fe80::dcf7:80ff:fe17:3e4c  prefixlen 64  scopeid 0x20</span><span class="tag">&lt;link&gt;</span><span class="pln">
        ether de:f7:80:17:3e:4c  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 100  bytes 18299 (17.8 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlx40a5efd5d9c5: flags=4163</span><span class="tag">&lt;UP</span><span class="pln">,</span><span class="atn">BROADCAST</span><span class="pln">,</span><span class="atn">RUNNING</span><span class="pln">,</span><span class="atn">MULTICAST</span><span class="tag">&gt;</span><span class="pln">  mtu 2312
        inet 192.168.1.154  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::6a24:4aa4:7bdc:c247  prefixlen 64  scopeid 0x20</span><span class="tag">&lt;link&gt;</span><span class="pln">
        ether 40:a5:ef:d5:d9:c5  txqueuelen 1000  (Ethernet)
        RX packets 157  bytes 23355 (22.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 152  bytes 28952 (28.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
</span></pre>

<p>
	Please let me know if there's any other information I can provide. Many thanks, appreciate your help.
</p>
]]></description><guid isPermaLink="false">22869</guid><pubDate>Thu, 11 Aug 2022 06:19:31 +0000</pubDate></item><item><title>USB Bluetooth Module conflict with Dbus service</title><link>https://testforum.armbian.com/topic/23127-usb-bluetooth-module-conflict-with-dbus-service/</link><description><![CDATA[<p>
	I have a new odroid XU4 that I plan to use for Home Assistant in Docker and run other services in containers.  I have loaded a fresh copy of Armbian cli (fully updated) with bluetooth from armbian-config. I installed linux drivers for my usb module (rtl8761a) from the manufacturer and it comes up in "bluetoothctl" as registered and pairable. However "bluetoothd show" gives me  a "D-Bus setup failed: Name already in use." I will need dbus to pass device information between my docker containers when I install docker and home assistant so this error is concerning. Any ideas on how I might resolve this error?
</p>

<p>
	 
</p>

<p>
	Thank you 
</p>

<p>
	 
</p>

<p>
	armianmonitor url: <a href="http://ix.io/48FG" rel="external nofollow">http://ix.io/48FG</a>
</p>
]]></description><guid isPermaLink="false">23127</guid><pubDate>Fri, 26 Aug 2022 09:52:36 +0000</pubDate></item><item><title>Upgrade from jammy to bullseye?</title><link>https://testforum.armbian.com/topic/22661-upgrade-from-jammy-to-bullseye/</link><description><![CDATA[<p>
	I’m running jammy and (I think) I’d like to upgrade to bullseye. But I can’t find a procedure for doing so. I’m guessing I can’t just dist-upgrade since jammy is Ubuntu and bullseye is Debian? I’ve googled for a procedure and searched this forum as well but I’m not finding a procedure. While searching this forum, I saw lots of topics where people had problems after upgrading to bullseye. Should I even do the upgrade?
</p>

<p>
	 
</p>

<p>
	 I don’t have much invested in the jammy install so far. Aside from running through armbian-config and getting all the settings the way I want them, the only things I’ve done are 1) installed Docker and 2) installed docker-compose. The latter was a major pain, though. I kept getting the “file not found” error. It took me hours to get it working and I’m still not exactly sure how I did it. Anyway, if my best course of action is to simply start over with the bullseye image, I can do that. 
</p>
]]></description><guid isPermaLink="false">22661</guid><pubDate>Fri, 29 Jul 2022 14:01:57 +0000</pubDate></item><item><title>Odroid XU4 kernel release missing some options in config</title><link>https://testforum.armbian.com/topic/22221-odroid-xu4-kernel-release-missing-some-options-in-config/</link><description><![CDATA[<p>
	Hello everyone,
</p>

<p>
	 
</p>

<p>
	I'm wondering if is possible to include in future releases of the Armbian Kernels these options:
</p>

<p>
	 
</p>

<p>
	CONFIG_NETLABEL
</p>

<p>
	CONFIG_MPTCP
</p>

<p>
	CONFIG_NET_VRF<br />
	CONFIG_OF_UNITTEST
</p>

<p>
	CONFIG_OF_DYNAMIC
</p>

<p>
	CONFIG_OF_OVERLAY
</p>

<p>
	CONFIG_INET_MPTCP_DIAG
</p>

<p>
	CONFIG_MPLS_ROUTING
</p>

<p>
	CONFIG_MPLS_IPTUNNEL
</p>

<p>
	CONFIG_NLMON
</p>

<p>
	CONFIG_NET_VRF
</p>

<p>
	CONFIG_GTP
</p>

<p>
	CONFIG_GENEVE
</p>

<p>
	CONFIG_IPVTAP
</p>

<p>
	CONFIG_IFB
</p>

<p>
	 
</p>

<p>
	I'm playing around with my Odroid XU4 and I notice that I'm missing such options and drivers compiled in the Kernel. As an example Debian has these options enabled by default.
</p>

<p>
	In my case I created a script that is getting the Armbian Odroid XU4 kernel sources, applying these settings in config and rebuild the kernel.
</p>

<p>
	 
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">22221</guid><pubDate>Fri, 01 Jul 2022 12:19:20 +0000</pubDate></item><item><title>Jammy/Focal nand-sata-install hangs after reboot</title><link>https://testforum.armbian.com/topic/21692-jammyfocal-nand-sata-install-hangs-after-reboot/</link><description><![CDATA[<p>
	I've tried <abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install on Armbian_22.05.3_Odroidxu4_jammy_current_5.4.199.img and Armbian_22.05.3_Odroidxu4_focal_current_5.4.199.img. Right at the end of running <abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install there's an error. If I try to install anything after <abbr title="A type of flash memory"><abbr title="A type of flash memory">nand</abbr></abbr>-sata-install it will hang or the SSD will go into read only mode. To be safe I tested various SD cards and USB to SATA controllers.
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sed: can't read /boot/boot.cmd: No such file or directory
sed: can't read /boot/boot.cmd: No such file or directory
Error while creating U-Boot loader image with mkimage
umount: /mnt/nand-sata-install.wwpusQ/bootfs: not mounted.</span></pre>

<p>
	 
</p>
]]></description><guid isPermaLink="false">21692</guid><pubDate>Mon, 27 Jun 2022 18:36:58 +0000</pubDate></item><item><title>HC1 kernel update gone wrong?</title><link>https://testforum.armbian.com/topic/19707-hc1-kernel-update-gone-wrong/</link><description><![CDATA[<p>
	I tried updating my kernel to self-built 5.4.173 as usual. I got some errors during installation due to low space on /boot, but after removing leftovers of 5.4.168 the installation worked as expected. Something went wrong though, as my HC1 no longer boots. This is shown via UART:
</p>

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

	<div class="ipsQuote_contents">
		<p>
			U-Boot 2017.05-armbian (Oct 13 2020 - 18:57:02 +0200) for ODROID-XU4
		</p>

		<p>
			CPU:   Exynos5422 @ 800 MHz<br />
			Model: Odroid XU4 based on EXYNOS5422<br />
			Board: Odroid XU4 based on EXYNOS5422<br />
			Type:  xu4<br />
			DRAM:  2 GiB<br />
			MMC:   EXYNOS DWMMC: 0, EXYNOS DWMMC: 1<br />
			MMC Device 0 ( SD ): 14.8 GiB<br />
			Card did not respond to voltage select!<br />
			mmc_init: -95, time 12<br />
			*** Warning - bad CRC, using default environment
		</p>

		<p>
			In:    serial<br />
			Out:   serial<br />
			Err:   serial<br />
			Net:   No ethernet found.<br />
			Press quickly 'Enter' twice to stop autoboot:  0<br />
			12489 bytes read in 16 ms (761.7 KiB/s)<br />
			## Executing script at 43e00000<br />
			** File not found /boot/armbianEnv.txt **<br />
			** Unrecognized filesystem type **<br />
			64 bytes read in 13 ms (3.9 KiB/s)<br />
			** File not found /boot/zImage **<br />
			** Unrecognized filesystem type **<br />
			7340760 bytes read in 734 ms (9.5 MiB/s)<br />
			** File not found /boot/uInitrd **<br />
			** Unrecognized filesystem type **<br />
			11220072 bytes read in 8034 ms (1.3 MiB/s)<br />
			** File not found /boot/.next **<br />
			** Unrecognized filesystem type **<br />
			0 bytes read in 8 ms (0 Bytes/s)<br />
			Found mainline kernel configuration<br />
			** File not found /boot/<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>/exynos5422-odroidhc1.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> **<br />
			** Unrecognized filesystem type **<br />
			** File not found <abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr>/exynos5422-odroidhc1.<abbr title="Device tree blob"><abbr title="Device tree blob">dtb</abbr></abbr> **<br />
			libfdt fdt_check_header(): FDT_ERR_BADMAGIC<br />
			No FDT memory address configured. Please configure<br />
			the FDT address via "fdt addr &lt;address&gt;" command.<br />
			Aborting!<br />
			Kernel image @ 0x40008000 [ 0x000000 - 0x7002d8 ]<br />
			## Loading init Ramdisk from Legacy Image at 42000000 ...<br />
			   Image Name:   uInitrd<br />
			   Image Type:   ARM Linux RAMDisk Image (gzip compressed)<br />
			   Data Size:    11220008 Bytes = 10.7 MiB<br />
			   Load Address: 00000000<br />
			   Entry Point:  00000000<br />
			   Verifying Checksum ... OK<br />
			ERROR: Did not find a cmdline Flattened Device Tree<br />
			Could not find a valid device tree<br />
			** File not found /boot/boot.ini **<br />
			## Executing script at 43e00000<br />
			** File not found /boot.scr **<br />
			## Executing script at 43e00000<br />
			Failed to mount ext2 filesystem...<br />
			** Unrecognized filesystem type **<br />
			## Executing script at 43e00000<br />
			Failed to mount ext2 filesystem...<br />
			** Unrecognized filesystem type **<br />
			## Executing script at 43e00000<br />
			Failed to mount ext2 filesystem...<br />
			** Unrecognized filesystem type **<br />
			## Executing script at 43e00000<br />
			mmc_init: -110, time 121<br />
			switch to partitions #0, OK<br />
			mmc0 is current device<br />
			Scanning mmc 0:1...<br />
			starting USB...<br />
			USB0:   USB EHCI 1.00<br />
			USB1:   Register 2000140 NbrPorts 2<br />
			Starting the controller<br />
			USB XHCI 1.00<br />
			USB2:   Register 2000140 NbrPorts 2<br />
			Starting the controller<br />
			USB XHCI 1.00<br />
			scanning bus 0 for devices... 1 USB Device(s) found<br />
			scanning bus 1 for devices... cannot reset port 1!?<br />
			1 USB Device(s) found<br />
			scanning bus 2 for devices... 2 USB Device(s) found<br />
			       scanning usb for storage devices... 0 Storage Device(s) found<br />
			       scanning usb for ethernet devices... 1 Ethernet Device(s) found
		</p>

		<p>
			USB device 0: unknown device<br />
			Waiting for Ethernet connection... done.<br />
			BOOTP broadcast 1
		</p>
	</div>
</blockquote>

<p>
	All the files seem to be on the SD card:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">$ ls -l
insgesamt 32447
-rw-r--r--. 1 root root       64  8. Jan 16:27 armbianEnv.txt
-rw-r--r--. 1 root root        0  6. Sep 2019  armbianEnv.txt.out
-rw-r--r--. 1 root root     1536 29. Mai 2018  armbian_first_run.txt.template
-rw-r--r--. 1 root root    38518 29. Mai 2018  boot.bmp
-rw-r--r--. 1 root root     4882 29. Mai 2018  boot-desktop.png
-rw-r--r--. 1 root root    12489 16. Jan 2021  boot.ini
-rw-r--r--. 1 root root        0 25. Jun 2019  boot.ini.out
-rw-r--r--. 1 root root   169645 22. Jan 10:57 config-5.4.173-odroidxu4
drwxr-xr-x. 3 root root     3072 22. Jan 15:34 dtb-5.4.173-odroidxu4
-rw-r--r--. 1 root root 11220008 22. Jan 15:23 initrd.img-5.4.173-odroidxu4
drwx------. 2 root root    12288 29. Mai 2018  lost+found
-rw-r--r--. 1 root root  3194528 22. Jan 10:57 System.map-5.4.173-odroidxu4
lrwxrwxrwx. 1 root root       25 22. Jan 15:23 uInitrd -&gt; uInitrd-5.4.173-odroidxu4
-rw-r--r--. 1 root root 11220072 22. Jan 15:23 uInitrd-5.4.173-odroidxu4
-rwxr-xr-x. 1 root root  7340760 22. Jan 10:57 vmlinuz-5.4.173-odroidxu4
lrwxrwxrwx. 1 root root       25 22. Jan 15:34 zImage -&gt; vmlinuz-5.4.173-odroidxu4</span></pre>

<p>
	Any ideas where to look?
</p>
]]></description><guid isPermaLink="false">19707</guid><pubDate>Sat, 22 Jan 2022 15:00:22 +0000</pubDate></item><item><title>Odroid HC1 ethernet hangs</title><link>https://testforum.armbian.com/topic/21443-odroid-hc1-ethernet-hangs/</link><description><![CDATA[<p>
	Hello all!
</p>

<p>
	 
</p>

<p>
	I used the following armbian image to write to an SD (I'm using an old odroid HC1 btw):
</p>

<p>
	<a href="https://armbian.site-meganet.com/dl/odroidxu4/archive/" rel="external nofollow">https://armbian.site-meganet.com/dl/odroidxu4/archive/</a>
</p>

<p>
	 
</p>

<p>
	I used the bullseye_current image that was there. On the main download page it says that the file for Odroid XU4 is compatible with HC1, HC2 and MC1.
</p>

<p>
	 
</p>

<p>
	<a href="https://www.armbian.com/odroid-xu4/" rel="external nofollow">https://www.armbian.com/odroid-xu4/</a>
</p>

<p>
	 
</p>

<p>
	My odroid HC1 boots ok but any attempt to use the built-in ethernet port results in an instant lock-up. Only way I can "get into" the device is with a USB ethernet adapter although even just issuing a command, eg ifconfig enx001e06366b84 192.168.1.99 locks everything up - even the USB ethernet adapter stopped working. I did check with ifconfig to find the relevent ethernet adapters'; names and two are listed.  
</p>

<p>
	 
</p>

<p>
	(The enx001e06366b84 name there is what the built-in ethernet adapters' name is btw).
</p>

<p>
	 
</p>

<p>
	Does anyone know why trying to use the inbuilt ethernet should lock the entire device up?
</p>

<p>
	 
</p>

<p>
	ljones
</p>
]]></description><guid isPermaLink="false">21443</guid><pubDate>Sun, 12 Jun 2022 15:34:16 +0000</pubDate></item><item><title>unable to locate package sysbench</title><link>https://testforum.armbian.com/topic/20995-unable-to-locate-package-sysbench/</link><description><![CDATA[<p>
	Hi!
</p>

<p>
	 
</p>

<p>
	my Odroid HC2 is running for more than three years now (24/7), hosting a nextcloud instance. Other than two preemptive SD-card swaps no maintenance necessary, armbian performs really great <span><span class="ipsEmoji">🙂</span> Since I was thinking about upgrading to a better machine (Nano Pi M4, if they ever sell them again...) I wanted to install sysbench to compare some CPU specs. But </span>
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">sudo apt-get install sysbench</span></pre>

<p>
	gives:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">unable to locate package sysbench</span></pre>

<p>
	I'm running a recently upgraded armbian, v22.02.1 with Kernel 5.4.181. Any ideas? I'm pretty sure I had sysbench on an earlier version of armbian.
</p>

<p>
	 
</p>

<p>
	EDIT: fixed typos
</p>
]]></description><guid isPermaLink="false">20995</guid><pubDate>Wed, 18 May 2022 18:55:29 +0000</pubDate></item><item><title>ODROID-XU4 half the cores idle</title><link>https://testforum.armbian.com/topic/20996-odroid-xu4-half-the-cores-idle/</link><description><![CDATA[<p>
	Hi, gotta ask a question<br>
	<br>
	Recently I just reinstalled all my XU4 based server from scratch.<br>
	Brand new armbian Bullseye with OMV on top installed via armbian-config<br>
	Then I noticed as seem bellow that half the cores (the low power ones) are idling, even when the system is fully under load on the high power cores
</p>

<p>
	 
</p>

<p>
	<img class="ipsImage ipsImage_thumbnailed" data-fileid="8993" width="668" alt="image.png.3c7f564c49a19e836adae5f10d408b3c.png" src="https://testforum.armbian.com/uploads/monthly_2022_05/image.png.3c7f564c49a19e836adae5f10d408b3c.png" loading="lazy" height="200.4">
</p>

<p>
	<br>
	The cores are enabled in the /sys/devices/system/cpu/cpuX/online files<br>
	<br>
	So the question is "what's wrong"?<br>
	I don't have prints but I remember all the cores working before<br>
	<br>
	Thanks in advance<br>
	<br>
	Will
</p>
]]></description><guid isPermaLink="false">20996</guid><pubDate>Wed, 18 May 2022 23:09:02 +0000</pubDate></item><item><title>Armbian buster libc-dev-bin upgrade held back</title><link>https://testforum.armbian.com/topic/20153-armbian-buster-libc-dev-bin-upgrade-held-back/</link><description><![CDATA[<p>
	Hi, I have been running Armbian Buster on an Odroid HC1 for a while but today one upgrade is held back:
</p>

<p>
	 
</p>

<pre class="ipsCode">The following packages have been kept back:
 libc-dev-bin
0 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
</pre>

<p>
	<br />
	This is why:
</p>

<p>
	 
</p>

<pre class="ipsCode">$ sudo apt install libc-dev-bin
Reading package lists... Done
Building dependency tree        
Reading state information... Done
The following package was automatically installed and is no longer required:
 linux-libc-dev
Use 'sudo apt autoremove' to remove it.
Recommended packages:
 manpages manpages-dev
The following packages will be REMOVED:
 armbian-config build-essential g++ g++-8 libc6-dev libstdc++-8-dev
The following packages will be upgraded:
 libc-dev-bin
1 upgraded, 0 newly installed, 6 to remove and 31 not upgraded.
Need to get 267 kB of archives.
After this operation, 44.0 MB disk space will be freed.
Do you want to continue? [Y/n]
</pre>

<p>
	<br />
	Obviously I have picked no, because I don't want to uninstall armbian-config<br />
	<br />
	It seems I have this wierd "oldstable" mess when I type the following:<br />
	<br />
	 
</p>

<pre class="ipsCode">$ sudo apt list --upgradable --all-versions  
Listing... Done
libc-dev-bin/oldstable 2.28-10+deb10u1 armhf [upgradable from: 2.28-10]
libc-dev-bin/now 2.28-10 armhf [installed,upgradable to: 2.28-10+deb10u1]

libc6-dev/oldstable 2.28-10+deb10u1 armhf [upgradable from: 2.28-10]
libc6-dev/now 2.28-10 armhf [installed,upgradable to: 2.28-10+deb10u1]

libssl-dev/oldstable 1.1.1n-0+deb10u1 armhf [upgradable from: 1.1.1d-0+deb10u7]
libssl-dev/oldstable 1.1.1d-0+deb10u8 armhf
libssl-dev/now 1.1.1d-0+deb10u7 armhf [installed,upgradable to: 1.1.1n-0+deb10u1]
</pre>

<p>
	 
</p>

<p>
	How did this happen? Is it fixable or time for a reinstall?<br />
	<br />
	By the way this has to run Debian 10, I know Debian 11 is out but the software this device runs requires Debian 10 still at this stage.
</p>
]]></description><guid isPermaLink="false">20153</guid><pubDate>Sun, 27 Mar 2022 05:36:50 +0000</pubDate></item><item><title>HDMI not working if HDMI is not connected at boot time on Odroid xu4</title><link>https://testforum.armbian.com/topic/19820-hdmi-not-working-if-hdmi-is-not-connected-at-boot-time-on-odroid-xu4/</link><description><![CDATA[<p>
	If I boot my Odroid XU4 without the HDMI cable connected, my HDMI display does not work.  If I boot with the HDMI cable and monitor connected, the HDMI display works fine even if it is disconnected and reconnected.
</p>

<p>
	 
</p>

<p>
	I am running debian buster.
</p>

<p>
	    deb <a href="http://deb.debian.org/debian" rel="external nofollow">http://deb.debian.org/debian</a> buster main contrib non-free   <br />
	 
</p>

<p>
	I have compared the dmesg output from when HDMI works and does not work and do not see a difference.  In case it helps, here are all of the dmesg lines with HDMI in them.
</p>

<p>
	 
</p>

<p>
	root@odroidxu4:~# grep -i hdmi dmesg_hdmi_works_usb_hdmi_plugged_in_at_boot.txt <br />
	[    0.000000] Kernel command line: console=ttySAC2,115200n8 console=tty1 consoleblank=0 loglevel=1 root=UUID=494e7783-a94f-45f7-940d-e0ce44ea1455 rootfstype=ext4 rootwait rw  smsc95xx.macaddr=00:1e:06:61:7a:55 governor=performance hdmi_tx_amp_lvl=31 hdmi_tx_lvl_ch0=3 hdmi_tx_lvl_ch1=3 hdmi_tx_lvl_ch2=3 hdmi_tx_emp_lvl=6 hdmi_clk_amp_lvl=31 hdmi_tx_res=0 HPD=true vout=hdmi usb-storage.quirks= <br />
	[    0.000000] hdmi: using HDMI mode<br />
	[    4.735974] OF: graph: no port node found in /<abbr title="System On a Chip">soc</abbr>/hdmi@14530000<br />
	[    4.737200] exynos-drm exynos-drm: bound 14530000.hdmi (ops 0xc0cb31ac)<br />
	 
</p>

<p>
	I read some other posts that talked about HDMI not working if a USB device was not connected.  For both of the attached dmesg output files, the USB keyboard and mouse were connected.  In <a class="ipsAttachLink" data-fileid="8665" href="https://testforum.armbian.com/applications/core/interface/file/attachment.php?id=8665&amp;key=9325d09950a501863dcaf9e1926bc405" data-fileext="txt" rel="">dmesg_hdmi_works_usb_hdmi_plugged_in_at_boot.txt</a>, the HDMI display was plugged in at boot time and works and in <a class="ipsAttachLink" data-fileid="8664" href="https://testforum.armbian.com/applications/core/interface/file/attachment.php?id=8664&amp;key=febe63c1d7b68a5df218671a7983e270" data-fileext="txt" rel="">dmesg_hdmi_fails_usb_plugged_in_at_boot_no_hdmi_at_boot.txt</a>, the HDMI display was not plugged in at boot time and does not work after it is plugged in.
</p>

<p>
	 
</p>

<p>
	Has anyone seen this behavior and, if so, do you know how to configure the Odriod to boot without the HDMI cable attached and have an HDMI display work after it is attached later?
</p>

<p>
	 
</p>

<p>
	Thanks,
</p>

<p>
	   Michael
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">19820</guid><pubDate>Sun, 06 Feb 2022 18:43:18 +0000</pubDate></item><item><title>armbianEnv.txt missing from latest XU4 focal image</title><link>https://testforum.armbian.com/topic/19591-armbianenvtxt-missing-from-latest-xu4-focal-image/</link><description><![CDATA[<p>
	armbianEnv.txt is missing from latest XU4 focal image Armbian_21.08.5_Odroidxu4_focal_current_5.4.159_minimal.img. Should I just create on or use boot.ini?
</p>
]]></description><guid isPermaLink="false">19591</guid><pubDate>Sun, 02 Jan 2022 16:45:37 +0000</pubDate></item><item><title>Error on kernel and armbian update with apt update [Odroid-HC1]</title><link>https://testforum.armbian.com/topic/18802-error-on-kernel-and-armbian-update-with-apt-update-odroid-hc1/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	I froze kernel to Linux 4.14.222-odroidxu4 as my Odroid-HC1 couldn't be sometime reach with ssh when updating kernel.
</p>

<p>
	I get that after reboot and doing apt update,
</p>

<p>
	N: Ignoring file '02-armbian-periodic.distrib' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension
</p>

<p>
	This file is apparently created again as I remove it each time.
</p>

<p>
	Laurent
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18802</guid><pubDate>Fri, 13 Aug 2021 12:20:23 +0000</pubDate></item><item><title>Odroid HC2 - Armbian - failure retrieving kernel</title><link>https://testforum.armbian.com/topic/18898-odroid-hc2-armbian-failure-retrieving-kernel/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	few days ago I did apt upgrade of my armbian system on Odroid HC2 and there was a reboot req cause of new kernel, so I did reboot it.
</p>

<p>
	It wont boot with this error (sorry for missing letters, my LCD is not able to reposition the screen output, attached usb kbd is not working, dont know why, so I just took a pict by my phone):
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted"><span class="pln">h to partitions #0, OK
is current device ing mmc 0:1...
/boot/extlinux/extlinux.conf
eving file: /boot/extlinux/extlinux.conf ytes read in 2 ms (149.4 KiB/s)
Armbian
eving file: /boot/uInitrd 776 bytes read in 782 ms (20.2 MiB/s)
eving file: /boot/Image d to load '/boot/Image'
ing Armbian for failure retrieving kernel
T FAILED: continuing... U-Boot script /boot/boot.scr
bytes read in 3 ms (2.3 MiB/s) ecuting script at 08000000
776 bytes read in 760 ms (20.7 MiB/s) d to load '/boot/Image'
bytes read in 8 ms (8.8 MiB/s)
d to load '/boot/dtb/am logic/overlay/-fixup.scr' inux ARM64 Image magic!
'T FAILED: continuing... ing disk sdeffe05000.blk...
did not respond to voltage select! : -110 ing disk mmc@ffe07000.blk...
mmc@ffe07000.blk not ready
2 disks
I system partition Irder not defined
oot manager: Cannot load any image
did not respond to voltage select!:
evice 2 not found
c device at slot 2
ing USB...
sbeff500000: Register 3000140 NbrPorts 3 ing the controller
HCI 1.10
ing bus usbeff500000 for devices... 1 USB Device(s) fou scanning usb for storage devices... 0 Storage Device C
e 0: unknown device meteff3f0000 Waiting for PHY auto negotiation to comple
not initialize PHY etherneteff3f0000 ng environment variable: pxeuuid
eving file: /boot/extlinux/pxelinux.cfg/01-00-1e-06-49 meteff3f0000 Waiting for PHY auto negotiation to comple not initialize PHY etherneteff3f0000
-110</span></pre>

<p>
	How can I fix it? Card is readable with no problem, tested with another pc...
</p>

<p>
	Thanks lot for help.
</p>

<p>
	VicC<br>
	<img alt="IMG_20210904_095728.png" class="ipsImage" data-ratio="75.08" height="750" width="422" src="https://heap.victorc.net/IMG_20210904_095728.png" loading="lazy">
</p>
]]></description><guid isPermaLink="false">18898</guid><pubDate>Sat, 04 Sep 2021 08:15:46 +0000</pubDate></item><item><title>XU4 upgrade kernel (boot from HDD</title><link>https://testforum.armbian.com/topic/15155-xu4-upgrade-kernel-boot-from-hdd/</link><description><![CDATA[<p>
	Hi, guys. Little help here
</p>

<p>
	 
</p>

<p>
	After being tired of my docker containers loosing connectivity to the internet I've decided to fully update/upgrade armbian (including the kernel)<br>
	<br>
	Now my system boots but most applications don't work. Most cases are missing kernel modules<br>
	The /lib/modules dir contains the new updated content as the /boot too<br>
	But the system keeps booting the old kernel image (4.14.176) and not the new one (4.14.195). It makes no difference if I upgrade the kernel via apt or via armbian-config<br>
	<br>
	I guess the issue is the files still in the SD card used for boot (they are 4.14.176 by it's names). Shouldn't armbian-config update those files?<br>
	If not, how do I update them so my apps can get back to work? I've mounted /dev/mmcblk1p1 and have access to the files, just don't know which ones I should overwrite<br>
	<br>
	Thanks in advance<br>
	Will
</p>
]]></description><guid isPermaLink="false">15155</guid><pubDate>Tue, 08 Sep 2020 06:14:02 +0000</pubDate></item><item><title>[Invalid] - Cluodshell2 questions</title><link>https://testforum.armbian.com/topic/18867-invalid-cluodshell2-questions/</link><description><![CDATA[<p>
	As far as I can see on odroid wiki for the lcd and fan enabling the links leads to ubuntu files.<br />
	I want to install latest armbian for odroid xu4q board and omv5 so I'm wondering if I can use these files or do I need some other files to enable lcd and fan on cloudshell2 + odroid xu4q and armbian?
</p>
]]></description><guid isPermaLink="false">18867</guid><pubDate>Mon, 30 Aug 2021 06:58:15 +0000</pubDate></item><item><title>XU4 loses network connections over time</title><link>https://testforum.armbian.com/topic/18333-xu4-loses-network-connections-over-time/</link><description><![CDATA[<p>
	Howdy, I'm running Armbian_21.05.1_Odroidxu4_focal_current_5.4.116.img on my XU4 for security cameras. It averages about 60 Mbps 24/7. After a couple days usually one adapter disappears (from ip a and nmtui) and sometimes both (I have a USB 1 Gbps adapter too). I'm not seeing anything in the logs to indicate an error. I monitor this system with Zabbix and I see no unusual activity before this happens. Is there a way to get diagnostics for this event?  
</p>
]]></description><guid isPermaLink="false">18333</guid><pubDate>Sun, 06 Jun 2021 16:20:58 +0000</pubDate></item><item><title>Odroid HC2 Hard Drive not found / readable under Armbian Focal</title><link>https://testforum.armbian.com/topic/18394-odroid-hc2-hard-drive-not-found-readable-under-armbian-focal/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	 
</p>

<p>
	My Hard Drive in my HC2 is not found or not readable. Before I was on Armbian Buster with Kernel 4.14 and everything was working fine.
</p>

<p>
	I switched and am now running Armbian Focal 21.05.2 with Kernel 5.4.116 . HDD is btrfs formatted. /proc/filesystems lists btrfs so this is not the problem. /dev/sda exists, but sda will not be listed when I lsblk.
</p>

<p>
	Dmesg shows a Read Capacity(16) failed. Not posting the whole dmesg log b/c armbianmonitor is attached.
</p>

<p>
	 
</p>

<p>
	Grateful for any help or hints =)
</p>
]]></description><guid isPermaLink="false">18394</guid><pubDate>Tue, 15 Jun 2021 16:28:48 +0000</pubDate></item><item><title>[Invalid] - xu4 with ZFS as root fs / on sd card</title><link>https://testforum.armbian.com/topic/18271-invalid-xu4-with-zfs-as-root-fs-on-sd-card/</link><description><![CDATA[<p>
	Hello,
</p>

<p>
	i saw a post regarding ZFS &gt;  <a href="https://testforum.armbian.com/topic/16119-zfs-on-helios64/page/2/?tab=comments#comment-119575" rel="">zfs </a>
</p>

<p>
	 
</p>

<p>
	What is the current state of ZFS support? Is it a stable to run ZFS as FS for root fs only on SD card (16-32GB)? I need that for an easy backup on FS level using send/rec commands. But as we know xu4 is 32bit only - &gt; maybe problem with stability - <a href="https://openzfs.github.io/openzfs-docs/Project%20and%20Community/FAQ.html#bit-vs-64-bit-systems" rel="external nofollow">stability 32bit</a>
</p>

<p>
	 
</p>

<p>
	official solution but for <a href="https://openzfs.github.io/openzfs-docs/Getting%20Started/Ubuntu/Ubuntu%2020.04%20Root%20on%20ZFS%20for%20Raspberry%20Pi.html" rel="external nofollow">rpi4</a>
</p>

<p>
	 
</p>

<p>
	Or maybe is there a point to use zfs for root fs at all? what about LMV? <br />
	 
</p>

<p>
	 
</p>

<p>
	thanks
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18271</guid><pubDate>Wed, 02 Jun 2021 21:30:30 +0000</pubDate></item><item><title>Odroid HC1 no boot after upgrade</title><link>https://testforum.armbian.com/topic/18121-odroid-hc1-no-boot-after-upgrade/</link><description><![CDATA[<p>
	Hi,<br />
	<br />
	I am using Nextcloudpi Image (Armbian) on an HC1. This setup is obviously not booting anymore after system upgrade.
</p>

<p>
	Packages that have been upgraded:<br />
	- armbian-config<br />
	- armbian-firmware<br />
	- linux-buster-root-legacy-odroidxu4<br />
	- linux-<abbr title="Device tree blob">dtb</abbr>-legacy-odroidxu4<br />
	- linux-image-legacy-odroidxu4<br />
	- linux-u-boot-odroidxu4-legacy
</p>

<p>
	 
</p>

<p>
	Insterting the µSD into an Laptop running PureOS (Debian fork) I can access log files.<br />
	I could investigate so far, that there was a system upgrade (armbian-firmware_21.05.1) on 2021-05-11 6:00 am. After that a message that system will be rebooted on 2021-05-12 4:00 am.<br />
	That actually happened. I can see this in several log files. BUT after that system shutdown there are no further log entries, which indicates a failes boot (in my very unprofessional opinion).<br />
	<br />
	Since this system is not only running NC, but also AdGuard and other stuff, it is very important to me. There is a full NC backup I weekly run, BUT not for AdGuard and other stuff. That is why I am fighting not to reflash the SD card.<br />
	I can post log files or other things, that may enable you helping and investigating the issue.<br />
	<br />
	Thank you very much in advance.
</p>
]]></description><guid isPermaLink="false">18121</guid><pubDate>Fri, 14 May 2021 19:12:04 +0000</pubDate></item><item><title>Odroid XU4(q)</title><link>https://testforum.armbian.com/topic/18229-odroid-xu4q/</link><description><![CDATA[<p>
	.
</p>
]]></description><guid isPermaLink="false">18229</guid><pubDate>Wed, 26 May 2021 13:13:26 +0000</pubDate></item><item><title>Remove linux-buster-root-current-odroidxu4?</title><link>https://testforum.armbian.com/topic/18114-remove-linux-buster-root-current-odroidxu4/</link><description><![CDATA[<p>
	After latest upgrade 21.05.01 apt says linux-buster-root-current-odroidxu4 is obsolete now and could be removed with autoremove.
</p>

<p>
	But even this version was installed with same upgrade, so i wonder why it should be removed now?  Should i really remove that package?
</p>

<p>
	Thx
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">18114</guid><pubDate>Fri, 14 May 2021 09:02:02 +0000</pubDate></item><item><title>Odroid HC1 and kernel-5.4: soft reset makes the sata drive disappear</title><link>https://testforum.armbian.com/topic/15611-odroid-hc1-and-kernel-54-soft-reset-makes-the-sata-drive-disappear/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I have recently installed armbian-config on my HC1 running OMV and switched to -current kernel from -legacy. Unfortunately, now whenever I soft-reboot following a kernel update, the sda drive is missing:
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">[    6.161366] usbcore: registered new interface driver usb-storage
[    6.180240] scsi host0: uas
[    6.181260] usbcore: registered new interface driver uas
[    6.182155] scsi 0:0:0:0: Direct-Access     JMicron  Generic          3102 PQ: 0 ANSI: 6
[    6.193271] sd 0:0:0:0: [sda] Unit Not Ready
[    6.193290] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
[    6.193302] sd 0:0:0:0: [sda] ASC=0x44 &lt;</span><span class="tag">&lt;vendor&gt;</span><span class="pln">&gt;ASCQ=0x81 
[    6.194247] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
[    6.194258] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
[    6.194267] sd 0:0:0:0: [sda] ASC=0x44 &lt;</span><span class="tag">&lt;vendor&gt;</span><span class="pln">&gt;ASCQ=0x81 
[    6.195019] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
[    6.195029] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
[    6.195038] sd 0:0:0:0: [sda] ASC=0x44 &lt;</span><span class="tag">&lt;vendor&gt;</span><span class="pln">&gt;ASCQ=0x81 
[    6.196157] sd 0:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
[    6.196177] sd 0:0:0:0: [sda] 0-byte physical blocks
[    6.197261] sd 0:0:0:0: [sda] Test WP failed, assume Write Enabled
[    6.197631] sd 0:0:0:0: [sda] Asking for cache data failed
[    6.197651] sd 0:0:0:0: [sda] Assuming drive cache: write through
[    6.198713] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)
[    6.302324] sd 0:0:0:0: [sda] Unit Not Ready
[    6.302371] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
[    6.302414] sd 0:0:0:0: [sda] ASC=0x44 &lt;</span><span class="tag">&lt;vendor&gt;</span><span class="pln">&gt;ASCQ=0x81 
[    6.303970] sd 0:0:0:0: [sda] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
[    6.304015] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
[    6.304057] sd 0:0:0:0: [sda] ASC=0x44 &lt;</span><span class="tag">&lt;vendor&gt;</span><span class="pln">&gt;ASCQ=0x81 
[    6.305549] sd 0:0:0:0: [sda] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
[    6.305592] sd 0:0:0:0: [sda] Sense Key : 0x4 [current] 
[    6.305632] sd 0:0:0:0: [sda] ASC=0x44 &lt;</span><span class="tag">&lt;vendor&gt;</span><span class="pln">&gt;ASCQ=0x81 
[    6.310272] sd 0:0:0:0: [sda] Attached SCSI disk</span></pre>

<p>
	Hard reset brings the drive back so it is not that tragic, but it is still a regression compared to 4.14 kernels.
</p>
]]></description><guid isPermaLink="false">15611</guid><pubDate>Sun, 18 Oct 2020 09:34:50 +0000</pubDate></item><item><title>procedure for cloning of sd card</title><link>https://testforum.armbian.com/topic/10729-procedure-for-cloning-of-sd-card/</link><description><![CDATA[<p>
	Hi!
</p>

<p>
	 
</p>

<p>
	short question: Best way to create a bootable clone of sd card? I did some reading and found "&gt;&gt;create image on windows &gt;&gt; shrink image via gparted" doesn't work for me since I dont have a second computer running linux (will the linux subsystem on windows 10 help?).
</p>

<p>
	 
</p>

<p>
	In the past, I used the rpi-clone on a raspberry, but reading in this forum has taught me that hotcloning an armbian sd card via script is not necessarily safe.
</p>

<p>
	 
</p>

<p>
	Computers availabel to me are: 1) odroid hc2 running armbian 2) acer laptop running windows 10
</p>
]]></description><guid isPermaLink="false">10729</guid><pubDate>Sat, 22 Jun 2019 15:29:52 +0000</pubDate></item><item><title>NFS Problems on HC4 after changing to Armbian</title><link>https://testforum.armbian.com/topic/17099-nfs-problems-on-hc4-after-changing-to-armbian/</link><description><![CDATA[<p>
	After switching from Debian Buster (installed via Petitboot) to Armbian, I have problems with NFS on Openmediavault that didn't exist the weeks before. My NFS streams abort after a few minutes, sometimes seconds (on Libreelec as well as Kodi for Windows). In OMV it shows me that the service is enabled and running, but systemctl says: nfs-server.service loaded active exited. With exportfs -rav it runs again, only to stop after a few minutes. It also works without command if I wait a few minutes. I also did a fresh install of Armbian, wich did nothing.
</p>
]]></description><guid isPermaLink="false">17099</guid><pubDate>Sat, 20 Feb 2021 15:47:31 +0000</pubDate></item><item><title>After apt upgrade unable to boot</title><link>https://testforum.armbian.com/topic/17056-after-apt-upgrade-unable-to-boot/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	 
</p>

<p>
	I'm running a couple of ODroid XU4's as a server. Yesterday I ran an update and after this update the board no longer boots... (I was running Armbian Focal kernel 4
</p>

<p>
	I have tested a 'fresh' armbian image and then the system boots without issues. I have saved what packages are updated and wonder if I would be able to restore this somehow?
</p>

<p>
	 
</p>

<p>
	A log of the update (never mind the dutch)
</p>

<p>
	<a href="https://pastebin.com/WWP2DFfC" rel="external nofollow">https://pastebin.com/WWP2DFfC</a>
</p>

<p>
	 
</p>

<p>
	I used to have kernal 5.4 on this board, but I downgraded about 6 months ago. Could that be the issue?
</p>

<p>
	Because in the log I read:
</p>

<pre class="ipsCode">
Uitpakken van .../77-linux-image-current-odroidxu4_21.02.2_armhf.deb wordt voorbereid...
update-initramfs: Deleting /boot/initrd.img-5.4.72-odroidxu4
Removing obsolete file 4.14.202-odroidxu4
Removing obsolete file uInitrd-4.14.202-odroidxu4
update-initramfs: Deleting /boot/initrd.img-4.14.202-odroidxu4
Bezig met uitpakken van linux-image-current-odroidxu4 (21.02.2) over (20.08.13) ...
Uitpakken van .../78-linux-image-legacy-odroidxu4_21.02.2_armhf.deb wordt voorbereid...
Bezig met uitpakken van linux-image-legacy-odroidxu4 (21.02.2) over (20.08.13) ...
Uitpakken van .../79-linux-u-boot-odroidxu4-legacy_21.02.1_armhf.deb wordt voorbereid...
Bezig met uitpakken van linux-u-boot-odroidxu4-legacy (21.02.1) over (20.08.13) ...</pre>

<p>
	 
</p>

<p>
	But later I find:
</p>

<pre class="ipsCode">
Instellen van linux-image-current-odroidxu4 (21.02.2) ...
update-initramfs: Generating /boot/initrd.img-5.4.98-odroidxu4
update-initramfs: Converting to u-boot format</pre>

<p>
	And even later:
</p>

<pre class="ipsCode">
Instellen van linux-image-legacy-odroidxu4 (21.02.2) ...
update-initramfs: Generating /boot/initrd.img-4.14.212-odroidxu4
update-initramfs: Converting to u-boot format</pre>

<p>
	 
</p>

<p>
	What would be the way to revert the culprit updates?
</p>
]]></description><guid isPermaLink="false">17056</guid><pubDate>Tue, 16 Feb 2021 16:36:55 +0000</pubDate></item><item><title>Odroid HC2 freeze during logrotate?</title><link>https://testforum.armbian.com/topic/16798-odroid-hc2-freeze-during-logrotate/</link><description><![CDATA[<p>
	I can't pinpoint the cause of the freeze exactly, but it shows as follows in syslog:
</p>

<p>
	At midnight, logrotate was started but never successfully concluded.
</p>

<p>
	At the time, I was also recording a stream via smb to the hdd. (Not a very demanding activity)
</p>

<p>
	When I tried to access the <abbr title="Single board computer">SBC</abbr> via network share or ssh this morning, neither would show as available. The <abbr title="Single board computer">SBC</abbr> was running but "dead".
</p>

<p>
	When I rebooted it by re-plugging power, instead of showing ~9:00 o'clock, the SBCs internal clock showed 02:17.
</p>

<p>
	 
</p>

<p>
	Here are the last messages of the syslog before the <abbr title="Single board computer">SBC</abbr> locked up:
</p>

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

	<div class="ipsQuote_contents">
		<p>
			Jan 17 00:00:00 droid systemd[1]: Starting Rotate log files...<br />
			Jan 17 00:00:01 droid armbian-ramlog[390]: Sun 17 Jan 2021 12:00:01 AM CET: Syncing logs to storage<br />
			Jan 17 00:00:01 droid armbian-ramlog[390]: sending incremental file list<br />
			Jan 17 00:00:01 droid armbian-ramlog[390]: auth.log<br />
			Jan 17 00:00:01 droid armbian-ramlog[390]: daemon.log<br />
			Jan 17 02:17:10 droid systemd-udevd[370]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.<br />
			Jan 17 02:17:10 droid systemd-udevd[365]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
		</p>
	</div>
</blockquote>

<p>
	 
</p>

<p>
	I should note that the <abbr title="Single board computer">SBC</abbr> has been running 24/7 stable for weeks.
</p>

<p>
	There have been more hardware demanding tasks running without issue.
</p>
]]></description><guid isPermaLink="false">16798</guid><pubDate>Sun, 17 Jan 2021 09:33:55 +0000</pubDate></item><item><title>Best core for Odroid HC2</title><link>https://testforum.armbian.com/topic/16713-best-core-for-odroid-hc2/</link><description><![CDATA[<p>
	Hi, please, which core are You using on odroid HC2? I am running on HC2 only openmediavault, but i will try nextcloud in the docker  - which core image is better for?
</p>
]]></description><guid isPermaLink="false">16713</guid><pubDate>Thu, 07 Jan 2021 08:34:12 +0000</pubDate></item><item><title>Issue with armbian-truncate-logs [odroid-HC1]</title><link>https://testforum.armbian.com/topic/16605-issue-with-armbian-truncate-logs-odroid-hc1/</link><description><![CDATA[<p>
	Hi,
</p>

<p>
	 
</p>

<p>
	I've got since several days an issue with armbian-truncate-logs. I received mail alerts from cron as this one,
</p>

<p>
	<br />
	error: error running shared postrotate script for '/var/log.hdd/mysql/mysql.log /var/log.hdd/mysql/mysql-slow.log<br />
	+/var/log.hdd/mysql/mariadb-slow.log /var/log.hdd/mysql/error.log '<br />
	error: error running shared postrotate script for '/var/log.hdd/nginx/*.log '
</p>

<p>
	<br />
	How to debug that?
</p>

<p>
	<br />
	Laurent
</p>
]]></description><guid isPermaLink="false">16605</guid><pubDate>Sun, 27 Dec 2020 18:05:10 +0000</pubDate></item><item><title>XU4 gpio device line names</title><link>https://testforum.armbian.com/topic/16441-xu4-gpio-device-line-names/</link><description><![CDATA[<p>
	OK, so while documenting the Armbian patch process I needed something actual to patch. I added <abbr title="General purpose input/output"><abbr title="General purpose input/output">gpio</abbr></abbr>-line-names to the device tree, so now all lines are defined. Once I finish the documentation I'll PR this patch. No more guessing what physical pin is! At some point it might make sense to put in jumper and physical pin #.
</p>

<p>
	 
</p>

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

	<div class="ipsSpoiler_contents">
		<pre class="ipsCode prettyprint lang-html prettyprinted">

<span class="pln">gpioinfo
gpiochip0 - 8 lines:
	line   0:     "GPY7.0"       unused   input  active-high 
	line   1:     "GPY7.1"       unused   input  active-high 
	line   2:     "GPY7.2"       unused   input  active-high 
	line   3:     "GPY7.3"       unused   input  active-high 
	line   4:     "GPY7.4"       unused   input  active-high 
	line   5:     "GPY7.5"       unused   input  active-high 
	line   6:     "GPY7.6"       unused   input  active-high 
	line   7:     "GPY7.7"       unused   input  active-high 
gpiochip1 - 8 lines:
	line   0:     "GPX0.0"       unused   input  active-high 
	line   1:     "GPX0.1"       unused   input  active-high 
	line   2:     "GPX0.2"       unused   input  active-high 
	line   3:     "GPX0.3"  "power key"   input   active-low [used]
	line   4:     "GPX0.4"  "interrupt"   input  active-high [used]
	line   5:     "GPX0.5"       unused   input  active-high 
	line   6:     "GPX0.6"       unused   input  active-high 
	line   7:     "GPX0.7"       unused   input  active-high 
gpiochip10 - 8 lines:
	line   0:     "GPD1.0"      "reset"  output   active-low [used]
	line   1:     "GPD1.1"       unused   input  active-high 
	line   2:     "GPD1.2"       unused   input  active-high 
	line   3:     "GPD1.3"       unused   input  active-high 
	line   4:     "GPD1.4"       unused   input  active-high 
	line   5:     "GPD1.5"       unused   input  active-high 
	line   6:     "GPD1.6"       unused   input  active-high 
	line   7:     "GPD1.7"       unused   input  active-high 
gpiochip11 - 6 lines:
	line   0:     "GPY0.0"       unused   input  active-high 
	line   1:     "GPY0.1"       unused   input  active-high 
	line   2:     "GPY0.2"       unused   input  active-high 
	line   3:     "GPY0.3"       unused   input  active-high 
	line   4:     "GPY0.4"       unused   input  active-high 
	line   5:     "GPY0.5"       unused   input  active-high 
gpiochip12 - 4 lines:
	line   0:     "GPY1.0"       unused   input  active-high 
	line   1:     "GPY1.1"       unused   input  active-high 
	line   2:     "GPY1.2"       unused   input  active-high 
	line   3:     "GPY1.3"       unused   input  active-high 
gpiochip13 - 6 lines:
	line   0:     "GPY2.0"       unused   input  active-high 
	line   1:     "GPY2.1"       unused   input  active-high 
	line   2:     "GPY2.2"       unused   input  active-high 
	line   3:     "GPY2.3"       unused   input  active-high 
	line   4:     "GPY2.4"       unused   input  active-high 
	line   5:     "GPY2.5"       unused   input  active-high 
gpiochip14 - 8 lines:
	line   0:     "GPY3.0"       unused   input  active-high 
	line   1:     "GPY3.1"       unused   input  active-high 
	line   2:     "GPY3.2"       unused   input  active-high 
	line   3:     "GPY3.3"       unused   input  active-high 
	line   4:     "GPY3.4"       unused   input  active-high 
	line   5:     "GPY3.5"       unused   input  active-high 
	line   6:     "GPY3.6"       unused   input  active-high 
	line   7:     "GPY3.7"       unused   input  active-high 
gpiochip15 - 8 lines:
	line   0:     "GPY4.0"       unused   input  active-high 
	line   1:     "GPY4.1"       unused   input  active-high 
	line   2:     "GPY4.2"       unused   input  active-high 
	line   3:     "GPY4.3"       unused   input  active-high 
	line   4:     "GPY4.4"       unused   input  active-high 
	line   5:     "GPY4.5"       unused   input  active-high 
	line   6:     "GPY4.6"       unused   input  active-high 
	line   7:     "GPY4.7"       unused   input  active-high 
gpiochip16 - 8 lines:
	line   0:     "GPY5.0"       unused   input  active-high 
	line   1:     "GPY5.1"       unused   input  active-high 
	line   2:     "GPY5.2"       unused   input  active-high 
	line   3:     "GPY5.3"       unused   input  active-high 
	line   4:     "GPY5.4"       unused   input  active-high 
	line   5:     "GPY5.5"       unused   input  active-high 
	line   6:     "GPY5.6"       unused   input  active-high 
	line   7:     "GPY5.7"       unused   input  active-high 
gpiochip17 - 8 lines:
	line   0:     "GPY6.0"       unused   input  active-high 
	line   1:     "GPY6.1"       unused   input  active-high 
	line   2:     "GPY6.2"       unused   input  active-high 
	line   3:     "GPY6.3"       unused   input  active-high 
	line   4:     "GPY6.4"       unused   input  active-high 
	line   5:     "GPY6.5"       unused   input  active-high 
	line   6:     "GPY6.6"       unused   input  active-high 
	line   7:     "GPY6.7"       unused   input  active-high 
gpiochip18 - 8 lines:
	line   0:     "GPE0.0"       unused   input  active-high 
	line   1:     "GPE0.1"       unused   input  active-high 
	line   2:     "GPE0.2"       unused   input  active-high 
	line   3:     "GPE0.3"       unused   input  active-high 
	line   4:     "GPE0.4"       unused   input  active-high 
	line   5:     "GPE0.5"       unused   input  active-high 
	line   6:     "GPE0.6"       unused   input  active-high 
	line   7:     "GPE0.7"       unused   input  active-high 
gpiochip19 - 2 lines:
	line   0:     "GPE1.0"       unused   input  active-high 
	line   1:     "GPE1.1"       unused   input  active-high 
gpiochip2 - 8 lines:
	line   0:     "GPX1.0"       unused   input  active-high 
	line   1:     "GPX1.1"       unused   input  active-high 
	line   2:     "GPX1.2"       unused   input  active-high 
	line   3:     "GPX1.3"       unused   input  active-high 
	line   4:     "GPX1.4"       unused   input  active-high 
	line   5:     "GPX1.5"       unused   input  active-high 
	line   6:     "GPX1.6"       unused   input  active-high 
	line   7:     "GPX1.7"       unused   input  active-high 
gpiochip20 - 6 lines:
	line   0:     "GPF0.0"       unused   input  active-high 
	line   1:     "GPF0.1"       unused   input  active-high 
	line   2:     "GPF0.2"       unused   input  active-high 
	line   3:     "GPF0.3"       unused   input  active-high 
	line   4:     "GPF0.4"       unused   input  active-high 
	line   5:     "GPF0.5"       unused   input  active-high 
gpiochip21 - 8 lines:
	line   0:     "GPF1.0"       unused   input  active-high 
	line   1:     "GPF1.1"       unused   input  active-high 
	line   2:     "GPF1.2"       unused   input  active-high 
	line   3:     "GPF1.3"       unused   input  active-high 
	line   4:     "GPF1.4"       unused   input  active-high 
	line   5:     "GPF1.5"       unused   input  active-high 
	line   6:     "GPF1.6"       unused   input  active-high 
	line   7:     "GPF1.7"       unused   input  active-high 
gpiochip22 - 8 lines:
	line   0:     "GPG0.0"       unused   input  active-high 
	line   1:     "GPG0.1"       unused   input  active-high 
	line   2:     "GPG0.2"       unused   input  active-high 
	line   3:     "GPG0.3"       unused   input  active-high 
	line   4:     "GPG0.4"       unused   input  active-high 
	line   5:     "GPG0.5"       unused   input  active-high 
	line   6:     "GPG0.6"       unused   input  active-high 
	line   7:     "GPG0.7"       unused   input  active-high 
gpiochip23 - 8 lines:
	line   0:     "GPG1.0"       unused   input  active-high 
	line   1:     "GPG1.1"       unused   input  active-high 
	line   2:     "GPG1.2"       unused   input  active-high 
	line   3:     "GPG1.3"       unused   input  active-high 
	line   4:     "GPG1.4"       unused   input  active-high 
	line   5:     "GPG1.5"       unused   input  active-high 
	line   6:     "GPG1.6"       unused   input  active-high 
	line   7:     "GPG1.7"       unused   input  active-high 
gpiochip24 - 2 lines:
	line   0:     "GPG2.0"       unused   input  active-high 
	line   1:     "GPG2.1"       unused   input  active-high 
gpiochip25 - 4 lines:
	line   0:     "GPJ4.0"       unused   input  active-high 
	line   1:     "GPJ4.1"       unused   input  active-high 
	line   2:     "GPJ4.2"       unused   input  active-high 
	line   3:     "GPJ4.3"       unused   input  active-high 
gpiochip26 - 8 lines:
	line   0:     "GPA0.0"       unused   input  active-high 
	line   1:     "GPA0.1"       unused   input  active-high 
	line   2:     "GPA0.2"       unused   input  active-high 
	line   3:     "GPA0.3"       unused   input  active-high 
	line   4:     "GPA0.4"       unused   input  active-high 
	line   5:     "GPA0.5"       unused   input  active-high 
	line   6:     "GPA0.6"       unused   input  active-high 
	line   7:     "GPA0.7"       unused   input  active-high 
gpiochip27 - 6 lines:
	line   0:     "GPA1.0"       unused   input  active-high 
	line   1:     "GPA1.1"       unused   input  active-high 
	line   2:     "GPA1.2"       unused   input  active-high 
	line   3:     "GPA1.3"       unused   input  active-high 
	line   4:     "GPA1.4"       unused   input  active-high 
	line   5:     "GPA1.5"       unused   input  active-high 
gpiochip28 - 8 lines:
	line   0:     "GPA2.0"       unused   input  active-high 
	line   1:     "GPA2.1"       unused   input  active-high 
	line   2:     "GPA2.2"       unused   input  active-high 
	line   3:     "GPA2.3"       unused   input  active-high 
	line   4:     "GPA2.4"       unused   input  active-high 
	line   5:     "GPA2.5"       unused   input  active-high 
	line   6:     "GPA2.6"       unused   input  active-high 
	line   7:     "GPA2.7"       unused   input  active-high 
gpiochip29 - 5 lines:
	line   0:     "GPB0.0"       unused   input  active-high 
	line   1:     "GPB0.1"       unused   input  active-high 
	line   2:     "GPB0.2"       unused   input  active-high 
	line   3:     "GPB0.3"       unused   input  active-high 
	line   4:     "GPB0.4"       unused   input  active-high 
gpiochip3 - 8 lines:
	line   0:     "GPX2.0"       unused   input  active-high 
	line   1:     "GPX2.1"       unused   input  active-high 
	line   2:     "GPX2.2"       unused   input  active-high 
	line   3:     "GPX2.3"       unused   input  active-high 
	line   4:     "GPX2.4"       unused   input  active-high 
	line   5:     "GPX2.5"       unused   input  active-high 
	line   6:     "GPX2.6"       unused   input  active-high 
	line   7:     "GPX2.7"       unused   input  active-high 
gpiochip30 - 5 lines:
	line   0:     "GPB1.0"       unused   input  active-high 
	line   1:     "GPB1.1"       unused   input  active-high 
	line   2:     "GPB1.2"       unused   input  active-high 
	line   3:     "GPB1.3"       unused   input  active-high 
	line   4:     "GPB1.4"       unused   input  active-high 
gpiochip31 - 4 lines:
	line   0:     "GPB2.0"       unused   input  active-high 
	line   1:     "GPB2.1"       unused   input  active-high 
	line   2:     "GPB2.2"       unused   input  active-high 
	line   3:     "GPB2.3"       unused   input  active-high 
gpiochip32 - 8 lines:
	line   0:     "GPB3.0"       unused   input  active-high 
	line   1:     "GPB3.1"       unused   input  active-high 
	line   2:     "GPB3.2"       unused   input  active-high 
	line   3:     "GPB3.3"       unused   input  active-high 
	line   4:     "GPB3.4"       unused   input  active-high 
	line   5:     "GPB3.5"       unused   input  active-high 
	line   6:     "GPB3.6"       unused   input  active-high 
	line   7:     "GPB3.7"       unused   input  active-high 
gpiochip33 - 2 lines:
	line   0:     "GPB4.0"       unused   input  active-high 
	line   1:     "GPB4.1"       unused   input  active-high 
gpiochip34 - 8 lines:
	line   0:     "GPH0.0"       unused   input  active-high 
	line   1:     "GPH0.1"       unused   input  active-high 
	line   2:     "GPH0.2"       unused   input  active-high 
	line   3:     "GPH0.3"       unused   input  active-high 
	line   4:     "GPH0.4"       unused   input  active-high 
	line   5:     "GPH0.5"       unused   input  active-high 
	line   6:     "GPH0.6"       unused   input  active-high 
	line   7:     "GPH0.7"       unused   input  active-high 
gpiochip35 - 7 lines:
	line   0:      "GPZ.0"       unused   input  active-high 
	line   1:      "GPZ.1"       unused   input  active-high 
	line   2:      "GPZ.2"       unused   input  active-high 
	line   3:      "GPZ.3"       unused   input  active-high 
	line   4:      "GPZ.4"       unused   input  active-high 
	line   5:      "GPZ.5"       unused   input  active-high 
	line   6:      "GPZ.6"       unused   input  active-high 
gpiochip4 - 8 lines:
	line   0:     "GPX3.0"       unused   input  active-high 
	line   1:     "GPX3.1"       unused   input  active-high 
	line   2:     "GPX3.2"       unused   input  active-high 
	line   3:     "GPX3.2"       unused   input  active-high 
	line   4:     "GPX3.4"       unused   input  active-high 
	line   5:     "GPX3.5"       unused   input  active-high 
	line   6:     "GPX3.6"       unused   input  active-high 
	line   7:     "GPX3.7"        "hpd"   input  active-high [used]
gpiochip5 - 8 lines:
	line   0:     "GPC0.0"       unused   input  active-high 
	line   1:     "GPC0.1"       unused   input  active-high 
	line   2:     "GPC0.2"       unused   input  active-high 
	line   3:     "GPC0.3"       unused   input  active-high 
	line   4:     "GPC0.4"       unused   input  active-high 
	line   5:     "GPC0.5"       unused   input  active-high 
	line   6:     "GPC0.6"       unused   input  active-high 
	line   7:     "GPC0.7"       unused   input  active-high 
gpiochip6 - 8 lines:
	line   0:     "GPC1.0"       unused   input  active-high 
	line   1:     "GPC1.1"       unused   input  active-high 
	line   2:     "GPC1.2"       unused   input  active-high 
	line   3:     "GPC1.3"       unused   input  active-high 
	line   4:     "GPC1.4"       unused   input  active-high 
	line   5:     "GPC1.5"       unused   input  active-high 
	line   6:     "GPC1.6"       unused   input  active-high 
	line   7:     "GPC1.7"       unused   input  active-high 
gpiochip7 - 7 lines:
	line   0:     "GPC2.0"       unused   input  active-high 
	line   1:     "GPC2.1"       unused   input  active-high 
	line   2:     "GPC2.2"       unused   input  active-high 
	line   3:     "GPC2.3"       unused   input  active-high 
	line   4:     "GPC2.4"       unused   input  active-high 
	line   5:     "GPC2.5"       unused   input  active-high 
	line   6:     "GPC2.6"       unused   input  active-high 
gpiochip8 - 4 lines:
	line   0:     "GPC3.0"       unused   input  active-high 
	line   1:     "GPC3.1"       unused   input  active-high 
	line   2:     "GPC3.2"       unused   input  active-high 
	line   3:     "GPC3.3"       unused   input  active-high 
gpiochip9 - 2 lines:
	line   0:     "GPC4.0"       unused   input  active-high 
	line   1:     "GPC4.1"       unused   input  active-high </span></pre>

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

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">16441</guid><pubDate>Fri, 11 Dec 2020 23:25:48 +0000</pubDate></item><item><title>/dev/gpiomem doesn't support GPZ</title><link>https://testforum.armbian.com/topic/16313-devgpiomem-doesnt-support-gpz/</link><description><![CDATA[<p>
	So I tried switching my MMIO <abbr title="General purpose input/output">GPIO</abbr> to /dev/gpiomem from /dev/mem and it doesn't appear to support the GPZ block <a href="https://wiki.odroid.com/odroid-xu4/hardware/expansion_connectors#con_11_-_2x6_pins" rel="external nofollow">https://wiki.odroid.com/odroid-xu4/hardware/expansion_connectors#con_11_-_2x6_pins</a> The address is 0x03860000. Hard Kernel's wiringPi doesn't seem to support this either. Should this be a question I ask Hard Kernel folks? <a href="https://wiki.odroid.com/odroid-xu4/software/gpio_register_map" rel="external nofollow">https://wiki.odroid.com/odroid-xu4/software/gpio_register_map</a>
</p>
]]></description><guid isPermaLink="false">16313</guid><pubDate>Sun, 06 Dec 2020 03:24:23 +0000</pubDate></item><item><title>Odroid XU4, Copy System from SD-Card to EMMC</title><link>https://testforum.armbian.com/topic/16228-odroid-xu4-copy-system-from-sd-card-to-emmc/</link><description><![CDATA[<p>
	Dear Readers<br />
	 
</p>

<p>
	I had quite some troubles migrating my armbian system from an SD-Card (16GB) to my <abbr title="embedded MultiMediaCard">emmc</abbr> (32GB). I'd like to sum up my journey for future travelers ;-)<br />
	<br />
	I was not successful simply copying the image of the sd to the <abbr title="embedded MultiMediaCard">emmc</abbr> and resizing the partition. It would not boot. Apparently <abbr title="embedded MultiMediaCard">emmc</abbr> has additional boot partitions which must be set correctly.
</p>

<p>
	I "repaired" the <abbr title="embedded MultiMediaCard">emmc</abbr> with this https://wiki.odroid.com/accessory/<abbr title="embedded MultiMediaCard">emmc</abbr>/recovery_xu4 and it booted Android all right from <abbr title="embedded MultiMediaCard">emmc</abbr>.<br />
	I then rebooted on my SD-Card and used the <abbr title="A type of flash memory">nand</abbr>-sata-install command to "Boot from <abbr title="embedded MultiMediaCard">eMMC</abbr> - system on <abbr title="embedded MultiMediaCard">eMMC</abbr>". It took some time to copy, but when booting on the <abbr title="embedded MultiMediaCard">emmc</abbr>, still Android.<br />
	Reboot on the SD-Card again and I manually deleted the <abbr title="embedded MultiMediaCard">emmc</abbr>-partitions (using parted, fdisk should work just as well) and created a new ext4 partition. I don't know, if the creation was necessary (it got overwritten anyway, as it should).<br />
	<br />
	I then used the <abbr title="A type of flash memory">nand</abbr>-sata-install command again and chose "Boot from <abbr title="embedded MultiMediaCard">eMMC</abbr> - system on <abbr title="embedded MultiMediaCard">eMMC</abbr>". After it finished I checked by mounting the new partition and it looked ok. And then it booted my system from <abbr title="embedded MultiMediaCard">emmc</abbr> just fine.<br />
	<br />
	I can't tell what the problem was initially, may be <abbr title="A type of flash memory">nand</abbr>-sata-install got confused by the 4 partitions the Android system had made on the <abbr title="embedded MultiMediaCard">emmc</abbr>.<br />
	 
</p>

<p>
	Many thanks to all contributors of armbian, especially for the very handy <abbr title="A type of flash memory">nand</abbr>-sata-install tool!<br />
	<br />
	Regards<br />
	<br />
	Ivo
</p>
]]></description><guid isPermaLink="false">16228</guid><pubDate>Tue, 01 Dec 2020 10:03:02 +0000</pubDate></item><item><title>kernel swap error with 5.8.16-odroidxu4 running on odroid HC2</title><link>https://testforum.armbian.com/topic/16064-kernel-swap-error-with-5816-odroidxu4-running-on-odroid-hc2/</link><description><![CDATA[<p>
	I have an array of HC2's running lizardfs.
</p>

<p>
	The other units are running 5.4.72-odroidxu4 kernels, but I dared to upgrade one to 5.8.16-odroidxu4
</p>

<p>
	Only this one unit threw a 
</p>

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

	<div class="ipsQuote_contents">
		<p>
			swapper/0: page allocation failure: order:0, mode:0xa20(GFP_ATOMIC), nodemask=(null),cpuset=/,mems_allowed=0
		</p>
	</div>
</blockquote>

<p>
	Since the other units didn't I show anything in their logs, I have to assume it isn't because a process running away or a memory leak.
</p>

<p>
	 
</p>

<p>
	line of fstab to mount the spinning rust drive:  <br />
	<strong>UUID=be95e207-1768-4fd9-bda9-ddc126a47d50 /chunks/be95e207-1768-4fd9-bda9-ddc126a47d50 xfs rw,noexec,nodev,noatime,nodiratime,largeio,inode64 0 2</strong>
</p>

<p>
	 
</p>

<p>
	Can't think of any additional info that would be useful.
</p>

<p>
	If someone has suggestions, i would be interested.
</p>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">16064</guid><pubDate>Sat, 21 Nov 2020 15:15:44 +0000</pubDate></item><item><title>Debian upgrade changes uInitrd link to point at latest Debian (instead of Armbian) version (ODROID-XU4)</title><link>https://testforum.armbian.com/topic/15958-debian-upgrade-changes-uinitrd-link-to-point-at-latest-debian-instead-of-armbian-version-odroid-xu4/</link><description><![CDATA[<p>
	Just doing maintenance tonight on my boxen, regular `apt upgrade &amp;&amp; apt update` on ODROID-XU4 and I noticed Debian upgraded to latest kernel (5.8 or whatever).  I go look in boot and notice `uInitrd' is pointing at the new Debian version (instead of Armbian version):
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">drwxr-xr-x  4 root root     4096 Nov 15 19:53 .
drwxr-xr-x 22 root root     4096 Nov 15 19:50 ..
-rw-r--r--  1 root root       65 Nov 15 19:28 armbianEnv.txt
-rw-r--r--  1 root root     1536 Jun  4 15:24 armbian_first_run.txt.template
-rw-r--r--  1 root root    38518 Jun  4 15:24 boot.bmp
-rw-r--r--  1 root root     4882 Jun  4 15:24 boot-desktop.png
-rw-r--r--  1 root root    12479 Jun  4 15:24 boot.ini
-rw-r--r--  1 root root       64 Jun  4 15:24 boot.scr
-rw-r--r--  1 root root   151722 Oct 18 15:42 config-4.14.202-odroidxu4
-rw-r--r--  1 root root   238874 Apr 23  2020 config-5.5.0-0.bpo.2-armmp-lpae
-rw-r--r--  1 root root   246529 Sep 26 13:31 config-5.8.0-0.bpo.2-armmp-lpae
lrwxrwxrwx  1 root root       22 Nov 15 19:49 dtb -&gt; dtb-4.14.202-odroidxu4
drwxr-xr-x  2 root root     4096 Nov 15 19:49 dtb-4.14.180-odroidxu4
drwxr-xr-x  2 root root     4096 Nov 15 19:49 dtb-4.14.202-odroidxu4
lrwxrwxrwx  1 root root       22 Jun  4 15:24 dtb.old -&gt; dtb-4.14.180-odroidxu4
-rw-r--r--  1 root root  7011311 Nov 15 19:50 initrd.img-4.14.202-odroidxu4
-rw-r--r--  1 root root 21912634 Nov 15 19:51 initrd.img-5.8.0-0.bpo.2-armmp-lpae
-rw-r--r--  1 root root        0 Nov 15 19:50 .next
-rw-r--r--  1 root root  2394556 Oct 18 15:42 System.map-4.14.202-odroidxu4
-rw-r--r--  1 root root  4131671 Apr 23  2020 System.map-5.5.0-0.bpo.2-armmp-lpae
-rw-r--r--  1 root root       83 Sep 26 13:31 System.map-5.8.0-0.bpo.2-armmp-lpae
lrwxrwxrwx  1 root root       26 Nov 15 19:53 uInitrd -&gt; uInitrd-5.8.0-0.bpo.2-armmp-lpae # &lt;--- see here
-rw-r--r--  1 root root  7011375 Nov 15 19:50 uInitrd-4.14.202-odroidxu4
-rw-r--r--  1 root root 21912698 Nov 15 19:51 uInitrd-5.8.0-0.bpo.2-armmp-lpae
-rwxr-xr-x  1 root root  5728872 Oct 18 15:42 vmlinuz-4.14.202-odroidxu4
-rw-r--r--  1 root root  4817408 Apr 23  2020 vmlinuz-5.5.0-0.bpo.2-armmp-lpae
-rw-r--r--  1 root root  4874752 Sep 26 13:31 vmlinuz-5.8.0-0.bpo.2-armmp-lpae
lrwxrwxrwx  1 root root       26 Nov 15 19:50 zImage -&gt; vmlinuz-4.14.202-odroidxu4</span></pre>

<p>
	 
</p>

<p>
	Only uInitrd was changed, not any others (as you can see).
</p>

<p>
	 
</p>

<p>
	I'm on Buster Stable.
</p>

<p>
	 
</p>

<p>
	I don't think this is supposed to happen?  Just wanted to ask here before filing bug though.
</p>

<p>
	 
</p>

<p>
	EDIT:  I also don't think it's a big deal either, as I'm pretty sure I rebooted without issue at least once in the meantime (before noticing).
</p>
]]></description><guid isPermaLink="false">15958</guid><pubDate>Mon, 16 Nov 2020 01:37:01 +0000</pubDate></item><item><title>Can not get realtek r8152b usb ethernet to work XU4</title><link>https://testforum.armbian.com/topic/15198-can-not-get-realtek-r8152b-usb-ethernet-to-work-xu4/</link><description><![CDATA[<p>
	Hello I can not seem to get my USB Ethernet dongle with a r8152b chip to work on the latest armbian focal release. I tied both kernels 4.14.y. and 5.4.y  with no luck. It works on "clean" ubuntu focal when i first plug it it without drivers and when i add the drivers. I am also posting in the odroid fourms here:  https://forum.odroid.com/viewtopic.php?f=172&amp;t=38713&amp;p=306027#p306027
</p>

<p>
	 
</p>

<p>
	I am following these directions:
</p>

<p>
	tar -xf r8152.53.56-2.13.0.tar.bz2<br />
	cd r8152-2.13.0<br />
	make<br />
	sudo make install<br />
	lsmod | grep r8
</p>

<p>
	 
</p>

<p>
	If this works, and if the module does not load at reboot, add "r8152" in modules.conf: sudo vi /etc/modules-load.d/modules.conf or sudo vi /etc/modules.conf. Not sure which one it is on the Ubuntu running on your XU4.
</p>

<p>
	 
</p>

<p>
	At the lsmod step nothing is showing up. Here is my lsusb -t
</p>

<p>
	 
</p>

<p>
	lsusb -t<br />
	/: Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M<br />
	|__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=r8152, 5000M<br />
	/: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M<br />
	/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M<br />
	|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 5000M<br />
	|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M<br />
	|__ Port 4: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 5000M<br />
	/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 480M<br />
	|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/2p, 480M<br />
	|__ Port 1: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M<br />
	|__ Port 3: Dev 9, If 1, Class=Human Interface Device, Driver=usbhid, 12M<br />
	|__ Port 3: Dev 9, If 2, Class=Human Interface Device, Driver=usbhid, 12M<br />
	|__ Port 3: Dev 9, If 0, Class=Human Interface Device, Driver=usbhid, 12M<br />
	|__ Port 1: Dev 5, If 2, Class=Vendor Specific Class, Driver=btusb, 12M<br />
	|__ Port 1: Dev 5, If 0, Class=Vendor Specific Class, Driver=btusb, 12M<br />
	|__ Port 1: Dev 5, If 3, Class=Application Specific Interface, Driver=, 12M<br />
	|__ Port 1: Dev 5, If 1, Class=Vendor Specific Class, Driver=btusb, 12M<br />
	|__ Port 2: Dev 8, If 2, Class=Human Interface Device, Driver=usbhid, 12M<br />
	|__ Port 2: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M<br />
	|__ Port 2: Dev 8, If 1, Class=Human Interface Device, Driver=usbhid, 12M<br />
	|__ Port 2: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M<br />
	/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=exynos-ohci/3p, 12M<br />
	/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=exynos-ehci/3p, 480M
</p>
]]></description><guid isPermaLink="false">15198</guid><pubDate>Sat, 12 Sep 2020 18:34:51 +0000</pubDate></item><item><title>Odroid XU4 Odroid Game Station Turbo Screen</title><link>https://testforum.armbian.com/topic/15874-odroid-xu4-odroid-game-station-turbo-screen/</link><description><![CDATA[<p>
	Hello I am wondering if there is a way to get the screen that comes with the OGST to work on Armbian?
</p>
]]></description><guid isPermaLink="false">15874</guid><pubDate>Mon, 09 Nov 2020 18:41:27 +0000</pubDate></item><item><title>Samba on HC2 - fluctuating speed</title><link>https://testforum.armbian.com/topic/15755-samba-on-hc2-fluctuating-speed/</link><description><![CDATA[<p>
	Hi, i have odroid HC2 with up-to-date armbian (kernel 4.something - i am not at home, i do not remember its version)
</p>

<p>
	 
</p>

<p>
	I have issues with samba speed - before last minority update it was 115/110 MB/s (read/write) now it is 100/90 with cifs mount in arch linux and 60/60 in Windows 10. Cables, router - everything is untact and still the same
</p>

<p>
	 
</p>

<p>
	cpu governor is on demand, samba is installed over OMV, htop shows max 10%, ram the same
</p>

<p>
	 
</p>

<p>
	where can be the problem?
</p>
]]></description><guid isPermaLink="false">15755</guid><pubDate>Thu, 29 Oct 2020 08:33:49 +0000</pubDate></item><item><title>on Odroid HC2: htop showing only "(       .LITTLE)", for 8 lines</title><link>https://testforum.armbian.com/topic/15592-on-odroid-hc2-htop-showing-only-little-for-8-lines/</link><description><![CDATA[<p>
	Hi!
</p>

<p>
	 
</p>

<p>
	my odroid HC2 is running pretty great on armbian 5.90 for &gt;1,5 years (24/7) now. Running a nextcloud instance, with decent perfomance, even when clocked to 600/1200 Mhz in the summer, because of one (1) crash, that I think might have been heat-related.
</p>

<p>
	 
</p>

<p>
	The thing I'm wondering about: in htop, it shows only (      .LITTLE) cores for eight lines, but the cpu is a (.big.LITTLE) architecture and my other HC2 <abbr title="Single board computer">sbc</abbr>, which runs armbian 20.02.7, show "(.big.LITTLE)" in htop. Perfomance in sysbench is equal on both boards, so this might mean nothing, but it still seemed strange to me.
</p>

<p>
	 
</p>

<p>
	Anyone knows why htop only shows "(     .LITTLE)" cores?
</p>
]]></description><guid isPermaLink="false">15592</guid><pubDate>Fri, 16 Oct 2020 20:27:29 +0000</pubDate></item><item><title>Xu4 will not upgrade to Caple</title><link>https://testforum.armbian.com/topic/15495-xu4-will-not-upgrade-to-caple/</link><description><![CDATA[<p>
	Hi ..
</p>

<p>
	 
</p>

<p>
	I try to upgrade to latest armbian. I run now bionic
</p>

<p>
	Only when i do sudo apt-get-dist-upgrade i get no upgrade options.
</p>

<p>
	I was thinking i need to chage somewhere in setting something with tls.
</p>

<p>
	 
</p>

<p>
	Only...
</p>

<p>
	So i cannot find a wiki or a other good working how to.
</p>

<p>
	 
</p>

<p>
	So please can some help me to get my xu4 update tot latest version..
</p>

<p>
	Or give me a good wiki or a working how to.
</p>

<p>
	 
</p>

<p>
	Thanks!!
</p>
]]></description><guid isPermaLink="false">15495</guid><pubDate>Sun, 11 Oct 2020 08:43:29 +0000</pubDate></item><item><title>Odroid HC1 does not boot with kernel 5.4.6</title><link>https://testforum.armbian.com/topic/12586-odroid-hc1-does-not-boot-with-kernel-546/</link><description><![CDATA[<p>My HC1 after changing from 4.14.157 to 5.4.6 using armbian-config is not able to get up ... zero response, no boot<br>
Does HC1 work with kernel 5 and boot, can anyone confirm?</p>]]></description><guid isPermaLink="false">12586</guid><pubDate>Thu, 02 Jan 2020 10:06:29 +0000</pubDate></item><item><title>Odroid HC-1 died after apt-update/upgrade</title><link>https://testforum.armbian.com/topic/14249-odroid-hc-1-died-after-apt-updateupgrade/</link><description><![CDATA[<p>
	First I have to thank all maintainers for their work. I ran this server for 1.5 years before something broke. Since armbian is maintained by volunteers I want to cheer you up and thank you for your hard work.
</p>

<p>
	 
</p>

<p>
	However just today my little server would die after apt-update/upgrade. I use a SATA drive together with a boot SD-card (only containing /boot). I can observe the following behavior:
</p>

<p>
	 
</p>

<p>
	The system leds indicate that booting is sucessful (blue LED does blink regularly, I can detect HDD usage by observing the green LED), yet SSH login that I have been using for years now is impossible. The device is also not responsive when pinging it. From my router's dashboard I can not detect a sucessful network connection, yet the NIC's orange LED would blink regularly. Sadly I do not own an UART adapter, maybe I should have bought one sooner.
</p>

<p>
	 
</p>

<p>
	What I have already done:
</p>

<p>
	 
</p>

<p>
	Mirror the SD card using dd. I am uploading the file and will post the link here for review. // Upload finished: <a href="https://mega.nz/file/yYJwEIiA#zw4lBfeJ8wXyxS1EeGDpMGERbQquEoxvNaCh2CFwTbg" rel="external nofollow">https://mega.nz/file/yYJwEIiA#zw4lBfeJ8wXyxS1EeGDpMGERbQquEoxvNaCh2CFwTbg</a>
</p>

<p>
	Notice that the focal images seem to be corrupt. I have added focal sources since I needed more modern packages for installing ntopng. Maybe this had something to do with it.
</p>

<p>
	 
</p>

<p>
	I am very glad if someone has some advice, well any advice. I would hate to setup everything again <img alt=";)" data-emoticon="" height="20" src="https://testforum.armbian.com/uploads/emoticons/default_wink.png" srcset="https://testforum.armbian.com/uploads/emoticons/wink@2x.png 2x" title=";)" width="20" loading="lazy"></p>
]]></description><guid isPermaLink="false">14249</guid><pubDate>Tue, 02 Jun 2020 17:17:48 +0000</pubDate></item><item><title>XU4 -- IPv6 -- builtautomatic</title><link>https://testforum.armbian.com/topic/15170-xu4-ipv6-builtautomatic/</link><description><![CDATA[<p>
	Linux 2b8e 4.14.150-odroidxu4 #2 SMP PREEMPT Mon Oct 28 08:07:45 CET 2019 armv7l GNU/Linux
</p>

<p>
	DB 10.5 updates and upgraded
</p>

<p>
	High everybody <span><img alt=":)" data-emoticon="" height="20" src="https://testforum.armbian.com/uploads/emoticons/default_smile.png" srcset="https://testforum.armbian.com/uploads/emoticons/smile@2x.png 2x" title=":)" width="20" loading="lazy"></span>
</p>

<p>
	<span>AAMOE the starting procedure brings very often a new address for local use. As XU4 should be reachable by some other machines automatcally withour searching seconds an seconds I wonder if DHCP6 could help, when</span>
</p>

<p>
	<span>searching takes too much time and they already do have fixed IPv6 adresses and DHCP is disgusting.</span>
</p>

<p>
	<span>So, how the IPv6 ist made in Armbian?</span>
</p>

<p>
	<span>TIA  </span>
</p>
]]></description><guid isPermaLink="false">15170</guid><pubDate>Wed, 09 Sep 2020 07:41:58 +0000</pubDate></item><item><title>Buster images are missing symlik to boot.ini</title><link>https://testforum.armbian.com/topic/14604-buster-images-are-missing-symlik-to-bootini/</link><description><![CDATA[<p>
	My board is Odroid HC1<br>
	Using balenaEtcher under Windows 10 I have instaled today Armbian_20.05.7_Odroidxu4_buster_current_5.4.50_minimal.img.xz and also was trying before Armbian_20.05.7_Odroidxu4_buster_legacy_4.14.187.img.xz.<br>
	On both images I wanted to increase verbosity to 7 to see in serial console boot process. 
</p>

<p>
	Changes in boot.ini are not used during boot until symlink /boot.ini is created which point to /boot/boot.ini
</p>

<p>
	Until this is done you will se uboot error that script /boot.ini is not found.
</p>

<p>
	 
</p>

<p>
	Please add this symlink to images for XU4/HC1.
</p>

<p>
	 
</p>

<p>
	Second issue is that editing armbianEnv.txt is not overwriting values in boot.ini. I have added new line verbosity=7 and it has no effect. Only editing boot.ini is changing boot behaviour.
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">14604</guid><pubDate>Thu, 09 Jul 2020 15:31:22 +0000</pubDate></item><item><title>odroid hc1: connection uart to uart external device pb</title><link>https://testforum.armbian.com/topic/15068-odroid-hc1-connection-uart-to-uart-external-device-pb/</link><description><![CDATA[<p>
	Hi armbian staff and users, i must/try to connect through uart (HC1 /Dev/ttySAC2) to an external uart device.<br>
	1. As uart /dev/ttySAC2 is used by boot/kernel, /sbin/agetty has been renamed to stop its launching / lock rather than rebuild uboot/...<br>
	2. So as powers supply of 2 uart are differents, 2 converters UART/USB are installed on 2 sides<br>
	HC1 &lt;-&gt; UART/USB(CP2102N) &lt;=======&gt; USB/UART(XR21V14xy) &lt;-&gt; device. External PS 5v is connected on USB(vcc:gnd), red light on CP2102N is up.<br>
	I precise 2 points :<br>
	HC1 &lt;-&gt; UART/USB(CP2102N) &lt;=======&gt; laptop=OK<br>
	DEVICE &lt;-&gt; UART/USB(XR21V14xy) &lt;=======&gt; laptop=OK<br>
	Nothing TX/RX, where is the mistake ?<br>
	Any clue are welcome<br>
	Best regards<br>
	Frederic
</p>

<p>
	ps: armbian buster 4.14
</p>
]]></description><guid isPermaLink="false">15068</guid><pubDate>Tue, 01 Sep 2020 06:48:52 +0000</pubDate></item><item><title>odroid hc2 overheating</title><link>https://testforum.armbian.com/topic/14614-odroid-hc2-overheating/</link><description><![CDATA[<p>
	Hi!
</p>

<p>
	 
</p>

<p>
	my nextcloud instance on an odroid hc2 running armbian has been running stable and smoothly for several months now. Thanks Igor and the whole armbian team!
</p>

<p>
	 
</p>

<p>
	I have one question though:
</p>

<p>
	 
</p>

<p>
	<strong>Task:</strong> I convert videos with ffmpeg to reduce file size and optimize them for streaming
</p>

<p>
	 
</p>

<p>
	<strong>observed behaviour: </strong>the<strong> </strong>CPU is getting very hot! In the evening up to 100 °C (see below), but at noon I have seen temperatures of up to 115 °C! I read somewhere that 110 °C is the critical temperature for the board and the stock hardkernel image has an emergency shutdown implemented. But my board running armbian seems to be negligent of this. On a side note, the CPU frequency reported in armbianmonitor -m is 1800/1300, in htop all 8 cores show 1300 ( .LITTLE)?
</p>

<p>
	 
</p>

<p>
	<strong>expected behaviour: </strong>shouldn't the CPU be throttled automatically?
</p>

<p>
	 
</p>

<p>
	excerpts from armbianmonitor -m:<br>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">Stop monitoring using [ctrl]-[c]
Time       big.LITTLE   load %cpu %sys %usr %nice %io %irq   CPU  C.St.

17:56:51: 1800/1300MHz  2.20   2%   0%   0%   1%   0%   0% 84.0°C  2/13
17:56:57: 1800/1300MHz  2.99  93%   0%  17%  75%   0%   0% 87.0°C  2/13
17:57:02: 1800/1300MHz  3.79  93%   0%  18%  74%   0%   0% 89.0°C  2/13
17:57:07: 1800/1300MHz  3.89  82%   0%  13%  68%   0%   0% 84.0°C  2/13
17:57:12: 1800/1300MHz  3.74  80%   0%  18%  60%   0%   0% 85.0°C  2/13

...

17:59:19: 1800/1300MHz  9.83  90%   0%  16%  73%   0%   0% 98.0°C  2/13
17:59:25: 1800/1300MHz 10.38  95%   0%  15%  79%   0%   0% 99.0°C  2/13
Time       big.LITTLE   load %cpu %sys %usr %nice %io %irq   CPU  C.St.
17:59:30: 1800/1300MHz 10.27  94%   1%  22%  70%   0%   0% 100.0°C  2/13
17:59:36: 1800/1300MHz  9.85  90%   0%  16%  72%   0%   0% 99.0°C  2/13
17:59:42: 1800/1300MHz 10.10  95%   0%  17%  77%   0%   0% 100.0°C  2/13
17:59:48: 1800/1300MHz 10.33  98%   0%  18%  79%   0%   0% 102.0°C  2/13
17:59:54: 1800/1300MHz 10.38  95%   0%  22%  71%   0%   0% 101.0°C  2/13
18:00:00: 1800/1300MHz 10.79  97%   1%  20%  75%   0%   0% 100.0°C  2/13</span></pre>

<p>
	 
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">14614</guid><pubDate>Sun, 12 Jul 2020 18:16:01 +0000</pubDate></item><item><title>SSH KEYS not accepted</title><link>https://testforum.armbian.com/topic/14674-ssh-keys-not-accepted/</link><description><![CDATA[<p>
	Hi all,
</p>

<p>
	I am trying to add SSH Keys to an HC1.
</p>

<p>
	The commands I am using are:
</p>

<p>
	<br>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">sudo mkdir ~/.ssh

sudo chmod 700 ~/.ssh

sudo nano ~/.ssh/authorized_keys</span></pre>

<p>
	 
</p>

<p>
	Then I select all the PUBLIC key from PuTTy Gen and copy/paste it on the file above, close and save the file.
</p>

<p>
	 
</p>

<pre class="ipsCode prettyprint lang-html prettyprinted">
<span class="pln">sudo chmod 600 ~/.ssh/authorized_keys

sudo chown -R $(whoami):$(whoami) ~/.ssh/

sudo reboot</span></pre>

<p>
	 
</p>

<p>
	I then try to SSH with PuTTy and SSH keys. Immediately I get an error saying "Server refused our key" and then it asks me for my normal password as a user.
</p>

<p>
	Any idea what I am doing wrong?
</p>

<p>
	 
</p>
]]></description><guid isPermaLink="false">14674</guid><pubDate>Mon, 20 Jul 2020 15:41:23 +0000</pubDate></item><item><title>Odroid HC2 seems doesn't work?</title><link>https://testforum.armbian.com/topic/14607-odroid-hc2-seems-doesnt-work/</link><description><![CDATA[<p>
	I do not use my HC2 for a while. Now I have issue to boot it up. I have download image ubuntu 18.04.3 from official odroid wiki link and during first boot blue led is blinking in heart beat rate forever, I was trying 18.04.1 and first boot run smooth, leds turn off and only red is on, but after reset I can not see my odroid in my network (I used two different cables to check if any is broken). Earlier when I was using it there was no problems.
</p>]]></description><guid isPermaLink="false">14607</guid><pubDate>Fri, 10 Jul 2020 20:44:15 +0000</pubDate></item><item><title>XU4 / HC1,2 Bullseye Server 404 not found</title><link>https://testforum.armbian.com/topic/14562-xu4-hc12-bullseye-server-404-not-found/</link><description><![CDATA[<p>
	<a href="https://dl.armbian.com/odroidxu4/archive/Armbian_20.05.2_Odroidxu4_bullseye_current_5.4.41.img.xz" rel="external nofollow">https://dl.armbian.com/odroidxu4/archive/Armbian_20.05.2_Odroidxu4_bullseye_current_5.4.41.img.xz</a>
</p>

<p>
	 
</p>

<p>
	Third link on XU4 and HC1,2 MC1 download pages are 404 not found.
</p>

<p>
	 
</p>

<p>
	Building an archive for a workshop I'm doing next week and got the 404. No big deal, just wanted to make a note.
</p>
]]></description><guid isPermaLink="false">14562</guid><pubDate>Sat, 04 Jul 2020 18:08:54 +0000</pubDate></item></channel></rss>
