DHCP Problem after FOG menu
-
This is what I get from the device manager under hardware ID
usb\vid_17E9&PID_431F&REV_0102&MI_05
-
@chrisyoung said in DHCP Problem after FOG menu:
usb\vid_17E9&PID_431F&REV_0102&MI_05
OK good the linux translation would be [17E9:431F]
DisplayLink Network Adapter NCM
From https://wiki.gentoo.org/wiki/DisplayLink
Required kernel parameters
Device Drivers —>
<> Network device support —>
<> USB Network Adapters —>
-M- CDC NCM support
<M> CDC MBIM supporthttp://nothen.com.ar/en/support-for-displaylink-adapters-on-linux/
Specific linux kernel driver code: http://nothen.com.ar/resources/displaylink-1.0.68.txzIf I understand correctly the cdc ncm module is needed and should be part of linux 4.7.2 onwards.
-
I am not exactly sure but back in my mind I remember that we had issues with those CDC drivers and possibly removed those from the current kernel. Yes, looks like it: https://github.com/FOGProject/fogproject/blob/dev-branch/kernel/TomElliott.config.64
# CONFIG_USB_NET_CDCETHER is not set # CONFIG_USB_NET_CDC_EEM is not set # CONFIG_USB_NET_CDC_NCM is not set
Let me see if I find those old posts in the forum…
-
-
Quoting myself from the post here:
I just found out that all the RTL8152/8153 based connectors are blacklisted in the cdc_ether driver (see here: http://lxr.free-electrons.com/source/drivers/net/usb/cdc_ether.c#L686). Your microsoft NIC isn’t just because they don’t know/care about those yet I guess.
The issue we had was that MS surface devices wouldn’t properly boot with those CDC drivers in the kernel. As we didn’t need those back then we just removed them back in late 2015. I wouldn’t recommend using a kernel that old.
@Tom-Elliott Do you mind adding this driver to the kernel? http://nothen.com.ar/resources/displaylink-1.0.68.txz
@chrisyoung Or you could just build your very own kernel following the wiki article here: https://wiki.fogproject.org/wiki/index.php?title=Build_TomElliott_Kernel
-
@Sebastian-Roth Sorry to not read much, but do you by chance have straight up dmethod I could use to add?
-
@george1421, @Sebastian-Roth Turns out I can enable the NCM and MBIM without the EEM and CDCETHER (If I remember correctly, the cdcether was the thing causing all of our issues).
-
Kernels are updated with NCM and MBIM support.
Please try:
wget -O /var/www/fog/service/ipxe/bzImage https://fogproject.org/kernels/bzImage wget -O /var/www/html/fog/service/ipxe/bzImage https://fogproject.org/kernels/bzImage wget -O /var/www/fog/service/ipxe/bzImage32 https://fogproject.org/kernels/bzImage32 wget -O /var/www/html/fog/service/ipxe/bzImage32 https://fogproject.org/kernels/bzImage32
-
@Tom-Elliott Nice, it will be interesting to see if that addresses the issue.
It does appear that these DisplayLink chipset (and variants) are used in quite a few of these new external tablet docks from different hardware vendors. So if this addresses the OP’s issue without creating new headaches its a good move to add to the fog kernel.
-
@Tom-Elliott Great stuff! Yeah from what I see in those MS surface posts it was only the CDC -ether driver causing the issue. Keeping my fingers crossed…