Raspberry Pi 4 Model B
-
@Aury88 said in Raspberry Pi 4 Model B:
@Pulsar33
Hi!
The unity8 log is very similar to this issue in mir-kiosk. It says there is a workaround but I don't understand what it is....we need to study it and or help from @alan_git seems we need to
--env-hacks MIR_MESA_KMS_DISABLE_MODESET_PROBEwhen run mir/unity8 but I don't undestand how...
That's just one way to set an environment variable.
-
@alan_g sorry but I'm not so skilled about bash and linux. so excuse me for the stupid question:
I knew that environment variable had to have a value so something likeENV_NAME=valueMIR_MESA_KMS_DISABLE_MODESET_PROBE seem only the name...what is its value? is it"true"?
-
@Aury88 said in Raspberry Pi 4 Model B:
@alan_g sorry but I'm not so skilled about bash and linux. so excuse me for the stupid question:
I knew that environment variable had to have a value so something likeENV_NAME=valueMIR_MESA_KMS_DISABLE_MODESET_PROBE seem only the name...what is its value? is it"true"?
It doesn't need a value, so "true" will be fine (as will "false").
-
no, setting that as an enviroment variable didn't solved the problem... ¯\(ツ)/¯
-
Hello
Still stuck in console mode.
Please tell me the commands to try launching the graphical mode, even if this doesn't succeed at this time.
Pulsar33 -
@Pulsar33 it should be in the Ctrl+Alt+F7. unity8 is by default already running in background. you can prove that by typing in the console
start unity8Also you can restart it with
restart unity8The problem is that it doesn't seem to work properly because of the mesa-kms missing support in the raspberrypi4 as you can see above
(EGL platform does not support EGL_KHR_platform_gbm extension, Failed to detect whether device /dev/dri/card1 and card2 supports KMS and Couldn't get DRM resources for an Invalid argument) -
@Aury88 said in Raspberry Pi 4 Model B:
@Pulsar33 it should be in the Ctrl+Alt+F7. unity8 is by default already running in background. you can prove that by typing in the console
start unity8Also you can restart it with
restart unity8The problem is that it doesn't seem to work properly because of the mesa-kms missing support in the raspberrypi4 as you can see above
(EGL platform does not support EGL_KHR_platform_gbm extension, Failed to detect whether device /dev/dri/card1 and card2 supports KMS and Couldn't get DRM resources for an Invalid argument)If that's how you are starting Unity8, then setting the environment variable needs to be done in the launch scripts, not in your terminal session. (Sorry, I don't know enough about how your image is set up to know where these scripts are.)
-
@alan_g i didn't set that variable throught the terminal session but by editing /etc/environment and ~/.bashrc files
-
@Aury88 it might help others help you if you pastebin the Unity8 log.
-
@alan_g : Hello
I would be glad to pastebin it but I don't know where to find it. The only relevant logs I have are :pulsar33@Minerve:/media/pulsar33/root/var/log$ ls -alR | grep oct. -rw-r--r-- 1 root root 979 oct. 20 21:00 .log20191020-185955.2080 -rw-r----- 1 root root 20 oct. 20 20:59 biometryd.log -rw-r----- 1 root root 153 oct. 20 20:59 hwclock-save.log -rw-r----- 1 root root 32 oct. 20 20:59 lightdm.log -rw-r----- 1 root root 22 oct. 20 20:59 udev.log -rw-r----- 1 root root 12 oct. 20 20:59 urfkill.logAnd here is all what they contain :
pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ sudo cat biometryd.log Terminated Killed pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ sudo cat urfkill.log Terminated pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ sudo cat lightdm.log Failed to get D-Bus connection pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ sudo cat udev.log starting version 229 pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ sudo cat hwclock-save.log hwclock: Cannot access the Hardware Clock via any known method. hwclock: Use the --debug option to see the details of our search for an access method. pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ sudo cat system-watchdog.log touch: cannot touch '/userdata/.last_watchdog_reboot': No such file or directory touch: cannot touch '/userdata/.last_watchdog_reboot': No such file or directory touch: cannot touch '/userdata/.last_watchdog_reboot': No such file or directory touch: cannot touch '/userdata/.last_watchdog_reboot': No such file or directory touch: cannot touch '/userdata/.last_watchdog_reboot': No such file or directory pulsar33@Minerve:/media/pulsar33/root/var/log/upstart$ cd ../ubuntu-download-manager/ pulsar33@Minerve:/media/pulsar33/root/var/log/ubuntu-download-manager$ cat .log20191020-185955.2080 Log file created at: 2019/10/20 18:59:55 Running on machine: ubuntu-phablet Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg I1020 18:59:55.082846 2080 base_daemon.cpp:204] Timeout is enabled: 1 I1020 18:59:55.083389 2080 base_daemon.cpp:206] Daemon is stoppable: 0 I1020 18:59:55.087118 2080 downloads_db.cpp:151] Db file is /var/cache/ubuntu-download-manager/downloads.db I1020 18:59:55.126965 2080 network_session.cpp:100] Instance is null I1020 18:59:55.127024 2080 network_session.cpp:103] Create new instance I1020 18:59:55.222091 2080 network_session.cpp:68] Connection type 802-3-ethernet I1020 18:59:55.222759 2080 manager.cpp:113] virtual void Ubuntu::DownloadManager::Daemon::DownloadManager::setAcceptedCertificates(const QList<QSslCertificate>&) I1020 18:59:55.223557 2080 base_daemon.cpp:122] Service registered to com.canonical.applications.Downloader I1020 19:00:25.228682 2080 base_daemon.cpp:152] Timeout reached, shutdown service.Not so useful I guess
BR
Pulsar33 -
@alan_g
Hi Alan!
The unity8 log pastebin was already linked in the first post of this thread. Sorry I thought that it was convenient to put it there. Here the link to the unity8 log pastebin.@Pulsar33 for the unity8 log you have to do this:
cat /.cache/upstart/unity8.log -
Sorry, I miss that all logs in /home/phablet/.cache where not seen.
Same log as you ...
Pulsar33 -
@Aury88 sorry, I didn't read the whole thread, just from the point you pinged me.
That log isn't related to https://github.com/MirServer/mir/issues/704 where one of the DRM functions returns a misleading result. Instead it looks like the graphics driver isn't adequately supported by Mesa.
I know that my colleagues at Canonical have yet to get graphics working on the Pi4 with Ubuntu Core (I think that's lack of time, not a technical issue). But maybe you can find something useful here: https://forum.snapcraft.io/t/support-for-raspberry-pi-4/11970
For example:
you might need to play with the dtoverlay= kms or fkms values in config.txt. i know the vc4 driver isnt fully ready to drive the vc5 hardware in the pi4 but i know that for example my omxplayer-pi snap works fine (only 1080p though, omxplayer does not support h265 yet) when either using no dtoverlay or with the fkms one (not with the kms one though). - https://forum.snapcraft.io/t/support-for-raspberry-pi-4/11970/17
-
@alan_g thank you.! I will try that.
-
Hello
Don't know what to do.
And you ?
BR
Pulsar33 -
No @Pulsar33, we mortals are all stuck with the compositor error. also I can access only the first time to the session. it asks to set a name to the device but in the following boots, after login (with phablet or the chosen name is the same) it start a wrongly orientated login interface without keyboard recognition and the impossibility to use the virtual keyboard due to the compositor problem.... also I am not able to access the console mode
-
Thank you for the answer
Is your build the last successful one #44 created today ?
I can't test it before a few days but I will asap
BR
Pulsar33 -
@Pulsar33 yes. the #44 have a working GUI (but still not the compositor).
-
Warning!: the last rootfs-rpi build (#51) has not the GUI.
Here thecat /.cache/upstart/unity8.logpastebin -
Hello,
Things are moving on the raspberrypi.org forum. An Ubuntu sub-forum has been open in Operating System distributions / Other and an old thread about Unity has been updated. A few members are posting.
BR
Pulsar33
