Display HP S410u possible workling with RaspberryPi

Mahdi2016 · 11-14-2016, 12:40 PM

Hi Michal,

i've built the evdipp package without errors.

After reboot and plug in the HP s140u Monitor and type "sudo monitorsim EDIDv1_1600x900"
a new clear window opened and after 10 seconds the window closed automatically. The output of the terminal window is at follows:

Code:

pi@raspberrypi:~ $ sudo monitorsim EDIDv1_1600x900
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information

Please i need some help and i havent any ideas anymore.

Best regards
Michael

mlukaszek · 11-14-2016, 05:10 PM

Hmm. Try with something simpler first, e.g. the "example" program that you also built.
This won't show any pixels, but will possibly print more to the console, especially if you
enable debug printout (you need to define DEBUG for the build).

What's closing the app? Is it crashing? If yes, then running it in gdb might give some extra clues.

Cheers,
Michal

Mahdi2016 · 11-15-2016, 10:12 AM

Hi Michal,

i've built the evdipp package with debug symbols. The output of the terminal window is at follows:

Code:

(gdb) run
Starting program: /bin/monitorsim edid.dat --enable-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
MESA-LOADER: failed to retrieve device information

Program received signal SIGILL, Illegal instruction.
0x73424de8 in ?? () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0
(gdb)

The output from 'example' command of the terminal window is at follows:

Code:

(gdb) run
Starting program: /bin/example EDIDv1_1280x900 --enable-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Reading the EDID file EDIDv1_1280x900 failed.
[Inferior 1 (process 1822) exited with code 01]
(gdb)

The "edid.dat" is generated with "tvservice -d edid.dat" (for the pluged in HDMI-Monitor).

I hope that helps.

Best regards
Michael

mlukaszek · 11-16-2016, 08:14 AM

What happens if you use a full path to edid file. The message indicates that the program had problems with opening/reading the file that you gave as an argument?

Cheers,
Michal

Mahdi2016 · 11-22-2016, 11:40 AM

Hi Michal,

i'm back from vacation.

Here is the output from 'example' command of the terminal window is at follows:

Code:

(gdb) run
Starting program: /bin/example /home/pi/EDIDv1_1280x900 --enable-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Reading the EDID file /home/pi/EDIDv1_1280x900 failed.
[Inferior 1 (process 962) exited with code 01]

And the output from 'monitorsim' command of the terminal window is at follows:

Code:

Reading symbols from /bin/monitorsim...done.
(gdb) run
Starting program: /bin/monitorsim /home/pi/EDIDv1_1280x900 --enable-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
Reading the EDID file /home/pi/EDIDv1_1280x900 failed.
[Inferior 1 (process 1018) exited with code 01]

I hope that helps.

Best regards
Michael

mlukaszek · 11-22-2016, 12:49 PM

I don't think the file "EDIDv1_1280x900" exists, given that you probably are using EDIDs from Google autotest. You probably meant 1280x800, 1440x900 or 1600x900.

Cheers,
Michal

Mahdi2016 · 11-24-2016, 01:13 PM

Hi Michal,

Here is the output from 'example' command of the terminal window is at follows:

Code:

Starting program: /bin/example /home/pi/EDIDv1_1440x900 --enable-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
Attempting to use device /dev/dri/card1...
[libevdi] ioctl: drop_master error=-1
Press Enter or Ctrl+C to quit...

There was a window without information (title bar with clean and minimal window, to see is a "maximized" symbol as window).

And the output from 'monitorsim' command of the terminal window is at follows:

Code:

(gdb) run
Starting program: /bin/monitorsim /home/pi/EDIDv1_1440x900 --enable-debug
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/arm-linux-gnueabihf/libthread_db.so.1".
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
MESA-LOADER: failed to retrieve device information

Program received signal SIGILL, Illegal instruction.
0x73424de8 in ?? () from /usr/lib/arm-linux-gnueabihf/libcrypto.so.1.0.0

I hope this information will help you..

Best regards
Michael

Mahdi2016 · 12-06-2016, 01:42 PM

Hi Michal,

I have tested as native desktop and with ssh.

Here is the output from 'example' command of the terminal window is at follows:

Code:

sudo /bin/example /home/pi/EDIDv1_1440x900
[libevdi] ioctl: drop_master error=-1
Attempting to use device /dev/dri/card1...
[libevdi] ioctl: drop_master error=-1
Press Enter or Ctrl+C to quit...

In the same time the other window is at follows:

Code:

pi@raspberrypi:~ $ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 2048 x 2048
HDMI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 359mm x 287mm
   1280x1024     60.02*+
   1280x960      60.00
   1024x768      60.00
   800x600       60.32
   640x480       60.00
   720x400       70.08

pi@raspberrypi:~ $ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x43 cap: 0x2, Sink Output crtcs: 3 outputs: 1 associated providers: 0 name:modesetting
Provider 1: id: 0x270 cap: 0x2, Sink Output crtcs: 1 outputs: 1 associated providers: 0 name:modesetting

pi@raspberrypi:~ $ xrandr --setprovideroutputsource 1 0
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  35 ()
  Value in failed request:  0x43
  Serial number of failed request:  16
  Current serial number in output stream:  17

 pi@raspberrypi:~ $ xrandr --auto
(without output)

And here is the output from 'monitorsim' command of the terminal window is at follows:

Code:

