Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

Slow screen recovery after nVidia driver update?

For help or questions about 64-bit version of MEPIS, this is the forum to use.
Message
Author
User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9325
Joined: Wed Jul 12, 2006 2:26 pm

Re: Slow screen recovery after nVidia driver update?

#21 Post by kmathern » Thu Jan 30, 2014 9:46 pm

The kernel lines in menu.lst are the ony place I know of of where the xdrvr=nvidia confx cheats would get added on a permanent basis. Would you have manually added them to the kernel options line while at the grub screen for troubleshooting purposes or whatever?

What does 'cat /proc/cmdline' show? If you booted the current session with those cheats, they will show up in the output.

User avatar
Eadwine Rose
Forum Veteran
Forum Veteran
Posts: 6050
Joined: Wed Jul 12, 2006 2:10 am

Re: Slow screen recovery after nVidia driver update?

#22 Post by Eadwine Rose » Fri Jan 31, 2014 4:20 am

Silent Observer wrote:Sorry to be so slow replying on this -- had a mild heart attack early Monday morning the 20th, then triple bypass surgery on the 24th and came home from the hospital yesterday (29th) and been sleeping a lot; that seems to be receding now and I'm getting more able to read and type on my computer.
And he just throws that in just like that.. geez

Get well soon!
MX-17.1_x64 Horizon 14-3-2018 * 4.15.0-1-amd64 ext4 Xfce 4.12.3 * AMD Asus M4A785TD-V EVO AM3 * ASUS GF GT640-1GD5-L NVIDIA 384.130 * AMD Proc. Athl II X4 635, sAM3 * HDA ATI SB VT1708S An * 2x4Gb DDR3 1600 Kingst * 22" Samsung SyncM P2250 * HP F2280

User avatar
lucky9
Forum Veteran
Forum Veteran
Posts: 11380
Joined: Wed Jul 12, 2006 5:54 am

Re: Slow screen recovery after nVidia driver update?

#23 Post by lucky9 » Fri Jan 31, 2014 12:47 pm

Get well soon!
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

User avatar
Silent Observer
Forum Regular
Forum Regular
Posts: 432
Joined: Wed Nov 09, 2011 9:51 pm

Re: Slow screen recovery after nVidia driver update?

#24 Post by Silent Observer » Fri Jan 31, 2014 1:39 pm

kmathern wrote:The kernel lines in menu.lst are the ony place I know of of where the xdrvr=nvidia confx cheats would get added on a permanent basis. Would you have manually added them to the kernel options line while at the grub screen for troubleshooting purposes or whatever?
I most likely did enter those cheat codes on the grub screen, when I was trying to get the 64-bit to boot originally. I don't recall for certain, this has run with few problems for several months. I surely haven't entered a cheat code during routine start in many, many cycles (I restart this machine approximately weekly, more often if I'm tweaking something, and haven't entered a video-related cheat code since it started booting into X successfully after nVidia driver installation).
What does 'cat /proc/cmdline' show? If you booted the current session with those cheats, they will show up in the output.

Code: Select all

root=/dev/sdb7 nomce quiet splash vga=788 xdrvr=nvidia confx
No idea how that's getting in there...
But just to confuse the issue, the last kdm.log I could find that has a startup looks like this:

Code: Select all

nvLock: client timed out, taking the lock

X.Org X Server 1.7.7
Release Date: 2010-05-04
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.10-3-amd64 x86_64 Debian
Current Operating System: Linux Donald 2.6.36-1-mepis64-smp #1 SMP Thu Mar 31 15:10:33 CDT 2011 x86_64
Kernel command line: root=/dev/sdb7 nomce quiet splash vga=788 xdrvr=nvidia confx
Build Date: 22 October 2013  09:04:18AM
xorg-server 2:1.7.7-17 (Moritz Muehlenhoff <jmm@debian.org>) 
Current version of pixman: 0.21.2
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 17 20:50:46 2014
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
SELinux: Disabled on system, not enabling in X server
No time stamps, this was from kdm.log.6.gz -- most of the newer ones contain only the single line

Code: Select all

nvLock: client timed out, taking the lock
, but kdm.log.1, modified date 6:53 AM this morning (should have been idle for 7+ hours at that point, or just waking from screen saver) that minute -- I don't recall what time I first got to my console today) looks like this:

Code: Select all

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "NoSymbol+AnyOf(all)"
>                   Using last definition for duplicate fields
Errors from xkbcomp are not fatal to the X server
nvLock: client timed out, taking the lock
lucky9 wrote:Get well soon!
Working on it... :)
MEPIS 11 64-bit, MSI P6NGM-L motherboard, Core 2 Quad 9400 2.67 GHz, 4 GiB PC2-5300 RAM, 1 GiB nVidia GT520 on PCI Express x16.

User avatar
lucky9
Forum Veteran
Forum Veteran
Posts: 11380
Joined: Wed Jul 12, 2006 5:54 am

Re: Slow screen recovery after nVidia driver update?

#25 Post by lucky9 » Fri Jan 31, 2014 2:09 pm

My understanding of what is supposed to happen is that if you enter a cheatcode it is automatically written to the GRUB boot stanza. Hence you find one that works and you're done.
Yes, even I am dishonest. Not in many ways, but in some. Forty-one, I think it is.
--Mark Twain

User avatar
Silent Observer
Forum Regular
Forum Regular
Posts: 432
Joined: Wed Nov 09, 2011 9:51 pm

Re: Slow screen recovery after nVidia driver update?

#26 Post by Silent Observer » Fri Jan 31, 2014 2:25 pm

lucky9 wrote:My understanding of what is supposed to happen is that if you enter a cheatcode it is automatically written to the GRUB boot stanza. Hence you find one that works and you're done.
But if that were the case, it should show in the menu.lst. However, I think I may have a resolution for this dilemma; when I installed 64-bit, I had just finished getting 32-bit PAE running and may have still had a 32-bit SMP kernel installation; I'm pretty sure the actual grub startup screen still offers me one or more 32-bit options, aid in order to preserve those, I might have manually edited one of them to add the 64-bit kernel install. That is to say, I may not be starting from /sdb7/boot/grub/menu.lst; rather, I may be using a different copy of menu.lst even though I'm using /sdb7/boot/vmlinuz* as my kernel. Let me go check for other copies of menu.lst that may be active.

(let it never be said I can't come up with an oddball way to make stuff not work right)

Okay, this is probably where we're getting the conflict between menu.lst and /proc/cmdline:

Code: Select all

timeout 10
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title MEPIS 64-bit at sdb7, newest kernel
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sdb7 nomce quiet splash vga=788 xdrvr=nvidia confx
initrd /boot/initrd.img

title MEPIS 32-bit at sdb1, newest kernel
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sdb1 nomce quiet splash vga=788 
initrd /boot/initrd.img
boot

title MEPIS at sdb1, kernel 2.6.36-1-mepis-pae
root (hd0,0)
kernel /boot/vmlinuz-2.6.36-1-mepis-pae root=/dev/sdb1 nomce quiet splash vga=788 
initrd /boot/initrd.img-2.6.36-1-mepis-pae
boot

title MEPIS at sdb1, kernel 2.6.36-1-mepis-smp
root (hd0,0)
kernel /boot/vmlinuz-2.6.36-1-mepis-smp root=/dev/sdb1 nomce quiet splash vga=788 
initrd /boot/initrd.img-2.6.36-1-mepis-smp
boot

title Win NT/2000/XP at sda1
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloader +1

title Win 95/98/Me at sda5
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,4)
chainloader +1

title MEPIS at sdb7, newest kernel
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sdb7 nomce quiet splash vga=788
initrd /boot/initrd.img

title MEMTEST
kernel /boot/memtest86+.bin

I'm almost certain this is the copy that's actually being used during boot...
Last edited by Silent Observer on Fri Jan 31, 2014 2:30 pm, edited 1 time in total.
MEPIS 11 64-bit, MSI P6NGM-L motherboard, Core 2 Quad 9400 2.67 GHz, 4 GiB PC2-5300 RAM, 1 GiB nVidia GT520 on PCI Express x16.

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9325
Joined: Wed Jul 12, 2006 2:26 pm

Re: Slow screen recovery after nVidia driver update?

#27 Post by kmathern » Fri Jan 31, 2014 2:26 pm

