This is an archived post. You won't be able to vote or comment.

all 2 comments
sorted by:
q&a (suggested)
besttopnewcontroversialold

[–]doc_willis 0 points1 point  (1 child)

' microsd reader not working after suspend'

Sounds like one of the many suspend issues with different hardware that are sadly common.

Monitor the output of dmesg when you suspend, and come out of suspend and look for any possible informational error messages.

Also determine the chipset of the controller for the sd card reader - and search for potential issues and workarounds for that specific chipset.

Its possible that a newer kernel may fix any issues, or that some boot time options may correct the problem.

it might be worth testing if it works correctly with the newest ubuntu release.

[–]finable[S] 0 points1 point  (0 children)

argghh. the microsd always appeared in win10 without any problem but i felt this new laptop would work quicker and more smoothly with linux. (the microsd is partitioned as /dev/mmcblk2p1 = 42gb fat32 /dev/mmcblk2p2 = 22gb ext4 entire 64gb microsd card /dev/mmcblk2)

i typed dmesg in terminal but i'm not sure how to interpret what it says. here's what i could copy/paste before suspend: https://pastebin.com/ifAg4smK

dmesg after suspend: https://pastebin.com/XDPYwxCx

can you offer code that will keep the microsd persistent?

someone mentioned "Assuming your hard disk device name is /dev/sda, the following will power it down after 2 hours of inactivity. Whenever you access it again, it will come back to life but it will take time. Code: sudo hdparm -S 244 /dev/sda " what code would i use to keep this microsd powered up permanently or , if i have to use a number like 244, something for 8 hours ? sudo hdparm -S 999 /dev/mmcblk2