You are not logged in.

Pages: 1 2

#1 2017-12-02 14:55:14

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Suspend function on Nvidia Prop. driver problem

So i found that articlae https://wiki.archlinux.org/index.php/NV … om_suspend and i got it working 1 time but after reboot the suspend function is making lag again. Can anyone explain how to do it properly ?

Last edited by Qik000 (2017-12-02 16:58:21)

Offline

#2 2017-12-02 15:04:56

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

How are you loading nvidia module? Via /etc/modprobe.d/ or /etc/default/grub?

Offline

#3 2017-12-02 15:46:57

fsckd
Forum Fellow
Registered: 2009-06-15
Posts: 4,173

Re: Suspend function on Nvidia Prop. driver problem

Please remove the plea for help in the thread subject and replace the subject with something more descriptive of the problem you are facing. Thank you.

https://wiki.archlinux.org/index.php/Co … ow_to_post

aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

Offline

#4 2017-12-02 16:07:38

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:

How are you loading nvidia module? Via /etc/modprobe.d/ or /etc/default/grub?

/etc/modprobe.d/file.conf

and in that file i have:

options nvidia NVreg_RegisterForACPIEvents=1 NVreg_EnableMSI=1

The fix worked 1 time, bur after reboot the sleep started braking performance again

Last edited by Qik000 (2017-12-02 16:14:44)

Offline

#5 2017-12-02 16:16:42

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

Read wiki again, specifically this, section Using files in /etc/modprobe.d. Syntax of your file.conf is wrong, and that's your problem. Correct syntax is:

options module_name parameter_name=parameter_value

For example:

options nvidia NVreg_RegisterForACPIEvents=1

I'll let you figure out second line on your own wink

And this:

fsckd wrote:

Please remove the plea for help in the thread subject and replace the subject with something more descriptive of the problem you are facing. Thank you.

https://wiki.archlinux.org/index.php/Co … ow_to_post

Last edited by boojum (2017-12-02 16:19:23)

Offline

#6 2017-12-02 16:59:26

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:

Read wiki again, specifically this, section Using files in /etc/modprobe.d. Syntax of your file.conf is wrong, and that's your problem. Correct syntax is:

options module_name parameter_name=parameter_value

For example:

options nvidia NVreg_RegisterForACPIEvents=1

I'll let you figure out second line on your own wink

And this:

fsckd wrote:

Please remove the plea for help in the thread subject and replace the subject with something more descriptive of the problem you are facing. Thank you.

https://wiki.archlinux.org/index.php/Co … ow_to_post

the second line should be

options nvidia NVreg_EnableMSI=1 ?

Offline

#7 2017-12-02 17:01:12

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

Qik000 wrote:

the second line should be

options nvidia NVreg_EnableMSI=1 ?

That is indeed correct.

Offline

#8 2017-12-02 17:07:05

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:
Qik000 wrote:

the second line should be

options nvidia NVreg_EnableMSI=1 ?

That is indeed correct.

It doesnt work.
i applied changes to the file and suspend still strikes performance

Offline

#9 2017-12-02 17:13:22

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

Have you rebooted or suspended straight away? If you are not reloading nvidia module manually you need to reboot before changes will take effect.

Offline

#10 2017-12-02 17:15:07

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:

Have you rebooted or suspended straight away? If you are not reloading nvidia module manually you need to reboot before changes will take effect.

I rebooted. And suspend is still a performance eating monster

Offline

#11 2017-12-02 17:22:41

loqs
Member
Registered: 2014-03-06
Posts: 17,315

Re: Suspend function on Nvidia Prop. driver problem

@boojum have you tried using multiple paramaters on a single line and proven it does not work?
See below for example for it working

$ cat /etc/modprobe.d/test.conf 
options libiscsi debug_libiscsi_conn=1 debug_libiscsi_session=1
$ sudo modprobe libiscsi
$ systool -vm libiscsi
Module = "libiscsi"

  Attributes:
    coresize            = "49152"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    debug_libiscsi_conn = "1"
    debug_libiscsi_eh   = "0"
    debug_libiscsi_session= "1"

  Sections:
    .bss                = "0xffffffffa04b03c0"
    .gnu.linkonce.this_module= "0xffffffffa04b0080"
    .note.gnu.build-id  = "0xffffffffa04ac000"
    .orc_unwind         = "0xffffffffa04aebd8"
    .orc_unwind_ip      = "0xffffffffa04ae088"
    .rodata.str1.1      = "0xffffffffa04acf85"
    .rodata.str1.8      = "0xffffffffa04ac3e8"
    .rodata             = "0xffffffffa04ad260"
    .smp_locks          = "0xffffffffa04ac3c8"
    .strtab             = "0xffffffffa0201118"
    .symtab             = "0xffffffffa01ff000"
    .text               = "0xffffffffa04a6000"
    __bug_table         = "0xffffffffa04b0000"
    __kcrctab_gpl       = "0xffffffffa04ac310"
    __ksymtab_gpl       = "0xffffffffa04ac030"
    __ksymtab_strings   = "0xffffffffa04adc84"
    __mcount_loc        = "0xffffffffa04afcd0"
    __param             = "0xffffffffa04ae010"
$ sudo rm /etc/modprobe.d/test.conf 
$ sudo rmmod libiscsi 
$ systool -vm libiscsi
Error opening module libiscsi
$ sudo modprobe libiscsi
$ systool -vm libiscsi
Module = "libiscsi"

  Attributes:
    coresize            = "49152"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "0"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    debug_libiscsi_conn = "0"
    debug_libiscsi_eh   = "0"
    debug_libiscsi_session= "0"

  Sections:
    .bss                = "0xffffffffa078c3c0"
    .gnu.linkonce.this_module= "0xffffffffa078c080"
    .note.gnu.build-id  = "0xffffffffa0788000"
    .orc_unwind         = "0xffffffffa078abd8"
    .orc_unwind_ip      = "0xffffffffa078a088"
    .rodata.str1.1      = "0xffffffffa0788f85"
    .rodata.str1.8      = "0xffffffffa07883e8"
    .rodata             = "0xffffffffa0789260"
    .smp_locks          = "0xffffffffa07883c8"
    .strtab             = "0xffffffffa0201118"
    .symtab             = "0xffffffffa01ff000"
    .text               = "0xffffffffa0782000"
    __bug_table         = "0xffffffffa078c000"
    __kcrctab_gpl       = "0xffffffffa0788310"
    __ksymtab_gpl       = "0xffffffffa0788030"
    __ksymtab_strings   = "0xffffffffa0789c84"
    __mcount_loc        = "0xffffffffa078bcd0"
    __param             = "0xffffffffa078a010"

Offline

#12 2017-12-02 17:27:08

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

Ioqs wrote:

have you tried using multiple paramaters on a single line and proven it does not work?

No I did not, and I'm sure that it works. Thou one-option-per-line seems clearer, that's it.

@Qik000
Let's try to figure it out. Drivers first, post the output of

lspci -k | grep -A 2 -E "(VGA|3D)"
pacman -Qs '^nvidia*'
cat /etc/mkinitcpio.conf
lsmod | grep nvidia

...and we will take it from there.

Last edited by boojum (2017-12-02 17:28:46)

Offline

#13 2017-12-02 17:35:48

loqs
Member
Registered: 2014-03-06
Posts: 17,315

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:
Ioqs wrote:

have you tried using multiple paramaters on a single line and proven it does not work?

No I did not, and I'm sure that it works. Thou one-option-per-line seems clearer, that's it.

Ah its just you stated the format of Qik000's /etc/modprobe.d/file.conf was wrong so I assumed you meant it was actually not syntactically valid in some way
and would be related to the cause of this bug not you find one option per line clearer.

Offline

#14 2017-12-02 17:36:07

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:
Ioqs wrote:

have you tried using multiple paramaters on a single line and proven it does not work?

No I did not, and I'm sure that it works. Thou one-option-per-line seems clearer, that's it.

@Qik000
Let's try to figure it out. Drivers first, post the output of

lspci -k | grep -A 2 -E "(VGA|3D)"
pacman -Qs '^nvidia*'
cat /etc/mkinitcpio.conf
lsmod | grep nvidia

...and we will take it from there.

lspci -k | grep -A 2 -E "(VGA|3D)"
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
    Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
    Kernel driver in use: i915
--
01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 980] (rev a1)
    Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980]
    Kernel driver in use: nvidia
cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(piix ide_disk reiserfs)
MODULES=()

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=()

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No raid, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect block filesystems)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev block filesystems)
#
##   This setup assembles a pata mdadm array with an encrypted root FS.
##   Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
#    HOOKS=(base udev block mdadm encrypt filesystems)
#
##   This setup loads an lvm2 volume group on a usb device.
#    HOOKS=(base udev block lvm2 filesystems)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr, fsck and shutdown hooks.
HOOKS=(base udev autodetect modconf block filesystems keyboard fsck)

# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()
lsmod | grep nvidia
nvidia_drm             45056  5
nvidia_modeset        888832  11 nvidia_drm
nvidia              13897728  861 nvidia_modeset
drm_kms_helper        131072  2 i915,nvidia_drm
drm                   303104  11 i915,nvidia_drm,drm_kms_helper

Last edited by Qik000 (2017-12-02 17:41:42)

Offline

#15 2017-12-02 17:38:33

loqs
Member
Registered: 2014-03-06
Posts: 17,315

Re: Suspend function on Nvidia Prop. driver problem

Please use code tags for commands and their output Qik000.
So /etc/mkinitcpio.conf is default and the other outputs look normal.

Offline

#16 2017-12-02 17:39:22

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

loqs wrote:

Please use code tags for commands and their output Qik000.
So /etc/mkinitcpio.conf is default and the other outputs look normal.

so what to do to make suspend work as intended ?

Offline

#17 2017-12-02 17:42:51

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

Try adding nvidia module to your mkinitcpio.conf, like so:

MODULES=(nvidia)

the rebuild initramfs with:

mkinitcpio -p linux

restart and test.

And:

Ioqs wrote:

Please use code tags for commands and their output Qik000.

Last edited by boojum (2017-12-02 17:43:58)

Offline

#18 2017-12-02 17:47:55

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:

Try adding nvidia module to your mkinitcpio.conf, like so:

MODULES=(nvidia)

the rebuild initramfs with:

mkinitcpio -p linux

restart and test.

And:

Ioqs wrote:

Please use code tags for commands and their output Qik000.

sudo mkinitcpio -p linux
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 4.13.12-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 4.13.12-1-ARCH
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: aic94xx
==> WARNING: Possibly missing firmware for module: wd719x
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful

Now reboot and test it or what ?

Offline

#19 2017-12-02 17:49:06

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

Yes, reboot and then test performance after suspend.

Offline

#20 2017-12-02 17:56:49

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:

Yes, reboot and then test performance after suspend.

I undid the changes bacause it was impossible to wake-up - i got a black screen with only the cursor visible, i could't move it.

Last edited by Qik000 (2017-12-02 18:04:33)

Offline

#21 2017-12-02 18:09:41

boojum
Member
From: /dev/null
Registered: 2013-09-23
Posts: 44
Website

Re: Suspend function on Nvidia Prop. driver problem

It's to do with KMS but it was worth to try. I've somewhere to be but here are some things to keep you busy:

  • Look trough journalctl / X11 logs and check for any errors there.

  • Read through these two wiki pages (one, two).

  • And you can get detailed info (options etc etc.) of nvidia with modinfo.

Good luck!

Offline

#22 2017-12-02 18:16:52

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

boojum wrote:

It's to do with KMS but it was worth to try. I've somewhere to be but here are some things to keep you busy:

  • Look trough journalctl / X11 logs and check for any errors there.

  • Read through these two wiki pages (one, two).

  • And you can get detailed info (options etc etc.) of nvidia with modinfo.

Good luck!

But the fix from the article worked yesterday... Today it doesnt work. So if it worked what stopped it from working ? A reboot ?

Last edited by Qik000 (2017-12-02 18:19:33)

Offline

#23 2017-12-02 20:35:55

RaptorAnon
Member
Registered: 2014-03-16
Posts: 11
Website

Re: Suspend function on Nvidia Prop. driver problem

Following this. I recommend looking through this opensuse thread for some possible solutions.
https://forums.opensuse.org/showthread. … -RAM/page3
I also recommend sending a complaint to nvidia or posting on the nvidia linux forums.

EDIT: note that some of the solutions on the suse forum are suse-only solutions that involve uninstalling a linux kernel package only found in suse. Just a heads up.

Last edited by RaptorAnon (2017-12-02 20:37:14)

huh?

Offline

#24 2017-12-03 12:27:57

Qik000
Banned
Registered: 2017-09-23
Posts: 61

Re: Suspend function on Nvidia Prop. driver problem

RaptorAnon wrote:

Following this. I recommend looking through this opensuse thread for some possible solutions.
https://forums.opensuse.org/showthread. … -RAM/page3
I also recommend sending a complaint to nvidia or posting on the nvidia linux forums.

EDIT: note that some of the solutions on the suse forum are suse-only solutions that involve uninstalling a linux kernel package only found in suse. Just a heads up.

that doesnt fix the issue

Offline

#25 2017-12-03 18:52:05

loqs
Member
Registered: 2014-03-06
Posts: 17,315

Re: Suspend function on Nvidia Prop. driver problem

Qik000 wrote:

that doesnt fix the issue

Please list everything that you tried from that thread that did not work so that others no what did not work,
this prevents redundant suggestions and others may have insight into the cause from what failed to work.

Offline

Pages: 1 2

Board footer

Powered by FluxBB