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 |
Hi Michal,
i've built the evdipp package with debug symbols. The output of the terminal window is at follows: Code:
(gdb) run Code:
(gdb) run I hope that helps. Best regards Michael |
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 |
Hi Michal,
i'm back from vacation. Here is the output from 'example' command of the terminal window is at follows: Code:
(gdb) run Code:
Reading symbols from /bin/monitorsim...done. Best regards Michael |
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 |
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 And the output from 'monitorsim' command of the terminal window is at follows: Code:
(gdb) run Best regards Michael |
Looks like `example` managed to talk to evdi and connected to it. You didn't define DEBUG so the output is minimal.
Not sure why you're getting SIGILL for the Qt app, but it looks like you should perhaps update your pi (https://github.com/raspberrypi/linux/issues/766). Anyway. With the `example` running, play with `xrandr` to list available outputs and connectors, and see if reverse prime works. So, in short, keep `example` in the background, and test the following:
...and see how far you get. Regards, Michal |
Hi Michal,
Here is the output from 'xrandr' command of the terminal window is at follows: Code:
xrandr Code:
Providers: number : 1 Code:
xrandr --setprovideroutputsource 1 0 For this test I used a 17 inch monitor and the HP s140u USB monitor. For a special debug I put up a new image, because I have updated the mesa and libdrm manually. Best regards Michael |
Hi Michal,
I have built a new image, only with existing packages. I builded evdi module and evdipp without any problems. The system is an up-to-date Raspian Jessi. After testing the following commands, there was always the error message: *No usable EVDI found* (The evdi module under lsmod is active.) Here is the output from 'example' command of the terminal window is at follows: Code:
#as root: And the output from 'monitorsim' command of the terminal window is at follows: Code:
#as root: I hope this information will help you. Best regards Michael |
Not being able to use evdi if not running as root is normal. (see note in https://displaylink.github.io/evdi/q...rt/#evdi-nodes)
Not seeing any extra output from "example" is also normal - but while the application is running, it should already be possible to check `xrandr` if you see DVI-*-* connector. Also, what `xrandr --listproviders` shows. From what monitorsim run as root logs, I think you are running in ssh session, with no DISPLAY set. Run `export DISPLAY=:0` and try again... Edit: on another look, it complains about not being able to connect to :0, so it might be something else... Cheers, Michal |
All times are GMT. The time now is 05:48 PM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.