- #ASUS MB168B DISPLAYLINK USB GRAPHICS DEVICE DRIVER#
- #ASUS MB168B DISPLAYLINK USB GRAPHICS DEVICE PORTABLE#
Initialized evdi 1.0. evdi evdi.0: fb1: evdidrmfb frame buffer device Cannot find any crtc or sizes - going 1024x768 evdi evdi.0: No connectors reported connected with modes
#ASUS MB168B DISPLAYLINK USB GRAPHICS DEVICE DRIVER#
usbcore: registered new interface driver i2400m_usb IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready ACPI Warning: \_SB_._DSM: Argument #4 type mismatch - Found, ACPI requires (20150619/nsarguments-95) vgaarb: this pci device is not a vga device evdi_init Initialising logging on level 5 bbswitch: detected an Optimus _DSM function Though the last outputs from dmesg don't look good : ACPI Warning: \_SB_._DSM: Argument #4 type mismatch - Found, ACPI requires (20150619/nsarguments-95) systemd: Failed to insert module 'kdbus': Function not implemented EXT4-fs (sda5): mounted filesystem with ordered data mode. clocksource: Switched to clocksource tsc I am seeing the monitor recognized in dmesg output : usb 1-1.2.1: New USB device found, idVendor=17e9, idProduct=ff03 After that I plugged the monitor in and after a short delay it just worked. To get it working originally, I downloaded displaylink-driver-1.0.335.run from. I am very new to Ubuntu, but I would really like to get this working again. Now, I can't get the monitor to be recognized at all.
#ASUS MB168B DISPLAYLINK USB GRAPHICS DEVICE PORTABLE#
I needed to be portable so I wasn't worried about it - disconnected and walked away. After resuming from sleep later in the day, the monitor was blank. I first set it up yesterday, and it was working well and behaving as expected. I have been installing Ubuntu on a laptop (Samsung QX410-SO2), and while there have been hurdles, my Asus DisplayLink monitor is one of the things that worked immediately after driver install.
0 kommentar(er)