pi@raspberrypi:~ $ sudo /bin/monitorsim /home/pi/EDIDv1_1440x900
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
[libevdi] ioctl: drop_master error=-1
No protocol specified
QXcbConnection: Could not connect to display :0

I hope this information will help you.. i havent any ideas anymore.

Best regards
Michael

mlukaszek · 12-07-2016, 08:52 AM

He're how it looks on my Pi - just had a moment to try a few things out. Note this is WITHOUT evdi loaded yet.

Code:

$ uname -a
Linux ubuntupi 4.4.35-v7+ #931 SMP Sat Nov 26 13:05:09 GMT 2016 armv7l armv7l armv7l GNU/Linux

Code:

$ lsmod | grep drm
drm_kms_helper        101028  2 vc4
drm_mipi_dsi            8702  1 vc4
drm                   262564  4 vc4,drm_kms_helper
syscopyarea             2945  1 drm_kms_helper
sysfillrect             3443  1 drm_kms_helper
sysimgblt               2069  1 drm_kms_helper
fb_sys_fops             1309  1 drm_kms_helper

And the most important difference - Sink Offload capability is present:

Code:

$ xrandr --listproviders 
Providers: number : 1
Provider 0: id: 0x43 cap: 0x9, Source Output, Sink Offload crtcs: 3 outputs: 1 associated providers: 0 name:modesetting

I used rpi-update and rpi-source to get the freshest kernel and its sources. What happens if you try the same?

Cheers,
Michal

Mahdi2016 · 12-07-2016, 09:44 AM

Hi Michal,

I use Debian Jessi (raspbian) on my RaspberryPi 2.
The system is up-to-date.

Here is the output from 'uname -a' command of the terminal window is at follows:

Code:

Linux raspberrypi 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l GNU/Linux

Here is the output from 'lsmod | grep drm' command of the terminal window is at follows:

Code:

drm_mipi_dsi            8702  1 vc4
drm_kms_helper        101028  3 vc4,evdi
drm                   262564  5 vc4,evdi,drm_kms_helper
syscopyarea             2945  2 evdi,drm_kms_helper
sysfillrect             3443  2 evdi,drm_kms_helper
sysimgblt               2069  2 evdi,drm_kms_helper
fb_sys_fops             1309  1 drm_kms_helper

Here is the output from 'xrandr --listproviders ' command of the terminal window is at follows:

Code:

Providers: number : 1
Provider 0: id: 0x43 cap: 0x2, Sink Output crtcs: 3 outputs: 1 associated providers: 0 name:modesetting

What kind of OS do you use on your Raspi?

Best regards
Michael

11-14-2016, 12:40 PM	#1
Mahdi2016 Junior Member Join Date: Oct 2016 Posts: 20	Hi Michal, i've built the evdipp package without errors. After reboot and plug in the HP s140u Monitor and type "sudo monitorsim EDIDv1_1600x900" a new clear window opened and after 10 seconds the window closed automatically. The output of the terminal window is at follows: Code: pi@raspberrypi:~ $ sudo monitorsim EDIDv1_1600x900 [libevdi] ioctl: drop_master error=-1 [libevdi] ioctl: drop_master error=-1 [libevdi] ioctl: drop_master error=-1 MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to retrieve device information Please i need some help and i havent any ideas anymore. Best regards Michael Last edited by Mahdi2016; 02-09-2017 at 08:09 AM.

12-07-2016, 09:44 AM	#10
Mahdi2016 Junior Member Join Date: Oct 2016 Posts: 20	Hi Michal, I use Debian Jessi (raspbian) on my RaspberryPi 2. The system is up-to-date. Here is the output from 'uname -a' command of the terminal window is at follows: Code: Linux raspberrypi 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l GNU/Linux Here is the output from 'lsmod \| grep drm' command of the terminal window is at follows: Code: drm_mipi_dsi 8702 1 vc4 drm_kms_helper 101028 3 vc4,evdi drm 262564 5 vc4,evdi,drm_kms_helper syscopyarea 2945 2 evdi,drm_kms_helper sysfillrect 3443 2 evdi,drm_kms_helper sysimgblt 2069 2 evdi,drm_kms_helper fb_sys_fops 1309 1 drm_kms_helper Here is the output from 'xrandr --listproviders ' command of the terminal window is at follows: Code: Providers: number : 1 Provider 0: id: 0x43 cap: 0x2, Sink Output crtcs: 3 outputs: 1 associated providers: 0 name:modesetting What kind of OS do you use on your Raspi? Best regards Michael

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

11-14-2016, 05:10 PM	#2
mlukaszek Senior Member Join Date: Feb 2010 Posts: 386	Hmm. Try with something simpler first, e.g. the "example" program that you also built. This won't show any pixels, but will possibly print more to the console, especially if you enable debug printout (you need to define DEBUG for the build). What's closing the app? Is it crashing? If yes, then running it in gdb might give some extra clues. Cheers, Michal

11-16-2016, 08:14 AM	#4
mlukaszek Senior Member Join Date: Feb 2010 Posts: 386	What happens if you use a full path to edid file. The message indicates that the program had problems with opening/reading the file that you gave as an argument? Cheers, Michal

11-22-2016, 12:49 PM	#6
mlukaszek Senior Member Join Date: Feb 2010 Posts: 386	I don't think the file "EDIDv1_1280x900" exists, given that you probably are using EDIDs from Google autotest. You probably meant 1280x800, 1440x900 or 1600x900. Cheers, Michal