• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Raspberry Pi 4 Model B

Scheduled Pinned Locked Moved UT for Raspberry Pi
69 Posts 8 Posters 22.7k Views 4 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      Pulsar33
      last edited by 16 Oct 2019, 21:21

      Sorry but I didn't understand how to launch the graphical user interface.
      And with a console mode only, I don't see what to do with it ...
      I hope someone will describe the solution.
      BR
      Pulsar33

      Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
      Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
      Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

      1 Reply Last reply Reply Quote 0
      • P Offline
        Pulsar33
        last edited by 18 Oct 2019, 05:08

        Hello,

        Nobody (knows how) is interested in running Ubports in graphical mode on a Raspberry Pi4 ?

        Have a nice day
        Pulsar33

        Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
        Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
        Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

        ? 1 Reply Last reply 18 Oct 2019, 07:15 Reply Quote 0
        • ? Offline
          A Former User @Pulsar33
          last edited by A Former User 18 Oct 2019, 07:15

          Well I, for one, am following UT on Pi with great interest, @Pulsar33.

          I'm still at the "Kernel Panic" stage though, so I can't help much. Sorry.

          1 Reply Last reply Reply Quote 0
          • P Offline
            Pulsar33
            last edited by Pulsar33 18 Oct 2019, 08:38

            Hello,

            Thanks for your answer, @3arn0wl

            To be sure that we all use the same image, here are the sha256sums of the #8 latest stable build (2019 09 25) I use :
            ubuntu-touch-raspberrypi.img.gz febf1ce00e639ae469bf075bce4472b82b25a6d634a147c01d666f1d4f5033c0
            ubuntu-touch-raspberrypi.img 76a47458b90702a156e6f9741b448db5e4d0e5235ec177ae4dea9224e4e7e2b5

            The flashing process on my Linux Mint 19.2 Desktop :

            lsblk   # the SDcard appears as /dev/sdc
            umount /dev/sdc1
            umount /dev/sdc2
            sudo dd bs=4M if=ubuntu-touch-raspberrypi.img of=/dev/sdc status=progress
            

            BR
            Pulsar33

            Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
            Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
            Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

            1 Reply Last reply Reply Quote 1
            • P Offline
              Pulsar33
              last edited by Pulsar33 19 Oct 2019, 08:51

              Still no clue from the GURUs ?
              Please help us to progress and launch the GUI ...
              Best regards
              Pulsar33

              Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
              Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
              Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

              A 2 Replies Last reply 20 Oct 2019, 07:39 Reply Quote 0
              • A Offline
                Aury88 @Pulsar33
                last edited by Aury88 20 Oct 2019, 07:39

                @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_g

                it seems we need to

                --env-hacks MIR_MESA_KMS_DISABLE_MODESET_PROBE
                

                when run mir/unity8 but I don't undestand how...

                A 1 Reply Last reply 20 Oct 2019, 08:10 Reply Quote 0
                • A Offline
                  Aury88 @Pulsar33
                  last edited by Aury88 20 Oct 2019, 07:46

                  also we are using an old rootfs with missing firmwares (last building image is the #8 from 24 September when the firmwares integration in the common rootfs is from 3 October )

                  1 Reply Last reply Reply Quote 0
                  • A Offline
                    alan_g @Aury88
                    last edited by 20 Oct 2019, 08:10

                    @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_g

                    it seems we need to

                    --env-hacks MIR_MESA_KMS_DISABLE_MODESET_PROBE
                    

                    when run mir/unity8 but I don't undestand how...

                    That's just one way to set an environment variable.

                    A 1 Reply Last reply 20 Oct 2019, 08:55 Reply Quote 0
                    • A Offline
                      Aury88 @alan_g
                      last edited by Aury88 20 Oct 2019, 08:55

                      @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 like

                      ENV_NAME=value
                      

                      MIR_MESA_KMS_DISABLE_MODESET_PROBE seem only the name...what is its value? is it"true"?

                      A 1 Reply Last reply 20 Oct 2019, 08:59 Reply Quote 0
                      • A Offline
                        alan_g @Aury88
                        last edited by 20 Oct 2019, 08:59

                        @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 like

                        ENV_NAME=value
                        

                        MIR_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").

                        A 1 Reply Last reply 20 Oct 2019, 09:49 Reply Quote 1
                        • A Offline
                          Aury88 @alan_g
                          last edited by 20 Oct 2019, 09:49

                          no, setting that as an enviroment variable didn't solved the problem... ¯\(ツ)/¯

                          1 Reply Last reply Reply Quote 0
                          • P Offline
                            Pulsar33
                            last edited by 20 Oct 2019, 09:53

                            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

                            Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
                            Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
                            Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

                            A 1 Reply Last reply 20 Oct 2019, 15:38 Reply Quote 0
                            • A Offline
                              Aury88 @Pulsar33
                              last edited by Aury88 20 Oct 2019, 15:38

                              @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 unity8
                              

                              Also you can restart it with

                              restart unity8
                              

                              The 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)

                              A 1 Reply Last reply 20 Oct 2019, 16:22 Reply Quote 1
                              • A Offline
                                alan_g @Aury88
                                last edited by 20 Oct 2019, 16:22

                                @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 unity8
                                

                                Also you can restart it with

                                restart unity8
                                

                                The 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.)

                                A 1 Reply Last reply 20 Oct 2019, 17:10 Reply Quote 0
                                • A Offline
                                  Aury88 @alan_g
                                  last edited by Aury88 20 Oct 2019, 17:10

                                  @alan_g i didn't set that variable throught the terminal session but by editing /etc/environment and ~/.bashrc files

                                  A 1 Reply Last reply 20 Oct 2019, 22:43 Reply Quote 0
                                  • A Offline
                                    alan_g @Aury88
                                    last edited by 20 Oct 2019, 22:43

                                    @Aury88 it might help others help you if you pastebin the Unity8 log.

                                    P A 2 Replies Last reply 21 Oct 2019, 05:06 Reply Quote 0
                                    • P Offline
                                      Pulsar33 @alan_g
                                      last edited by Pulsar33 21 Oct 2019, 05:06

                                      @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.log
                                      
                                      

                                      And 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

                                      Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
                                      Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
                                      Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

                                      1 Reply Last reply Reply Quote 0
                                      • A Offline
                                        Aury88 @alan_g
                                        last edited by Aury88 21 Oct 2019, 05:32

                                        @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
                                        
                                        A 1 Reply Last reply 21 Oct 2019, 08:58 Reply Quote 1
                                        • P Offline
                                          Pulsar33
                                          last edited by 21 Oct 2019, 05:52

                                          Sorry, I miss that all logs in /home/phablet/.cache where not seen.
                                          Same log as you ...
                                          Pulsar33

                                          Aquaris BQ E5 HD UBports OTA-25 (currently testing features)
                                          Aquaris BQ E5 HD Ubuntu Edition Canonical OTA-15 (last Canonical version, daily use)
                                          Raspberry Pi 4 B - 4 GB & 8 GB with various OS and Desktops (UBports not OK)

                                          1 Reply Last reply Reply Quote 0
                                          • A Offline
                                            alan_g @Aury88
                                            last edited by 21 Oct 2019, 08:58

                                            @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

                                            A A 2 Replies Last reply 21 Oct 2019, 15:19 Reply Quote 1
                                            40 out of 69
                                            • First post
                                              40/69
                                              Last post