LM18 Cannot shutdown, restart, or suspend

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Thu Jun 30, 2016 10:33 am

I got the a new notebook (Asus UX501VW) a few days ago. Yesterday I downloaded the LM18 beta image (Cinnamon version) and installed it (dual boot with Win10) on the new notebook. That was before I read Clem's announcement that beta testing is over and LM18 is ready for release this week.

Anyway, I installed it all the same and except for having to enter nomodeset in boot parameter, I was able to install it without problem. Don't even need to turn off secure boot or legacy mode in BIOS.

But post installation I encountered the following problems:
  • 1. The fan turned on full blast almost immediately after login to Cinnamon. It was loud and never stop.

    2. The function keys that control screen & keyboard backlight brightness was not working.

    3. I cannot shutdown, restart or suspend the system (via GUI and CL). When I shutdown or restart, the screen goes into tty1 (so mostly black except for the login prompt) and freezes. On suspend, the default screensaver appear and again the screen freezes. Regardless, the only thing I can do is to press and hold the power button. While holding down the button the whole system power off. But when I released the power button the system rebooted into grub. There is no way I can completely turn off the system when in LM. The only way I can shutdown the system is to boot into Windows and then shutdown from there. What an irony this is.

    4. When I run inxi, lshw, System Info or hardinfo (a GUI that display hardware info) the screen again freezes and become unresponsive. I cannot even drop into any of the tty to get a command line to see what is happening.

I managed to solve problem 1 & 2 by entering the following boot parameters in grub:

Code: Select all

i915.preliminary_hw_support=1 nouveau.modeset=0 acpi_osi=! acpi_backlight=native idle=nomwait
So 1 & 2 are no longer a problem.


I have no idea where to even begin looking into problem 4. Would appreciate any suggestion from anybody.

As for problem 3, I have tried (a) trying boot parameters reboot=efi, reboot=pci (one at a time) and acpi=force in grub (b) Updating BIOS (c) upgrading to kernel 4.4.13 as suggested by somebody in the LM blog comments. None of them had worked for me.

I tried entering the kernel debug mode and then shutdown/restart/suspend the system. The messages showed a lot of hardware and services being stopped and the final message, before the system froze, shows that it reached target shutdown. (I actually took a shot of the screen with the messages with my camera but am unable to upload it to the forum even though it is only 529KB)

Also, here are some relevant parts from the system log:

When trying to shutdown:
Starting Stop ureadahead data collection...
Jun 30 08:03:48 JSec systemd[1]: Stopped Read required files in advance.
Jun 30 08:03:48 JSec systemd[1]: Started Stop ureadahead data collection.
Jun 30 08:03:52 JSec NetworkManager[790]: <warn> [1467245032.7343] dhcp6 (wlp3s0): request timed out
Jun 30 08:03:52 JSec NetworkManager[790]: <info> [1467245032.7344] dhcp6 (wlp3s0): state changed unknown -> timeout
Jun 30 08:03:52 JSec NetworkManager[790]: <info> [1467245032.7351] dhcp6 (wlp3s0): canceled DHCP transaction, DHCP client pid 1329
Jun 30 08:03:52 JSec NetworkManager[790]: <info> [1467245032.7351] dhcp6 (wlp3s0): state changed timeout -> done
Jun 30 08:05:02 JSec cinnamon-session[1626]: WARNING: t+107.95745s: Playing logout sound '/usr/share/mint-artwork-cinnamon/sounds/logout.ogg'
Jun 30 08:05:02 JSec cinnamon-session[1626]: WARNING: t+108.03466s: Finished playing logout sound
Jun 30 08:05:02 JSec cinnamon-session[1626]: WARNING: t+108.03475s: Resuming logout sequence...
Jun 30 08:05:03 JSec cinnamon-session[1626]: WARNING: t+108.98124s: Requesting system shutdown...
Jun 30 08:05:03 JSec cinnamon-session[1626]: WARNING: t+108.98269s: Attempting to shutdown using systemd...
Jun 30 08:05:03 JSec cinnamon-session[1626]: WARNING: t+108.98422s: Requesting system shutdown...
Jun 30 08:05:03 JSec cinnamon-session[1626]: WARNING: t+108.98497s: Attempting to shutdown using systemd...
Jun 30 16:23:51 JSec rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="764" x-info="http://www.rsyslog.com"] start
Jun 30 16:23:51 JSec rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Jun 30 16:23:51 JSec rsyslogd: rsyslogd's groupid changed to 108
Jun 30 16:23:51 JSec rsyslogd: rsyslogd's userid changed to 104
Jun 30 16:23:51 JSec rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ]
Jun 30 16:23:51 JSec rsyslogd-2007: action 'action 10' suspended, next retry is Thu Jun 30 16:24:21 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
Jun 30 16:23:51 JSec kernel: [ 0.000000] Initializing cgroup subsys cpuset
Jun 30 16:23:51 JSec kernel: [ 0.000000] Initializing cgroup subsys cpu
Jun 30 16:23:51 JSec kernel: [ 0.000000] Initializing cgroup subsys cpuacct
Jun 30 16:23:51 JSec kernel: [ 0.000000] Linux version 4.4.13-040413-generic (kernel@gloin) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1) ) #201606072354 SMP Wed Jun 8 03:56:47 UTC 2016
Jun 30 16:23:51 JSec kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.13-040413-generic root=UUID=4ac5d3f9-37a0-4024-9ffb-67358dd6b080 ro reboot=efi elevator=deadline quiet splash i915.preliminary_hw_support=1 nouveau.modeset=0 acpi_osi=! acpi_backlight=native idle=nomwait vt.handoff=7
Jun 30 16:23:51 JSec kernel: [ 0.000000] KERNEL supported cpus:
Jun 30 16:23:51 JSec kernel: [ 0.000000] Intel GenuineIntel
When trying to restart:
Jun 30 11:45:56 JSec cinnamon-session[1622]: WARNING: t+520.83331s: Playing logout sound '/usr/share/mint-artwork-cinnamon/sounds/logout.ogg'
Jun 30 11:45:56 JSec cinnamon-session[1622]: WARNING: t+520.91244s: Finished playing logout sound
Jun 30 11:45:56 JSec cinnamon-session[1622]: WARNING: t+520.91251s: Resuming logout sequence...
Jun 30 11:45:57 JSec cinnamon-session[1622]: WARNING: t+521.87999s: Requesting system restart...
Jun 30 11:45:57 JSec cinnamon-session[1622]: WARNING: t+521.88056s: Attempting to restart using systemd...
Jun 30 11:45:57 JSec cinnamon-session[1622]: WARNING: t+521.88079s: Requesting system restart...
Jun 30 11:45:57 JSec cinnamon-session[1622]: WARNING: t+521.88122s: Attempting to restart using systemd...

