07-25-2023, 10:12 AM
(07-23-2023, 08:30 PM)Cornelia Xaos Wrote: I've been using a combination of USB-A to USB-C adapters to do all manner of things from usb tethering off my phone, utilizing a USB-A wifi adapter, and using a USB to ethernet adapter. While all of these options previously worked with the danctnix installation, none of them appear to be functioning with Mobian.
Can you share the exact type of network/wifi adapters?
The 'friendly' identifier is hopefully enough, but `lsusb` also outputs a USB ID in the form of <4-numbers-or-a-to-f>:<4-numbers-or-a-to-f> and that uniquely (and precisely) identifies the device.
The Mobian system has 2 types of issues:
- Missing kernel modules for several devices
- The 'non-free-firmware' archive component is not enabled and thus no firmware is available or installed. Especially wifi devices often require it to function at all
Quote:The USB ethernet adapter worked with danctnix and the USB wifi adapter worked once I upgraded the device.. but after installing U-Boot and Mobian according to the instructions, while the operating system appears to function, I cannot get any level of network connectivity to hopefully get my wifi adapter functioning.
The danctnix update gave you a new kernel where some extra modules were likely enabled. Possibly some extra firmware too.
While Mobian lacks it. Even after enabling 'firmware-non-free' and installing the firmware package my wireless device needs, it still doesn't work. Which is 99% certain due to missing kernel modules, which are present in 'normal' Debian kernel (and is therefor also much larger in size).
The USB non-wireless NIC does work, but the weight of the adapter and cable likely isn't too good for my USB-C-to-A adapter.
Quote:Interestingly, both the USB to ethernet adapter and the USB wifi adapter show up under `lsusb` and there's a "usb0" connection that shows as "unavailable" when running `nmcli`, but I'm at a bit of a loss at this point for what to do now.
The kernel sees the USB ID and therefor knows what it is. But if the kernel module which would make it work isn't available, then it can't make it actually work.
I noticed the usb0 thing too, but I don't know where that's coming from.
