4

I've upgraded from 17.10 recently and now no removable device is recognized.

Neither cat /proc/partition nor fdisk -l shows the devices.

Improve this question
3
  • 2
    fixed after changing from X.Org X server to NVIDIA drivers
    – Anahit Vardanian
    May 4, 2018 at 13:57
  • I have the same problem after update (from 17.10 to 18.04) - no pop-up shown and the USB stick is not mounted. Changed the login type to "Ubuntu on Wayland" which didn't help (at the beginning). The strange thing is that after some time (like 5-10 minutes) it started to work on Wayland (I suspect if first started to work on the USB port I usually use the stick). Maybe it's worth playing with Wayland and all the USB ports (sounds disappointing, but at least works for now).
    – user1228603
    Aug 20, 2018 at 5:29
  • 2
    @AnahitVardanian I have converted your comment into a community wiki answer since comments might be deleted for various reasons. If you wish to post it on your own, let me know by pinging in comments using @Kulfy. I'll delete my answer.
    – Kulfy
    Sep 4, 2019 at 12:27

2 Answers 2

Reset to default
2

I had the same problem after upgrading 16.04 to 18.04. USB memory sticks, printer or even mouse would not be recognized. As mentioned in the above answer, after 10-20 minutes a memory stick was sometimes recognized. What worked consistently was connecting the device at boot time. Another thing I found was the device WAS listed in the connected devices list but NOT mounted! I could manually mount it with mount command but the mounted device still would not show up in Nautilus!

Finally found the answer when I decided to tackle the laptop overheating problem. (Read about it here: Ubuntu 18.04 systemd-udevd uses high CPU, conflict with wifi). Indeed my CPU usage was at 100%. The moment I disabled bluetooth from BIOS, the CPU usage became normal - between 10 to 25%, overheating stopped and now the USB devices are getting recognized too!

So it means the whole problem was due to high CPU usage! Probably the other processes were not getting CPU time to do their stuff. I'm no expert on OSs, but this is a logical guess :-).

Improve this answer
2

From the comment by Anahit Vardanian:

fixed after changing from X.Org X server to NVIDIA drivers

Improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .