Slow video after upgrade to 2010.11 [SOLVED - sorta]

[mousegun]

help!

After updating my AMD Barton machine to PCLOS2010.11, the video is now so slow that browser scrolling is a "waterfall".  The video card is a Geforce2 mx400 32MB.

It worked fine before the update, but now needs to be reconfigured with the Control Center video configuration checking the  "Enable RENDER Acceleration" option. After logging out and logging back in it works as before the update.  Checking /etc/X11/xorg.conf I find that enabling "render acceleration" deletes a line with 'Option "RenderAccel" "false"' in it.  So far so good.

Trouble is, it won't survive a reboot.  The Option "RenderAccel" "false" line reappears and I can't find out where it comes from. I have to re-enable and log out/in each time.

Anyone have a clue about this?

[T6]

hello and welcome to the forum!

upgrading 2010.11 to latest version?

what video driver uses this very old video card?

[coffeetime]

Trouble is, it won't survive a reboot.  The Option "RenderAccel" "false" line reappears and I can't find out where it comes from. I have to re-enable and log out/in each time.

Try to reboot [you can use ctrl+alt+del]

[mousegun]

hello and welcome to the forum!

upgrading 2010.11 to latest version?

what video driver uses this very old video card?

Driver is from the nvidia96xx package for the GeForce2 MX to GeForce 4 cards.  Been using this driver for at least two years with no complaints.. until now, that is.

The problem is not with the driver but with /etc/X11/xorg.conf settings surviving reboot.

[mousegun]

Trouble is, it won't survive a reboot.  The Option "RenderAccel" "false" line reappears and I can't find out where it comes from. I have to re-enable and log out/in each time.

Try to reboot [you can use ctrl+alt+del]

Therein lies the problem.  The setting won't survive a reboot... any kind of reboot.  It'll live through a log out/log in, but not a shutdown of any kind.

[T6]

ok, it seems that you are using right driver, that is good

how are you editing the xorg.conf file?

are you opening kwrite as logging as root or are you editing file as normal user with superuser privileges?

[mousegun]

ok, it seems that you are using right driver, that is good

how are you editing the xorg.conf file?

are you opening kwrite as logging as root or are you editing file as normal user with superuser privileges?

Well, I tried it couple of ways: with the options in the video card configuration screen in Control Panel in superuser privs and with vim in a root terminal session. Every time I reboot that one line reappears.

I think it's being regenerated from an init script somewhere, but I just can't find it.

[Texstar]

I have never had PCLinuxOS rewrite my /etc/X11/xorg.file and know of no script at boot that alters it. You can however change the permission on the file that will prevent it from being overwritten.

By setting the file as immutable, any user including super-user cannot write or delete the file but they can read it. Below is an example on how to set an immutable file attribute.

[root@localhost texstar]# chattr +i /etc/X11/xorg.conf

To reverse:

[root@localhost texstar]# chattr -i /etc/X11/xorg.conf

[mousegun]

I have never had PCLinuxOS rewrite my /etc/X11/xorg.file and know of no script at boot that alters it. You can however change the permission on the file that will prevent it from being overwritten.

By setting the file as immutable, any user including super-user cannot write or delete the file but they can read it. Below is an example on how to set an immutable file attribute.

[root@localhost texstar]# chattr +i /etc/X11/xorg.conf

To reverse:

[root@localhost texstar]# chattr -i /etc/X11/xorg.conf

Thank you.  I considered doing that but wasn't sure how it would impact the boot process.  However, it's worth a try.  I was focusing on the reason xorg.conf always was restored through a reboot but at this stage I'll try chattring the file and see what happens.

I'll be back...

[mousegun]

OK.  Making xorg.conf immutable works and doesn't seem to throw any irrecoverable errors.  I'll just have to write a script to launch drakconf to change parameters that preserves the "i" attribute.  Good idea.

Still kinda worried about why the file is restored through a reboot.  Oh well...

Thanks a lot.  Texstar saves the day!