Post by RobHPost by PaulPost by RobHPost by PaulPost by RobHPost by PaulPost by RobHPost by Jonathan N. LittlePost by PaulPost by Cybe R. WizardOn Fri, 1 Nov 2019 23:06:45 +0000
Post by Jonathan N. LittlePost by RobHOops, my apologies, no dkms 2.3 was indeed not the file name. It
was just called 'install' inside a debian folder of dkms 2.3
I downloaded dkms 2.3 and in then debian folder there is a file
called install. I don't know how to actually get it to run.
You don't need to compile from source, dkms package is already in
the repository. Just install with apt
sudo apt install dkms
Resource temporarily unavailable) E: Unable to acquire the dpkg
frontend lock (/var/lib/dpkg/lock-frontend), is another process using
Are you trying to use apt in a terminal window while synaptic or some
other package manager is open? That is the typical error message for
such a condition.
On a distro that computes updates immediately at boot, there
can be a conflict between the user trying to lock dpkg and
the system already having it locked. You just have to
wait until the other process is finished (or find the mother
and hammer it).
So there are at least three potential sources of conflict.
command line Apt
usage of synaptic package manager GUI
whatever the system is doing to compute updates, right after bootup
Wait until the above condition clears, and try again.
The process is unattended-upgrades...
Ok, I tried agina several hours later, and it all went well, dkms
was installed successfully.
I then ran the displaylink-driver file again and there were no
errors this time and installation was complete.
Is there something I have to do to get the actual displaylink to
work, ie show the desktop of a monitor when connected to the usb
to vga adaptor. I just tried it and there was no desktop, just a
black screen
The most useful command of the lot here
https://www.linuxquestions.org/questions/linux-newbie-8/asus-mb168b-driver-4175645315/
xrandr --listproviders
As that seems to reflect that a second provider is present, and
show the connector name. Then, when you look at less useful pages
like this one, things will make slightly more sense.
https://support.displaylink.com/knowledgebase/articles/675136-how-to-configure-displaylink-displays-on-ubuntu
Paul
The 2nd display is not showing up under hardware, devices, screen
Providers: number : 1
Provider 0: id: 0x45 cap: 0x9, Source Output, Sink Offload crtcs: 3
outputs: 3 associated providers: 0 name:modesetting
It doesn't look like the usb3 to vga adaptor is picking up the 2nd
monitor. Although it does appear as a 8mb volume.
Thanks
Some of the USB display devices, have been created as
"composite" devices, where a storage device containing
a Windows-only driver package is contained. The
8MB volume will be staged as a "fake CD drive" and
via an autorun.inf on the fake drive, the intention
is to cause a driver to be installed automatically
on Windows systems.
+------- Display part
|
USB <-----+ (composite)
|
+------- Storage part ("fake CD", data stored in flash)
Samsung made an LCD monitor which was based on
this mechanism (the LCD monitor plugged in via a
USB cable). I didn't think DisplayLink did that,
but it is a practical means to help naive users
(people who would not otherwise know how to
install a driver).
The DisplayLink installation you've done, won't
work if the device is some brand other than
DisplayLink. Have you used LSUSB to verify
the identity of the hardware ? The other reason
LSUSB is useful, is to prove the device is
even detected. The BIOS can be used to disable
USB ports, and you should verify the USB port works too.
Since you used DKMS, I would think you would need
one reboot after that point, before the module
installed via DKMS, would get loaded. The times I've
used DKMS, I think I did a reboot.
Paul
I couldn't find a usb to vga by DisplayLink, do they do them.
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 004: ID 067b:2731 Prolific Technology, Inc.
Bus 003 Device 002: ID 2109:0813 VIA Labs, Inc.
Bus 003 Device 003: ID 174c:55aa ASMedia Technology Inc. ASM1051E
SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 8087:0a2a Intel Corp.
Bus 002 Device 007: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 002 Device 006: ID 045e:0039 Microsoft Corp. IntelliMouse Optical
Bus 002 Device 004: ID 2109:2813 VIA Labs, Inc.
Bus 002 Device 023: ID 534d:6021
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I have a Intel NUC with a spinning disk attatched by usb3 cable which
has ubuntu 18.03 on, then a 3 port usb3 hub for peripherals.
The monitor is connected by mini hdmi to vga adaptor.
http://www.linux-usb.org/usb.ids
17e9 DisplayLink
0051 USB VGA Adaptor
But the usb.ids and pci.ids lists are missing a
lot of entries. The "17e9" part is something
you can bank on though.
The 17e9 can be seen in a picture here from the DisplayLink site.
https://support.displaylink.com/knowledgebase/articles/544834-my-displaylink-device-does-not-work-at-all-or-i-g
I can't find the 534d:6021. The 534d:0021 is a Macro Silicon
M2106 as an EasyCap video capture dongle.
I can't positively identify anything in your list as
a DisplayLink, or as a Fake DisplayLink.
Does the Prospective Device need a source of power,
or is it bus-powered ?
Paul
The usb to vga device (if you mean that) must be bus powered as there is
no other source of of power.
The link for the 17e9 is for windows as you know and I do see the entry
for 17e9 in the device property window, and unfortunately that doesn't
apply to Ubuntu as far as I know.
Have I come to a dead end now.
Yes, sir, it *does* apply.
These are bus "Plug and Play" values, which *both* ecosystems use.
The "17E9" is important to both Windows and Linux,
and for the same reasons.
This is one reason we can switch ecosystems for testing,
to verify that hardware exists in one environment, then
come back to another environment and work with renewed vigor,
knowing the hardware works or is visible on a bus.
I regularly use the Linux hardware ID files, when working
on Windows problems. When you look in a Windows INF file,
values like 17e9 tell the INF file whether the driver
installer is "applicable" to the hardware or not. That's
how a DisplayLink driver for Windows, gets applied to
a DisplayLink hardware device.
Linux also checks for matches, to decide what to use.
If you know the device is showing "8MB storage", and
is demonstrating it is a Composite USB device, you
should be able to find it in LSUSB. It's got to be in
there, if it showed itself like that. That's a breadcrumb.
You can use "dmesg | grep -i someidentifier"
to search for hardware probing at system boot,
as another means to spot that certain kinds
of hardware are present. Have a look with
"dmesg | less" and see what's in the log right
now. I sometimes look at SATA device responses
in such outputs. But I can spot other things,
like Ubuntu not having firmware for my TV tuner
card (Hauppauge). I have to install the firmware
manually.
The DisplayLink could use firmware too. You never know.
See if "dmesg | grep -i firmware" is present.
Even without firmware, I would still be expecting
to see a 17e9:xxxx value. You can't bootstrap something,
without endpoints forming during initialization. And
exchanging config data comes right after that.
On Windows, you can use this:
https://www.uwe-sieber.de/usbtreeview_e.html
It will show the VID (17e9) and PID of each plugged
in item. The only limitation of the Windows tools, is
they don't actually display the entire USB tree.
If you have a tree of depth four or five, you
won't see the subtending devices - it's encouraged
to plug USB devices directly into the PC, when
using the TreeView thing.
Paul