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

[Stephen Morris]

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


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

Edited /etc/default/grub to this:

GRUB_TIMEOUT="5"
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT="saved"
GRUB_DISABLE_SUBMENU="true"
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rd.driver.blacklist=nouveau 
modprobe.blacklist=nouveau nvidia-drm.modeset=1 rd.l>

GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG="true"

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

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

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


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

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

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

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


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

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

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

fi

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


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


regards,
Steve











___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org


___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

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

[ja]

> 
> 
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Just a thought:

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

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

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

Not my code but probably from this list.

John
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: DMESG Output Indicating Potential CPU Errors?

[Patrick O'Callaghan]

On Tue, 2020-06-09 at 16:52 -0700, Gordon Messmer wrote:
> 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.

In KVM/QEMU you can also pin specific cores to your VM to prevent
competition between the host and guest (mainly by avoiding cache
pollution as I understand it). I do this for Windows gaming under
Fedora, but I don't know if that's supported in VB on a Windows host.

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 Update this morning -

[Bob Goodwin]

DNF failed first try, I ran clean metadata and re-tried, got same result:

Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
The downloaded packages were saved in cache until the next successful 
transaction.

You can remove cached packages by executing 'dnf clean packages'.
Error: SQLite error on "/var/lib/dnf/history.sqlite": Reading a row 
failed: database disk image is malformed


I have no idea why this happening, have done nothing unusual? *Bob*

--

Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
FEDORA-32/64bit LINUX XFCE Fastmail POP3
___
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 7:56 pm, Patrick O'Callaghan wrote:

On Tue, 2020-06-09 at 16:52 -0700, Gordon Messmer wrote:

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.

In KVM/QEMU you can also pin specific cores to your VM to prevent
competition between the host and guest (mainly by avoiding cache
pollution as I understand it). I do this for Windows gaming under
Fedora, but I don't know if that's supported in VB on a Windows host.
I think virtualbox has the equivalent in that it has an execution cap to 
limit the amount of physical cpu time the virtual cpu is allowed to use, 
and by setting the percentage to 100% disables the cap, which I assume 
means the vm will not release the cpu back to windows.


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

[Patrick O'Callaghan]

On Wed, 2020-06-10 at 21:18 +1000, Stephen Morris wrote:
> On 10/6/20 7:56 pm, Patrick O'Callaghan wrote:
> > On Tue, 2020-06-09 at 16:52 -0700, Gordon Messmer wrote:
> > > 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.
> > In KVM/QEMU you can also pin specific cores to your VM to prevent
> > competition between the host and guest (mainly by avoiding cache
> > pollution as I understand it). I do this for Windows gaming under
> > Fedora, but I don't know if that's supported in VB on a Windows host.
> I think virtualbox has the equivalent in that it has an execution cap to 
> limit the amount of physical cpu time the virtual cpu is allowed to use, 
> and by setting the percentage to 100% disables the cap, which I assume 
> means the vm will not release the cpu back to windows.

Not really the same thing in how it works, but it certainly would help.

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

[Gordon Messmer]

On 6/10/20 2:56 AM, Patrick O'Callaghan wrote:

In KVM/QEMU you can also pin specific cores to your VM to prevent
competition between the host and guest (mainly by avoiding cache
pollution as I understand it).



CPU affinity can improve performance for NUMA systems, and does improve 
cache efficiency, but it does not (to my knowledge) prevent competition 
between the host and guest.


https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/virtualization/ch33s08

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_tuning_and_optimization_guide/sect-virtualization_tuning_optimization_guide-numa-numa_and_libvirt

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

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

[Jonathan Billings]

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

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

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

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

-- 
Jonathan Billings 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: [SOLVED] Audacity can't play audio on Fedora 32

[Sreyan Chakravarty]

On 5/31/20 10:42 PM, Łukasz Posadowski wrote:

Sorry, I didn't read entire thread, so it is possible that someone
mentioned that. It is a problem with many distributions and possibly
You are missing one package. Try:
dnf install alsa-plugins-pulseaudio.x86_64
After that, Audacity will detect any sound card and interface, that
Pulse is able to detect (like every one).


It seems I am out of luck:

$ sudo dnf install alsa-plugins-pulseaudio

Package alsa-plugins-pulseaudio-1.2.2-1.fc32.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!

Its already installed.

Now what do I do ?

--
Regards,
Sreyan
___
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 to install Wifi firmware so it's not overwritten?

[Richard Shaw]

So the short version...

The current linux firmware package doesn't work with the Wifi on the MS
Surface GO, and the instructions to copy the downloaded board.bin and copy
over firmware-4.bin were incorrect. It actually saw the Wifi adapter after
I did that and it tried scanning for wireless networks but never got any
further.

Since the Killerwifi board.bin and the linux firmware board.bin were the
exact same size (whereas the firmware files were orders of magnitude
larger), I tried replacing board.bin instead and can report after rebooting
that the Wifi now works.

So one thing I am wondering is what is the naming convention for these
files? Could I just save it as board-2.bin and it work? Is there some sort
of search hiearchy?

>From what I can tell it looks like udev takes care of it but I don't know
enough about udev to intuit what kind of naming scheme might work without
overriding the existing board file.

Thanks,
Richard
___
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]

Sorry, you are confusing the option not causing an issue with it
actaully selecting version=1.

The option may not have caused an issue on f28, but as wikipedia says
and someone else says there never was NFS version 1 (on linux).  It
would seem the behavior when you give it an incorrect mount now causes
it to actually fail, and did not before.

Note I just checked on an old RHEL4 and RHEL5 box (2.6.9/2.6.18
kernel, I believe RHEL4 is based off of Fedora Core 3) and the man
pages says this on both.

   Three different versions of the NFS protocol are supported by the
Linux NFS client: NFS version 2, NFS version 3, and NFS version 4.  To
mount via NFS version 2, use the nfs  file  system
   type  and  specify nfsvers=2.  To mount via NFS version 3, use
the nfs file system type and specify nfsvers=3.  Version 3 is the
default protocol version for the nfs file system type when
   nfsvers= is not specified on the mount command.  To mount via
NFS version 4, use the nfs4 file system type.  The nfsvers= keyword is
not supported for the nfs4 file system type.

So many years prior to F28 there was no mention of 1 existing.

On Tue, Jun 9, 2020 at 6:40 PM Stephen Morris  wrote:
>
> 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
___
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: [SOLVED] Audacity can't play audio on Fedora 32

[George N. White III]

On Wed, 10 Jun 2020 at 10:57, Sreyan Chakravarty  wrote:

>
> On 5/31/20 10:42 PM, Łukasz Posadowski wrote:
> > Sorry, I didn't read entire thread, so it is possible that someone
> > mentioned that. It is a problem with many distributions and possibly
> > You are missing one package. Try:
> > dnf install alsa-plugins-pulseaudio.x86_64
> > After that, Audacity will detect any sound card and interface, that
> > Pulse is able to detect (like every one).
>
> It seems I am out of luck:
>
> $ sudo dnf install alsa-plugins-pulseaudio
>
> Package alsa-plugins-pulseaudio-1.2.2-1.fc32.x86_64 is already installed.
> Dependencies resolved.
> Nothing to do.
> Complete!
>
> Its already installed.
>
> Now what do I do ?
>

Early on you were asked to run pavucontrol and bash didn't find it.
 Apologies if I missed further mention of pavucontrol, but have you tried
"dnf install pavucontrol"?   You also mentioned that audacity might be a
flatpak.   In that case there may be a miscommunication between the flatpak
and fedora's audio support.

It is worth looking for reports of linux installs (of any distro) on your
laptop model for discussions of audio problems.  I have a desktop that
disables the analog audio output if it is sending audio to HDMI --
unfortunately my monitor has terrible speakers and (unlike TV's) no analog
audio output.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: How to install Wifi firmware so it's not overwritten?

[George N. White III]

On Wed, 10 Jun 2020 at 11:55, Richard Shaw  wrote:

> So the short version...
>
> The current linux firmware package doesn't work with the Wifi on the MS
> Surface GO, and the instructions to copy the downloaded board.bin and copy
> over firmware-4.bin were incorrect. It actually saw the Wifi adapter after
> I did that and it tried scanning for wireless networks but never got any
> further.
>
> Since the Killerwifi board.bin and the linux firmware board.bin were the
> exact same size (whereas the firmware files were orders of magnitude
> larger), I tried replacing board.bin instead and can report after rebooting
> that the Wifi now works.
>

Did you try a newer file from the githhub link?  Are there any license
restrictions on Killerwifi's board.bin that prevent you from sending the
link to the upstream URL I posted.


>
> So one thing I am wondering is what is the naming convention for these
> files? Could I just save it as board-2.bin and it work? Is there some sort
> of search hiearchy?
>
> From what I can tell it looks like udev takes care of it but I don't know
> enough about udev to intuit what kind of naming scheme might work without
> overriding the existing board file.
>

The best outcome would be to get upstream to add support for the
"Killerwifi" board (if they don't already have by now) so you don't have to
worry about losing wifi with each update.

-- 
George N. White III
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: DMESG Output Indicating Potential CPU Errors?

[Patrick O'Callaghan]

On Wed, 2020-06-10 at 05:57 -0700, Gordon Messmer wrote:
> On 6/10/20 2:56 AM, Patrick O'Callaghan wrote:
> > In KVM/QEMU you can also pin specific cores to your VM to prevent
> > competition between the host and guest (mainly by avoiding cache
> > pollution as I understand it).
> 
> CPU affinity can improve performance for NUMA systems, and does improve 
> cache efficiency, but it does not (to my knowledge) prevent competition 
> between the host and guest.
> 
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/virtualization/ch33s08
> 
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_tuning_and_optimization_guide/sect-virtualization_tuning_optimization_guide-numa-numa_and_libvirt

My understanding is based on:

https://vfio.blogspot.com/2015/05/vfio-gpu-how-to-series-part-4-our-first.html

(search for vcpupin partway down the page). This doesn't relate to NUMA
systems but to cache efficiency (also mentioned in your second
reference), though it may be a matter of terminology. Perhaps I should
have said "avoid" or "mitigate" rather than "prevent".

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 ?

[linux guy]

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

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

That would explain a few things.

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

What target or directory should I be specifying ?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

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

[linux guy]

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

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

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

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

What/where do you want me to check ?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

Re: NFS Mount Point Failed

[Tom H]

On Wed, Jun 10, 2020 at 1:40 AM Stephen Morris  wrote:
> 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".
>
> 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

Indeed, nfsv4 has been the default for many releases. So it makes
sense that the mount would fallback to nfsv4 if the requested version
isn't available.


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

I'm glad that "nfsvers=3" is working. Are you sure that you're not
misremembering "nfsvers=1"?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

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

[Jonathan Billings]

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

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

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

Look for another EFI partition.

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

-- 
Jonathan Billings 
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org

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

[linux guy]

# blkid
/dev/nvme0n1p1: UUID="D76F-0EDB" BLOCK_SIZE="512" TYPE="vfat"
PARTLABEL="EFI System Partition"
PARTUUID="c2d93266-9038-4fc9-923a-797fb0595aa0"
/dev/nvme0n1p2: UUID="39373709-00f2-43a6-8f8d-dae45eb32add"
BLOCK_SIZE="4096" TYPE="ext4"
PARTUUID="d20f2f5b-be53-4714-80ae-2dd675aba973"
/dev/nvme0n1p3: UUID="3VH3r7-BOSc-PaRC-Ragt-15Co-Th5g-YX4nVs"
TYPE="LVM2_member" PARTUUID="2d9c0127-b6a4-4afd-a1e0-c1285615b572"
/dev/mapper/fedora_localhost--live-root:
UUID="8d74a47c-8d3f-4b5a-acc5-02bc6888c8bb" BLOCK_SIZE="4096" TYPE="ext4"
/dev/mapper/fedora_localhost--live-swap:
UUID="c236d9d8-66f4-409b-bac5-88c4662c4fe5" TYPE="swap"
/dev/mapper/fedora_localhost--live-home:
UUID="6c65d0c7-865d-4c32-9bb8-227d63dfa37b" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
Looks like only 1 EFI partition.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org