You are not logged in.
I just convert from Fedora/CentOS/Redhat to arch. Real attraction is its rolling update; tired of fedora's half-year release schedule while centos is quite lag behind the frontier.
Setup is pretty easy in arch, though there are some differences but not too many. I had one major issue in fedora and have it here in arch also: not resuming after pm-suspend/hibernate. This is related to the machine or very likely the host controller that I have: Marvell 88SE6480. There is no error in suspend/hibernate part (pm-suspend.log contains no error); console outputs during resume in fedora and arch are similar. The symptom is that I can't access to my scsi hard disk: even ls will fail. For this reason, there is impossible to record the console error output into file, except the network file which is impossible for me to run.
This problem bothers me from the beginning when I bought this machine at around kernel 3.1.14; my latest trial is 3.5.0.rc3 (the latest kernel just available). I found one person who has the similar machine as mine and reported same symptom as mine in fedora. Not sure if there is any one here having the similar symptom.
thank you in advance for any suggestion.
Offline
After kernel upgrade to 3.4.4-2 can't resume (black screen) my laptop (Samsung R700 AS-02). I tried remove autodetect hook and rebuild initrd, but its didn't help.
Offline
Something to look into: After some kernel upgrades my laptop started showing erratic suspend problems. After a lot of trial an error I found out that the "Lid closed"-event is apparently now also recognised as a "Sleep button"-event. Both events triggered a suspend command when I closed the lid, which led to some weird shit.
Offline
Apparently suspend to RAM does not work anymore on my asus pro5av.
It worked perfectly till two or three days ago.
Now it suspend, but when I try to resume, keyboards (both the notebook and external usb) do not work anymore and the screen remains black.
If I try the Alt+Sys+REISUB procedure it does not work and if I press the power off button , I can hear the shutdown sound and, apparently, the system shuts down cleanly.
Maybe I can try to revert to the late kernel which worked, but I don't know if I can do that by simply reinstalling the old linux package which is in /var/cache/pacman/pkg.
Do I have to reinstall any other package?
This is the list of all packages starting with linux in the cache directory:
ls linux*
linux-3.3.6-1-x86_64.pkg.tar.xz linux-3.3.8-1-x86_64.pkg.tar.xz linux-3.4.3-1-x86_64.pkg.tar.xz linux-api-headers-3.3.8-1-x86_64.pkg.tar.xz
linux-3.3.7-1-x86_64.pkg.tar.xz linux-3.4.2-2-x86_64.pkg.tar.xz linux-api-headers-3.3.2-1-x86_64.pkg.tar.xz linux-firmware-20120227-2-any.pkg.tar.xz
Thank you,
Xwang
I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.
Offline
Apparently suspend to RAM does not work anymore on my asus pro5av.
It worked perfectly till two or three days ago.
Now it suspend, but when I try to resume, keyboards (both the notebook and external usb) do not work anymore and the screen remains black.
If I try the Alt+Sys+REISUB procedure it does not work and if I press the power off button , I can hear the shutdown sound and, apparently, the system shuts down cleanly.
Maybe I can try to revert to the late kernel which worked, but I don't know if I can do that by simply reinstalling the old linux package which is in /var/cache/pacman/pkg.
Do I have to reinstall any other package?
This is the list of all packages starting with linux in the cache directory:ls linux*
linux-3.3.6-1-x86_64.pkg.tar.xz linux-3.3.8-1-x86_64.pkg.tar.xz linux-3.4.3-1-x86_64.pkg.tar.xz linux-api-headers-3.3.8-1-x86_64.pkg.tar.xz
linux-3.3.7-1-x86_64.pkg.tar.xz linux-3.4.2-2-x86_64.pkg.tar.xz linux-api-headers-3.3.2-1-x86_64.pkg.tar.xz linux-firmware-20120227-2-any.pkg.tar.xzThank you,
Xwang
Moreover in the same days I've upgraded also the nvidia driver.
Can the suspend issue be related to it?
Xwang
I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.
Offline
from: https://bbs.archlinux.org/viewtopic.php?id=143545
If you haven't already seen it, check out http://www.nvnews.net/vbulletin/showthread.php?t=179956.
Adding the kernel parameter vga=0 as a workaround does help to wake it up again here. But it still takes longer to wakeup and my cursor flickers while initializing the display. Sometimes I have to switch between a text console and the X server after a wakeup to bring the display back.
I noticed this, as well, when upgrading to 3.4 and the newest nvidia drivers.
Offline
from: https://bbs.archlinux.org/viewtopic.php?id=143545
olebowle wrote:If you haven't already seen it, check out http://www.nvnews.net/vbulletin/showthread.php?t=179956.
Adding the kernel parameter vga=0 as a workaround does help to wake it up again here. But it still takes longer to wakeup and my cursor flickers while initializing the display. Sometimes I have to switch between a text console and the X server after a wakeup to bring the display back.I noticed this, as well, when upgrading to 3.4 and the newest nvidia drivers.
Thank you!
I can confirm it is an nvidia bug.
Reverting to the previous package (nvidia-295.59-1) has solved the issue (suspend works perfectly).
Xwang
I'm still learning English so please excuse me if my English is not good enough and feel free to correct me via PM if you want.
Offline
mbone wrote:from: https://bbs.archlinux.org/viewtopic.php?id=143545
olebowle wrote:If you haven't already seen it, check out http://www.nvnews.net/vbulletin/showthread.php?t=179956.
Adding the kernel parameter vga=0 as a workaround does help to wake it up again here. But it still takes longer to wakeup and my cursor flickers while initializing the display. Sometimes I have to switch between a text console and the X server after a wakeup to bring the display back.I noticed this, as well, when upgrading to 3.4 and the newest nvidia drivers.
Thank you!
I can confirm it is an nvidia bug.
Reverting to the previous package (nvidia-295.59-1) has solved the issue (suspend works perfectly).Xwang
Thanks you!!
Offline
mbone wrote:from: https://bbs.archlinux.org/viewtopic.php?id=143545
olebowle wrote:If you haven't already seen it, check out http://www.nvnews.net/vbulletin/showthread.php?t=179956.
Adding the kernel parameter vga=0 as a workaround does help to wake it up again here. But it still takes longer to wakeup and my cursor flickers while initializing the display. Sometimes I have to switch between a text console and the X server after a wakeup to bring the display back.I noticed this, as well, when upgrading to 3.4 and the newest nvidia drivers.
Thank you!
I can confirm it is an nvidia bug.
Reverting to the previous package (nvidia-295.59-1) has solved the issue (suspend works perfectly).Xwang
This does require also downgrading nvidia-utils.
I hadn't updated for a while so the latest nvidia pkg in cache was 295.53 which requires linux<3.4. 295.59 is available on ARM:
# Downloading and installing the nvidia downgraded pkgs
cd /var/cache/pacman/pkg
wget http://arm.konnichi.com/extra/os/x86_64/nvidia-utils-295.59-1-x86_64.pkg.tar.xz
wget http://arm.konnichi.com/extra/os/x86_64/nvidia-295.59-1-x86_64.pkg.tar.xz
pacman -U nvidia-utils-295.59-1-x86_64.pkg.tar.xz nvidia-295.59-1-x86_64.pkg.tar.xz Offline