You are not logged in.
Pages: 1
Hi all,
Before I started with systemd, I was using pm-utils and pm-suspend and pm-hibernate were working fine. However, now that I am using systemd, I'm getting the above problem: pm-suspend and systemctl suspend both suspend fine, but will resume with a black screen. (The fans etc start running, but the screen remains blank.)
Here's what I've tried:
--- removed autodetect hook. Hooks are now:
HOOKS="base udev modconf block resume filesystems usbinput fsck"
and I have run mkinitcpio -p linux etc.
--- I have pm-quirks
--- did what I could from this post: https://bbs.archlinux.org/viewtopic.php?id=152381. I'm a relative newbie, so I didn't look into posts #13-#15.
--- Looked into this: https://wiki.archlinux.org/index.php/Pm … om_suspend and added the file to /etc/pm/sleep.d/ with no result. I have not tried the stuff about BIOS, as I don't even know what it means to go into the BIOS.
I've spent a few hours trying to figure this out, with no luck, so any help would be appreciated!
Much appreciated,
Ianhoolihan
Offline
Does journalctl show anything?
I laugh, yet the joke is on me
Offline
Hi there, I haven't used journalctl before, but here are the last few entries:
-- Reboot --
Jan 01 13:00:49 typewriter spideroak_inotify[8573]: Program started
Jan 01 13:00:50 typewriter spideroak_inotify[8573]: inotify_add_watch ignoring directory (access denied) /etc/sudoers.d
Jan 01 13:00:50 typewriter spideroak_inotify[8573]: inotify_add_watch ignoring directory (access denied) /etc/polkit-1/locala
Jan 01 13:00:50 typewriter spideroak_inotify[8573]: inotify_add_watch ignoring directory (access denied) /etc/polkit-1/rules.
Jan 01 13:00:51 typewriter spideroak_inotify[8573]: excluding path /home/archimedes/.SpiderOak (/home/archimedes/.SpiderOak)
Jan 01 13:00:52 typewriter spideroak_inotify[8573]: ignoring path /home/archimedes/.SpiderOak_old/fs_notify__dir_watcher_igno
Jan 01 13:04:11 typewriter spideroak_inotify[8573]: Parent process gone: stopping
-- Reboot --
Jan 28 08:57:46 typewriter spideroak_inotify[14198]: Program started
Jan 28 08:57:46 typewriter spideroak_inotify[14198]: inotify_add_watch ignoring directory (access denied) /etc/sudoers.d
Jan 28 08:57:46 typewriter spideroak_inotify[14198]: inotify_add_watch ignoring directory (access denied) /etc/polkit-1/local
Jan 28 08:57:46 typewriter spideroak_inotify[14198]: inotify_add_watch ignoring directory (access denied) /etc/polkit-1/rules
Jan 28 08:57:47 typewriter spideroak_inotify[14198]: excluding path /home/archimedes/.SpiderOak (/home/archimedes/.SpiderOak)
Jan 28 08:57:51 typewriter spideroak_inotify[14198]: ignoring path /home/archimedes/.SpiderOak_old/fs_notify__dir_watcher_ign
Jan 28 09:06:52 typewriter spideroak_inotify[14198]: Parent process gone: stopping
It doesn't seem to have anything to do with the suspend, though I shoud look into why SpiderOak is starting ...
However, I'm starting to think it has something to do with laptop-mode tools not playing well with systemd. Here's a list of some of my services from systemctl list-units:
console-kit-log-system-start.service loaded active exited Console System Startup Logging
cpupower.service loaded active exited Apply cpupower configuration
laptop-mode.service loaded active exited Laptop Mode Tools
So apparently laptop-mode.service (and the others) aren't continuing running? Will this have anything to do with it? There's also the following ones, but I'm guessing it's normal for them to be exited?
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup.service loaded active exited Recreate Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
Edit: I am also using LXDE, so this post is relevant: https://bbs.archlinux.org/viewtopic.php?pid=1227000
I am on a Thinkpad X40, so this post is relevant, though the issue seems different (and I don't have xf86-input-synaptics installed): https://bbs.archlinux.org/viewtopic.php?pid=1155371 (See post #130).
It seems thinkpad_acpi may be related. I don't know what the big warning on this page http://www.thinkwiki.org/wiki/Thinkpad-acpi means, but I do have thinkpad_acpi installed.
Cheers
Last edited by ianhoolihan (2013-02-04 11:05:49)
Offline
Does that span of time in the journal include when the laptop froze?
If not, you can specify which part of the journal you want to look at with this variable:
--since=, --until=
Start showing entries on or newer than the specified date, or on or older than the specified date, respectively. Date specifications should be of the format "2012-10-30 18:17:16". If the time part is omitted, 00:00:00 is assumed. If only the seconds component is omitted, :00 is assumed. If the date component is omitted, the current day is assumed. Alternatively the strings yesterday, today, tomorrow are understood, which refer to 00:00:00 of the day before the current day, the current day, or the day after the current day, respectively. now refers to the current time. Finally, relative times may be specified, prefixed with - or +, referring to times before or after the current time, respectively.
I pulled it from the man page for journalctl. You can read more about it here: http://www.freedesktop.org/software/sys … alctl.html
I would use both 'since' and 'until' and narrow the output to just the time period containing the incident.
Last edited by the sad clown (2013-02-05 04:24:37)
I laugh, yet the joke is on me
Offline
BTW, there is an easy way to check if LXDE is causing an issue, and that is to use a different environment (try something small like dwm that doesn't need a whole lot of dependencies to try out) and see if you continue to have the same issue.
Also, if you are using LXDE to suspend, you can test alternate means of suspending and see if these have the same problem:
I laugh, yet the joke is on me
Offline
1. Setup SSH and see if you can login to your computer from another computer when it's 'frozen'. This should tell you if it's actually frozen or if there may just be a graphics driver or screen backlight issue.
2. I did a recent upgrade where now the backlight won't turn on until I switch to another VT after resume and then back again. (Ctrl-Alt F2, then Ctrl-Alt F1 to get back to my X session). Annoying, but at least I can work around it.
Scott
Offline
Wouldn't an easier method simply be to have a terminal open when he suspends. Upon wake up, he should be able to issue a command (reboot?). If it works, then it's just the screen.
Better yet, if he has a hotkey that opens a terminal.
Last edited by the sad clown (2013-02-05 04:45:26)
I laugh, yet the joke is on me
Offline
Does that span of time in the journal include when the laptop froze?
Indeed, my computer has had the suspend issue many times during the month of January.
BTW, there is an easy way to check if LXDE is causing an issue, and that is to use a different environment (try something small like dwm that doesn't need a whole lot of dependencies to try out) and see if you continue to have the same issue.
Also, if you are using LXDE to suspend, you can test alternate means of suspending and see if these have the same problem:
Interesting point. At the moment I will assume it isn't LXDE since there's never been any issues before, and I don't use LXDE to suspend. (Actually, I will try to suspend using the lxde-logout application later, and see what it does.)
1. Setup SSH and see if you can login to your computer from another computer when it's 'frozen'. This should tell you if it's actually frozen or if there may just be a graphics driver or screen backlight issue.
2. I did a recent upgrade where now the backlight won't turn on until I switch to another VT after resume and then back again. (Ctrl-Alt F2, then Ctrl-Alt F1 to get back to my X session). Annoying, but at least I can work around it.
Scott
That's clever Scott. I don't actually know how to SSH into my own computer (etc). I will try the sad clown's suggestion first. I am fairly certain I tried switching tty, but to no avail. I will test this later though.
Wouldn't an easier method simply be to have a terminal open when he suspends. Upon wake up, he should be able to issue a command (reboot?). If it works, then it's just the screen.
Better yet, if he has a hotkey that opens a terminal.
OK, I have tried using my hotkey to start a terminal, but that didn't seem to work. Hmmm, I am using vlock, and while I've been logging in blind, it's probably best to disable that (in my handler.sh) until I've fixed this. Oh, and I've never explicitly left a terminal open, so I will also try it.
Thanks for all the helpful suggestions, and I will post back soon to let you know if it worked. If not, I may be tempted to do a complete re-install soon (lots of bloat as a result of learning how to install Arch for the first time etc). If that doesn't work, I may have to move to the likes of OpenSUSE --- which is the solution another archer took who had this exact same problem.
Cheers,
Ianhoolihan
Offline
OK, tried:
---open terminal when suspend and then rebooting
---switching from to one tty and back
---installing uswsusp and using s2ram, with the following /etc/suspend.conf:
snapshot device = /dev/snapshot
resume device = /dev/sda2
#image size = 350000000
#suspend loglevel = 2
#compute checksum = y
#compress = y
#encrypt = y
#early writeout = y
#splash = y
In all cases, nothing happened. Actually, I can tell it's not just a video issue, as althought the fans turn on for some reason, none of the usual thinkpad lights do (AC power, flashing wireless, hard-drive write) though the sleep one (half-moon) stays on. Hmmm, any other suggestions?
Thanks for your help,
Ianhoolihan
Offline
2. I did a recent upgrade where now the backlight won't turn on until I switch to another VT after resume and then back again. (Ctrl-Alt F2, then Ctrl-Alt F1 to get back to my X session). Annoying, but at least I can work around it.
Well, i'm having the same issue since kernel 3.7, only after hibernation, suspend works perfectly here. (i thought it was tuxonice related, even if it always worked on my system, but now i'm pretty sure it is kernel related.)
@ianhoolihan: post:
journalctl -a | grep systemd-sleep
after the issue (hope you don't mount your logs in tmpfs!)
Offline
@ianhoolihan: post:
journalctl -a | grep systemd-sleep
after the issue (hope you don't mount your logs in tmpfs!)
No output I'm afraid = (
If this is all kernel related, when can we expect a fix?
Ianhoolihan
Offline
If this is all kernel related, when can we expect a fix?
Ianhoolihan
That depends. What kernel are you using?
I laugh, yet the joke is on me
Offline
Same issue here. Sometimes after sleep I have a blank screen, cannot open other TTYs and wifi also does not work. The machine freezes and there is no obvious error in kernel logs.
Machine: Thinkpad x220
Kernel: 3.7.5-1-ARCH
Last edited by spinx (2013-02-05 15:35:00)
Offline
Well, i guess it is someway related to linux 3.7.
Try installing linux-lts and see if it works, at least we'll know that!
Offline
Same here, with kernel 3.7.5-1.
Cheers
Offline
Yeah, it could be related to kernel version 3.7. Until last week with kernel 3.6 there was no problem. It would be nice to force this issue to debug where it is from. Does anyone know how to recreate it exactly?
Edit: Perhaps it is also related to https://bugs.launchpad.net/ubuntu/+sour … ug/1085837, than it would be also an issue under 3.6
Last edited by spinx (2013-02-05 16:29:43)
Offline
Another option to linux-lts is this: http://sakuscans.com/pacmanpkg/x86_64/ although it is only for x86_64 processors. I've switched to it due to issues with gpu freezing after waking from suspend.
You can read up on the thread following it here: https://bbs.archlinux.org/viewtopic.php?id=150743&p=14
Last edited by the sad clown (2013-02-06 03:09:26)
I laugh, yet the joke is on me
Offline
Hi all, I downgraded to Arch 3.6.11-1, and all the issues seem to have gone away. Not a real solution, but a temporary fix.
Ianhoolihan
Offline
Hi guys ! i have a similar problem! I have installed catalyst driver from repositories! When resuming from suspend to ram (systemctl susend or pm-suspend ) my screen is powered off!!
sudo journalctl -a | grep systemd-sleep
Feb 10 15:29:50 funky systemd-sleep[1385]: Suspending system...
Feb 10 15:33:32 funky systemd-sleep[1385]: System resumed.
Feb 10 15:54:07 funky systemd-sleep[552]: Suspending system...
Feb 10 15:54:18 funky systemd-sleep[552]: System resumed.
I tried the terminal and change tty .Not one of them worked.
My kernel is 3-7-6.1
Offline
Another option to linux-lts is this: http://sakuscans.com/pacmanpkg/x86_64/ although it is only for x86_64 processors. I've switched to it due to issues with gpu freezing after waking from suspend.
You can read up on the thread following it here: https://bbs.archlinux.org/viewtopic.php?id=150743&p=14
Sorry to post in an old thread but it is the closest solution I've found.
I'm having this issue, so it seems.
ATI GPU on a laptop. Laptop sleeps fine but waking up to blank/off screen, at which point I must poweroff/reboot in order to use the computer again.
No WM or DE installed, just Arch Kernel 3.16.4-1-ARCH
fglrx installed
suggestions?
the quoted link above doesn't exist anymore.
Offline
Pages: 1