Re: fedup 20 -> 21 -> No X
On Sat, 25 Jul 2015 06:37:10 -0700
Rich Emberson <emberson.rich(a)gmail.com> wrote:
Ah, fedora upgrades using fedup ...
Starting with Fedora 20, did
> yum update
and then
> fedup --network 21 --product=nonproduct
Took a while but there were no issues but
remember, as root
> export PATH=$PATH:$HOME/bin:/sbin:/usr/sbin
or use
> su -
to become root otherwise fedup has an issue.
So, now rebooted and it started.
I have all my machines in multi-user mode just
in case there is an issue with X.
Now tried to start X ... and there was an issue.
[snip]
[ 2.969504] fbcon: nouveaufb (fb0) is primary device
[ 3.284089] nouveau 0000:06:00.0: fb0: nouveaufb frame buffer
device [ 3.284091] nouveau 0000:06:00.0: registered panic notifier
[ 3.290053] [drm] Initialized nouveau 1.2.1 20120801 for
0000:06:00.0 on minor 0
END dmesg
So, fedup somehow blew away something.
The Question is what?
rpm -qa --qf '%{NAME} %{VERSION}-%{RELEASE} %{ARCH}\n' | grep kmod
kmod-libs 19-1.fc21 x86_64
kmod 19-1.fc21 x86_64
What did fedup change and how can I recover?
If you're using kmod, that means you've been using the rpmfusion nvidia
binary driver, right? But it looks like the kernel is trying to use the
nouveau open source driver. They're incompatible.
Maybe you need to set up to use the nvidia binary blob again. I think
this involves blacklisting nouveau and installing the nvidia driver for
your kernel. There should be instructions you can find online, or in
the archives of this list, for how to do this.