Home / user-219972

WoJ's questions

Martin Hope
WoJ
Asked: 2022-01-15 03:42:46 +0800 CST
  • 0

Note: I read two other questions (here and here) that address the same problem but none of the solutions is applicable to my case.

I run Pi-hole in a docker container as my DNS server - for the server it is running on (Ubuntu 18.04), and the rest of my home network. It works fine, everything resolves as expected.

Except in one specific case: when Pi-hile itself is starting. It wants to check something on the Internet and fails because the DNS resolution obviously fails.

This is not the end of the world but this triggered my question: can I set up systemd-resolved so that it chooses a DNS server based on the requested domain?

The questions in my introductory note mention the ability to do a split DNS but my understanding is that the DNS can only be set on a per-NIC basis. In other words, for one interface there can be only one DNS (or several backup ones, what I mean is that there is no possibility of dynamically choosing the one to use).

Is this understanding correct?

networking
Martin Hope
WoJ
Asked: 2021-04-18 09:03:28 +0800 CST
  • 1

I have a machine (18.04, will be 20.04 at some point) that has a wired NIC as well as a USB card with a wireless one. It is usually connected by cable, but sometimes the cable is disconnected (mechanically, by someone, for various reasons).

I would like to ensure that the static IP 192.168.10.1 is always reachable:

  • either via the cable when it is plugged in,
  • or via Wi-Fi when it is not.

Is there a standard (or at least reasonable) way to do this?

I saw an answer to a question that was suggesting to assign this IP to the lo interface:

ip address add IP/32 dev lo

but I am not sure this is a reasonable approach?

networking
Martin Hope
WoJ
Asked: 2020-07-14 03:21:41 +0800 CST
  • 1

I see in the Ubuntu lifecycle and release cadence documentation that there is a difference made between "maintenance updates" and "hardware updates".

What exactly are "hardware updates"?

Are these:

  • updates to currently supported hardware (say, I have an Intel Skylake which is already supported, and these are new updates for that equipment)
  • support for new hardware, not supported before?
  • both?
  • something else?
updates hardware
Martin Hope
WoJ
Asked: 2020-02-22 05:41:10 +0800 CST
  • 1

I run a home server on Ubuntu 18.04. It boots from a M2 internal drive (/dev/sda1) and basically

  • mounts another drive (/dev/sdc1)
  • mounts an LVM partition (/dev/mapper/data-data)
  • starts docker which in turn runs a set of containers

I would like to test a disaster scenario where the M2 (boot) drive fails. My backup is stored on /dev/sdc1 (and also remotely, which is the same type of testing).

In order to perform the test I would like to

  • remove the M2 drive (this is to simulate its failure, and also protect from a mistake which would damage it)
  • plug in an external USB drive (USB drive 1)
  • boot from a Ubuntu ISO (flashed on USB drive 2)
  • install Ubuntu on the external drive (= on USB drive 1, and then remove and forget USB drive 2)
  • install docker and other utilities, recover the backup, start the containers etc. ← that part is simpler as I (hopefully) understand how to orchestrate the activities.

My main concern (there may be others I am not aware of) is whether the external USB drive will be recognized as a "proper" drive to install the system. Are there limitation on the kind of connectivity for an installation?

The alternative is to borrow an M2 drive and swap the existing one with the "recovery" one but I would prefer to do the testing on the USB one, which I already have.

Additionally - are there any possible problems with the testing process above? (especially the part from "disaster" to having a shell prompt and start the last point -- I am sure I will discover a lot of problems in the last one but I will be able to handle them fine, the booting process which I am not that acquired with is the one I do not feel comfortable with)

system-installation data-recovery backup hard-drive
Martin Hope
WoJ
Asked: 2019-07-29 06:36:24 +0800 CST
  • 3

I use Wireguard as my primary VPN (running a server and having several clients connecting to it) - it works fine but I realized today that I do not understand how it is actually managed. It is the following sequence of events which led me to that realization:

  • client A and client B are defined in /etc/wireguard/wg0.conf. They both connect correctly.
  • I added some packages that modified the kernel. This triggered the usual messages about modprobe etc. I never really paid attention to those as they were acknowledgements that everything was OK.
  • when the step above is done, client A is still connected, client B does not connect anymore. I am trying with a client C and it connects.

I then had a look at wg show and it was not showing peer B. Since peer B (= client B) is in /etc/wireguard/wg0.conf then something must have gone wrong. Solution: reboot.

After the reboot client A reconnects automatically, client B still does not connect (and is still not visible in wg show, even in the disconnected state).

How could have it be connected in the first place at all? (I ask myself).

