Display HP S410u possible workling with RaspberryPi
i've an Display HP S140u (DL 41xx). I would like to use this display on a RaspberryPi 2. Currently, I've translated dkms to evdi module. The udev.rules are installed, and the modules are successfully loaded. At the moment, i´ve got no alternative for the "DisplayManager".
According to the description, the firmware should not be the problem? Debug output: Quote:
Quote:
|
After testing this, i've loaded the udl and the evdi module. The LED of this display, blinked white for 1 second.
lsusb: Code:
Bus 001 Device 004: ID 17e9:ff06 DisplayLink Code:
evdi 43794 0 Has anyone got an idea to get the ad running on a Raspberry or ARM platform? |
These are your options:
1. Hope that DisplayLink releases the DisplayLinkManager code as open source 2. Hope that DisplayLink releases a DisplayLinkManager build for ARM 3. Hope that someone is able to reverse engineer the protocol for these devices and write their own (hopefully open source) driver. That's all you can do. DisplayLink has not been doing well at all when it comes to supporting Linux users IMO. |
is it possible that DisplayLink will support ARM in the near future?
Especially in the ARM environment, there are many solutions that may work very fine with such a display. At my company we have already installed & configured such a display. |
tl;dr: no compatible ARM platform found yet, except for Chromebooks and Android devices.
The main use case we'd like to enable is being able to extend screens - to be able to use multiple monitors simultaneously. While DisplayLinkManager can be compiled for ARM (and in fact it already has been compiled for ARM; there are Chromebooks which use ARM binary of DLM, as well as our Android app), that's not all you need. We have not yet seen an ARM based platform which would support cross-device DRM prime support well (necessary to use output offloading, think xrandr --setprovideroutputsource ...). This is required for evdi to get pixels that we display on a device. Last time I tried, Raspberry Pi was almost there - with Eric Anholt's experimental vc4 module for the GPU. However, I only managed to use one screen at a time - i.e. only DisplayLink-connected screen was operable, not the built-in HDMI. Other devices I tried (e.g. BBB) didn't even get close to this. You could argue that certain use cases would be fine with just accessing a plain framebuffer through /dev/fbX - so, legacy fbdev interface. Sadly, neither UDL nor evdi don't support this mode anymore - last driver that did was pre-DRM legacy driver "udlfb" - which only supported USB2.0-era devices. If someone confirms he's successful with second screen driven by UDL on any ARM-based platform, configured in a way that both screens can be used - both the built-in and UDL-driven, I think we'd be happy to release ARM binary of DLM for use with evdi. Regards, Michal |
Thanks for the note.
After some testing this , i got some problems with the new kernel. At the first bootup the "rainbowscreen" comes up too. The kernel 4.9.0-rc2 works _not_ fine. I`ve builded the kernel 4.4.26 (stable) and the newest versions from the extra modules e.g. libdrm, mesa, xserver, evdev .. After this, i activated experimental opengl (vc4) and rebooted the system - works fine. The output from glxgears -info Code:
Running synchronized to the vertical refresh. The framerate should be Code:
Module Size Used by I need this display as the primary (standalone) display on my RaspberryPi2 (raspian jessie). Has anyone some experience to get the display working on an rasperrypi? |
See, but that's just half way through. The only thing that changed so far is using a DRM-compatible module for the built-in GPU (vc4).
Now, the trick is to add `udl` (for older devices) or evdi (for newer) on top of that, and call `xrandr --setprovideroutputsource ...`. So - what you could do now is to try to build evdi (I remember I used rpi-update and rpi-source combo for getting kernel sources and building the module afterwards). Then, despite lacking DLM, you can try to build and run monitorsim from here. Alternatively, if you have an older device that can be driven with UDL, try this instead. If everything works, meaning that you still get to see the main HDMI output, plus additionally you see the second screen (in a window, in case of monitorsim), please do report back. Note: I'd recommend to experiment via ssh. Fingers crossed! Cheers, Michal |
Hi Michal,
i've built the evdi module and it works fine. here is the output from lsmod: Code:
#lsmod | grep evdi After 'make install' the build breaks up with the following message: Code:
make install Best regards Michael |
Hi,
You need a C++14 compliant compiler. For the reasons I can't fully understand you sometimes must pass CXX flags manually, as cmake setting that I think should work doesn't :) Have a look at https://github.com/mlukaszek/evdipp/...er/.travis.yml - this is the configuration for Travis CI. I was forced to run cmake with -DCMAKE_CXX_FLAGS="-std=c++14" as you'll see. Cheers, Michal |
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 Please i need some help and i havent any ideas anymore. Best regards Michael |
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 |
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 Code:
pi@raspberrypi:~ $ xrandr Code:
pi@raspberrypi:~ $ sudo /bin/monitorsim /home/pi/EDIDv1_1440x900 Best regards Michael |
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 Code:
$ lsmod | grep drm Code:
$ xrandr --listproviders Cheers, Michal |
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 Code:
drm_mipi_dsi 8702 1 vc4 Code:
Providers: number : 1 Best regards Michael |
Hi, at the moment it's Ubuntu MATE.
Cheers, Michal |
Hi Michal,
I use ubuntu mate (16.04) on my RaspberryPi 2. The system is up-to-date. The outputs are the same. I will try to install 'evdi' and 'evdipp' tomorrow, and hope it will work. My goal is to just using the USB monitor.. Best regards Michael |
Hi Michal,
I use ubuntu mate (16.04) for my RaspberryPi 2. The system is up to date (apt update, apt upgrade). After trying 'sudo BRANCH=next rpi-update' and 'sudo rpi-source' the current kernel and sources was installed. I also try to add the following lines into '/boot/config.txt’: Code:
dtoverlay=vc4-kms-v3d Code:
Error! Bad return status for module build on kernel: 4.4.36-v7+ (armv7l) A try with the original installation package 'displaylink-driver-1.2.65.run*' end also with a similar error. I've built the evdipp package without errors. so far so good :) What steps have you done until to compile evdi and running the module? Best regards Michael |
I didn't use dkms, just used make to build in place. I think the problem you have is this:
Code:
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ Michal |
Hi Michal,
After successfull build the evdi module and reboot The Build of evdi are successfull. Here is the output from 'example' command of the terminal window is at follows: Code:
pi@pi-desktop:~/target/bin$ sudo ./example EDIDv1_1440x900 Code:
pi@pi-desktop:~/target/bin$ sudo ./example EDIDv1_1440x900 The output from 'lsmod' command of the terminal window is at follows: Code:
lsmod| grep evdi What steps have you done until to compile evdi? How did you actually compile evdi? Runs under ubuntu mate an USB monitor (DL31xx) e.g. HP s104u? I havent any ideas anymore.. Best regards Michael |
..does anyone else have an idea? :confused:
|
.. push.
Best regards Michael |
Quote:
|
Quote:
PineBook Pro: https://forum.pine64.org/showthread.php?tid=7093 Asus NovaGo TP370QL, HP Envy x2 12-e011nr/12-e001nf, Lenovo Mixx 630: https://github.com/aarch64-laptops |
Not sure if you noticed, but we started releasing armhf binaries of DLM since 4.4 release.
There are still serious limitations of the environment though, which cause us being unable to support it at this stage. See our FAQs, let us know if you manage to get it running! The idea page is here: https://support.displaylink.com/foru...-linux-support FAQ: https://support.displaylink.com/know...n-raspberry-pi https://support.displaylink.com/know...n-raspberry-pi Cheers, Michal |
Pinebook Pro?
Quote:
Thank you |
Quote:
|
All times are GMT. The time now is 11:00 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.