Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

rosbeef

Members
  • Joined

  • Last visited

Everything posted by rosbeef

  1. Damne sorry! i did not have auto follow activted and not seen your message util now. i have not anymore this image but as i read, the new images includes a new uboot with drivers isn't it? so as you said, the new uboot shoud permits me to remove the blob i had to configure. i'm not sure to understand how a uboot upgrade could include something which make the blob not relevant anymore. so i don't know if flashing new uboot with the blob will confict. is someone can resolve this dubt? thks
  2. @usual user@Efe Çetin it seem to work with i burned an sd card with the new compiled Armbian-unofficial_24.8.0-trunk_Orangepi5-plus_bookworm_legacy.5.10.160 image . I boot from the sdcard It seems to work as i have no crash copying a 250GB file between a usb ssd and the mvne. I'm trying now memtester 31G. ... ... trying mlock ...Killed BUT not crash trying memtester 30G is working ... ... and it does not crash. @Efe Çetin Is it possible to make the official release working for the 32Gb version ?
  3. @Eddie as @MichaIng explain me did you add the next in the armbienEnv.txt ?
  4. ok thankyou, that makes debian boot with 12G effectively and big file (250GB tested) coping is fully working. So it discard a hardware power failure. Sorry @Werner Now i have a half working memory. And if i want to get my fully working 32G memory i have to try the @Efe Çetin solution. just let me time to compile the new armbian with those blobs Thanks all.
  5. Hum i saw that my power is 5.1v I removed the mvne and try to cp a big file, it crash too. Maybe the right way to explore is the bad memory managment. I could not reduce visible memory, sorry i'm noob here. I put the mem=12G in the /boot/armbianEnv.txt file then "update-initramfs -u" I tried directly in /boot/boot.cmd on the bootagrs parameter too without success. , i read that too : source https://github.com/linux-sunxi/u-boot-sunxi/issues/11#issuecomment-6358135 maybe there is an other way to shrink the memory or accept the 32G.
  6. i don't have the tools to test the voltages and don't have a precise tunable powersource. as you seems to know about electronic can i ask you ? Is 6V will be too much overvoltage ?
  7. i don't need 32 for now, i jut bought it for the future. Should it be possible to lie on the size of the memory and only declare 16Gb usable ?
  8. More current (5A instead of 4A) did not resolve the problem for me. I tried the vendor distro (debian) and problem is not solved. Writing from SD to emmc makes crash too. even if no usb connected. A simple copy command make debian crash. i will go to orangepi forum 😕 for help.
  9. Damn ! the opi5+ bundle from aliexpress includes a 5V-4A which should be short for a 32G+nvme. I will try a 5V-5A as i am not able to find a 5V-6A on amazon.
  10. Hi ! i am in this situation: Orangepi 5plus 32gb ram , uboot on spi and root on nvme i experiment the crash on Armbian 24.5.1 Bookworm with Linux 5.10.160-legacy-rk35xx and 6.1.43-vendor-rk35xx and 6.8.10-edge-rk3588 too I would help you to resolve my bug but could you help me to send you all you could need. i recover some datas from the serial 409.837122] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 409.837821] CPU: 3 PID: 1 Comm: systemd Not tainted 6.8.11-edge-rockchip-rk3588 #1 [ 409.838494] Hardware name: Xunlong Orange Pi 5 Plus (DT) [ 409.838967] Call trace: [ 409.839191] dump_backtrace+0x94/0x114 [ 409.839538] show_stack+0x18/0x24 [ 409.839840] dump_stack_lvl+0x38/0xf0 [ 409.840173] dump_stack+0x18/0x24 [ 409.840473] panic+0x3b8/0x3f8 [ 409.840754] do_exit+0x898/0x9bc [ 409.841050] do_group_exit+0x34/0x90 [ 409.841376] copy_siginfo_to_user+0x0/0xc8 [ 409.841746] do_notify_resume+0x27c/0x1430 [ 409.842114] el0_da+0x8c/0x90 [ 409.842387] el0t_64_sync_handler+0xe4/0x158 [ 409.842772] el0t_64_sync+0x1a4/0x1a8 [ 409.843104] SMP: stopping secondary CPUs [ 409.843559] Kernel Offset: disabled [ 409.843871] CPU features: 0x0,c0000000,7002814a,2100720b [ 409.844345] Memory Limit: none [ 409.844629] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]--- other dump 279.842385] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP [ 279.842949] Modules linked in: macvlan nft_masq bridge snd_seq_dummy rfcomm snd_seq snd_seq_device nft_fib_inet nft_fib_ipv4 nft_fib_ipvb [ 279.843297] libarc4 gpu_sched drm_shmem_helper drm_exec rfkill_gpio rfkill dm_mod ip_tables x_tables autofs4 uas rockchipdrm drm_dma_hes [ 279.853805] CPU: 2 PID: 190 Comm: kworker/2:1 Not tainted 6.8.11-edge-rockchip-rk3588 #1 [ 279.854522] Hardware name: Xunlong Orange Pi 5 Plus (DT) [ 279.854995] Workqueue: events kernfs_notify_workfn [ 279.855439] pstate: a0400009 (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 279.856057] pc : find_inode_fast+0x38/0xe4 [ 279.856430] lr : ilookup+0x8c/0x118 [ 279.856747] sp : ffff80008353bca0 [ 279.857044] x29: ffff80008353bca0 x28: 0000000000000000 x27: ffff800081f57980 [ 279.857686] x26: ffff800081d5e000 x25: ffff00010048ebb0 x24: ffff800081172078 [ 279.858327] x23: ffff0001008a5800 x22: ffff0007d9300c00 x21: ffff0001008a5800 [ 279.858968] x20: 00000000000027c8 x19: 90d48fefa3653def x18: ffff80008c523c58 [ 279.859609] x17: 0000000000000000 x16: 1fffe0002046dc41 x15: 00000000000002e9 [ 279.860249] x14: 0000000000000000 x13: 0000000000000030 x12: 0101010101010101 [ 279.860889] x11: 7f7f7f7f7f7f7f7f x10: fefefefefefefeff x9 : 7f7f7f7f7f7f7f7f [ 279.861530] x8 : 8080808080808080 x7 : ffff00010048ebb0 x6 : ffff000100aa7380 [ 279.862170] x5 : d83827dd7f7cc000 x4 : 0000000000000015 x3 : d9bf05c4657e16ae [ 279.862810] x2 : 00000000000027c8 x1 : ffff0007d9300c00 x0 : ffff0001008a5800 [ 279.863451] Call trace: [ 279.863675] find_inode_fast+0x38/0xe4 [ 279.864016] ilookup+0x8c/0x118 [ 279.864303] kernfs_notify_workfn+0x12c/0x220 [ 279.864698] process_one_work+0x160/0x3a8 [ 279.865064] worker_thread+0x32c/0x438 [ 279.865404] kthread+0x118/0x11c [ 279.865701] ret_from_fork+0x10/0x20 [ 279.866030] Code: aa0003f5 f9001bf7 d503201f 54000140 (f9402263) [ 279.866441] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b [ 279.866448] SMP: stopping secondary CPUs [ 279.866573] ---[ end trace 0000000000000000 ]--- [ 279.866610] Kernel Offset: disabled [ 279.868331] CPU features: 0x0,c0000000,7002814a,2100720b [ 279.868799] Memory Limit: none [ 279.869076] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b ]---

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.