I have installed Debian 8.1 with KDE desktop on Lenovo t431s with intel HD4000 graphics.
When using it with dual monitor configuration, I experience the problem when I put system to sleep (by closing the lid), then remove the external monitor cable (from miniDP port) and then try to wake system from sleep. The login screen freezes and I am unable to move the mouse or type in credentials. In case I had music player running I can hear the music after system wake , but it shutters while playing.
This does not happen on some other distributions, but the problem is that I very much like my current setup and I would like to fix this problem and keep it.
I do not know if this problem is due to KDE or KDM or it's Debian base.
I have Debian Jessie 8 installed on a Acer 5733 Laptop. After I closed the screen, it goes sleeping, and when I open it, aleatory, it freezes. I don't have graphical interface, and the tty are not accessible. Sometimes, I get access to the computer 10 seconds, and then freeze.I have to shutdown the computer...and lose my work I was doing.I thought it was a X-problem, but the tty don't work too, so it's not ? When I restart the computer, it shows Code: Select allclearing orphaned inode <some inode number.
Whenever I close my laptop lid or just press the suspend button, it will go to sleep just fine. Perfect. Waking up is the problem. The drive light flashes for a few seconds, and then it just goes to back to normal but my display is still busted.
I'm running 9.10, how do I wake up from sleep or hibernation on my Dell XPS notebook? I have no problem putting the comp to sleep/hiber but can't seem to work out the keys to wake it up again.
I don't get any responses from the keys even when I try CAPS LOCK or NUM LOCK, so all I can do is reach for the on/off switch.
I am running Ubuntu 9.10 on my desktop and everynow and then I get this annoying problem. If I walk away for a bit, just upstairs to use the bathroom, sometimes when I come back the monitor is off and the power light is blinking. You know, like what monitors usually do when they are still powered on but the screensaver is done playing. However, this happens to me well before the 10 minutes that the screensaver is supposed to end.
It does not always happen, and I can't really isolate what may be causing it, as I never take a note of what I'm doing when I go pee. HOwever, I rarely do anything other that run VLC, Chrome, Firefox, or OpenOffice Writer.
The problem is that the screen won't wake up. Moving the mouse does nothing. Jamming some keys does nothing. Trying to go to text terminal does nothing. I have to either REISUB or hold down the power button on the tower.
I just recently got my old box back and now I'm running 10.4. I've had some minor issues that I have got through but now there is one which seems to really be frustrating me. At any random time my monitor may go black as if it is in sleep mode. The problem is when it does this, no mouse movement or keystroke will wake the thing up. So I am forced to press the power button. When I press the power button the Ubuntu logo pops up on the screen as if it magically woke up but it is too late because now the computer is shutting down... When I go to System>Preferences>Screensaver I get to the options for the screensaver and I have about 2 seconds before that triggers the screen going black.
I can't even start until I know that my screen won't shut off at any random moment!
I have dist-upgrade from Wheezy to Jessie, however it randomly freezes. Everything was okay with kernel 3.2, but when I run several applications kernel 3.16 fails.
At below you can see the dmesg output of Jessie:
Code: Select all[ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09)
I installed Jessie day before yesterday on a freshly formatted partition. After a random time, it hangs. If I am playing music at the time, the music continues for a few more seconds _after_ the mouse and keyboard become unresponsive, if that is useful.
Sine I did not understand how to pick the desktop during the installation, I installed Gnome. Afterwards, I installed KDE. Now I have a lot of Gnome stuff around I don't really need. But they are in principle compatible, right?
This morning, the hang was almost immediate after logging on. Only Iceweasl and Amarok and a Konsole were running. I attempted to start Icedove, when everything hung.
Here is the relevant part of the syslog.
Dec 8 07:41:38 jon-desktop rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="775" x-info="http://www.rsyslog.com"] rsyslogd was HUPed ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^
I have installed Debian 8 Jessie on my mid 2009 (5.5?) macbook pro. My computer is dual booted with OS X. I installed / on a partition with 30GB space, /home with 40GB, and swap with 4GB. My computer states are: 4GB ram, Intel Core Two Duo CPU 8700 2.53 Ghz x2, Graphics Gallium 0.4 on NVAC. The system has been running great compared to any other distro I have tried, except for that it randomly freezes sometimes. I've been running it for 4 days now and it has locked up 4 times.
Twice waking from suspend, once when changing the desktop background photo, and once after a reboot. I've a little afraid of messing with NVIDIA drivers as I tried that with various other distros and every time I rebooted after using these drivers the system would never boot into GUI and crazy kernal panic would insue. This is the closest I have come to successfully running linux on my mac. If there are any logs or information I can provide to find a solution to the freezing that would be amazing, because I absolutely love this setup!
By freeze, I mean that the mouse can still move, but everything else behind it is frozen entirelyI can switch to a terminal with CTRL+ALT+F1, it's ... I guess... X or gnome-shell or something that's frozen? Not the whole OS thoughThese freezes last anywhere between 5 or 10 seconds and 3-5 minutesI can't predict when they will occur, but often, after a suspend/resume, they will start occuring much more frequently. Also, they often happen after I enter my password and press ENTER on the lock screen after a resume from suspend. But not exclusively -- they can happen at any other time when I'm doing pretty much anything in GNOME...
Things I've Tried...
When frozen, I've tried to CTRL+ALT+F1, login, and run gnome-shell --replace... [*[When frozen, I can successfully CTRL+ALT+F1 and run `service gdm restart`... with the obvious downside of losing everything I have open. But the screen responds immediately and I can log back in to GNOMEI tried running `Xorg -configure` to generate an /etc/X11/xorg.conf file to edit, but received an error about not being able to generate configuration for multiple screens or something (I can retry and provide the exact error if this is a useful direction to try) is it the gnome-shell freezing? Is it X? Is it a problem with the X driver I'm using?
I've configured my F12 system to go to sleep when idle for a period of time and so far everything has been working out well except that it appears that the USB ports are completely dead with the system is put into sleep. I can't wake it using keyboard or mouse. only with the power button. Anyoen else experience this or know how to allow sleep from keyboard/mouse?
Firstly, wol works fine from shutdown and hibernate; it's just suspend which doesn't work.
I've got 2 types of workstations, all running 11.1. They both have this kernel: 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100 x86_64 x86_64 x86_64 GNU/Linux
Type 1 is a dell optiplex 745, bios version 2.4.1. Here's the relevant bit from lspci: 03:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02) Kernel driver in use: tg3 Kernel modules: tg3
[Code]....
The fact that it's happening across two different machines makes me wonder if it is some OS setting I've missed, but then maybe neither card/driver supports it from suspend.
I'd really like to get them waking from suspend because training users to use suspend rather than hibernate would be a pain. Also, being able to configure such that it only wakes from suspend and not hibernate/shutdown, as implied in the bios, would allow me to wake machines up for backups etc only when the users are here, rather than on holiday/seconded to another department etc.
My laptop won't wake from sleep. I hit the powerbutton and it'll blink a few more times, turn green and the keys will light up but the screen stays black.
Running sony vaio s with windows 7 and 11.4 duelboot. I really need it to be able to suspend and wake because I'll be taking it to college in the fall.
I'm having some trouble getting Ubuntu Netbook Edition to work properly on my Netbook. If I close my netbook for long enough for it to go asleep, which only takes 10-20 seconds, then when I open it back up and press the power switch, nothing appears on the screen.
I have an interesting issue. I have a computer running Ubuntu 10.10. I have a wireless USB Microsoft keyboard attached to this, and I have a cheap USB infrared remote also attached to it.The wireless USB Microsoft keyboard can wake up the system from suspend. The USB infrared remote cannot.To start off, I made sure my /proc/acpi/wakeup had wakeup enabled for all usb devices.
Code: xbmc:~$ cat /proc/acpi/wakeup Device S-state Status Sysfs node
Is there any way to find out which device/event caused Ubuntu (10.10) to wake up from the most recent sleep/hibernation? I am trying to troubleshoot some sleep issues on a new box, and knowing what's causing it to wake up would help. I did check /var/log/pm-suspend.log but all it seems to say is Sat Dec 11 22:18:27 GMT 2010: Awake.
I have openSUSE 11.4 KDE (upgraded to Tumbleweed but that's not relevant here). The computer is a Dell Optiplex. My sleep (suspend to ram) and wake (restore from ram) work very well. The box can multiboot to windows 7 as well as to Linux.
In Linux, the restore process is triggered by pressing the power button on the front of the case. No other action will bring it awake.
In windows, the restore process is triggered by the power button but also by moving the mouse or touching the Escape key, spacebar etc.
Here's the question: how do I get the computer to wake in Linux by activating a key (or mouse, whatever) instead of just the power button (which is under the desk and hard to get to)?
This morning I woke up and while my computer was turned on, I couldn't wake my monitor up from "sleep". So I turned off the computer and turned it back on. I noticed that the normal boot screen (which usually shows a monster truck from Abit) was pretty severely distorted.Basically all output to the screen is so distorted visually that I can't tell what's going on. I've attached two images that I took below:
The first image is at the very beginning of the boot (perhaps when the monster truck should normally show <- sometimes it shows and sometimes it is just too distorted to tell anything). The second image is after it's been on for about a minute, and you can see a little text box giving me some sort of warning (which I of course can't read). I can click "OK" or something along those lines by using they keyboard though and progress to a new warning box, but again, can't read what they say. How can I figure out what the problem is?s it definitely a videocard thing, or could this be caused by anything? I don't know if it's a software problem (running Ubuntu 10.04), or if something went wrong with my hardware overnight.
I upgraded to fedora 11 from fedora 10 yesterday, I like it ok but when I put the machine in sleep mode and then go to turn it back on it comes up to the log in screen and thats it its frozen. I hate to completely shut down the machine every time I get off.
I've recently installed Ubuntu 11.04 on my MBP4,1. Whenever I wake the laptop from sleep the trackpad seems to freeze up. Everything else works - I can use the keyboard to switch through programs and interact with them, but I can't move the trackpad at all.
I am hosting a home server to make developing stuff easier. And because I don't need my server all day and night I automatically start and shut it down. For starting I use Wake-On-Lan (etherwake) and to shut it down I am using my RaspberryPi. Finally I have a problem doing that: When I use WOL to start my home server it works perfect. But when I try to shut it down, I have to do that twice. After the first shutdown it restarts automatically even when no WOL-Package is sent.
I am using Debian 8.1 Mate as os.
My stop script is:
Code: Select allsshpass -p<password> ssh root@server.home.lan shutdown -h now
I came back to debian after trying many others because it installed flawlessly and worked. I'm on the testing channel and upgrade nearly everyday and after a recent upgrade my xsession (Xfce4) display won't wake up any more after I close and re-open the lid. I know the box is awake because I can go to a ctr-alt-fn console login and use it normally. How can I track this down? And is there some way I can restart the gui display from the console without losing what was running before I shut the lid? Right now the only way I can recover is to restart the computer.
I have installed Debian Jessie (<-- brilliant OS ) on my uncles Laptop (it is a Thinkpad E540) with Cinnamon as desktop environment. The installation was no problem. Everything apart from one minor thing works nicely. The minor thing however is the following:
I don't know what it is, but when I don't use a particular usb port for a while and then try to plug in a usb stick or a wacom tablet, it doesn't get recognized, it doesn't show up when I use f.e. Code: Select alllsusb. When I close the lid of the laptop and open it again, then the particular usb device gets recognized and cinnamon asks me what to do, f.e. open a folder and show the content of the usb stick I have plugged in. Because of the success on two other laptops I use the following
to save power on the Thinkpad (this is in no way my service script, I tuned everything using powertop in the terminal after having had logged in, the script above stems from a brilliant user here on the forum). Could it therefore be autosuspend that is not working properly here?
I recently switched back to Debian after getting fed up with Ubuntu. The one feature that I haven't been able to get back since the switch is Wake on LAN.If I turn on the computer and watch tcpdump, I can see the packets hitting my machine. I don't think it's a router configuration issue.If I shut down from windows, WOL works.Another sign that it's not a networking or BIOS thing.Here's some stuff I've tried:When I boot up in linux, if I run ethtool eth0, it tells me that wake is set to g (which every guide I've read says is correct).Just in case, I added "post-up /usr/sbin/ethtool -s $IFACE wol g" to /etc/network/interfaces (as shown here: ewtopic.php?f=5&t=42049&p=244736&hilit=wakeonlan#p244736). Also added same thing for post-down.
In /etc/init.d/halt, I changed NETDOWN to no (also from previous guide) to keep my eth card from being shut down.Also changed /etc/init.d/networking to exclude eth0 (as documented in Added "pre-down false" to /etc/network/interfaces.. trepid+wol), to keep eth0 from being shut off.Anyway, I'm guessing that either there's another script somewhere shutting off eth0 or I'm completely wrong in assuming that's the problem. I've been googling this problem for a couple weeks now and I'm totally out of ideas.
I'm am able to WOL my computer when it has been halted (or shutdown, which is basically the same thing for the problem I'm facing). The problem comes when I try to WOL the computer when it is suspended or hibernated. Then, it does not work.
I've been investigating for a while and have found that when halting, the following is done in the /etc/init.d/halt script:
[code]...
But I don't know which script must be modified in case I want the network not to be brought down when the computer is suspended or hibernated.
Suspend worked before I completely reinstalled Testing from scratch. Now it seems to suspend OK, but when it tries to wake up it fails. Details here: [URL]
