Although my knowledge is very limited, I somehow managed to install Arch (before EOS has been created) and whenever I run into some problem I search on my own and sooner or later I find how to fix. But for the following I’m unable to find solution:
The only way to be able to use a USB stick is to have it already plugged in during boot. I’m unable to “see” it when plugging in after boot or even when remove and add again, it will not show up (also not in lsblk).
I assume the Kernel is loading the something, which is required for USB Stick detection, only when the stick is plugged in during boot.
Please can anyone help?
Thank you.
Welcome to the forum. Thanks for giving EndeavourOS a try. I hope you enjoy your time here.
First I assume you installed the OS with EndeavourOS LiveISO.
Second what Desktop Environment are you using?
I believe udev is mainly responsible for detecting USB drives being plugged in. I am also sure other things are also involved,
I had that same problem on a very basic XFCE install. If I remember correctly both gvfs and gnome-packagekit had to be installed to fix the problem. But in this case I think lsblk -f did detect the USB device.
Thank you.
I’m not on EOS, but Arch (installed already before EOS existed).
DE is GNOME.
gvfs and gnome-packagekit is installed. I can use USB stick w/o problem when it was already plugged in during boot. My problem is if USB stick was not already plugged in during boot.
lsblk -f not detecting anything
Ah, I can see this is not your first rodeo. Yes pastebin is OK. My bad, I should have mentioned ix.io
The preferred method here is inxi which is in the Arch AUR. It’s usage is
"command" | curl -F 'f:1=<-' ix.io
Which will produce an URL such as http;//ix.io/R3hs
then just list the URL in your post.
However pastebin is fine for now.
So it looks like the correct kernel modules are in place. So let’s try to eliminate a corrupted USB drive. I’m sure you have tried the following, but to be sure.
Does the suspect USB drive work on another Linux, MAC, or gasp WIndows machine?
Does a new or otherwise known good USB stick work in the suspect machine?
If both of those are false, it will start to get nasty.
The USB stick is fine, works on other notebook as well as on mine notebook if it was already plugged in during boot.
Same behaviour with other USB sticks.
Should I get same logs after rebooting with usb stick plugged in?
I believe the above logs would be pretty much the same with it plugged in at bootup.
What would be interesting is if after booting with the USB stick plugged in, does lsblk -f
or fdisk -l show the USB device? If so then, it would have to be something involved with recognizing the action of the USB stick being plugged in while OS is up and running.
That kind of gets us back to udev. I assume this install of Arch is systemd? If so, maybe some service is not getting enabled in systemd?
lsblk -f and fdisk -l show the USB stick WHEN it has been plugged in during boot but not when it was not plugged in during boot.
Arch with systemd
could be some systemd service or similar. Basically I believe it is such a simple issue, but I’m unable to find on my own. I believed it is rather the kernel then systemd, but my knowledge is very very low, therefore often not clear for me what is systemd and what is kernel.
Edit: http://ix.io/2nbq
(as you can see a bit special hard drive, but shouldn’t affect USB stick?!?)
These daemons or services are started by configurations started by systemd at boot and should not be affected by what is or isn’t plugged into a USB port.
But it will interesting to see.
Let’s go back to the statement above. Are you saying the suspect USB device is recognized on other devices when plugged in at boot up, but not when plugged in with a running OS on different machines?
