[opensuse-factory] Can not properly recover from suspend to ram (42.2)
Hi, When system comes back from suspend to ram, I get a black screen with a mouse. Does not respond. I have to ctrl-alt-f1 to get a terminal, and back to F7. Once it worked, another time it did not. I had to kill xscreensaver to get a display. But touchpad mouse had disappeared from sight. Again to console and back, mouse was restored. On hibernate to disk there are no issues. Machine is Intel cpu and graphics, not recent make. "Pentium(R) Dual-Core CPU T4300 @ 2.10GHz" Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x103c "Hewlett-Packard Company" Driver: "i915" Driver Modules: "drm" -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
When system comes back from suspend to ram, I get a black screen with a mouse. Does not respond. I have to ctrl-alt-f1 to get a terminal, and back to F7. Once it worked, another time it did not. I had to kill xscreensaver to get a display. But touchpad mouse had disappeared from sight. Again to console and back, mouse was restored.
On hibernate to disk there are no issues.
Machine is Intel cpu and graphics, not recent make.
"Pentium(R) Dual-Core CPU T4300 @ 2.10GHz"
Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x103c "Hewlett-Packard Company"
Driver: "i915" Driver Modules: "drm"
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-18 02:31, Felix Miata wrote:
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel.
Makes no difference regarding this problem. To recover I still have to kill xscreensaver, so it is a problem with it, not directly with the video driver. I had problems on another setup with xscreensaver, too. I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted. -- Cheers/Saludos Carlos E. R. (testing openSUSE Leap 42.2, at Minas-Anor) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Carlos E. R. composed on 2016-11-17 20:57 (UTC-0500):
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I think I remember seeing a discussion about network kill in [opensuse] not very long ago, weeks rather than months. Remember these? https://lists.opensuse.org/opensuse/2016-02/msg00336.html https://lists.opensuse.org/opensuse/2016-10/msg00576.html -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Carlos E. R.
On 2016-11-18 02:31, Felix Miata wrote:
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel.
Makes no difference regarding this problem. To recover I still have to kill xscreensaver, so it is a problem with it, not directly with the video driver. I had problems on another setup with xscreensaver, too.
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I see that problem, and have complained, on two laptops. I work-a-round it with: "init 3;systemctl restart wicked" or more usually: "systemctl isolate multi-user;systemctl restart wicked" and the same when changing to runlevel 5, "systemctl isolate graphical;systemctl restart wicked" On my main workstation I must include "restart SuSEfirewall2". Luckily when needing to perform a remote restart, the network is available, but have had that problem too. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.11.2016 06:49, Patrick Shanahan пишет:
* Carlos E. R.
[11-17-16 20:59]: On 2016-11-18 02:31, Felix Miata wrote:
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel.
Makes no difference regarding this problem. To recover I still have to kill xscreensaver, so it is a problem with it, not directly with the video driver. I had problems on another setup with xscreensaver, too.
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I see that problem, and have complained, on two laptops. I work-a-round it with: "init 3;systemctl restart wicked" or more usually: "systemctl isolate multi-user;systemctl restart wicked" and the same when changing to runlevel 5, "systemctl isolate graphical;systemctl restart wicked"
Is it 42.2 regression? I cannot reproduce it on 42.1.
On my main workstation I must include "restart SuSEfirewall2".
Luckily when needing to perform a remote restart, the network is available, but have had that problem too.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andrei Borzenkov
18.11.2016 06:49, Patrick Shanahan пишет:
* Carlos E. R.
[11-17-16 20:59]: On 2016-11-18 02:31, Felix Miata wrote:
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel.
Makes no difference regarding this problem. To recover I still have to kill xscreensaver, so it is a problem with it, not directly with the video driver. I had problems on another setup with xscreensaver, too.
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I see that problem, and have complained, on two laptops. I work-a-round it with: "init 3;systemctl restart wicked" or more usually: "systemctl isolate multi-user;systemctl restart wicked" and the same when changing to runlevel 5, "systemctl isolate graphical;systemctl restart wicked"
Is it 42.2 regression? I cannot reproduce it on 42.1.
On my main workstation I must include "restart SuSEfirewall2".
Luckily when needing to perform a remote restart, the network is available, but have had that problem too.
uuups, tumbleweed.... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.11.2016 07:19, Patrick Shanahan пишет:
* Andrei Borzenkov
[11-17-16 23:18]: 18.11.2016 06:49, Patrick Shanahan пишет:
* Carlos E. R.
[11-17-16 20:59]: On 2016-11-18 02:31, Felix Miata wrote:
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel.
Makes no difference regarding this problem. To recover I still have to kill xscreensaver, so it is a problem with it, not directly with the video driver. I had problems on another setup with xscreensaver, too.
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I see that problem, and have complained, on two laptops. I work-a-round it with: "init 3;systemctl restart wicked" or more usually: "systemctl isolate multi-user;systemctl restart wicked" and the same when changing to runlevel 5, "systemctl isolate graphical;systemctl restart wicked"
Is it 42.2 regression? I cannot reproduce it on 42.1.
On my main workstation I must include "restart SuSEfirewall2".
Luckily when needing to perform a remote restart, the network is available, but have had that problem too.
uuups, tumbleweed....
I cannot reproduce this either in TW. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Andrei Borzenkov
18.11.2016 07:19, Patrick Shanahan пишет:
* Andrei Borzenkov
[11-17-16 23:18]: 18.11.2016 06:49, Patrick Shanahan пишет:
* Carlos E. R.
[11-17-16 20:59]: On 2016-11-18 02:31, Felix Miata wrote:
Carlos E. R. composed on 2016-11-18 01:48 (UTC+0100):
Not sure which chipset that has, might be too old for this to be supported, but try uninstalling xf86-video-intel.
Makes no difference regarding this problem. To recover I still have to kill xscreensaver, so it is a problem with it, not directly with the video driver. I had problems on another setup with xscreensaver, too.
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I see that problem, and have complained, on two laptops. I work-a-round it with: "init 3;systemctl restart wicked" or more usually: "systemctl isolate multi-user;systemctl restart wicked" and the same when changing to runlevel 5, "systemctl isolate graphical;systemctl restart wicked"
Is it 42.2 regression? I cannot reproduce it on 42.1.
On my main workstation I must include "restart SuSEfirewall2".
Luckily when needing to perform a remote restart, the network is available, but have had that problem too.
uuups, tumbleweed....
I cannot reproduce this either in TW.
Yes, I cannot pinpoint it either. I only see it on a recently new install of tw and my main workstation which has continually be updated since Greg KH maintained pre-tw. And sometimes I get network but firewall blocks connection so I have made the habit of restarting both *anytime* I change display mode. I suspect the age of the workstation might be a problem as I cannot remember whether it began life as 12.1 or .... -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 Photos: http://wahoo.no-ip.org/piwigo @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-18 04:49, Patrick Shanahan wrote:
* Carlos E. R. <> [11-17-16 20:59]:
I noticed that "init 3; init 5" kills the network (NM). I did not know how to recover it, so I rebooted.
I see that problem, and have complained, on two laptops. I work-a-round it with: "init 3;systemctl restart wicked" or more usually: "systemctl isolate multi-user;systemctl restart wicked" and the same when changing to runlevel 5, "systemctl isolate graphical;systemctl restart wicked"
The laptop uses NM. I saw a message about disappearing interface or something. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 18-11-16 01:48, Carlos E. R. wrote:
Hi,
When system comes back from suspend to ram, I get a black screen with a mouse. Does not respond. I have to ctrl-alt-f1 to get a terminal, and back to F7. Once it worked, another time it did not. I had to kill xscreensaver to get a display. But touchpad mouse had disappeared from sight. Again to console and back, mouse was restored.
On hibernate to disk there are no issues.
Machine is Intel cpu and graphics, not recent make.
"Pentium(R) Dual-Core CPU T4300 @ 2.10GHz"
Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x103c "Hewlett-Packard Company"
Driver: "i915" Driver Modules: "drm"
I've had some suspend to RAM and other instability problems with i915 as well. Adding |i915.semaphores|to the kernel's boot parameters solved a lot: /i915.semaphores=1/ Also (for screen tearing issues): |/etc/X11/xorg.conf.d/20-intel.conf|: /Section "Device"// // Identifier "Intel Graphics"// // Driver "intel"// // Option "TearFree" "true"// // Option "AccelMethod" "uxa"// //EndSection/ If your system has two graphics chips (nVidia Optimus hardware) then also blacklist nouveau, in file /etc/modprobe.d/50-blacklist.conf add: ///blacklist nouveau/ And do a /mkinitrd/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2016-11-18 08:18, opensuse@maridonkers.info wrote:
On 18-11-16 01:48, Carlos E. R. wrote:
Hi,
When system comes back from suspend to ram, I get a black screen with a mouse. Does not respond. I have to ctrl-alt-f1 to get a terminal, and back to F7. Once it worked, another time it did not. I had to kill xscreensaver to get a display. But touchpad mouse had disappeared from sight. Again to console and back, mouse was restored.
On hibernate to disk there are no issues.
Machine is Intel cpu and graphics, not recent make.
"Pentium(R) Dual-Core CPU T4300 @ 2.10GHz"
Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x103c "Hewlett-Packard Company"
Driver: "i915" Driver Modules: "drm"
I've had some suspend to RAM and other instability problems with i915 as well. Adding |i915.semaphores|to the kernel's boot parameters solved a lot:
My problem seems to be related solely to xscreensaver not responding to keyboard or mouse. But I can try your suggestions.
/i915.semaphores=1/
Also (for screen tearing issues):
|/etc/X11/xorg.conf.d/20-intel.conf|:
/Section "Device"// // Identifier "Intel Graphics"// // Driver "intel"// // Option "TearFree" "true"// // Option "AccelMethod" "uxa"// //EndSection/
If your system has two graphics chips (nVidia Optimus hardware) then also blacklist nouveau, in file /etc/modprobe.d/50-blacklist.conf add:
No, only intel graphics. Intentionally so. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 18-11-16 01:48, Carlos E. R. wrote:
Hi,
When system comes back from suspend to ram, I get a black screen with a mouse. Does not respond. I have to ctrl-alt-f1 to get a terminal, and back to F7. Once it worked, another time it did not. I had to kill xscreensaver to get a display. But touchpad mouse had disappeared from sight. Again to console and back, mouse was restored.
On hibernate to disk there are no issues.
Machine is Intel cpu and graphics, not recent make.
"Pentium(R) Dual-Core CPU T4300 @ 2.10GHz"
Model: "Intel Mobile 4 Series Chipset Integrated Graphics Controller" Device: pci 0x2a43 "Mobile 4 Series Chipset Integrated Graphics Controller" SubVendor: pci 0x103c "Hewlett-Packard Company"
Driver: "i915" Driver Modules: "drm"
I've had some suspend to RAM and other instability problems with i915 as well. Adding i915.semaphores to the kernel's boot parameters solved a lot: i915.semaphores=1 Also (for screen tearing issues): /etc/X11/xorg.conf.d/20-intel.conf: Section "Device" Identifier "Intel Graphics" Driver "intel" Option "TearFree" "true" Option "AccelMethod" "uxa" EndSection If your system has two graphics chips (nVidia Optimus hardware) then also blacklist nouveau, in file /etc/modprobe.d/50-blacklist.conf add: blacklist nouveau And do a mkinitrd -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (5)
-
Andrei Borzenkov
-
Carlos E. R.
-
Felix Miata
-
opensuse@maridonkers.info
-
Patrick Shanahan