At first run of setup usb lan devices will not correct listed. You can still configure it but the manufacturer and device entries are empty. I have tested this on arm and intel nightly builds for core123 Should we revert the update?
We can do this for now, but eventually we will need to find out what is going wrong...
This commit has been reverted because no fix was present and the release should not be blocked by this: https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=df74fcbff940c9b92cd51be36a5b7c831f9b5292 Please figure out why this updated caused this problem.
At the moment I have no idea about what is going wrong here (testing did not show this issue, but no USB LAN devices were in place) but I will take care of this.
https://github.com/gregkh/usbutils/commit/94986fc7abcc6bd932a3f45501e83f4f5a4126f2 > The lsusb binary does not use the usb.ids file anymore, instead it uses > the udev hardware database. Mentionning usb.ids in lsusb(8) is therefore > very confusing for the users. This patch therefore drops that part. So I guess we have to make sure the udev hardware database is properly present. @Arne: Do we even need usb.ids anymore?
I fear the udev hwdb is also generated from this usb.ids list at udev startup. Also at the time of S75firstsetup udev is already started and running. So i still not understand why lsusb is not working.
(In reply to Peter Müller from comment #4) > @Arne: Do we even need usb.ids anymore? Yes, we want to know what hardware is connected when we run "lsusb".
Closing this, since I believe it is a duplicate of bug #12667, which was fixed in Core Update 164. Please reopen, if necessary. *** This bug has been marked as a duplicate of bug 12667 ***