Debian/Ubuntu Netboot Installer (Feat. Ubuntu Gnome Desktop with Wayland)

[tobetter]

Is there anyone else who has an issue to start Ubuntu Gnome Desktop after new keren 5.10.4 is installed?

[specs]

I found this in my logfile (After downgrading to the 5.10.2 kernel (needless to say wayland did not start):

Code: Select all

Jan  3 19:49:33 n2std kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Jan  3 19:49:33 n2std kernel: [    0.000000] Linux version 5.10.0-odroid-arm64 (tobetter@gmail.com) (gcc-9 (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP PREEMPT Ubuntu 5.10.4-202012311803~focal (2020-12-31)
Jan  3 19:49:33 n2std kernel: [    0.000000] Machine model: Hardkernel ODROID-N2
...
Jan  3 19:49:41 n2std systemd[2008]: Starting Tracker metadata database store and lookup manager...
Jan  3 19:49:41 n2std systemd[2008]: Started Tracker file system data miner.
Jan  3 19:49:41 n2std systemd[2008]: Reached target Main User Target.
Jan  3 19:49:41 n2std kernel: [   18.231979] Unable to handle kernel paging request at virtual address ffff8002d1198dc0
Jan  3 19:49:41 n2std kernel: [   18.231991] Mem abort info:
Jan  3 19:49:41 n2std kernel: [   18.231994]   ESR = 0x96000005
Jan  3 19:49:41 n2std kernel: [   18.231997]   EC = 0x25: DABT (current EL), IL = 32 bits
Jan  3 19:49:41 n2std kernel: [   18.232001]   SET = 0, FnV = 0
Jan  3 19:49:41 n2std kernel: [   18.232004]   EA = 0, S1PTW = 0
Jan  3 19:49:41 n2std kernel: [   18.232006] Data abort info:
Jan  3 19:49:41 n2std kernel: [   18.232009]   ISV = 0, ISS = 0x00000005
Jan  3 19:49:41 n2std kernel: [   18.232011]   CM = 0, WnR = 0
Jan  3 19:49:41 n2std kernel: [   18.232014] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000014d7000
Jan  3 19:49:41 n2std kernel: [   18.232017] [ffff8002d1198dc0] pgd=00000000bb7ff003, p4d=00000000bb7ff003, pud=0000000000000000
Jan  3 19:49:41 n2std kernel: [   18.232026] Internal error: Oops: 96000005 [#1] PREEMPT SMP
Jan  3 19:49:41 n2std kernel: [   18.232030] Modules linked in: fuse cpufreq_conservative cpufreq_powersave cifs fscache sr_mod cdrom sg rfkill snd_soc_hdmi_codec dw_hdmi_i2s_audio snd_soc_meson_g12a_tohdmitx ir_nec_decoder mali_kbase(O) snd_soc_meson_g12a_toacodec snd_soc_meson_axg_sound_card snd_soc_meson_card_utils meson_dw_hdmi meson_rng rng_core meson_vdec(C) snd_soc_meson_codec_glue dw_hdmi meson_drm v4l2_mem2mem snd_soc_meson_axg_tdmout snd_soc_meson_axg_toddr videobuf2_dma_contig snd_soc_meson_axg_frddr videobuf2_v4l2 reset_meson_audio_arb videobuf2_memops videobuf2_common snd_soc_meson_axg_tdmin snd_soc_meson_axg_spdifout snd_soc_meson_axg_fifo videodev snd_soc_meson_t9015 mc meson_ir meson_canvas snd_soc_meson_axg_tdm_interface pwm_fan snd_soc_meson_axg_tdm_formatter snd_soc_simple_amplifier snd_soc_spdif_tx sch_fq_codel ip_tables x_tables rtc_pcf8563 axg_audio sclk_div clk_phase meson_gxl realtek
Jan  3 19:49:41 n2std kernel: [   18.232112] CPU: 4 PID: 2180 Comm: gnome-shell Tainted: G         C O      5.10.0-odroid-arm64 #1 Ubuntu 5.10.4-202012311803~focal
Jan  3 19:49:41 n2std kernel: [   18.232115] Hardware name: Hardkernel ODROID-N2 (DT)
Jan  3 19:49:41 n2std kernel: [   18.232120] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)
Jan  3 19:49:41 n2std kernel: [   18.232129] pc : osq_lock+0x74/0x1e8
Jan  3 19:49:41 n2std kernel: [   18.232133] lr : rwsem_optimistic_spin+0x48/0x298
Jan  3 19:49:41 n2std kernel: [   18.232136] sp : ffff800012ca3b60
Jan  3 19:49:41 n2std kernel: [   18.232139] x29: ffff800012ca3b60 x28: ffff00004088d338 
Jan  3 19:49:41 n2std kernel: [   18.232144] x27: 0000000000000000 x26: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232148] x25: 0000000000000000 x24: ffff00004088d328 
Jan  3 19:49:41 n2std kernel: [   18.232152] x23: 0000000000000001 x22: 0000000000000004 
Jan  3 19:49:41 n2std kernel: [   18.232156] x21: ffff000057f30e80 x20: 0000000000000001 
Jan  3 19:49:41 n2std kernel: [   18.232160] x19: 0000000000000002 x18: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232164] x17: 0000000000000000 x16: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232168] x15: 0000000000000000 x14: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232172] x13: 0000000000000000 x12: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232176] x11: 0000000000000000 x10: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232180] x9 : ffff8000115aa000 x8 : 0000000000000002 
Jan  3 19:49:41 n2std kernel: [   18.232184] x7 : ffff000057f30e80 x6 : ffff00004088d338 
Jan  3 19:49:41 n2std kernel: [   18.232187] x5 : 0000000000000000 x4 : 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232191] x3 : ffff0000b6fdf340 x2 : 0000000057f30e80 
Jan  3 19:49:41 n2std kernel: [   18.232195] x1 : ffff8000115b7340 x0 : ffff8000118119c0 
Jan  3 19:49:41 n2std kernel: [   18.232200] Call trace:
Jan  3 19:49:41 n2std kernel: [   18.232203]  osq_lock+0x74/0x1e8
Jan  3 19:49:41 n2std kernel: [   18.232206]  rwsem_optimistic_spin+0x48/0x298
Jan  3 19:49:41 n2std kernel: [   18.232210]  rwsem_down_write_slowpath+0xc0/0x690
Jan  3 19:49:41 n2std kernel: [   18.232216]  down_write+0x58/0x68
Jan  3 19:49:41 n2std kernel: [   18.232256]  kbase_mem_commit+0x38/0x210 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232284]  kbase_ioctl+0xa14/0x1840 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232290]  __arm64_sys_ioctl+0xa8/0xf0
Jan  3 19:49:41 n2std kernel: [   18.232295]  el0_svc_common.constprop.0+0x78/0x1a0
Jan  3 19:49:41 n2std kernel: [   18.232299]  do_el0_svc+0x24/0x90
Jan  3 19:49:41 n2std kernel: [   18.232302]  el0_svc+0x14/0x20
Jan  3 19:49:41 n2std kernel: [   18.232305]  el0_sync_handler+0xb0/0xb8
Jan  3 19:49:41 n2std kernel: [   18.232308]  el0_sync+0x174/0x180
Jan  3 19:49:41 n2std kernel: [   18.232313] Code: 340009c2 51000442 9000ba00 91270000 (f862d800) 
Jan  3 19:49:41 n2std kernel: [   18.232318] ---[ end trace 2cd9d4cd43529d36 ]---
Jan  3 19:49:41 n2std kernel: [   18.232322] note: gnome-shell[2180] exited with preempt_count 1
Jan  3 19:49:42 n2std systemd[2008]: Started Tracker metadata database store and lookup manager.
...
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.service: Main process exited, code=killed, status=11/SEGV
Jan  3 19:51:16 n2std kernel: [  113.454606] detected fb_set_par error, error code: -16
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.service: Failed with result 'timeout'.
Jan  3 19:51:16 n2std systemd[2008]: Failed to start GNOME Shell on Wayland.Jan  3 19:49:41 n2std kernel: [   18.232180] x9 : ffff8000115aa000 x8 : 0000000000000002 
Jan  3 19:49:41 n2std kernel: [   18.232184] x7 : ffff000057f30e80 x6 : ffff00004088d338 
Jan  3 19:49:41 n2std kernel: [   18.232187] x5 : 0000000000000000 x4 : 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232191] x3 : ffff0000b6fdf340 x2 : 0000000057f30e80 
Jan  3 19:49:41 n2std kernel: [   18.232195] x1 : ffff8000115b7340 x0 : ffff8000118119c0 
Jan  3 19:49:41 n2std kernel: [   18.232200] Call trace:
Jan  3 19:49:41 n2std kernel: [   18.232203]  osq_lock+0x74/0x1e8
Jan  3 19:49:41 n2std kernel: [   18.232206]  rwsem_optimistic_spin+0x48/0x298
Jan  3 19:49:41 n2std kernel: [   18.232210]  rwsem_down_write_slowpath+0xc0/0x690
Jan  3 19:49:41 n2std kernel: [   18.232216]  down_write+0x58/0x68
Jan  3 19:49:41 n2std kernel: [   18.232256]  kbase_mem_commit+0x38/0x210 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232284]  kbase_ioctl+0xa14/0x1840 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232290]  __arm64_sys_ioctl+0xa8/0xf0
Jan  3 19:49:41 n2std kernel: [   18.232295]  el0_svc_common.constprop.0+0x78/0x1a0
Jan  3 19:49:41 n2std kernel: [   18.232299]  do_el0_svc+0x24/0x90
Jan  3 19:49:41 n2std kernel: [   18.232302]  el0_svc+0x14/0x20
Jan  3 19:49:41 n2std kernel: [   18.232305]  el0_sync_handler+0xb0/0xb8
Jan  3 19:49:41 n2std kernel: [   18.232308]  el0_sync+0x174/0x180
Jan  3 19:49:41 n2std kernel: [   18.232313] Code: 340009c2 51000442 9000ba00 91270000 (f862d800) 
Jan  3 19:49:41 n2std kernel: [   18.232318] ---[ end trace 2cd9d4cd43529d36 ]---
Jan  3 19:49:41 n2std kernel: [   18.232322] note: gnome-shell[2180] exited with preempt_count 1
Jan  3 19:49:42 n2std systemd[2008]: Started Tracker metadata database store and lookup manager.

Jan  3 19:51:16 n2std systemd[2008]: Dependency failed for GNOME Shell on Wayland.
Jan  3 19:51:16 n2std systemd[2008]: Dependency failed for GNOME Wayland Session.
Jan  3 19:51:16 n2std systemd[2008]: Dependency failed for GNOME Wayland Session (session: ubuntu).
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-wayland@ubuntu.target: Job gnome-session-wayland@ubuntu.target/start failed with result 'dependency'.
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'.
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'.
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.service: Triggering OnFailure= dependencies.
Jan  3 19:51:16 n2std systemd[2008]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
Jan  3 19:51:16 n2std systemd[2008]: Stopped target GNOME Session Manager is ready.
Jan  3 19:51:16 n2std systemd[2008]: Stopping GNOME Session Manager (session: ubuntu)...
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-manager@ubuntu.service: Succeeded.
Jan  3 19:51:16 n2std systemd[2008]: Stopped GNOME Session Manager (session: ubuntu).
Jan  3 19:51:16 n2std systemd[2008]: Stopped target Tasks to be run before GNOME Session starts.
Jan  3 19:51:16 n2std systemd[2008]: Stopped target Session services which should run early before the graphical session is brought up.
Jan  3 19:51:16 n2std systemd[2008]: Reached target Shutdown running GNOME Session.
Jan  3 19:51:16 n2std systemd[2008]: Stopping Start gnome-keyring as SSH agent...
Jan  3 19:51:16 n2std systemd[2008]: Stopping Monitor Session leader for GNOME Session...
Jan  3 19:51:16 n2std systemd[2008]: Starting Restart DBus after GNOME Session shutdown...
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-monitor.service: Succeeded.
Jan  3 19:51:16 n2std systemd[2008]: Stopped Monitor Session leader for GNOME Session.
Jan  3 19:51:16 n2std systemd[2008]: Started Restart DBus after GNOME Session shutdown.

I shortened it a bit, but I think I got most of the keypoints included.
(Hope this helps, if not, just ask for more.)

[tobetter]

I found this in my logfile (After downgrading to the 5.10.2 kernel (needless to say wayland did not start):

Code: Select all

Jan  3 19:49:33 n2std kernel: [    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
Jan  3 19:49:33 n2std kernel: [    0.000000] Linux version 5.10.0-odroid-arm64 (tobetter@gmail.com) (gcc-9 (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP PREEMPT Ubuntu 5.10.4-202012311803~focal (2020-12-31)
Jan  3 19:49:33 n2std kernel: [    0.000000] Machine model: Hardkernel ODROID-N2
...
Jan  3 19:49:41 n2std systemd[2008]: Starting Tracker metadata database store and lookup manager...
Jan  3 19:49:41 n2std systemd[2008]: Started Tracker file system data miner.
Jan  3 19:49:41 n2std systemd[2008]: Reached target Main User Target.
Jan  3 19:49:41 n2std kernel: [   18.231979] Unable to handle kernel paging request at virtual address ffff8002d1198dc0
Jan  3 19:49:41 n2std kernel: [   18.231991] Mem abort info:
Jan  3 19:49:41 n2std kernel: [   18.231994]   ESR = 0x96000005
Jan  3 19:49:41 n2std kernel: [   18.231997]   EC = 0x25: DABT (current EL), IL = 32 bits
Jan  3 19:49:41 n2std kernel: [   18.232001]   SET = 0, FnV = 0
Jan  3 19:49:41 n2std kernel: [   18.232004]   EA = 0, S1PTW = 0
Jan  3 19:49:41 n2std kernel: [   18.232006] Data abort info:
Jan  3 19:49:41 n2std kernel: [   18.232009]   ISV = 0, ISS = 0x00000005
Jan  3 19:49:41 n2std kernel: [   18.232011]   CM = 0, WnR = 0
Jan  3 19:49:41 n2std kernel: [   18.232014] swapper pgtable: 4k pages, 48-bit VAs, pgdp=00000000014d7000
Jan  3 19:49:41 n2std kernel: [   18.232017] [ffff8002d1198dc0] pgd=00000000bb7ff003, p4d=00000000bb7ff003, pud=0000000000000000
Jan  3 19:49:41 n2std kernel: [   18.232026] Internal error: Oops: 96000005 [#1] PREEMPT SMP
Jan  3 19:49:41 n2std kernel: [   18.232030] Modules linked in: fuse cpufreq_conservative cpufreq_powersave cifs fscache sr_mod cdrom sg rfkill snd_soc_hdmi_codec dw_hdmi_i2s_audio snd_soc_meson_g12a_tohdmitx ir_nec_decoder mali_kbase(O) snd_soc_meson_g12a_toacodec snd_soc_meson_axg_sound_card snd_soc_meson_card_utils meson_dw_hdmi meson_rng rng_core meson_vdec(C) snd_soc_meson_codec_glue dw_hdmi meson_drm v4l2_mem2mem snd_soc_meson_axg_tdmout snd_soc_meson_axg_toddr videobuf2_dma_contig snd_soc_meson_axg_frddr videobuf2_v4l2 reset_meson_audio_arb videobuf2_memops videobuf2_common snd_soc_meson_axg_tdmin snd_soc_meson_axg_spdifout snd_soc_meson_axg_fifo videodev snd_soc_meson_t9015 mc meson_ir meson_canvas snd_soc_meson_axg_tdm_interface pwm_fan snd_soc_meson_axg_tdm_formatter snd_soc_simple_amplifier snd_soc_spdif_tx sch_fq_codel ip_tables x_tables rtc_pcf8563 axg_audio sclk_div clk_phase meson_gxl realtek
Jan  3 19:49:41 n2std kernel: [   18.232112] CPU: 4 PID: 2180 Comm: gnome-shell Tainted: G         C O      5.10.0-odroid-arm64 #1 Ubuntu 5.10.4-202012311803~focal
Jan  3 19:49:41 n2std kernel: [   18.232115] Hardware name: Hardkernel ODROID-N2 (DT)
Jan  3 19:49:41 n2std kernel: [   18.232120] pstate: 00000005 (nzcv daif -PAN -UAO -TCO BTYPE=--)
Jan  3 19:49:41 n2std kernel: [   18.232129] pc : osq_lock+0x74/0x1e8
Jan  3 19:49:41 n2std kernel: [   18.232133] lr : rwsem_optimistic_spin+0x48/0x298
Jan  3 19:49:41 n2std kernel: [   18.232136] sp : ffff800012ca3b60
Jan  3 19:49:41 n2std kernel: [   18.232139] x29: ffff800012ca3b60 x28: ffff00004088d338 
Jan  3 19:49:41 n2std kernel: [   18.232144] x27: 0000000000000000 x26: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232148] x25: 0000000000000000 x24: ffff00004088d328 
Jan  3 19:49:41 n2std kernel: [   18.232152] x23: 0000000000000001 x22: 0000000000000004 
Jan  3 19:49:41 n2std kernel: [   18.232156] x21: ffff000057f30e80 x20: 0000000000000001 
Jan  3 19:49:41 n2std kernel: [   18.232160] x19: 0000000000000002 x18: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232164] x17: 0000000000000000 x16: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232168] x15: 0000000000000000 x14: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232172] x13: 0000000000000000 x12: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232176] x11: 0000000000000000 x10: 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232180] x9 : ffff8000115aa000 x8 : 0000000000000002 
Jan  3 19:49:41 n2std kernel: [   18.232184] x7 : ffff000057f30e80 x6 : ffff00004088d338 
Jan  3 19:49:41 n2std kernel: [   18.232187] x5 : 0000000000000000 x4 : 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232191] x3 : ffff0000b6fdf340 x2 : 0000000057f30e80 
Jan  3 19:49:41 n2std kernel: [   18.232195] x1 : ffff8000115b7340 x0 : ffff8000118119c0 
Jan  3 19:49:41 n2std kernel: [   18.232200] Call trace:
Jan  3 19:49:41 n2std kernel: [   18.232203]  osq_lock+0x74/0x1e8
Jan  3 19:49:41 n2std kernel: [   18.232206]  rwsem_optimistic_spin+0x48/0x298
Jan  3 19:49:41 n2std kernel: [   18.232210]  rwsem_down_write_slowpath+0xc0/0x690
Jan  3 19:49:41 n2std kernel: [   18.232216]  down_write+0x58/0x68
Jan  3 19:49:41 n2std kernel: [   18.232256]  kbase_mem_commit+0x38/0x210 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232284]  kbase_ioctl+0xa14/0x1840 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232290]  __arm64_sys_ioctl+0xa8/0xf0
Jan  3 19:49:41 n2std kernel: [   18.232295]  el0_svc_common.constprop.0+0x78/0x1a0
Jan  3 19:49:41 n2std kernel: [   18.232299]  do_el0_svc+0x24/0x90
Jan  3 19:49:41 n2std kernel: [   18.232302]  el0_svc+0x14/0x20
Jan  3 19:49:41 n2std kernel: [   18.232305]  el0_sync_handler+0xb0/0xb8
Jan  3 19:49:41 n2std kernel: [   18.232308]  el0_sync+0x174/0x180
Jan  3 19:49:41 n2std kernel: [   18.232313] Code: 340009c2 51000442 9000ba00 91270000 (f862d800) 
Jan  3 19:49:41 n2std kernel: [   18.232318] ---[ end trace 2cd9d4cd43529d36 ]---
Jan  3 19:49:41 n2std kernel: [   18.232322] note: gnome-shell[2180] exited with preempt_count 1
Jan  3 19:49:42 n2std systemd[2008]: Started Tracker metadata database store and lookup manager.
...
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.service: Main process exited, code=killed, status=11/SEGV
Jan  3 19:51:16 n2std kernel: [  113.454606] detected fb_set_par error, error code: -16
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.service: Failed with result 'timeout'.
Jan  3 19:51:16 n2std systemd[2008]: Failed to start GNOME Shell on Wayland.Jan  3 19:49:41 n2std kernel: [   18.232180] x9 : ffff8000115aa000 x8 : 0000000000000002 
Jan  3 19:49:41 n2std kernel: [   18.232184] x7 : ffff000057f30e80 x6 : ffff00004088d338 
Jan  3 19:49:41 n2std kernel: [   18.232187] x5 : 0000000000000000 x4 : 0000000000000000 
Jan  3 19:49:41 n2std kernel: [   18.232191] x3 : ffff0000b6fdf340 x2 : 0000000057f30e80 
Jan  3 19:49:41 n2std kernel: [   18.232195] x1 : ffff8000115b7340 x0 : ffff8000118119c0 
Jan  3 19:49:41 n2std kernel: [   18.232200] Call trace:
Jan  3 19:49:41 n2std kernel: [   18.232203]  osq_lock+0x74/0x1e8
Jan  3 19:49:41 n2std kernel: [   18.232206]  rwsem_optimistic_spin+0x48/0x298
Jan  3 19:49:41 n2std kernel: [   18.232210]  rwsem_down_write_slowpath+0xc0/0x690
Jan  3 19:49:41 n2std kernel: [   18.232216]  down_write+0x58/0x68
Jan  3 19:49:41 n2std kernel: [   18.232256]  kbase_mem_commit+0x38/0x210 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232284]  kbase_ioctl+0xa14/0x1840 [mali_kbase]
Jan  3 19:49:41 n2std kernel: [   18.232290]  __arm64_sys_ioctl+0xa8/0xf0
Jan  3 19:49:41 n2std kernel: [   18.232295]  el0_svc_common.constprop.0+0x78/0x1a0
Jan  3 19:49:41 n2std kernel: [   18.232299]  do_el0_svc+0x24/0x90
Jan  3 19:49:41 n2std kernel: [   18.232302]  el0_svc+0x14/0x20
Jan  3 19:49:41 n2std kernel: [   18.232305]  el0_sync_handler+0xb0/0xb8
Jan  3 19:49:41 n2std kernel: [   18.232308]  el0_sync+0x174/0x180
Jan  3 19:49:41 n2std kernel: [   18.232313] Code: 340009c2 51000442 9000ba00 91270000 (f862d800) 
Jan  3 19:49:41 n2std kernel: [   18.232318] ---[ end trace 2cd9d4cd43529d36 ]---
Jan  3 19:49:41 n2std kernel: [   18.232322] note: gnome-shell[2180] exited with preempt_count 1
Jan  3 19:49:42 n2std systemd[2008]: Started Tracker metadata database store and lookup manager.

Jan  3 19:51:16 n2std systemd[2008]: Dependency failed for GNOME Shell on Wayland.
Jan  3 19:51:16 n2std systemd[2008]: Dependency failed for GNOME Wayland Session.
Jan  3 19:51:16 n2std systemd[2008]: Dependency failed for GNOME Wayland Session (session: ubuntu).
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-wayland@ubuntu.target: Job gnome-session-wayland@ubuntu.target/start failed with result 'dependency'.
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-wayland.target: Job gnome-session-wayland.target/start failed with result 'dependency'.
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.target: Job gnome-shell-wayland.target/start failed with result 'dependency'.
Jan  3 19:51:16 n2std systemd[2008]: gnome-shell-wayland.service: Triggering OnFailure= dependencies.
Jan  3 19:51:16 n2std systemd[2008]: Condition check resulted in Disable GNOME Shell extensions after failure being skipped.
Jan  3 19:51:16 n2std systemd[2008]: Stopped target GNOME Session Manager is ready.
Jan  3 19:51:16 n2std systemd[2008]: Stopping GNOME Session Manager (session: ubuntu)...
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-manager@ubuntu.service: Succeeded.
Jan  3 19:51:16 n2std systemd[2008]: Stopped GNOME Session Manager (session: ubuntu).
Jan  3 19:51:16 n2std systemd[2008]: Stopped target Tasks to be run before GNOME Session starts.
Jan  3 19:51:16 n2std systemd[2008]: Stopped target Session services which should run early before the graphical session is brought up.
Jan  3 19:51:16 n2std systemd[2008]: Reached target Shutdown running GNOME Session.
Jan  3 19:51:16 n2std systemd[2008]: Stopping Start gnome-keyring as SSH agent...
Jan  3 19:51:16 n2std systemd[2008]: Stopping Monitor Session leader for GNOME Session...
Jan  3 19:51:16 n2std systemd[2008]: Starting Restart DBus after GNOME Session shutdown...
Jan  3 19:51:16 n2std systemd[2008]: gnome-session-monitor.service: Succeeded.
Jan  3 19:51:16 n2std systemd[2008]: Stopped Monitor Session leader for GNOME Session.
Jan  3 19:51:16 n2std systemd[2008]: Started Restart DBus after GNOME Session shutdown.

Can you check if panfrost driver is loaded with the command lsmod | grep panfrost?

[specs]

I can not do that since I uninstalled the kernel.

But I see no panfrost mentioned in the "Modules linked in" rule:
Jan 3 19:49:41 n2std kernel: [ 18.232030] Modules linked in: fuse cpufreq_conservative cpufreq_powersave cifs fscache sr_mod cdrom sg rfkill snd_soc_hdmi_codec dw_hdmi_i2s_audio snd_soc_meson_g12a_tohdmitx ir_nec_decoder mali_kbase(O) snd_soc_meson_g12a_toacodec snd_soc_meson_axg_sound_card snd_soc_meson_card_utils meson_dw_hdmi meson_rng rng_core meson_vdec(C) snd_soc_meson_codec_glue dw_hdmi meson_drm v4l2_mem2mem snd_soc_meson_axg_tdmout snd_soc_meson_axg_toddr videobuf2_dma_contig snd_soc_meson_axg_frddr videobuf2_v4l2 reset_meson_audio_arb videobuf2_memops videobuf2_common snd_soc_meson_axg_tdmin snd_soc_meson_axg_spdifout snd_soc_meson_axg_fifo videodev snd_soc_meson_t9015 mc meson_ir meson_canvas snd_soc_meson_axg_tdm_interface pwm_fan snd_soc_meson_axg_tdm_formatter snd_soc_simple_amplifier snd_soc_spdif_tx sch_fq_codel ip_tables x_tables rtc_pcf8563 axg_audio sclk_div clk_phase meson_gxl realtek

