Re: Interfaces

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 10:39 +0930, Tim via users wrote:
> Icon choices really annoy me, so many of them are just so completely
> 
> arbitrary that they convey no meaning.  You eventually get used to
> 
> clicking on the third icon across by habit.  And too many of them are
> 
> too similar.  On Evolution, the printer icon sits next to the trash
> 
> icon, the printer icon looks like a paper shredder sitting on top of a
> 
> rubbish bin.

If you think the layout is problematic, I'd suggest discussing it on
the Evo mailing list and eventually filing an RFE.

The icons are determined by the current style dictated by Gnome, not by
Evolution itself. The same applies to fonts.

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

RPM Fusion GPG not Found

[Stephen Morris]

Hi,
    As part of upgrading F31 to F32 using 'dnf system-upgrade download 
--releasever=32', dnf downloaded all packages and downloaded and 
installed the gpg for rpmfusion-free, but it was not able to download 
and install the gpg for rpmfusion-nonfree, and hence would not recognise 
the system as being rebootable to do the upgrade until I manually 
downloaded and imported the rpmfusion-nonfree gpg data. Has anyone else 
encountered this situation?


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: Mount options for mostly-offline drives

[Patrick O'Callaghan]

On Mon, 2020-06-08 at 23:25 -0400, Jon LaBadie wrote:
> On Tue, Jun 02, 2020 at 10:57:10AM +0100, Patrick O'Callaghan wrote:
> > I have a powered USB dock with a couple of SATA drives configured as
> > RAID1, and used only for nightly backups. The (minimal) manual for the
> > dock tells me it will power down after 30 minutes idle time, however I
> > don't see this happening. I presume that something (such as the md
> > system) is touching the drives periodically.
> > 
> > What is the fstab option to have the drives mounted only when accessed?
> > This used to be automount (or autofs) but with systemd getting its
> > fingers into everything I know longer know how to do this.
> > 
> > Can the drive be automatically unmounted if not in use? I presume this
> > would stop md from trying to check it and hence prevent the dock from
> > keeping it powered on.
> > 
> I have an external 4 drive USB enclosure also for nightly backup.  No
> raid, JBOD.
> 
> I use hdparm's -S option (sleep timeout) to set the drives own sleep
> time.  I think I use 10 or 20 min.  The drives still look like they
> are mounted, but their activity lights are all out during the day.
> 
> If I do access one of them, say do a df, cd, or ls, they all wake up
> but there is a delay of 10-20 seconds before my command completes.

Thanks. I tested that and although the hdparm succeeded, the drives
don't power down. I think this particular dock has its own ideas about
idling the drives and won't do it as long as the interface is online.

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

DNF Upgrade of F31 to F32 did not Update Grub

[Stephen Morris]

Hi,
    After eventually getting 'dnf system-upgrade download 
--releasever=32' to download and reboot the system, when the upgrade had 
finished the system booted into sddm. When I selected KDE to start into 
all it did was display a black screen. If I selected Gnome, that did 
exactly the same thing. To try to work around this I booted into 
recovery mode to see if I could identify why this was happening. Looking 
at /boot I found that an F32 kernel had been installed, and when I 
looked at /boot/efi/EFI/fedora/grub.cfg I found that there was no entry 
for the F32 kernel. To circumvent this I issued the command 
grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg, and rebooted via the 
F32 kernel entry, which then enabled KDE and Gnome to both start 
successfully. Has anyone else seen the issue of the F32 upgrade not 
updating grub?


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

NFS Mount Point Failed

[Stephen Morris]

Hi,
    I have the following statement in fstab:

            192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs 
nfsvers=1,x-systemd.automount,defaults 0 0


    When I issue the command 'mount /mnt/nfs' it fails with the 
following messages shown in dmesg, which indicate that the mount seems 
to be trying to proceed via nfs4, why is it doing this when I have the 
option nfsvers=1?


[48439.472418] FS-Cache: Netfs 'nfs' registered for caching
[48439.472732] *** VALIDATE nfs ***
[48439.472741] *** VALIDATE nfs4 ***
[48439.476329] Key type dns_resolver registered
[48439.639981] NFS: Registering the id_resolver key type
[48439.639993] Key type id_resolver registered
[48439.639994] Key type id_legacy registered
[48439.844036] NFS4: Couldn't follow remote path
[48439.852856] NFS4: Couldn't follow remote path
[48439.898650] NFS4: Couldn't follow remote path
[48480.763754] NFS4: Couldn't follow remote path
[48480.774645] NFS4: Couldn't follow remote path

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

DMESG Output Indicating Potential CPU Errors?

[Stephen Morris]

Hi,
    I have the following messages in dmesg output, are they indicating 
a cpu issue, or are they just indicating that because linux is running 
in a vm under windows, and hence sharing the cpu cores with windows that 
windows was using core 7 at the time the process checked?


[16236.896502] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[16236.896506] rcu: 7-...!: (0 ticks this GP) idle=d48/0/0x0 
softirq=207101/207101 fqs=0

[16236.896508]  (detected by 4, t=60008 jiffies, g=263697, q=1058)
[16236.896510] Sending NMI from CPU 4 to CPUs 7:
[16236.896563] NMI backtrace for cpu 7 skipped: idling at 
native_safe_halt+0xe/0x10
[16236.897522] rcu: rcu_sched kthread starved for 60008 jiffies! g263697 
f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=7

[16236.897522] rcu: RCU grace-period kthread stack dump:
[16236.897524] rcu_sched   I    0    11  2 0x80004000
[16236.897526] Call Trace:
[16236.897532]  __schedule+0x26f/0x760
[16236.897535]  schedule+0x4a/0xb0
[16236.897536]  schedule_timeout+0x7b/0x140
[16236.897539]  ? __next_timer_interrupt+0xd0/0xd0
[16236.897541]  rcu_gp_kthread+0x4db/0xa90
[16236.897543]  ? rcu_nocb_cb_kthread+0x210/0x210
[16236.897545]  kthread+0x115/0x140
[16236.897547]  ? __kthread_bind_mask+0x60/0x60
[16236.897549]  ret_from_fork+0x22/0x40

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: NFS Mount Point Failed

[Tom Horsley]

On Tue, 9 Jun 2020 21:54:30 +1000
Stephen Morris wrote:

> nfsvers=1

I seriously doubt there is any support for nfs 1 left
in the code (could be wrong).

Depending on random variations every time the nfs
utilities get updates, I've had to sometimes
specify "proto=udp" as well as or instead of
the nfs version in order to speak to antique servers.
___
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: DMESG Output Indicating Potential CPU Errors?

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 22:10 +1000, Stephen Morris wrote:
> Hi,
>  I have the following messages in dmesg output, are they indicating 
> a cpu issue, or are they just indicating that because linux is running 
> in a vm under windows, and hence sharing the cpu cores with windows that 
> windows was using core 7 at the time the process checked?
> 
> [16236.896502] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
> [16236.896506] rcu: 7-...!: (0 ticks this GP) idle=d48/0/0x0 
> softirq=207101/207101 fqs=0
> [16236.896508]  (detected by 4, t=60008 jiffies, g=263697, q=1058)
> [16236.896510] Sending NMI from CPU 4 to CPUs 7:
> [16236.896563] NMI backtrace for cpu 7 skipped: idling at 
> native_safe_halt+0xe/0x10
> [16236.897522] rcu: rcu_sched kthread starved for 60008 jiffies! g263697 
> f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=7
> [16236.897522] rcu: RCU grace-period kthread stack dump:
> [16236.897524] rcu_sched   I011  2 0x80004000
> [16236.897526] Call Trace:
> [16236.897532]  __schedule+0x26f/0x760
> [16236.897535]  schedule+0x4a/0xb0
> [16236.897536]  schedule_timeout+0x7b/0x140
> [16236.897539]  ? __next_timer_interrupt+0xd0/0xd0
> [16236.897541]  rcu_gp_kthread+0x4db/0xa90
> [16236.897543]  ? rcu_nocb_cb_kthread+0x210/0x210
> [16236.897545]  kthread+0x115/0x140
> [16236.897547]  ? __kthread_bind_mask+0x60/0x60
> [16236.897549]  ret_from_fork+0x22/0x40

Surely a VM would see only virtual cores and not be aware of the host.
However this is running on Windows, so who knows. You might want to
mention which VM it is (VirtualBox, VMware, Microsoft's, ...)

poc
___
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: NFS Mount Point Failed

[Stephen Morris]

On 9/6/20 10:14 pm, Tom Horsley wrote:

On Tue, 9 Jun 2020 21:54:30 +1000
Stephen Morris wrote:


nfsvers=1

I seriously doubt there is any support for nfs 1 left
in the code (could be wrong).

Depending on random variations every time the nfs
utilities get updates, I've had to sometimes
specify "proto=udp" as well as or instead of
the nfs version in order to speak to antique servers.
Thanks Tom, I'll try that option and see what happens. There is also one 
other thing I don't understand. If I run dolphin, under the Remote 
Section in the left hand panel it shows the entry /mnt/HD/HD_a2:/mnt/nfs 
on 192.168.1.12 which matches the fstab entry, and when I click on that 
entry, dolphin successfully displays the contents of my nas drive. Given 
the manual mount process doesn't work what is dolphin using to actually 
access the drive?


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: DMESG Output Indicating Potential CPU Errors?

[Stephen Morris]

On 9/6/20 10:34 pm, Patrick O'Callaghan wrote:

On Tue, 2020-06-09 at 22:10 +1000, Stephen Morris wrote:

Hi,
  I have the following messages in dmesg output, are they indicating
a cpu issue, or are they just indicating that because linux is running
in a vm under windows, and hence sharing the cpu cores with windows that
windows was using core 7 at the time the process checked?

[16236.896502] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[16236.896506] rcu: 7-...!: (0 ticks this GP) idle=d48/0/0x0
softirq=207101/207101 fqs=0
[16236.896508]  (detected by 4, t=60008 jiffies, g=263697, q=1058)
[16236.896510] Sending NMI from CPU 4 to CPUs 7:
[16236.896563] NMI backtrace for cpu 7 skipped: idling at
native_safe_halt+0xe/0x10
[16236.897522] rcu: rcu_sched kthread starved for 60008 jiffies! g263697
f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=7
[16236.897522] rcu: RCU grace-period kthread stack dump:
[16236.897524] rcu_sched   I011  2 0x80004000
[16236.897526] Call Trace:
[16236.897532]  __schedule+0x26f/0x760
[16236.897535]  schedule+0x4a/0xb0
[16236.897536]  schedule_timeout+0x7b/0x140
[16236.897539]  ? __next_timer_interrupt+0xd0/0xd0
[16236.897541]  rcu_gp_kthread+0x4db/0xa90
[16236.897543]  ? rcu_nocb_cb_kthread+0x210/0x210
[16236.897545]  kthread+0x115/0x140
[16236.897547]  ? __kthread_bind_mask+0x60/0x60
[16236.897549]  ret_from_fork+0x22/0x40

Surely a VM would see only virtual cores and not be aware of the host.
However this is running on Windows, so who knows. You might want to
mention which VM it is (VirtualBox, VMware, Microsoft's, ...)
Thanks Patrick, I'm using VirtualBox now, I was using Vmware Player, but 
I switched to VirtualBox because VirtualBox supports uefi where as 
Vmware doesn't. I was just wondering whether because the VM is sharing 
the cpu cores with windows, because it is running under windows, could 
the issue be that windows itself was using Core 7 and hence rcu couldn't 
get to it at the time it checked?


regards,
Steve



poc
___
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: NFS Mount Point Failed

[Roger Heflin]

I used linux in 2.0.X kernels (vintage 1998), and we used version=2,
so I am going to guess there was never a version 1 on linux.

And wikipedia says this interesting bit I did not know:
Sun used version 1 only for in-house experimental purposes.

So I guess that says no one outside of sun used version 1.

On Tue, Jun 9, 2020 at 7:14 AM Tom Horsley  wrote:
>
> On Tue, 9 Jun 2020 21:54:30 +1000
> Stephen Morris wrote:
>
> > nfsvers=1
>
> I seriously doubt there is any support for nfs 1 left
> in the code (could be wrong).
>
> Depending on random variations every time the nfs
> utilities get updates, I've had to sometimes
> specify "proto=udp" as well as or instead of
> the nfs version in order to speak to antique servers.
> ___
> 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: Interfaces

[Tim via users]

On Tue, 2020-06-09 at 11:40 +0100, Patrick O'Callaghan wrote:
> If you think the layout is problematic, I'd suggest discussing it on
> the Evo mailing list and eventually filing an RFE.
> 
> The icons are determined by the current style dictated by Gnome, not
> by Evolution itself. The same applies to fonts.

I suspected that's the case, so it'd be pointless complaining to
Evolution about the icons drawn by someone else.

I usually delete by hitting the delete key on the keyboard, anyway. 
But I mention it as an example of an unclear icon.  Here's another: 
I've got an app on the phone for controlling smart lights, it lets you
pick provided icons for your presets, but the images all have no
meaning, and you can't create your own images.  Or the controllers on
video games that I never play, there's nothing sensible about why a
game uses the square button, or the green button, etc., it's all
arbitrary.  They do nothing to contribute to ease of use.

Bye,
Tim.
 
-- 
 
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: NFS Mount Point Failed

[Tim via users]

On Tue, 2020-06-09 at 23:01 +1000, Stephen Morris wrote:
> There is also one other thing I don't understand. If I run dolphin,
> under the Remote Section in the left hand panel it shows the entry
> /mnt/HD/HD_a2:/mnt/nfs on 192.168.1.12 which matches the fstab entry,
> and when I click on that entry, dolphin successfully displays the
> contents of my nas drive. Given the manual mount process doesn't work
> what is dolphin using to actually access the drive?

I think if you view /etc/mtab you'll see the parameters being used for
everything that's currently mounted.
 
-- 
 
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: DMESG Output Indicating Potential CPU Errors?

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 23:04 +1000, Stephen Morris wrote:
> On 9/6/20 10:34 pm, Patrick O'Callaghan wrote:
> > On Tue, 2020-06-09 at 22:10 +1000, Stephen Morris wrote:
> > > Hi,
> > >   I have the following messages in dmesg output, are they indicating
> > > a cpu issue, or are they just indicating that because linux is running
> > > in a vm under windows, and hence sharing the cpu cores with windows that
> > > windows was using core 7 at the time the process checked?
> > > 
> > > [16236.896502] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
> > > [16236.896506] rcu: 7-...!: (0 ticks this GP) idle=d48/0/0x0
> > > softirq=207101/207101 fqs=0
> > > [16236.896508]  (detected by 4, t=60008 jiffies, g=263697, q=1058)
> > > [16236.896510] Sending NMI from CPU 4 to CPUs 7:
> > > [16236.896563] NMI backtrace for cpu 7 skipped: idling at
> > > native_safe_halt+0xe/0x10
> > > [16236.897522] rcu: rcu_sched kthread starved for 60008 jiffies! g263697
> > > f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=7
> > > [16236.897522] rcu: RCU grace-period kthread stack dump:
> > > [16236.897524] rcu_sched   I011  2 0x80004000
> > > [16236.897526] Call Trace:
> > > [16236.897532]  __schedule+0x26f/0x760
> > > [16236.897535]  schedule+0x4a/0xb0
> > > [16236.897536]  schedule_timeout+0x7b/0x140
> > > [16236.897539]  ? __next_timer_interrupt+0xd0/0xd0
> > > [16236.897541]  rcu_gp_kthread+0x4db/0xa90
> > > [16236.897543]  ? rcu_nocb_cb_kthread+0x210/0x210
> > > [16236.897545]  kthread+0x115/0x140
> > > [16236.897547]  ? __kthread_bind_mask+0x60/0x60
> > > [16236.897549]  ret_from_fork+0x22/0x40
> > Surely a VM would see only virtual cores and not be aware of the host.
> > However this is running on Windows, so who knows. You might want to
> > mention which VM it is (VirtualBox, VMware, Microsoft's, ...)
> Thanks Patrick, I'm using VirtualBox now, I was using Vmware Player, but 
> I switched to VirtualBox because VirtualBox supports uefi where as 
> Vmware doesn't. I was just wondering whether because the VM is sharing 
> the cpu cores with windows, because it is running under windows, could 
> the issue be that windows itself was using Core 7 and hence rcu couldn't 
> get to it at the time it checked?

AFAIK that wouldn't happen. The cores you are seeing in the guest are
virtualised. They aren't the real cores of your host CPU.

poc
___
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: Interfaces

[Patrick O'Callaghan]

On Wed, 2020-06-10 at 00:25 +0930, Tim via users wrote:
> On Tue, 2020-06-09 at 11:40 +0100, Patrick O'Callaghan wrote:
> > If you think the layout is problematic, I'd suggest discussing it on
> > the Evo mailing list and eventually filing an RFE.
> > 
> > The icons are determined by the current style dictated by Gnome, not
> > by Evolution itself. The same applies to fonts.
> 
> I suspected that's the case, so it'd be pointless complaining to
> Evolution about the icons drawn by someone else.

You could however make suggestions about the layout, i.,e. the order of
icons on the top row. That's determined by Evo.

poc
___
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: Interfaces

[Beartooth]

On Tue, 09 Jun 2020 11:40:15 +0100, Patrick O'Callaghan wrote:

> If you think the layout is problematic, I'd suggest discussing it on the
> Evo mailing list and eventually filing an RFE.
> 
> The icons are determined by the current style dictated by Gnome, not by
> Evolution itself. The same applies to fonts.

Years ago, I think about the time OSX first appeared, there were 
reports of an eminent industrial psychologist (whose name I've forgotten) 
who had said that all modern GUIs were downright wrong-headed. Does 
anybody remember? And was that insight ever followed up on? (I believe 
the guy died not long after writing that.)
-- 
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
___
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: Interfaces

[Jerry James]

On Tue, Jun 9, 2020 at 9:33 AM Beartooth  wrote:
> Years ago, I think about the time OSX first appeared, there were
> reports of an eminent industrial psychologist (whose name I've forgotten)
> who had said that all modern GUIs were downright wrong-headed. Does
> anybody remember? And was that insight ever followed up on? (I believe
> the guy died not long after writing that.)

I don't recall that one, but I remember this little gem from Doug Gwyn in 1991:

https://groups.google.com/d/msg/comp.unix.wizards/EMpOm6PVQYo/zOBTPgoDpWMJ

I liked his first sentence so much that it went into my quotes file. :-)
-- 
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: Interfaces

[Tom Horsley]

I don't know about GUIs in general, but I do know that
only one icon means anything to anyone :-). They invented
the envelope icon to mean mail, and everyone recognized it,
so they set off the dynamite in the icon factory and
exploded cryptic icons all over everything, and not
one of them can be recognized (other than mail).
___
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: What is backup_vg-backup? Can it be so big?

[Beartooth]

On Mon, 08 Jun 2020 11:18:21 -0700, Samuel Sieb wrote:

> On 6/8/20 9:35 AM, Beartooth wrote:
>> On Sun, 07 Jun 2020 14:07:29 -0700, Samuel Sieb wrote:
>>> It's not a file.  It appears to be an lvm volume, kind of like a
>>> partition.  It's mounted at /.snapshot, so what does "ls -a
>>> /.snapshot"
>>> show you?
>> 
>>  Now it gets weird. I tried that command both as user and as root,
>> and got only
>> 
>>  ls: cannot access '/.snapshot': No such file or directory
> 
> Not weird, just my mistake.  I retyped from memory instead of looking at
> it or doing copy and paste.  "ls -a /.snapshots"  (It's plural...)

# ls -a /.snapshots
.  ..  alpha.0  lost+found


> Also, what about "lsof /.snapshots"?

# lsof /.snapshots
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/65536/
gvfs
  Output information may be incomplete.

It says "incomplete"; but the lines above are its whole output.
 
>>  For most of my time, there has been no question whether I would
>> snarl up a machine, but only when. So every time I bought a new one, I
>> kept the old one and the one before it, in order to be able to holler
>> for help.
> 
> Sounds like a good plan. :-)
> 
>> Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors Disk
>> model: WDC WD20EZRZ-00Z Units: sectors of 1 * 512 = 512 bytes Sector
>> size (logical/physical): 512 bytes / 4096 bytes I/O size
>> (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk
>> identifier: 772CAD71-6AAB-4868-9D69-C46B183C9581
>> 
>> Device  StartEndSectors  Size Type /dev/sdb12048   
>>  251903 249856  122M Microsoft reserved /dev/sdb2  251904
>> 3907026943 3906775040  1.8T Linux filesystem
> 
> Was this drive brought over from a windows system?  But anyway, there's
> your storage.

It's my wife's previous machine, a System76 PC from several years 
back. (She thinks five to eight years.) Being from them, it arrived with 
Ubuntu (only, afaik). But I had so much trouble installing Fedora 
(trouble I had not had with an early System76 netbook) that I had to call 
a friend here, who came and did the install for me. 

All I can think of, and it seems unlikely, is that System76 might 
for some reason have started with a Windows machine, not bare metal. 
Maybe that's why. 

> It appears like you took a large hard drive and set it up for some
> backup system, but I have no idea what one would work like that.

I don't know what the friend did. The whole PC is now a backup; so 
I'd have no hesitation to DBAN it, install F32, and recopy data from my 
present #1 machine. I did think it seemed to have surprisingly little 
storage when I did that df -h; but if I understand better now, that 1.7T 
is real -- and, I hope, available for other uses. Is that so? Maybe I 
don't need to wipe it?
-- 
Beartooth Staffwright, Not Quite Clueless Linux Power User
I have precious (very precious) little idea where up is.

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

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 15:32 +, Beartooth wrote:
> On Tue, 09 Jun 2020 11:40:15 +0100, Patrick O'Callaghan wrote:
> 
> > If you think the layout is problematic, I'd suggest discussing it on the
> > Evo mailing list and eventually filing an RFE.
> > 
> > The icons are determined by the current style dictated by Gnome, not by
> > Evolution itself. The same applies to fonts.
> 
>   Years ago, I think about the time OSX first appeared, there were 
> reports of an eminent industrial psychologist (whose name I've forgotten) 
> who had said that all modern GUIs were downright wrong-headed. Does 
> anybody remember? And was that insight ever followed up on? (I believe 
> the guy died not long after writing that.)

Don Norman? He did have a lot of influence on HCI design (or at least
he was cited a good deal). This is probably his best-known book:

https://www.amazon.co.uk/Design-Everyday-Things-Revised-Expanded/dp/0465050654/ref=sr_1_1?dchild=1&keywords=design+of+everyday+things&qid=1591720486&sr=8-1

poc


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

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 09:52 -0600, Jerry James wrote:
> On Tue, Jun 9, 2020 at 9:33 AM Beartooth  wrote:
> > Years ago, I think about the time OSX first appeared, there were
> > reports of an eminent industrial psychologist (whose name I've forgotten)
> > who had said that all modern GUIs were downright wrong-headed. Does
> > anybody remember? And was that insight ever followed up on? (I believe
> > the guy died not long after writing that.)
> 
> I don't recall that one, but I remember this little gem from Doug Gwyn in 
> 1991:
> 
> https://groups.google.com/d/msg/comp.unix.wizards/EMpOm6PVQYo/zOBTPgoDpWMJ
> 
> I liked his first sentence so much that it went into my quotes file. :-)

Brian Kernighan's version of that (which I think is earlier) is "What
You See is All You Get".

poc
___
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: What is backup_vg-backup? Can it be so big?

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 16:16 +, Beartooth wrote:
> I did think it seemed to have surprisingly little 
> 
> storage when I did that df -h; but if I understand better now, that 1.7T 
> 
> is real -- and, I hope, available for other uses. Is that so? Maybe I 
> 
> don't need to wipe it?

If 'df' says that space is there, then you can believe it. Wiping it or
not is up to you, but a new install will be happier on a clean
partition (or in fact several partitions in order to keep /home
separate from root). However AFAIK the standard Fedora installer will
do this for you.

poc
___
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: Interfaces

[Doug McGarrett]

On 6/9/20 12:01 PM, Tom Horsley wrote:

I don't know about GUIs in general, but I do know that
only one icon means anything to anyone :-). They invented
the envelope icon to mean mail, and everyone recognized it,
so they set off the dynamite in the icon factory and
exploded cryptic icons all over everything, and not
one of them can be recognized (other than mail).

You have a point, altho not completely correct. Among the icons on my 
KDE screen,
the Package Manager looks like a wrapped parcel, two CD icons (K3b and 
Brasero)
sort of look like CDs, KCalc looks like a pocket calculator, sort of, 
KPatience card
games looks like playing cards. And Thunderbird, while showing a letter, 
has it
wrapped in a wig that covers where ears would be. Is that supposed to be 
feathers?

Anyway, one gets used to the image associated with a given app--much better
than have every app look like a manila folder--thanx to Microsoft for 
that! Even they

realized their error rather quickly.
--doug
___
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: Interfaces

[Matti Pulkkinen]

Tim via users kirjoitti 9.6.2020 klo 17.55:

the controllers on video games that I never play, there's nothing
sensible about why a game uses the square button, or the green
button, etc., it's all arbitrary.  They do nothing to contribute to
ease of use.
I don't know about you, but I can't think of an icon or symbol that 
would convey useful semantic meaning for a button which you sometimes 
use to jump, sometimes to activate a contextual action, sometimes to 
select a menu item, sometimes to shoot, sometimes to either crouch or go 
prone depending on how long you hold the button down, sometimes to apply 
gas in a car, sometimes to pass a ball to another player player, or 
whatever else. There are a limited number of buttons you can fit on a 
controller of reasonable size, and an unlimited number of potential 
in-game actions players may be able to take with said controller. I 
would argue that a four-button controller – perhaps labelled with 
arbitrary geometric shapes – contributes to ease of use much better than 
a controller with who knows how many buttons labeled with their precise 
in-game action. Since learning to play with a regular controller as a 
child, I've never actually had any difficulty in learning the controls 
to any game using such a controller. Playing with a controller becomes 
second nature, even if it contains arbitrary elements, because you just 
get used to it.


As for application and toolbar icons, usually after a while of looking 
at them, most will lose the metaphoric link between representation and 
reality, at least in my mind. In fact it didn't even register with me 
that the Files icon in Gnome is actually a filing cabinet until someone 
mentioned it earlier. It was just the symbol for the Files application.



--
Terveisin / Regards,
Matti Pulkkinen
___
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: DMESG Output Indicating Potential CPU Errors?

[Samuel Sieb]

On 6/9/20 5:10 AM, Stephen Morris wrote:

Hi,
     I have the following messages in dmesg output, are they indicating 
a cpu issue, or are they just indicating that because linux is running 
in a vm under windows, and hence sharing the cpu cores with windows that 
windows was using core 7 at the time the process checked?


[16236.896502] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[16236.896506] rcu: 7-...!: (0 ticks this GP) idle=d48/0/0x0 
softirq=207101/207101 fqs=0

[16236.896508]  (detected by 4, t=60008 jiffies, g=263697, q=1058)
[16236.896510] Sending NMI from CPU 4 to CPUs 7:
[16236.896563] NMI backtrace for cpu 7 skipped: idling at 
native_safe_halt+0xe/0x10
[16236.897522] rcu: rcu_sched kthread starved for 60008 jiffies! g263697 
f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=7


It's possible that Windows was using that core for long enough that the 
kernel thought that it wasn't getting enough time.  Did you share all 
the cores with the VM?  That's not a good idea.

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

[Samuel Sieb]

On 6/9/20 10:09 AM, Doug McGarrett wrote:
games looks like playing cards. And Thunderbird, while showing a letter, 
has it
wrapped in a wig that covers where ears would be. Is that supposed to be 
feathers?


If you look closer, you'll see that it's a bird with its wings wrapping 
around the envelope.

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

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

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]

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

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: NFS Mount Point Failed

[Tom H]

On Tue, Jun 9, 2020 at 1:55 PM Stephen Morris  wrote:
>
> I have the following statement in fstab:
>
> 192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs
> nfsvers=1,x-systemd.automount,defaults 0 0
>
> When I issue the command 'mount /mnt/nfs' it fails with the
> following messages shown in dmesg, which indicate that the mount
> seems to be trying to proceed via nfs4, why is it doing this when I
> have the option nfsvers=1?
>
> [48439.472418] FS-Cache: Netfs 'nfs' registered for caching
> [48439.472732] *** VALIDATE nfs ***
> [48439.472741] *** VALIDATE nfs4 ***
> [48439.476329] Key type dns_resolver registered
> [48439.639981] NFS: Registering the id_resolver key type
> [48439.639993] Key type id_resolver registered
> [48439.639994] Key type id_legacy registered
> [48439.844036] NFS4: Couldn't follow remote path
> [48439.852856] NFS4: Couldn't follow remote path
> [48439.898650] NFS4: Couldn't follow remote path
> [48480.763754] NFS4: Couldn't follow remote path
> [48480.774645] NFS4: Couldn't follow remote path

nfsv1 has never existed. Use "nfsvers=3" or "nfsvers=4".
___
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 ?

[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: NFS Mount Point Failed

[Tom H]

On Tue, Jun 9, 2020 at 2:14 PM Tom Horsley  wrote:
> On Tue, 9 Jun 2020 21:54:30 +1000
> Stephen Morris wrote:
>
>> nfsvers=1
>
> I seriously doubt there is any support for nfs 1 left
> in the code (could be wrong).
>
> Depending on random variations every time the nfs
> utilities get updates, I've had to sometimes
> specify "proto=udp" as well as or instead of
> the nfs version in order to speak to antique servers.

nfsd is tcp-only these days. Check out "rpcinfo -s".
___
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 ?

[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: NFS Mount Point Failed

[Stephen Morris]

On 10/6/20 12:40 am, Roger Heflin wrote:

I used linux in 2.0.X kernels (vintage 1998), and we used version=2,
so I am going to guess there was never a version 1 on linux.

And wikipedia says this interesting bit I did not know:
Sun used version 1 only for in-house experimental purposes.

So I guess that says no one outside of sun used version 1.
Hi Roger, earlier versions of Fedora (F28) supported version 1 of nfs as 
well as version 4 which they used by default, and I had to set nfsvers=1 
in the mount point in fstab to be able to mount my nas as it only 
supports version 1 of nfs.ff


regards,
Steve



On Tue, Jun 9, 2020 at 7:14 AM Tom Horsley  wrote:

On Tue, 9 Jun 2020 21:54:30 +1000
Stephen Morris wrote:


nfsvers=1

I seriously doubt there is any support for nfs 1 left
in the code (could be wrong).

Depending on random variations every time the nfs
utilities get updates, I've had to sometimes
specify "proto=udp" as well as or instead of
the nfs version in order to speak to antique servers.
___
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: NFS Mount Point Failed

[Stephen Morris]

On 10/6/20 7:12 am, Tom H wrote:

On Tue, Jun 9, 2020 at 1:55 PM Stephen Morris  wrote:

I have the following statement in fstab:

192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs
nfsvers=1,x-systemd.automount,defaults 0 0

When I issue the command 'mount /mnt/nfs' it fails with the
following messages shown in dmesg, which indicate that the mount
seems to be trying to proceed via nfs4, why is it doing this when I
have the option nfsvers=1?

[48439.472418] FS-Cache: Netfs 'nfs' registered for caching
[48439.472732] *** VALIDATE nfs ***
[48439.472741] *** VALIDATE nfs4 ***
[48439.476329] Key type dns_resolver registered
[48439.639981] NFS: Registering the id_resolver key type
[48439.639993] Key type id_resolver registered
[48439.639994] Key type id_legacy registered
[48439.844036] NFS4: Couldn't follow remote path
[48439.852856] NFS4: Couldn't follow remote path
[48439.898650] NFS4: Couldn't follow remote path
[48480.763754] NFS4: Couldn't follow remote path
[48480.774645] NFS4: Couldn't follow remote path

nfsv1 has never existed. Use "nfsvers=3" or "nfsvers=4".
Hi Tom, In another thread to Roger I've mentioned that in F28, and even 
though I didn't specify it, probably F30, Fedora used nfs4 by default 
which would not enable mounting of my nas, I had to specify nfsvers=1 in 
the mount instruction in fstab for the nas to be mounted, which now 
seems to no longer work. Following your suggestion I have tried 
nfsvers=3 and that has enabled the nas to be mounted. Now I have to try 
and figure out the right specification for the cifs mount point to be 
able to be mounted via the Windows share exposed by the nas. Thankyou 
for all your help.


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: DMESG Output Indicating Potential CPU Errors?

[Stephen Morris]

On 10/6/20 4:19 am, Samuel Sieb wrote:

On 6/9/20 5:10 AM, Stephen Morris wrote:

Hi,
 I have the following messages in dmesg output, are they 
indicating a cpu issue, or are they just indicating that because 
linux is running in a vm under windows, and hence sharing the cpu 
cores with windows that windows was using core 7 at the time the 
process checked?


[16236.896502] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
[16236.896506] rcu: 7-...!: (0 ticks this GP) idle=d48/0/0x0 
softirq=207101/207101 fqs=0

[16236.896508]  (detected by 4, t=60008 jiffies, g=263697, q=1058)
[16236.896510] Sending NMI from CPU 4 to CPUs 7:
[16236.896563] NMI backtrace for cpu 7 skipped: idling at 
native_safe_halt+0xe/0x10
[16236.897522] rcu: rcu_sched kthread starved for 60008 jiffies! 
g263697 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=7


It's possible that Windows was using that core for long enough that 
the kernel thought that it wasn't getting enough time.  Did you share 
all the cores with the VM?  That's not a good idea.
I did specify that the VM had access to 8 cores, as I wanted the VM to 
be able to time slice all cores if I was doing graphic intensive 
processes like photo editing, video playing or video format conversions 
if I could figure out how to drive ffmpeg properly.


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: DMESG Output Indicating Potential CPU Errors?

[Gordon Messmer]

On 6/9/20 5:10 AM, Stephen Morris wrote:
I have the following messages in dmesg output, are they indicating a 
cpu issue, or are they just indicating that because linux is running 
in a vm under windows, and hence sharing the cpu cores with windows 
that windows was using core 7 at the time the process checked? 



Yes, probably something like that.  Typically, in order to schedule a 
virtual machine run time, all of the CPUs that the guest will use must 
be free simultaneously.  As you allot more CPUs to a virtual machine, 
that becomes harder to schedule, and the guest can experience greater 
latency between run time.  If your host system doesn't have at least 12 
CPU cores, I would recommend against allotting 8 to the guest.  Fewer 
cores will be easier to schedule, and may perform better.


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

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

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

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

[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: What is backup_vg-backup? Can it be so big?

[Samuel Sieb]

On 6/9/20 9:16 AM, Beartooth wrote:

On Mon, 08 Jun 2020 11:18:21 -0700, Samuel Sieb wrote:

it or doing copy and paste.  "ls -a /.snapshots"  (It's plural...)


# ls -a /.snapshots
.  ..  alpha.0  lost+found


I should have said "ls -l".  I'm just curious what that is.  Can you do 
"file /.snapshots/alpha.0" and if it's a directory, do "ls -la 
/.snapshots/alpha.0""?


To find out how it's getting mounted, do "mount | grep snapshot" and 
"cat /etc/fstab". (You don't need to include the whole thing, just see 
if there's a relevant line in there.)



Also, what about "lsof /.snapshots"?


# lsof /.snapshots
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/65536/
gvfs
   Output information may be incomplete.

It says "incomplete"; but the lines above are its whole output.


Yes, you can ignore that warning.


It appears like you took a large hard drive and set it up for some
backup system, but I have no idea what one would work like that.


I don't know what the friend did. The whole PC is now a backup; so
I'd have no hesitation to DBAN it, install F32, and recopy data from my
present #1 machine. I did think it seemed to have surprisingly little
storage when I did that df -h; but if I understand better now, that 1.7T
is real -- and, I hope, available for other uses. Is that so? Maybe I
don't need to wipe it?


If there's nothing important on the computer or the hard drive, I would 
suggest reinstalling it.  You can use the SSD for the root filesystem 
and put /home on the big drive.

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

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