12:39 a.m.
I find that Fedora's usual graphical boot splash goes away when I install the
proprietary Nvidia drivers from rpmfusion.org, replaced with a text-based progress-bar.
However, I found that all I needed to do to get back to the graphical version was to
change gfxpayload=text to gfxpayload=keep in the GRUB2 config. Given that it seems so
simple, I wonder why this isn't the default? Have I just shot myself in the foot in
some way that I'm yet to realise?
--
Peter Oliver
2:42 p.m.
Hello,
I've had the same issue here. I did have gfxpayload=text /boot/grub2/grub.cfg and I
changed all instances from text to keep.
But still, no graphical boot.
So perhaps it's not that simple? :)
----- Original Message -----
From: "Peter Oliver"
<lists.rpmfusion.org(a)mavit.org.uk>
To: rpmfusion-users(a)lists.rpmfusion.org
Sent: Thursday, 15 August, 2013 12:39:45 AM
Subject: Plymouth with Nvidia drivers
I find that Fedora's usual graphical boot splash goes away when I
install the proprietary Nvidia drivers from rpmfusion.org, replaced
with a text-based progress-bar.
However, I found that all I needed to do to get back to the graphical
version was to change gfxpayload=text to gfxpayload=keep in the
GRUB2 config. Given that it seems so simple, I wonder why this
isn't the default? Have I just shot myself in the foot in some way
that I'm yet to realise?
--
Peter Oliver
8:23 p.m.
On Thu, 15 Aug 2013, Peter Oliver wrote:
I found that all I needed to do to get back to the graphical version
was to change gfxpayload=text to gfxpayload=keep in the GRUB2 config. Given
that it seems so simple, I wonder why this isn't the default? Have I just
shot myself in the foot in some way that I'm yet to realise?
To answer my own question, I noticed the following in dmesg:
[ 14.950146] NVRM: Your system is not currently configured to drive a VGA console
[ 14.950149] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
[ 14.950150] NVRM: requires the use of a text-mode VGA console. Use of other console
[ 14.950152] NVRM: drivers including, but not limited to, vesafb, may result in
[ 14.950153] NVRM: corruption and stability problems, and is not supported.
--
Peter Oliver
2:33 a.m.
On Sat, 17 Aug 2013 21:23:49 +0100 (BST)
Peter Oliver <lists.rpmfusion.org(a)mavit.org.uk> wrote:
| On Thu, 15 Aug 2013, Peter Oliver wrote:
|
| > I found that all I needed to do to get back to the graphical version
| > was to change gfxpayload=text to gfxpayload=keep in the GRUB2 config. Given
| > that it seems so simple, I wonder why this isn't the default? Have I just
| > shot myself in the foot in some way that I'm yet to realise?
|
| To answer my own question, I noticed the following in dmesg:
|
| [ 14.950146] NVRM: Your system is not currently configured to drive a VGA console
| [ 14.950149] NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
| [ 14.950150] NVRM: requires the use of a text-mode VGA console. Use of other console
| [ 14.950152] NVRM: drivers including, but not limited to, vesafb, may result in
| [ 14.950153] NVRM: corruption and stability problems, and is not supported.
|
Also watch where you change the setting
/boot/grub2/grub.cfg
for example is probably re-created from the /etc config files in some
situations.
A pain if you ask me!
Anthony Thyssen ( System Programmer ) <A.Thyssen(a)griffith.edu.au>
--------------------------------------------------------------------------
No dragon can resist the fascination of riddling talk, and of
wasting time trying to understand it. -- JRR Tolkein, "The Hobbit"
--------------------------------------------------------------------------
Anthony's Castle http://www.ict.griffith.edu.au/anthony/
4142
days inactive
4146
days old
rpmfusion-users@lists.rpmfusion.org
3 comments
3 participants
participants (3)
-
Anthony Thyssen -
Peter Oliver -
Richard Allen