#displaylink — Public Fediverse posts

macOS 27 Golden Gate Betaをサポートし、スリープ復帰後の外部モニターとの互換性、ウィンドウ移動時のカクつきを修正したDisplayLinkデバイス用マネージャー「DisplayLink Manager macOS v16.2」がリリース。
https://applech2.com/archives/20260722-displaylink-manager-macos-v16-2.html

#applech2 #Display #DisplayLink #Mac #macOS #アクセシビリティ #アップデート #アプリ #ディスプレイ #デュアルディスプレイ

The current version of #KDE on my machine (6.7) seems to be very buggy in terms of what happens when I try to add extra monitor(s) in the #Wayland version, whether it’s via #HDMI or #USB with #Displaylink. The screens go haywire and I can even get a terminal open. I’ve had to revert back to the #X11 version just as I’d got used to Wayland. I’m no fanboy of Wayland or X11 but when such a major breaking of the system happens, it forces my hand. Not good at all.

#Fedora #Linux #Desktop #KDE6_7

The current version of #KDE on my machine (6.7) seems to be very buggy in terms of what happens when I try to add extra monitor(s) in the #Wayland version, whether it’s via #HDMI or #USB with #Displaylink. The screens go haywire and I can even get a terminal open. I’ve had to revert back to the #X11 version just as I’d got used to Wayland. I’m no fanboy of Wayland or X11 but when such a major breaking of the system happens, it forces my hand. Not good at all.

#Fedora #Linux #Desktop #KDE6_7

Experimental, Reverse-Engineered & #AI Assisted #Rust Driver Targets Modern #DisplayLink Hardware

https://lxer.com/module/newswire/ext_link.php?rid=365666

Experimental, Reverse-Engineered & #AI Assisted #Rust Driver Targets Modern #DisplayLink Hardware

https://lxer.com/module/newswire/ext_link.php?rid=365666

A priori, "bien" faire marcher DisplayLink sous Ubuntu n'est pas si simple. Et ce repository semble intégrer l'ensemble des étapes dans un script Shell bien packagé. https://github.com/anthony-hopkins/ubuntu_displaylink_setup #displaylink #configuration #ubuntu #script #opensource

A priori, "bien" faire marcher DisplayLink sous Ubuntu n'est pas si simple. Et ce repository semble intégrer l'ensemble des étapes dans un script Shell bien packagé. https://github.com/anthony-hopkins/ubuntu_displaylink_setup #displaylink #configuration #ubuntu #script #opensource

Une espèce de hack curieux permettant d'accéder à une machine sans écran en faisant simuler à un Raspberry Zero un écran DisplayLink (et évidement, le Raspberry fait aussi clavier/souris USB) et en réexposant tout ça à travers du Wifi et du HTTP. https://github.com/doominator42/ZeroKVM #kvm #displaylink #http #raspberrypi #hack

Une espèce de hack curieux permettant d'accéder à une machine sans écran en faisant simuler à un Raspberry Zero un écran DisplayLink (et évidement, le Raspberry fait aussi clavier/souris USB) et en réexposant tout ça à travers du Wifi et du HTTP. https://github.com/doominator42/ZeroKVM #kvm #displaylink #http #raspberrypi #hack

Si je comprends bien, avec ça, vous pouvez faire de votre matériel Android un écran compatible DisplayLink. Malheureusement, comme c'est un driver, il faut recompiler "des trucs" et être root, j'imagine. https://github.com/magoroku15/DisplayLink-driver-for-android #android #vidéo #écran #displaylink #driver

Si je comprends bien, avec ça, vous pouvez faire de votre matériel Android un écran compatible DisplayLink. Malheureusement, comme c'est un driver, il faut recompiler "des trucs" et être root, j'imagine. https://github.com/magoroku15/DisplayLink-driver-for-android #android #vidéo #écran #displaylink #driver

一部のMacBookシリーズでクラムシェルモード中にMacを再起動すると外部ディスプレイが黒くなってしまう不具合を修正した「DisplayLink Manager macOS v16.1」がリリース。
https://applech2.com/archives/20260526-displaylink-manager-macos-v16-1-update.html

