Mageia forum

Folks,

I've a new laptop (Toshiba Satellite L70) that won't come out of sleep mode. When you open the lid it doesn't wake up, you have to push the power button (but this might have nothing to do with it).

It has an Optimus card and I'd installed Bublebee with Nouveau (Nouveau works really well on my Macbook now). With that when you powered up the fan came hard on and you had to press the power button again to get the login screen, but that didn't help as you couldn't move the mouse and the keyboard didn't work.

I unistalled Bumblebee, but although the fan doesn't come hard on any more, you still can't type anything or move the mouse.

I found this:

viewtopic.php?f=7&t=7596&p=48288&hilit=sleep#p48288

Ran journalctl -afxb | tee somefile and ended up with a sizeable file. The important part of which is, I assume,

Code: Select all

-- The system has now left the suspend sleep state.
Mar 23 00:40:03 localhost systemd-logind[862]: Operation finished.
Mar 23 00:40:04 localhost kernel: bbswitch: disabling discrete graphics
Mar 23 00:40:04 localhost kernel: ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)
Mar 23 00:40:03 localhost ifplugd(wlp2s0)[1230]: Link beat lost.
Mar 23 00:40:06 localhost kernel: wlp2s0: authenticate with 30:91:8f:00:72:f3
Mar 23 00:40:06 localhost kernel: wlp2s0: send auth to 30:91:8f:00:72:f3 (try 1/3)
Mar 23 00:40:06 localhost kernel: wlp2s0: authenticated
Mar 23 00:40:06 localhost kernel: wlp2s0: associate with 30:91:8f:00:72:f3 (try 1/3)
Mar 23 00:40:06 localhost kernel: wlp2s0: RX AssocResp from 30:91:8f:00:72:f3 (capab=0x411 status=0 aid=4)
Mar 23 00:40:06 localhost kernel: wlp2s0: associated
Mar 23 00:40:06 localhost systemd-networkd[952]: wlp2s0          : gained carrier
Mar 23 00:40:06 localhost systemd-timesyncd[724]: Network configuration changed, trying to establish connection.
Mar 23 00:40:06 localhost systemd-timesyncd[724]: Using NTP server 216.239.32.15:123 (time1.google.com).
Mar 23 00:40:06 localhost systemd[2367]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Mar 23 00:40:06 localhost systemd-timesyncd[724]: interval/delta/delay/jitter/drift 32s/+0.514s/0.076s/0.194s/-4ppm
Mar 23 00:40:07 localhost ifplugd(wlp2s0)[1230]: Link beat detected.
Mar 23 00:40:14 localhost systemd-logind[862]: Power key pressed.
Mar 23 00:40:25 localhost systemd-logind[862]: Power key pressed.
Mar 23 00:40:25 localhost systemd-logind[862]: Power key pressed.
Mar 23 00:40:25 localhost systemd-logind[862]: Power key pressed.
Mar 23 00:40:26 localhost systemd-logind[862]: Power key pressed.
Mar 23 00:40:26 localhost systemd-logind[862]: Power key pressed.
Mar 23 00:40:26 localhost systemd-logind[862]: Power key pressed.


This line:

Code: Select all

ACPI Warning: \_SB_.PCI0.RP05.PXSX._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20150410/nsarguments-95)



Brings up a few hits, but nothing for Mageia as far as I can find.

This shows a similar ish issue and he suggests changing Grub:

http://forums.debian.net/viewtopic.php?f=7&t=124373

My Grub file doesn't have

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet nomodeset"

It has:

GRUB_CMDLINE_LINUX_DEFAULT=" splash quiet noiswmd resume=UUID=297d805e-9f48-489e-98b4-12ecec9febe2"

I tried that and it makes no difference.

However, what I have just found is that if I plug in a USB keyboard and mouse then it works (and I am, indeed, posting this with an external keyboard after coming out of sleep.

I can find similar Ubuntu issues:

http://askubuntu.com/questions/483416/k ... er-suspend

But the answer people have shown to work, we don't seem to have that package. Or if we do it's a different name and I can't find it.

I'm out of ideas now. Can anyone think of what I cold try please?

Thanks!

DiBosco wrote:I can find similar Ubuntu issues:

http://askubuntu.com/questions/483416/k ... er-suspend

But the answer people have shown to work, we don't seem to have that package. Or if we do it's a different name and I can't find it.

Which package from that thread did you refer to in particular? He installed the proprietary nvidia driver in the end, you can do that on Mageia too via drakx11.

doktor5000 wrote:

DiBosco wrote:I can find similar Ubuntu issues:

http://askubuntu.com/questions/483416/k ... er-suspend

But the answer people have shown to work, we don't seem to have that package. Or if we do it's a different name and I can't find it.

Which package from that thread did you refer to in particular? He installed the proprietary nvidia driver in the end, you can do that on Mageia too via drakx11.

I was referring to the one he ticked as the answer:

Code: Select all

sudo apt-get install xserver-xorg-input-all

I may be completely wrong, but this seems to be keyboard and mouse rather than graphics card related?

When you say try the proprietary one are you saying try Bumblebee nvidia proprietary? Oddly I have found the nouveau to be much better than nvidia for coming out of sleep (and finally the nouveau works beautifully for rending graphics as well!).

This is the fist time I've had an Optimus card. From what I understand, it generally uses the Intel low power card and then in Windows switches automatically to nvidia for gaming or graphics intensive programs, whereas we have to actually launch the program and instruct it to use the nividia card. (I realise we're going off ast a bit of a angent now.)

Another thing that may be connected is that sometimes on boot there is no cursor. The keyboard does work and CTL ATL BACKSPACE brings up the cursor!

What input device do you use? Can you post the output of

Code: Select all

xinput list

xinput may need to be installed for that ...

I can!

Code: Select all

xinput list
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ ETPS/2 Elantech Touchpad                  id=11   [slave  pointer  (2)]
⎣ Virtual core keyboard                         id=3    [master keyboard (2)]
    ↳ Virtual core XTEST keyboard               id=5    [slave  keyboard (3)]
    ↳ Power Button                              id=6    [slave  keyboard (3)]
    ↳ Video Bus                                 id=7    [slave  keyboard (3)]
    ↳ Video Bus                                 id=8    [slave  keyboard (3)]
    ↳ TOSHIBA Web Camera - HD                   id=9    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=10   [slave  keyboard (3)]

You don't seem to use any external mouse, only the touchpad, right? Might be a bug with that one, there were issues with the quirks for the Elantech ones ...

I think I have solved it.

This:

https://forums.linuxmint.com/viewtopic.php?t=152185

Had a suggestion for changing grub, which I followed and it now seems to come back to life when.

I need to find why opening the lid doesn't switch it on next. I was sure KDE settings used to have that sort of thing, but I can only see options for closing the lid. Thanks for suggestions, it all helps "talking" this stuff over by making things occur to me.

I'll mark as solved as long as it continues behaving in the next day or two.