nvidia.ko issue

[Jack Wallen]

hello,

trying to update my Fedora 10. i use the nvidia-kmod packages and am 
getting this error:

Test Transaction Errors:   file 
/lib/modules/2.6.27.9-159.fc10.i686/extra/nvidia/nvidia.ko from install 
of kmod-nvidia-2.6.27.9-159.fc10.i686-180.22-1.fc10.i686 conflicts with 
file from package kmod-nvidia-2.6.27.9-159.fc10.i686-177.82-1.fc10.7.i686

Upon my last upgrade emerald will no longer load. I am assuming that 
issue is related to this new update issue. has anyone managed to fix 
this update issue?

thanks so much.

jack

[Thorsten Leemhuis]

On 08.02.2009 18:32, jack wallen wrote:
> trying to update my Fedora 10. i use the nvidia-kmod packages and am 
> getting this error:
>
> Test Transaction Errors:   file 
> /lib/modules/2.6.27.9-159.fc10.i686/extra/nvidia/nvidia.ko from install 
> of kmod-nvidia-2.6.27.9-159.fc10.i686-180.22-1.fc10.i686 conflicts with 
> file from package kmod-nvidia-2.6.27.9-159.fc10.i686-177.82-1.fc10.7.i686

Quoting
http://rpmfusion.org/FAQ#head-a0575c3e9e8a6be3c18a572cf97df92c0a4f2c83

---
I'm getting file conflict errors from yum when installing kmods. How can 
I solve this?

yum-fedorakmod plugin is known to cause them (see 
https://bugzilla.redhat.com/show_bug.cgi?id=482893 for details). It is 
no longer needed, so you can safely remove it using:

rpm -e yum-fedorakmod
---

Hope this helps!

CU
knurd

[Jack Wallen]

Thorsten Leemhuis wrote:
> Quoting
> http://rpmfusion.org/FAQ#head-a0575c3e9e8a6be3c18a572cf97df92c0a4f2c83

thank you Thorsten. removing yum-fedorakmod did the trick.
>

[Jack Wallen]

jack wallen wrote:
> Thorsten Leemhuis wrote:
> > Quoting
> > http://rpmfusion.org/FAQ#head-a0575c3e9e8a6be3c18a572cf97df92c0a4f2c83
>
> thank you Thorsten. removing yum-fedorakmod did the trick.
> >

forgot to mention that this didn't solve the compiz issue. compiz is 
segfaulting. i've been googling this and have yet to come up with an 
answer. i ran compiz with gdb and this is all i got:

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)

Program received signal SIGSEGV, Segmentation fault.
0x000022c0 in ?? ()

[Matthew Saltzman]

On Sun, 2009-02-08 at 14:15 -0500, jack wallen wrote:
> jack wallen wrote:
> > Thorsten Leemhuis wrote:
> > > Quoting
> > > http://rpmfusion.org/FAQ#head-a0575c3e9e8a6be3c18a572cf97df92c0a4f2c83
> >
> > thank you Thorsten. removing yum-fedorakmod did the trick.
> > >
>
> forgot to mention that this didn't solve the compiz issue. compiz is 
> segfaulting. i've been googling this and have yet to come up with an 
> answer. i ran compiz with gdb and this is all i got:
>
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> ---Type <return> to continue, or q <return> to quit---
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000022c0 in ?? ()

I haven't seen that issue, but if you want to debug, you'll need to
install the compiz-debuginfo package.  Enable the fedora-debuginfo and
updates-debuginfo repos.
>

[oleksandr korneta]

on 02/08/2009 01:51 PM Thorsten Leemhuis wrote:
> yum-fedorakmod plugin is known to cause them (see 
> https://bugzilla.redhat.com/show_bug.cgi?id=482893 for details). It is 
> no longer needed, so you can safely remove it using:

thanks a bunch. Helped me as well. I was surprised to discover yesterday 
  that even having  "Driver nvidia" and  Load  "glx" in my xorg.cong I 
have no 3d and

Xlib: extension "GLX" missing on display ":0.0".

message popping up here and there. Everything works perfectly after 
removing that package.

cheers