6:26 p.m.
Hello,
After a failed attempt to install the manufacturer's nvidia driver, my
system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad T430) does
not reach the graphical login screen any more, but instead ends up in a
white screen with a frowning computer cartoon and the message
"Oh no! Something has gone wrong. A problem occurred and the system can't
recover. Please contact a system administrator."
I can still do Ctrl-Alt-F2 to log into text mode. When I try startx, I
get an empty screen with white or black background and a mouse cursor,
extending over my two screens (laptop and external). When I try startkde it
says:
$DISPLAY is not set or cannot connect to X server.
The only error in /var/etc/X11.0.log is:
Failed to load module "nv" (module does not exist, 0)
In /var/log/messages, there are a bunch of lines like (I'm typing by
hand):
gnome-session[2658]: (gnome-shell:2949): Cogl-WARNING **:
./driver/gl/cogl-framebuffer-gl.c:561: GL error (1282): Invalid operation
Could not find a solution on Google.
I already reinstalled a bunch of packages, including cogl, gdm,
gnome-shell, @kde-desktop, xorg-x11-drv-nouveau, kernel, but no change.
Any advice? Thanks!
Best,
Oliver
--
Oliver Ruebenacker
IT Project Lead at PanGenX (http://www.pangenx.com)
Be always grateful, but never satisfied.
6:40 p.m.
On 10/31/2013 10:26 AM, Oliver Ruebenacker wrote:
Hello,
After a failed attempt to install the manufacturer's nvidia driver,
my system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad
T430) does not reach the graphical login screen any more, but instead
ends up in a white screen with a frowning computer cartoon and the
message
"Oh no! Something has gone wrong. A problem occurred and the system
can't recover. Please contact a system administrator."
I can still do Ctrl-Alt-F2 to log into text mode. When I try startx,
I get an empty screen with white or black background and a mouse
cursor, extending over my two screens (laptop and external). When I
try startkde it says:
$DISPLAY is not set or cannot connect to X server.
The only error in /var/etc/X11.0.log is:
Failed to load module "nv" (module does not exist, 0)
In /var/log/messages, there are a bunch of lines like (I'm typing by
hand):
gnome-session[2658]: (gnome-shell:2949): Cogl-WARNING **:
./driver/gl/cogl-framebuffer-gl.c:561: GL error (1282): Invalid operation
Could not find a solution on Google.
I already reinstalled a bunch of packages, including cogl, gdm,
gnome-shell, @kde-desktop, xorg-x11-drv-nouveau, kernel, but no change.
Any advice? Thanks!
Best,
Oliver
I remember running into this problem over time with Fedora 16,18 and
19 so did a fresh install using the standard nouveau driver, then when
the system was working, followed the instructions on the Fedora page
to install the nvidia driver.
Apart from a slightly smoother movement of windows and terminals, and
I usually have quite several open at once, I have seen no real benefit
from the nvidia video driver.
I believe nvidia has released helpful code to the
nouveau devs but have
no knowledge on the benefits or other.
Roger
9:24 p.m.
On 10/30/2013 04:40 PM, Roger wrote:
On 10/31/2013 10:26 AM, Oliver Ruebenacker wrote:
>
> Hello,
>
> After a failed attempt to install the manufacturer's nvidia driver,
> my system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad
> T430) does not reach the graphical login screen any more, but instead
> ends up in a white screen with a frowning computer cartoon and the
> message
>
> "Oh no! Something has gone wrong. A problem occurred and the system
> can't recover. Please contact a system administrator."
>
> I can still do Ctrl-Alt-F2 to log into text mode. When I try
> startx, I get an empty screen with white or black background and a
> mouse cursor, extending over my two screens (laptop and external).
> When I try startkde it says:
>
> $DISPLAY is not set or cannot connect to X server.
>
> The only error in /var/etc/X11.0.log is:
>
> Failed to load module "nv" (module does not exist, 0)
>
> In /var/log/messages, there are a bunch of lines like (I'm typing
> by hand):
>
> gnome-session[2658]: (gnome-shell:2949): Cogl-WARNING **:
> ./driver/gl/cogl-framebuffer-gl.c:561: GL error (1282): Invalid
> operation
>
> Could not find a solution on Google.
>
> I already reinstalled a bunch of packages, including cogl, gdm,
> gnome-shell, @kde-desktop, xorg-x11-drv-nouveau, kernel, but no change.
>
> Any advice? Thanks!
>
> Best,
> Oliver
> I remember running into this problem over time with Fedora 16,18 and
> 19 so did a fresh install using the standard nouveau driver, then
> when the system was working, followed the instructions on the Fedora
> page to install the nvidia driver.
> Apart from a slightly smoother movement of windows and terminals, and
> I usually have quite several open at once, I have seen no real
> benefit from the nvidia video driver.
I believe nvidia has released helpful code to the nouveau devs but
have no knowledge on the benefits or other.
> Roger
The major benefits from the Nvidia driver for me are working power
management and working vdpau, which lets me play 1080P video smoothly on
an old Intel core2 cpu. With the nouveau driver, my video card runs
about 30 degrees hotter, and HD video looks like crap. Of course, 3D
rendering is much much faster with the Nvidia driver, but I don't play
games.
John
2:25 a.m.
On 31.10.2013, Oliver Ruebenacker wrote:
Failed to load module "nv" (module does not exist, 0)
Take a look into /boot/grub2/grub.cfg, most probably the uninstaller
didn't restore the kernel boot parameters which has been placed in
order to get the nv driver to work. Looks like you'll have to do this
manually (= remove the nouveau blacklisting etc.).
6:55 a.m.
Hello,
On Thu, Oct 31, 2013 at 3:25 AM, Heinz Diehl <htd(a)fritha.org> wrote:
On 31.10.2013, Oliver Ruebenacker wrote:
> Failed to load module "nv" (module does not exist, 0)
Take a look into /boot/grub2/grub.cfg, most probably the uninstaller
didn't restore the kernel boot parameters which has been placed in
order to get the nv driver to work. Looks like you'll have to do this
manually (= remove the nouveau blacklisting etc.).
Found no reference of nv or nvidia in /boot/grub2/grub.conf. It also says
in that file not to edit it because it will be auto-generated.
AFAICT, nvidia driver was never installed. Ran the installer a few times,
but it always failed. I had put a "blacklist nouveau" in
/etc/modprobe.d/blacklist.conf, but removed that long since.
Best,
Oliver
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
--
Oliver Ruebenacker
IT Project Lead at PanGenX (http://www.pangenx.com)
Be always grateful, but never satisfied.
7:46 a.m.
Hello,
On Thu, Oct 31, 2013 at 7:55 AM, Oliver Ruebenacker <curoli(a)gmail.com>wrote:
Hello,
On Thu, Oct 31, 2013 at 3:25 AM, Heinz Diehl <htd(a)fritha.org> wrote:
> On 31.10.2013, Oliver Ruebenacker wrote:
>
> > Failed to load module "nv" (module does not exist, 0)
>
> Take a look into /boot/grub2/grub.cfg, most probably the uninstaller
> didn't restore the kernel boot parameters which has been placed in
> order to get the nv driver to work. Looks like you'll have to do this
> manually (= remove the nouveau blacklisting etc.).
>
Found no reference of nv or nvidia in /boot/grub2/grub.conf. It also
says in that file not to edit it because it will be auto-generated.
AFAICT, nvidia driver was never installed. Ran the installer a few
times, but it always failed. I had put a "blacklist nouveau" in
/etc/modprobe.d/blacklist.conf, but removed that long since.
My system boots again into KDE after this:
sudo yum groupinstall kde-desktop-environment
sudo systemctl enable --force kdm.service
Now back to the original problem: how I can make KDE work with two
monitors again.
Best,
Oliver
--
Oliver Ruebenacker
IT Project Lead at PanGenX (http://www.pangenx.com)
Be always grateful, but never satisfied.
8:11 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/31/2013 12:26 AM, Oliver Ruebenacker wrote:
Hello,
After a failed attempt to install the manufacturer's nvidia driver,
my system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad
T430) does not reach the graphical login screen any more, but
instead ends up in a white screen with a frowning computer cartoon
and the message
"Oh no! Something has gone wrong. A problem occurred and the
system can't recover. Please contact a system administrator."
One solution I dound with difficulty is that Alt+F4 (I think) kills
the "frowning computer" and (at least in my case) leaves you with a
working system. Surely something to be improved in the UI....
Theo.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlJyVxsACgkQEr8WrU8nPV26hQCfRDUGzYPlZdWnQbgloCicvkc7
E/kAoKZbeDiZBDRfoZLM7+F3lboIptHm
=lmQ3
-----END PGP SIGNATURE-----
8:34 a.m.
Hello,
On Thu, Oct 31, 2013 at 9:11 AM, Theodore Papadopoulo <
Theodore.Papadopoulo(a)inria.fr> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/31/2013 12:26 AM, Oliver Ruebenacker wrote:
>
> Hello,
>
> After a failed attempt to install the manufacturer's nvidia driver,
> my system (Fedora 19, with both Gnome and KDE, on a Lenovo ThinkPad
> T430) does not reach the graphical login screen any more, but
> instead ends up in a white screen with a frowning computer cartoon
> and the message
>
> "Oh no! Something has gone wrong. A problem occurred and the
> system can't recover. Please contact a system administrator."
One solution I dound with difficulty is that Alt+F4 (I think) kills
the "frowning computer" and (at least in my case) leaves you with a
working system. Surely something to be improved in the UI....
Really? That's so funny.
Certainly it is the most useless error message I ever saw. It should at
least indicate form which direction the error came from. Maybe the author
of that piece of software felt it too embarrassing to reveal the source of
this message.
Best,
Oliver
--
Oliver Ruebenacker
IT Project Lead at PanGenX (http://www.pangenx.com)
Be always grateful, but never satisfied.
1:30 p.m.
On 10/31/2013 06:11 AM, Theodore Papadopoulo wrote:
One solution I dound with difficulty is that Alt+F4 (I think) kills
the "frowning computer" and (at least in my case) leaves you with a
working system. Surely something to be improved in the UI....
And the first step, of course, is a more informative error message.
3865
days inactive
3866
days old
8 comments
6 participants
participants (6)
-
Heinz Diehl -
Joe Zeff -
John Wendel -
Oliver Ruebenacker -
Roger -
Theodore Papadopoulo