On Sun, 2021-06-20 at 18:00 -0600, Chris Murphy wrote: > On Sun, Jun 20, 2021 at 3:48 PM Patrick O'Callaghan > <pocallaghan@xxxxxxxxx> wrote: > > > > If I power on the dock on after startup is complete, one drive > > appears > > immediately and the other takes 30 seconds or so, so the delay is not > > being caused by the boot process itself. It must be the hardware (the > > drive or the dock) taking that long for whatever reason, possibly > > power > > management as George suggested. As I've said, my goal is to convince > > the kernel that it doesn't need to wait for this so as to continue > > with > > the startup. > > > > dmesg will show this whole sequence: dock appearing, bus appearing, > drive on bus appearing, partition map appearing. I couldn't open the > previous journal log provided, it wasn't publicly visible or I'd have > taken a gander. The logs are now publicly visible at: https://drive.google.com/drive/folders/1nGwVkeTJh5hz4dYRBD7Ikpx6q4MaPki9?usp=sharing I've included my home-grown 'dock' scripts for completeness, plus logs of a Fedora Live boot (with no delay) and my current installed system (with the delay), both with unchanged hardware. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