#applech2 #Display #DisplayLink #Mac #macOS #アクセシビリティ #アップデート #アプリ #ディスプレイ #デュアルディスプレイ

As this new #kernel series is not supported by the version of #EVDI that I had for #Displaylink, I had to download the newest version of that and compile it. Then the evdi #KernelModule built correctly on the next boot up.

As this new #kernel series is not supported by the version of #EVDI that I had for #Displaylink, I had to download the newest version of that and compile it. Then the evdi #KernelModule built correctly on the next boot up.

DisplayLinkチップを搭載したUSBアダプタ接続のディスプレイでも、カラーの反転やコントラストを上げるなどmacOSのアクセシビリティ機能が利用可能になった「DisplayLink Manager macOS v16.0」がリリース。
https://applech2.com/archives/20260408-displaylink-for-mac-support-accessibility-features.html

#applech2 #Display #DisplayLink #Mac #macOS #アクセシビリティ #アップデート #アプリ #ディスプレイ #デュアルディスプレイ

外部ディスプレイ出力が1台という制限がある「MacBook Neo」でもDisplayLinkチップ搭載のUSBグラフィックスアダプタを利用することでデュアルディスプレイ以上の出力が可能に。
https://applech2.com/archives/20260313-macbook-neo-support-displaylink-display.html

#applech2 #MacBook #A18_Pro #Apple_Silicon #CPU #DisplayLink #Mac #MacBook_Neo #ディスプレイ #デュアルディスプレイ

And here I am sitting in front of four working monitors (three external, two via #HDMI, one via #USBC), all configured through #KDE and using #Displaylink and #EVDI #KernelModules without any faffing around, except for plugging things into the correct ports to begin with. #FreeSoftware has come a long way in the decades since I started using it. And now, more often that not, #ItJustWorks!

#Fedora #GNU #USB #StraightOutOfTheBox

And here I am sitting in front of four working monitors (three external, two via #HDMI, one via #USBC), all configured through #KDE and using #Displaylink and #EVDI #KernelModules without any faffing around, except for plugging things into the correct ports to begin with. #FreeSoftware has come a long way in the decades since I started using it. And now, more often that not, #ItJustWorks!

#Fedora #GNU #USB #StraightOutOfTheBox

Finally! After three months of niggling frustration, I got #Displaylink to work with a new #Linux #kernel. That allows me to connect a monitor via a #USB, rather than an #HDMI connection, giving me to attach two or more monitors as the case may be. I’d been running 6.16.12 since that was the last one that worked with it, watching new kernel updates come and go.

#Fedora #FreeSoftware

Finally! After three months of niggling frustration, I got #Displaylink to work with a new #Linux #kernel. That allows me to connect a monitor via a #USB, rather than an #HDMI connection, giving me to attach two or more monitors as the case may be. I’d been running 6.16.12 since that was the last one that worked with it, watching new kernel updates come and go.

#Fedora #FreeSoftware

Upgraded to #Fedora43. The upgrade went very smoothly and quite fast but I'm having the issue with my third screen. It's a problem with the compatibility of the new 6.17 #kernel and the #Displaylink package. But I can forgo the luxury of a third screen for now. I'm hopeful that an update with be forthcoming soon.

#GNU #Linux #Fedora #F43

Upgraded to #Fedora43. The upgrade went very smoothly and quite fast but I'm having the issue with my third screen. It's a problem with the compatibility of the new 6.17 #kernel and the #Displaylink package. But I can forgo the luxury of a third screen for now. I'm hopeful that an update with be forthcoming soon.

#GNU #Linux #Fedora #F43

Gioco la carta magia #AiutoFediversico .

Mi servirebbe una #dockingStation per il mio portatile, un #ThinkPad #T480, compatibile con #GNU / #Linux. Ora, ho già avuto modo di constatare che quelle #DisplayLink sono da evitare come la morte, per via di driver e carichi di lavoro spropositati sulla CPU, quindi vorrei puntare su quelle #thunderbolt verticali, per risparmiare spazio. Mi confermate che possono funzionare potenzialmente tutte o danno problemi? Consigli?

#Tecnologia #Informatica

Gioco la carta magia #AiutoFediversico .

Mi servirebbe una #dockingStation per il mio portatile, un #ThinkPad #T480, compatibile con #GNU / #Linux. Ora, ho già avuto modo di constatare che quelle #DisplayLink sono da evitare come la morte, per via di driver e carichi di lavoro spropositati sulla CPU, quindi vorrei puntare su quelle #thunderbolt verticali, per risparmiare spazio. Mi confermate che possono funzionare potenzialmente tutte o danno problemi? Consigli?

#Tecnologia #Informatica

Finally built my own PC, should have done it years ago!

I got an EECS degree from MIT in the early 90’s, which involved a lot of hands-on work with computer hardware. I’ve always been a DIY type of person, preferring to fix things myself when possible rather than paying other people, including e.g. replacing the controller in a dishwasher, installing my own light fixtures, punching down network cables (though I paid an electrician to snake the cables through the walls of my house, I’m not that much of a masochist), and doing various laptop and smart-phone repairs that haven’t required too specialized equipment or skills. So it’s a bit of a mystery why, until a few days ago, I’d never built out my own PC from parts.

I bought my last new desktop computer over nine years ago, in January 2016. My old computer was struggling a bit at that point. The day I bought that new computer I was trying to do my taxes in TurboTax, running in a Windows VM running on Linux, and the old computer Just Could Not Cope With That. In exasperation, I drove over to Micro Center and made an employee on the floor very happy (they get paid on commission!) by asking him to sell me the most mini-tower PC I could walk out of the store with immediately. He sold me an Acer Predator gaming computer for nearly $2,000.

As I said, that computer has lasted me for over nine years, with just hard drive and SSD replacements and upgrades. I wouldn’t have decided last week, again in exasperation, to replace it, if it weren’t for the fact that it came with an NVIDIA graphics card. NVIDIA and Linux have never really fully gotten along. Even today it can still be a struggle to get an NVIDIA card to work 100% properly with Linux, and it works even less reliably when your monitors are connected through a DisplayLink hub, which mine are.

For a long time I had a mostly working configuration: the open-source “nouveau” kernel driver rather than the proprietary “nvidia” driver, and Xorg rather than Wayland. However, that became non-viable for three reasons: (1) my desktop was crashing every few days inside the display drivers and I was losing work; (2) Debian is in the process of desupporting Xorg; and (3) the folks who maintain the kernel drivers are de-emphasizing the nouveau driver in favor of the nvidia driver, which means the former is getting less attention and maintenance.

Last week, after my desktop crashed for the nth time inside the display driver, I decided enough was enough and tried yet again (previous attempts had failed) to switch to the nvidia driver and Wayland. This, it turns out, was a mistake. I will spare you all the gory details, but suffice it to say when all was said and done I could only get my computer to recognize one of my two monitors at any given time with the nvidia driver and Wayland, and I couldn’t revert to the nouveau driver because Wayland wouldn’t work with that driver, and I couldn’t revert to Xorg because it had stopped working completely with either driver and I couldn’t figure out why or how to get it working again.

At that point I had two choices: (1) rip out the NVIDIA card inside the computer and replace it with a card that works better with Linux; or (2) time for an entirely new computer. I chose option (2), because graphics cards are expensive and it seemed unwise to throw hundreds of dollars into a nine-and-a-half-year-old computer. However, the only way I convinced myself that this was the right choice was to say to myself, “You know what? You need to stop wasting money buying computers that other people built for you and build it yourself.” Also, one of my children has successfully built two gaming PCs (admittedly, with friends’ help, though honestly for the second one I think it was mostly for moral support), and what kind of a wuss am I if I’m going to let my kids show me up like that? 😉

Before I changed my mind I started browsing the Micro Center web site for components and discovered that they have an well-designed custom PC builder which reminds you what components you need and lets you pick them all out one by one, ensuring that each component you pick is compatible with the ones you’ve previously chosen. Slick!

Here’s what I ended up buying:

• CPU: Intel Core Ultra 7 265K
• Motherboard: MSI Pro B60M A WF
• Memory: 2x16GB Crucial 5600 46 B
• Storage: SanDisk 2TB SSD PLUS NVMe (M.2)
• Case: Thermaltake V100 ATX Mid-Tower Black
• PSU: Thermaltake Smart 700W Power Supply
• CPU Cooler: Be Quiet Pure Rock 3 Air Cooler Black

Not listed: The CD-RW drive which I will be moving from my old computer into the new one once things have settled down.

The total cost of all the components above with tax was $874.35, more than $1,000 less than the Acer Predator I bought pre-assembled nine and a half years ago. A decent graphics card that’s Linux-compatible probably would have cost nearly half that.

I ordered all that stuff on the website, and Micro Center had it ready for me to pick up about a half hour later. About an hour after I placed the order I was back home with the components ready to start putting them together:

Two hours after that, the PC was assembled, and it worked the first time I powered up, except for the BIOS telling me that I needed to move one of the DIMMS to a different slot.

Six hours (!) after that (yes, I stayed up all night *sigh*), I had Debian Trixie installed on it and all my data copied over from the old computer to the new one. This took about 3x as long as it should have for several reasons, some of which were my fault and some of which were not:

• I miscalculated how large my /boot partition needed to be, so the installer kept failing. [my fault]
• A bug in the installer prevented it from being able to connect to my WiFi, which I probably spent several hours trying to work around. [not my fault]
  • Caveat: This wouldn’t have been nearly as bad of a problem if the /boot partition size hadn’t been an issue. [my fault]
• The installer wasn’t giving me any sort of useful error message about my /boot partition filling up, so I repeatedly guessed wrong about what was going on and spent hours going down rabbit-holes. [not my fault]
  • It eventually occurred to me to look in the installer logs to figure out what was going wrong. [1/2 my fault: it should have occurred to me sooner but the installer should have suggested it after displaying completely content-less error messages]

It took a couple of days after that to get everything transferred over fully from the old computer to the new one (it’s not just a desktop, it also runs various services and scheduled tasks and the like), but at this point I’m pretty much 100% using the new computer, and the old one is sitting idle waiting for me to figure out what I’m going to do with a prefectly usable old min-tower gaming PC with a hole in the front where a CD-RW drive used to be.

Linux works out of the box with the intel graphics hardware built into the CPU, with one exception: there are annoying display artifacts caused by the DisplayLink driver. I can live with it, knowing that it’ll eventually be fixed.

And while my old PC was certainly fast enough for what I was using it for, HOLY SHIT THIS NEW PC IS SO MUCH FASTER. Apps launch noticeably faster. My 61GB GnuCash file loads in less than a second. Paperless NGX processes new documents several times faster than before. Perhaps the best thing about waiting so long between upgrades is that when you finally do upgrade, you really notice the difference.

I’m now totally sold on building your own PC, and if I ever have to upgrade again (why should I? I can’t imagine needing more computer power than this PC has!), I’m definitely going to go the DIY route again.

#DisplayLink #DIY #Intel #Linux #MicroCenter #NVIDIA

Finally built my own PC, should have done it years ago!

I got an EECS degree from MIT in the early 90’s, which involved a lot of hands-on work with computer hardware. I’ve always been a DIY type of person, preferring to fix things myself when possible rather than paying other people, including e.g. replacing the controller in a dishwasher, installing my own light fixtures, punching down network cables (though I paid an electrician to snake the cables through the walls of my house, I’m not that much of a masochist), and doing various laptop and smart-phone repairs that haven’t required too specialized equipment or skills. So it’s a bit of a mystery why, until a few days ago, I’d never built out my own PC from parts.

I bought my last new desktop computer over nine years ago, in January 2016. My old computer was struggling a bit at that point. The day I bought that new computer I was trying to do my taxes in TurboTax, running in a Windows VM running on Linux, and the old computer Just Could Not Cope With That. In exasperation, I drove over to Micro Center and made an employee on the floor very happy (they get paid on commission!) by asking him to sell me the most mini-tower PC I could walk out of the store with immediately. He sold me an Acer Predator gaming computer for nearly $2,000.

As I said, that computer has lasted me for over nine years, with just hard drive and SSD replacements and upgrades. I wouldn’t have decided last week, again in exasperation, to replace it, if it weren’t for the fact that it came with an NVIDIA graphics card. NVIDIA and Linux have never really fully gotten along. Even today it can still be a struggle to get an NVIDIA card to work 100% properly with Linux, and it works even less reliably when your monitors are connected through a DisplayLink hub, which mine are.

For a long time I had a mostly working configuration: the open-source “nouveau” kernel driver rather than the proprietary “nvidia” driver, and Xorg rather than Wayland. However, that became non-viable for three reasons: (1) my desktop was crashing every few days inside the display drivers and I was losing work; (2) Debian is in the process of desupporting Xorg; and (3) the folks who maintain the kernel drivers are de-emphasizing the nouveau driver in favor of the nvidia driver, which means the former is getting less attention and maintenance.

Last week, after my desktop crashed for the nth time inside the display driver, I decided enough was enough and tried yet again (previous attempts had failed) to switch to the nvidia driver and Wayland. This, it turns out, was a mistake. I will spare you all the gory details, but suffice it to say when all was said and done I could only get my computer to recognize one of my two monitors at any given time with the nvidia driver and Wayland, and I couldn’t revert to the nouveau driver because Wayland wouldn’t work with that driver, and I couldn’t revert to Xorg because it had stopped working completely with either driver and I couldn’t figure out why or how to get it working again.

At that point I had two choices: (1) rip out the NVIDIA card inside the computer and replace it with a card that works better with Linux; or (2) time for an entirely new computer. I chose option (2), because graphics cards are expensive and it seemed unwise to throw hundreds of dollars into a nine-and-a-half-year-old computer. However, the only way I convinced myself that this was the right choice was to say to myself, “You know what? You need to stop wasting money buying computers that other people built for you and build it yourself.” Also, one of my children has successfully built two gaming PCs (admittedly, with friends’ help, though honestly for the second one I think it was mostly for moral support), and what kind of a wuss am I if I’m going to let my kids show me up like that? 😉

Before I changed my mind I started browsing the Micro Center web site for components and discovered that they have an well-designed custom PC builder which reminds you what components you need and lets you pick them all out one by one, ensuring that each component you pick is compatible with the ones you’ve previously chosen. Slick!

Here’s what I ended up buying:

• CPU: Intel Core Ultra 7 265K
• Motherboard: MSI Pro B60M A WF
• Memory: 2x16GB Crucial 5600 46 B
• Storage: SanDisk 2TB SSD PLUS NVMe (M.2)
• Case: Thermaltake V100 ATX Mid-Tower Black
• PSU: Thermaltake Smart 700W Power Supply
• CPU Cooler: Be Quiet Pure Rock 3 Air Cooler Black

Not listed: The CD-RW drive which I will be moving from my old computer into the new one once things have settled down.

The total cost of all the components above with tax was $874.35, more than $1,000 less than the Acer Predator I bought pre-assembled nine and a half years ago. A decent graphics card that’s Linux-compatible probably would have cost nearly half that.

I ordered all that stuff on the website, and Micro Center had it ready for me to pick up about a half hour later. About an hour after I placed the order I was back home with the components ready to start putting them together:

Two hours after that, the PC was assembled, and it worked the first time I powered up, except for the BIOS telling me that I needed to move one of the DIMMS to a different slot.

Six hours (!) after that (yes, I stayed up all night *sigh*), I had Debian Trixie installed on it and all my data copied over from the old computer to the new one. This took about 3x as long as it should have for several reasons, some of which were my fault and some of which were not:

• I miscalculated how large my /boot partition needed to be, so the installer kept failing. [my fault]
• A bug in the installer prevented it from being able to connect to my WiFi, which I probably spent several hours trying to work around. [not my fault]
  • Caveat: This wouldn’t have been nearly as bad of a problem if the /boot partition size hadn’t been an issue. [my fault]
• The installer wasn’t giving me any sort of useful error message about my /boot partition filling up, so I repeatedly guessed wrong about what was going on and spent hours going down rabbit-holes. [not my fault]
  • It eventually occurred to me to look in the installer logs to figure out what was going wrong. [1/2 my fault: it should have occurred to me sooner but the installer should have suggested it after displaying completely content-less error messages]

It took a couple of days after that to get everything transferred over fully from the old computer to the new one (it’s not just a desktop, it also runs various services and scheduled tasks and the like), but at this point I’m pretty much 100% using the new computer, and the old one is sitting idle waiting for me to figure out what I’m going to do with a prefectly usable old min-tower gaming PC with a hole in the front where a CD-RW drive used to be.

Linux works out of the box with the intel graphics hardware built into the CPU, with one exception: there are annoying display artifacts caused by the DisplayLink driver. I can live with it, knowing that it’ll eventually be fixed.

And while my old PC was certainly fast enough for what I was using it for, HOLY SHIT THIS NEW PC IS SO MUCH FASTER. Apps launch noticeably faster. My 61GB GnuCash file loads in less than a second. Paperless NGX processes new documents several times faster than before. Perhaps the best thing about waiting so long between upgrades is that when you finally do upgrade, you really notice the difference.

I’m now totally sold on building your own PC, and if I ever have to upgrade again (why should I? I can’t imagine needing more computer power than this PC has!), I’m definitely going to go the DIY route again.

#DisplayLink #DIY #Intel #Linux #MicroCenter #NVIDIA

So colleagues warned me that the display outputs on the Thinkpad docks sucked, and they do as they are DisplayLink. (bleh)

But I tried.

I got it 'working' in a couple of minutes.

Then random apps started dying.

Running them in a terminal showed that they were being killed for an illegal instruction.

Removing the #DisplayLink driver fixed them.

Only #Electron apps were affected.

I wonder if the newer DisplayLink driver could fix this... But bespoke packages in #Nixos annoy me.

So colleagues warned me that the display outputs on the Thinkpad docks sucked, and they do as they are DisplayLink. (bleh)

But I tried.

I got it 'working' in a couple of minutes.

Then random apps started dying.

Running them in a terminal showed that they were being killed for an illegal instruction.

Removing the #DisplayLink driver fixed them.

Only #Electron apps were affected.

I wonder if the newer DisplayLink driver could fix this... But bespoke packages in #Nixos annoy me.

#ayuda fediverso #arch #displaylink

no logro que me funcione un dock usb de wavlink con la tecnologia wavlink

pasos que hago:
1. instalar evdi y displaylink desde aur
2. crear /usr/share/X11/xorg.conf.d/20-displaylink.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
EndSection
3. modprobe udl
4. systemctl enable / start displaylink.service
5. reiniciar

3 y 4 otra vez (entiendo que no se levantan al boot?)

tengo linux headers (6.14)

me baso en estas guias:
https://wiki.archlinux.org/title/DisplayLink
https://savoisn.github.io/post/displaylink_on_arch/

me va el servicio, pero no me detecta los displays del dock

se agradece #boost

#ayuda fediverso #arch #displaylink

no logro que me funcione un dock usb de wavlink con la tecnologia wavlink

pasos que hago:
1. instalar evdi y displaylink desde aur
2. crear /usr/share/X11/xorg.conf.d/20-displaylink.conf
Section "Device"
Identifier "Intel Graphics"
Driver "intel"
EndSection
3. modprobe udl
4. systemctl enable / start displaylink.service
5. reiniciar

3 y 4 otra vez (entiendo que no se levantan al boot?)

tengo linux headers (6.14)

me baso en estas guias:
https://wiki.archlinux.org/title/DisplayLink
https://savoisn.github.io/post/displaylink_on_arch/

me va el servicio, pero no me detecta los displays del dock

se agradece #boost

Who says you can't have it all? The new Plugable UD-7400PD docking station gives you screen real estate for days—FIVE monitors at once! Perfect for pros, gamers, and workflow wizards.

Dive into details: https://www.cryovex.com/multiple-monitors-plugable-ud-7400pd-supports-5/

#TechNews #GadgetLove #Plugable #DisplayLink #Multitasking #OpenWeb

Who says you can't have it all? The new Plugable UD-7400PD docking station gives you screen real estate for days—FIVE monitors at once! Perfect for pros, gamers, and workflow wizards.

Dive into details: https://www.cryovex.com/multiple-monitors-plugable-ud-7400pd-supports-5/

#TechNews #GadgetLove #Plugable #DisplayLink #Multitasking #OpenWeb

My latest for @cryovex:

Multiple monitors are great for improving your workflow. Many people these days use two or three, but in some cases, the more, the merrier. While some docking stations support up to four external monitors, the new Plugable UD-7400PD utilizes the new Synaptics DisplayLink DL-7400 chipset to support up to FIVE monitors.

#Plugable #MultipleMonitors #DisplayLink #DockingStation #DockTag #tech #technology

https://www.cryovex.com/multiple-monitors-plugable-ud-7400pd-supports-5/

My latest for @cryovex:

Multiple monitors are great for improving your workflow. Many people these days use two or three, but in some cases, the more, the merrier. While some docking stations support up to four external monitors, the new Plugable UD-7400PD utilizes the new Synaptics DisplayLink DL-7400 chipset to support up to FIVE monitors.

#Plugable #MultipleMonitors #DisplayLink #DockingStation #DockTag #tech #technology

https://www.cryovex.com/multiple-monitors-plugable-ud-7400pd-supports-5/

I setup #systemd-boot on my computer, but there were a couple of annoyances:

• The #kernel isn't signed for whatever reason. I wired in sbctl sign to the install script, but that wasn't completely straightforward.

• Since #Windows is installed in a separate #EFI (because Windows likes to fuck up the entire EFI partition sometimes) it couldn't "see" the Windows Boot Manager. I copied it to the other partition, but it will have to be manually updated whenever Microsoft changes it. Maybe that doesn't happen that often idk.

Side problem is that #Ubuntu's nvidia-lowlatency kernel isn't set up to reject unsigned modules, so it's a bit of a security hole, but also means that I don't have to figure out getting #DKMS to use the correct key. Right now I don't have a dependency on a DKMS-built driver. I used to use one for my dock and NVidia, but it seems that #NVidia doesn't need it now? and I don't use the video in my dock anymore because the #DisplayLink driver is annoying regardless of secure boot issues, because it doesn't work from power on. This isn't a problem with Linux, just DisplayLink in general.

@Sturmflut I wonder whether this is the state-of-the-art DP alt mode (which USB-C-docks usually support) or some #displaylink like adapter. And why are there no details on this, only this image?

1st time that I actually got a #DisplayLink dock working mostly acceptably... after using a DP to HDMI converter cable to not use its singular HDMI port. So either the port is bad or #HDCP was being a pain in the rear-end. Fingers crossed that this will survive reboots... 🤞

(I know one thing: my next laptop will be equiped with USB4 or Thunderbolt. DL is a crutch. And before you ask: the screens' DP connectors are already in use by my PC.)

#linux #archlinux #adayinthelife

Yesterday, I realized that I need to check if the #Displaylink driver for #Fedora works with my setup, before I actually install it.

I also realized that I should do it before next week 🤔

Does anyone have any experience with the Elgato prompter under Linux (Debian 12)?

Everything but EVDI seems to work for me and I can't get any further after hours of troubleshooting.

#linux #debian #elgato #elgatopromter #Displaylink

Due to changes in how the #DisplayLink driver is built on @opensuse #Tumbleweed and #Leap, I have added the new process for installing the drivers to this post rather than just write something entirely new. I left the old way there, just in case.
https://cubiclenate.com/2023/10/07/displaylink-video-on-opensuse-tumbleweed/