you have rebooted since update? Every time updates generate a new startup? file I lose network, printing and usb until I do a reboot. Just what you need when doing a backup to a slow usb drive mick in glen innes 2370 On Tue, 24 Mar 2020 at 18:32, Robin Martijn <ik@robinmartijn.nl> wrote:

I see that I made a mistake in the mail subject. My apologies for that.

Thanks a lot Justin! My port is open in the bios and firmware. My USB keyboard and mouse do get recognized.

When I run `ls -ld /usr/lib/modules/5.5.11-arch1-1`, I get the following result:

`drwxr-xr-x 4 root root 4096 Mar 24 15:26 /usr/lib/modules/5.5.11-arch1-1`

To me, that looks like a good result. The folder is filled with what I would expect in such a file.

The USB controller is recognized correctly by `lspci`, but that probably isn't very unexpected since my USB keyboard and mouse are functioning.

Thank you very much for thinking with me!

...

Have you looked at lsusb -t ? Maybe the port is disabled in your bios/firmware? Verify that you are booting a kernel you have (modules for) ls -ld /usr/lib/modules/`uname -r` check which usb controllers you have, lspci, they will be *hci

On Tue, Mar 24, 2020, 11:00 AM Robin Martijn <ik@robinmartijn.nl> wrote:

...

Currently, I am using linux 5.5.11.arch1-1. Since this version, I am unable to use my USB storage drives. Nothing shows up in dmesg when inserting the storage drive and also lsblk does not detect the drive. lsusb also does not detect the drive. I have rebooted my system after the kernel update, more than once actually, so I am sure that that is not the problem. Would anybody know what could potentially be the

On 3/24/20 7:25 PM, Justin Capella via arch-general wrote: problem?

...

...

Thanks in advance!

On Tue, 24 Mar 2020 at 22:57, Andy Pieters <arch-general@andypieters.me.uk> wrote:

On Tue, 24 Mar 2020 at 21:38, mick howe via arch-general < arch-general@archlinux.org> wrote:

...

you have rebooted since update? Every time updates generate a new startup?

I concur: in many cases you need to reboot after doing a kernel update in order to recognise devices that were not plugged in before the update

Indeed. To also explain why this happens: the relevant kernal modules hadn't been loaded yet, and the modules on disk are for the newly upgraded kernel while you're still running an older kernel. In that case, `pacman -Qi linux` and `uname -r` will also show different version information. -- Maarten

Update: Thanks everyone for helping me think! Finally, I discovered that all three of my USB devices were broken. A fourth one finally connected. I should've known when dmesg did not see anything at all, that they were broken. On 3/24/20 11:27 PM, Robin Martijn wrote:

Thanks everyone for thinking with me! However, I have indeed rebooted many times, and I have verified my versions. I am, with no doubt, on the right kernel.

On 3/24/20 11:02 PM, Maarten de Vries via arch-general wrote:

...

On Tue, 24 Mar 2020 at 22:57, Andy Pieters <arch-general@andypieters.me.uk> wrote:

...

On Tue, 24 Mar 2020 at 21:38, mick howe via arch-general < arch-general@archlinux.org> wrote:

...

you have rebooted since update? Every time updates generate a new startup?

I concur: in many cases you need to reboot after doing a kernel update in order to recognise devices that were not plugged in before the update

Indeed.

To also explain why this happens: the relevant kernal modules hadn't been loaded yet, and the modules on disk are for the newly upgraded kernel while you're still running an older kernel. In that case, `pacman -Qi linux` and `uname -r` will also show different version information.

-- Maarten