FYI--what I learned about no-detect usb & Arch today

General system Kernel, boot, graphics & hardware
1

Got home a while back.
Did what looked like a big update.
Went back to work, inserted USB drive, Endeavour could not read it.
“Shi*” I had a lot to do so DDG’d this problem, went right to the Arch Board where the first forum responder said “this sounds like you did a kernel update and did not reboot. A USB won’t be read by the kernel until the reboot.”

I did not read another opinion, I just knew this was it, and it was.
Lesson learned: reboot after kernel update; do not go back to work.
I don’t get the loss of peripheral drives but it’s probably safety-related.

This is just a PSA/FYI for those that didn’t know. Dig it.

2 Likes
2

This happens not only on EndeavourOS but also on many other distros as well.

1 Like
3

can’t say I noticed tbh. I know two distros where usb is detected after updates, on the other hand.

4

Noticed this before as well, great info to pass on.

5

The reason is the kernel modules (on disk) don’t match versions with the kernel running (in memory). Yes, there is that thing that tells you that you should reboot after anything that causes a kernel rebuild (and a few other things). Heed it.

1 Like
6

interesting, thanks did not know

usually do but thought I could get on with my business another 3 hours. Apparently not. thanks for explaining the “why”

7

Well you probably could if you didn’t need any new kernel modules inserted…(been there, done that) lol. But inevitably…etc. Same logic with firefox requiring a restart after a new binary (that one gets me all the time).

1 Like
8

[Inserst GRRRRR emoji here]

9

I always restart after any update, saves headaches

5 Likes
10

It’s worse on Windows… you have to restart to update mostly everytime.

11

I think Windows would prefer you to reboot before scratching your mouse.