Jun 30 19:46:24 JSec rsyslogd-2222: command 'KLogPermitNonKernelFacility' is currently not permitted - did you already set it via a RainerScript command (v6+ config)? [v8.16.0 try http://www.rsyslog.com/e/2222 ]
Jun 30 19:46:24 JSec rsyslogd: rsyslogd's groupid changed to 108
Jun 30 19:46:24 JSec rsyslogd: rsyslogd's userid changed to 104
Jun 30 19:46:24 JSec systemd-modules-load[354]: Inserted module 'lp'
Jun 30 19:46:24 JSec systemd-modules-load[354]: Inserted module 'ppdev'
Jun 30 19:46:24 JSec systemd-modules-load[354]: Inserted module 'parport_pc'
Jun 30 19:46:24 JSec systemd-modules-load[354]: Failed to find module 'apm power_off=1'
Jun 30 19:46:24 JSec systemd[1]: Starting Apply Kernel Variables...
Jun 30 19:46:24 JSec systemd[1]: Mounting FUSE Control File System...

When trying to suspend:
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4037] manager: sleep requested (sleeping: no enabled: yes)
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4037] manager: sleeping...
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4038] device (wlp3s0): state change: activated -> unmanaged (reason 'sleeping') [100 10 37]
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4198] dhcp4 (wlp3s0): canceled DHCP transaction, DHCP client pid 1308
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4198] dhcp4 (wlp3s0): state changed bound -> done
Jun 30 11:36:20 JSec kernel: [ 239.566381] wlp3s0: deauthenticating from c8:d7:19:99:54:62 by local choice (Reason: 3=DEAUTH_LEAVING)
Jun 30 11:36:20 JSec wpa_supplicant[1070]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=c8:d7:19:99:54:62 reason=3 locally_generated=1
Jun 30 11:36:20 JSec avahi-daemon[805]: Withdrawing address record for 192.168.1.148 on wlp3s0.
Jun 30 11:36:20 JSec avahi-daemon[805]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.1.148.
Jun 30 11:36:20 JSec avahi-daemon[805]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
Jun 30 11:36:20 JSec avahi-daemon[805]: Withdrawing address record for fd02:d319:112e:0:3e53:c95d:535b:4058 on wlp3s0.
Jun 30 11:36:20 JSec avahi-daemon[805]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fd02:d319:112e:0:3e53:c95d:535b:4058.
Jun 30 11:36:20 JSec avahi-daemon[805]: Interface wlp3s0.IPv6 no longer relevant for mDNS.
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4417] dns-mgr: Writing DNS information to /sbin/resolvconf
Jun 30 11:36:20 JSec dnsmasq[1318]: setting upstream servers from DBus
Jun 30 11:36:20 JSec NetworkManager[809]: <info> [1467257780.4524] manager: NetworkManager state is now ASLEEP
Jun 30 11:36:20 JSec wpa_supplicant[1070]: nl80211: deinit ifname=p2p-dev-wlp3s0 disabled_11b_rates=0
Jun 30 11:36:20 JSec dbus[747]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Jun 30 11:36:20 JSec systemd[1]: Reached target Sleep.
Jun 30 11:36:20 JSec systemd[1]: Starting Suspend...
Jun 30 11:36:20 JSec systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 30 11:36:20 JSec dbus[747]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 30 11:36:20 JSec systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 30 11:36:20 JSec nm-dispatcher: req:1 'down' [wlp3s0]: new request (1 scripts)
Jun 30 11:36:20 JSec nm-dispatcher: req:1 'down' [wlp3s0]: start running ordered scripts...
Jun 30 11:36:20 JSec wpa_supplicant[1070]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Jun 30 11:36:30 JSec systemd-sleep[2070]: Selected interface 'p2p-dev-wlp3s0'
Jun 30 11:36:30 JSec systemd-sleep[2070]: 'SUSPEND' command timed out.
Jun 30 11:36:30 JSec systemd-sleep[2074]: /lib/systemd/system-sleep/wpasupplicant failed with error code 254.
Jun 30 11:36:30 JJun 30 19:37:03 JSec rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="767" x-info="http://www.rsyslog.com"] start
One thing I noticed from the logs is the huge time difference between actual system time and the time shown when the system is being booted up. Anybody have any ideas?

I would appreciate any suggestions, inputs, etc. from anybody on these problems (3 & 4) as I really would like to use LM on this notebook.

As I cannot use inxi, lshw, etc. without freezing the system, I am unable to give the output from them. Is there any other way to get the relevant info? Anyway, the following are the info on my system as far as I know: CPU: Quad core Intel Core i7-6700HQ, kernel: 4.4.13, GPU: NVIDIA GTX 960M, RAM: 16GB, 512GB SSD. What other info are needed?

Laurent85
Level 16
Level 16
Posts: 6148
Joined: Tue May 26, 2015 10:11 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Laurent85 » Thu Jun 30, 2016 10:41 am

The nouveau driver is problematic, did you install the nvidia driver 361 from Driver Manager ?
Image

ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Thu Jun 30, 2016 11:30 am

Yes, one of the first thing I did after installation was to install the nvidia driver 361 from Driver Manager.

altair4
Level 19
Level 19
Posts: 9752
Joined: Tue Feb 03, 2009 10:27 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by altair4 » Thu Jun 30, 2016 2:48 pm

There's actually a very popular bug report on this for Ubuntu 16.04. Not sure how well it maps to your current situation: https://bugs.launchpad.net/ubuntu/+sour ... ug/1582011

I have experienced this myself on a test box with 16.04. Long time users of Ubuntu have adopted a Microsoft-like policy of never installing the XX.04 version of an LTS release but wait for the XX.04.1 release. Anyway that's what I'm betting on.
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Thu Jun 30, 2016 7:28 pm

Altair4 and Laurent85, thanks for your responses. I still have LM17.3 ISO on my old notebook (an old Dell XPS L501X which had been running LM without any problem from LM16 to LM17.3). I thought since this is a new notebook I might as well install the latest LM on it.

Anyway I will try to install LM17.3 and see how it goes. This is a bummer really. I really love the new LM18 Cinnamon edition. :( But, whatever it takes to get the system going. Once again, thank you for your responses. :)

ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

[Solved] Re: LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Thu Jun 30, 2016 10:23 pm

Hi guys, good news. :D I managed to solve the problem by falling back on the nouveau open source driver. Now the system can shutdown, reboot, and suspend without any problem. The problem with inxi, lshw, and System Info freezing the system is also resolved. Just for the record of this forum (since I was unable to provide it earlier) here's the inxi -Fxz output

Code: Select all

System:    Host: JSec Kernel: 4.4.13-040413-generic x86_64 (64 bit gcc: 5.3.1)
           Desktop: Cinnamon 3.0.6 (Gtk 3.18.9-1ubuntu3) Distro: Linux Mint 18 Sarah
Machine:   System: ASUSTeK (portable) product: N501VW v: 1.0
           Mobo: ASUSTeK model: N501VW v: 1.0
           Bios: American Megatrends v: N501VW.300 date: 05/09/2016
CPU:       Quad core Intel Core i7-6700HQ (-HT-MCP-) cache: 6144 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 20735
           clock speeds: max: 3500 MHz 1: 811 MHz 2: 799 MHz 3: 840 MHz 4: 808 MHz 5: 800 MHz
           6: 801 MHz 7: 802 MHz 8: 827 MHz
Graphics:  Card-1: Intel Skylake Integrated Graphics bus-ID: 00:02.0
           Card-2: NVIDIA GM107M [GeForce GTX 960M] bus-ID: 01:00.0
           Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.10hz
           GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)
           GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Audio:     Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.4.13-040413-generic
Network:   Card: Intel Wireless 7265 driver: iwlwifi bus-ID: 03:00.0
           IF: wlp3s0 state: up mac: <filter>
Drives:    HDD Total Size: 8.0GB (Used Error!) ID-1: /dev/nvme0n1 model: N/A size: 512.1GB
           ID-2: USB /dev/sda model: Cruzer_Edge size: 8.0GB
Partition: ID-1: / size: 30G used: 6.4G (23%) fs: ext4 dev: /dev/nvme0n1p6
           ID-2: /home size: 319G used: 302M (1%) fs: ext4 dev: /dev/nvme0n1p5
           ID-3: swap-1 size: 17.18GB used: 0.00GB (0%) fs: swap dev: /dev/nvme0n1p4
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 51.0C mobo: N/A
           Fan Speeds (in rpm): cpu: 2100
Info:      Processes: 280 Uptime: 24 min Memory: 1674.7/15911.2MB
           Init: systemd runlevel: 5 Gcc sys: 5.3.1 Client: Shell (bash 4.3.421) inxi: 2.2.35 
But I will continue to monitor this because, as Laurent85 had mentioned, and I have also read about it, the nouveau driver can be problematic. If anybody have any further advice on using nouveau driver (e.g. things to watch out for) it would be greatly appreciated. In the meantime I will mark this thread as [SOLVED].

I have one final question though. I am running Cinnamon. After reverting to nouveau driver, the NVIDIA applet remained in the panel with a red error icon. Hoovering the mouse over it a message bubble appeared saying "Active graphics card: unknown". Clicking on it brings up the "NVIDIA X Server Settings" window. How do I remove this applet from the panel? I checked under Applets and the only NVIDIA related applet installed is "NVIDIA Prime". But that is not added to the panel. It is simply installed but not added. When I right clicked on it, the option to uninstall is greyed out. My guess is that the uninstallation of NVIDIA drivers have not been done cleanly. I simply used the Driver Manager and select the nouveau driver and click apply changes. Can anybody advice on how to clean up the remaining files. At the very least I would like to get rid of the applet on the panel because it really is an eyesore on an otherwise beautiful desktop.

Once again, thank you guys for your responses. I am very happy that I can continue to use the latest version of LM, my favourite OS, on this new machine. Thank you very much. :)

Cosmo.
Level 23
Level 23
Posts: 17830
Joined: Sat Dec 06, 2014 7:34 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Cosmo. » Fri Jul 01, 2016 6:10 am

Regarding the prime icon: What you see is not an applet, but a tray icon. You can disable in the startup-options: Support for Nvidia Prime.

ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Fri Jul 01, 2016 7:07 am

Thanks Cosmo. I just disabled it.

Laurent85
Level 16
Level 16
Posts: 6148
Joined: Tue May 26, 2015 10:11 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Laurent85 » Fri Jul 01, 2016 8:05 am

ttjimera wrote:My guess is that the uninstallation of NVIDIA drivers have not been done cleanly.
Looks like.

The prime applet only appears when nvidia prime is installed which is the normal behavior, this applet should not be disabled. Disabling the applet only hides current broken settings :idea:

Fix incorrectly purged nvidia packages, from a terminal you can purge the Nvidia packages this way:

Code: Select all

apt purge nvidia-*
And reinstall Mint prime applet package which is present by default:

Code: Select all

apt install nvidia-prime-applet
Graphics: Card-1: Intel Skylake Integrated Graphics bus-ID: 00:02.0
Card-2: NVIDIA GM107M [GeForce GTX 960M] bus-ID: 01:00.0
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1920x1080@60.10hz
GLX Renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2)
GLX Version: 3.0 Mesa 11.2.0 Direct Rendering: Yes
Actually the Nvidia card is not running, see Intel card in use.

i915.preliminary_hw_support=1 boot option is only relevant for pre 4.3 kernels.

Unless a fix released soon you may try as a workaround either:

- use Intel graphics, no Nvidia driver installed, disable discrete card Nvidia, boot options
modprobe.blacklist=nouveau acpi_osi=Linux acpi_backlight=vendor idle=nomwait

- use discrete card Nvidia with open source driver Nouveau, no Nvidia driver installed, Nouveau hardware acceleration disabled, boot options
nouveau.noaccel=1 acpi_osi=Linux acpi_backlight=vendor idle=nomwait

- use Nvidia driver, install driver from Driver Manager, use boot options
acpi_osi=Linux acpi_backlight=vendor idle=nomwait

See which setup works better for your needs. Asus Bios/firmware may need an update to fix current issues.
Image

Cosmo.
Level 23
Level 23
Posts: 17830
Joined: Sat Dec 06, 2014 7:34 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Cosmo. » Fri Jul 01, 2016 10:27 am

Laurent85 wrote:
ttjimera wrote:My guess is that the uninstallation of NVIDIA drivers have not been done cleanly.
Looks like.
I don't think so. The prime-applet (in difference to nvidia-prime) gets even installed in a virtual machine.

Laurent85
Level 16
Level 16
Posts: 6148
Joined: Tue May 26, 2015 10:11 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Laurent85 » Fri Jul 01, 2016 10:54 am

Cosmo. wrote: I don't think so. The prime-applet (in difference to nvidia-prime) gets even installed in a virtual machine.
See my post that's why I suggested to purge nvidia package and reinstall nvidia-prime-applet.
Image

ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Fri Jul 01, 2016 10:41 pm

Laurent85, thank you for your response. I have cleaned up the nvidia packages as per your instruction and reinstalled prime applet. That looks fine now. I no longer get the tray icon on the panel.

I have updated BIOS just two days ago. This is the latest version released by Asus just last month.

I have noticed that I am not using the Nvidia card. But at present this is fine with me. I did not want that card anyway. For my work right now I do not realy need it. It just came with the system. So using the Intel driver is fine with me.

But I now notice that there could be a problem coming out of suspension. I suspended the system several time yesterday for short period of time (an hour at most) but did encounter any problem. But this morning, after a whole night in suspend mode, shortly after waking up the system from suspension, the screen started flickering like crazy and the system become unresponsive. I could not do ctrl-alt-esc to restart Cinnamon. But I could drop into a tty. From there I restarted mdm. This is a bit drastic, but it's the only thing I know to do. Anyway here's the relevant part from syslog when the screen started flickering and when I restarted mdm.

Code: Select all

Jul  2 06:50:47 JSec console-kit-daemon[1608]: (process:11009): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == failed' 0
Jul  2 06:50:51 JSec console-kit-daemon[1608]: (process:11011): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul  2 06:50:55 JSec console-kit-daemon[1608]: (process:11037): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed 
Jul  2 06:51:00 JSec systemd[1]: Started Getty on tty6.
Jul  2 06:51:02 JSec console-kit-daemon[1608]: (process:11045): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul  2 06:51:08 JSec console-kit-daemon[1608]: (process:11090): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul  2 06:51:22 JSec console-kit-daemon[1608]: (process:11095): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul  2 06:51:37 JSec console-kit-daemon[1608]: (process:11203): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed
Jul  2 06:51:52 JSec systemd[1]: Stopping MDM Display Manager...
Jul  2 06:51:52 JSec systemd[11211]: mdm.service: Failed at step EXEC spawning /usr/sbin/mdm-stop: No such file or directory
Jul  2 06:51:52 JSec systemd[1]: mdm.service: Control process exited, code=exited status=203
Jul  2 06:51:52 JSec org.a11y.atspi.Registry[2290]: XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
Jul  2 06:51:52 JSec org.a11y.atspi.Registry[2290]:       after 10587 requests (10587 known processed) with 0 events remaining.
Jul  2 06:51:52 JSec bluetoothd[1036]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSource
Jul  2 06:51:52 JSec bluetoothd[1036]: Endpoint unregistered: sender=:1.37 path=/MediaEndpoint/A2DPSink
Jul  2 06:51:52 JSec org.gnome.Terminal[2272]: (gnome-terminal-server:3088): Gdk-WARNING **: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Jul  2 06:51:52 JSec org.gtk.vfs.Daemon[2272]: A connection to the bus can't be made
Jul  2 06:51:52 JSec org.gtk.vfs.Daemon[2272]: message repeated 5 times: [ A connection to the bus can't be made]
Jul  2 06:51:52 JSec systemd[1]: Stopped MDM Display Manager.
Jul  2 06:51:52 JSec systemd[1]: mdm.service: Unit entered failed state.
Jul  2 06:51:52 JSec systemd[1]: mdm.service: Failed with result 'exit-code'.
Jul  2 06:51:52 JSec systemd[1]: Starting Detect the available GPUs and deal with any system changes...
Jul  2 06:51:52 JSec gpu-manager[11228]: /etc/modprobe.d is not a file
Jul  2 06:51:52 JSec gpu-manager[11228]: message repeated 4 times: [ /etc/modprobe.d is not a file]
Jul  2 06:51:52 JSec gpu-manager[11228]: Error: can't open /lib/modules/4.4.13-040413-generic/updates/dkms
Jul  2 06:51:52 JSec gpu-manager[11228]: Error: can't open /lib/modules/4.4.13-040413-generic/updates/dkms
Jul  2 06:51:52 JSec acpid: client 2108[0:0] has disconnected
Jul  2 06:51:52 JSec gpu-manager[11228]: update-alternatives: error: no alternatives for x86_64-linux-gnu_gfxcore_conf
Jul  2 06:51:52 JSec systemd[1]: Started Detect the available GPUs and deal with any system changes.
Jul  2 06:51:52 JSec systemd[1]: Started MDM Display Manager.
Jul  2 06:51:52 JSec mdm[11252]: Starting mdm...
Thanks for listing out all boot parameters needed for the different scenarios. I appreciate it. It's always good to have options. As Nvidia driver gave me problem with shutdown/reboot/suspend, I did not try the third option. I tried the second suggestion but it brought back the problem with the loud fan and the shutdown/reboot/suspend. So now we know nouveau driver may be problematic too. I tried the first option. No loud fan or shutdown/reboot/suspend problem. But the function keys that control the screen brightness did not work. So finally I set acpi_osi=! acpi_backlight=native (what I used originally) and it work again.

Some questions: What is the difference between nouveau.modeset=0 (which I used originally) and modprobe.blacklist=nouveau in your option one (which I am using now)? Also I feel that I need to learn more about the boot options available and what they really mean. Right now I am just reading all these solutions on the internet and trying them out. But in the long run I think I should start learning this if I am going to continue using Linux as my primary OS. I found some links on boot parameters via Google but they are very technical and seem to assume some foundation knowledge of the kernel, something that I don't have. Can anyone please point me in the right direction. I don't need to know in detail, but just enough to understand what is going on. Thanks everybody.

Laurent85
Level 16
Level 16
Posts: 6148
Joined: Tue May 26, 2015 10:11 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Laurent85 » Sun Jul 03, 2016 1:44 pm

ttjimera wrote: Some questions: What is the difference between nouveau.modeset=0 (which I used originally) and modprobe.blacklist=nouveau in your option one (which I am using now)?
nouveau.modeset=0 is equivalent to the nomodeset option only applied to Nouveau module, discrete card still used. Assuming no Nvidia driver installed modprobe.blacklist=nouveau prevents the kernel from loading the Nouveau module, discrete card is then disabled, Intel graphics is used.
Also I feel that I need to learn more about the boot options available and what they really mean. Right now I am just reading all these solutions on the internet and trying them out. But in the long run I think I should start learning this if I am going to continue using Linux as my primary OS. I found some links on boot parameters via Google but they are very technical and seem to assume some foundation knowledge of the kernel, something that I don't have. Can anyone please point me in the right direction. I don't need to know in detail, but just enough to understand what is going on. Thanks everybody.
I personally understand few boot options, documentation available is very basic, mostly from the kernel source tree.
Image

ttjimera
Level 1
Level 1
Posts: 31
Joined: Fri Jun 27, 2014 8:47 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by ttjimera » Mon Jul 04, 2016 5:19 am

Thanks for the clarification

ivan3x
Level 1
Level 1
Posts: 1
Joined: Sun Oct 23, 2016 7:36 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by ivan3x » Sun Oct 23, 2016 7:52 am

Hello

I have nvidia property (367.44) driver. When I use Nvidia (driver) shutdown/restart is good, but when I switched to Intel (2.0.2) driver the shutdown/restart doesnt work.
I dont know but the problem might be Intel driver??

My bios is updated.

Thanks in advance

Sorry, my English isnt good

Pampmousse
Level 1
Level 1
Posts: 3
Joined: Sun Oct 23, 2016 12:01 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by Pampmousse » Sun Oct 23, 2016 12:39 pm

Hello.

I have exactly the same problem as ivan3x. (LM18 - Clevo W650)
After completing the installation of the Nvidia driver and restarting the laptop, the system works quite well with the discrete card (GTX 950M) but the battery is draining fast and the fan turns on full blast quickly.
Intel video card works too, nonetheless there are fews problems :
-Logout, Shutdown and Sleep Mode freeze the laptop
-Commands like "lspci", "lshw", "inxi", which are displaying PCI informations, freeze the laptop aswell
Switching from Intel to Nvidia prevents the system to perform anything out of the session as it results to a permanent frozen tty login screen when logging out.
I suspect the Intel driver to be the origin of this problem.

I am currently running with nouveau driver and have not installed Nvidia driver. (fresh install)
It works well but like before, commands which are displaying PCI informations do not work. (although Logout, Shutdown and Sleep Mode are working)
I cannot display what video card and driver I am currently using.

Cheers.

Pampmousse
Level 1
Level 1
Posts: 3
Joined: Sun Oct 23, 2016 12:01 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by Pampmousse » Mon Oct 24, 2016 4:23 am

I found that the nouveau driver was causing these troubles...

I have simply blacklisted the nouveau driver in grub options with these parameters Laurent85 gave :

Code: Select all

modprobe.blacklist=nouveau acpi_osi=Linux acpi_backlight=vendor idle=nomwait
Intel driver actually works fine. I have no use of the discrete card for now. Thanks Laurent85.

Cheers.

Possum
Level 1
Level 1
Posts: 1
Joined: Wed Nov 09, 2016 11:06 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Possum » Wed Nov 09, 2016 11:39 am

Hello!

First of all: Linux Mint 18 is beautiful! I´m coming from 6 months of Mint 17.3

I´m having the same issues: fan running full throttle, system not shutting down.

I´ve added the line "modprobe.....nowait" to the GRUB after hitting "e" then booted hitting F10. Later I opened the GRUB file (located at /etc/default/GRUB) as root and added that line there too.

Problems persist. I checked the GRUB hitting "e" again and the line containing the blacklist is gone.

I´m rather new to the Linux world and probably missing some basic thing somewhere...

Thank a lot!

Possum

Laurent85
Level 16
Level 16
Posts: 6148
Joined: Tue May 26, 2015 10:11 am

Re: LM18 Cannot shutdown, restart, or suspend

Post by Laurent85 » Wed Nov 09, 2016 12:03 pm

Possum wrote: I´ve added the line "modprobe.....nowait" to the GRUB after hitting "e" then booted hitting F10. Later I opened the GRUB file (located at /etc/default/GRUB) as root and added that line there too.

Problems persist. I checked the GRUB hitting "e" again and the line containing the blacklist is gone.
You also need to ask grub to take the change into account, from a terminal :

Code: Select all

sudo update-grub
Image

Pampmousse
Level 1
Level 1
Posts: 3
Joined: Sun Oct 23, 2016 12:01 pm

Re: LM18 Cannot shutdown, restart, or suspend

Post by Pampmousse » Wed Nov 09, 2016 4:17 pm

Hello again.

I figured out what was wrong with my shutdown/no lspci problem, in the case where you have installed Nvidia driver and switching from it to Intel.
Here's what I have done :
-Remove all packages related to nvidia, bumblebee, and primus.
-Open the driver manager and add ppa:graphics-drivers/ppa.
-Before selecting your driver, you must verify the latest driver available for your Nvidia card :
http://www.nvidia.com/Download/index.aspx?lang=en-us
-Then install the correct driver, and restart.

WARNING: It worked at first, but the last update for ubuntu-drivers-common, which is the Driver Manager, has ruined the whole thing. I managed to make it work again by removing ubuntu-drivers-common package. But obviously you won't be able to launch the Driver Manager anymore after this removal.

Hope it helps.

Cheers.

Post Reply

Return to “Installation & Boot”