Last idea:

wg-quick down wg0
wg-quick up wg0

and everything is back to normal, client A and client B connect.

This means one thing: the initial (post-boot or post-apt-which-changed-kernel) startup of wireguard must use another configuration file. This is conceivable - client A was set up a long time ago and client B added only recently (to /etc/wireguard/wg0) so it may be that I forgot where I set this up.

I had the problem above once in the past, now that I remember it, and fixed it with the two wg-quick commands but had no time to debate any further (which would explain how client B managed to connect at all)

My question: in Ubuntu 18.04, what is the service actually starting wireguard (installed from the wireguard PPA) and where is the configuration file used by that service?

networking server vpn wireguard
Martin Hope
WoJ
Asked: 2019-03-01 11:43:44 +0800 CST
  • 2

When reading How do I restrict a specified SSH user to connect only from one IP or hostname? I came close to solving a problem I have with specific logins - but it does not cover my case.

I need to ensure that an ssh connection to my host coming from anything else than 192.168.10.0/24 is authenticated via a key. Connections from 192.168.10.0/24 can use both (or only password based if this is a problem).

The ssh_config man page mentions in the PATTERNS section that

the following entry (in authorized_keys) could be used:

from="!*.dialup.example.com,*.example.com"

This would allow for a solution exactly opposite to mine: that some sources are not allowed to use keys but I do not see how to turn it into my need.

How to force the use of ssh keys when the client does not connect from certain IPs?

networking ssh password login
Martin Hope
WoJ
Asked: 2018-03-15 00:52:22 +0800 CST
  • 1

I would like to setup an OpenVPN server which would accept credential based authentication from clients. The concept is described in the documentation:

While it is discouraged from a security perspective, it is also possible to disable the use of client certificates, and force username/password authentication only. On the server:

client-cert-not-required

Such configurations should usually also set:

username-as-common-name

which will tell the server to use the username for indexing purposes as it would use the Common Name of a client which was authenticating via a client certificate.

Where and how is this password set up?

I would like it to be the same for all clients (which would just identify themselves via the username, per username-as-common-name above)

networking vpn openvpn
Martin Hope
WoJ
Asked: 2017-06-02 02:38:19 +0800 CST
  • 2

I use systemd (xenial) and want o be up to date. To do so, I install Martin Pitt's PPA and everything is fine.

On one system (not special in any way, this is a clean install actually), despite the PPA being configured ...

root@eu11:~# apt update
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:2 http://fr.archive.ubuntu.com/ubuntu xenial InRelease
Hit:3 http://fr.archive.ubuntu.com/ubuntu xenial-updates InRelease
Hit:4 http://fr.archive.ubuntu.com/ubuntu xenial-backports InRelease
Hit:5 http://ppa.launchpad.net/pitti/systemd/ubuntu xenial InRelease
Fetched 102 kB in 0s (297 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

... systemd is installed from the standard repository.

root@eu11:~# apt show systemd
Package: systemd
Version: 229-4ubuntu17
Priority: required
Section: admin
Origin: Ubuntu

What can be the reason for such behaviour? (I did not configure any pinning because I do not know how to do it, never having had the need before)

This is the output of apt-cache policy systemd :

root@eu11:~# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu17
  Candidate: 229-4ubuntu17
  Version table:
 *** 229-4ubuntu17 500
        500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     229-4ubuntu10 500
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
     229-4ubuntu4 500
        500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
apt
Martin Hope
WoJ
Asked: 2016-11-24 03:55:58 +0800 CST
  • 3

I wanted to update systemd on my 16.04. In order to access to upstream, I use Martin Pitt's PPA. The version there is 232+upstream20161120-0.master.

The version I have is 

root@srv /e/apt# apt-cache showpkg systemd
Package: systemd
Versions:
229-4ubuntu12 (/var/lib/apt/lists/fr.archive.ubuntu.com_ubuntu_dists_xenial-updates_main_binary-amd64_Packages)
(...)

Reverse Depends:
  libpam-systemd,systemd 229-4ubuntu10
  udev,systemd 224-2
(...)
Dependencies:
229-4ubuntu12 - libc6 (2 2.17) libgcrypt20 (2 1.6.1) (...)
Provides:
229-4ubuntu12 - systemd:i386 (= 229-4ubuntu12) systemd-services:i386 (= ) systemd-services (= )
229-4ubuntu10 - systemd:i386 (= 229-4ubuntu10) systemd-services:i386 (= ) systemd-services (= )
229-4ubuntu4 - systemd-services:i386 (= ) systemd:i386 (= 229-4ubuntu4) systemd-services (= )
Reverse Provides:
systemd:i386 229-4ubuntu10 (= 229-4ubuntu10)
systemd:i386 229-4ubuntu12 (= 229-4ubuntu12)
systemd:i386 229-4ubuntu4 (= 229-4ubuntu4)

It looks like the PPA is not taken into account even though it is in /etc/apt/sources.list.d and part of apt update:

root@srv /e/apt# apt update
Hit:1 http://fr.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://fr.archive.ubuntu.com/ubuntu xenial-updates InRelease
Get:3 http://fr.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB]
Hit:4 http://ppa.launchpad.net/ansible/ansible/ubuntu xenial InRelease
Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]
Hit:6 http://ppa.launchpad.net/pitti/systemd/ubuntu xenial InRelease
Fetched 187 kB in 0s (638 kB/s)

