I've always had problems with systemd not actually waiting for the network to be up before letting network dependent services run.
Now the last couple of updates I've installed I have a new symptom: The system appears to (sometimes) zoom right past something that would allow USB to work correctly. My USB keyboard and mouse won't work, I get mail about the system losing connection to the APC UPS box (which is plugged into a completely different USB port than the keyboard and mouse).
Is anyone else getting random USB failures at boot?
At least I can ssh into the system and run shutdown, and USB (so far) has worked correctly following a powerup from scratch.
Maybe I should just stop using reboot and always power down :-).
On 05.03.2015, Tom Horsley wrote:
Is anyone else getting random USB failures at boot?
I'm using an APC UPS as well, and a USB mouse and keyboard. Have not encountered a single problem yet. F21, fully updated.
[root@chiara ~]# lsusb Bus 004 Device 002: ID 8087:8001 Intel Corp. Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 8087:8009 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 174c:5106 ASMedia Technology Inc. Transcend StoreJet 25M3 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:0101 Cypress Semiconductor Corp. Keyboard/Hub Bus 001 Device 005: ID 1038:137a SteelSeries ApS Bus 001 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[root@chiara ~]# uname -a Linux chiara.fritha.org 3.19.1-rc1-bfq #1 SMP PREEMPT Thu Mar 5 08:47:53 CET 2015 x86_64 x86_64 x86_64 GNU/Linux
-
Heinz Diehl -
Tom Horsley