![]() ![]() Unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1 V: kernel pcie: speed: 2.5 GT/s lanes: 4 bus-ID: 01:00.0 chip-ID: 10de:139aĭevice-3: Acer Integrated Camera type: USB driver: uvcvideo bus-ID: 1-7:3ĭisplay: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting Ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0ĭevice-2: NVIDIA GM107M vendor: Lenovo driver: nouveau Speed (MHz): avg: 800 min/max: 400/3500 cores: 1: 800 2: 800 3: 800įlags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3ĭevice-1: Intel HD Graphics 620 vendor: Lenovo driver: i915 v: kernel Smt: enabled arch: Amber/Kaby Lake note: check rev: 9 cache: L1: 128 KiB Info: dual core model: Intel Core i7-7500U bits: 64 type: MT MCP Volts: 15.6 min: 14.8 model: SANYO 01AV418 type: Li-ion serial: Type: Laptop System: LENOVO product: 20H50047US v: ThinkPad E570 I'd attach the log but it says it's too big. There's no obvious errors in the X logs indicating why it gets stuck with the DisplayLink connected. This isn't ideal, but it's better than nothing. ![]() ![]() However, with the device disconnected, the system boots correctly and DisplayLink can be subsequently connected. Booting with the DisplayLink device connected, the system will still get stuck at the LinuxMint logo. Removed that via sudo dkms remove evdi/1.9.0 -all -q and installed current version (1.12.0 as of writing) from DisplayLink/evdi page: īuilt & installed EVDI, then reinstalled DisplayLink drivers. di-exec-foĭkms status shows Mint-supplied EVDI version 1.9.0. (II) UnloadSubModule: "fbdevhw"īooting in recovery mode I was able to uninstall the driver and get the system booting properly again. (EE) Screen 1 deleted because of no matching config section. Code: Select all (EE) Screen 0 deleted because of no matching config section. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |