Re: Errors in DMESG After System Update

2025-03-16 Thread Samuel Sieb
On 2025-03-16 15:23, Stephen Morris wrote:     Is the nvidia API mismatch because the Xorg nvidia drivers were updated with the update I did and I haven't rebooted yet? [ 3055.581655] NVRM: API mismatch: the client has the version 570.124.04, but   NVRM: this kernel module has t

Re: Would like to replace BIOS on Lenovo X131e running Fedora - should this work?

2025-03-16 Thread Andre Robatino
Since 42 Beta went Gold, I decided to install the UEFI firmware and then F42. Afterwards, it works perfectly. I had 2 issues before: 1) suspend didn't work, and 2) the GRUB menu wasn't responsive on a cold boot (I could see it but not interact), unless I plugged in an external USB keyboard. Both

Re: Errors in DMESG After System Update

2025-03-16 Thread Todd Zullinger
Stephen Morris wrote: >     Just a query first off, why do I need to run dmesg under sudo for it to > produce its output? In Fedora 39 (or there about), the CONFIG_SECURITY_DMESG_RESTRICT kernel config was changed. The commit in the Fedora kernel source tree provides some useful details¹: Tu

Errors in DMESG After System Update

2025-03-16 Thread Stephen Morris
Hi,     Just a query first off, why do I need to run dmesg under sudo for it to produce its output?     Could someone explain the systemd message below as to why they are coming out rather than the package being updated as specified in the message. The device non-existant errors and the lockd

Re: e2fsck malfunction?

2025-03-16 Thread Tim via users
On Thu, 2025-03-13 at 16:47 -0700, Dave Close wrote: > Later, after mounting the ext4 partition on the card under Fedora and > doing two or three minutes of exploration, I encounter a bad block. > So I unmount the partition and use e2fsck to locate any bad blocks > and mark them: > > e2fsck -y -