Re: How do I change the grub kernel boot parameters in F32 ?

[Roberto Ragusa]

On 2020-06-19 09:33, Stephen Morris wrote:


My issue with BLS is the way it displays the kernel menu entries in grub, it is 
exactly the same as the way grubby showed the entries which I also hated, 
consequently I refuse to use BLS until such time as they provide an option to 
get the menus displayed as an entry for the current kernel and an expandable 
menu for all other kernels and the recovery entries.



You are lucky to see kernel versions because in my case I just have

Fedora 32 (Thirty Two)
Fedora 32 (Thirty Two)
Fedora 32 (Thirty Two)
Fedora Memtest memtest86+-5.01

I've tried debugging that a bit and the scripts are just taking the PRETTY_NAME
var from /etc/os-release.

This is on BLS, without EFI.

Regards.
--
   Roberto Ragusamail at robertoragusa.it
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Fri, Jun 19, 2020 Stephen Morris  wrote:
> On 17/6/20 1:52 am, Tom H wrote:
>> On Tue, Jun 16, 2020 Stephen Morris  wrote:
>>>
>>> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
>>> how does one disable BLS if we don't want it?
>>
>> You MAY be right in assuming that Fedora might choose only to
>> support BLS.
>>
>> If that day comes, we'll use BLS. I hope that, by then, we'll have
>> a way to customize the snippets, for example, not to use the
>> machine-id UUIDs.
>
> My issue with BLS is the way it displays the kernel menu entries in
> grub, it is exactly the same as the way grubby showed the entries
> which I also hated, consequently I refuse to use BLS until such time
> as they provide an option to get the menus displayed as an entry for
> the current kernel and an expandable menu for all other kernels and
> the recovery entries.

I agree that the default menu entries are pretty weird.

I only have two Fedora BIOS VMs where the BLS snippets are created by
"/usr/lib/kernel/install.d/20-grub.install".

I've edited the 20-... script to create the file name and the menu
entry that I want. It's not a "%config" or "%config(noreplace)" file,
so it'll be overwritten on "grub2-common" upgrades.

I overwrite the snippet for the running kernel with:

KERNEL_INSTALL_MACHINE_ID=$(cat /etc/machine-id)
/usr/lib/kernel/install.d/20-grub.install add $(uname -r)
/boot/${KERNEL_INSTALL_MACHINE_ID}/$(uname -r) /lib/modules/$(uname
-r)/vmlinuz
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 20/6/20 7:25 am, Jonathan Billings wrote:


On Jun 19, 2020, at 03:34, Stephen Morris  
wrote:


My issue with BLS is the way it displays the kernel menu entries in 
grub, it is exactly the same as the way grubby showed the entries 
which I also hated, consequently I refuse to use BLS until such time 
as they provide an option to get the menus displayed as an entry for 
the current kernel and an expandable menu for all other kernels and 
the recovery entries.



Do you mean something like changing:

GRUB_DISABLE_SUBMENU=true
*
*
*... to ...*
*
*
GRUB_DISABLE_SUBMENU=false

... in your /etc/default/grub?
I have always had GRUB_DISABLE_SUBMENU=false, but grubby and BLS have 
always ignored it whereas grub2-mkconfig has always honoured it.


regards,
Steve



(and of course regenerate the grub.cfg)

--
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


___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Jonathan Billings]

On Jun 19, 2020, at 03:34, Stephen Morris  wrote:
> 
> My issue with BLS is the way it displays the kernel menu entries in grub, it 
> is exactly the same as the way grubby showed the entries which I also hated, 
> consequently I refuse to use BLS until such time as they provide an option to 
> get the menus displayed as an entry for the current kernel and an expandable 
> menu for all other kernels and the recovery entries.


Do you mean something like changing:

GRUB_DISABLE_SUBMENU=true

... to ...

GRUB_DISABLE_SUBMENU=false

... in your /etc/default/grub?

(and of course regenerate the grub.cfg)

--
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 17/6/20 1:52 am, Tom H wrote:

On Tue, Jun 16, 2020 Stephen Morris  wrote:

On 16/6/20 9:06 am, Ed Greshko wrote:

On 2020-06-16 07:01, Tom H wrote:

The kernel options are in the BLS entries, so it doesn't matter
what you have in grubenv.

 From the grub2 changelog on may 13th:

Store cmdline in BLS snippets instead of using a grubenv variable

The kernel cmdline was stored as a kernelopts variable in the
grubenv file and the BLS snippets used that. But this turned out to
be fragile since the grubenv file could be removed or get corrupted
easily.

To prevent the entries to not have a cmdline if the grubenv can't
be read, a fallback variable was set in the GRUB config file. But
this still caused issues since the config needs to be re-generated
to change the parameters.

Instead, let's store the cmdline in the BLS snippets. This will
make the configuration more robust, since it will work even without
the grubenv file and the BLS entries will contain all the
information needed to boot.

Thanks for that.

Just to complete my understanding, by the BLS snippets you mean the

/boot/loader/entries/*.conf

files?

If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how
does one disable BLS if we don't want it?

You MAY be right in assuming that Fedora might choose only to support BLS.

If that day comes, we'll use BLS. I hope that, by then, we'll have a
way to customize the snippets, for example, not to use the machine-id
UUIDs.
My issue with BLS is the way it displays the kernel menu entries in 
grub, it is exactly the same as the way grubby showed the entries which 
I also hated, consequently I refuse to use BLS until such time as they 
provide an option to get the menus displayed as an entry for the current 
kernel and an expandable menu for all other kernels and the recovery 
entries.


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

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Wed, Jun 17, 2020 at 12:10 PM George N. White III  wrote:
> On Tue, 16 Jun 2020 at 13:38, Tom H  wrote:
>> On Tue, Jun 16, 2020 at 1:50 PM Ed Greshko  wrote:
>>> On 2020-06-16 19:42, Stephen Morris wrote:


 If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
 how does one disable BLS if we don't want it?
>>>
>>> If that should happen then one needs to learn how to work with BLS.
>>> Legacy methods aren't supported forever. Just like we don't have
>>> System V init scripts.
>>
>> LOL. I don't think that you can call the grub config that every
>> distribution other than Fedora and RHEL uses "legacy." I wonder
>> whether BLSCFG's been upstreamed.
>
> BLS seems to be tied to UEFI, so the old grub config will last as
> long as distros still boot with BIOS.

I'm using BLSCFG with BIOS for a Fedora VM.


> Other distributions do use BLS: debian testing, ubuntu focal fossa
> (20.04)

You've misunderstood. No one else is using BLS with grub.

In Debian and Ubuntu (and not just in "testing" and 20.04), you can
use systemd-boot. But there aren't any scripts to install it on the
ESP, to set up a firmware entry, or to create or update the files in
"/boot/loader/entries/*".
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[George N. White III]

On Tue, 16 Jun 2020 at 13:38, Tom H  wrote:

> On Tue, Jun 16, 2020 at 1:50 PM Ed Greshko  wrote:
> > On 2020-06-16 19:42, Stephen Morris wrote:
> >>
> >> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
> >> how does one disable BLS if we don't want it?
> >
> > If that should happen then one needs to learn how to work with BLS.
> > Legacy methods aren't supported forever. Just like we don't have
> > System V init scripts.
>
> LOL. I don't think that you can call the grub config that every
> distribution other than Fedora and RHEL uses "legacy." I wonder
> whether BLSCFG's been upstreamed.
>

BLS seems to be tied to UEFI, so the old grub config will last as long
as distros still boot with BIOS.   Other distributions do use BLS:
debian testing
, ubuntu
focal fossa (20.04)


https://systemd.io/BOOT_LOADER_SPECIFICATION/ wants to infest not
only linux, but other open-source operating systems.   It seems one of the
main reasons for BLS is to avoid conflicts in /boot when two different
linux
distros are installed.

The specification lives at
https://freedesktop.org/wiki/Specifications/BootLoaderSpec/



-- 
George N. White III
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Ed Greshko]

On 2020-06-17 00:38, Tom H wrote:
> On Tue, Jun 16, 2020 at 1:50 PM Ed Greshko  wrote:
>> On 2020-06-16 19:42, Stephen Morris wrote:
>>> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
>>> how does one disable BLS if we don't want it?
>> If that should happen then one needs to learn how to work with BLS.
>> Legacy methods aren't supported forever. Just like we don't have
>> System V init scripts.
> LOL. I don't think that you can call the grub config that every
> distribution other than Fedora and RHEL uses "legacy." I wonder
> whether BLSCFG's been upstreamed.

Well, I do think that if a given distribution has decided to no longer support 
a feature it
can be call "legacy" within that distribution. 

What was the arc of systemd?

Oh, and it seems, BLS is an outgrowth of systemd?   
https://systemd.io/BOOT_LOADER_SPECIFICATION/

-- 
The key to getting good answers is to ask good questions.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Tue, Jun 16, 2020 at 1:50 PM Ed Greshko  wrote:
> On 2020-06-16 19:42, Stephen Morris wrote:
>>
>> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore,
>> how does one disable BLS if we don't want it?
>
> If that should happen then one needs to learn how to work with BLS.
> Legacy methods aren't supported forever. Just like we don't have
> System V init scripts.

LOL. I don't think that you can call the grub config that every
distribution other than Fedora and RHEL uses "legacy." I wonder
whether BLSCFG's been upstreamed.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Tue, Jun 16, 2020 Stephen Morris  wrote:
> On 16/6/20 9:06 am, Ed Greshko wrote:
>> On 2020-06-16 07:01, Tom H wrote:
>>>
>>> The kernel options are in the BLS entries, so it doesn't matter
>>> what you have in grubenv.
>>>
>>> From the grub2 changelog on may 13th:
>>>
>>> Store cmdline in BLS snippets instead of using a grubenv variable
>>>
>>> The kernel cmdline was stored as a kernelopts variable in the
>>> grubenv file and the BLS snippets used that. But this turned out to
>>> be fragile since the grubenv file could be removed or get corrupted
>>> easily.
>>>
>>> To prevent the entries to not have a cmdline if the grubenv can't
>>> be read, a fallback variable was set in the GRUB config file. But
>>> this still caused issues since the config needs to be re-generated
>>> to change the parameters.
>>>
>>> Instead, let's store the cmdline in the BLS snippets. This will
>>> make the configuration more robust, since it will work even without
>>> the grubenv file and the BLS entries will contain all the
>>> information needed to boot.
>>
>> Thanks for that.
>>
>> Just to complete my understanding, by the BLS snippets you mean the
>>
>> /boot/loader/entries/*.conf
>>
>> files?
>
> If GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how
> does one disable BLS if we don't want it?

You MAY be right in assuming that Fedora might choose only to support BLS.

If that day comes, we'll use BLS. I hope that, by then, we'll have a
way to customize the snippets, for example, not to use the machine-id
UUIDs.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Ed Greshko]

On 2020-06-16 19:42, Stephen Morris wrote:
> If
>
> GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how does one 
> disable BLS if we don't want it? 

If that should happen then one needs to learn how to work with BLS.  Legacy 
methods aren't supported
forever.  Just like we don't have System V init scripts.

-- 
The key to getting good answers is to ask good questions.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 16/6/20 9:06 am, Ed Greshko wrote:

On 2020-06-16 07:01, Tom H wrote:

The kernel options are in the BLS entries, so it doesn't matter what
you have in grubenv.

 From the grub2 changelog on may 13th:

Store cmdline in BLS snippets instead of using a grubenv variable

The kernel cmdline was stored as a kernelopts variable in the grubenv
file and the BLS snippets used that. But this turned out to be fragile
since the grubenv file could be removed or get corrupted easily.

To prevent the entries to not have a cmdline if the grubenv can't be
read, a fallback variable was set in the GRUB config file. But this
still caused issues since the config needs to be re-generated to change
the parameters.

Instead, let's store the cmdline in the BLS snippets. This will make
the configuration more robust, since it will work even without the
grubenv file and the BLS entries will contain all the information
needed to boot.

Thanks for that.

Just to complete my understanding, by the BLS snippets you mean the

/boot/loader/entries/*.conf

files?

Hi Ed,
    If

GRUB_ENABLE_BLSCFG=false is not going to be supported anymore, how does one 
disable BLS if we don't want it?

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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Tue, Jun 16, 2020 Ed Greshko  wrote:
> On 2020-06-16 07:01, Tom H wrote:
>>
>> The kernel options are in the BLS entries, so it doesn't matter what
>> you have in grubenv.
>>
>> From the grub2 changelog on may 13th:
>>
>> Store cmdline in BLS snippets instead of using a grubenv variable
>>
>> The kernel cmdline was stored as a kernelopts variable in the
>> grubenv file and the BLS snippets used that. But this turned out to
>> be fragile since the grubenv file could be removed or get corrupted
>> easily.
>>
>> To prevent the entries to not have a cmdline if the grubenv can't be
>> read, a fallback variable was set in the GRUB config file. But this
>> still caused issues since the config needs to be re-generated to
>> change the parameters.
>>
>> Instead, let's store the cmdline in the BLS snippets. This will make
>> the configuration more robust, since it will work even without the
>> grubenv file and the BLS entries will contain all the information
>> needed to boot.
>
> Thanks for that.

You're welcome.


> Just to complete my understanding, by the BLS snippets you mean the
>
> /boot/loader/entries/*.conf
>
> files?

Yes.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Ed Greshko]

On 2020-06-16 07:01, Tom H wrote:
> The kernel options are in the BLS entries, so it doesn't matter what
> you have in grubenv.
>
> From the grub2 changelog on may 13th:
>
> Store cmdline in BLS snippets instead of using a grubenv variable
>
> The kernel cmdline was stored as a kernelopts variable in the grubenv
> file and the BLS snippets used that. But this turned out to be fragile
> since the grubenv file could be removed or get corrupted easily.
>
> To prevent the entries to not have a cmdline if the grubenv can't be
> read, a fallback variable was set in the GRUB config file. But this
> still caused issues since the config needs to be re-generated to change
> the parameters.
>
> Instead, let's store the cmdline in the BLS snippets. This will make
> the configuration more robust, since it will work even without the
> grubenv file and the BLS entries will contain all the information
> needed to boot.

Thanks for that.

Just to complete my understanding, by the BLS snippets you mean the

/boot/loader/entries/*.conf

files?

-- 
The key to getting good answers is to ask good questions.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Tue, Jun 16, 2020 at 12:08 AM Ed Greshko  wrote:
> On 2020-06-15 21:15, Tom H wrote:


>> Hope you'll be well soon!
>
> Thanks. I know I'll be happier after the stitches come out.

Hope so :)


>> Heads-up: On Rawhide, and therefore on F33 when it's released,
>> BLSCFG no longer uses "/boot/grub2/grubenv" for kernel options.
>
> I don't quite know what you mean.
>
> On my Rawhide system /boot/grub2/grubenv is a link to
> ../efi/EFI/fedora/grubenv.
>
> [root@frk fedora]# pwd
> /boot/efi/EFI/fedora
>
> [root@frk fedora]# date
> Tue 16 Jun 2020 06:05:05 AM CST
>
> [root@frk fedora]# ll grubenv
> -rw---. 1 root root 1024 Jun 15 21:35 grubenv
>
> [root@frk fedora]# grub2-editenv - set
> "kernelopts=root=/dev/mapper/fedora_frk-root ro
> resume=/dev/mapper/fedora_frk-swap rd.lvm.lv=fedora_frk/root
> rd.lvm.lv=fedora_frk/swap rhgb quiet"
>
> [root@frk fedora]# ll grubenv
> -rw---. 1 root root 1024 Jun 16 06:05 grubenv
>
> [root@frk fedora]# grep quiet grubenv
> kernelopts=root=/dev/mapper/fedora_frk-root ro
> resume=/dev/mapper/fedora_frk-swap rd.lvm.lv=fedora_frk/root
> rd.lvm.lv=fedora_frk/swap rhgb quiet
>
> So, what are the changes you are referring to?

The kernel options are in the BLS entries, so it doesn't matter what
you have in grubenv.

From the grub2 changelog on may 13th:

Store cmdline in BLS snippets instead of using a grubenv variable

The kernel cmdline was stored as a kernelopts variable in the grubenv
file and the BLS snippets used that. But this turned out to be fragile
since the grubenv file could be removed or get corrupted easily.

To prevent the entries to not have a cmdline if the grubenv can't be
read, a fallback variable was set in the GRUB config file. But this
still caused issues since the config needs to be re-generated to change
the parameters.

Instead, let's store the cmdline in the BLS snippets. This will make
the configuration more robust, since it will work even without the
grubenv file and the BLS entries will contain all the information
needed to boot.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Ed Greshko]

On 2020-06-15 21:15, Tom H wrote:
> Hope you'll be well soon!

Thanks.  I know I'll be happier after the stitches come out.

> Heads-up: On Rawhide, and therefore on F33 when it's released, BLSCFG
> no longer uses "/boot/grub2/grubenv" for kernel options.

I don't quite know what you mean.

On my Rawhide system /boot/grub2/grubenv is a link to ../efi/EFI/fedora/grubenv.

[root@frk fedora]# pwd
/boot/efi/EFI/fedora

[root@frk fedora]# date
Tue 16 Jun 2020 06:05:05 AM CST

[root@frk fedora]# ll grubenv
-rw---. 1 root root 1024 Jun 15 21:35 grubenv

[root@frk fedora]# grub2-editenv - set 
"kernelopts=root=/dev/mapper/fedora_frk-root ro 
resume=/dev/mapper/fedora_frk-swap rd.lvm.lv=fedora_frk/root 
rd.lvm.lv=fedora_frk/swap rhgb quiet"

[root@frk fedora]# ll grubenv
-rw---. 1 root root 1024 Jun 16 06:05 grubenv

[root@frk fedora]# grep quiet grubenv
kernelopts=root=/dev/mapper/fedora_frk-root ro 
resume=/dev/mapper/fedora_frk-swap rd.lvm.lv=fedora_frk/root 
rd.lvm.lv=fedora_frk/swap rhgb quiet

So, what are the changes you are referring to?

-- 
The key to getting good answers is to ask good questions.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Mon, Jun 15, 2020 Philip Rhoades  wrote:
> On 2020-06-15 19:05, Ed Greshko wrote:
>> On 2020-06-11 05:41, R. G. Newbury wrote:
>>> On 2020-06-09 Stephen Morris wrote:

 if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
 that inserts a line into the grub processes to use the new BLS
 standard, in which case grub2-mkconfig and possibly grubby do
 nothing until that entry is set to false. I have always use
 grub2-mkconfig because I have never liked what grubby generated,
 and what BLS generates appears to be the same as what grubby does,
 and I found that I had to set that entry to false for
 grub2-mkconfig to continue to work.
>>>
>>> THANKS FOR THAT, Steve!
>>>
>>> I could not get grub2-mkconfig to actually change the grub.cfg
>>> file. Now I know why ( but not why such a dangerously
>>> misdescriptive switch would be hidden away in a default file). In
>>> the past I would just edit the damn file,
>
> Hear, hear! Why did things have to get so obscure and complicated?

1) You can still edit one file. Simply "chmod -x" everything except
"40_custom", then write your own "grub.cfg" within it, and run
"grub2-mkconfig".

2) I suspect that grub2's mkconfig was inspired by Debian's grub1 update-grub.

With grub1/grub-legacy on Debian, there was a section in "menu.lst"
called "AUTOMAGIC" in which you set some options, for example

groot=(hdX,Y)
kopt=root=UUID= ro
altoptions=(single) single
altoptions=(emergency) emergency

and you'd end up with the following at the end of the "AUTOMAGIC"
section after running "update-grub"

title  Debian 5.7.2
root   (hdX,Y)
kernel /boot/vmlinuz-5.7.2 root=UUID= ro
initrd /boot/initrd.img-5.7.2

title  Debian 5.7.2 (single)
root   (hdX,Y)
kernel /boot/vmlinuz-5.7.2 root=UUID= ro single
initrd /boot/initrd.img-5.7.2

title  Debian 5.7.2 (emergency)
root   (hdX,Y)
kernel /boot/vmlinuz-5.7.2 root=UUID= ro emergency
initrd /boot/initrd.img-5.7.2

There were probably a few other options that you could set, but I've
forgotten...

But grub2's more complex thangrub1, and the grub2 developers must've
wanted to massage the config file a bit more than above, so we've
ended up with lines and lines of scripts.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Mon, Jun 15, 2020 at 11:05 AM Ed Greshko  wrote:
> On 2020-06-11 05:41, R. G. Newbury wrote:
>> On 2020-06-09 8:11 p.m.Stephen Morris wrote:


>>> if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
>>> that inserts a line into the grub processes to use the new BLS
>>> standard, in which case grub2-mkconfig and possibly grubby do
>>> nothing until that entry is set to false. I have always use
>>> grub2-mkconfig because I have never liked what grubby generated,
>>> and what BLS generates appears to be the same as what grubby does,
>>> and I found that I had to set that entry to false for
>>> grub2-mkconfig to continue to work.
>>
>> THANKS FOR THAT, Steve!
>>
>> I could not get grub2-mkconfig to actually change the grub.cfg file.
>> Now I know why ( but not why such a dangerously misdescriptive
>> switch would be hidden away in a default file). In the past I would
>> just edit the damn file, but the new motherboard uses EFI, and such
>> hands-on fixing might lead to an undesired result!
>
> I know I'm "late to the party". Laid up in hospital for the past week
> and previous message in this thread have been "expired".

Hope you'll be well soon!


> I've just used the grub2-editenv command which is new with the BLS
> standard. My understanding is that at some point using
> GRUB_ENABLE_BLSCFG=false may no longer be an option.
>
> So, using my system as an example, I just do below to do a change.
>
> grub2-editenv - set
> "kernelopts=root=UUID=4455f2e9-fed2-4e1e-856d-642b531547f9 ro
> rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"
>
> Of course I normally first do
>
> grub2-editenv list to get the current settings.

Heads-up: On Rawhide, and therefore on F33 when it's released, BLSCFG
no longer uses "/boot/grub2/grubenv" for kernel options.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Philip Rhoades]

Stephen,


On 2020-06-15 19:05, Ed Greshko wrote:

On 2020-06-11 05:41, R. G. Newbury wrote:

On 2020-06-09 8:11 p.m.Stephen Morris wrote

if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
that inserts a line into the grub processes to use the new BLS 
standard,=20
in which case grub2-mkconfig and possibly grubby do nothing until 
that=20
entry is set to false. I have always use grub2-mkconfig because I 
have=20
never liked what grubby generated, and what BLS generates appears to 
be=20
the same as what grubby does, and I found that I had to set that 
entry=20

to false for grub2-mkconfig to continue to work.


THANKS FOR THAT, Steve!

I could not get grub2-mkconfig to actually change the grub.cfg file. 
Now I know why ( but not why such a dangerously misdescriptive switch 
would be hidden away in a default file).

In the past I would just edit the damn file,



Hear, hear!  Why did things have to get so obscure and complicated?

Phil.
--
Philip Rhoades

PO Box 896
Cowra  NSW  2794
Australia
E-mail:  p...@pricom.com.au
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Ed Greshko]

On 2020-06-11 05:41, R. G. Newbury wrote:
> On 2020-06-09 8:11 p.m.Stephen Morris wrote
>> if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
>> that inserts a line into the grub processes to use the new BLS standard,=20
>> in which case grub2-mkconfig and possibly grubby do nothing until that=20
>> entry is set to false. I have always use grub2-mkconfig because I have=20
>> never liked what grubby generated, and what BLS generates appears to be=20
>> the same as what grubby does, and I found that I had to set that entry=20
>> to false for grub2-mkconfig to continue to work.
>
> THANKS FOR THAT, Steve!
>
> I could not get grub2-mkconfig to actually change the grub.cfg file. Now I 
> know why ( but not why such a dangerously misdescriptive switch would be 
> hidden away in a default file).
> In the past I would just edit the damn file, but the new motherboard uses 
> EFI, and such hands-on fixing might lead to an undesired result!
>

I know I'm "late to the party".  Laid up in hospital for the past week and 
previous message in this
thread have been "expired".

I've just used the grub2-editenv command which is new with the BLS standard.  
My understanding
is that at some point using GRUB_ENABLE_BLSCFG=false may no longer be an option.

So, using my system as an example, I just do below to do a change.

grub2-editenv - set "kernelopts=root=UUID=4455f2e9-fed2-4e1e-856d-642b531547f9 
ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau"

Of course I normally first do

grub2-editenv list to get the current settings.




-- 
The key to getting good answers is to ask good questions.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Mon, Jun 15, 2020 at 6:29 AM Tim via users
 wrote:
> On Sun, 2020-06-14 at 19:15 +0200, Tom H wrote:
>>
>> These regular more or less long threads on "grub.cfg" should be the
>> signal that Fedora's setting up grub incorrectly on EFI and should
>> adopt the Ubuntu setup with two config files:
>>
>> 1) /boot/efi/EFI/fedora/grub.cfg : generated by grub2-install and
>> solely there to set "prefix" to "(hdX,gptY)/boot/grub"
>>
>> 2) /boot/grub2/grub.cfg : generated by "grub2-mkconfig" just like
>> BIOS systems
>
> I have to wonder whether it really needs two files, can't GRUB just
> use one file?  Surely the choice of drive, kernel, and parameters,
> would be the same whether ye olde BIOS or UEFI?

To be clear. On Fedora, you only need two files.

You need two files on Ubuntu because the firmware only understands
FAT, so you need a "grub.cfg" along the grub executable on the EFI
partition that points to the "real" config firectory and file.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tim via users]

On Sun, 2020-06-14 at 19:15 +0200, Tom H wrote:
> These regular more or less long threads on "grub.cfg" should be the
> signal that Fedora's setting up grub incorrectly on EFI and should
> adopt the Ubuntu setup with two config files:
> 
> 1) /boot/efi/EFI/fedora/grub.cfg : generated by grub2-install and
> solely there to set "prefix" to "(hdX,gptY)/boot/grub"
> 
> 2) /boot/grub2/grub.cfg : generated by "grub2-mkconfig" just like
> BIOS systems

I have to wonder whether it really needs two files, can't GRUB just use
one file?  Surely the choice of drive, kernel, and parameters, would be
the same whether ye olde BIOS or UEFI?
 
-- 
 
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tom H]

On Sat, Jun 13, 2020 Stephen Morris  wrote:
> On 11/6/20 7:41 am, R. G. Newbury wrote:
>> On 2020-06-09 Stephen Morris wrote:
>>>
>>> if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
>>> that inserts a line into the grub processes to use the new BLS
>>> standard, in which case grub2-mkconfig and possibly grubby do
>>> nothing until that entry is set to false. I have always use
>>> grub2-mkconfig because I have never liked what grubby generated,
>>> and what BLS generates appears to be the same as what grubby does,
>>> and I found that I had to set that entry to false for
>>> grub2-mkconfig to continue to work.
>>
>> THANKS FOR THAT, Steve!
>>
>> I could not get grub2-mkconfig to actually change the grub.cfg file.
>> Now I know why ( but not why such a dangerously misdescriptive
>> switch would be hidden away in a default file). In the past I would
>> just edit the damn file, but the new motherboard uses EFI, and such
>> hands-on fixing might lead to an undesired result!
>
> If you are booting via uefi with fedora then if you use grub2-mkconfig
> to update grub.cfg then you need to run it against
> /boot/efi/EFI/fedora/grub.cfg as that is where uefi looks for it,
> /boot/grub2/grub.cfg is only used for legacy non-uefi boots which also
> require grub2-install to be used to write the grub menus to the legacy
> mbr. Uefi doesn't require the mbr updates.

These regular more or less long threads on "grub.cfg" should be the
signal that Fedora's setting up grub incorrectly on EFI and should
adopt the Ubuntu setup with two config files:

1) /boot/efi/EFI/fedora/grub.cfg : generated by grub2-install and
solely there to set "prefix" to "(hdX,gptY)/boot/grub"

2) /boot/grub2/grub.cfg : generated by "grub2-mkconfig" just like BIOS systems
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Samuel Sieb]

On 6/12/20 9:34 PM, Tim via users wrote:

On Sat, 2020-06-13 at 14:00 +1000, Stephen Morris wrote:

/boot/grub2/grub.cfg is only used for legacy non-uefi boots which
also require grub2-install to be used to write the grub menus to the
legacy mbr. Uefi doesn't require the mbr updates.


I didn't think menus were written to MBR, just the code to load GRUB,
and then GRUB loads its menus from the files deeper inside /boot.


Right.  It only writes the bootsector and the part of grub that the 
bootsector will load.  Then that part has enough to load everything else 
from the filesystem.

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Tim via users]

On Sat, 2020-06-13 at 14:00 +1000, Stephen Morris wrote:
> /boot/grub2/grub.cfg is only used for legacy non-uefi boots which
> also require grub2-install to be used to write the grub menus to the
> legacy mbr. Uefi doesn't require the mbr updates.

I didn't think menus were written to MBR, just the code to load GRUB,
and then GRUB loads its menus from the files deeper inside /boot.

-- 
 
uname -rsvp
Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 11/6/20 4:18 am, linux guy wrote:



On Wed, Jun 10, 2020 at 1:37 AM Stephen Morris 
mailto:samor...@netspace.net.au>> wrote:


    Also as I understand it /boot/grub2/grub.cfg is the grub
config file used to generate the grub menus for legacy booting,
where to get that structure into the mbr you need to issue
grub2-install, and, the /boot/efi/EFI/fedora/grub.cfg is what is
used for efi booting and in that scenario you do not need to issue
grub2-install.


That would explain a few things.

# grub2-install
grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't 
exist. Please specify --target or --directory.


What target or directory should I be specifying ?

If you boot your system from your first hard disk then the mbr update 
command you would issue is    grub2-install /dev/sda. I think the reason 
for the error was you didn't tell the command which disk's mbr to update.


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


___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 11/6/20 7:41 am, R. G. Newbury wrote:

On 2020-06-09 8:11 p.m.Stephen Morris wrote

if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
that inserts a line into the grub processes to use the new BLS 
standard,=20
in which case grub2-mkconfig and possibly grubby do nothing until 
that=20
entry is set to false. I have always use grub2-mkconfig because I 
have=20
never liked what grubby generated, and what BLS generates appears to 
be=20
the same as what grubby does, and I found that I had to set that 
entry=20

to false for grub2-mkconfig to continue to work.


THANKS FOR THAT, Steve!

I could not get grub2-mkconfig to actually change the grub.cfg file. 
Now I know why ( but not why such a dangerously misdescriptive switch 
would be hidden away in a default file).
In the past I would just edit the damn file, but the new motherboard 
uses EFI, and such hands-on fixing might lead to an undesired result!
If you are booting via uefi with fedora then if you use grub2-mkconfig 
to update grub.cfg then you need to run it against 
/boot/efi/EFI/fedora/grub.cfg as that is where uefi looks for it, 
/boot/grub2/grub.cfg is only used for legacy non-uefi boots which also 
require grub2-install to be used to write the grub menus to the legacy 
mbr. Uefi doesn't require the mbr updates.


regards,
Steve



Geoff
___
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

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[R. G. Newbury]

On 2020-06-09 8:11 p.m.Stephen Morris wrote

if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true
that inserts a line into the grub processes to use the new BLS standard,=20
in which case grub2-mkconfig and possibly grubby do nothing until that=20
entry is set to false. I have always use grub2-mkconfig because I have=20
never liked what grubby generated, and what BLS generates appears to be=20
the same as what grubby does, and I found that I had to set that entry=20
to false for grub2-mkconfig to continue to work.


THANKS FOR THAT, Steve!

I could not get grub2-mkconfig to actually change the grub.cfg file. Now 
I know why ( but not why such a dangerously misdescriptive switch would 
be hidden away in a default file).
In the past I would just edit the damn file, but the new motherboard 
uses EFI, and such hands-on fixing might lead to an undesired result!


Geoff
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

# blkid
/dev/nvme0n1p1: UUID="D76F-0EDB" BLOCK_SIZE="512" TYPE="vfat"
PARTLABEL="EFI System Partition"
PARTUUID="c2d93266-9038-4fc9-923a-797fb0595aa0"
/dev/nvme0n1p2: UUID="39373709-00f2-43a6-8f8d-dae45eb32add"
BLOCK_SIZE="4096" TYPE="ext4"
PARTUUID="d20f2f5b-be53-4714-80ae-2dd675aba973"
/dev/nvme0n1p3: UUID="3VH3r7-BOSc-PaRC-Ragt-15Co-Th5g-YX4nVs"
TYPE="LVM2_member" PARTUUID="2d9c0127-b6a4-4afd-a1e0-c1285615b572"
/dev/mapper/fedora_localhost--live-root:
UUID="8d74a47c-8d3f-4b5a-acc5-02bc6888c8bb" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/fedora_localhost--live-swap:
UUID="c236d9d8-66f4-409b-bac5-88c4662c4fe5" TYPE="swap"
/dev/mapper/fedora_localhost--live-home:
UUID="6c65d0c7-865d-4c32-9bb8-227d63dfa37b" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
Looks like only 1 EFI partition.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Jonathan Billings]

On Wed, Jun 10, 2020 at 12:20:35PM -0600, linux guy wrote:
> On Wed, Jun 10, 2020 at 7:31 AM Jonathan Billings 
> wrote:
> 
> > First, it's probably worth seeing whether you're booting via a legacy
> > boot (CSM) or directly to UEFI.
> >
> > Does /sys/firmware/efi/ exist and have files in it?  Then you've
> > booted via EFI.  If it doesn't?  Then you aren't.
> >
> 
> # ls -al /sys/firmware/efi
> total 0
> drwxr-xr-x.  5 root root0 Jun  9 19:06 .
> drwxr-xr-x.  6 root root0 Jun  9 19:06 ..
> -r--r--r--.  1 root root 4096 Jun 10 12:19 config_table
> drwxr-xr-x.  2 root root0 Jun  9 19:06 efivars
> drwxr-xr-x.  3 root root0 Jun 10 12:19 esrt
> -r--r--r--.  1 root root 4096 Jun 10 12:16 fw_platform_size
> -r--r--r--.  1 root root 4096 Jun 10 12:19 fw_vendor
> -r--r--r--.  1 root root 4096 Jun 10 12:19 runtime
> drwxr-xr-x. 11 root root0 Jun 10 12:19 runtime-map
> -r.  1 root root 4096 Jun 10 12:19 systab

So, you're using UEFI.  You can basically ignore the
/boot/grub2/grub.cfg file.  Anything you are working with will be in
/boot/efi/EFI/fedora/.  

> You might also want to make sure there aren't any other EFI or /boot
> > partitions that might be hanging around that are being used by the
> > boot that have old data on them.
> >
> 
> What/where do you want me to check ?

Look for another EFI partition.

Run `blkid` as root, and look for anything with:
PARTLABEL="EFI System Partition"

-- 
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

On Wed, Jun 10, 2020 at 7:31 AM Jonathan Billings 
wrote:

> First, it's probably worth seeing whether you're booting via a legacy
> boot (CSM) or directly to UEFI.
>
> Does /sys/firmware/efi/ exist and have files in it?  Then you've
> booted via EFI.  If it doesn't?  Then you aren't.
>

# ls -al /sys/firmware/efi
total 0
drwxr-xr-x.  5 root root0 Jun  9 19:06 .
drwxr-xr-x.  6 root root0 Jun  9 19:06 ..
-r--r--r--.  1 root root 4096 Jun 10 12:19 config_table
drwxr-xr-x.  2 root root0 Jun  9 19:06 efivars
drwxr-xr-x.  3 root root0 Jun 10 12:19 esrt
-r--r--r--.  1 root root 4096 Jun 10 12:16 fw_platform_size
-r--r--r--.  1 root root 4096 Jun 10 12:19 fw_vendor
-r--r--r--.  1 root root 4096 Jun 10 12:19 runtime
drwxr-xr-x. 11 root root0 Jun 10 12:19 runtime-map
-r.  1 root root 4096 Jun 10 12:19 systab

You might also want to make sure there aren't any other EFI or /boot
> partitions that might be hanging around that are being used by the
> boot that have old data on them.
>

What/where do you want me to check ?
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

On Wed, Jun 10, 2020 at 1:37 AM Stephen Morris 
wrote:

> Also as I understand it /boot/grub2/grub.cfg is the grub config file
> used to generate the grub menus for legacy booting, where to get that
> structure into the mbr you need to issue grub2-install, and, the
> /boot/efi/EFI/fedora/grub.cfg is what is used for efi booting and in that
> scenario you do not need to issue grub2-install.
>

That would explain a few things.

# grub2-install
grub2-install: error: /usr/lib/grub/x86_64-efi/modinfo.sh doesn't exist.
Please specify --target or --directory.

What target or directory should I be specifying ?
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Jonathan Billings]

On Tue, Jun 09, 2020 at 07:14:23PM -0600, linux guy wrote:
> Rebooted.  No change to the grub kernel parameters.

First, it's probably worth seeing whether you're booting via a legacy
boot (CSM) or directly to UEFI.

Does /sys/firmware/efi/ exist and have files in it?  Then you've
booted via EFI.  If it doesn't?  Then you aren't.

You might also want to make sure there aren't any other EFI or /boot
partitions that might be hanging around that are being used by the
boot that have old data on them.

-- 
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

Re: How do I change the grub kernel boot parameters in F32 ?

[ja]

> 
> 
> ___
> 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

Just a thought:

If you are using efi boot and BLS ("normal" fo F32) then try
commands of the form below.

You can change entries in /boot/efi/EFI/fedora/grubenv directly as follows
Modify as required 

Add a kernelopt
grub2-editenv - set "$(grub2-editenv - list | grep kernelopts) net.ifnames=0 
biosdevname=0"
Remove a kernelopt
grub2-editenv - set "$(grub2-editenv - list | grep kernelopts | sed -e 
's/rhgb//')"
grub2-editenv - set "$(grub2-editenv - list | grep kernelopts | sed -e 
's/quiet//')"

Not my code but probably from this list.

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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 10/6/20 2:42 pm, linux guy wrote:
c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64.conf as it 
sits now:


title Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)
version 5.6.16-300.fc32.x86_64
linux /vmlinuz-5.6.16-300.fc32.x86_64
initrd /initramfs-5.6.16-300.fc32.x86_64.img
options $kernelopts
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel

Edited /etc/default/grub to this:

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.blacklist=nouveau 
modprobe.blacklist=nouveau nvidia-drm.modeset=1 rd.l>

GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="true"

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64.conf after 
running these.


Title Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)
version 5.6.16-300.fc32.x86_64
linux /vmlinuz-5.6.16-300.fc32.x86_64
initrd /initramfs-5.6.16-300.fc32.x86_64.img
options $kernelopts
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel

from nano /boot/efi/EFI/fedora/grub.cfg:

===
# This section was generated by a script. Do not modify the generated 
file - all changes
# will be lost the next time file is regenerated. Instead edit the 
BootLoaderSpec files.

#
# The blscfg command parses the BootLoaderSpec files stored in 
/boot/loader/entries and
# populates the boot menu. Please refer to the Boot Loader 
Specification documentation
# for the files format: 
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/ 
.


# The kernelopts variable should be defined in the grubenv file. But 
to ensure that menu
# entries populated from BootLoaderSpec files that use this variable 
work correctly even
# without a grubenv file, define a fallback kernelopts variable if 
this has not been set.

#
# The kernelopts variable in the grubenv file can be modified using 
the grubby tool or by
# executing the grub2-mkconfig tool. For the latter, the values of the 
GRUB_CMDLINE_LINUX
# and GRUB_CMDLINE_LINUX_DEFAULT options from /etc/default/grub file 
are used to set both
# the kernelopts variable in the grubenv file and the fallback 
kernelopts variable.

if [ -z "${kernelopts}" ]; then
  set kernelopts="root=/dev/mapper/fedora_localhost--live-root ro 
rd.driver.blacklist=nouveau modpro>

fi

insmod blscfg
blscfg
### END /etc/grub.d/10_linux ###


This is as far as I got with the instructions in your post. I'll 
finish this later.
As I understand the processes, those two blscfg statements are what 
controls the kernels displayed and kernel commands issues in the boot 
menu. As I specified in another thread, when this standard was 
introduced, I think if F31, I was always using grub2-mkconfig to 
generate the grub menus and the introduction of the blscfg standard 
caused the usage of grub2-mkconfig to not make any difference to the 
menus shown at boot time, and people on this mailing list told me to 
disable blscfg in /etc/default/grub, which having done that causes 
grub2-mkconfig to actually work.
    Also as I understand it /boot/grub2/grub.cfg is the grub config 
file used to generate the grub menus for legacy booting, where to get 
that structure into the mbr you need to issue grub2-install, and, the 
/boot/efi/EFI/fedora/grub.cfg is what is used for efi booting and in 
that scenario you do not need to issue grub2-install.


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


___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64.conf as it sits now:

title Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)
version 5.6.16-300.fc32.x86_64
linux /vmlinuz-5.6.16-300.fc32.x86_64
initrd /initramfs-5.6.16-300.fc32.x86_64.img
options $kernelopts
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel

Edited /etc/default/grub to this:

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.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1 rd.l>
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="true"

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64.conf after running
these.

Title Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)
version 5.6.16-300.fc32.x86_64
linux /vmlinuz-5.6.16-300.fc32.x86_64
initrd /initramfs-5.6.16-300.fc32.x86_64.img
options $kernelopts
grub_users $grub_users
grub_arg --unrestricted
grub_class kernel

from nano /boot/efi/EFI/fedora/grub.cfg:

===
# This section was generated by a script. Do not modify the generated file
- all changes
# will be lost the next time file is regenerated. Instead edit the
BootLoaderSpec files.
#
# The blscfg command parses the BootLoaderSpec files stored in
/boot/loader/entries and
# populates the boot menu. Please refer to the Boot Loader Specification
documentation
# for the files format:
https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/.

# The kernelopts variable should be defined in the grubenv file. But to
ensure that menu
# entries populated from BootLoaderSpec files that use this variable work
correctly even
# without a grubenv file, define a fallback kernelopts variable if this has
not been set.
#
# The kernelopts variable in the grubenv file can be modified using the
grubby tool or by
# executing the grub2-mkconfig tool. For the latter, the values of the
GRUB_CMDLINE_LINUX
# and GRUB_CMDLINE_LINUX_DEFAULT options from /etc/default/grub file are
used to set both
# the kernelopts variable in the grubenv file and the fallback kernelopts
variable.
if [ -z "${kernelopts}" ]; then
  set kernelopts="root=/dev/mapper/fedora_localhost--live-root ro
rd.driver.blacklist=nouveau modpro>
fi

insmod blscfg
blscfg
### END /etc/grub.d/10_linux ###


This is as far as I got with the instructions in your post. I'll finish
this later.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[stan via users]

On Tue, 9 Jun 2020 19:14:23 -0600
linux guy  wrote:

> Changed GRUB_ENABLE_BLSCFG=true  to false.

Some random suggestions.  I don't run nvidia anymore so never have
problems like this, but maybe one of these will at least give you some
insight to what is happening.

F32 should work with GRUB_ENABLE_BLSCFG=true since it is the default
for new installs.  Can you set it back to true and then run the
mkconfig for efi again.  Once you do that, can you show the output of 

cat /boot/loader/entries for the .conf file for the 5.6.16-300 kernel

Then show the line in /boot/efi/EFI/fedora/grub.cfg that has kernelopts
in it.  If the kernel options you want aren't in that line, I don't see
how they will get to your kernel.

I know whether the system is booting efi or not because a message comes
up during boot, before the selection menu, that says something like
using efi secure boot
I have rhgb and quiet turned off, though, so I see that message.  I see
you have them turned on.  If you remove them, there might be a clue to
what is happening in the kernel messages.

Does anything show up as an issue if you do a
journalctl -b
and go to a boot that didn't have the parameters you want?

Try reinstalling the nvidia packages from rpmfusion after you generate
a new grub.cfg, and forget about the nvidia options, to see if it will
install correctly the way it always has once you have a grub.cfg file (I
think you said initially you didn't have one).

What happens if you use the efi firmware boot menu to try to boot using
efi?
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

On Tue, Jun 9, 2020 at 6:57 PM Samuel Sieb  wrote:

>
> I think there is a file added to /etc/modprobe.d with the blacklist
> entry.  You need to install a new kernel or regenerate the initramfs
> using dracut for it to take effect at boot.
>

I've installed several kernels since changing to the NVidia driver.
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

Changed GRUB_ENABLE_BLSCFG=true  to false.

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.6.16-300.fc32.x86_64
Found initrd image: /boot/initramfs-5.6.16-300.fc32.x86_64.img
Found linux image: /boot/vmlinuz-5.6.14-300.fc32.x86_64
Found initrd image: /boot/initramfs-5.6.14-300.fc32.x86_64.img
Found linux image: /boot/vmlinuz-5.6.13-300.fc32.x86_64
Found initrd image: /boot/initramfs-5.6.13-300.fc32.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-c1d3ebaecd08428ba86f4aba3749efca
Found initrd image:
/boot/initramfs-0-rescue-c1d3ebaecd08428ba86f4aba3749efca.img
Adding boot menu entry for EFI firmware configuration

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.6.16-300.fc32.x86_64
Found initrd image: /boot/initramfs-5.6.16-300.fc32.x86_64.img
Found linux image: /boot/vmlinuz-5.6.14-300.fc32.x86_64
Found initrd image: /boot/initramfs-5.6.14-300.fc32.x86_64.img
Found linux image: /boot/vmlinuz-5.6.13-300.fc32.x86_64
Found initrd image: /boot/initramfs-5.6.13-300.fc32.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-c1d3ebaecd08428ba86f4aba3749efca
Found initrd image:
/boot/initramfs-0-rescue-c1d3ebaecd08428ba86f4aba3749efca.img
Adding boot menu entry for EFI firmware configuration
done

Rebooted.  No change to the grub kernel parameters.



On Tue, Jun 9, 2020 at 6:11 PM Stephen Morris 
wrote:

> On 10/6/20 8:53 am, linux guy wrote:
>
> I've run Nvidia drivers since the RH8 days, back in the early 2000s.  Same
> experience.  This is the first time I've had this issue.
>
> On Tue, Jun 9, 2020 at 4:31 PM Joe Zeff  wrote:
>
>> On 06/09/2020 02:40 PM, linux guy wrote:
>> > So both grubby and /etc/default/grub are set up correctly to run the
>> > nvidia driver by blacklisting the nouveau driver.
>> >
>> > But when I boot and edit the grub menu (with e), the kernal parameter
>> > entries lack the blacklisting of the nouveau driver.
>>
>> I used nVidia cards for over a decade with the drivers from rpmfusion
>> and I never had to explicitly blacklist the noveau drivers.  I think
>> that the best way to go is to install the drivers and see what happens.
>> If they Just Work, leave well enough alone and Be Happy.  If they don't
>> work right, then it's time to try things such as blacklisting.
>>
> if in /etc/default/grub you have the entry   GRUB_ENABLE_BLSCFG=true   ,
> that inserts a line into the grub processes to use the new BLS standard, in
> which case grub2-mkconfig and possibly grubby do nothing until that entry
> is set to false. I have always use grub2-mkconfig because I have never
> liked what grubby generated, and what BLS generates appears to be the same
> as what grubby does, and I found that I had to set that entry to false for
> grub2-mkconfig to continue to work.
>
> 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
>>
>
> ___
> 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
>
>
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Samuel Sieb]

On 6/9/20 4:59 PM, Stephen Morris wrote:

On 10/6/20 4:46 am, linux guy wrote:

dnf list akmod-nvidia
Last metadata expiration check: 0:09:43 ago on Tue 09 Jun 2020 
12:35:57 PM MDT.

Installed Packages
akmod-nvidia.x86_64                            3:440.82-2.fc32 
                   @rpmfusion-nonfree-updates


Not sure why the changes don't make it into grub.  If I blacklist 
nouveau in kernel params manually, the nvidia driver works fine.




On Tue, Jun 9, 2020 at 12:01 PM Jerry James > wrote:


On Tue, Jun 9, 2020 at 11:44 AM linux guy mailto:linuxguy...@gmail.com>> wrote:
> This is pretty interesting because I am trying to fix a problem
caused by transitioning from nouveau drivers to the Nvidia
drivers.  I installed the Nvidia drivers but my system continues
to boot the nouveau drivers.   If I blacklist the nouveau drivers,
my system boots and runs the Nvidia drivers just fine.   The
kernel parameters I want to add are for blacklisting the nouveau
driver.  (See above).


Did you install from rpmfusion, or somewhere else?  If rpmfusion, did
you install the akmod-nvidia package?

I'm not sure what happens now, as I no longer use the nvidia package 
since switching to using Fedora in a VM, but with earlier versions of 
Fedora, when using the akmod-nvidia package from rpmfusion or the 
equivalent package from negativo17 (which I switched to for better 
Fedora compatibility) the blacklisting of the nouveau drivers used to be 
automatically place in the kernel options in /etc/default/grub, but 
these options also only worked properly after they worked around the 
issue of the nouveau drivers being installed into the initramfs img files.


I think there is a file added to /etc/modprobe.d with the blacklist 
entry.  You need to install a new kernel or regenerate the initramfs 
using dracut for it to take effect at boot.

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 10/6/20 8:53 am, linux guy wrote:
I've run Nvidia drivers since the RH8 days, back in the early 2000s.  
Same experience.  This is the first time I've had this issue.


On Tue, Jun 9, 2020 at 4:31 PM Joe Zeff > wrote:


On 06/09/2020 02:40 PM, linux guy wrote:
> So both grubby and /etc/default/grub are set up correctly to run
the
> nvidia driver by blacklisting the nouveau driver.
>
> But when I boot and edit the grub menu (with e), the kernal
parameter
> entries lack the blacklisting of the nouveau driver.

I used nVidia cards for over a decade with the drivers from rpmfusion
and I never had to explicitly blacklist the noveau drivers.  I think
that the best way to go is to install the drivers and see what
happens.
If they Just Work, leave well enough alone and Be Happy.  If they
don't
work right, then it's time to try things such as blacklisting.

if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true   , 
that inserts a line into the grub processes to use the new BLS standard, 
in which case grub2-mkconfig and possibly grubby do nothing until that 
entry is set to false. I have always use grub2-mkconfig because I have 
never liked what grubby generated, and what BLS generates appears to be 
the same as what grubby does, and I found that I had to set that entry 
to false for grub2-mkconfig to continue to work.


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




___
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


___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Stephen Morris]

On 10/6/20 4:46 am, linux guy wrote:

dnf list akmod-nvidia
Last metadata expiration check: 0:09:43 ago on Tue 09 Jun 2020 
12:35:57 PM MDT.

Installed Packages
akmod-nvidia.x86_64                            3:440.82-2.fc32         
                   @rpmfusion-nonfree-updates


Not sure why the changes don't make it into grub.  If I blacklist 
nouveau in kernel params manually, the nvidia driver works fine.




On Tue, Jun 9, 2020 at 12:01 PM Jerry James > wrote:


On Tue, Jun 9, 2020 at 11:44 AM linux guy mailto:linuxguy...@gmail.com>> wrote:
> This is pretty interesting because I am trying to fix a problem
caused by transitioning from nouveau drivers to the Nvidia
drivers.  I installed the Nvidia drivers but my system continues
to boot the nouveau drivers.   If I blacklist the nouveau drivers,
my system boots and runs the Nvidia drivers just fine.   The
kernel parameters I want to add are for blacklisting the nouveau
driver.  (See above).


Did you install from rpmfusion, or somewhere else?  If rpmfusion, did
you install the akmod-nvidia package?

I'm not sure what happens now, as I no longer use the nvidia package 
since switching to using Fedora in a VM, but with earlier versions of 
Fedora, when using the akmod-nvidia package from rpmfusion or the 
equivalent package from negativo17 (which I switched to for better 
Fedora compatibility) the blacklisting of the nouveau drivers used to be 
automatically place in the kernel options in /etc/default/grub, but 
these options also only worked properly after they worked around the 
issue of the nouveau drivers being installed into the initramfs img files.


regards,
Steve

-- 
Jerry James

http://www.jamezone.org/ 
___
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




___
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


___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

re: Adam Mercer's suggestion:

grubby --update-kernel=ALL --args="rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1"

Grubby is already returning the right kernel parameters.  Not sure why I
would need to run this.


re: As far as setting /etc/default/grub LINUX_CMDLINE args, those appear to
be used by grub2-mkconfig, not grubby.
So I ran this:

# grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

and it made no difference.

So I ran this:

# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Adding boot menu entry for EFI firmware configuration
done

Also made no difference.







On Tue, Jun 9, 2020 at 3:24 PM Mike Wright 
wrote:

> On 6/9/20 1:40 PM, linux guy wrote:
> > So both grubby and /etc/default/grub are set up correctly to run the
> nvidia
> > driver by blacklisting the nouveau driver.
> >
> > But when I boot and edit the grub menu (with e), the kernal parameter
> > entries lack the blacklisting of the nouveau driver.
> >
> > According to this page
> >
> https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/
> > grub.cfg is generated from /etc/default/grub from anaconda and I'm only
> > supposed to run grub2-mkconfig as a last resort to regenerate grub.cfg.
> >
> > This article must be out of date because my machine has neither
> > /boot/grub2/grub.cfg nor /boot/efi/EFI/fedora/grub.cfg
> >
> > This confuses things even more.
> > https://fedoraproject.org/wiki/GRUB_2
> >
> > How do I properly change the kernel parameters in my grub boot menu ?
>
> See the reply from Adam Mercer.  He gives the whole command line argument.
>
> As far as setting /etc/default/grub LINUX_CMDLINE args, those appear to
> be used by grub2-mkconfig, not grubby.
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

I've run Nvidia drivers since the RH8 days, back in the early 2000s.  Same
experience.  This is the first time I've had this issue.

On Tue, Jun 9, 2020 at 4:31 PM Joe Zeff  wrote:

> On 06/09/2020 02:40 PM, linux guy wrote:
> > So both grubby and /etc/default/grub are set up correctly to run the
> > nvidia driver by blacklisting the nouveau driver.
> >
> > But when I boot and edit the grub menu (with e), the kernal parameter
> > entries lack the blacklisting of the nouveau driver.
>
> I used nVidia cards for over a decade with the drivers from rpmfusion
> and I never had to explicitly blacklist the noveau drivers.  I think
> that the best way to go is to install the drivers and see what happens.
> If they Just Work, leave well enough alone and Be Happy.  If they don't
> work right, then it's time to try things such as blacklisting.
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Joe Zeff]

On 06/09/2020 02:40 PM, linux guy wrote:
So both grubby and /etc/default/grub are set up correctly to run the 
nvidia driver by blacklisting the nouveau driver.


But when I boot and edit the grub menu (with e), the kernal parameter 
entries lack the blacklisting of the nouveau driver.


I used nVidia cards for over a decade with the drivers from rpmfusion 
and I never had to explicitly blacklist the noveau drivers.  I think 
that the best way to go is to install the drivers and see what happens. 
If they Just Work, leave well enough alone and Be Happy.  If they don't 
work right, then it's time to try things such as blacklisting.

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Mike Wright]

On 6/9/20 1:40 PM, linux guy wrote:

So both grubby and /etc/default/grub are set up correctly to run the nvidia
driver by blacklisting the nouveau driver.

But when I boot and edit the grub menu (with e), the kernal parameter
entries lack the blacklisting of the nouveau driver.

According to this page
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/
grub.cfg is generated from /etc/default/grub from anaconda and I'm only
supposed to run grub2-mkconfig as a last resort to regenerate grub.cfg.

This article must be out of date because my machine has neither
/boot/grub2/grub.cfg nor /boot/efi/EFI/fedora/grub.cfg

This confuses things even more.
https://fedoraproject.org/wiki/GRUB_2

How do I properly change the kernel parameters in my grub boot menu ?


See the reply from Adam Mercer.  He gives the whole command line argument.

As far as setting /etc/default/grub LINUX_CMDLINE args, those appear to 
be used by grub2-mkconfig, not grubby.

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Mike Wright]

On 6/9/20 1:40 PM, linux guy wrote:

So both grubby and /etc/default/grub are set up correctly to run the nvidia
driver by blacklisting the nouveau driver.

But when I boot and edit the grub menu (with e), the kernal parameter
entries lack the blacklisting of the nouveau driver.

According to this page
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/
grub.cfg is generated from /etc/default/grub from anaconda and I'm only
supposed to run grub2-mkconfig as a last resort to regenerate grub.cfg.

This article must be out of date because my machine has neither
/boot/grub2/grub.cfg nor /boot/efi/EFI/fedora/grub.cfg

This confuses things even more.
https://fedoraproject.org/wiki/GRUB_2

How do I properly change the kernel parameters in my grub boot menu ?


This may be useful:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/sec-making_persistent_changes_to_a_grub_2_menu_using_the_grubby_tool
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

So both grubby and /etc/default/grub are set up correctly to run the nvidia
driver by blacklisting the nouveau driver.

But when I boot and edit the grub menu (with e), the kernal parameter
entries lack the blacklisting of the nouveau driver.

According to this page
https://docs.fedoraproject.org/en-US/fedora/rawhide/system-administrators-guide/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader/
grub.cfg is generated from /etc/default/grub from anaconda and I'm only
supposed to run grub2-mkconfig as a last resort to regenerate grub.cfg.

This article must be out of date because my machine has neither
/boot/grub2/grub.cfg nor /boot/efi/EFI/fedora/grub.cfg

This confuses things even more.
https://fedoraproject.org/wiki/GRUB_2

How do I properly change the kernel parameters in my grub boot menu ?
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

# grubby --info=ALL
index=0
kernel="/boot/vmlinuz-5.6.16-300.fc32.x86_64"
args="ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.6.16-300.fc32.x86_64.img"
title="Fedora (5.6.16-300.fc32.x86_64) 32 (Thirty Two)"
id="c1d3ebaecd08428ba86f4aba3749efca-5.6.16-300.fc32.x86_64"
index=1
kernel="/boot/vmlinuz-5.6.14-300.fc32.x86_64"
args="ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.6.14-300.fc32.x86_64.img"
title="Fedora (5.6.14-300.fc32.x86_64) 32 (Thirty Two)"
id="c1d3ebaecd08428ba86f4aba3749efca-5.6.14-300.fc32.x86_64"
index=2
kernel="/boot/vmlinuz-5.6.13-300.fc32.x86_64"
args="ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-5.6.13-300.fc32.x86_64.img"
title="Fedora (5.6.13-300.fc32.x86_64) 32 (Thirty Two)"
id="c1d3ebaecd08428ba86f4aba3749efca-5.6.13-300.fc32.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-c1d3ebaecd08428ba86f4aba3749efca"
args="ro rd.lvm.lv=fedora/root rd.lvm.lv=fedora/swap rhgb quiet
rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1"
root="/dev/mapper/fedora_localhost--live-root"
initrd="/boot/initramfs-0-rescue-c1d3ebaecd08428ba86f4aba3749efca.img"
title="Fedora (0-rescue-c1d3ebaecd08428ba86f4aba3749efca) 31 (Thirty One)"
id="c1d3ebaecd08428ba86f4aba3749efca-0-rescue"
This appears correct !
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

It appears that the problem is that my machine thinks it is booting in non
efi mode but is in fact booting in UEFI mode.   How do I fix this ?

On Tue, Jun 9, 2020 at 12:49 PM linux guy  wrote:

> Thank you for sharing that !   Here is my /etc/default/grub.  It
> blacklists the nouveau driver.
>
> How do I tell how my computer is booting (UEFI or not) and how do I set up
> the parameters if its booting UEFI ?
>
> 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.blacklist=nouveau modprobe.blacklist=nouveau
> nvidia-drm.modeset=1 rd.lvm.lv=fedora/ro>
> GRUB_DISABLE_RECOVERY="true"
> GRUB_ENABLE_BLSCFG="true"
>
>
>
>
> On Tue, Jun 9, 2020 at 12:39 PM Robert McBroom via users <
> users@lists.fedoraproject.org> wrote:
>
>> On 6/9/20 1:43 PM, linux guy wrote:
>>
>> This is pretty interesting because I am trying to fix a problem caused by
>> transitioning from nouveau drivers to the Nvidia drivers.  I installed the
>> Nvidia drivers but my system continues to boot the nouveau drivers.   If I
>> blacklist the nouveau drivers, my system boots and runs the Nvidia drivers
>> just fine.   The kernel parameters I want to add are for blacklisting the
>> nouveau driver.  (See above).
>>
>>
>>
>>
>> I just installed Fedora 32 on a machine 2 days ago, and had to install
>>> the nvidia drivers because nouveau kept crashing (alas!).  I installed
>>> the rpmfusion akmod-nvidia package, and the corresponding kernel entry
>>> has this:
>>>
>>> options $kernelopts
>>>
>>> So it looks like the grubby issue has been fixed.
>>> --
>>
>> So far this setup still works for a legacy non-efi boot
>>
>> /etc/default/grub
>> GRUB_TIMEOUT=15
>> GRUB_DISTRIBUTOR="Fedora"
>> GRUB_DEFAULT="Windows 10 (loader) (on /dev/sda1)"
>> GRUB_GFXMODE=1280x1024x32
>> GRUB_GFXPAYLOAD_LINUX=keep
>> GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True  KEYTABLE=us
>> rd.luks=0 LANG=en_US.UTF-8 vga=791 "
>> GRUB_THEME="/boot/grub2/themes/system/theme.txt"
>> # GRUB_THEME=/boot/grub2/themes/starfield/theme.txt
>>
>> GRUB_ENABLE_BLSCFG=true
>>
>>
>> Have yet to get the gfxmode line to do anything with the grub screen
>> though.
>> ___
>> 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
>>
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

Thank you for sharing that !   Here is my /etc/default/grub.  It blacklists
the nouveau driver.

How do I tell how my computer is booting (UEFI or not) and how do I set up
the parameters if its booting UEFI ?

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.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1 rd.lvm.lv=fedora/ro>
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="true"




On Tue, Jun 9, 2020 at 12:39 PM Robert McBroom via users <
users@lists.fedoraproject.org> wrote:

> On 6/9/20 1:43 PM, linux guy wrote:
>
> This is pretty interesting because I am trying to fix a problem caused by
> transitioning from nouveau drivers to the Nvidia drivers.  I installed the
> Nvidia drivers but my system continues to boot the nouveau drivers.   If I
> blacklist the nouveau drivers, my system boots and runs the Nvidia drivers
> just fine.   The kernel parameters I want to add are for blacklisting the
> nouveau driver.  (See above).
>
>
>
>
> I just installed Fedora 32 on a machine 2 days ago, and had to install
>> the nvidia drivers because nouveau kept crashing (alas!).  I installed
>> the rpmfusion akmod-nvidia package, and the corresponding kernel entry
>> has this:
>>
>> options $kernelopts
>>
>> So it looks like the grubby issue has been fixed.
>> --
>
> So far this setup still works for a legacy non-efi boot
>
> /etc/default/grub
> GRUB_TIMEOUT=15
> GRUB_DISTRIBUTOR="Fedora"
> GRUB_DEFAULT="Windows 10 (loader) (on /dev/sda1)"
> GRUB_GFXMODE=1280x1024x32
> GRUB_GFXPAYLOAD_LINUX=keep
> GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True  KEYTABLE=us
> rd.luks=0 LANG=en_US.UTF-8 vga=791 "
> GRUB_THEME="/boot/grub2/themes/system/theme.txt"
> # GRUB_THEME=/boot/grub2/themes/starfield/theme.txt
>
> GRUB_ENABLE_BLSCFG=true
>
>
> Have yet to get the gfxmode line to do anything with the grub screen
> though.
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

dnf list akmod-nvidia
Last metadata expiration check: 0:09:43 ago on Tue 09 Jun 2020 12:35:57 PM
MDT.
Installed Packages
akmod-nvidia.x86_643:440.82-2.fc32
   @rpmfusion-nonfree-updates

Not sure why the changes don't make it into grub.  If I blacklist nouveau
in kernel params manually, the nvidia driver works fine.



On Tue, Jun 9, 2020 at 12:01 PM Jerry James  wrote:

> On Tue, Jun 9, 2020 at 11:44 AM linux guy  wrote:
> > This is pretty interesting because I am trying to fix a problem caused
> by transitioning from nouveau drivers to the Nvidia drivers.  I installed
> the Nvidia drivers but my system continues to boot the nouveau drivers.
>  If I blacklist the nouveau drivers, my system boots and runs the Nvidia
> drivers just fine.   The kernel parameters I want to add are for
> blacklisting the nouveau driver.  (See above).
>
>
> Did you install from rpmfusion, or somewhere else?  If rpmfusion, did
> you install the akmod-nvidia package?
> --
> Jerry James
> http://www.jamezone.org/
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Robert McBroom via users]

On 6/9/20 1:43 PM, linux guy wrote:
This is pretty interesting because I am trying to fix a problem caused 
by transitioning from nouveau drivers to the Nvidia drivers.  I 
installed the Nvidia drivers but my system continues to boot the 
nouveau drivers.   If I blacklist the nouveau drivers, my system boots 
and runs the Nvidia drivers just fine.   The kernel parameters I want 
to add are for blacklisting the nouveau driver.  (See above).





I just installed Fedora 32 on a machine 2 days ago, and had to install
the nvidia drivers because nouveau kept crashing (alas!).  I installed
the rpmfusion akmod-nvidia package, and the corresponding kernel entry
has this:

options $kernelopts

So it looks like the grubby issue has been fixed.
-- 


So far this setup still works for a legacy non-efi boot

/etc/default/grub

GRUB_TIMEOUT=15
GRUB_DISTRIBUTOR="Fedora"
GRUB_DEFAULT="Windows 10 (loader) (on /dev/sda1)"
GRUB_GFXMODE=1280x1024x32
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 SYSFONT=True KEYTABLE=us 
rd.luks=0 LANG=en_US.UTF-8 vga=791 "

GRUB_THEME="/boot/grub2/themes/system/theme.txt"
# GRUB_THEME=/boot/grub2/themes/starfield/theme.txt

GRUB_ENABLE_BLSCFG=true


Have yet to get the gfxmode line to do anything with the grub screen though.

___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Jerry James]

On Tue, Jun 9, 2020 at 11:44 AM linux guy  wrote:
> This is pretty interesting because I am trying to fix a problem caused by 
> transitioning from nouveau drivers to the Nvidia drivers.  I installed the 
> Nvidia drivers but my system continues to boot the nouveau drivers.   If I 
> blacklist the nouveau drivers, my system boots and runs the Nvidia drivers 
> just fine.   The kernel parameters I want to add are for blacklisting the 
> nouveau driver.  (See above).


Did you install from rpmfusion, or somewhere else?  If rpmfusion, did
you install the akmod-nvidia package?
-- 
Jerry James
http://www.jamezone.org/
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

This is pretty interesting because I am trying to fix a problem caused by
transitioning from nouveau drivers to the Nvidia drivers.  I installed the
Nvidia drivers but my system continues to boot the nouveau drivers.   If I
blacklist the nouveau drivers, my system boots and runs the Nvidia drivers
just fine.   The kernel parameters I want to add are for blacklisting the
nouveau driver.  (See above).



On Tue, Jun 9, 2020 at 8:07 AM Jerry James  wrote:

> On Tue, Jun 9, 2020 at 6:38 AM Jonathan Billings 
> wrote:
> > One thing I've noticed, if you've used grubby to add/modify kernel
> > arguments, on default Fedora configs, it modifies all the files in
> > /boot/loader/entries/*.conf to have hard-coded kernelopts.  By
> > default, it uses $kernelopts which is defined in the default grub.cfg
> > but once grubby is run they're hard-coded in each entry file.  So
> > running grub2-mkconfig doesn't do anything anymore.  You might not
> > even realize you've used grubby, but packages like the rpmfusion
> > akmod-nvidia package runs it to add the blacklist kernel options.
> >
> > Maybe this is a bug that has been fixed since I encountered it?
>
> I just installed Fedora 32 on a machine 2 days ago, and had to install
> the nvidia drivers because nouveau kept crashing (alas!).  I installed
> the rpmfusion akmod-nvidia package, and the corresponding kernel entry
> has this:
>
> options $kernelopts
>
> So it looks like the grubby issue has been fixed.
> --
> Jerry James
> http://www.jamezone.org/
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Jerry James]

On Tue, Jun 9, 2020 at 6:38 AM Jonathan Billings  wrote:
> One thing I've noticed, if you've used grubby to add/modify kernel
> arguments, on default Fedora configs, it modifies all the files in
> /boot/loader/entries/*.conf to have hard-coded kernelopts.  By
> default, it uses $kernelopts which is defined in the default grub.cfg
> but once grubby is run they're hard-coded in each entry file.  So
> running grub2-mkconfig doesn't do anything anymore.  You might not
> even realize you've used grubby, but packages like the rpmfusion
> akmod-nvidia package runs it to add the blacklist kernel options.
>
> Maybe this is a bug that has been fixed since I encountered it?

I just installed Fedora 32 on a machine 2 days ago, and had to install
the nvidia drivers because nouveau kept crashing (alas!).  I installed
the rpmfusion akmod-nvidia package, and the corresponding kernel entry
has this:

options $kernelopts

So it looks like the grubby issue has been fixed.
-- 
Jerry James
http://www.jamezone.org/
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Jonathan Billings]

On Mon, Jun 08, 2020 at 09:06:39PM -0700, Mike Wright wrote:
> Follow that with a update-grub or update-grub2 (not sure which) and that
> will fix your grub.cfg without having to go through the grub-mkconfig
> process.

update-grub{,2} is a debian/ubuntu-ism, I believe.  I typically use
grub2-mkconfig after modifying /etc/default/grub.

One thing I've noticed, if you've used grubby to add/modify kernel
arguments, on default Fedora configs, it modifies all the files in
/boot/loader/entries/*.conf to have hard-coded kernelopts.  By
default, it uses $kernelopts which is defined in the default grub.cfg
but once grubby is run they're hard-coded in each entry file.  So
running grub2-mkconfig doesn't do anything anymore.  You might not
even realize you've used grubby, but packages like the rpmfusion
akmod-nvidia package runs it to add the blacklist kernel options.

Maybe this is a bug that has been fixed since I encountered it?

-- 
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Adam Mercer]

On Mon, Jun 8, 2020 at 6:29 PM linux guy  wrote:

> I would like to change the grub boot parameters for the kernels installed on 
> my F32 workstation.
>
> Specifically, I would like to add the following to the kernel boot 
> parameters: "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau 
> nvidia-drm.modeset=1"
>
> How do I do this ?

I like using the grubby command for this as it adds the arguments and
updates the grub config all in one, so I think you should be able to
apply this to all your kernels with:

$ sudo grubby --update-kernel=ALL --args="rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modeset=1"

Cheers

Adam
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[linux guy]

Thank you.

On Mon, Jun 8, 2020 at 10:07 PM Mike Wright 
wrote:

> On 6/8/20 6:28 PM, linux guy wrote:
> > I would like to change the grub boot parameters for the kernels installed
> > on my F32 workstation.
> >
> > Specifically, I would like to add the following to the kernel boot
> > parameters: "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
> > nvidia-drm.modeset=1"
> >
> > How do I do this ?
>
> I think kernel command line addons are in /etc/default/grub.  Look for
> lines like GRUB_CMDLINE_LINUX or GRUB_CMDLINE_LINUX_DEFAULT, and add
> your options after the = and between the ""
>
> Follow that with a update-grub or update-grub2 (not sure which) and that
> will fix your grub.cfg without having to go through the grub-mkconfig
> process.
>
> :m
> ___
> 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
>
___
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

Re: How do I change the grub kernel boot parameters in F32 ?

[Mike Wright]

On 6/8/20 6:28 PM, linux guy wrote:

I would like to change the grub boot parameters for the kernels installed
on my F32 workstation.

Specifically, I would like to add the following to the kernel boot
parameters: "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1"

How do I do this ?


I think kernel command line addons are in /etc/default/grub.  Look for 
lines like GRUB_CMDLINE_LINUX or GRUB_CMDLINE_LINUX_DEFAULT, and add 
your options after the = and between the ""


Follow that with a update-grub or update-grub2 (not sure which) and that 
will fix your grub.cfg without having to go through the grub-mkconfig 
process.


:m
___
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

How do I change the grub kernel boot parameters in F32 ?

[linux guy]

I would like to change the grub boot parameters for the kernels installed
on my F32 workstation.

Specifically, I would like to add the following to the kernel boot
parameters: "rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modeset=1"

How do I do this ?

Thanks
___
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