Dockingstation 2 Displays, Thinkpad

Hey People,

I seem to have some trouble with my lenovo dockingstation.
I am using the w540 thinkpad with the following specs:

Operating System: Manjaro Linux
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.15.0
Kernel Version: 5.7.15-1-MANJARO
OS Type: 64-bit

Processors: 8 × Intel® Core™ i7-4800MQ CPU @ 2.70GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa DRI Intel® HD Graphics 4600

i do also have a NVIDIA graphic-card on board but it isnt showing on the about page. I would like to make use of it of course, the NVIDIA quadro k1100m.
Its showing in the hardware configurations but not on the about page.

I had to make several installs because I had futile attempts of encrypting my drive using the manjaro architect and on my first install the dockingstation worked. I have no idea why it doesn’t now.
Also I would like to ad that the keyboard, the mouse and the sound hooks up perfectly its just the Displays making the problems. so because of the first install i know that it isn’t a hardware problem.

I would appreciate help very much because i would love to stay on this distro because it so beautiful and nice.

Hi! I have no specific advice but to :

  • Try on kernel 5.8
  • Try fron a live USB.

Also does your Quadro card show up when running inxi -Fxxz?


Is still supported by the 390 series of drivers, but support was removed from the 400 series, so:

  • Log off

  • Switch to TTY2 by pressing Ctrl+Alt+F2

  • Log in there

  • Execute:

    sudo mhwd --listinstalled
  • remove all lines of the output with:

    sudo mhwd --remove pci WhateverComesupAbove
  • And install the 390 series and reboot:

    sudo mhwd --install pci video-nvidia-390xx
    sudo reboot


Warning! You’ve not provided any inxi output so I can’t verify whether or not you do have the Quadro 1100M series. An inxi --full --admin --verbosity=7 --filter --no-host would be the minimum required information… (Personally Identifiable Information like serial numbers and MAC addresses will be filtered out by the above command)


1 Like

Thanks for reminding me of that!

:innocent: :+1:

1 Like

thank you for the reply
I never saw this “TTY2” and got overwhelmed by it. Also I couldn’t log in as well. It didn’t work.

When I am looking into my hardware config stuff in the GUI it is showing me that I am using the 390 drivers already. I would love to provide a screenshot but the forum doesn’t allow me post images or links unfortunately.

I installed the 5.8 Kernel and its up and running. It didn’t change anything. And from a live USB it also doesn’t work.
Thank you for the effort though.

Unfortunately i cant reply with a copy from the command because this forum is recognizing it as a link i dont know why it then its telling me that i am not allowed to post this but i can say that the graphic card is showing up under the command

so yeah it is showing up. Cool command btw.

precede the output of inxi with 3 backticks ``` and end with three backticks:

then your output will look line this

I’ve done the above by typing:

then your output will look line this

What do you mean? It’s just a black screen in text asking you for your user name and password. (password echoes nothing, so no one can guess how long it is, old-style security; just keep typing as nothing has happened.)

nxi --full --admin --verbosity=7 --filter --no-host
System: Kernel: 5.8.1-3-MANJARO x86_64 bits: 64 compiler: N/A
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8-x86_64 root=UUID=96197d22-38ae-4c28-9aa9-c6524b7e8040 rw quiet
resume=UUID=99721703-11e6-4ea0-95f2-38b90e2256d2 udev.log_priority=3
Desktop: KDE Plasma 5.19.4 tk: Qt 5.15.0 wm: kwin_x11 dm: SDDM Distro: Manjaro Linux
Machine: Type: Laptop System: LENOVO product: 20BHS0L000 v: ThinkPad W540 serial: Chassis: type: 10
Mobo: LENOVO model: 20BHS0L000 serial: UEFI: LENOVO v: GNET90WW (2.38 ) date: 03/25/2019
Battery: ID-1: BAT0 charge: 86.0 Wh condition: 89.7/99.5 Wh (90%) volts: 12.2/10.8 model: SANYO 45N1779 type: Li-ion
serial: status: Unknown
Memory: RAM: total: 15.52 GiB used: 2.41 GiB (15.6%)
RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU: Topology: Quad Core model: Intel Core i7-4800MQ bits: 64 type: MT MCP arch: Haswell family: 6 model-id: 3C (60)
stepping: 3 microcode: 28 L2 cache: 6144 KiB bogomips: 43112
Speed: 2529 MHz min/max: 800/3700 MHz Core speeds (MHz): 1: 2617 2: 2236 3: 2114 4: 2166 5: 2666 6: 2094 7: 2241
8: 2229
Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2 bts clflush cmov constant_tsc cpuid
cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht ibpb ibrs ida invpcid invpcid_single lahf_lm lm mca mce md_clear mmx monitor movbe msr mtrr
nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdtscp
rep_good sdbg sep smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tpr_shadow tsc tsc_adjust
tsc_deadline_timer vme vmx vnmi vpid x2apic xsave xsaveopt xtopology xtpr
Vulnerabilities: Type: itlb_multihit status: KVM: Split huge pages
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel 4th Gen Core Processor Integrated Graphics vendor: Lenovo driver: i915 v: kernel bus ID: 00:02.0
chip ID: 8086:0416
Device-2: NVIDIA GK107GLM [Quadro K1100M] driver: N/A alternate: nouveau, nvidia_drm, nvidia bus ID: 01:00.0
chip ID: 10de:0ff6
Device-3: Lite-On Integrated Camera type: USB driver: uvcvideo bus ID: 2-12:7 chip ID: 04ca:7035
Display: x11 server: X(.)Org 1.20.8 compositor: kwin_x11 driver: intel display ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1013x285mm (39.9x11.2") s-diag: 1052mm (41.4")
OpenGL: renderer: Mesa DRI Intel HD Graphics 4600 (HSW GT2) v: 4.5 Mesa 20.1.5 compat-v: 3.0 direct render: Yes
Audio: Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 00:03.0 chip ID: 8086:0c0c
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 00:1b.0 chip ID: 8086:8c20
Device-3: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0e1b
Sound Server: ALSA v: k5.8.1-3-MANJARO
Network: Device-1: Intel Ethernet I217-LM vendor: Lenovo driver: e1000e v: 3.2.6-k port: 5080 bus ID: 00:19.0
chip ID: 8086:153a
IF: enp0s25 state: down mac:
Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: efa0 bus ID: 03:00.0 chip ID: 8086:08b2
IF: wlp3s0 state: down mac:
IF-ID-1: enp0s20u9u3 state: up speed: N/A duplex: N/A mac:
IP v4: type: dynamic noprefixroute scope: global broadcast:
IP v6: type: noprefixroute scope: link
Drives: Local Storage: total: 4.55 TiB used: 10.99 GiB (0.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/sda vendor: Intenso model: SSD Sata III size: 465.76 GiB block size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s serial: rev: 6A scheme: GPT
ID-2: /dev/sdb vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB block size: physical: 512 B logical: 512 B
speed: 6.0 Gb/s serial: rev: 023 scheme: GPT
ID-3: /dev/sdc type: USB vendor: Intenso model: External USB 3.0 size: 3.64 TiB block size: physical: 4096 B
logical: 4096 B serial: rev: 1402 scheme: GPT
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Message: No Optical or Floppy data was found.
RAID: Message: No RAID data was found.
Partition: ID-1: / raw size: 448.39 GiB size: 440.35 GiB (98.21%) used: 10.99 GiB (2.5%) fs: ext4 dev: /dev/sda2 label: N/A
uuid: 96197d22-38ae-4c28-9aa9-c6524b7e8040
ID-2: /boot/efi raw size: 300.0 MiB size: 299.4 MiB (99.80%) used: 280 KiB (0.1%) fs: vfat dev: /dev/sda1
label: N/A uuid: 6034-342E
Swap: Kernel: swappiness: 60 (default) cache pressure: 100 (default)
ID-1: swap-1 type: partition size: 17.07 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda3 label: N/A
uuid: 99721703-11e6-4ea0-95f2-38b90e2256d2
Unmounted: ID-1: /dev/sdb1 size: 16.0 MiB fs: <superuser/root required> label: N/A uuid: N/A
ID-2: /dev/sdb2 size: 465.74 GiB fs: ntfs label: N/A uuid: 4A7E7B307E7B1443
ID-3: /dev/sdc1 size: 931.32 GiB fs: vfat label: Files_FAT uuid: B3DB-E954
ID-4: /dev/sdc2 size: 1.82 TiB fs: crypto_luks label: N/A uuid: 86db94b7-e1e5-4885-ab5c-6f586c4edf5b
ID-5: /dev/sdc3 size: 419.11 GiB fs: crypto_luks label: N/A uuid: e0c7d93e-5832-43a7-b043-b0905eb4d397
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0 speed: 480 Mb/s chip ID: 8087:8008
Hub: 2-0:1 info: Full speed (or root) Hub ports: 15 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Device-1: 2-6:3 info: Logitech Unifying Receiver type: Keyboard,Mouse,HID driver: logitech-djreceiver,usbhid
interfaces: 3 rev: 2.0 speed: 12 Mb/s chip ID: 046d:c52b
Hub: 2-9:4 info: Lenovo ThinkPad Ultra Dock Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip ID: 17ef:1010
Device-1: 2-9.1:6 info: Logitech Internet 350 Keyboard type: Keyboard,HID driver: hid-generic,usbhid interfaces: 2
rev: 1.1 speed: 1.5 Mb/s chip ID: 046d:c313
Device-2: 2-9.2:8 info: Logitech G402 Gaming Mouse type: Mouse,HID driver: hid-generic,usbhid interfaces: 2
rev: 2.0 speed: 12 Mb/s chip ID: 046d:c07e serial:
Device-3: 2-9.3:11 info: Research In Motion type: Communication,CDC-Data driver: cdc_ncm interfaces: 2 rev: 2.1
speed: 480 Mb/s chip ID: 0fca:8035 serial:
Hub: 2-9.4:10 info: Lenovo ThinkPad Ultra Dock Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 17ef:100f
Device-1: 2-11:5 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb interfaces: 2 rev: 2.0
speed: 12 Mb/s chip ID: 8087:07dc
Device-2: 2-12:7 info: Lite-On Integrated Camera type: Video driver: uvcvideo interfaces: 2 rev: 2.0
speed: 480 Mb/s chip ID: 04ca:7035
Hub: 3-0:1 info: Full speed (or root) Hub ports: 6 rev: 3.0 speed: 5 Gb/s chip ID: 1d6b:0003
Device-1: 3-1:3 info: JMicron / JMicron USA External USB 3.0 type: Mass Storage driver: uas interfaces: 1 rev: 3.0
speed: 5 Gb/s chip ID: 152d:578f serial:
Hub: 3-5:2 info: Lenovo ThinkPad Ultra Dock Hub ports: 4 rev: 3.0 speed: 5 Gb/s chip ID: 17ef:1010
Hub: 4-0:1 info: Full speed (or root) Hub ports: 3 rev: 2.0 speed: 480 Mb/s chip ID: 1d6b:0002
Hub: 4-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0 speed: 480 Mb/s chip ID: 8087:8000
Sensors: System Temperatures: cpu: 49.0 C mobo: 0.0 C
Fan Speeds (RPM): cpu: 1607
Info: Processes: 238 Uptime: 43m Init: systemd v: 245 Compilers: gcc: N/A Packages: pacman: 1174 lib: 323 Shell: Bash
v: 5.0.18 running in: konsole inxi: 3.1.05

btw when I connect the screen with a regular cable it does work and manjaro is recognizing the secound screen it just doesnt work with the dockingstation. even though in one install it did work.

If it’s a pure docking station issue and not a general system issue, I can’t help you any further as i have no experience with docking stations under Linux.


Ok. This is a very vital function for me and as I’ve said, it did work at one point.

Thank you for your help anyway. :smiley:

1 Like

Which docking station model is it exactly?
For some of them firmware can be upgraded.

What I would try also is to unplug the powercable for a minute or so. Power off NB, disconnect power supply/cable from docking station. Wait a minute. Plug power back in. Start NB.

1 Like


–> Its the Thinkpad Ultradock 40A2

–> I’ll try that on the next chance. thanks.

There are firmware upgrades for that model. See list of fixed issues further below in the linked text file. Some of them are related to display port and using 2x DP output…

Unfortunatly you can only apply them with Windows OS

1 Like

Thank you i’ll give it a try but the weird thing is that at one point (an earlier install) it did work.
This is so weird.
Anyway thank you :slight_smile:

Yes there are weird things happening with docks sometimes. So far it always helped to cut the power and let the docking “reboot”.

1 Like

inxi --full --admin --verbosity=7 --filter --no-host

is just a long redundant way to type: inxi -azv7

to avoid those hard to read side scrolling code boxes on narrow forums like manjaro, add a y: inxi -yazv7 and suddenly the output will be far more readable for users.

-v7 has more data than -F/–full, and when you remove --full from the string, and --no-host, you’ll see that there is zero change, -z/–filter implies --no-host

Trying to make inxi harder to use or add more characters to get a result doesn’t really help users in my opinion, it just makes it sound far more complicated to run than it really is.

Note that it was manjaro that requested that --no-host be rolled into -z, which was done quite a while ago.

If you find yourself mixing -b, -F, or -v general output levels, you are probably making a mistake since -b is for basic output, -F is for limited but relatively full output, and the -v levels help fill in the gaps between -b and -F and actually full output. They aren’t intended to be used together, and it’s largely pointless in almost all cases to do so.

I beg to differ. As my background is in development and system engineering on multiple *nix dialects, the long version is the clear way of writing inxi -azv7.
A command gets written only once, but gets read multiple times, and to newbies coming over here, the long version gives more information whereas the short version needs everyone to read the man page.

Think of everyone reading your code and the time it takes to understand your code, whereas the time it takes to read and understand mine: your code takes less time to read and type, but mine takes a fraction of yours to understand.

I.E. I’ve only been e-mailed once about any of the code I wrote in the last 30 years and that was because said developer was unfamiliar with the obscure language variant that was the corporate standard at that time. (I advised him to hand that project over to someone else or take the time to study for 3 days before attempting to change my code) :man_shrugging:

P.S. I should actually change inxi --full --admin --verbosity=7 --filter --no-host to inxi --full --admin --verbosity=7 --no-host --filter as that is even more understandable…


cc @cscs :stuck_out_tongue_winking_eye:

I’m not going to argue this, but you are giving wrong suggestions based on wrong understandings, it’s clearly not related to any experience since it’s wrong.

Again, use EITHER -b/basic OR -F/full OR -v/verbosity!!! Don’t mix them, it’s silly and redundant and confusing for users. Note that by your reasoning, we also do it this way:

inxi --basic --full --verbosity 7 --filter --no-host --width

in that case, -full overrides --basic, --verbosity 7 overrides --full, and --filter implies --no-host. The reason that manjaro itsel asked for -z to trip --no-host was specifically to include in filter the host name exclusion, that is, excluding hostname is a feature of filter, not an additional filter added,

It may appear to be more understandable by postiing nonsensical redundant lists of arguments to you, and I can’t stop you promoting this nonsense, but please don’t’ pretend it has any rational basis is reality, it just means you don’t understand how to use inxi, that’s all, and insist on sharing your confusion over and over.

Using such silly redundant forms won’t of course give ‘wrong’ results, they cancel each other out, but it does give users a totally wrong idea.

Given this appears to be some obsession you’ve generated however, I clearly can’t get you to stop this silly stuff, but I would like other users to be aware that it’s just a pointless waste of typing.

I’ll give up on this now since this isn’t about rationality or actual understanding of how to use inxi, it’s just some fixed idea you’ve developed and won’t let go of, even when the developer tells you are doing it wrong.

For other users, again, don’t waste your typing, for almost all common inxi options, there are short forms which can be combined into convenient easy to type strings, like:

inxi -bxyz
inxi -bayz
inxi -Fxxyz
inxi -FJayz
inxi -azyv7
inxi -aGy

and so on. You really don’t become more L33T by typing a lot of redendant arguments in long form.

So I’ll give up on this one, lol, have fun with endless pointless typing…

and do add --width if you must have all these add, so at least we can read the output in reasonable format, or -y.

This is too silly to spend more time on, I thought I’d try reason, but that appears to be a waste of time, so I guess do whatever you want, lol…

and now I have to move on to more real things, but people, please, don’t listen to the verbose redundant suggestions offered here, and elsewhere by this confused person, read the -h menu, pick what you think will be right for your case, and use it, inxi is supposed to be fast and easy to use, not convoluted and confusing.