Update: I checked the current (downgraded) 5.10.2-kernel. It also has no panfrost.
(Instead of "lsmod | grep panfrost" you get the whole shebang, since the asked command yields no output.)

Code: Select all

root@n2std:~# cat /proc/version 
Linux version 5.10.0-odroid-arm64 (tobetter@gmail.com) (gcc-9 (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP PREEMPT Ubuntu 5.10.0-202012161718~focal (2020-12-16)
root@n2std:~# lsmod 
Module                  Size  Used by
fuse                  126976  3
cpufreq_conservative    16384  0
cpufreq_powersave      20480  0
cifs                  516096  4
fscache               344064  1 cifs
sr_mod                 32768  1
cdrom                  73728  1 sr_mod
sg                     49152  0
rfkill                 36864  3
snd_soc_hdmi_codec     20480  1
dw_hdmi_i2s_audio      16384  0
mali_kbase            548864  4
snd_soc_meson_axg_sound_card    16384  0
meson_vdec             77824  0
snd_soc_meson_card_utils    16384  1 snd_soc_meson_axg_sound_card
ir_nec_decoder         20480  0
v4l2_mem2mem           40960  1 meson_vdec
videobuf2_dma_contig    24576  1 meson_vdec
videobuf2_v4l2         32768  2 meson_vdec,v4l2_mem2mem
snd_soc_meson_g12a_toacodec    16384  1
videobuf2_memops       20480  1 videobuf2_dma_contig
snd_soc_meson_g12a_tohdmitx    20480  1
videobuf2_common       61440  3 meson_vdec,videobuf2_v4l2,v4l2_mem2mem
meson_dw_hdmi          24576  0
meson_ir               16384  0
videodev              278528  4 meson_vdec,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
snd_soc_meson_codec_glue    16384  2 snd_soc_meson_g12a_toacodec,snd_soc_meson_g12a_tohdmitx
meson_drm              61440  4 meson_dw_hdmi
mc                     61440  4 videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
meson_rng              16384  0
rng_core               24576  1 meson_rng
snd_soc_meson_axg_spdifout    16384  1
reset_meson_audio_arb    16384  6
dw_hdmi                53248  2 meson_dw_hdmi,dw_hdmi_i2s_audio
snd_soc_meson_axg_tdmout    24576  2
meson_canvas           16384  2 meson_drm,meson_vdec
snd_soc_meson_axg_tdmin    24576  0
snd_soc_meson_axg_frddr    36864  3
snd_soc_meson_axg_toddr    28672  0
snd_soc_meson_axg_fifo    20480  2 snd_soc_meson_axg_toddr,snd_soc_meson_axg_frddr
snd_soc_meson_t9015    24576  1
pwm_fan                20480  0
snd_soc_meson_axg_tdm_interface    16384  3 snd_soc_meson_axg_sound_card
snd_soc_meson_axg_tdm_formatter    16384  3 snd_soc_meson_axg_tdmin,snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout
snd_soc_spdif_tx       16384  1
snd_soc_simple_amplifier    16384  1
sch_fq_codel           20480  2
ip_tables              32768  0
x_tables               45056  1 ip_tables
rtc_pcf8563            24576  0
axg_audio              77824  51
sclk_div               16384  1 axg_audio
clk_phase              16384  1 axg_audio
meson_gxl              20480  0
realtek                24576  1

I hope this helps you locate the problem.

[tobetter]

I can not do that since I uninstalled the kernel.

But I see no panfrost mentioned in the "Modules linked in" rule:
Jan 3 19:49:41 n2std kernel: [ 18.232030] Modules linked in: fuse cpufreq_conservative cpufreq_powersave cifs fscache sr_mod cdrom sg rfkill snd_soc_hdmi_codec dw_hdmi_i2s_audio snd_soc_meson_g12a_tohdmitx ir_nec_decoder mali_kbase(O) snd_soc_meson_g12a_toacodec snd_soc_meson_axg_sound_card snd_soc_meson_card_utils meson_dw_hdmi meson_rng rng_core meson_vdec(C) snd_soc_meson_codec_glue dw_hdmi meson_drm v4l2_mem2mem snd_soc_meson_axg_tdmout snd_soc_meson_axg_toddr videobuf2_dma_contig snd_soc_meson_axg_frddr videobuf2_v4l2 reset_meson_audio_arb videobuf2_memops videobuf2_common snd_soc_meson_axg_tdmin snd_soc_meson_axg_spdifout snd_soc_meson_axg_fifo videodev snd_soc_meson_t9015 mc meson_ir meson_canvas snd_soc_meson_axg_tdm_interface pwm_fan snd_soc_meson_axg_tdm_formatter snd_soc_simple_amplifier snd_soc_spdif_tx sch_fq_codel ip_tables x_tables rtc_pcf8563 axg_audio sclk_div clk_phase meson_gxl realtek

Update: I checked the current (downgraded) 5.10.2-kernel. It also has no panfrost.
(Instead of "lsmod | grep panfrost" you get the whole shebang, since the asked command yields no output.)

Code: Select all

root@n2std:~# cat /proc/version 
Linux version 5.10.0-odroid-arm64 (tobetter@gmail.com) (gcc-9 (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1 SMP PREEMPT Ubuntu 5.10.0-202012161718~focal (2020-12-16)
root@n2std:~# lsmod 
Module                  Size  Used by
fuse                  126976  3
cpufreq_conservative    16384  0
cpufreq_powersave      20480  0
cifs                  516096  4
fscache               344064  1 cifs
sr_mod                 32768  1
cdrom                  73728  1 sr_mod
sg                     49152  0
rfkill                 36864  3
snd_soc_hdmi_codec     20480  1
dw_hdmi_i2s_audio      16384  0
mali_kbase            548864  4
snd_soc_meson_axg_sound_card    16384  0
meson_vdec             77824  0
snd_soc_meson_card_utils    16384  1 snd_soc_meson_axg_sound_card
ir_nec_decoder         20480  0
v4l2_mem2mem           40960  1 meson_vdec
videobuf2_dma_contig    24576  1 meson_vdec
videobuf2_v4l2         32768  2 meson_vdec,v4l2_mem2mem
snd_soc_meson_g12a_toacodec    16384  1
videobuf2_memops       20480  1 videobuf2_dma_contig
snd_soc_meson_g12a_tohdmitx    20480  1
videobuf2_common       61440  3 meson_vdec,videobuf2_v4l2,v4l2_mem2mem
meson_dw_hdmi          24576  0
meson_ir               16384  0
videodev              278528  4 meson_vdec,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
snd_soc_meson_codec_glue    16384  2 snd_soc_meson_g12a_toacodec,snd_soc_meson_g12a_tohdmitx
meson_drm              61440  4 meson_dw_hdmi
mc                     61440  4 videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
meson_rng              16384  0
rng_core               24576  1 meson_rng
snd_soc_meson_axg_spdifout    16384  1
reset_meson_audio_arb    16384  6
dw_hdmi                53248  2 meson_dw_hdmi,dw_hdmi_i2s_audio
snd_soc_meson_axg_tdmout    24576  2
meson_canvas           16384  2 meson_drm,meson_vdec
snd_soc_meson_axg_tdmin    24576  0
snd_soc_meson_axg_frddr    36864  3
snd_soc_meson_axg_toddr    28672  0
snd_soc_meson_axg_fifo    20480  2 snd_soc_meson_axg_toddr,snd_soc_meson_axg_frddr
snd_soc_meson_t9015    24576  1
pwm_fan                20480  0
snd_soc_meson_axg_tdm_interface    16384  3 snd_soc_meson_axg_sound_card
snd_soc_meson_axg_tdm_formatter    16384  3 snd_soc_meson_axg_tdmin,snd_soc_meson_axg_tdm_interface,snd_soc_meson_axg_tdmout
snd_soc_spdif_tx       16384  1
snd_soc_simple_amplifier    16384  1
sch_fq_codel           20480  2
ip_tables              32768  0
x_tables               45056  1 ip_tables
rtc_pcf8563            24576  0
axg_audio              77824  51
sclk_div               16384  1 axg_audio
clk_phase              16384  1 axg_audio
meson_gxl              20480  0
realtek                24576  1

I hope this helps you locate the problem.

Thanks...this helps me...do you use ODROID-N2 or ODROID-N2Plus?

[wallyz21]

Updated petiboot to the latest 20201222 via the command pb-update. This seemed to work.

I then exited to the shell and entered the following command:

pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer ... N2/default

I exit back to the petiboot menu but don't see any netboot menu?!?!?

Tried power off & on and retrying command but no netboot menu. Is it obvious?

[tobetter]

Updated petiboot to the latest 20201222 via the command pb-update. This seemed to work.

I then exited to the shell and entered the following command:

pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer ... N2/default

I exit back to the petiboot menu but don't see any netboot menu?!?!?

Tried power off & on and retrying command but no netboot menu. Is it obvious?

Before running the command, please check if you have IP address assigned by your DHCP server. If not, please run udhcpc in the command line of the Petitboot.
Once you confirm the IP address, do run netboot_default which will load the Netboot Installer menus.

[tobetter]

@istanbulls and @specs, Can you guys please try this script after updating all packages and Wayland driver does not work this the kernel error? This script will fix the missing packages to build DKMS if necessary and will build 'mali-bifrost-dkms' again.
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

Footnote: I am suddenly wondering how many users are now using Mali Bifrost Wayland driver with Gnome Desktop...since I only have several users who has the Mali Bifrost issue after new kernel package 5.10.4 is updated. Curious...

[istanbulls]

@istanbulls and @specs, Can you guys please try this script after updating all packages and Wayland driver does not work this the kernel error? This script will fix the missing packages to build DKMS if necessary and will build 'mali-bifrost-dkms' again.
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

Footnote: I am suddenly wondering how many users are now using Mali Bifrost Wayland driver with Gnome Desktop...since I only have several users who has the Mali Bifrost issue after new kernel package 5.10.4 is updated. Curious...

Code: Select all

n2p@ubuntu:~$ sudo sh ./adsız.sh
(Veritabanı okunuyor ... 164313 dosya veya dizin kurulu durumda.)
Paket açılacak: .../linux-headers-5.10.0-odroid-arm64_5.10.4-202101051123~focal_arm64.deb ...
Paket açılıyor: linux-headers-5.10.0-odroid-arm64 (5.10.4-202101051123~focal) üzerine (5.10.4-202101051123~focal) ...
Paket açılacak: .../linux-headers-5.10.0-odroid-common_5.10.4-202101051123~focal_arm64.deb ...
Paket açılıyor: linux-headers-5.10.0-odroid-common (5.10.4-202101051123~focal) üzerine (5.10.4-202101051123~focal) ...
dpkg: uyarı: linux-kbuild-5.10, 5.10.4-202101051132~focal sürümünden 5.10.4-202101051123~focal sürümüne düşürülüyor
Paket açılacak: .../linux-kbuild-5.10_5.10.4-202101051123~focal_arm64.deb ...
Paket açılıyor: linux-kbuild-5.10 (5.10.4-202101051132~focal) üzerine (5.10.4-202101051123~focal) ...
Ayarlanıyor: linux-headers-5.10.0-odroid-common (5.10.4-202101051123~focal) ...
Ayarlanıyor: linux-kbuild-5.10 (5.10.4-202101051123~focal) ...
Ayarlanıyor: linux-headers-5.10.0-odroid-arm64 (5.10.4-202101051123~focal) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.10.0-odroid-arm64
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/mali-bifrost/24.0+202011130753~focal/source/dkms.conf does not exist.
   ...done.
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/mali-bifrost/24.0+202011130753~focal/source/dkms.conf does not exist.
(Veritabanı okunuyor ... 164313 dosya veya dizin kurulu durumda.)
Paket açılacak: .../linux-headers-5.9.0-odroid-arm64_5.9.16-202012232304~focal_arm64.deb ...
Paket açılıyor: linux-headers-5.9.0-odroid-arm64 (5.9.16-202012232304~focal) üzerine (5.9.16-202012232304~focal) ...
Paket açılacak: .../linux-headers-5.9.0-odroid-common_5.9.16-202012232304~focal_arm64.deb ...
Paket açılıyor: linux-headers-5.9.0-odroid-common (5.9.16-202012232304~focal) üzerine (5.9.16-202012232304~focal) ...
Paket açılacak: .../linux-kbuild-5.9_5.9.16-202012232304~focal_arm64.deb ...
Paket açılıyor: linux-kbuild-5.9 (5.9.16-202012232304~focal) üzerine (5.9.16-202012232304~focal) ...
Ayarlanıyor: linux-headers-5.9.0-odroid-common (5.9.16-202012232304~focal) ...
Ayarlanıyor: linux-kbuild-5.9 (5.9.16-202012232304~focal) ...
Ayarlanıyor: linux-headers-5.9.0-odroid-arm64 (5.9.16-202012232304~focal) ...
/etc/kernel/header_postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.9.0-odroid-arm64
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/mali-bifrost/24.0+202011130753~focal/source/dkms.conf does not exist.
   ...done.
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/mali-bifrost/24.0+202011130753~focal/source/dkms.conf does not exist.
update-initramfs: Generating /boot/initrd.img-5.10.0-odroid-arm64
Using DTB: amlogic/meson64_odroidn2_plus.dtb
Installing amlogic into /boot/dtbs/5.10.0-odroid-arm64/amlogic/
Installing amlogic into /boot/dtbs/5.10.0-odroid-arm64/amlogic/
flash-kernel: installing version 5.10.0-odroid-arm64
Generating boot script u-boot image... done.
Taking backup of boot.scr.
Installing new boot.scr.
n2p@ubuntu:~$ 

I have Ubuntu-Wayland, Ubuntu-Panprost, KDE-Panfrost on my SSD. I use all three OSes regularly.
The most problem-free system for me is Ubuntu-Wayland and I use this OS up to date. Ubuntu-Panfrost is my second choice. KDE-Panfrost is the most problematic system, so I only use it for updating and keeping track of new developments.

[tobetter]

ARM Mali Bifrost Wayland issue after updating the latest kernel version 5.10.4

I've just done refresh the Mali driver on @MamkinHacker's N2 remotely using TeamViewer and resolved after bunch of commands below. So finally, @MamkinHacker confrimed that Wayland driver works after reboot. I hope you also can try this on your N2 and see if Wayland is back.

Code: Select all

sudo dpkg --force-depends -r mali-bifrost-dkms
rm -rf /var/lib/dkms/mali-bifrost
find /usr/lib -name "mali_kbase.ko" -exec rm -rf {} \;
find /lib/modules/$(uname -r) -name "mali_kbase.ko" -exec rm -rf {} \;
sudo update-initramfs -u
sudo reboot
sudo apt install mali-bifrost-dkms
wget http://ppa.linuxfactory.or.kr/band-aid/rebuild_bifrost_dkms.sh
sh ./rebuild_bifrost_dkms.sh
sudo reboot

If you see this error while following the commands, it's not good sign. It says Good news but real meaning is that dkms is not working...

Code: Select all

Good news! Module version r24p0-01rel0 for mali_kbase.ko
exactly matches what is already found in kernel 5.10.0-odroid-arm64.
DKMS will not replace this module.
You may override by specifying --force.

Thank you @MamkinHacker to help me out...

[istanbulls]

I was trying the commands you suggested earlier. It was a faultless and longer installation compared to the previous one, but towards the end, the electricity was cut and the system was completely broken.

Now I'm trying these new commands.

[istanbulls]

sudo apt install mali-bifrost-dkms/mali-bifrost

this command fails!

[tobetter]

sudo apt install mali-bifrost-dkms/mali-dkms

this command fails!

Sorry, TYPO!! Please use this one.

sudo apt install mali-bifrost-dkms

[istanbulls]

sudo apt install mali-bifrost-dkms/mali-dkms

this command fails!

Sorry, TYPO!! Please use this one.

sudo apt install mali-bifrost-dkms

I guessed. I have already continued with this command.

[istanbulls]

ARM Mali Bifrost Wayland issue after updating the latest kernel version 5.10.4

I've just done refresh the Mali driver on @MamkinHacker's N2 remotely using TeamViewer and resolved after bunch of commands below. So finally, @MamkinHacker confrimed that Wayland driver works after reboot. I hope you also can try this on your N2 and see if Wayland is back.

Code: Select all

sudo dpkg --force-depends -r mali-bifrost-dkms
rm -rf /var/lib/dkms/mali-bifrost
find /usr/lib -name "mali_kbase.ko" -exec rm -rf {} \;
find /lib/modules/$(uname -r) -name "mali_kbase.ko" -exec rm -rf {} \;
sudo update-initramfs -u
sudo reboot
sudo apt install mali-bifrost-dkms
wget http://ppa.linuxfactory.or.kr/band-aid/rebuild_bifrost_dkms.sh
sh ./rebuild_bifrost_dkms.sh
sudo reboot

If you see this error while following the commands, it's not good sign. It says Good news but real meaning is that dkms is not working...

Code: Select all

Good news! Module version r24p0-01rel0 for mali_kbase.ko
exactly matches what is already found in kernel 5.10.0-odroid-arm64.
DKMS will not replace this module.
You may override by specifying --force.

Thank you @MamkinHacker to help me out...

It worked for me, thanks @tobetter

Code: Select all

n2p@ubuntu:~$ uname -a
Linux ubuntu 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.4-202101051123~focal (2021-01-05) aarch64 aarch64 aarch64 GNU/Linux
n2p@ubuntu:~$ dpkg -l | grep linux-image
ii  linux-image-5.10.0-odroid-arm64            5.10.4-202101051123~focal                 arm64        Linux 5.10 for 64-bit ARMv8 machines
ii  linux-image-5.9.0-odroid-arm64             5.9.16-202012232304~focal                 arm64        Linux 5.9 for 64-bit ARMv8 machines
ii  linux-image-generic                        5:2020.12-1+202012241958~focal            arm64        Generic Linux kernel image
n2p@ubuntu:~$ 

[wallyz21]

Updated petiboot to the latest 20201222 via the command pb-update. This seemed to work.

I then exited to the shell and entered the following command:

pb-event url@/net/eth0 url=http://ppa.linuxfactory.or.kr/installer ... N2/default

I exit back to the petiboot menu but don't see any netboot menu?!?!?

Tried power off & on and retrying command but no netboot menu. Is it obvious?

Before running the command, please check if you have IP address assigned by your DHCP server. If not, please run udhcpc in the command line of the Petitboot.
Once you confirm the IP address, do run netboot_default which will load the Netboot Installer menus.

I down graded petiboot to a stable version and it was able to see both my eMMC card and the netboot menus.

[wallyz21]

OK so following the instructions on post 1 I started a petiboot netboot install of Ubuntu 20.04.

It all went smoothly for about two hours and then prompted to reboot.

Rebooted and black screen.

Took the eMMc card out of the N2 and mounted the partitions on my N2+ via a USB adapter and could see the partitions looked Ok. The config.ini looks identical as my regular working system and is set to 1080P. So should be good.

Not sure if I partitioned the eMMC card correctly during the install. I made it identical to the normal HK eMMC cards with a 128mb fat16 boot partition and the rest as an ext04 partition labeled rootfs.

Looks like the contents of the 128mb boot partition were not created during during the install. I'm feeling like I should have just chosen to install to the entire device rather than make multiple partitions.

Can someone recommend the partition layout before I (happily) waste my time doing another reinstall.

If I do have my partitioning wrong can I use gparted to correct the issue?

Not sure what else to check?!?!

[specs]

@istanbulls and @specs, Can you guys please try this script after updating all packages and Wayland driver does not work this the kernel error? This script will fix the missing packages to build DKMS if necessary and will build 'mali-bifrost-dkms' again.
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

Footnote: I am suddenly wondering how many users are now using Mali Bifrost Wayland driver with Gnome Desktop...since I only have several users who has the Mali Bifrost issue after new kernel package 5.10.4 is updated. Curious...

Sorry for the late response.

Currently the system is running on Ubuntu 5.10.4-202101051123~focal
You and @istanbulls already fixed the mistakes, so it works now.

As for the reason I run Gnome with Wayland:
I tried using mate like the original Hardkernel image, but I could not get hardware accelation to work with mpv and mate.
It does not do all I want it to do, but now I can at least play DVD's with mpv (hardware accelerated).
For the user experience I prefer mate though.

[tobetter]

@istanbulls and @specs, Can you guys please try this script after updating all packages and Wayland driver does not work this the kernel error? This script will fix the missing packages to build DKMS if necessary and will build 'mali-bifrost-dkms' again.
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

Footnote: I am suddenly wondering how many users are now using Mali Bifrost Wayland driver with Gnome Desktop...since I only have several users who has the Mali Bifrost issue after new kernel package 5.10.4 is updated. Curious...

Sorry for the late response.

Currently the system is running on Ubuntu 5.10.4-202101051123~focal
You and @istanbulls already fixed the mistakes, so it works now.

As for the reason I run Gnome with Wayland:
I tried using mate like the original Hardkernel image, but I could not get hardware accelation to work with mpv and mate.
It does not do all I want it to do, but now I can at least play DVD's with mpv (hardware accelerated).
For the user experience I prefer mate though.

Glad to know it works...
Mate is not based on Wayland AFAIK, maybe jump to Panfrost sometime soon?

So now I know 4 users are running Mali Bifrost Wayland....Then no one else is using this? Or everybody switched to ALARM or Ubuntu 20.10 to be with Panfrost??

[wallyz21]

Thanks tobetter.

I restarted the netboot install let the installer use the entire eMMc card and create it's own partitions. Selected a minimal install and presto 30 minutes later. I have a booting 5.10.0 Ubuntu 20.04.1 LTS system.

Any recommendations for which desktop to use?

I normally use MATE but my understanding is that there would be no acceleration with MATE!

Gnome is nice but a little memory hungry.

XFCE is lite weight.

What do I need to consider in terms of using Panfrost or the alternative (Mali Bifrost driver). I think I'd prefer to use Panfrost.

[tobetter]

Thanks tobetter.

I restarted the netboot install let the installer use the entire eMMc card and create it's own partitions. Selected a minimal install and presto 30 minutes later. I have a booting 5.10.0 Ubuntu 20.04.1 LTS system.

Any recommendations for which desktop to use?

I normally use MATE but my understanding is that there would be no acceleration with MATE!

Gnome is nice but a little memory hungry.

XFCE is lite weight.

What do I need to consider in terms of using Panfrost or the alternative (Mali Bifrost driver). I think I'd prefer to use Panfrost.

Since you have not intened to install OS using the Netboot Installer, you must be missing many information. Let me summarize some based on what you can choose for GPU acceleration.

1. Bifrost
> Linux kernle 5.9 - 5.10
> Ubuntu 20.04 or Ubuntu 20.10
> Gnome Desktop only with Wayland session manager
> Support is updated in this thread

2. Panfrost
> Linux kernel 5.10
> Ubuntu 20.10 only
> Can run most Desktops with X11/Wayland
> Support is updated in another thread, viewtopic.php?f=52&t=40761&start=200

If you have not started to install Desktop or Mali Bifrost driver yet, you can decide which Ubuntu version you want to use. Since I do not have the Netboot Installer for Ubuntu 20.10, you must install Ubuntu 20.04 server version and upgrade it to Ubuntu 20.10. Please refer to the link, viewtopic.php?p=310287#p310287

[RussianNeuroMancer]

The current installer will install Linux v4.9 with U-boot v2015.01, they are all official kernel and U-boot from Hardkernel but kernel configuration could be slightly different.

Is there similar image with 4.9 for ODROID-C4? (Besides Hardkernel official images, of course.)

[tobetter]

The current installer will install Linux v4.9 with U-boot v2015.01, they are all official kernel and U-boot from Hardkernel but kernel configuration could be slightly different.

Is there similar image with 4.9 for ODROID-C4? (Besides Hardkernel official images, of course.)

I have no image with 4.9 kernel, but you can try the prebuilt image which has 5.x kernel.
https://docs.linuxfactory.or.kr/install ... image.html

After booting with 5.x kernel, you can try to run these commands. The source code of the package is from Hardkernel but build with different kernel config.

Code: Select all

$ sudo apt update
$ sudo apt install linux-image-4.9.241-odroidg12
$ sudo reboot

The package is building daily basis automatically, I don't test every single package due to low demand and focusing to 5.x kernel. You can try and let me know if not working or you need to add kernel config.

[RussianNeuroMancer]

After booting with 5.x kernel, you can try to run these commands.

Tried, boot process get stuck. Is it works for you?

I don't test every single package due to low demand and focusing to 5.x kernel.

Understandable, however while there is workaround for temporary Panforst issues (someday it will work fine) there is no workaround or solution for pinky gray issue, so images based on 5.x is not an option, at least for now. Hardkernel's image with 4.9 is not an option too due to lack of hardware accelerated rendering for Gnome Shell Wayland session (which works on your images). So overall I don't see usable images for C4 and N2+ yet, but I going to try proprietary driver working on Armbian 4.9 images, maybe this way it will work out.

[wallyz21]

...

Since you have not intened to install OS using the Netboot Installer, you must be missing many information. Let me summarize some based on what you can choose for GPU acceleration.

1. Bifrost
> Linux kernle 5.9 - 5.10
> Ubuntu 20.04 or Ubuntu 20.10
> Gnome Desktop only with Wayland session manager
> Support is updated in this thread

2. Panfrost
> Linux kernel 5.10
> Ubuntu 20.10 only
> Can run most Desktops with X11/Wayland
> Support is updated in another thread, viewtopic.php?f=52&t=40761&start=200

If you have not started to install Desktop or Mali Bifrost driver yet, you can decide which Ubuntu version you want to use. Since I do not have the Netboot Installer for Ubuntu 20.10, you must install Ubuntu 20.04 server version and upgrade it to Ubuntu 20.10. Please refer to the link, viewtopic.php?p=310287#p310287

Thanks.

Ok so I have upgraded to 20.10.

Is Wayland already installed on the base image or do I need to do that?

I have seen instructions in another post to install Wayland. Just need to find it.

[tobetter]

...

Since you have not intened to install OS using the Netboot Installer, you must be missing many information. Let me summarize some based on what you can choose for GPU acceleration.

1. Bifrost
> Linux kernle 5.9 - 5.10
> Ubuntu 20.04 or Ubuntu 20.10
> Gnome Desktop only with Wayland session manager
> Support is updated in this thread

2. Panfrost
> Linux kernel 5.10
> Ubuntu 20.10 only
> Can run most Desktops with X11/Wayland
> Support is updated in another thread, viewtopic.php?f=52&t=40761&start=200

If you have not started to install Desktop or Mali Bifrost driver yet, you can decide which Ubuntu version you want to use. Since I do not have the Netboot Installer for Ubuntu 20.10, you must install Ubuntu 20.04 server version and upgrade it to Ubuntu 20.10. Please refer to the link, viewtopic.php?p=310287#p310287

Thanks.

Ok so I have upgraded to 20.10.

Is Wayland already installed on the base image or do I need to do that?

I have seen instructions in another post to install Wayland. Just need to find it.

Bifrost Wayland driver must be installed by you.

Code: Select all

$ sudo apt update
$ sudo apt install mali-bifrost-wayland-driver ubuntu-desktop

[trwn2p]

So now I know 4 users are running Mali Bifrost Wayland....Then no one else is using this? Or everybody switched to ALARM or Ubuntu 20.10 to be with Panfrost??

Soon as panfrost worked even marginally (3 months ago) I've used it and not the mali drivers on Manjaro and LFS.
Now I'm using panfrost on both my Deb 11 LXQt and Ubu 20.10 Gnome for Odroid N2+. No more mali on these for a while now.

Code: Select all

  Host: groovy-server Kernel: 5.10.0-odroid-panfrost-arm64 aarch64 bits: 64 Desktop: GNOME 3.38.1 
           Distro: Ubuntu 20.10 (Groovy Gorilla) 
Machine:   Type: ARM Device System: Hardkernel ODROID-N2Plus details: N/A 
CPU:       Info: 6-Core (2-Die) model: N/A variant-1: cortex-a53 variant-2: cortex-a73 bits: 64 type: MCP MCM 
           Speed: 2208 MHz min/max: 1000/2016:2400 MHz Core speeds (MHz): 1: 2016 2: 2016 3: 2208 4: 2208 5: 2208 6: 2208 
Graphics:  Device-1: meson-g12a-mali driver: panfrost v: kernel 
           Device-2: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: kernel 
           Display: wayland server: X.Org 1.20.9 driver: modesetting unloaded: fbdev resolution: 2560x1440~60Hz 
           OpenGL: renderer: Mali G52 (Panfrost) v: 2.1 Mesa 21.0.0-devel (git-a6bdbd5c0f)  

System Updated Jan 7th 2021 I'd like to get Xorg-server 1.20.10 if possible. Also I'd like to hear of anyone's experience with a minimal Ubu 20.10 netboot install and then a Kde/Plasma install added to it. I have it on Manjaro using X. Wayland isn't right yet.

[wallyz21]

Ok so I have now completed the :

- Netboot install Ubuntu 20.04.1
- Upgraded to 20.10
- sudo apt install mali-bifrost-wayland-driver
- Installed Ubuntu-Mate-Desktop

Code: Select all

odroid@odroid-n2:~$ uname -a
Linux odroid-n2 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.4-202101051123~focal (2021-01-05) aarch64 aarch64 aarch64 GNU/Linux
odroid@odroid-n2:~$ lsb_release  -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.10
Release:	20.10
Codename:	groovy
odroid@odroid-n2:~$ 

I am getting a lot of internal errors from glx. & glxinfo core dumps. and of course glmark2 core dumps as well.

[downunder52]

@istanbulls and @specs, Can you guys please try this script after updating all packages and Wayland driver does not work this the kernel error? This script will fix the missing packages to build DKMS if necessary and will build 'mali-bifrost-dkms' again.
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

Footnote: I am suddenly wondering how many users are now using Mali Bifrost Wayland driver with Gnome Desktop...since I only have several users who has the Mali Bifrost issue after new kernel package 5.10.4 is updated. Curious...

@tobetter I'm also had problem with Mali Bifrost after upgrading to 5.10.4 kernel. I'm on N2+ groovy.
The problem was fixed after following your post to reinstall Mali Bifrost package.
Also just want to report that your repository fails to install wifi driver for Hardkernel module 5A. I had to follow this link https://blog.abysm.org/2020/03/realtek- ... tallation/ from Kali linux to successfully install the driver.
Could you look into this so any future upgrade I/we don't have to search for the driver outside your repository.
And big thank you for your effort to make my ODRIOD-N2+ flies.

[tobetter]

@istanbulls and @specs, Can you guys please try this script after updating all packages and Wayland driver does not work this the kernel error? This script will fix the missing packages to build DKMS if necessary and will build 'mali-bifrost-dkms' again.
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

Footnote: I am suddenly wondering how many users are now using Mali Bifrost Wayland driver with Gnome Desktop...since I only have several users who has the Mali Bifrost issue after new kernel package 5.10.4 is updated. Curious...

@tobetter I'm also had problem with Mali Bifrost after upgrading to 5.10.4 kernel. I'm on N2+ groovy.
The problem was fixed after following your post to reinstall Mali Bifrost package.
Also just want to report that your repository fails to install wifi driver for Hardkernel module 5A. I had to follow this link https://blog.abysm.org/2020/03/realtek- ... tallation/ from Kali linux to successfully install the driver.
Could you look into this so any future upgrade I/we don't have to search for the driver outside your repository.
And big thank you for your effort to make my ODRIOD-N2+ flies.

Can you share the log please?

[downunder52]

Which log? Mali Bifrost problem or wifi module?

[tobetter]

Which log? Mali Bifrost problem or wifi module?

Whatever the issue you have...probaly Wifi since Bifrost looks like fixed?

[tobetter]

Note
New kernel package 5.10.5 has been uploaded and it fixes the Pinky-Grey issue that was discussed in another thread. Several users had confirmed it's been fixed with their display.

[istanbulls]

Note
New kernel package 5.10.5 has been uploaded and it fixes the Pinky-Grey issue that was discussed in another thread. Several users had confirmed it's been fixed with their display.

I updated it, it works perfectly with the N2. Thanks @tobetter.

Code: Select all

n2@odroid:~$ uname -a
Linux odroid 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.5-202101082057~focal (2021-01-08) aarch64 aarch64 aarch64 GNU/Linux
n2@odroid:~$ dpkg -l | grep linux-image
ii  linux-image-5.10.0-odroid-arm64            5.10.5-202101082057~focal                 arm64        Linux 5.10 for 64-bit ARMv8 machines
ii  linux-image-generic                        5:2020.12-1+202012241958~focal            arm64        Generic Linux kernel image
n2@odroid:~$ cat /proc/device-tree/model
Hardkernel ODROID-N2n2@odroid:~$ 

[wallyz21]

Issue with package updates on 20.04.1 LTS upgrade to 20.10.

After upgrading to groovy from focal I have noticed that all package searches and installs are finding the focal version rather than the groovy version.

If i do a package search for libqt5core5a via the official ubuntu package search site I find the latest version for groovy is 5.14.2. (for arm64)

However when I attempt a search from the command line it reports 5.12.8 which is the focal version.

This causes a lot of other packages to fail installation due to missing dependencies.

I don't think the upgrade has worked correctly even though the system reports it is at groovy.

[tobetter]

Issue with package updates on 20.04.1 LTS upgrade to 20.10.

After upgrading to groovy from focal I have noticed that all package searches and installs are finding the focal version rather than the groovy version.

If i do a package search for libqt5core5a via the official ubuntu package search site I find the latest version for groovy is 5.14.2. (for arm64)

However when I attempt a search from the command line it reports 5.12.8 which is the focal version.

This causes a lot of other packages to fail installation due to missing dependencies.

I don't think the upgrade has worked correctly even though the system reports it is at groovy.

If you had upgraded as Desktop is installed, specifically Qt has installed for example, it won't be upgraded successfully. Since I managed the Qt package customized to run with Mali Wayland driver for Ubuntu 20.04 and its version and this package won't be updated when you upgrade to Ubuntu 20.10. So if you like to try Ubuntu 20.10, install non-Desktop version which is likely server/minimal version of Ubuntu 20.04 and upgrade to 20.10. Then every package will be upgraded for 20.10 from Canonical mostly and some tweak packages including Linux kernel will come from my package.

[wallyz21]

Issue with package updates on 20.04.1 LTS upgrade to 20.10.

After upgrading to groovy from focal I have noticed that all package searches and installs are finding the focal version rather than the groovy version.

If i do a package search for libqt5core5a via the official ubuntu package search site I find the latest version for groovy is 5.14.2. (for arm64)

However when I attempt a search from the command line it reports 5.12.8 which is the focal version.

This causes a lot of other packages to fail installation due to missing dependencies.

I don't think the upgrade has worked correctly even though the system reports it is at groovy.

If you had upgraded as Desktop is installed, specifically Qt has installed for example, it won't be upgraded successfully. Since I managed the Qt package customized to run with Mali Wayland driver for Ubuntu 20.04 and its version and this package won't be updated when you upgrade to Ubuntu 20.10. So if you like to try Ubuntu 20.10, install non-Desktop version which is likely server/minimal version of Ubuntu 20.04 and upgrade to 20.10. Then every package will be upgraded for 20.10 from Canonical mostly and some tweak packages including Linux kernel will come from my package.

That is what I did. A minimal 20.04 install without desktop then an upgrade to 20.10 using these instructions

viewtopic.php?p=310287#p310287

After that I attempted to install some desktop packages but was unable to install a full MATE. I could install the usual ubuntu-mate-desktop but not install the full ubuntu-mate-desktop^ (the up arrow is intended) which has a dependancy on 5.14.2 of qt.

So can I ask someone to enter the following command on a groovy system

Apt search libqt5core5a

And confirm the version is 5.14.2 and not 5.12.8.

[tobetter]

Issue with package updates on 20.04.1 LTS upgrade to 20.10.

After upgrading to groovy from focal I have noticed that all package searches and installs are finding the focal version rather than the groovy version.

If i do a package search for libqt5core5a via the official ubuntu package search site I find the latest version for groovy is 5.14.2. (for arm64)

However when I attempt a search from the command line it reports 5.12.8 which is the focal version.

This causes a lot of other packages to fail installation due to missing dependencies.

I don't think the upgrade has worked correctly even though the system reports it is at groovy.

If you had upgraded as Desktop is installed, specifically Qt has installed for example, it won't be upgraded successfully. Since I managed the Qt package customized to run with Mali Wayland driver for Ubuntu 20.04 and its version and this package won't be updated when you upgrade to Ubuntu 20.10. So if you like to try Ubuntu 20.10, install non-Desktop version which is likely server/minimal version of Ubuntu 20.04 and upgrade to 20.10. Then every package will be upgraded for 20.10 from Canonical mostly and some tweak packages including Linux kernel will come from my package.

That is what I did. A minimal 20.04 install without desktop then an upgrade to 20.10 using these instructions

viewtopic.php?p=310287#p310287

After that I attempted to install some desktop packages but was unable to install a full MATE. I could install the usual ubuntu-mate-desktop but not install the full ubuntu-mate-desktop^ (the up arrow is intended) which has a dependancy on 5.14.2 of qt.

So can I ask someone to enter the following command on a groovy system

Apt search libqt5core5a

And confirm the version is 5.14.2 and not 5.12.8.

Did you change /etc/apt/sources.d/ppa_linuxfactory_or_kr.list as well?

[wallyz21]

...

Did you change /etc/apt/sources.d/ppa_linuxfactory_or_kr.list as well?

No I didn't!

[tobetter]

...

Did you change /etc/apt/sources.d/ppa_linuxfactory_or_kr.list as well?

No I didn't!

Then, please...since /etc/apt/sources.list is for the package from official Ubuntu server and /etc/apt/sources.d/ppa_linuxfactory_or_kr.list is for the packages from my server.

[loredin]

Hi while going through manual installation via netboot , I have the choice to install different packages of ubuntu (lubuntu, ubuntu studio, server base, etc ...)
Are there only specific ones that are suited for N2 ? May I install simultaneously some of the packages or differently formulated, does it make sense ?

[odroidn2user]

Hi while going through manual installation via netboot , I have the choice to install different packages of ubuntu (lubuntu, ubuntu studio, server base, etc ...)
Are there only specific ones that are suited for N2 ? May I install simultaneously some of the packages or differently formulated, does it make sense ?

If you want GPU desktop acceleration, you'll have to choose the Ubuntu Gnome Desktop and install the Wayland driver after the installation of the desktop environment is done.
If you don't require GPU desktop acceleration, pick any desktop environment you like.
You can always add specific packages later, though some choices are more fitting with specific desktop environments.

[loredin]

Hi while going through manual installation via netboot , I have the choice to install different packages of ubuntu (lubuntu, ubuntu studio, server base, etc ...)
Are there only specific ones that are suited for N2 ? May I install simultaneously some of the packages or differently formulated, does it make sense ?

If you want GPU desktop acceleration, you'll have to choose the Ubuntu Gnome Desktop and install the Wayland driver after the installation of the desktop environment is done.
If you don't require GPU desktop acceleration, pick any desktop environment you like.
You can always add specific packages later, though some choices are more fitting with specific desktop environments.

I have chosen ubuntu-desktop thanks to some advice and installed mali-bifrost-wayland-driver amongs other on top of it.
I have then some problems running some applicationss though, like mixxx .
It was worst choosing ubuntu-studio directly , I could not even use krita there. It is still mysterious to me how all these work together.
Would I have better chance with older versions ?

[wallyz21]

...

Did you change /etc/apt/sources.d/ppa_linuxfactory_or_kr.list as well?

No I didn't!

Then, please...since /etc/apt/sources.list is for the package from official Ubuntu server and /etc/apt/sources.d/ppa_linuxfactory_or_kr.list is for the packages from my server.

Thanks that fixed it!!!

[wallyz21]

Having trouble running glx programs

glxinfo core dumps

and glmark2 returns this error:

Code: Select all

odroid@odroid-n2:/etc/apt/sources.list.d$ glmark2
** GLX does not support GLX_EXT_swap_control or GLX_MESA_swap_control!
** Failed to set swap interval. Results may be bounded above by refresh rate.
terminate called after throwing an instance of 'std::logic_error'
  what():  basic_string::_M_construct null not valid
Aborted (core dumped)
odroid@odroid-n2:/etc/apt/sources.list.d$ 

I'm guessing I need to install MESA or similar!

[wallyz21]

Have installed odroid-alsa and now have an audio device showing in the Sound device manager but I'm still not getting sound via HDMI.

[istanbulls]

Have installed odroid-alsa and now have an audio device showing in the Sound device manager but I'm still not getting sound via HDMI.

When you finish the installation with Ubuntu-Desktop with the netboot installer, mali-bifrost is sometimes missing.
It will be useful to run this command (it will increase your video performance):

Code: Select all

sudo apt install ubuntu-desktop mali-bifrost-wayland-driver

[odroidn2user]

I have chosen ubuntu-desktop thanks to some advice and installed mali-bifrost-wayland-driver amongs other on top of it.
I have then some problems running some applicationss though, like mixxx .
It was worst choosing ubuntu-studio directly , I could not even use krita there. It is still mysterious to me how all these work together.
Would I have better chance with older versions ?

I remember reading something about Mixxx on the forum, try searching, perhaps something turns up.
The thing is that getting all things to work is not as easy as you'd think, with kernel drivers, user space drivers, desktop environments, etc.
Then add in experimental and/or development level software and things get complicated quickly.
Wayland on its own is also not quite feature complete and has its issues, and Mali support for Wayland also seems not completely right/correct.
And then you have to patch things like QT to get it going right with the Mali drivers, etc, etc, etc. All of which may or may not work together right...
So, yeah. If you require very specific packages, it may or may not work. Sometimes alternatives for those packages are a working solution.
I find default/normal gnome software to work well, but... You'll have to find stuff that works, and a lot does, but certainly not everything.

Hopefully and likely things improve with the Panfrost drivers, once they gets up to speed and become available in pre-packaged image form.
Then you can do the usual X11 style desktop work, which is generally more stable.