Livna-config-display. How to erase?

[v00d00]

I'm looking for a way to erase the livna-config-display package while keeping the nvidia driver installed.

It continually alters my xorg.conf to the point where i have now made the file immutable to stop it messing with my settings.

Cue the new problem, where by the above package crashes on boot and shutdown with an error that basically says it cant alter the file anymore.

Short of forcing the removal and ignoring dependencies, or installing the mainstream driver and tainting things, is there any way of ridding myself of this package?

Thanks.

[Hlingler]

Hello:

For the record, I had the same problem with livna-config-display constantly goofing with my xorg.conf file, and I used the same fix: make xorg.conf immutable. I don't recall any crashes, but I still ended up switching to (...ahem...) driver that "taints" the kernel. You might be able to disable this annoying feature by editing one of the python scripts in /usr/lib/python2.5/site-packages/livnaConfigDisplay/ or maybe it's /usr/sbin/livna-config-display that's the culprit, but which one of these (or another?) and which lines to edit/remove, I don't know.

Good Luck,
V

[Seve]

Hello:
v00d00... / Hlingler
One way around the issue is to remove the kmod-nvida package(s)
Sorry, I cannot recall the exact package names ?

and use the nvidia-x11-drv rpm package from freshrpms.
It is not kernel specific [uses dkms] and works just fine.

http://moonshine.freshrpms.net/rpm.html?id=436

If you do not have the freshrpms repo installed, then just follow the instructions here : http://freshrpms.net/

Just remember to disable the freshrpms repo after you install the nvidia pacakge to avoid potential dependency issues with livna.


Seve

[wintersm]

if you look at /etc/init.d/nvidia it executes /usr/sbin/nvidia-config-display which is what is modifying your files - that program checks to see if you have the correct kernel module.. if it changes xorg.conf I dont know, but you can easily edit /etc/init.d/nvidia to stop it from executing nvidia-config-display

:)

[Hlingler]

if you look at /etc/init.d/nvidia it executes /usr/sbin/nvidia-config-display which is what is modifying your files - that program checks to see if you have the correct kernel module.. if it changes xorg.conf I dont know, but you can easily edit /etc/init.d/nvidia to stop it from executing nvidia-config-display

:)Yeah, that's gotta be it, because I have no such file /etc/init.d/nvidia and I'm using the freshrpms driver package. That file is part of the livna xorg-x11-drv-nvidia-xyz.rpm package. I hesitate to suggest this, but maybe just moving /etc/init.d/nvidia to /etc/init.d/backups/nvidia will stop it, without screwing up anything else <fingers crossed, no guarantees>.

V

[wintersm]

i wouldnt move it, to stop something from starting under init, issue the following command as root

chkconfig nvidia off

the problem with stopping it is the kernel module might not be loaded..

[v00d00]

I am 50/50 on just going back to the taint method.

I had to do that originally to get my 8600 running when F7 first came out, and it ran fine using that method until recently. But in doing so i forgot all about the hassle of livna-config-display and its associated programs.

Basically i set up my card and monitor to give custom refresh rates, and add a few extra options for the driver. These were what got removed, and the display always defaulted back to a 60Hz refresh rate or less (which hurts my eyes). I use 85Hz or 75Hz depending on resolution, and created custom modelines to allow me to do it.

The more i think about it, i may just use that taint, and get rid of kernel upgrades from yum (not like they really add anything new that i use anyway). Its a simple solution that gets rid of the problem.

[Firewing1]

Sorry about that problem, I'm going to fix it for F8 (I develop lcd for livna) when we move to static configuration. If you'd like, replace your /etc/init.d/nvidia with the nvidia.txt file attached (remove the .txt, I had to rename it to upload). Once that's done it shouldn't touch your xorg.conf unless the module's missing.

Answering your original question though, that's impossible ATM because the drivers require lcd to edit xorg.conf.

What are you editing that's being removed? It should only change the 'driver' field and add options to make Compiz work, which if it didn't would prevent the driver from working so that's not a bad thing.

Also, you could always run l-c-d and disable the driver on bootup, and edit then xorg.conf accordingly to make it work.
Firewing1

[v00d00]

I sort of went the way of the taint, for a couple of reasons.

Firewing, also you should maybe be aware that i was getting a glx load error with Livna's nvidia driver. I found it caused x to crash and restart after i installed Doom 3 earlier. Removing it and going back to the taint method fixed the problem and Doom works once again. Although when i installed the nvidia driver it said their was something up with glx, and something had to be repaired.

My main annoyance with it, was my custom modelines all disappeared, whether due to l-c-d im unsure, but they were running ok until i installed kmod-nvidia, then disappeared after the install (which caused my monitor to go a bit nuts, and the max res i had was 800x600 which was a tad bit annoying)..

But its fixed and working for the minute.

[Firewing1]

Have you 'gone for the taint' before? Maybe your libglx.so was replaced... Either that or Doom3 hardcodes libglx.so. Livna places it in a non-default location so it doesn't replace the original libglx.so and uses ldconfig to load nVidia's libglx rather than Mesa's...

If libglx wasn't working, it would crash all GLX applications and not just doom3 which is why I'm bringing this up...
Firewing1

[merijn]

Ok I found two solutions for this problem.

1. You can just go to: System --> Administration --> Livna Display Configuration and
uncheck "allow livna-config-display to edit configuration files"

for me this didn't work because for some reason the text was grey and I couldn't uncheck it.
I think this is because I use the poulsbo (psb) driver (more info here) (http://www.happyassassin.net/2009/08/10/intel-gma500-poulsbo-on-fedora-11-repository-with-working-3d-compiz-support/).
When i start "Livna Display Configuration" I get some error about not having installed the amd ati driver or something.

2. edit the config file of "Livna Display Configuration" located at /etc/sysconfig/livna-config-display
and replace "active = true" with "active = false"
[edit]the second solution didn't work. Now my driver doesn't load properly. If I find out why Ill post it

[Firewing1]

Why are you using livna-config-display if you have the Intel PSB driver? livna-config-display is only supposed to be used with the nvidia, fglrx or catalyst drivers...

[merijn]

I dont know. The livna display configuration was installed as dependency.
When I try to remove it rpm also wants to remove my psb driver.
And when I disable livna from the config file as described in my previous post my X wont work. Display gets weird and striped when I restart X.

Resolving Dependencies
--> Running transaction check
---> Package livna-config-display.noarch 0:0.0.23-1.fc11 set to be erased
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-psb-0.31.0-15.fc11.i586
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-psb-0.31.0-15.fc11.i586
--> Processing Dependency: livna-config-display for package: xorg-x11-drv-psb-0.31.0-15.fc11.i586
--> Running transaction check
---> Package xorg-x11-drv-psb.i586 0:0.31.0-15.fc11 set to be erased
--> Processing Dependency: psb-kmod-common >= 4.41.1 for package: kmod-psb-2.6.30.9-102.fc11.i586-4.41.1-10.fc11.5.i586
--> Running transaction check
---> Package kmod-psb-2.6.30.9-102.fc11.i586.i586 0:4.41.1-10.fc11.5 set to be erased
--> Processing Dependency: kmod-psb-2.6.30.9-102.fc11.i586 >= 4.41.1-10.fc11.5 for package: kmod-psb-4.41.1-10.fc11.5.i586
--> Running transaction check
---> Package kmod-psb.i586 0:4.41.1-10.fc11.5 set to be erased
--> Finished Dependency Resolution

[Firewing1]

Hrm, I'll speak to Adam (the psb package maintainer) - I think a patch or two is needed in livna-config-display to fully work with psb properly.