Install error
Hi, I am installing F36, from the "netinstall disk" on a HP laptop (dual boot, Xfce). After downloading and installing it gives this: error in POSTTRANS scriptlet in rpm package grub2 common and aborts the installation, twice. At reboot goes to the grub prompt. Is there something we can do? G ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong
On 4/7/22 22:42, Tim via users wrote: On Mon, 2022-07-04 at 18:15 +1000, Stephen Morris wrote: The package must have been updated as when I looked yesterday it didn't supply any of those files, unless I looked at the file list from the wrong package dnf history See what got updated when. Thanks Tim, I'll check that out. I've booted directly into Fedora this morning and the wifi is not working again, its back to the situation of getting probe error -110 without ever trying to load the adapter's firmware. I've seen another thread on the net where someone else was raising an issue with the same wifi adapter with Fedora 34, where that person was saying it seemed to work if he booted into Windows first, and it's now looking like I'm getting the same issue. I'm assuming this is a kernel issue, so what is the linux kernel not doing that windows does do to activate the hardware (its not an issue specific to Fedora as I get the same lack of wifi issue under Ubuntu as well)? regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Akmod Built Nvidia Module Tainting the Kernel at Boot Time
Hi, I believe I am using akmod to build the nvidia kernel module when the kernel version changes and that built module is tainting the kernel because of missing signature or keys, which I am assuming are secure boot keys, but I also followed some instructions I found on the net to get nvidia keys into secure boot when I first installed the nvidia modules. I don't know whether I was getting the following messages at that time or not, as I found these when I was looking for something else. Is the issue with the following messages that the secure boot keys have to be rebuilt every time the nvidia modules are updated? Just as a follow on from this, I've read that nvidia have open sourced their linux drivers, how long will it take for those to be incorporated into the distribution to remove the requirement for the Rpm Fusion versions? [ 13.973631] nvidia: loading out-of-tree module taints kernel. [ 13.973636] nvidia: module license 'NVIDIA' taints kernel. [ 13.978637] nvidia: module verification failed: signature and/or required key missing - tainting kernel [ 13.988926] nvidia-nvlink: Nvlink Core is being initialized, major device number 511 [ 13.989619] nvidia:09:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [ 14.040430] NVRM: loading NVIDIAUNIX x86_64 Kernel Module 510.68.02 Wed Apr 20 21:10:34 UTC 2022 [ 14.677665] caller _nv000651rm+0x1ad/0x200 [nvidia] mapping multiple BARs [ 14.928567] nvidia_uvm: module uses symbols from proprietary module nvidia, inheriting taint. regards, Steve___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Dual booting
On 4/7/22 22:37, Tim via users wrote: Barry wrote: I ran duel boot win10+fedora like this, now I duel boot win11+fedora in this way. Patrick O'Callaghan: Duel? Are they fighting each other? Sorry :-) I think it's rather apt. Not sorry ;-) I'm tri-booting between Win11, Fedora and Ubuntu. I used to have the bios time configured to local time and found that Linux assumed the bios time was UTC, and didn't provide an easy way of changing that, and hence was always 10 hours out, Windows used to allow configuration of that. As indicated by other people setting the bios time to UTC used to correct the issues. The motherboard I have now seems to have the time hard set and doesn't provide any way of manually changing the time, and at the moment I haven't paid attention to whether or not its set to UTC time. I don't have separate home partitions, but being UEFI what I do have is separate UEFI system partitions for all 3 OS's, I didn't try using one partition for all 3, and I also found that Fedora would not start it's installation process unless there was a partition configured as a UEFI system partition. regards, Steve ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Wifi not Started at Boot and Networkmanager Wifi Last Used Stats Wrong
Error -110 is timeout, meaning the device did not respond to the commands. It usually means the hardware in question is in a bad/locked up state so the kernel is unable to init it. If the issue is after a suspend/resume then try below: Other notes indicate this: Please create the file /etc/modprobe.d/iwlwifi.conf with content options iwlwifi remove_when_gone=1 as some of these issues are suspend/resume issues where it does not get init'ed right on resume. On Tue, Jul 5, 2022 at 5:39 PM Stephen Morris wrote: > > On 4/7/22 22:42, Tim via users wrote: > > On Mon, 2022-07-04 at 18:15 +1000, Stephen Morris wrote: > >> The package must have been updated as when I looked yesterday it > >> didn't supply any of those files, unless I looked at the file list > >> from the wrong package > > dnf history > > > > See what got updated when. > > > Thanks Tim, I'll check that out. > > I've booted directly into Fedora this morning and the wifi is not > working again, its back to the situation of getting probe error -110 > without ever trying to load the adapter's firmware. > I've seen another thread on the net where someone else was raising an > issue with the same wifi adapter with Fedora 34, where that person was > saying it seemed to work if he booted into Windows first, and it's now > looking like I'm getting the same issue. I'm assuming this is a kernel > issue, so what is the linux kernel not doing that windows does do to > activate the hardware (its not an issue specific to Fedora as I get the > same lack of wifi issue under Ubuntu as well)? > > regards, > Steve > > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Akmod Built Nvidia Module Tainting the Kernel at Boot Time
On 7/5/22 16:54, Stephen Morris wrote: I believe I am using akmod to build the nvidia kernel module when the kernel version changes and that built module is tainting the kernel because of missing signature or keys, which I am assuming are secure boot keys, but I also followed some instructions I found on the net to get nvidia keys into secure boot when I first installed the nvidia modules. I don't know whether I was getting the following messages at that time or not, as I found these when I was looking for something else. No. Any use of the binary blob nVidia drivers, including either knod or akmod, taints the kernel because the maintainers don't have access to the source code. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Akmod Built Nvidia Module Tainting the Kernel at Boot Time
On Tue, Jul 5, 2022 at 7:55 PM Stephen Morris wrote: > Hi, > I believe I am using akmod to build the nvidia kernel module when the > kernel version changes and that built module is tainting the kernel because > of missing signature or keys, which I am assuming are secure boot keys, but > I also followed some instructions I found on the net to get nvidia keys > into secure boot when I first installed the nvidia modules. I don't know > whether I was getting the following messages at that time or not, as I > found these when I was looking for something else. > Is the issue with the following messages that the secure boot keys > have to be rebuilt every time the nvidia modules are updated? > It is the nvidia proprietary code that kernel developers can't examine -- nothing to do with the secure boot keys: https://ask.fedoraproject.org/t/nvidia-taints-kernel/12753 > Just as a follow on from this, I've read that nvidia have open sourced > their linux drivers, how long will it take for those to be incorporated > into the distribution to remove the requirement for the Rpm Fusion versions? > > [ 13.973631] nvidia: loading out-of-tree module taints kernel. > [ 13.973636] nvidia: module license 'NVIDIA' taints kernel. > [ 13.978637] nvidia: module verification failed: signature and/or > required key missing - tainting kernel > [ 13.988926] nvidia-nvlink: Nvlink Core is being initialized, major > device number 511 > [ 13.989619] nvidia :09:00.0: vgaarb: changed VGA decodes: > olddecodes=io+mem,decodes=none:owns=io+mem > [ 14.040430] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 510.68.02 > Wed Apr 20 21:10:34 UTC 2022 > [ 14.677665] caller _nv000651rm+0x1ad/0x200 [nvidia] mapping multiple > BARs > [ 14.928567] nvidia_uvm: module uses symbols from proprietary module > nvidia, inheriting taint. > -- 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
EXT4 Data Loss Error on Resume from Suspend
Should this go here, or the devel list? 2022-07-05T11:05:50.127140-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165908482: comm firefox: reading directory lblock 0 2022-07-05T11:05:50.127574-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_wait_block_bitmap:532: comm IndexedDB #724: Cannot read block bitmap - block_group = 9174, block_bitmap = 300417030 2022-07-05T11:05:50.152383-07:00 localhost kernel: EXT4-fs (dm-7): Delayed block allocation failed for inode 167575560 at logical offset 0 with max blocks 1 with error 5 2022-07-05T11:05:50.159591-07:00 localhost kernel: EXT4-fs (dm-7): This should not happen!! Data will be lost 2022-07-05T11:05:50.168021-07:00 localhost kernel: EXT4-fs warning (device dm-7): ext4_add_entry:2377: inode #165904385: lblock 0: comm firefox: error -5 reading directory block 2022-07-05T11:05:50.172627-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165908484: comm firefox: reading directory lblock 0 2022-07-05T11:05:50.172704-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165908482: comm firefox: reading directory lblock 0 2022-07-05T11:05:50.564696-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165617665: comm gsd-color: reading directory lblock 0 2022-07-05T11:05:50.564863-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_get_inode_loc:4576: inode #165609493: block 1324875809: comm gsd-color: unable to read itable block 2022-07-05T11:05:50.611903-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_get_inode_loc:4576: inode #165609493: block 1324875809: comm gsd-color: unable to read itable block 2022-07-05T11:05:50.627480-07:00 localhost kernel: EXT4-fs error (device dm-7) in ext4_reserve_inode_write:5748: IO failure 2022-07-05T11:05:50.641644-07:00 localhost kernel: EXT4-fs error (device dm-7) in ext4_orphan_add:188: IO failure 2022-07-05T11:05:50.655065-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_get_inode_loc:4576: inode #165609493: block 1324875809: comm gsd-color: unable to read itable block 2022-07-05T11:05:50.724704-07:00 localhost kernel: EXT4-fs warning (device dm-7): htree_dirblock_to_tree:1044: inode #165543937: lblock 0: comm updatedb: error -5 reading directory block 2022-07-05T11:06:03.113724-07:00 localhost kernel: EXT4-fs error: 16 callbacks suppressed 2022-07-05T11:06:03.113925-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #165654532: comm gnome-shell: reading directory lblock 0 2022-07-05T11:06:03.124575-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:03.124637-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_journal_check_start:83: comm gnome-shell: Detected aborted journal 2022-07-05T11:06:03.124794-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:03.124837-07:00 localhost kernel: EXT4-fs (dm-7): Remounting filesystem read-only 2022-07-05T11:06:35.711297-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:06:35.718013-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:54.859144-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:06:54.864491-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:06:58.405981-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:06:58.416978-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:05.526024-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:07:05.539798-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:08.309750-07:00 localhost kernel: EXT4-fs error (device dm-7): __ext4_find_entry:1635: inode #166707205: comm wireplumber: reading directory lblock 0 2022-07-05T11:07:08.317093-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.246700-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_wait_block_bitmap:532: comm gdbus: Cannot read block bitmap - block_group = 10030, block_bitmap = 328204302 2022-07-05T11:07:26.246844-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_discard_preallocations:5042: comm gdbus: Error -5 loading buddy information for 10030 2022-07-05T11:07:26.281601-07:00 localhost kernel: EXT4-fs (dm-7): I/O error while writing superblock 2022-07-05T11:07:26.281630-07:00 localhost kernel: EXT4-fs error (device dm-7): ext4_w
Re: Akmod Built Nvidia Module Tainting the Kernel at Boot Time
On Jul 5, 2022, at 18:55, Stephen Morris wrote:
> [ 13.973636] nvidia: module license 'NVIDIA' taints kernel.
It’s this line where the kernel notes why it is tainted. Somewhere in the
nvidia kmod C code, there is a line that looks like this:
MODULE_LICENSE("NVIDIA");
The kernel will print out the aforementioned kernel message if it isn’t one of
the open licenses defined in the kernel. There’s more about tainted kernels
here:
https://www.kernel.org/doc/html/latest/admin-guide/tainted-kernels.html
There are a variety of reasons why the kernel would be tainted, but in this
case it is because a proprietary kernel module was loaded. It doesn’t have
anything to do with signed kernel modules or secure boot.
--
Jonathan Billings___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: Dual booting
On Wed, 2022-07-06 at 09:16 +1000, Stephen Morris wrote: > I'm tri-booting between Win11, Fedora and Ubuntu. I used to have the > bios time configured to local time and found that Linux assumed the > bios time was UTC, and didn't provide an easy way of changing that, > and hence was always 10 hours out, Windows used to allow > configuration of that. It used to be dead easy to set Linux to UTC or localtime, there was a tickbox on the graphical tool for setting the clock (during the install, and later on the running OS). Doing the same thing on Windows required delving into the registry after first finding out how to do that over the web. I have had recent Linux installs presume localhost, then had to figure out how to change it because they didn't make it easy. At least the option's still findable in MATE on CentOS 7, it's a tickbox in the timezone tab in system-config-date. I can't see one on Fedora 36, and I don't recall whether I got asked during the install. Another of those things that got hidden by people who think we don't need to see these options. -- uname -rsvp Linux 3.10.0-1160.71.1.el7.x86_64 #1 SMP Tue Jun 28 15:37:28 UTC 2022 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
