-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No devices found - 1.14.1+, kernel 6.7* #451
Comments
Loaded module:
|
Using an fprobe attached to
kernel log:
|
Adding another fprobe for the USB notifier also does not report any events:
|
After studying I've added PR Issue #453 "module: add README with instructions on usage" to address this. Although outputs now show up the host still has the same problem as others have reported; the physical devices are not discovered. |
Update with system config now
Summary of the kernel log (full log is attached):
|
I added logging to
|
In order to determine what the userspace daemon
When connecting the DL hub the
|
I think I'm having the same issue as you (although I haven't done any fiddling with the logs), Whenever I connect or disconnect a display from my docking station, I don't see any messages on dmesg or anything related to evdi. I have evdi and displayport installed on Arch, the daemon is working and evdi is listed on dkms. Also, nothing shows up when I strace the process when disconnecting the display. |
Edited based on realising DKMS had cached an old copy of the source so changes in
/usr/src/evdi-1.14.1/
were not being builtWhen doing
modprobe evdi initial_loglevel=6
the kernel log only shows:I added
pr_info()
messages to ensureevdi_init()
was completing - and it is:unloading and reloading the module doesn't improve things; nor does unplugging and reconnecting the Dell D3000 USB3 hub. Kernel correctly reports the USB devices being discovered:
Udev rules are triggered and userspace seems to do its part correctly, creating
/dev/displaylink/by-id/usb-002-006-DisplayLink_Dell_USB_3.0_Dock_31108357
and thedisplaylink.service
is active andDisplayLinkManager
running.Debian 12 Bookworm, amd64, v6.7.1+debian+tj
I build upstream kernels with the Debian kernel config and a handful of my own patches (none of which would cause this!) E.g:
I suspect this is caused by recent kernel changes - I shall pepper the module with
pr_info()
to try to identify what is (not) working.The text was updated successfully, but these errors were encountered: