Announcement

Collapse
No announcement yet.

Error message after installing 4DPI 24 HAT monitor

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error message after installing 4DPI 24 HAT monitor

    Hi folks!

    NOOBS SD card
    RASPBIAN JESSIE with VLC installed
    RASPBERRY PI2
    WiFI USB stick
    32 GB USBDISK with video, music,images
    ALL worked fine before 4DPI-24-HAT installation

    After this small monitor been installed following Quick Start Guide from 4DPI, Raspbian desktop is now visible on the 4DPI (hopefully YES !)
    BUT
    ERROR message : NO session for PID xxx
    AND
    Not possible to mount my USBDISK anymore !! (Unfortunately Oh No!)
    Makes me crazy! As my aim in buying the 4DPI monitor was to use VLC for my videos, sounds and images on the USBDISK!
    HELP

    Other question: Will it be possible to have OPENELEC KODI 16 (also on my NOOBS boot) running along with 4DPI monitor ? Hummm ?

    I am afraid I am a newbie in the LINUX world but I'll do my best to have a multimedia GUI !

    Jean from France
    Last edited by jean Gaillat; 14 October 2015, 02:55 AM.

  • #2
    Hope my English not too poor ? I can't figure out what's wrong ! Nobody seems to have been in front of the same issue? These associated devices were so appealing!

    Comment


    • #3
      Hello Jean

      Sorry for the delay in reply. We have been trying to figure out what problem you have, as we cannot replicate the same issue here.
      We were discussing this yesterday and into the night also.

      So you are using the new NOOBS version of Raspbian, which is Jessie rather than Wheezy, right?
      One of our engineers did this, and everything was still working correctly.

      We are currently building a new package for the later Kernel, which might help your problem, as our current 4DPi install package is for a 3.8 kernel and I am not 100% sure what the new NOOBs Jessie build kernel is, do you know this information?

      Did you start with a fresh installation of NOOBs, and then load the package for the 4DPi, and the problem with USB happened right away?
      I am not sure what this PID issue is you have though, we did not experience this.

      Someone will continue to work on this today and will reply to you, and we will have a new installation package available soon too.

      Regards
      James

      Comment


      • #4
        Thx a lot for trying to solve that! I have just bought a Raspberry 2 with NOOBS SD card from FARNELL, 2 weeks ago.
        Was perfect when booting with OPEN ELEC that I have updated with KODI 16 - HDMI monitor used in this first experience.
        Have installed a 32 GB USB disk and a WiFI USB dongle. Both perfectly recognized and mounted by KODI
        Was possible to watch my films, listen to my Music, see my images or connect to the Internet listening Radios
        KODI 16 is great.

        Then I have bought your 4DPi 24 monitor thinking it was possible to use OPEN ELEC with it.
        Disappointed when I have been told it works just under RASPBIAN ( As my very first aim was to have a tiny multimedia system under KODI)

        So reboot on NOOBS. Install RASPBIAN.
        Trying first with HDMI monitor.
        OK to see my USB DISK.Not the WiFi dongle.
        Installed VLC with Ethernet cable
        OK to listen music,see films and images.

        Then install your codes after reading Quick Start Guide from 4DPI,
        Raspbian desktop is now visible on the 4DPI but can't see the complete screen and windows. I cant figure out how to have complete screen resolution on it.

        And the worst:
        ERROR message : NO session for PID xxx
        AND
        Not possible to mount my USBDISK anymore !!
        So now I am waiting for your answer as I am not a LINUX code expert.

        Last but not least: do you plan to develop something so as it shoud work under OpenElec or is not possible at all?

        Anyway. Experimenting new devices and ideas is something I like so much. I like your 4DPi device.
        Great dommage if I can't use it for my project.
        You know that if it works you can be certain I 'll promote this to all my Geek friends in my neighbourhood.

        I send you Le Bonjour from France.

        Jean


        Comment


        • #5
          Hello again Jean

          I am not even sure what KODI is, so you are a few steps ahead of me.
          In the datasheet of the 4DPi-24-HAT it states its only compatible with Rasbian. So getting it to work under something else will be up to you to do, as this is an open source platform.

          The resolution of the 4DPi-24-HAT is 320x240 pixels, so obviously you will not be able to see the full desktop and screen that you would have on your HDMI monitor, which is likely 1920x1080 or something like that. You cant just change the resolution on the 4DPi as it has finite number of pixels.

          I still dont know what this PID error is you are talking about, or where you are seeing it. Can you explain more when and where this occurs, and possibly take some photos?

          Unsure why the 4DPi would be affecting your USB. Can you please tell me the Kernel version of the Raspian installation you are using, prior to installing the 4DPi software.

          Open Elec, again, you are going to have to do some work yourself if you want to port the 4DPi-24-HAT over to this. It was designed specifically to run on Raspbian. however we have the source code available if you want to build your own kernel etc for Open Elec, which may give you a stepping stone to doing what you want.

          https://bitbucket.org/4DPi/4d-hats/src

          Regards
          James

          Comment


          • #6
            Hi again

            Using the uname -a command I have obtained the Linux kernel:
            Linux raspberrypi 3.18.11-v7+ #13 SMP PREEMPT Fri Jul 24 07:42:47 CEST 2015 armv 7l GNU/Linux

            Then using the command /opt/vc/bin/vcgencmd version I have obtained:
            Sep 23 2015 12:12:01
            Copyright (c) 2012 Broadcom
            version c156d00b148c30a3ba28ec376c9c01e95a77d6d5 (clean) (release)

            VoilĂ  !

            Regarding the error message see the attached picture.

            Regardin OPEN ELEC I am afraid I am not a LINUX expert and it will not be possible for me to try.
            Anyway I will be happy if it works under Raspbian to access my files on the USB DISK and watch my video, listem my music, see my pictures with VLC.

            Thx for your effort

            Jean


            Attached Files

            Comment


            • #7
              Usin the ps aux command I have found what is the pid 692 which has no session error message :it is lxpolkit ( I am amazed by my own capacity to find how to search with the great help of my friend INTERNET !!!)

              [email protected] ~ $ ps aux
              USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
              root 1 0.0 0.4 5532 4012 ? Ss oct.13 0:06 /sbin/init
              root 2 0.0 0.0 0 0 ? S oct.13 0:00 [kthreadd]
              root 3 0.0 0.0 0 0 ? S oct.13 0:00 [ksoftirqd/0]
              root 5 0.0 0.0 0 0 ? S< oct.13 0:00 [kworker/0:0H]
              root 7 0.0 0.0 0 0 ? S oct.13 0:01 [rcu_preempt]
              root 8 0.0 0.0 0 0 ? S oct.13 0:00 [rcu_sched]
              root 9 0.0 0.0 0 0 ? S oct.13 0:00 [rcu_bh]
              root 10 0.0 0.0 0 0 ? S oct.13 0:00 [migration/0]
              root 11 0.0 0.0 0 0 ? S oct.13 0:00 [migration/1]
              root 12 0.0 0.0 0 0 ? S oct.13 0:00 [ksoftirqd/1]
              root 14 0.0 0.0 0 0 ? S< oct.13 0:00 [kworker/1:0H]
              root 15 0.0 0.0 0 0 ? S oct.13 0:00 [migration/2]
              root 16 0.0 0.0 0 0 ? S oct.13 0:00 [ksoftirqd/2]
              root 18 0.0 0.0 0 0 ? S< oct.13 0:00 [kworker/2:0H]
              root 19 0.0 0.0 0 0 ? S oct.13 0:00 [migration/3]
              root 20 0.0 0.0 0 0 ? S oct.13 0:00 [ksoftirqd/3]
              root 22 0.0 0.0 0 0 ? S< oct.13 0:00 [kworker/3:0H]
              root 23 0.0 0.0 0 0 ? S< oct.13 0:00 [khelper]
              root 24 0.0 0.0 0 0 ? S oct.13 0:00 [kdevtmpfs]
              root 25 0.0 0.0 0 0 ? S< oct.13 0:00 [netns]
              root 26 0.0 0.0 0 0 ? S< oct.13 0:00 [perf]
              root 27 0.0 0.0 0 0 ? S oct.13 0:00 [khungtaskd]
              root 28 0.0 0.0 0 0 ? S< oct.13 0:00 [writeback]
              root 29 0.0 0.0 0 0 ? S< oct.13 0:00 [crypto]
              root 30 0.0 0.0 0 0 ? S< oct.13 0:00 [bioset]
              root 31 0.0 0.0 0 0 ? S< oct.13 0:00 [kblockd]
              root 33 0.0 0.0 0 0 ? S< oct.13 0:00 [rpciod]
              root 35 0.0 0.0 0 0 ? S oct.13 0:00 [kswapd0]
              root 36 0.0 0.0 0 0 ? S oct.13 0:00 [fsnotify_mark]
              root 37 0.0 0.0 0 0 ? S< oct.13 0:00 [nfsiod]
              root 43 0.0 0.0 0 0 ? S< oct.13 0:00 [kthrotld]
              root 44 0.0 0.0 0 0 ? S oct.13 0:03 [spi0]
              root 45 0.0 0.0 0 0 ? S oct.13 0:00 [kworker/u8:1]
              root 50 0.0 0.0 0 0 ? S< oct.13 0:00 [VCHIQ-0]
              root 51 0.0 0.0 0 0 ? S< oct.13 0:00 [VCHIQr-0]
              root 52 0.0 0.0 0 0 ? S< oct.13 0:00 [VCHIQs-0]
              root 53 0.0 0.0 0 0 ? S< oct.13 0:00 [iscsi_eh]
              root 54 0.0 0.0 0 0 ? S< oct.13 0:00 [dwc_otg]
              root 55 0.0 0.0 0 0 ? S< oct.13 0:00 [DWC Notificatio]
              root 56 0.0 0.0 0 0 ? S oct.13 0:00 [VCHIQka-0]
              root 57 0.0 0.0 0 0 ? S< oct.13 0:00 [SMIO]
              root 58 0.0 0.0 0 0 ? S< oct.13 0:00 [deferwq]
              root 59 0.0 0.0 0 0 ? S oct.13 0:01 [kworker/u8:2]
              root 60 0.0 0.0 0 0 ? S oct.13 0:00 [mmcqd/0]
              root 63 0.0 0.0 0 0 ? S oct.13 0:00 [jbd2/mmcblk0p8-]
              root 64 0.0 0.0 0 0 ? S< oct.13 0:00 [ext4-rsv-conver]
              root 65 0.0 0.0 0 0 ? S< oct.13 0:00 [ipv6_addrconf]
              root 66 0.0 0.0 0 0 ? S oct.13 0:00 [scsi_eh_0]
              root 67 0.0 0.0 0 0 ? S< oct.13 0:00 [scsi_tmf_0]
              root 69 0.0 0.0 0 0 ? S oct.13 0:00 [usb-storage]
              root 103 0.0 0.0 0 0 ? S oct.13 0:00 [kauditd]
              root 105 0.0 0.0 0 0 ? S oct.13 0:02 [kworker/3:2]
              root 115 0.0 0.3 9728 2832 ? Ss oct.13 0:01 /lib/systemd/systemd-journald
              root 117 0.0 0.3 11792 2948 ? Ss oct.13 0:00 /lib/systemd/systemd-udevd
              root 230 0.0 0.0 0 0 ? S oct.13 0:01 [kworker/2:2]
              root 452 0.0 0.0 0 0 ? S< oct.13 0:00 [cfg80211]
              root 523 0.0 0.2 5012 2464 ? Ss oct.13 0:00 /usr/sbin/cron -f
              root 525 0.0 0.4 7796 4268 ? Ss oct.13 0:00 /usr/sbin/sshd -D
              root 527 0.0 0.2 3824 2384 ? Ss oct.13 0:00 /lib/systemd/systemd-logind
              root 536 0.0 0.3 7620 3236 ? S oct.13 0:00 sudo -u pi FRAMEBUFFER=/dev/fb1 startx
              avahi 539 0.0 0.2 3848 2580 ? Ss oct.13 0:00 avahi-daemon: running [raspberrypi.local]
              message+ 540 0.0 0.3 5584 3016 ? Ss oct.13 0:00 /usr/bin/dbus-daemon --system --address=systemd: --
              pi 549 0.0 0.1 1888 1148 ? S oct.13 0:00 /bin/sh /usr/bin/startx
              nobody 574 0.0 0.1 2264 1428 ? Ss oct.13 0:00 /usr/sbin/thd --daemon --triggers /etc/triggerhappy
              avahi 592 0.0 0.0 3848 240 ? S oct.13 0:00 avahi-daemon: chroot helper
              ntp 595 0.0 0.4 5656 3676 ? Ss oct.13 0:01 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 107:112
              root 610 0.0 0.3 32116 2836 ? Ssl oct.13 0:00 /usr/sbin/rsyslogd -n
              pi 613 0.0 0.1 3204 1500 ? S oct.13 0:00 xinit /etc/X11/xinit/xinitrc -- /etc/X11/xinit/xser
              root 614 0.0 1.2 20096 11092 tty2 Ss+ oct.13 0:06 /usr/bin/X -nolisten tcp :0 -auth /tmp/serverauth.5
              root 628 0.0 0.5 35832 5316 ? Ssl oct.13 0:00 /usr/sbin/lightdm
              root 630 0.0 0.3 5096 2828 tty1 Ss oct.13 0:00 /bin/login -f
              root 631 0.0 0.2 3844 1968 ? Ss+ oct.13 0:00 /sbin/agetty --keep-baud 115200 38400 9600 ttyAMA0
              root 636 0.0 0.5 12312 5084 tty7 Ss+ oct.13 0:00 /usr/bin/X :1 -seat seat0 -auth /var/run/lightdm/ro
              pi 641 0.0 1.2 50824 11748 ? Sl oct.13 0:00 /usr/bin/lxsession -s LXDE-pi -e LXDE
              pi 665 0.0 0.0 3672 220 ? Ss oct.13 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with
              pi 668 0.0 0.1 3664 1592 ? S oct.13 0:00 /usr/bin/dbus-launch --exit-with-session x-session-
              pi 669 0.0 0.2 5576 2088 ? Ss oct.13 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-a
              pi 675 0.0 0.6 30948 5712 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfsd
              pi 679 0.0 0.4 46160 4452 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfsd-fuse /home/pi/.gvfs -f -o big_w
              pi 689 0.0 1.2 19944 11124 ? S oct.13 0:00 openbox --config-file /home/pi/.config/openbox/lxde
              pi 692 0.0 1.7 34636 15752 ? Sl oct.13 0:00 lxpolkit
              pi 694 0.1 2.3 88936 21896 ? Sl oct.13 0:24 lxpanel --profile LXDE-pi
              pi 695 0.0 1.8 73652 17420 ? Sl oct.13 0:00 pcmanfm --desktop --profile LXDE-pi
              pi 702 0.0 0.0 3672 220 ? Ss oct.13 0:00 /usr/bin/ssh-agent -s
              pi 710 0.0 0.8 41940 7420 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
              root 718 0.0 0.7 54672 6580 ? Ssl oct.13 0:00 /usr/lib/udisks2/udisksd --no-debug
              root 722 0.0 0.6 36324 5748 ? Ssl oct.13 0:00 /usr/lib/policykit-1/polkitd --no-debug
              pi 782 0.0 0.7 42376 6464 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
              root 786 0.0 0.0 2020 172 ? Ss oct.13 0:00 /sbin/dhcpcd
              pi 791 0.0 0.3 4916 3192 ? Ss oct.13 0:00 /lib/systemd/systemd --user
              pi 793 0.0 0.1 6756 1384 ? S oct.13 0:00 (sd-pam)
              pi 797 0.0 0.5 30912 5432 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
              pi 798 0.0 0.4 6408 4336 tty1 S+ oct.13 0:00 -bash
              pi 804 0.0 0.5 29892 5148 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
              pi 808 0.0 0.5 29996 5468 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor
              pi 822 0.0 0.6 59208 6232 ? Sl oct.13 0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/g
              pi 823 0.0 0.5 28224 4844 ? Ssl oct.13 0:00 /usr/lib/menu-cache/menu-cached /tmp/.menu-cached-:
              root 841 0.0 0.0 0 0 ? S oct.13 0:03 [kworker/0:0]
              root 895 0.0 0.0 0 0 ? S oct.13 0:00 [kworker/3:0]
              root 937 0.0 0.5 11624 5100 ? Ss oct.13 0:00 sshd: pi [priv]
              pi 939 0.0 0.4 11760 3748 ? R oct.13 0:00 sshd: [email protected]/0
              pi 940 0.0 0.4 6408 4324 pts/0 Ss oct.13 0:00 -bash
              root 956 0.0 0.0 0 0 ? S oct.13 0:00 [kworker/2:1]
              root 957 0.0 0.0 0 0 ? S oct.13 0:00 [kworker/0:2]
              root 958 0.0 0.0 0 0 ? S oct.13 0:00 [kworker/1:0]
              root 960 0.0 0.0 0 0 ? D oct.13 0:00 [kworker/1:1]
              root 963 0.0 0.0 0 0 ? S 00:01 0:00 [kworker/0:1]
              pi 964 0.0 0.2 4712 2156 pts/0 R+ 00:03 0:00 ps aux

              Comment


              • #8
                Does this help?

                https://www.raspberrypi.org/forums/v...09333&p=754170
                James

                Comment


                • #9
                  Just like you I have discovered this discussion but as I told you it is of no help for me because I am not enough expert in LINUX language and coding.
                  You know I am coming from the Windows world. Some friends of mine were telling me that the free Linux world was much more easy to use. But as far as I know at that time it is not so obvious...Debian Raspbian GNU Linux what a mess!
                  Anyway tons of discussions to discover and like a police enquiry try to find out the shameful codes! This will improve my English for sure!
                  Forward men!

                  Jean

                  Comment


                  • #10
                    USB problems are often related to power supply - there are quite some devices in your system. Is the RPi's power LED (red) permanently on or is it blinking (blinking = too weak power supply)? You can also leave HAT drivers installed, just disconnect the HAT and try if USB disk works...

                    Comment


                    • #11
                      Hi

                      I have already checked that the power supply was ok (in fact that was the very first thing I have checked).
                      But following your last message I have disconnected the HAT and launched an SSH session through my PC.
                      I have launched a ps aux command to see the tasks which are running in the Pi.
                      What interesting thing I noticed is that there is no more lxpolkit process running!
                      see below :

                      [email protected] ~ $ ps aux
                      USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
                      root 1 3.4 0.4 5460 4004 ? Ss 19:05 0:06 /sbin/init
                      root 2 0.0 0.0 0 0 ? S 19:05 0:00 [kthreadd]
                      root 3 0.0 0.0 0 0 ? S 19:05 0:00 [ksoftirqd/0]
                      root 4 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/0:0]
                      root 5 0.0 0.0 0 0 ? S< 19:05 0:00 [kworker/0:0H]
                      root 6 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/u8:0]
                      root 7 0.0 0.0 0 0 ? S 19:05 0:00 [rcu_preempt]
                      root 8 0.0 0.0 0 0 ? S 19:05 0:00 [rcu_sched]
                      root 9 0.0 0.0 0 0 ? S 19:05 0:00 [rcu_bh]
                      root 10 0.0 0.0 0 0 ? S 19:05 0:00 [migration/0]
                      root 11 0.0 0.0 0 0 ? S 19:05 0:00 [migration/1]
                      root 12 0.0 0.0 0 0 ? S 19:05 0:00 [ksoftirqd/1]
                      root 13 0.2 0.0 0 0 ? S 19:05 0:00 [kworker/1:0]
                      root 14 0.0 0.0 0 0 ? S< 19:05 0:00 [kworker/1:0H]
                      root 15 0.0 0.0 0 0 ? S 19:05 0:00 [migration/2]
                      root 16 0.0 0.0 0 0 ? S 19:05 0:00 [ksoftirqd/2]
                      root 17 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/2:0]
                      root 18 0.0 0.0 0 0 ? S< 19:05 0:00 [kworker/2:0H]
                      root 19 0.0 0.0 0 0 ? S 19:05 0:00 [migration/3]
                      root 20 0.0 0.0 0 0 ? S 19:05 0:00 [ksoftirqd/3]
                      root 21 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/3:0]
                      root 22 0.0 0.0 0 0 ? S< 19:05 0:00 [kworker/3:0H]
                      root 23 0.0 0.0 0 0 ? S< 19:05 0:00 [khelper]
                      root 24 0.0 0.0 0 0 ? S 19:05 0:00 [kdevtmpfs]
                      root 25 0.0 0.0 0 0 ? S< 19:05 0:00 [netns]
                      root 26 0.0 0.0 0 0 ? S< 19:05 0:00 [perf]
                      root 27 0.0 0.0 0 0 ? S 19:05 0:00 [khungtaskd]
                      root 28 0.0 0.0 0 0 ? S< 19:05 0:00 [writeback]
                      root 29 0.0 0.0 0 0 ? S< 19:05 0:00 [crypto]
                      root 30 0.0 0.0 0 0 ? S< 19:05 0:00 [bioset]
                      root 31 0.0 0.0 0 0 ? S< 19:05 0:00 [kblockd]
                      root 32 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/1:1]
                      root 33 0.0 0.0 0 0 ? S< 19:05 0:00 [rpciod]
                      root 34 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/0:1]
                      root 35 0.0 0.0 0 0 ? S 19:05 0:00 [kswapd0]
                      root 36 0.0 0.0 0 0 ? S 19:05 0:00 [fsnotify_mark]
                      root 37 0.0 0.0 0 0 ? S< 19:05 0:00 [nfsiod]
                      root 43 0.0 0.0 0 0 ? S< 19:05 0:00 [kthrotld]
                      root 44 0.0 0.0 0 0 ? S< 19:05 0:00 [VCHIQ-0]
                      root 45 0.0 0.0 0 0 ? S< 19:05 0:00 [VCHIQr-0]
                      root 46 0.0 0.0 0 0 ? S< 19:05 0:00 [VCHIQs-0]
                      root 47 0.0 0.0 0 0 ? S< 19:05 0:00 [iscsi_eh]
                      root 48 0.0 0.0 0 0 ? S< 19:05 0:00 [dwc_otg]
                      root 49 0.0 0.0 0 0 ? S< 19:05 0:00 [DWC Notificatio]
                      root 50 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/u8:1]
                      root 51 0.0 0.0 0 0 ? S 19:05 0:00 [VCHIQka-0]
                      root 52 0.0 0.0 0 0 ? S< 19:05 0:00 [SMIO]
                      root 53 0.0 0.0 0 0 ? S< 19:05 0:00 [deferwq]
                      root 54 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/u8:2]
                      root 55 0.1 0.0 0 0 ? S 19:05 0:00 [mmcqd/0]
                      root 56 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/1:2]
                      root 57 0.0 0.0 0 0 ? S 19:05 0:00 [jbd2/mmcblk0p8-]
                      root 58 0.0 0.0 0 0 ? S< 19:05 0:00 [ext4-rsv-conver]
                      root 59 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/2:1]
                      root 60 0.0 0.0 0 0 ? S< 19:05 0:00 [ipv6_addrconf]
                      root 72 0.0 0.0 0 0 ? S 19:05 0:00 [scsi_eh_0]
                      root 73 0.0 0.0 0 0 ? S< 19:05 0:00 [scsi_tmf_0]
                      root 74 0.0 0.0 0 0 ? S 19:05 0:00 [usb-storage]
                      root 81 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/3:1]
                      root 87 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/u8:3]
                      root 88 0.0 0.0 0 0 ? S< 19:05 0:00 [kworker/0:1H]
                      root 100 0.0 0.0 0 0 ? S 19:05 0:00 [kauditd]
                      root 102 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/2:2]
                      root 112 0.5 0.2 9728 2736 ? Ss 19:05 0:00 /lib/systemd/systemd-journald
                      root 113 0.2 0.3 11792 3112 ? Ss 19:05 0:00 /lib/systemd/systemd-udevd
                      root 128 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/3:2]
                      root 204 0.0 0.0 0 0 ? S 19:05 0:00 [kworker/0:2]
                      root 442 0.0 0.0 0 0 ? S< 19:05 0:00 [cfg80211]
                      root 510 0.0 0.2 5012 2332 ? Ss 19:05 0:00 /usr/sbin/cron -f
                      root 512 0.0 0.4 7796 4232 ? Ss 19:05 0:00 /usr/sbin/sshd -D
                      root 514 0.0 0.2 3824 2372 ? Ss 19:05 0:00 /lib/systemd/systemd-logind
                      avahi 527 0.0 0.2 3848 2556 ? Ss 19:05 0:00 avahi-daemon: running [raspberrypi.local]
                      message+ 530 0.1 0.3 5464 2968 ? Ss 19:05 0:00 /usr/bin/dbus-daemon --system --address=system
                      nobody 555 0.0 0.1 2264 1444 ? Ss 19:05 0:00 /usr/sbin/thd --daemon --triggers /etc/trigger
                      ntp 565 0.0 0.3 5656 3660 ? Ss 19:05 0:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 107:
                      avahi 566 0.0 0.0 3848 240 ? S 19:05 0:00 avahi-daemon: chroot helper
                      root 579 0.0 0.2 32116 2620 ? Ssl 19:05 0:00 /usr/sbin/rsyslogd -n
                      root 597 0.0 0.3 5096 2828 tty1 Ss 19:05 0:00 /bin/login -f
                      root 598 0.0 0.2 3844 1956 ? Ss+ 19:05 0:00 /sbin/agetty --keep-baud 115200 38400 9600 tty
                      root 707 0.0 0.0 2020 172 ? Ss 19:05 0:00 /sbin/dhcpcd
                      pi 710 0.0 0.3 4916 3216 ? Ss 19:05 0:00 /lib/systemd/systemd --user
                      pi 712 0.0 0.1 6684 1380 ? S 19:05 0:00 (sd-pam)
                      pi 714 0.3 0.4 6408 4296 tty1 S+ 19:05 0:00 -bash
                      root 724 0.2 0.5 11624 5100 ? Ss 19:05 0:00 sshd: pi [priv]
                      pi 726 0.0 0.4 11624 3748 ? S 19:05 0:00 sshd: [email protected]/0
                      pi 727 0.2 0.4 6408 4324 pts/0 Ss 19:05 0:00 -bash
                      pi 738 0.0 0.2 4712 2168 pts/0 R+ 19:08 0:00 ps aux

                      Anyway this evening I am tired to fight against something I can't solve by myself.
                      So I plan to reboot from a fresh RASPBIAN SD card (not from NOOBS) and follow strictly your Quick Start Guide.
                      I have just to find an SD card in my drawers.

                      Jean

                      Comment


                      • #12
                        When the HAT is disconnected, I have switched to HDMI using the command startx -- -layout HDMI
                        I can see the RASPBIAN desktop on my HDMI monitor
                        No error message window pop-up
                        And I see the USBDISK!
                        But when I want to browse files in it using VLC the system ask for an authentication Password in the Identity : root
                        And I dont know what Password to enter.

                        So now I give up!

                        Comment


                        • #13
                          In fact I was obliged to get Super User rights using SUDO command within SSH
                          Then I can see the mounted UB DISK and access to it in the RASPBIAN desktop.
                          Too complicated for me. I understand that there several level of rights.
                          OK now I format a fresh SD card and will try to install a new RASPBIAN boot. I get rid of NOOBS!

                          Comment


                          • #14
                            Now I have re booted with a fresh RASPBIAN JESSIE on a new SD card.
                            (found at http://downloads.raspberrypi.org/raspbian_latest)
                            No NOOBS.
                            I have done exactly what is written on your Quickstart Guide.(the paper version which was in the box with the HAT)
                            Checked that before installing your piece of code for the HAT before connecting the HAT, I can see the USB DISK an no error message, all worked fine.

                            And, after entering your codes and connecting the HAT and reboot, guess what?

                            I see the RASPBIAN desktop on the HAT but same error message again !!!!!! NO session for PID xxx where xxx is the lxpolkit PID.
                            ( I have done again ps aux to check)
                            USB disk not accessible and can't mount it.

                            There is something wrong with your HAT piece of code when used with the RASPBIAN JESSIE image. I am afraid.

                            Jean
                            Last edited by jean Gaillat; 15 October 2015, 06:38 AM.

                            Comment


                            • #15
                              Hi Jean

                              Very strange, we have not seen this before, but that said Jessie is just new out, so maybe there is an issue with Jessie compatibility. Previously it was Wheezy.

                              There is a new package for the 4DPi which we are in the middle of testing. You are welcome to download and try this if you wish, on a fresh install of Jessie, and see how you get on. It uses the later Kernel, which may be part of the issue if Jessie uses a newer kernel than what our package for the 4DPi comes with. Essentially the Jessie Kernel may be downgraded when you install the 4DPi, which then might cause issues after the reboot. Not sure at this moment.

                              As I say, Jessie is just recently released so may be the reason why.

                              Please try this and let me know how you get on: http://www.4dsystems.com.au/download...10_v1.0.tar.gz

                              Regards
                              James

                              Comment

                              Working...
                              X