lucky9 wrote:My understanding of what is supposed to happen is that if you enter a cheatcode it is automatically written to the GRUB boot stanza. Hence you find one that works and you're done.
Your understanding is wrong, the mepis specific cheats (xdrvr=*, confx, etc.) don't touch grub or it's menu.lst.
You might be confusing those with the 'nomodeset' & 'nouveau.modeset=0" options that sgfxi automatically adds when it installs the nvidia driver.


@Silent Observer, was your nvidia driver installed using sgfxi? If it was the presence of the xdrvr=nvidia & confx cheats might be a non-issue anyway.
When you install the nvidia driver with sgfxi it does a preinstall cleanup, removing all packages with the word "nvidia" in their packagename.
One of the packages that gets removed is nvidia-xconfig, that in turn removes Warren's mepis-init package (mepis-init has nvidia-xconfig as a dependency).
A script in the mepis-init package (/etc/init.d/mepis-init.sh) is what processes the the xdrvr=nvidia & confx cheats. If the mepis-init package isn't installed, the cheats aren't acted upon, so it doesn't matter whether they're on kernel options line or not. {I had forgotten about sgfxi doing this}
What does the following show:

Code: Select all

apt-cache policy mepis-init

User avatar
Silent Observer
Forum Regular
Forum Regular
Posts: 432
Joined: Wed Nov 09, 2011 9:51 pm

Re: Slow screen recovery after nVidia driver update?

#28 Post by Silent Observer » Fri Jan 31, 2014 3:17 pm

kmathern wrote:@Silent Observer, was your nvidia driver installed using sgfxi? If it was the presence of the xdrvr=nvidia & confx cheats might be a non-issue.
When you install the nvidia driver with sgfxi it does a preinstall cleanup, removing all packages with the word "nvidia" in their packagename.
One of the packages that gets removed is nvidia-xconfig, that in turn removes Warren's mepis-init package (mepis-init has nvidia-xconfig as a dependency).
A script in the mepis-init package (/etc/init.d/mepis-init.sh) is what processes the the xdrvr=nvidia & confx cheats. If the mepis-init package isn't installed, the cheats aren't acted upon, so it doesn't matter whether they're on kernel options line or not. {I had forgotten about sgfxi doing this}
What does the following show:

Code: Select all

apt-cache policy mepis-init
Yes, I've never installed the nVidia driver with any tool or method other than sgfxi.

Edit: forgot to answer: apt-cache policy mepis-init returns:

Code: Select all

mepis-init:
  Installed: (none)
  Candidate: 11.0.01
  Version table:
     11.0.01 0
        990 ftp://ftp.mepis.com/mepis/ mepis-11.0/main amd64 Packages
After my last post , I closed my browser to find my wallpaper had reverted, as it's done before to a different image with no icons; the problem again was in the "activities" menu (upper right cashew), not sure how I'd once again gotten to a round dozen different activities, but only one of those has the wallpaper and icons I expect and an accidental key combo must have switched me over. I spent a couple minutes deleting the unnamed extras, then edited out the xdrvr=nvidia confx in the 64-bit line of the active menu.lst, and restarted, but wound up with a black screen and good mouse cursor, had a "you have three updates" popup in the corner, though, and CTL-ALT-DEL got me a visible exit menu; I've seen this before when xorg had gotten an update without nVidia driver change. I logged as root at command line (option 3), and ran sgfxi -z; as commonly occurs on this system, there was a cleanup error, so I had to issue reboot and return to the command line to finish installation. Doing that restored the update version of the nVidia driver that had putatively started this issue, but I figured I'd let it run and revert later if needed.

Once the driver had finished installing, another reboot brought me quickly and efficiently into X (at which time I installed the three curl-related updates), and everything seems normal now relative to screen saver breaks. I haven't had a chance to let the screen time out and see how it recovers, but recovery after manual lock is better than it's been.

Edit: I left my desk and let the screen time out to screen saver and lock, then moved the mouse -- got the unlock dialog instantly, and after entering my password, the wallpaper, icons, and mouse cursor were ready to work in less than a second. I still don't know what caused the problem, but it's fixed. I'm marking the thread solved, but I'd be interested in additional discussion on where this odd problem came from.
MEPIS 11 64-bit, MSI P6NGM-L motherboard, Core 2 Quad 9400 2.67 GHz, 4 GiB PC2-5300 RAM, 1 GiB nVidia GT520 on PCI Express x16.

Post Reply

Return to “64-bit Newbies”