Cant get ext-screen to work with ext-pir

Arhum123

I see the ext-screen count down and the screen goes black after the timer but no motion is turning it back on. The pir is hooked up correct to gpio:11

[24.08.2022 00:26.17.229] [LOG]   [PIR] Initialize...
[24.08.2022 00:26.17.231] [LOG]   [PIR] All needed @bugsounet library loaded !
[24.08.2022 00:26.17.233] [LOG]   [PIR] PIR Library v1.1.0 Initialized...
[24.08.2022 00:26.17.242] [LOG]   [PIR] Callback Notification: PIR_INITIALIZED 
[24.08.2022 00:26.17.245] [LOG]   [PIR] Start
[24.08.2022 00:26.17.254] [LOG]   [PIR] Callback Notification: PIR_STARTED 
[24.08.2022 00:26.17.256] [LOG]   [PIR] Initialize Complete Version: 1.0.1 rev: 220403

here is my log, ext-alert doesn’t mention anything about the pir

		{
		  module: 'EXT-Pir',
		  config: {
		    debug: true,
		    gpio: 11,
		    reverseValue: false
		  }
		},
		{
		  module: 'EXT-Screen',
		  position: 'top_left',
		  config: {
		    delay: 2 * 60 * 1000
		  }
		},

here is my config.js file

venditti69500

@Arhum123 I think you should add an option to “mode” your EXT-Screen config

venditti69500

@Arhum123 try :

{
  module: 'EXT-Screen',
  position: 'top_left',
  config: {
    ...
    mode: 1, // Set your mode choice (1 to 6)
},

bugsounet

and what EXT-Alert says ?

Arhum123

@bugsounet alert does not mention anything about the modules

Arhum123

@venditti69500 I added that but nothing happened, what does mode do? how do I know which number to put?

bugsounet

how do I know which number to put?

wiki can help …
I know nobody read it but this info is inside

It seams to be a driver/firmware problem with vc4-kms-v3d driver.
The command to verify screen state always return “screen is on”

Can Try this:

sudo nano /boot/config.txt

scroll down to [pi4] section
Change dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

Save the file, reboot your pi and test with default config

Arhum123

@bugsounet I opened up the config and the above settings were already there

What could the issue be?

Olive974

Hello Cedric @bugsounet ,

i have the same problem, i try

dtoverlay=vc4-fkms-v3d

but my screen never goes OFF (i mean really shutoff).

Before i use 2 shell script with PIR.py : one shutoff : vcgencmd display_power 0 2 and one power on : vcgencmd display_power 1 2 but it doesnt work anymore too…

any idea please?

It related to my last update of RaspiOS

Olive974

@Arhum123 have you found a solution please?

bugsounet

I use this in /boot/config.txt

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=1
#hdmi_mode=1

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=1800
#over_voltage=2
#arm_freq=1750
over_voltage=6
arm_freq=2000
#gpu_freq=750

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d-pi4
#dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d

Warn:

it’s MY personal config for my pi4 and Overclocked to 2Ghz ! (tested and stable -> uptime ~250 days)
don’t forget to make a backup of your own file

and EXT-Screen works

mecco86

Hello, goodmorning, i have same problem, when i start my myrror, i have this alert:

MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast: /usr/lib/dri/kms_swrast_dri.so: impossibile aprire il file oggetto condiviso: Permesso negato (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast: /usr/lib/dri/swrast_dri.so: impossibile aprire il file oggetto condiviso: Permesso negato (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver

how i can solve this?
thanks

kevinoue

Make sure you are using the GPIO numbering system and not the Actual pinout.
GPIO 11 is the same as Physical pin #23

You must also use mode: 1-7 in your code if you want to turn your monitor off. Otherwise it will just Blank the screen. The definitions for the modes are explained in the Wiki.

Without using mode, it will only blank your screen, which makes me think you have the incorrect pin setting.

kevinoue

@Olive974
Hi, please see my post, https://forum.bugsounet.fr/topic/1260/screen-does-not-go-to-sleep

It sounds like you have the same problem I was having.

Unsolved Cant get ext-screen to work with ext-pir