| 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 to work.
This worked for a short time. A
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 linux from scratch
That w
| 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 insane :-)
(I mean that as a
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
> >> /lib/modules/4.14.18-300.fc27.x86_64/vml
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 w
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 up
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&paste instead trying to understand some
basic stuff
give somebody a fish vers
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:
>>
>>
>>> maybe you have an UEFI system
>>>
>> Quite possibly
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 of those are willing to
| 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 / MBR regime. Generall
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 systems, the command wil
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
>> # cat /etc/default/gru
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 h
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"
GRUB_CMDLINE_LINUX="rd.driver.bl
Am 25.02.2018 um 15:12 schrieb 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
because you didn't cope with major changes like grub to grub2 many years
ago but we are *b
Am 25.02.2018 um 15:09 schrieb Dave Pawson:
Reading
https://www.freedesktop.org/software/systemd/man/kernel-install.html
The file /bin/kernel-install add 4.14.18-300.fc27.x86_64 /lib/modules/4.14.18-
300.fc27.x86_64/vmlinuz is an executable?
Earlier you said to run
kernel-install remove
then
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:
>
>
> Am 25.02.2018 um 15:0
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
>> /lib/modules/4.15.3-300.fc27.
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
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:
>>
>> On Sun, 2018-02-25 at
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
/lib/modules/4.14.18-
200.fc27.x86_6
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-
> > > > 200.fc27.x86_64/vmlinuz
>
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 script that you should ru
On Sun, 2018-02-25 at 09:13 +, Dave Pawson wrote:
> 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 sam
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 the
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 kde, boots and runs fine.
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 Sat, 2018-02-24 at 17:33 +, Dave Pawson wr
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 script, I want wrote:
28 matches
Mail list logo