Candidates for upgrade:

root@srv /e/apt/# apt list --upgradable | grep systemd

libpam-systemd/xenial-updates 229-4ubuntu12 amd64 [upgradable from: 229-4ubuntu10]
libsystemd0/xenial-updates 229-4ubuntu12 amd64 [upgradable from: 229-4ubuntu10]
systemd/xenial-updates 229-4ubuntu12 amd64 [upgradable from: 229-4ubuntu10]
systemd-container/xenial-updates 229-4ubuntu12 amd64 [upgradable from: 229-4ubuntu10]
systemd-sysv/xenial-updates 229-4ubuntu12 amd64 [upgradable from: 229-4ubuntu10]

I also checked that it is not pinned somewhere, but /etc/apt/preferences.dis empty.

EDIT: info requested in comments:

root@srv ~# apt-cache policy systemd
systemd:
  Installed: 229-4ubuntu10
  Candidate: 229-4ubuntu12
  Version table:
     229-4ubuntu12 500
        500 http://fr.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 229-4ubuntu10 500
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
        100 /var/lib/dpkg/status
     229-4ubuntu4 500
        500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Why isn't the last version of the packaged suggested as an update?

apt
Martin Hope
WoJ
Asked: 2016-08-17 09:33:25 +0800 CST
  • 2

I installed kodi from the standard repositories (Ubuntu 16.04 xenial):

# apt show kodi
Package: kodi
Version: 2:16.1~git20160424.1410-final-0wily

The web site for kodi states that the latest version is 16.1 "Jarvis".

What is the relationship between these two version numbers?

The install wiki mentions that one can use the team PPA but I do not know whether the versions diverge.

apt
Martin Hope
WoJ
Asked: 2016-07-25 03:24:25 +0800 CST
  • 1

I have an otherwise working systemd-nspawn managed container (minimal Ubuntu 16.04 from debootstrap) but I cannot make it restart when crashed/rebooted.

The unit file is

# cat /etc/systemd/nspawn/minec.nspawn

[Exec]
Boot=yes

[Network]
Bridge=minec

[Service]
ExecStartPre=-/sbin/ip link del vb-minec
Restart=always

Specifically, I was expecting Restart=always to respawn the system if it is powered off or rebooted (from within the container) or otherwise crash.

I was wondering if the reason is not because systemd sees a shutdown/ poweroff as the equivalent of a systemctl stop? If this is the case - is there a way to change this behaviour?

Otherwise, is there anything else to setup to have it restart?

boot
Martin Hope
WoJ
Asked: 2016-04-24 11:13:54 +0800 CST
  • 3

I would like to edit LXD profiles from the command line. This is done by lxc profile set:

lxc profile get <profile> <key> Get profile configuration.

lxc profile set <profile> <key> <value> Set profile configuration.

What is the expected format of the <key> <value>? The output from lxc show profile suggests a dotted structure:

root@ubuntu ~# lxc profile show zoneminder
name: zoneminder
config:
  raw.lxc: lxc.aa_allow_incomplete=1
description: ""
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: zoneminder0
    type: nic

but I did not manage to get anything (not to mention - set). I tried various incantations (as an example lxc profile get zoneminder name, lxc profile get zoneminder lxc.name, ... to get the value of name above) but they all return nothing.

lxc
Martin Hope
WoJ
Asked: 2016-04-24 01:34:38 +0800 CST
  • 28

Ubuntu has dropped Python 2 in 16.04. It is still installed after an upgrade, though (it was not part of the "obsolete packages").

Is there a clean way to remove Python 2 and all its dependencies in a clean way (to completely get rid of it)?

Is an apt purge the way to go?

