Hi!
I bought without researching a (cheap) Lenovo USB 3.0 Dock hoping to connect one extra monitor to my laptop. It turns out that video through USB is not part of the standards and thus proprietary. There is luckily a package available here: https://github.com/displaylink-rpm/displaylink-rpm
Still it doesn't work. I'm getting this:
systemctl status displaylink.service displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static) Active: activating (auto-restart) (Result: exit-code) since Fri 2021-04-02> Process: 3954 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILU> CPU: 4m
and this: sbin/modprobe evdi modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_64
Has anyone any experience on the topic or should I just ask on their github project?
Thank you.
Fred
On Fri, Apr 02, 2021 at 05:47:01PM +0700, Frederic Muller wrote:
Hi!
I bought without researching a (cheap) Lenovo USB 3.0 Dock hoping to connect one extra monitor to my laptop. It turns out that video through USB is not part of the standards and thus proprietary. There is luckily a package available here: https://github.com/displaylink-rpm/displaylink-rpm
Still it doesn't work. I'm getting this:
systemctl status displaylink.service displaylink.service - DisplayLink Manager Service Loaded: loaded (/usr/lib/systemd/system/displaylink.service; static) Active: activating (auto-restart) (Result: exit-code) since Fri 2021-04-02> Process: 3954 ExecStartPre=/sbin/modprobe evdi (code=exited, status=1/FAILU> CPU: 4m
and this: sbin/modprobe evdi modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_64
Has anyone any experience on the topic or should I just ask on their github project?
It sounds like you haven't actually got a compiled version of the kernel module evdi, so something is broken there. Perhaps you built it against a kernel you aren't booted into?
I looked and the RPM Sphere 3rd-party repo has a dkms package for evdi:
I don't know if the repo is trusted, but there is a source RPM here: https://github.com/rpmsphere/source/blob/master/e/evdi-1.8.0-1.src.rpm
On 4/2/21 3:47 AM, Frederic Muller wrote:
It turns out that video through USB is not part of the standards and thus proprietary.
Just a point of clarification: video (DisplayPort) over USB *is* a part of the USB standard. You have a non-standard dock.
DisplayLink (not DisplayPort) is basically a crappy GPU attached over USB. It has some advantages, such as driving multiple monitors over a single port without daisy chaining, and driving higher resolution monitors than is possible over USB 3.0, but it's also slow and prone to corruption, and requires a driver that's not good on any platform (I work with a group that supports thousands of these on Windows and macOS. They're a little bit terrible.)
sbin/modprobe evdi modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_64
dkms should have compiled that driver when you installed the RPM. Run this command to find the location of the log file, and examine that:
rpm -q displaylink --scripts
The log file should have more information about why you don't have an evdi module.
On 4/2/21 10:50 PM, Gordon Messmer wrote:
On 4/2/21 3:47 AM, Frederic Muller wrote:
It turns out that video through USB is not part of the standards and thus proprietary.
Just a point of clarification: video (DisplayPort) over USB *is* a part of the USB standard. You have a non-standard dock.
DisplayLink (not DisplayPort) is basically a crappy GPU attached over USB. It has some advantages, such as driving multiple monitors over a single port without daisy chaining, and driving higher resolution monitors than is possible over USB 3.0, but it's also slow and prone to corruption, and requires a driver that's not good on any platform (I work with a group that supports thousands of these on Windows and macOS. They're a little bit terrible.)
sbin/modprobe evdi modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_64
dkms should have compiled that driver when you installed the RPM. Run this command to find the location of the log file, and examine that:
rpm -q displaylink --scripts
The log file should have more information about why you don't have an evdi module. _______________________________________________
Hi!
Thank you for all those detailed information. I did install evdi through the repos suggested by Jonathan, with no success though.
Checking the log file I have the following message: Creating symlink /var/lib/dkms/evdi/1.7.2/source -> /usr/src/evdi-1.7.2
DKMS: add completed. Error! echo Your kernel headers for kernel 5.11.10-200.fc33.x86_64 cannot be found at /lib/modules/5.11.10-200.fc33.x86_64/build or /lib/modules/5.11.10-200.fc33.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located.
In fedora kernel headers are apparently in /usr/src/kernels/<kernel_version>/include/
But then I am getting this: /usr/sbin/dkms build evdi/1.7.2 --kernelsourcedir=/usr/src/kernels/5.11.11-200.fc33.x86_64/include/ Error! echo Your kernel headers for kernel 5.11.11-200.fc33.x86_64 cannot be found at /lib/modules/5.11.11-200.fc33.x86_64/build or /lib/modules/5.11.11-200.fc33.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located.
Searching a bit more I found out I could edit the evdi dkms.conf file and add the proper path. Then something starts happening when running dkms build but then stops again. Checking the log states: ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.
There is generated/autoconf.h but then I am not really sure where or how to run the next line.
A bit of help would be nice. Thank you very much.
Fred
On 4/3/21 12:03 AM, Frederic Muller wrote:
DKMS: add completed. Error! echo Your kernel headers for kernel 5.11.10-200.fc33.x86_64 cannot be found at /lib/modules/5.11.10-200.fc33.x86_64/build or /lib/modules/5.11.10-200.fc33.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located.
In fedora kernel headers are apparently in /usr/src/kernels/<kernel_version>/include/
/lib/modules/5.11.10-200.fc33.x86_64/build is a symlink to that directory. You most likely haven't installed the kernel-devel package.
On 4/3/21 2:29 PM, Samuel Sieb wrote:
On 4/3/21 12:03 AM, Frederic Muller wrote:
DKMS: add completed. Error! echo Your kernel headers for kernel 5.11.10-200.fc33.x86_64 cannot be found at /lib/modules/5.11.10-200.fc33.x86_64/build or /lib/modules/5.11.10-200.fc33.x86_64/source. You can use the --kernelsourcedir option to tell DKMS where it's located.
In fedora kernel headers are apparently in /usr/src/kernels/<kernel_version>/include/
/lib/modules/5.11.10-200.fc33.x86_64/build is a symlink to that directory. You most likely haven't installed the kernel-devel package.
sudo dnf install kernel-devel [sudo] password for fred: Last metadata expiration check: 2:56:38 ago on Sat 03 Apr 2021 01:00:23 PM +07. Package kernel-devel-5.11.11-200.fc33.x86_64 is already installed. Dependencies resolved. Nothing to do. Complete!
So nope, unfortunately the package is installed. Anything else you could think of?
Thank you.
Fred
On 4/3/21 9:16 PM, Go Canes wrote:
Your kernel headers for kernel 5.11.10-200.fc33.x86_64 cannot be
Package kernel-devel-5.11.11-200.fc33.x86_64 is already installed.
Perhaps it needs kernel-devel-5.11.10-200? Or you need to upgrade to kernel 5.11.11-200?
No no.. there was an kernel update since and the previous error message "Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_6" is now "modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.11-200.fc33.x86_64"
So everything is up to date and at the latest updated kernel.
Thank you.
Fred
On 4/3/21 12:03 AM, Frederic Muller wrote:
Thank you for all those detailed information. I did install evdi through the repos suggested by Jonathan, with no success though.
The package you started with had both the DKMS evdi kernel module and other support, so adding the package from rpmsphere means you now have two DKMS evdi modules installed.
At this point, I'd suggest removing both packages and reinstalling the displaylink-rpm package.
Searching a bit more I found out I could edit the evdi dkms.conf file and add the proper path.
Restore the file to its original state. The default path works. There's something else causing your error.
Then something starts happening when running dkms build but then stops again. Checking the log states: ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.
That might not be the key error. This bug report on the displaylink-rpm package suggests that you probably need to install libdrm-devel.
https://github.com/displaylink-rpm/displaylink-rpm/issues/55
If that doesn't resolve the problem, please post the entire log somewhere we can access it. Maybe: https://paste.centos.org/
On 03/04/2021 23:26, Frederic Muller wrote:
On 4/3/21 9:16 PM, Go Canes wrote:
Your kernel headers for kernel 5.11.10-200.fc33.x86_64 cannot be
Package kernel-devel-5.11.11-200.fc33.x86_64 is already installed.
Perhaps it needs kernel-devel-5.11.10-200? Or you need to upgrade to kernel 5.11.11-200?
No no.. there was an kernel update since and the previous error message "Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_6" is now "modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.11-200.fc33.x86_64"
So everything is up to date and at the latest updated kernel.
Maybe you need to look in
/var/lib/dkms/evdi/1.8.0/build/make.log
??
On 03/04/2021 23:26, Frederic Muller wrote:
No no.. there was an kernel update since and the previous error message "Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_6" is now "modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.11-200.fc33.x86_64"
So everything is up to date and at the latest updated kernel.
In addition to what I already posted....
e_evdi-1.8.0-1.src.rpm rebuilds and subsequently installs just fine on a fully updated F31 system....
A snippet from the process....
Building module: cleaning build area.... make -j2 KERNELRELEASE=5.8.18-100.fc31.x86_64 all INCLUDEDIR=/lib/modules/5.8.18-100.fc31.x86_64/build/include KVERSION=5.8.18-100.fc31.x86_64 DKMS_BUILD=1...... cleaning build area....
DKMS: build completed.
evdi.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.18-100.fc31.x86_64/extra/ Adding any weak-modules
depmod.....
DKMS: install completed.
So, it would seem, updates to more recent kernels is causing you grief.
On 4/4/21 2:42 AM, Gordon Messmer wrote:
On 4/3/21 12:03 AM, Frederic Muller wrote:
Thank you for all those detailed information. I did install evdi through the repos suggested by Jonathan, with no success though.
The package you started with had both the DKMS evdi kernel module and other support, so adding the package from rpmsphere means you now have two DKMS evdi modules installed.
At this point, I'd suggest removing both packages and reinstalling the displaylink-rpm package.
Searching a bit more I found out I could edit the evdi dkms.conf file and add the proper path.
Restore the file to its original state. The default path works. There's something else causing your error.
Then something starts happening when running dkms build but then stops again. Checking the log states: ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it.
That might not be the key error. This bug report on the displaylink-rpm package suggests that you probably need to install libdrm-devel.
https://github.com/displaylink-rpm/displaylink-rpm/issues/55
If that doesn't resolve the problem, please post the entire log somewhere we can access it. Maybe: https://paste.centos.org/ _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
OK removed both packages (and 1 repo). Restarted (we never know?) and installed libdrm-devel and displaylink again. Same exact thing is happening.
I enclosed all the steps in that paste here https://paste.centos.org/view/bf947c35 . The full make.log is at "the bottom" of the page (starts line 124).
Thank you for the help really.
Fred
On 4/4/21 12:33 PM, Ed Greshko wrote:
On 03/04/2021 23:26, Frederic Muller wrote:
No no.. there was an kernel update since and the previous error message "Module evdi not found in directory /lib/modules/5.11.10-200.fc33.x86_6" is now "modprobe: FATAL: Module evdi not found in directory /lib/modules/5.11.11-200.fc33.x86_64"
So everything is up to date and at the latest updated kernel.
In addition to what I already posted....
e_evdi-1.8.0-1.src.rpm rebuilds and subsequently installs just fine on a fully updated F31 system....
A snippet from the process....
Building module: cleaning build area.... make -j2 KERNELRELEASE=5.8.18-100.fc31.x86_64 all INCLUDEDIR=/lib/modules/5.8.18-100.fc31.x86_64/build/include KVERSION=5.8.18-100.fc31.x86_64 DKMS_BUILD=1...... cleaning build area....
DKMS: build completed.
evdi.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.8.18-100.fc31.x86_64/extra/ Adding any weak-modules
depmod.....
DKMS: install completed.
So, it would seem, updates to more recent kernels is causing you grief.
Hi!
Actually the diskplaylink package apparently works with evdi up to version 1.7.2 (the rpmsphere repo installed 1.8.x but it didn't seem to make any difference).
The make.log is in the link in my previous email.
Thank you.
Fred
On 04/04/2021 13:42, Frederic Muller wrote:
Actually the diskplaylink package apparently works with evdi up to version 1.7.2 (the rpmsphere repo installed 1.8.x but it didn't seem to make any difference).
The make.log is in the link in my previous email.
Yes, that is the set of errors one gets when compiling the evdi 1.8.0 module with the current F32 and F33 kernels.
You'll need someone with a "bit" more experience with gcc to patch the source to get it to compile with more recent kernels.
On 4/4/21 12:51 PM, Ed Greshko wrote:
On 04/04/2021 13:42, Frederic Muller wrote:
Actually the diskplaylink package apparently works with evdi up to version 1.7.2 (the rpmsphere repo installed 1.8.x but it didn't seem to make any difference).
The make.log is in the link in my previous email.
Yes, that is the set of errors one gets when compiling the evdi 1.8.0 module with the current F32 and F33 kernels.
You'll need someone with a "bit" more experience with gcc to patch the source to get it to compile with more recent kernels.
From what I am understanding (yeah I know.. don't laugh ;-) ) it is trying to compile v1.7.2 and the package is for Fedora 33. So it should all work seamlessly, no?
Fred
On 04/04/2021 14:26, Frederic Muller wrote:
On 4/4/21 12:51 PM, Ed Greshko wrote:
On 04/04/2021 13:42, Frederic Muller wrote:
Actually the diskplaylink package apparently works with evdi up to version 1.7.2 (the rpmsphere repo installed 1.8.x but it didn't seem to make any difference).
The make.log is in the link in my previous email.
Yes, that is the set of errors one gets when compiling the evdi 1.8.0 module with the current F32 and F33 kernels.
You'll need someone with a "bit" more experience with gcc to patch the source to get it to compile with more recent kernels.
From what I am understanding (yeah I know.. don't laugh ;-) ) it is trying to compile v1.7.2 and the package is for Fedora 33. So it should all work seamlessly, no?
Well, when I went to the link provided by Jonathan for evdi it says
https://github.com/rpmsphere/source/blob/master/e/evdi-1.8.0-1.src.rpm
So, I don't know where you're picking up v1.7.2. But, still, evdi-1.8.0-1 shows
evdi-1.8.0-1.src.rpm being rebuild for f32 6 months ago.
Since then, there have been changes to the kernel. 6 months ago F32 was using 5.8.18-200. The "same" as F31 which was using 5.8.18-100 at its EOL. At present F32 is at 5.11.11-100.fc32 and similarly F33 is at 5.11.11-200.fc33.
So, if nobody is actually maintaining the evdi package they wouldn't know to fix issues with the latest kernel. And, I would expect that compiling of the earlier v1.7.2 would fail in a similar fashion to the latest 1.8.0.
On 04/04/2021 14:50, Ed Greshko wrote:
On 04/04/2021 14:26, Frederic Muller wrote:
On 4/4/21 12:51 PM, Ed Greshko wrote:
On 04/04/2021 13:42, Frederic Muller wrote:
Actually the diskplaylink package apparently works with evdi up to version 1.7.2 (the rpmsphere repo installed 1.8.x but it didn't seem to make any difference).
The make.log is in the link in my previous email.
Yes, that is the set of errors one gets when compiling the evdi 1.8.0 module with the current F32 and F33 kernels.
You'll need someone with a "bit" more experience with gcc to patch the source to get it to compile with more recent kernels.
From what I am understanding (yeah I know.. don't laugh ;-) ) it is trying to compile v1.7.2 and the package is for Fedora 33. So it should all work seamlessly, no?
Well, when I went to the link provided by Jonathan for evdi it says
https://github.com/rpmsphere/source/blob/master/e/evdi-1.8.0-1.src.rpm
So, I don't know where you're picking up v1.7.2. But, still, evdi-1.8.0-1 shows
evdi-1.8.0-1.src.rpm being rebuild for f32 6 months ago.
Since then, there have been changes to the kernel. 6 months ago F32 was using 5.8.18-200. The "same" as F31 which was using 5.8.18-100 at its EOL. At present F32 is at 5.11.11-100.fc32 and similarly F33 is at 5.11.11-200.fc33.
So, if nobody is actually maintaining the evdi package they wouldn't know to fix issues with the latest kernel. And, I would expect that compiling of the earlier v1.7.2 would fail in a similar fashion to the latest 1.8.0.
Oh, while not an rpm, I see here....
https://github.com/DisplayLink/evdi
"Add support for 5.11 and 5.12 kernels"
On 04/04/2021 15:10, Ed Greshko wrote:
Oh, while not an rpm, I see here....
https://github.com/DisplayLink/evdi
"Add support for 5.11 and 5.12 kernels"
Adding to that.....
I downloaded the zip file and replaced the module files found in /usr/src/evdi-1.8.0 with the module files in the zip file and.....
[root@f32k ~]# dkms build -m evdi -v 1.8.0
Kernel preparation unnecessary for this kernel. Skipping...
Building module: cleaning build area... make -j2 KERNELRELEASE=5.11.11-100.fc32.x86_64 all INCLUDEDIR=/lib/modules/5.11.11-100.fc32.x86_64/build/include KVERSION=5.11.11-100.fc32.x86_64 DKMS_BUILD=1..... cleaning build area...
DKMS: build completed.
[root@f32k ~]# dkms install -m evdi -v 1.8.0
evdi.ko.xz: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.11-100.fc32.x86_64/extra/ Adding any weak-modules
depmod.......
DKMS: install completed.
You can do the same for F33.
On 4/3/21 10:39 PM, Frederic Muller wrote:
I enclosed all the steps in that paste here https://paste.centos.org/view/bf947c35 . The full make.log is at "the bottom" of the page (starts line 124).
Great. That log has information about the actual failures, starting on line 143. Searching for that error should lead you here:
https://github.com/DisplayLink/evdi/issues/249
There, the developers are discussing support for kernel 5.11 which isn't present in version 1.7.2. There are other release branches (1.8.0 and 1.9.0) but I would disregard those for now. 1.8.0 is older than 1.7.2 by several months, and 1.9.0 was released the same day as 1.7.2. There are no published releases that will support 5.11:
https://github.com/DisplayLink/evdi/releases
That leaves you with a handful of options, of which I think two stand out. The first would be to simply stick with kernel 5.10. It looks like 5.10.22-200.fc33 is still in the updates repo, and you could fall back to that, and I'd expect the evdi driver to work.
The other option, which is more work, would be to clone the evdi repo from GitHub and manually build the evdi kernel module. It looks like that would be:
git clone https://github.com/DisplayLink/evdi.git git checkout devel sudo make -C module install sudo make clean
If you go that route, you'll need to manually rebuild the module each time the kernel updates (until the displaylink-rpm package is updated to a version that supports your kernel, when such a version is published), and I'm not sure whether you might run into compatibility problems from a version mismatch between the kernel module (which will not be the 1.7 branch) and the userspace components (which will be the 1.7 branch on your system).
Between the two, I'd suggest sticking with kernel 5.10 until the displaylink-rpm catches up. (My employer has a large fleet of DisplayLink hardware, and periodically has to avoid updating our non-Linux desktop operating systems in order to keep them working, accepting the security vulnerabilities that come from delaying updates, which is why I recommend avoiding this hardware whenever possible.)
On 4/4/21 9:31 PM, Gordon Messmer wrote:
why I recommend avoiding this hardware whenever possible
Thank you for the very detailed explanation (again). I think I might (or might not) just accept to have only 2 external monitors connected, and when my other 3rd monitor (well the other 3rd one ;-) ) which I lent to a friend comes back (in 1+ month), I could look into it again.
I now understand this was a bad purchase and.. oh dare I ask... do you know of a better system to get 3 external monitors connected to a Thinkpad X1 Carbon 3rd gen (Thinkpad owner since 2000 and so happy with the Linux support these laptop have had so far, but hey, your mileage may vary). I also tried (forgot which port now.. still have the device though) a port splitter and while it worked, I couldn't get 3 external monitors working at once. I could however cycle between any 2 of the connected ones... happy me!
For reference the x1 carbon 3rd gen has a HDMI and a min-DP port (and 2x USB3 ports). And all the monitors I connected fit into the max resolution the graphic card can handle).
Thank you.
Fred
On 4/4/21 10:48 PM, Gordon Messmer wrote:
On 4/4/21 8:06 AM, Frederic Muller wrote:
do you know of a better system to get 3 external monitors connected to a Thinkpad X1 Carbon 3rd gen
What resolution and refresh rate are the 3 monitors?
RIght now 3 (I hoped) Dell, the coming back one is a HP. 1 Dell 24" 2560x1440 @ 60Hz 1 Dell 22" 1680x1050 @ 60Hz 1 Dell 17" 1280x1024 @... I think 60Hz but it's not connected for now
The HP coming back is a HD monitor, 23" and there 1920 x1080, I think at 60Hz.
The main (laptop) screen is a 2560x1440 @ 60HZ
Thank you.
Fred
On 4/4/21 8:58 AM, Frederic Muller wrote:
RIght now 3 (I hoped) Dell, the coming back one is a HP. 1 Dell 24" 2560x1440 @ 60Hz 1 Dell 22" 1680x1050 @ 60Hz 1 Dell 17" 1280x1024 @... I think 60Hz but it's not connected for now
The HP coming back is a HD monitor, 23" and there 1920 x1080, I think at 60Hz.
https://en.wikipedia.org/wiki/DisplayPort#Resolution_and_refresh_frequency_l...
2560x1440@60 requires 5.63 Gbps bandwidth. 1680x1050@60 requires 2.7 Gbps (I think) 1280x1024@60 requires 1.8 Gbps (again, I think) 1920x1080@60 requires 3.2 Gbps
The X1 Carbon 3rd Gen has one Mini DisplayPort (with roughly 12Gbps bandwidth) and one HDMI port (roughly 6Gbps), and the manual indicates support for three independent displays. That might indicate a limitation of just one display per port, I'm not really sure about that.
But, hypothetically, there should be enough bandwidth to drive any three of those displays with one monitor on HDMI and two monitors daisy-chained over DisplayPort with no other devices required as long as DisplayPort 1.2 is supported by both the laptop and the monitors. I *think* it is on the X1 Carbon 3rd Gen. If your monitors don't support DisplayPort daisy-chaining, but they do support DisplayPort, you might be able to use a DisplayPort MST hub to link two monitors on one laptop port.
If you don't have at least two DisplayPort monitors, then a dock with a DisplayLink chip is probably your only option.
On 4/4/21 11:43 PM, Gordon Messmer wrote:
On 4/4/21 8:58 AM, Frederic Muller wrote:
RIght now 3 (I hoped) Dell, the coming back one is a HP. 1 Dell 24" 2560x1440 @ 60Hz 1 Dell 22" 1680x1050 @ 60Hz 1 Dell 17" 1280x1024 @... I think 60Hz but it's not connected for now
The HP coming back is a HD monitor, 23" and there 1920 x1080, I think at 60Hz.
https://en.wikipedia.org/wiki/DisplayPort#Resolution_and_refresh_frequency_l...
2560x1440@60 requires 5.63 Gbps bandwidth. 1680x1050@60 requires 2.7 Gbps (I think) 1280x1024@60 requires 1.8 Gbps (again, I think) 1920x1080@60 requires 3.2 Gbps
The X1 Carbon 3rd Gen has one Mini DisplayPort (with roughly 12Gbps bandwidth) and one HDMI port (roughly 6Gbps), and the manual indicates support for three independent displays. That might indicate a limitation of just one display per port, I'm not really sure about that.
But, hypothetically, there should be enough bandwidth to drive any three of those displays with one monitor on HDMI and two monitors daisy-chained over DisplayPort with no other devices required as long as DisplayPort 1.2 is supported by both the laptop and the monitors. I *think* it is on the X1 Carbon 3rd Gen. If your monitors don't support DisplayPort daisy-chaining, but they do support DisplayPort, you might be able to use a DisplayPort MST hub to link two monitors on one laptop port.
If you don't have at least two DisplayPort monitors, then a dock with a DisplayLink chip is probably your only option.
ok. So I have the Displaylink already ;-) . Now I think I convert my splitter to VGA. Maybe I shouldn't (read something about that in a different thread today). Also the 2 "bigger" screens (so not the 17" one, only supports VGA) both have DP connections. Didn't know anything about daisy-chaining so I'll look into that when the HP monitor returns.
Thank you very much!
Fred
-
Ed Greshko -
Frederic Muller -
Go Canes -
Gordon Messmer -
Jonathan Billings -
Samuel Sieb