Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 08-12-2015, 09:56 PM   #1
ski11io
Junior Member
 
Join Date: Aug 2015
Posts: 1
Default

Quote:
Originally Posted by baldyman View Post
Dear Devs,
Unpacked the .run, went into the resulting folder and opened the installer sh. Walked through it manually and I now have a working Asus MB168B+.

Linux Mint 17.2 Rafaella
Kernel - 3.19.0-25-generic
Xorg - 1.15.1
cheerio,

have tried to replicate your steps as noted above.

system is atm also mint 17.2

3.19.3-031903-generic
X.Org X Server 1.15.1

the installer seems to run through with no errors when i just execute it as downloaded (did not see any difference to kernel 3.16):

Code:
sudo ./displaylink-driver-1.0.68.run 
Verifying archive integrity... All good.
Uncompressing DisplayLink Linux Driver 1.0.68  100%  
DisplayLink Linux Software 1.0.68 install script called: install
Distribution discovered: Linux Mint 17.2 Rafaela
Installing
Configuring EVDI DKMS module
Registering EVDI kernel module with DKMS
Building EVDI kernel module with DKMS
Installing EVDI kernel module to kernel tree
EVDI kernel module built successfully
Installing x64/DisplayLinkManager
Installing libraries
Installing firmware packages
Installing license file
Adding udev rule for DisplayLink DL-3xxx/5xxx devices
but i have the same error as cdriver321. everything seems fine, plugging in the screen makes it flash with the asus logo quickly and then go to standby directly.

extracting the .run and execute it manually shows only a short output and nothing more

Code:
sudo ./displaylink-installer.sh 
DisplayLink Linux Software 1.0.68 install script called: 
Distribution discovered: Linux Mint 17.2 Rafaela
lsusb shows the device as

Code:
Bus 002 Device 005: ID 17e9:ff03 DisplayLink
xrandr also does not show any other screen present.

help / hints would be awesome
ski11io is offline   Reply With Quote
Old 08-13-2015, 08:30 AM   #2
mlukaszek
Senior Member
 
mlukaszek's Avatar
 
Join Date: Feb 2010
Posts: 386
Default

The installer script only recognises Ubuntu. In other distros, you need to install an upstart init script or a systemd service file yourself (or modify the installer script to do it for you).

See http://displaylink.org/forum/showpos...&postcount=199.

Also see http://displaylink.org/forum/showthread.php?t=63994 if you need to use systemd.

Thanks,
Michal
mlukaszek is offline   Reply With Quote
Old 08-13-2015, 10:54 PM   #3
cdriver321
Junior Member
 
Join Date: Aug 2015
Posts: 2
Default This worked for me

Quote:
Originally Posted by mlukaszek View Post
The installer script only recognises Ubuntu. In other distros, you need to install an upstart init script or a systemd service file yourself (or modify the installer script to do it for you).

See http://displaylink.org/forum/showpos...&postcount=199.

Also see http://displaylink.org/forum/showthread.php?t=63994 if you need to use systemd.

Thanks,
Michal
This was it! I thought since the script ran without error it was complete. I went throught the script as you suggested and go the driver to start on boot. In addition, I had to go to the Display settings and turn on the monitor. Thanks for the hints!
cdriver321 is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 02:33 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2026, vBulletin Solutions, Inc.