radxa / radxa-zero-images-released

14 stars 1 forks source link

radxa-zero-v20211027 no hardware video acceleration? #7

Open almirus opened 2 years ago

almirus commented 2 years ago

https://photos.app.goo.gl/VgmCY8VaBPc9kU157

cursor flickers and video redrawing

[ 9119.172753]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.179629]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.186779]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.193699]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.201520]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.207232]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.214167]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.221270]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.228148]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.236263]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.241894]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.248811]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.255853]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.262818]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.270893]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.276407]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.283331]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.290335]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0
[ 9119.297163]  fe.dai-link-0: ASoC: no backend DAIs enabled for fe.dai-link-0

reboot command still doesn't work

rock@zero:~$ sudo reboot
[sudo] password for rock:
         Stopping Session c1 of user lightdm.
[  OK  ] Stopped target Sound Card.
[  OK  ] Stopped target Timers.
[  OK  ] Stopped Daily Cleanup of Temporary Directories.
[  OK  ] Sto         Stopping Serial Getty on ttyAML0...
         Stopping Getty on tty1...
         Stopping Avahi mDNS/DNS-SD Stack...
         Stopping Light Display Manager...
         Stopping DHCP Client Daemon...
[  OK  ] Stopped Daily man-db regeneration.
[  OK  ] Stopped target System Time Synchronized.
         Stopping LSB: Set sysfs variables from /etc/sysfs.conf...
[  OK  ] Stopped target Bluetooth.
         Stopping Bluetooth service...
[  OK  ] Stopped Resets System Activity Data Collector.
         Stopping OpenBSD Secure Shell server...
[  OK  ] Stopped Session 2 of user rock.
         Stopping User Manager for UID 1000...
[  OK  ] Stopped Avahi mDNS/DNS-SD Stack.
[  OK  ] Stopped DHCP Client Daemon.
[  OK  ] Stopped Bluetooth service.
[  OK  ] Stopped Serial Getty on ttyAML0.
[  OK  ] Stopped Getty on tty1.
[  OK  ] Stopped OpenBSD Secure Shell server.
[  OK  ] Stopped Authorization Manager.
[  OK  ] Stopped Network Time Service.
[  OK  ] Stopped User Manager for UID 1000.
[  OK  ] Stopped Save/Restore Sound Card State.
         Stopping Manage Sound Card State (restore and store)...
         Stopping User Runtime Directory /run/user/1000...
[  OK  ] Removed slice system-getty.slice.
[  OK  ] Removed slice system-serial\x2dgetty.slice.
[  OK  ] Stopped /etc/rc.local Compatibility.
[  OK  ] Unmounted /run/user/1000.
[  OK  ] Stopped LSB: Set sysfs variables from /etc/sysfs.conf.
[  OK  ] Stopped Manage Sound Card State (restore and store).
[  OK  ] Stopped User Runtime Directory /run/user/1000.
[  OK  ] Removed slice User Slice of UID 1000.
[  OK  ] Stopped Session c1 of user lightdm.
[  OK  ] Stopped Light Display Manager.
         Stopping Login Service...
         Stopping User Manager for UID 109...
[  OK  ] Stopped User Manager for UID 109.
         Stopping User Runtime Directory /run/user/109...
[  OK  ] Unmounted /run/user/109.
[  OK  ] Stopped User Runtime Directory /run/user/109.
[  OK  ] Removed slice User Slice of UID 109.
         Stopping Permit User Sessions...
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped target Network.
         Stopping Network Manager...
         Stopping WPA supplicant...
         Stopping Raise network interfaces...
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped Login Service.
[  OK  ] Stopped Network Manager.
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Stopped WPA supplicant.
         Stopping D-Bus System Message Bus...
[  OK  ] Stopped D-Bus System Message Bus.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped target Local Encrypted Volumes.
[  OK  ] Stopped Dispatch Password …ts to Console Directory Watch.
[  OK  ] Stopped Forward Password R…uests to Wall Directory Watch.
[  OK  ] Stopped target Swap.
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
         Stopping Update UTMP about System Boot/Shutdown...
         Stopping Restore / save the current clock...
         Stopping Load/Save Random Seed...
[  OK  ] Stopped Restore / save the current clock.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
[  OK  ] Unset automount boot.automount.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
[  OK  ] Started Reboot.
[  OK  ] Reached target Reboot.
[   63.368694] printk: systemd-shutdow: 26 output lines suppressed due to ratelimiting
[   63.428462] systemd-shutdown[1]: Syncing filesystems and block devices.
[   63.862304] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
[   63.871455] systemd-journald[1446]: Received SIGTERM from PID 1 (systemd-shutdow).
[   63.912303] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[   63.921914] systemd-shutdown[1]: Unmounting file systems.
[   63.924220] [1899]: Remounting '/' read-only in with options '(null)'.
[   63.965387] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
[   63.975323] systemd-shutdown[1]: All filesystems unmounted.
[   63.975454] systemd-shutdown[1]: Deactivating swaps.
[   63.980503] systemd-shutdown[1]: All swaps deactivated.
[   63.985440] systemd-shutdown[1]: Detaching loop devices.
[   63.993043] systemd-shutdown[1]: All loop devices detached.
[   63.996233] systemd-shutdown[1]: Detaching DM devices.
[   64.016365] kvm: exiting hardware virtualization

almirus commented 2 years ago
[ 1671.325366] uvcvideo: Failed to query (GET_INFO) UVC control 2 on unit 1: -32 (exp. 1).
[ 1684.165564] panfrost ffe40000.gpu: gpu sched timeout, js=1, config=0x7301, status=0x0, head=0x3984000, tail=0x3984000, sched_job=00000000152af2e8
[ 1691.592408] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x35dea00, tail=0x35dea00
[ 1691.596884] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7300, status=0x58, head=0x35dea00, tail=0x35dea00, sched_job=00000000771b52e2
StephenInVamrs commented 2 years ago

So far command reboot is available for Radxa Zero Debian image.

As for Ubuntu image, we are stilling looking for the cause.

steev commented 2 years ago

What I've found here is that if hdmi is connected, reboot does not work, but if hdmi is not connected, reboot seems to work properly. There's a bit of a hack patch floating around, e.g. https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/radxazero/002-revert-meson-drv-shutdown.patch (originally from chewitt iirc) that does seem to work, at least, with a 5.15.6 kernel, I am planning to test it against 5.10 at some point.

MichaIng commented 2 years ago

@StephenInVamrs

So far command reboot is available for Radxa Zero Debian image.

This doesn't seem to be true, we just tested the new Debian image but sadly reboot still leaves the Zero shut down 😢.

StephenInVamrs commented 2 years ago

Hi. I confirm that this patch helps to fix the 'reboot not working' issue. https://github.com/pyavitz/debian-image-builder/blob/feature/patches/amlogic/radxazero/002-revert-meson-drv-shutdown.patch

This patch is added to Radxa Zero kernel:

When you use prebuilt radxa-zero images, upgrade kernel to version 5.10.69-8-amlogic-g8e2cfaa5faa5 to fix the 'reboot not working' issue. Below is the steps to upgrade kernel.

1.Update your /etc/apt/sources.list.d/apt-radxa-com.list accordingly to enable Radxa APT repository.

For Ubuntu Focal:

 root@zero:~# cat /etc/apt/sources.list.d/apt-radxa-com.list 
 deb http://apt.radxa.com/focal-stable/ focal main
 deb http://apt.radxa.com/focal-testing/ focal main

For Debian Buster:

 root@zero:~# cat /etc/apt/sources.list.d/apt-radxa-com.list 
 deb http://apt.radxa.com/buster-stable/ buster main
 deb http://apt.radxa.com/buster-testing/ buster main

2.Install kernel packages

 sudo apt update
 sudo apt install -y linux-headers-5.10.69-8-amlogic-g8e2cfaa5faa5
 sudo apt install -y linux-image-5.10.69-8-amlogic-g8e2cfaa5faa5

3.Power cycle Radxa Zero. And execute command 'reboot' to restart Radxa zero.

MichaIng commented 2 years ago

We verified it works now, many thanks!

Just as a side note: the linux-headers-* packages are generally not required to run the system, but only to compile kernel modules. So depending on available disk space, one may want to purge it. Aside of manual kernel module compiling, some (rare) packages use DKMS to do so, hence without Linux headers, when you see any APT install/upgrade failure related to messages that DKMS tried to compile a kernel module, then reinstalling the headers can solve it. Kernel image and matching headers packages usually have the same name, just with image resp. headers as shown above.