![]() The only purpose here is for subsequent sudo commands (like the last one) not to require us to enter authentication, as it is kind of hard to type a password into a terminal when your screen is locked already )Īfter this we invoke the operating system and choice of desktop/GUI/window manager specific lock command, being xflock4 for xcfe in Linux Mint 20. We simply invoice sleep 0.1 as a dummy command. In the first line we invoke sudo to enable root/super user level authentication. ![]() For this guide, we will use Linux Mint 20 running xcfe.Įcho disk | sudo tee /sys/power/state # Requires sufficient swap space Implementation of this will depend on the operating system, as well as the chosen Desktop/GUI.Ī quick search in your favorite search engine for lock Linux Distribution GUI from the command line where screen is an optional word/search term, Linux Distribution is the name of your Linux distribution, and GUI is the name of your GUI (like xcfe for example), will reveal one or more ways to lock your terminal from the command line. We thus need a script which will not just hibernate, sleep or freeze our machine but also one which will lock our desktop for us. An easier way to do things, and presumably the default way on all modern Linux operating systems, would be to simply leave /sys/power/mem_sleep set to deep and write freeze to /sys/power/state to Suspend-To-Idle, and to write mem to /sys/power/state to Suspend-To-RAM. Note also that it is thus possible to use two different ways to Suspend-To-Idle: either by writing freeze to /sys/power/state, or by writing s2idle to /sys/power/mem_sleep and subsequently writing mem to /sys/power/state.Īs you can see, the terminology used is slightly confusing and intermixed due to the presence of the /sys/power/mem_sleep file. Suspend-To-RAM, which is set by using deep in /sys/power/mem_sleep) rather than the Suspend-To-Idle mode as signified by s2idle. ![]() ) on all Linux operating systems, simply because when one sets the /sys/power/state option to mem, one would expect the system to write the contents to memory (i.e. Also, if you are running anyĪpplication that affects IRQ timing, such as irqbalance, try disabling it.Generally speaking I would expect this option to be set by default to deep by default (as indicated by Manager app (for example from Ondemand to Performance). Lockups happen after you change your CPU time scaling scheme using a power To be that it has something to do with CPU time scaling. I'm not quite sure what causes this, but the consensus seems Using an SMP kernel, which, I have noticed sometimes hangs because of IRQ Had, I don't think, but I've had a similar problem: it looks like you're Mathias, the problem that you're having is not exactly the same as the one I name | 858.605.4580Įntity Communications, LLC | entitycom. > You received this bug notification because you are a direct subscriber > Feisty freeze, kernel (?) tries to access DVD drive > the drive, seems not to cause a system freeze. I haven't tried installing libdvdcss3 but not having a DVD inside > This doesn't happen only on encrypted DVD. There is no disk in the drive? It sounds like you can only work normally if Read, are you getting that too? Also, is your system locking up even if When I first insert the media, saying that a particular block could not be Messages can probably help us identify the problem. ![]() Not possible, try attaching /var/log/messages. The attached file is today's dmesg output, which is the only one which presented an (automagic!) solution to the problem.Ĭan you post the tail of dmesg after the system starts to hang? Or if that's To disable DMA, I've added this line to /etc/nf:īy thw way, this is my drive: hdc: TSSTcorpCD/DVDW TS-L632D, ATAPI CD/DVD-ROM drive. hdc: drive not ready for commandĪs I don't use the drive that much, I think I'm gonna disable DMA and see if the problem doesn't appear anymore. But now that's better because I can still see dmesg, and I see this message repeated all the time: Now I've switched to Ubuntu Feisty and it doesn't freeze anymore, but it gets really slow and as you said the system only answers 1 out of every 15 seconds. alsa) stopped, then only I could move the mouse but it didn't answer to mouseover or mouseclick events, and finally (when I pressed a keyin the keyboard or after some seconds) it freezed completely and I had to hit the reboot button. The freeze was step by step: first music (amarok. In Ubuntu Edgy with kernels 2.6.17 it just freezed and I had nothing to do but reboot the computer and I could not see kernel messages. I don't know if it's a software (driver) or hardware (drive, firmware) problem, but it's completely annoying. I've been having this pretty same problem since I got this laptop.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |