downgrading nvidia drivers [was Re: nvida 3:390.25 eats all mu cpus]

2018-02-25 Thread D. Hugh Redelmeier
| From: D. Hugh Redelmeier | | | From: Ed Greshko | | | Have you tried just "dnf downgrade akmod-nvidia"? | | Now I have. It worked well. Thanks! | | GDM seems to be confused but with patience I can get to my familiar | (GNOME) desktop and get back

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 18:26 schrieb D. Hugh Redelmeier: | From: Reindl Harald | understaning the boot process of my systems is something self-evindent for me | from the day i bought my first PC - likely the reason why i never needed to | reinstall any OS be it windows or

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread D. Hugh Redelmeier
| From: Reindl Harald | understaning the boot process of my systems is something self-evindent for me | from the day i bought my first PC - likely the reason why i never needed to | reinstall any OS be it windows or linux from scratch That would suggest that you are

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Sergio
Sent from my Android Em 25/02/2018 2:09 da tarde, Dave Pawson escreveu: > > On 25 February 2018 at 13:47, Sérgio Basto wrote: > > >> > >> > >> >  rpm -q kernel-core --scripts | grep add > >> > >> /bin/kernel-install add 4.14.18-300.fc27.x86_64 >

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 16:50 schrieb Dave Pawson: I said "I've had no reason to change it" (grub.cfg) More accurately, I've had no reason to modify it, since it has worked as installed. If it works, why should I spend weeks finding out how? it does not take weeks, it takes minutes and the moment

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
I said "I've had no reason to change it" (grub.cfg) More accurately, I've had no reason to modify it, since it has worked as installed. If it works, why should I spend weeks finding out how? I don't on Windows / Mac OS I only dive deeper when something goes wrong. It would appear you get

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 16:42 schrieb Dave Pawson: I shan't respond any more - you seem to be rather upset about this. i just find it exhausting when one expects to get every little step explained and prepared for copy instead trying to understand some basic stuff give somebody a fish versus

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
I shan't respond any more - you seem to be rather upset about this. Dave On 25 February 2018 at 14:51, Reindl Harald wrote: > > > Am 25.02.2018 um 15:47 schrieb Dave Pawson: >> >> On 25 February 2018 at 14:41, Reindl Harald >> wrote: >> >> >>>

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 15:55 schrieb D. Hugh Redelmeier: | From: Dave Pawson | Maybe (I may be wrong). | I have a note: | | #Show the boot information. | #edit /boot/grub/grub.conf On an EFI system, /boot/efi/EFI/fedora/grub.cfg. Most systems these days have EFI, but most

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread D. Hugh Redelmeier
| From: Dave Pawson | Maybe (I may be wrong). | I have a note: | | #Show the boot information. | #edit /boot/grub/grub.conf On an EFI system, /boot/efi/EFI/fedora/grub.cfg. Most systems these days have EFI, but most of those are willing to emulate the old fashioned BIOS

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 15:47 schrieb Dave Pawson: On 25 February 2018 at 14:41, Reindl Harald wrote: maybe you have an UEFI system Quite possibly don't get me wrong but do you know anything about your system? again: https://wiki.centos.org/HowTos/Grub2 On UEFI-based

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
On 25 February 2018 at 14:41, Reindl Harald wrote: > maybe you have an UEFI system > Quite possibly > again: https://wiki.centos.org/HowTos/Grub2 > On UEFI-based systems, the command will be grub2-mkconfig -o > /boot/efi/EFI/centos/grub.cfg > >> seems grub2 now has it

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 15:27 schrieb Dave Pawson: Fedora 27 [root@localhost ~]# ls /boot/grub2 grubenv themes maybe you have an UEFI system again: https://wiki.centos.org/HowTos/Grub2 On UEFI-based systems, the command will be grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg seems grub2 now

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
Fedora 27 [root@localhost ~]# ls /boot/grub2 grubenv themes seems grub2 now has it # cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console"

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
Maybe (I may be wrong). I have a note: #Show the boot information. #edit /boot/grub/grub.conf #Remove 'rhbg quiet' from the end of the line NO LONGER WORKS but grub.conf no longer in /boot? Any suggestions? Dave On 25 February 2018 at 14:07, Reindl Harald wrote: >

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
On 25 February 2018 at 13:47, Sérgio Basto wrote: >> >> >> > rpm -q kernel-core --scripts | grep add >> >> /bin/kernel-install add 4.14.18-300.fc27.x86_64 >> /lib/modules/4.14.18-300.fc27.x86_64/vmlinuz || exit $? >> /bin/kernel-install add 4.15.3-300.fc27.x86_64 >>

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 15:03 schrieb Dave Pawson: Tried (my normal solution). In this case I'm getting no response to the keyboard, software continues to load with default kernel. Hence never get into grub menu? than you have really other problems - maybe it's because the idiotic defaults to hide

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
Tried (my normal solution). In this case I'm getting no response to the keyboard, software continues to load with default kernel. Hence never get into grub menu? Dave On 25 February 2018 at 13:54, Reindl Harald wrote: > > > Am 25.02.2018 um 14:47 schrieb Sérgio Basto: >>

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Reindl Harald
Am 25.02.2018 um 14:47 schrieb Sérgio Basto: On Sun, 2018-02-25 at 13:42 +, Dave Pawson wrote: Inline comment On 25 February 2018 at 13:08, Sérgio Basto wrote: Sergio, I'm running F27. Should that be /bin/kernel-install add 4.14.18-200.fc26.x86_64

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Sérgio Basto
On Sun, 2018-02-25 at 13:42 +, Dave Pawson wrote: > Inline comment > > On 25 February 2018 at 13:08, Sérgio Basto wrote: > > > > Sergio, I'm running F27. Should that be > > > > > > /bin/kernel-install add 4.14.18-200.fc26.x86_64 > > > /lib/modules/4.14.18- > > > >

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
Inline comment On 25 February 2018 at 13:08, Sérgio Basto wrote: >> Sergio, I'm running F27. Should that be >> >> /bin/kernel-install add 4.14.18-200.fc26.x86_64 /lib/modules/4.14.18- >> > 200.fc27.x86_64/vmlinuz >> >> I.e. fc27 not fc26? > > Please run [1] and see what

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Sérgio Basto
On Sun, 2018-02-25 at 11:00 +, Dave Pawson wrote: > Seems to be a gnome issue? > Installed kde, boots and runs fine. > > First 'big' issue I have seen with gnome. Maybe it is wayland as some users reported, so you may try use gnome with Xorg instead gnome with wayland ... > Thanks for

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
Correction. It runs fine, once KDE is in place. Takes me a minute or so to get past login after reboot. Thereafter running as per normal. Just need to get used to KDE now! Dave On 25 February 2018 at 11:00, Dave Pawson wrote: > Seems to be a gnome issue? > Installed

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
Seems to be a gnome issue? Installed kde, boots and runs fine. First 'big' issue I have seen with gnome. Thanks for the help Sergio. Dave On 25 February 2018 at 09:13, Dave Pawson wrote: > On 24 February 2018 at 17:42, Sérgio Basto wrote: >> On

Re: nvida 3:390.25 eats all mu cpus

2018-02-25 Thread Dave Pawson
On 24 February 2018 at 17:42, Sérgio Basto wrote: > On Sat, 2018-02-24 at 17:33 +, Dave Pawson wrote: >> current kernel is 4.15.4-300 >> >> Not sure why I'd want to remove 4.14.18-200? > > not remove, more or less the same efect of dnf reintall, oops I picked > the wrong