On 07/01/2023 03:30, Stephen Morris wrote:
On 6/1/23 22:22, John Pilkington wrote:
Heads up. After today's updates I get black unresponsive screens. OK
in 6.0.15
I'm using the nvidia 525.60.11 driver from
rpmfusion-nonfree-nvidia-driver and there is no issue with kernel 6.0.16.
regards,
Stev
> On Jan 7, 2023, at 02:44, Tim via users wrote:
>
> On Sat, 2023-01-07 at 14:36 +1100, Stephen Morris wrote:
>> I've just done an update which installed kernel 6.0.16 and I forgot
>> to run grub2-mkconfig, and when I booted from the grub menu's defined in
>> /boot/grub2/grub.cfg presumably
Tim:
>> I have to ask, since I see a lot of grubby posts (pun intended):
>>
>> I've *NEVER* run grub2-mkconfig. I've always just yum/dnf update (do
>> all current updates), or just dnf update kernel (if I wanted to
>> specifically just do that), and it's always installed the new kernel
>> properly
El 6/1/23 a las 14:33, Karlderletzte escribió:
Hello, since yesterday i do have a big problem.
After some updates and a succesfull reboot, i first could not login
anymore. Alsways a wrong password.
I solved this with resetting root password and my two user passwords.
Now i could login.
Root acc
> On 7 Jan 2023, at 15:42, Tim via users wrote:
>
> Tim:
>>> I have to ask, since I see a lot of grubby posts (pun intended):
>>>
>>> I've *NEVER* run grub2-mkconfig. I've always just yum/dnf update (do
>>> all current updates), or just dnf update kernel (if I wanted to
>>> specifically just
I remove rhgb too. I will even sometimes remove quiet. it doesn't do
anything to my system, that I do not want done. I like to see the boot
noise and if something comes up "failure" and I need my password for
something. This is only usually something t do with a filesystem issue.
Like e2fsck or
95% of the time when I see initrd did not get built and included in the
boot, it was because the kernel install runs in 2 steps, the first step
puts in the kernel grub entry, and the 2nd step build initrd and adds
initrd to the grub config.run "dnf reinstall kernel" and that fixes
it. Usually
On 7/1/23 22:06, John Pilkington wrote:
On 07/01/2023 03:30, Stephen Morris wrote:
On 6/1/23 22:22, John Pilkington wrote:
Heads up. After today's updates I get black unresponsive screens.
OK in 6.0.15
I'm using the nvidia 525.60.11 driver from
rpmfusion-nonfree-nvidia-driver and there is no
Can anyone try using grubby --set-default to change the default boot kernel
to something other than the most recently-installed kernel, successfully?
It tells me that it obeys my request, and grubby --info=DEFAULT shows that
the default boot kernel is what I specified.
But at boot the grub
On 7/1/23 18:43, Tim via users wrote:
On Sat, 2023-01-07 at 14:36 +1100, Stephen Morris wrote:
I've just done an update which installed kernel 6.0.16 and I forgot
to run grub2-mkconfig, and when I booted from the grub menu's defined in
/boot/grub2/grub.cfg presumably updated by grubby, it did no
grubby changes the per-kernel options (in the entries files), it has never
cared about what was in /etc/default/grub.
Typically /etc/default/grub is useless because typically no one ever runs
grub2-mkconfig, so the file is kind of pointless.
And kernel installs copy the options from one of the ot
On 7/1/23 23:33, Jonathan Billings wrote:
On Jan 7, 2023, at 02:44, Tim via users wrote:
On Sat, 2023-01-07 at 14:36 +1100, Stephen Morris wrote:
I've just done an update which installed kernel 6.0.16 and I forgot
to run grub2-mkconfig, and when I booted from the grub menu's defined in
/boo
On 8/1/23 02:42, Tim via users wrote:
Tim:
I have to ask, since I see a lot of grubby posts (pun intended):
I've *NEVER* run grub2-mkconfig. I've always just yum/dnf update (do
all current updates), or just dnf update kernel (if I wanted to
specifically just do that), and it's always installed
On 8/1/23 09:55, Barry wrote:
On 7 Jan 2023, at 15:42, Tim via users wrote:
Tim:
I have to ask, since I see a lot of grubby posts (pun intended):
I've *NEVER* run grub2-mkconfig. I've always just yum/dnf update (do
all current updates), or just dnf update kernel (if I wanted to
specifical
On 1/7/23 17:24, Stephen Morris wrote:
I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write its
log to /var/log) as the end of my log file is completely different to
what you are showing. I also don't have an xorg.conf file as I can get
the 4K resolution I run with without the ne
On 8/1/23 12:48, Roger Heflin wrote:
grubby changes the per-kernel options (in the entries files), it has
never cared about what was in /etc/default/grub.
Typically /etc/default/grub is useless because typically no one ever
runs grub2-mkconfig, so the file is kind of pointless.
And kernel in
On Sat, 07 Jan 2023 20:40:18 -0500
Sam Varshavchik wrote:
> But at boot the grub menu still highlights the most recently installed
> kernel, and that's what boots by default.
If you can stand looking through the scripts that are used to build
the grub.cfg (I think they may live in /etc/grub.d)
On 8/1/23 11:49, Roger Heflin wrote:
95% of the time when I see initrd did not get built and included in
the boot, it was because the kernel install runs in 2 steps, the first
step puts in the kernel grub entry, and the 2nd step build initrd and
adds initrd to the grub config. run "dnf reins
On 8/1/23 12:59, Samuel Sieb wrote:
On 1/7/23 17:24, Stephen Morris wrote:
I've attached ~/.local/share/xorg/Xorg.0.log (my Xorg doesn't write
its log to /var/log) as the end of my log file is completely
different to what you are showing. I also don't have an xorg.conf
file as I can get the 4K
Tom Horsley writes:
On Sat, 07 Jan 2023 20:40:18 -0500
Sam Varshavchik wrote:
> But at boot the grub menu still highlights the most recently installed
> kernel, and that's what boots by default.
If you can stand looking through the scripts that are used to build
the grub.cfg (I think they may
On Sat, 2023-01-07 at 18:49 -0600, Roger Heflin wrote:
> 95% of the time when I see initrd did not get built and included in
> the boot, it was because the kernel install runs in 2 steps, the
> first step puts in the kernel grub entry, and the 2nd step build
> initrd and adds initrd to the grub con
On Sun, 2023-01-08 at 12:53 +1100, Stephen Morris wrote:
> I have left the rhgb and quiet settings in there and if I want to see
> the boot details then I will use the ESC key to turn on the details.
The trouble with that, is by then its too late to see which was the
likely cause of the hang-up (
On Sat, 2023-01-07 at 20:40 -0500, Sam Varshavchik wrote:
> Can anyone try using grubby --set-default to change the default boot kernel
> to something other than the most recently-installed kernel, successfully?
>
> It tells me that it obeys my request, and grubby --info=DEFAULT shows that
> t
On 8/1/23 15:14, Sam Varshavchik wrote:
Tom Horsley writes:
On Sat, 07 Jan 2023 20:40:18 -0500
Sam Varshavchik wrote:
> But at boot the grub menu still highlights the most recently installed
> kernel, and that's what boots by default.
If you can stand looking through the scripts that are used
On 8/1/23 15:58, Tim via users wrote:
On Sat, 2023-01-07 at 20:40 -0500, Sam Varshavchik wrote:
Can anyone try using grubby --set-default to change the default boot kernel
to something other than the most recently-installed kernel, successfully?
It tells me that it obeys my request, and grubby
25 matches
Mail list logo
