Re: Is RPMfusion on strike? [SOLVED -- at least for me]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi gilpel;

I am no hardware expert; but maybe I can suggest some things to double
check and to remove and reinstall.

On Mon, 2009-08-24 at 09:36 +0500, gilpel@xxxxxxxxxx wrote:

> I'm trying :) But I never enabled rpmfusion-nonfree-updates-testing, and I
> installed the new update for kernel 2.6.29.6-217.2.8.fc11.x86_64.
> 
First some very basic stuff.  I am going to assume that by now you are
getting flustered, frustrated and flumexed.  You have probably already
done the stuff listed below; but take a deep breath and start again.

1) Can you boot under one of the kernels?
2) Do you have yumex installed?  I use yumex when the operations are
simple, when I want to keep them simple and when I want to think
visually.  Therefore, it is handy, to me, for double checking stuff.
3) Check on the gnome menu Applications => System Tools => nVidia
Display Settings.  Under X server Information; System Information write
down the NVIDIA Driver Version: so you have it handy if things go south.
4) Using Nautilus (or whatever your file browser is) go
to /etc/X11/xorg.conf and check and note down the Driver in the Section
"Device".  Also check the driver in xorg.conf.backup and
xorg.conf.livna-config-backup.  This so you can go to a different
xorg.config file if you have to rescue latter.  Keep these backups.
5) Optionally, as root cd to /etc/X11/ and remove any extra xorg.conf
bakups just to keep things clean.  I have the "nouveau' driver
installed, just in case.  I have a xorg.config.BU.vesa and a
xorg.config.BU.nouveau for quick fixes from a text screen.

> First time I rebooted, boot stopped, just where it used to with -217.2.7:
> "r8169: eth0: link up" . I checked if there was any akmod left to mess
> things up and all I found was /var/cache/akmods. I supposed this was
> unrelated, but I deleted it just the same. Now, the boot process stops at
> "atd".
> 
6) Optionally, test that the hardware is working by typing "vesa" or
"nouveau" as the "Device" driver in xorg-conf and reboot.
7) Using yumex (you can use the yum command line of course) list the
installed packages and search for kmod-nvidia.  Click to un-check
akmod-nvidia and any kmod-nvidia+kernel+version (185-18.14.x and any
other version), then remove by Processing Queue.  Any additional
dependencies that need to be removed will be included.  There should be
about five or six.  If there is more or some of the dependencies
suggested look weird or dangerous don't continue but cancel and get back
to this list.
8) When processing is done click on Available.  Search for kmod-nvidia
and select kmod-nvidia... 18.14 and kmod-nvidia...2.3...18.14.  Again
Process Queue. akmod, kmod-nvidia-for-other kernels, xorg-x11-drv-nvidia
+version and xorg-x11-drv-nvidia-libs+version should be included in the
dependencies list.  Double check that all the version numbers are the
same i.e. 185-18.14-x.  If something different happens cancel and get
back to the list.

NB.  Double check that akmods is installed; rpm -qa akmods.  This is a
different program from akmods-nvidia. To get it functioning again you
have to restart; maybe a complete shutdown and a cold boot just to be
sure.  Maybe you don't have to double check if its installed or cold
boot.  I just don't know; but better safe than sorry.


-- 
Regards Bill
Fedora 11, Gnome 2.26.3
Evo.2.26.3, Emacs 23.1.1

-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux