I am hoping someone can help me here. I received my Nexdock 360 wired. There is no video when plugged to my phone. It says it was connected, i could use the mouse and keyboard on my Librem 5.
It seems Librem 5 is not sending video or Nexdock is not receiving video
Nexdock is recognized in Mobile settings under convergence.
Any suggestion?
Try different cables and orientations oft the plugs…
Yep, this is usually a cable thing.
Thank you for your quick responses. I shall order a new cable and try it again.
I have recently had to re-flash my Librem5 and am reconfiguring.
My nexdock lapdock does not get recognized by the phone in the mobile settings/convergence menu.
I can move the mouse and use the keyboard but nothing on the dock display. I used both supplied cables in all 4 orientations.
Any suggestions what to do now?
I’m just throwing this link in case it helps someone: Unlocking Your USB-C Port's Display Potential: A Beginner's Guide to DP Alt Mode . I’m currently traveling and took my (UPerfect) lapdock but forgot the cable at home, turning the lapdock into a useless extra weight to carry around. None of the cables I found in the shops support video.
However @michel_souris I understand your cable is fine if you say it’s the one that came with the dock.
Next option would be to look at Display Settings and check if the external display is turned on…?
Just putting it out there but doesn’t the Librem 5’s charging cable support video?
In the Settings/display tab there is only one display listed, the built-in one. Plus a tab for night light.
In the mobile settings app the Covergence still does show " no known docks detected ".
I’m still at a loss here, what’s next?
I had a similar experience with a Lenovo Thinkpad dock. A different USB-C cable fixed it. I went back to the old cable and got it to work by flipping USB-C connector end upside down (not that there’s an up or down side).
As I said above, I used both the official cables in all possible configs but no display on the dock, I can type on the L5 screen and use the mouse so there is some connection. And it was working fine before my L5 chocked on an update and had to be reflashed…
lsusb is always your friend for troubleshooting this kind of thing but, having said that, it would be most useful if you could compare the output from when it worked with the output now, and I imagine that that is not a possibility.
Looking for messages in the system log may also be useful.
If I understand correctly, lsusb will show - when you connect the lapdock - a USB hub appearing and, connected to that, a mouse and a keyboard appearing, but no display. Maybe a “billboard” will appear (indicating a display that wants to burst into life).
This is correct, i see a keyboard and touch pad, and a terminus technology inc. Hub, but no billboard or display.
I’m still at a loss here, any takers before I kick
this over to purism support?
Purism Support will probably want journal entries as suggested above. Are there any relevant ones?
Purism Support will probably also want the exact differences in lsusb output before and after plugging in the lapdock.
I wouldn’t worry about that. My lapdock gives the same message under Convergence and my dock works fine.
The lack of a display / billboard is the thing that needs to get solved.
Here’s the output of lsusb when my Uperfect is plugged in and does work:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 2020:2060 Qualcomm, Incorporated Qualcomm CDMA Technologies MSM
Bus 001 Device 003: ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
Bus 001 Device 002: ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 27c0:0819 Cadwell Laboratories, Inc. WingCoolTouch
Bus 003 Device 003: ID 1c4f:007c SiGma Micro USB Keyboard
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Apparently the lapdock is the Bus 003 entries, but I don’t see anything related to the display (just the touch screen, an input device). But the screen works fine…
That’s one thing that bugs me about Uperfect. Different models work differently. For the record when I plug in my Uperfect, among other things, I get:
Bus 003 Device 006: ID 1d5c:7102 Fresco Logic Generic Billboard Device
Would love lsusb to gain a -f option (by analogy with tail)
In the meantime,
lsusb >before.txt
(plug in)
lsusb >after.txt
diff before.txt after.txt
I did this and printed to diff.txt:
5a6,10
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 27c0:0819 Cadwell Laboratories, Inc. WingCoolTouch
Bus 003 Device 003: ID 258a:8072 SINO WEALTH USB KEYBOARD
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
dmesg -w is my go-to when there’s weird hardware behavior. Something, somewhere is logging what’s happening. The -w flag here will continually update the screen, so you can plug and unplug things to see how the kernel reacts in real-time.
It seems like your system is not picking up the display, and thus not cloning/extending the display area to include the nexdock. It may be helpful to check the output of journalctl -u udev.service (or the equivalent name; not on a systemd device at present) or udevadm monitor, then plug/unplug the nexdock to see what the kernel tells us.
EDIT: Corrected a mistake on my part; the kernel itself doesn’t see the display yet, very weird. This points to some sort of initialization issue, but you mentioned it worked fine in the past. Has anything changed with these cables? No snags or other physical stress?
EDIT2: If someone who’s lapdock/nexdock is working could post their lsmod output, that would also be helpful.
Not sure if you were necro-ing some old post or something, but in case it is helpful I fired up my recently acquired NexDock. It’s a NexDock 360 Wireless rather than NexDock 360 Wired, but I’m using the wire part of it.
Here’s what I’m seeing:
purism@pureos:~$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0424:4041 Microchip Technology, Inc. (formerly SMSC) Hub and media card controller
Bus 001 Device 002: ID 0424:2640 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 27c0:0819 Cadwell Laboratories, Inc. WingCoolTouch
Bus 003 Device 003: ID 1c4f:007c SiGma Micro USB Keyboard
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Here is the output of lsmod:
purism@pureos:~$ lsmod
Module Size Used by
st_magn_i2c 12288 0
st_magn 16384 1 st_magn_i2c
st_lsm6dsx_i2c 16384 0
st_lsm6dsx_spi 16384 0
st_lsm6dsx 45056 2 st_lsm6dsx_i2c,st_lsm6dsx_spi
hid_multitouch 24576 0
usbhid 45056 0
rfcomm 90112 4
algif_hash 12288 4
algif_skcipher 12288 4
af_alg 28672 18 algif_hash,algif_skcipher
bnep 24576 2
hci_uart 98304 1
btqca 24576 1 hci_uart
bluetooth 843776 31 btqca,hci_uart,bnep,rfcomm
brcmfmac_cyw 12288 0
brcmfmac 348160 1 brcmfmac_cyw
cfg80211 1032192 1 brcmfmac
brcmutil 28672 1 brcmfmac
qmi_wwan 36864 0
cdc_wdm 28672 1 qmi_wwan
usbnet 57344 1 qmi_wwan
mii 20480 1 usbnet
option 61440 0
usb_wwan 24576 1 option
usbserial 61440 2 usb_wwan,option
exfat 81920 1
st_sensors_i2c 12288 1 st_magn_i2c
st_sensors 28672 3 st_magn_i2c,st_magn
usb_f_acm 20480 2
u_serial 32768 3 usb_f_acm
usb_f_ncm 32768 2
u_ether 36864 1 usb_f_ncm
caam_jr 155648 8
caamhash_desc 12288 1 caam_jr
caamalg_desc 36864 1 caam_jr
crypto_engine 28672 1 caam_jr
ledtrig_pattern 12288 0
hantro_vpu 258048 0
snd_soc_gtm601 12288 1
v4l2_vp9 24576 1 hantro_vpu
snd_soc_simple_card 20480 6
v4l2_h264 16384 1 hantro_vpu
snd_soc_simple_card_utils 36864 1 snd_soc_simple_card
snd_soc_imx_hdmi 12288 1
snd_soc_hdmi_codec 24576 1
v4l2_mem2mem 53248 1 hantro_vpu
snd_soc_fsl_sai 32768 6
snd_soc_fsl_utils 12288 1 snd_soc_fsl_sai
snd_soc_wm8962 98304 2 snd_soc_simple_card_utils
imx_pcm_dma 12288 1 snd_soc_fsl_sai
snd_soc_core 319488 8 imx_pcm_dma,snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_gtm601,snd_soc_simple_card,snd_soc_wm8962,snd_soc_fsl_sai,snd_soc_imx_hdmi
leds_lm3560 12288 0
vcnl4000 32768 0
videobuf2_dma_contig 24576 1 hantro_vpu
mousedev 16384 0
industrialio_triggered_buffer 12288 3 st_lsm6dsx,st_magn,vcnl4000
v4l2_flash_led_class 16384 1 leds_lm3560
videobuf2_memops 16384 1 videobuf2_dma_contig
kfifo_buf 12288 2 industrialio_triggered_buffer,st_lsm6dsx
snd_pcm_dmaengine 16384 1 snd_soc_core
dw9714 12288 0
v4l2_fwnode 28672 0
videobuf2_v4l2 32768 2 hantro_vpu,v4l2_mem2mem
gnss_mtk 12288 0
v4l2_async 28672 3 v4l2_fwnode,v4l2_flash_led_class,dw9714
snd_pcm 155648 6 snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_core,snd_soc_wm8962,snd_soc_fsl_sai,snd_pcm_dmaengine
gnss_serial 16384 1 gnss_mtk
gnss 16384 1 gnss_serial
videobuf2_common 73728 5 videobuf2_dma_contig,videobuf2_v4l2,hantro_vpu,v4l2_mem2mem,videobuf2_memops
videodev 323584 7 v4l2_async,v4l2_fwnode,v4l2_flash_led_class,videobuf2_v4l2,dw9714,hantro_vpu,v4l2_mem2mem
mc 86016 8 v4l2_async,videodev,v4l2_flash_led_class,videobuf2_v4l2,dw9714,hantro_vpu,videobuf2_common,v4l2_mem2mem
caam 24576 1 caam_jr
snd_timer 40960 1 snd_pcm
imx2_wdt 16384 0
error 24576 4 caamalg_desc,caamhash_desc,caam,caam_jr
watchdog 32768 1 imx2_wdt
snd 110592 18 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm
imx_rproc 28672 0
soundcore 12288 1 snd
rfkill_hks 16384 0
rfkill 28672 8 rfkill_hks,bluetooth,cfg80211
leds_pwm_multicolor 12288 0
led_class_multicolor 16384 1 leds_pwm_multicolor
libcomposite 86016 13 u_ether,usb_f_acm,usb_f_ncm
ledtrig_timer 12288 0
fuse 147456 5
zram 28672 2
ip_tables 32768 0
x_tables 61440 1 ip_tables
ipv6 548864 70
autofs4 49152 2
uas 28672 0
usb_storage 86016 2 uas
mtdblock 16384 1
mtd_blkdevs 20480 2 mtdblock
overlay 163840 1
xhci_plat_hcd 20480 0
xhci_hcd 294912 1 xhci_plat_hcd
ofpart 16384 0
usbcore 344064 11 usbserial,xhci_hcd,usbnet,usbhid,usb_storage,cdc_wdm,usb_wwan,qmi_wwan,uas,xhci_plat_hcd,option
spi_nor 114688 1
mtd 94208 7 spi_nor,ofpart,mtdblock,mtd_blkdevs
aes_ce_blk 32768 1
crct10dif_ce 12288 1
ghash_ce 20480 0
sha2_ce 12288 0
bq25890_charger 36864 0
sha1_ce 12288 0
phy_fsl_imx8mq_usb 20480 8
dwc3 163840 1
pwm_vibra 12288 0
cdns_mhdp_imx 24576 0
ulpi 20480 1 dwc3
imx_dcss 40960 5
cdns_mhdp_drmcore 57344 1 cdns_mhdp_imx
drm_display_helper 196608 1 cdns_mhdp_drmcore
udc_core 81920 6 u_ether,u_serial,libcomposite,usb_f_acm,dwc3,usb_f_ncm
usb_common 20480 6 xhci_hcd,usbcore,libcomposite,xhci_plat_hcd,dwc3,udc_core
edt_ft5x06 53248 0
tps6598x 77824 0
clk_bd718x7 16384 0
typec 98304 1 tps6598x
roles 16384 2 tps6598x,dwc3
snvs_pwrkey 12288 0
imx_sdma 32768 10
virt_dma 16384 1 imx_sdma
These are being sent directly from the docked NexDock using NexDock keyboard, where everything is working and I used the dock to copy from the terminal.