root@ubuntu ~# apt purge python2.7
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  libnss-ldap
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  auth-client-config* ldap-auth-client* ldap-auth-config* libpam-ldap* libsmbclient* ndiff* python* python-bs4* python-chardet* python-crypto* python-dnspython*
  python-html5lib* python-ldb* python-lxml* python-ntdb* python-pkg-resources* python-samba* python-setuptools* python-six* python-talloc* python-tdb* python2.7* samba*
  samba-common-bin* samba-dsdb-modules* samba-libs* samba-vfs-modules* smbclient* winbind*
0 upgraded, 0 newly installed, 29 to remove and 0 not upgraded.
After this operation, 58.4 MB disk space will be freed.
package-management
Martin Hope
WoJ
Asked: 2016-03-28 11:18:11 +0800 CST
  • 4

I get media files which are not indexed by kodi (running on Ubuntu 15.10) - they need to be renamed first (and then they get indexed and fully processed).

I did not find any built-in solution in kodi to monitor and rename files - beside an explanation about the format they should be in. There is also a list of recommended standalone software.

I am surprised that the renaming is no built into kodi and before jumping in with cron and filebot I wanted to make sure that I will not be reinventing the wheel.

xbmc
Martin Hope
WoJ
Asked: 2016-03-19 12:43:20 +0800 CST
  • 1

I have a Ubuntu machine (15.10) running as a gateway which routes / firewalls traffic between a LAN an Internet.

I need to block Internet access during some hours for specific devices on the LAN.

Before jumping into scripting iptables rules which will be enabled/disabled via cron, I wanted to check whether there is no such a service/program already existing. Neither a repository check nor Google searches brought in anything relevant.

networking
Martin Hope
WoJ
Asked: 2016-03-16 04:29:13 +0800 CST
  • 2

I installed LXD and created a few containers and while reading about various configurations (specifically about how to run unprivileged containers as root), I saw that the configuration files referenced in the various pages are

  • multiple (/etc/lxc/default.conf, /var/lib/lxc/<container>/default, ...)
  • and for the most part do not exist on mu Ubuntu 15.10.

It looks like the lxc command is the actual way to go, for instance

# lxc profile show test1
name: test1
config: {}
description: ""
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: br2
    type: nic

I do not understand how information of the kind

Append to [one of the config files mentioned above]

lxc.id_map = u 0 100000 65536
lxc.id_map = g 0 100000 65536

fits into the lxc command (if at all):

  • should I be editing the configuration via lxc profile edit test1 - in which case where (to take the example above) would lxc.id_map = u 0 100000 65536 go in?
  • or use something like lxc config set test1 raw.lxc 'lxc.id_map = u 0 100000 65536'? (when tested, it does not appear in the profile after execution)
  • or something else?
lxc
Martin Hope
WoJ
Asked: 2016-03-09 12:32:33 +0800 CST
  • 4

I installed lxd to use linux containers. For some reason I keep using lxc commands to install and start my containers. Since lxd seems to be close to lxc maybe there is a reason for that (but it is not clear).

I wanted to bind two lxc containers to two different bridges, different from the default lxcbr0 one. I created br1 and br2 and gave them IP addresses. They work fine and are pingable.

I am now trying to locate the place where I should change the configuration of my containers (cont1 and cont2) in order to have their eth0 (the interface name can be kept the same for each of those guests) bound to respectively br1 and br2.

The documentation states that

Then, specify the host's bridge in the container configuration file in place of lxcbr0, for instance

Where is this configuration file?

At the top of this documentation page, there is information about configuration files:

The following configuration files are consulted by LXC. For privileged use, they are found under /etc/lxc, while for unprivileged use they are under ~/.config/lxc.

lxc.conf may optionally specify alternate values for several lxc settings, including the lxcpath, the default configuration, cgroups to use, a cgroup creation pattern, and storage backend settings for lvm and zfs.

default.conf specifies configuration which every newly created container should contain. This usually contains at least a network section, and, for unprivileged users, an id mapping section

lxc-usernet.conf specifies how unprivileged users may connect their containers to the host-owned network.

lxc.conf and default.conf are both under /etc/lxc and $HOME/.config/lxc, while lxc-usernet.conf is only host-wide.

By default, containers are located under /var/lib/lxc for the root user, and $HOME/.local/share/lxc otherwise. The location can be specified for all lxc commands using the "-P|--lxcpath" argument.

If I read it correctly, it does not indicate where the container config file is.

The configuration I would like to add for cont1 is 

lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br1
lxc.network.name = eth0
lxc.network.ipv4 = 10.10.11.0/24
lxc.network.ipv4.gateway = 10.10.11.11

and I tried to put it in the files /etc/lxc/cont1/config and /var/lib/lxc/cont1/config but none was taken into account: the container does not start, failing to bring up the networking. It works fine with the default config using lxcbr0.

networking
Martin Hope
WoJ
Asked: 2014-01-22 01:40:23 +0800 CST
  • 3

I initially asked this question on SU but it is so specific to Ubuntu that I move it here.

I installed an 433Mhz transceiver on my Ubuntu system (3.8.0-35). It is an USB-to-Serial kind of device and is somehow recognized:

dmesg output:

[  324.051498] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[  324.088070] usb 3-1: New USB device found, idVendor=10c4, idProduct=8668
[  324.088081] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  324.088087] usb 3-1: Product: NETUSB1100 NEWMSG 
[  324.088093] usb 3-1: Manufacturer: HZWB
[  324.102259] hid-generic 0003:10C4:8668.0002: hiddev0,hidraw1: USB HID v1.01 Device [HZWB NETUSB1100 NEWMSG ] on usb-0000:0e:00.0-1/input0

lsusb output:

Bus 003 Device 002: ID 10c4:8668 Cygnal Integrated Products, Inc.

I would like to access it (via rfxcmd for instance) but I cannot get a relevant /dev path. The contents of /dev do not change when I plug it in so there is certainly something missing.

What other steps must be done in order to create a /dev/... device path - which can be then used in scripts?

EDIT after lekensteyn's answer: output of tree /sys/bus/usb/drivers/ following a modprobe cp210x (with non-relevant parts removed). Please note that following a reboot the 3-1 above became a 3-2 below. I took that into account in the tests.

/sys/bus/usb/drivers/
├── cp210x
│   ├── bind
│   ├── module -> ../../../../module/usbserial
│   ├── uevent
│   └── unbind
├── hub
│   ├── 1-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-0:1.0
│   ├── 1-1:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1:1.0
│   ├── 2-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-0:1.0
│   ├── 2-1:1.0 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0
│   ├── 3-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3/3-0:1.0
│   ├── 4-0:1.0 -> ../../../../devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb4/4-0:1.0
│   ├── bind
│   ├── module -> ../../../../module/usbcore
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── usb
│   ├── 1-1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1
│   ├── 1-1.2 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2
│   ├── 1-1.3 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3
│   ├── 1-1.4 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4
│   ├── 1-1.6 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6
│   ├── 2-1 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1
│   ├── 3-2 -> ../../../../devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3/3-2
│   ├── bind
│   ├── uevent
│   ├── unbind
│   ├── usb1 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1
│   ├── usb2 -> ../../../../devices/pci0000:00/0000:00:1d.0/usb2
│   ├── usb3 -> ../../../../devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3
│   └── usb4 -> ../../../../devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb4
├── usbhid
│   ├── 1-1.2:1.0 -> ../../../../devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0
│   ├── 3-2:1.0 -> ../../../../devices/pci0000:00/0000:00:1c.6/0000:0e:00.0/usb3/3-2/3-2:1.0
│   ├── bind
│   ├── module -> ../../../../module/usbhid
│   ├── new_id
│   ├── remove_id
│   ├── uevent
│   └── unbind
├── usbserial
│   ├── bind
│   ├── module -> ../../../../module/usbserial
│   ├── uevent
│   └── unbind
├── usbserial_generic
│   ├── bind
│   ├── module -> ../../../../module/usbserial
│   ├── uevent
│   └── unbind

EDIT: added dmesg after cp210x.ko recompilation and reboot (with the new cp210x.ko)

[    1.352918] usb 3-2: new full-speed USB device number 2 using xhci_hcd
[    1.389854] usb 3-2: New USB device found, idVendor=10c4, idProduct=8668
[    1.389865] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.389871] usb 3-2: Product: NETUSB1100 NEWMSG 
[    1.389877] usb 3-2: Manufacturer: HZWB
[    1.399869] usbcore: registered new interface driver usbhid
[    1.399872] usbhid: USB HID core driver
[    1.406870] hid-generic 0003:10C4:8668.0001: hiddev0,hidraw0: USB HID v1.01 Device [HZWB NETUSB1100 NEWMSG ] on usb-0000:0e:00.0-2/input0

after a manual modprobe cp210x, the extra lines in dmesg.

[ 1313.312593] usbcore: registered new interface driver usbserial
[ 1313.312642] usbcore: registered new interface driver usbserial_generic
[ 1313.312674] usbserial: USB Serial support registered for generic
[ 1313.329536] usbcore: registered new interface driver cp210x
[ 1313.329575] usbserial: USB Serial support registered for cp210x
(end of file)
usb