I think my problem is not going to solve right away and I can live without nvidia acceleration for now. By the way how can i safely remove kmod-nvidia for now? Will "yum remove kmod-nvidia" will do? I am asking this becasue I have upgraded the kernel ( to
2.6.17) and removed my old kernel (2.6.15) already. So i don't know if I try to remove this kmod-nvidia, I might end up without X or something like that??? because I saw during kmod-nvidia, it changed several settings of
<a href="http://X.org">X.org</a> configs.<br><br><br><br><div><span class="gmail_quote">On 7/4/06, <b class="gmail_sendername">Scott R. Godin</b> <<a href="mailto:scott.g@mhg2.com">scott.g@mhg2.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On Mon, 3 Jul 2006 15:12:35 -0700, Lonni J Friedman wrote:<br><br>> On 7/3/06, Scott R. Godin <
<a href="mailto:scott.g@mhg2.com">scott.g@mhg2.com</a>> wrote:<br>> > On Mon, 3 Jul 2006 18:02:00 +0800, Deepak Shrestha wrote:<br>> ><br>> > > But I did the nvidia installation as instructed in<br>
> > > <a href="http://www.mjmwired.net/resources/mjm-fedora-fc5.html#nvidia">http://www.mjmwired.net/resources/mjm-fedora-fc5.html#nvidia</a><br>> > ><br>> > > I checked if kmod-nvidia is really installed or not through rpm
<br>> and it<br>> > > says<br>> > > it is installed.<br>> > > ------------------<br>> > > $ rpm -q kmod-nvidia<br>> > > kmod-nvidia-1.0.8762-2.2.6.17_1.2139_FC5<br>> > > ----------------------
<br>> > ><br>> > > Now I am confused.<br>> > ><br>> ><br>> > what you should be paying attention to is the installation<br>> instructions<br>> > from the livna repo instead:
<a href="http://rpm.livna.org/">http://rpm.livna.org/</a> also note that<br>> the<br>> > news post from March 29th points out that the steps necessary have<br>> > changed. (hopefully they'll get around to updating or appending the
<br>> > original instructions to reflect the change)<br>> ><br>> > This having been said, I should warn you that with the current<br>> > kmod-nvidia I experienced quite a bit of error WRT memory corruption
<br>> > that reflected back into swap, which reflected back into what<br>> actually<br>> > got onto / -- I wound up having to manually fsck /, redo my swap<br>> > partition, and uninstall kmod-nvidia, after which my problems went
<br>> > away.<br>> ><br>> > Fortunately I was able to get quite a bit of debuginfo that will get<br>> > forwarded on to the lovely nvidia folks with a pound of thanks for<br>> not<br>> > open-sourcing their drivers so things like this could get caught
<br>> sooner.<br>> > =P<br>> ><br>> > my advice: live without kmod-nvidia for now. It's *not* ready for<br>> > prime-time; not because of livna but because of nvidia themselves.<br>> ><br>
> > Many thanks to Mike Harris for straightening me on this, and for<br>> > assistance with the recovery process. Cheers dude, where do I send<br>> the<br>> > beer? :)<br>><br>> What makes you so convinced that the nvidia X driver caused this mess,
<br>> and not hardware problems, or some other bug?<br>><br><br>Because the nvidia driver is a steaming pile of poodle feces wrapped in<br>a diaper full of stale chili burritos and sun-baked to august sidewalk<br>temperatures? If you don't believe me, feel free to ask the lead Red Hat
<br>guy for all things X, Mike Harris, what his opinion on and experience<br>with the nvidia drivers has been, with regards to<br><br> o stability<br> o general bug-free-ness<br> o reproducability of errors<br> o memory corruption
<br> o responsiveness of the Mfr. to bug-reports involving end-users<br><br>and other similarly fun topics. I'm sure he'll be more diplomatic than I<br>on print, but you'll easily grok the undertones of what he'd LIKE to put
<br>in print (let alone say out loud) regarding Nvidia's driver.<br><br>Having been bitten myself and doing FOUR re-installs of FC5 over the<br>past few months after the system gradually went completely<br>wahooni-shaped unrecoverably (though I tried valiantly to save things
<br>each time when I started noticing things going subtly weirder and<br>weirder), until I finally wised up and eliminated the nvidia driver from<br>the equation and watched my problems evaporate, I'm a believer with<br>logged kernel panics, a trashed swap partition that had to be remade,
<br>and a near-totalled glibc-common (along with several other rpms) with<br>half its files in /lost+found/ after a massive manual fsck to prove it.<br>and NO re-install after removing kmod_nvidia this time. and all is<br>
stable.<br><br>Fortunately /home is on a separate DRIVE altogether. =)<br><br>But feel free to continue losing sanity, loosening your hair, and<br>applying many QWERTY tattoos to your forehead in the meantime, if you<br>want to continue with it. Maybe you're one of the lucky ones _now_, but
<br>you'll get bit eventually.<br><br><br>-----BEGIN PGP SIGNATURE-----<br>Version: GnuPG v1.4.4 (GNU/Linux)<br><br>iD8DBQBEqnb8lfQeTCNIWLARAt8EAJ4vAztXs+J6x6wc/4ghbf+LDszP9QCfZpct<br>fF4HuoCKX3iS1jkjblmNkEU=<br>=kOtS<br>
-----END PGP SIGNATURE-----<br><br><br>--<br>fedora-list mailing list<br><a href="mailto:fedora-list@redhat.com">fedora-list@redhat.com</a><br>To unsubscribe: <a href="https://www.redhat.com/mailman/listinfo/fedora-list">
https://www.redhat.com/mailman/listinfo/fedora-list</a><br><br></blockquote></div><br>