Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
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,
Steve
Thanks. It's still the same for me after another dnf upgrade run.
Using KDE, it boots and continues for some time after password entry,
but then stays unresponsive. No light shows after Caps Lock key, and no
mouse pointer or action. 6.0.15 works.
/var/log/Xorg.0.log looks similar for both. For info, here's the end:
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): connected
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): 400.0 MHz maximum
pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): connected
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): Internal TMDS
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): 340.0 MHz maximum
pixel clock
[ 201.787] (--) NVIDIA(GPU-0):
[ 217.638] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[ 217.739] (II) NVIDIA(0): Setting mode "NULL"
[ 217.783] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 217.825] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0},
HDMI-0: 1920x1080_50 @1920x1080 +1680+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
John
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
> 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 updated by grubby, it did not run >> initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. > > 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 all by itself. No further action was required by me. > > What are people doing to their systems that they paint themselves into > a corner that they have to manually manage this, then have to pick up > the pieces when it doesn't work? You should never need to run grub2-mkconfig after each kernel update. The only reason I can guess at is that they ran it to overwrite the file in /boot/efi/EFI/fedora/ (which is normally a stub that loads the default file in /boot/grub2/) and now they have to manually run it each time. Normally, the only reason you’d run it is if you changed a variable in /etc/default/grub. Grubby just creates new bootloaderspec files in /boot/loader. Also, I don’t believe grubby creates new initrd files, that’s handled by the kernel post install scripts. (Which also calls grubby). -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 all by itself. No further action was required by me. Jonathan Billings: > You should never need to run grub2-mkconfig after each kernel update. > The only reason I can guess at is that they ran it to overwrite the > file in /boot/efi/EFI/fedora/ (which is normally a stub that loads > the default file in /boot/grub2/) and now they have to manually run > it each time. > > Normally, the only reason you’d run it is if you changed a variable > in /etc/default/grub. Grubby just creates new bootloaderspec files in > /boot/loader. Somewhere along the line I removed "rhgb" from there, one way or another (*), I don't recall ever running grub2-mkconfig, and I've certainly never run it at every kernel update. * I don't recall which method I used to remove it from the kernel command line, but it's not in there, and my system is running fine. It's the one change I make to booting up Linux, I want to see that it's actually booting and not jammed. And if it has, I want to see where, straight away, no horsing around after the fact. Blank bootup screens are one of the dumbest things about certain other OSs that Linux has copied. -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Fedora 37 hangs after graphical login
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 account works, one user account (the empty one) also. But my usually working account freezes, after i login. If i login via terminal Ctrl-Alt-F3 it works. So i think that something is crashed during the load after graphical login. How could i See, what is going on after graphical login? The different steps and programs i mean. Any logfiles? I know that one of the first thing is loading gdm? Or am i wrong? Btw: i use wayland and GNOME. An update via dnf brings nothing. Hope someone does have an idea. Thanks Jens Hello I'm having the same with F36 and kernel 6.0.16-200.fc36.x86_64, going to previous (6.0.15-200.fc36.x86_64) works fine. Happens with and without Wayland, Gnome and MATE. Hope helps someone ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
> 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 do that), and it's always installed the new kernel >>> properly all by itself. No further action was required by me. > > > > Jonathan Billings: >> You should never need to run grub2-mkconfig after each kernel update. >> The only reason I can guess at is that they ran it to overwrite the >> file in /boot/efi/EFI/fedora/ (which is normally a stub that loads >> the default file in /boot/grub2/) and now they have to manually run >> it each time. >> >> Normally, the only reason you’d run it is if you changed a variable >> in /etc/default/grub. Grubby just creates new bootloaderspec files in >> /boot/loader. > > Somewhere along the line I removed "rhgb" from there, one way or > another (*), I don't recall ever running grub2-mkconfig, and I've > certainly never run it at every kernel update. > > * I don't recall which method I used to remove it from the kernel > command line, but it's not in there, and my system is running fine. > > It's the one change I make to booting up Linux, I want to see that it's > actually booting and not jammed. And if it has, I want to see where, > straight away, no horsing around after the fact. Blank bootup screens > are one of the dumbest things about certain other OSs that Linux has > copied. Like you i remove rhgb and also quiet so i can see what is happening. But I think it is fine to not do this by default. We experts can remove this with a grubby command is 2s and the none experts do not get to worry about the boot noise. Barry > > -- > > uname -rsvp > Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 > > Boilerplate: All unexpected mail to my mailbox is automatically deleted. > I will only get to see the messages that are posted to the mailing list. > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 something needing run. I am sure all this is in the boot logs anyway. B On 1/7/2023 5:55 PM, 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 specifically just do that), and it's always installed the new kernel properly all by itself. No further action was required by me. Jonathan Billings: You should never need to run grub2-mkconfig after each kernel update. The only reason I can guess at is that they ran it to overwrite the file in /boot/efi/EFI/fedora/ (which is normally a stub that loads the default file in /boot/grub2/) and now they have to manually run it each time. Normally, the only reason you’d run it is if you changed a variable in /etc/default/grub. Grubby just creates new bootloaderspec files in /boot/loader. Somewhere along the line I removed "rhgb" from there, one way or another (*), I don't recall ever running grub2-mkconfig, and I've certainly never run it at every kernel update. * I don't recall which method I used to remove it from the kernel command line, but it's not in there, and my system is running fine. It's the one change I make to booting up Linux, I want to see that it's actually booting and not jammed. And if it has, I want to see where, straight away, no horsing around after the fact. Blank bootup screens are one of the dumbest things about certain other OSs that Linux has copied. Like you i remove rhgb and also quiet so i can see what is happening. But I think it is fine to not do this by default. We experts can remove this with a grubby command is 2s and the none experts do not get to worry about the boot noise. Barry -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 this happens because dnf got interrupted for some reason. Watch the rerun and notice that there are 2 steps that take a long time, one of them puts the files in and the 2nd one builds and adds in initrd. Installing : kernel-core-6.0.16-300.fc37.x86_64 1/3 Running scriptlet: kernel-core-6.0.16-300.fc37.x86_64 1/3 Installing : kernel-modules-6.0.16-300.fc37.x86_64 2/3 Running scriptlet: kernel-modules-6.0.16-300.fc37.x86_64 2/3 Installing : kernel-6.0.16-300.fc37.x86_64 3/3 Running scriptlet: kernel-core-6.0.16-300.fc37.x86_64 3/3 The last running scriptlet builds the initrd and adds it to grub. It runs after all install/upgrades are done, and if dnf gets aborted you end up with kernel only. On Fri, Jan 6, 2023 at 9:37 PM Stephen Morris wrote: > Hi, > 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 not run > initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. > Is this a defect with grubby? > > regards, > Steve > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
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 issue with kernel
6.0.16.
regards,
Steve
Thanks. It's still the same for me after another dnf upgrade run.
Using KDE, it boots and continues for some time after password entry,
but then stays unresponsive. No light shows after Caps Lock key, and
no mouse pointer or action. 6.0.15 works.
/var/log/Xorg.0.log looks similar for both. For info, here's the end:
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): connected
[ 201.742] (--) NVIDIA(GPU-0): DELL 2009W (CRT-0): 400.0 MHz maximum
pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: disconnected
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: Internal TMDS
[ 201.742] (--) NVIDIA(GPU-0): DFP-0: 330.0 MHz maximum pixel clock
[ 201.742] (--) NVIDIA(GPU-0):
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): connected
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): Internal TMDS
[ 201.787] (--) NVIDIA(GPU-0): SONY TV (DFP-1): 340.0 MHz maximum
pixel clock
[ 201.787] (--) NVIDIA(GPU-0):
[ 217.638] (II) NVIDIA(0): Setting mode "HDMI-0: nvidia-auto-select
@1360x768 +0+0 {ViewPortIn=1360x768, ViewPortOut=1360x768+0+0}"
[ 217.739] (II) NVIDIA(0): Setting mode "NULL"
[ 217.783] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0}"
[ 217.825] (II) NVIDIA(0): Setting mode "VGA-0: nvidia-auto-select
@1680x1050 +0+30 {ViewPortIn=1680x1050, ViewPortOut=1680x1050+0+0},
HDMI-0: 1920x1080_50 @1920x1080 +1680+0 {ViewPortIn=1920x1080,
ViewPortOut=1920x1080+0+0}"
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 need for any specific
specifications. The only configuration file in xorg.conf.d is the one
for the keyboard.
regards,
Steve
John
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
[ 291.838] (--) Log file renamed from "/home/steve/.local/share/xorg/Xorg.pid-2449.log" to "/home/steve/.local/share/xorg/Xorg.0.log"
[ 291.838]
X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
[ 291.838] Build Operating System: 6.0.9-300.fc37.x86_64
[ 291.838] Current Operating System: Linux fedora 6.0.16-300.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Dec 31 16:47:53 UTC 2022 x86_64
[ 291.838] Kernel command line: BOOT_IMAGE=/vmlinuz-6.0.16-300.fc37.x86_64 root=UUID=d22cf9df-0b3c-413a-a82f-b623c56c9841 ro rootflags=subvol=Fedora_Root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1
[ 291.838] Build Date: 19 December 2022 12:00:00AM
[ 291.838] Build ID: xorg-x11-server 1.20.14-12.fc37
[ 291.838] Current version of pixman: 0.40.0
[ 291.838] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 291.838] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 291.838] (==) Log file: "/home/steve/.local/share/xorg/Xorg.0.log", Time: Sun Jan 8 09:07:59 2023
[ 291.842] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 291.842] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 291.849] (==) ServerLayout "layout"
[ 291.850] (==) No screen section available. Using defaults.
[ 291.850] (**) |-->Screen "Default Screen Section" (0)
[ 291.850] (**) | |-->Monitor ""
[ 291.850] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 291.850] (==) Automatically adding devices
[ 291.850] (==) Automatically enabling devices
[ 291.850] (==) Automatically adding GPU devices
[ 291.850] (==) Automatically binding GPU devices
[ 291.850] (==) Max clients allowed: 256, resource mask: 0x1f
[ 291.850] (==) FontPath set to:
catalogue:/etc/X11/fontpath.d,
built-ins
[ 291.850] (==) ModulePath set to "/usr/lib64/xorg/modules"
[ 291.850] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[
grubby --set-default LOLs at me
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 menu still highlights the most recently installed kernel, and that's what boots by default. pgpgNGkC0dz_d.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 not run initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. 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 all by itself. No further action was required by me. What are people doing to their systems that they paint themselves into a corner that they have to manually manage this, then have to pick up the pieces when it doesn't work? I have always run grub2-mkconfig both for legacy and uefi environments because in the past grubby did not honour the configuration I specified in /etc/default/grub. For example, I always specify that I want sub-menus for all linux environments and grubby always refused to do that, whereas grub2-mkconfig always did, hence I always used that. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 other kernels(likely the currently booting on), so if you have the right options on the other kernels then it will copy the right options. On Sat, Jan 7, 2023 at 7:43 PM Stephen Morris wrote: > 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 not run > >> initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. > > 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 all by itself. No further action was required by me. > > > > What are people doing to their systems that they paint themselves into > > a corner that they have to manually manage this, then have to pick up > > the pieces when it doesn't work? > > > I have always run grub2-mkconfig both for legacy and uefi environments > because in the past grubby did not honour the configuration I specified > in /etc/default/grub. For example, I always specify that I want > sub-menus for all linux environments and grubby always refused to do > that, whereas grub2-mkconfig always did, hence I always used that. > > regards, > Steve > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 /boot/grub2/grub.cfg presumably updated by grubby, it did not run initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. 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 all by itself. No further action was required by me. What are people doing to their systems that they paint themselves into a corner that they have to manually manage this, then have to pick up the pieces when it doesn't work? You should never need to run grub2-mkconfig after each kernel update. The only reason I can guess at is that they ran it to overwrite the file in /boot/efi/EFI/fedora/ (which is normally a stub that loads the default file in /boot/grub2/) and now they have to manually run it each time. Normally, the only reason you’d run it is if you changed a variable in /etc/default/grub. Grubby just creates new bootloaderspec files in /boot/loader. Also, I don’t believe grubby creates new initrd files, that’s handled by the kernel post install scripts. (Which also calls grubby). As I replied in the mail response to Tim's mail, traditionally grubby has not honoured all the settings in /etc/default/grub, particularly the sub-menu options, hence I've always run grub2-mkconfig to build /boot/grub2/grub.cfg, which from what I have read is what grub in F37 boots from (that documentation also recommended to not run grub2-mkconfig but I still do. I seem to also remember that grubby ignore the resolution settings as well. The resolution settings are a mute point as a result of the recent updates done to grub to resolve the font security hole in grub, as statements to set the boot resolution and the gfxterm are now ignore by the fixed logic). regards, Steve -- Jonathan Billings ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 the new kernel properly all by itself. No further action was required by me. Jonathan Billings: You should never need to run grub2-mkconfig after each kernel update. The only reason I can guess at is that they ran it to overwrite the file in /boot/efi/EFI/fedora/ (which is normally a stub that loads the default file in /boot/grub2/) and now they have to manually run it each time. Normally, the only reason you’d run it is if you changed a variable in /etc/default/grub. Grubby just creates new bootloaderspec files in /boot/loader. Somewhere along the line I removed "rhgb" from there, one way or another (*), I don't recall ever running grub2-mkconfig, and I've certainly never run it at every kernel update. * I don't recall which method I used to remove it from the kernel command line, but it's not in there, and my system is running fine. It's the one change I make to booting up Linux, I want to see that it's actually booting and not jammed. And if it has, I want to see where, straight away, no horsing around after the fact. Blank bootup screens are one of the dumbest things about certain other OSs that Linux has copied. One other reason for running grub2-mkconfig that I forgot to mention in my previous email is I also turn off the blscfg functionality in /etc/default/grub because it doesn't honour all of those settings either. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 specifically just do that), and it's always installed the new kernel properly all by itself. No further action was required by me. Jonathan Billings: You should never need to run grub2-mkconfig after each kernel update. The only reason I can guess at is that they ran it to overwrite the file in /boot/efi/EFI/fedora/ (which is normally a stub that loads the default file in /boot/grub2/) and now they have to manually run it each time. Normally, the only reason you’d run it is if you changed a variable in /etc/default/grub. Grubby just creates new bootloaderspec files in /boot/loader. Somewhere along the line I removed "rhgb" from there, one way or another (*), I don't recall ever running grub2-mkconfig, and I've certainly never run it at every kernel update. * I don't recall which method I used to remove it from the kernel command line, but it's not in there, and my system is running fine. It's the one change I make to booting up Linux, I want to see that it's actually booting and not jammed. And if it has, I want to see where, straight away, no horsing around after the fact. Blank bootup screens are one of the dumbest things about certain other OSs that Linux has copied. Like you i remove rhgb and also quiet so i can see what is happening. But I think it is fine to not do this by default. We experts can remove this with a grubby command is 2s and the none experts do not get to worry about the boot noise. 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. regards, Steve Barry -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
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 need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 installs copy the options from one of the other kernels(likely the currently booting on), so if you have the right options on the other kernels then it will copy the right options. I have always wanted the kernel entries for Fedora and Ubuntu in sub-menus and the current kernel in the main menu. Traditionally grubby has always rewritten the grub menus to undo that functionality, hence I have always run grub2-mkconfig, plus I turn off blscfg as it has the same issues as grubby has done. I will continually run grub2-mkconfig until such time as the other facilities do things the way I want. regards, Steve On Sat, Jan 7, 2023 at 7:43 PM Stephen Morris wrote: 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 not run >> initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. > 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 all by itself. No further action was required by me. > > What are people doing to their systems that they paint themselves into > a corner that they have to manually manage this, then have to pick up > the pieces when it doesn't work? > I have always run grub2-mkconfig both for legacy and uefi environments because in the past grubby did not honour the configuration I specified in /etc/default/grub. For example, I always specify that I want sub-menus for all linux environments and grubby always refused to do that, whereas grub2-mkconfig always did, hence I always used that. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-le...@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: grubby --set-default LOLs at me
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) you will find massively unintelligible scripts implementing impossible to decode logic to decide all kinds of things, including the default kernel. It is possible the actual default is determined by grub environment file setting. I gave up trying to figure out how to get the scripts to do what I wanted in an official fashion and just have a script that runs after dnf to fix any stuff I don't want in the grub.cfg file. https://tomhorsley.com/game/Mjolnir.html ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 reinstall kernel" and that fixes it. Usually this happens because dnf got interrupted for some reason. Watch the rerun and notice that there are 2 steps that take a long time, one of them puts the files in and the 2nd one builds and adds in initrd. Installing : kernel-core-6.0.16-300.fc37.x86_64 1/3 Running scriptlet: kernel-core-6.0.16-300.fc37.x86_64 1/3 Installing : kernel-modules-6.0.16-300.fc37.x86_64 2/3 Running scriptlet: kernel-modules-6.0.16-300.fc37.x86_64 2/3 Installing : kernel-6.0.16-300.fc37.x86_64 3/3 Running scriptlet: kernel-core-6.0.16-300.fc37.x86_64 3/3 The last running scriptlet builds the initrd and adds it to grub. It runs after all install/upgrades are done, and if dnf gets aborted you end up with kernel only. That's interesting, my recent experience with grubby when I have forgotten to run grub2-mkconfig is that it has never added to initrd command into the grub menus to load the initrd image at boot time even though the image has already been built as part of the dnf kernel install processes. regards, Steve On Fri, Jan 6, 2023 at 9:37 PM Stephen Morris wrote: Hi, 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 not run initrd, the grub.cfg file generated by grub2-mkconfig does run initrd. Is this a defect with grubby? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list --users@lists.fedoraproject.org To unsubscribe send an email tousers-le...@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it:https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Black screens with rpmfusion nvidia 470xx and 6.0.16.fc36
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 resolution I run with without the need for any specific specifications. The only configuration file in xorg.conf.d is the one for the keyboard. By default, Xorg doesn't run as root any more, so it can only write logs to the user directory. I only included that specification for where my Xorg.0.log file is located because John was indicating that his Xorg.0.log is being written to /var/log. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: grubby --set-default LOLs at me
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 live in /etc/grub.d) you will find massively unintelligible scripts implementing impossible to decode logic to decide all kinds of things, including the default kernel. --set-default does not update grub.cfg. The default kernel setting is … somewhere. I distinctly recall there was an entry in /etc/default/grub that specified it. It's not there any more. It is possible the actual default is determined by grub environment file setting. Well, yes. After some random poking: grub2-editenv list This shows the default kernel boot that grubby sets. Except that it has absolutely no effect whatsoever. I see that grubby updates this. But grub, when it boots, completely ignores the default entry that's shown here. I gave up trying to figure out how to get the scripts to do what I wanted in an official fashion and just have a script that runs after dnf to fix any stuff I don't want in the grub.cfg file. This has all the telltale signs of grub's default boot kernel setting name's getting renamed or changed, but grubby was not updated, accordingly, so it thinks it's setting the default boot kernel, but grub doesn't read it. The environment file, /boot/grub2/grubenv, is just a generic name=value store, that you can toss any random names and values in there, from the looks of it. While I was typing this out I remembered that the actual bootloader gets installed by grub-install. Perhaps grub and grubby were updated, but grub- install did not ran. And after a "/sbin/grub-install /dev/sda", the default boot kernel setting, made by grubby, started working. Another Scooby-Doo mystery solved… pgpKgwM95rRbc.pgp Description: PGP signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 config.run "dnf reinstall > kernel" and that fixes it. Usually this happens because dnf got > interrupted for some reason. > > Watch the rerun and notice that there are 2 steps that take a long > time, one of them puts the files in and the 2nd one builds and adds > in initrd. > > Installing : kernel-core-6.0.16-300.fc37.x86_64 > > > 1/3 > Running scriptlet: kernel-core-6.0.16-300.fc37.x86_64 > > > 1/3 > Installing : kernel-modules-6.0.16-300.fc37.x86_64 > > >2/3 > Running scriptlet: kernel-modules-6.0.16-300.fc37.x86_64 > > >2/3 > Installing : kernel-6.0.16-300.fc37.x86_64 > > >3/3 > Running scriptlet: kernel-core-6.0.16-300.fc37.x86_64 > > > 3/3 > > The last running scriptlet builds the initrd and adds it to grub. > It runs after all install/upgrades are done, and if dnf gets aborted > you end up with kernel only. I wonder how many people are affected by that because they don't run update in the command line and watch the process, but have a system that does the updates at shutdown, or hidden by a GUI, and they don't wait for it to actually finish, but just assume it does after a period of apparent inactivity, and switch off or reset the PC? -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grubby? Doesn't Load Initrd
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 (the boot sequence isn't sequential any more). You need to see things as they happen, not a freeze-frame afterwards. And there's every chance that the PC won't respond to the keyboard, too. -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: grubby --set-default LOLs at me
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 > the default boot kernel is what I specified. > > But at boot the grub menu still highlights the most recently installed > kernel, and that's what boots by default. > As I recall, there was always several aspects to this. Each menu stanza for the particular kernel you booted needed to have a "set default" option set in it. So that when you picked that menu option at boot time, it set the default variable to itself *and* *then* booted that kernel. If you booted from a menu choice that didn't include that option, it wouldn't set itself as the default for the next boot. It was a per-stanza thing, not a once in the GRUB config, thing. And at boot/reboot, GRUB had to be configured to read the default variable to see which menu item to boot. I lack the perseverance to read through the conglomeration of GRUB menu files to see what it does these days. -- uname -rsvp Linux 3.10.0-1160.81.1.el7.x86_64 #1 SMP Fri Dec 16 17:29:43 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: grubby --set-default LOLs at me
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 to build the grub.cfg (I think they may live in /etc/grub.d) you will find massively unintelligible scripts implementing impossible to decode logic to decide all kinds of things, including the default kernel. --set-default does not update grub.cfg. The default kernel setting is …somewhere. I distinctly recall there was an entry in /etc/default/grub that specified it. It's not there any more. It is possible the actual default is determined by grub environment file setting. Well, yes. After some random poking: grub2-editenv list This shows the default kernel boot that grubby sets. Except that it has absolutely no effect whatsoever. I see that grubby updates this. But grub, when it boots, completely ignores the default entry that's shown here. I gave up trying to figure out how to get the scripts to do what I wanted in an official fashion and just have a script that runs after dnf to fix any stuff I don't want in the grub.cfg file. This has all the telltale signs of grub's default boot kernel setting name's getting renamed or changed, but grubby was not updated, accordingly, so it thinks it's setting the default boot kernel, but grub doesn't read it. The environment file, /boot/grub2/grubenv, is just a generic name=value store, that you can toss any random names and values in there, from the looks of it. While I was typing this out I remembered that the actual bootloader gets installed by grub-install. Perhaps grub and grubby were updated, but grub-install did not ran. And after a "/sbin/grub-install /dev/sda", the default boot kernel setting, made by grubby, started working. Another Scooby-Doo mystery solved… The current grub install command is grub2-install, but that is only run for legacy boot environments, it is never used for uefi boots. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: grubby --set-default LOLs at me
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 --info=DEFAULT shows that the default boot kernel is what I specified. But at boot the grub menu still highlights the most recently installed kernel, and that's what boots by default. As I recall, there was always several aspects to this. Each menu stanza for the particular kernel you booted needed to have a "set default" option set in it. So that when you picked that menu option at boot time, it set the default variable to itself *and* *then* booted that kernel. If you booted from a menu choice that didn't include that option, it wouldn't set itself as the default for the next boot. It was a per-stanza thing, not a once in the GRUB config, thing. And at boot/reboot, GRUB had to be configured to read the default variable to see which menu item to boot. I lack the perseverance to read through the conglomeration of GRUB menu files to see what it does these days. From a google check for the default grub kernel boots it seems that if you add the following two statements into /etc/default/grub and then run grub2-mkconfig grub will use the last selected kernel as the default boot kernel. |GRUB_SAVEDEFAULT=true GRUB_DEFAULT=saved| regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
