Re: recent kernel update failed

ction for that package? The answer may depend on the reason for the failure to create the initrd. Let me be more specific. Following an incomplete update, running 'dnf update' claimed there is nothing to do. Even after having removed the latest (failed) kernel. What is the correct

Re: recent kernel update failed

On Sat, Jul 5, 2025 at 10:07 PM wrote: > Today I did the usual 'dnf update' on a VM system. > As part of the update I received kernel-6.15.4-200.fc42.x86_64 > "VM System" is too vague: which VM? > > However, after the upgrades were done, the last console message was > >>> Running post-t

Re: recent kernel update failed

On Sun, 2025-07-06 at 08:49 +0100, Barry wrote: > > > On 6 Jul 2025, at 02:07, fed...@eyal.emu.id.au wrote: > > > > However, after the upgrades were done, the last console message was > >>>> Running post-transaction scriptlet: > > kernel-core-0:6.15.4-200.fc42.x86_64 > > after which the syst

Re: recent kernel update failed

> On 6 Jul 2025, at 02:07, fed...@eyal.emu.id.au wrote: > > However, after the upgrades were done, the last console message was >>>> Running post-transaction scriptlet: > kernel-core-0:6.15.4-200.fc42.x86_64 > after which the system was hard locked (about 45m...). No one else has reported

recent kernel update failed

Today I did the usual 'dnf update' on a VM system. As part of the update I received kernel-6.15.4-200.fc42.x86_64 However, after the upgrades were done, the last console message was >>> Running post-transaction scriptlet: kernel-core-0:6.15.4-200.fc42.x86_64 after which the system was ha

Re: Last kernel update leads to emergency mode

On Thu, Aug 31, 2023 at 3:50 PM George N. White III wrote: > >> >[...] >> > Given the fact that an older kernel works, but a newer one doesn't, it >> > sure seems like it is somehow related to the kernel. Since the same >> > version of systemd works on an old kernel, it is unlikely to be >> > sys

Re: Last kernel update leads to emergency mode

On Thu, Aug 31, 2023 at 9:26 AM Paul Smith wrote: > On Wed, Aug 30, 2023 at 2:04 PM stan via users > wrote: > >[...] > > Given the fact that an older kernel works, but a newer one doesn't, it > > sure seems like it is somehow related to the kernel. Since the same > > version of systemd works on

Re: Last kernel update leads to emergency mode

On Wed, Aug 30, 2023 at 2:04 PM stan via users wrote: > > > Maybe the following is relevant: > > > > > > # dracut --force --kver 6.4.12-200.fc38.x86_64 --verbose > > dracut: Executing: /usr/bin/dracut --force --kver > > 6.4.12-200.fc38.x86_64 --verbose > > dracut: drac

Re: Last kernel update leads to emergency mode

On Wed, 30 Aug 2023 00:38:08 +0100 Paul Smith wrote: > Maybe the following is relevant: > > > # dracut --force --kver 6.4.12-200.fc38.x86_64 --verbose > dracut: Executing: /usr/bin/dracut --force --kver > 6.4.12-200.fc38.x86_64 --verbose > dracut: dracut module 'busy

Re: Last kernel update leads to emergency mode

On Tue, Aug 29, 2023 at 11:41 PM Paul Smith wrote: > > > > > > Thanks, Stan. I guess the files are almost similar, since they > > > > > have almost the same size: > > > > > > > > I agree. Your issue isn't the issue I had. Debugging these early > > > > issues is hard, because it has to be done fr

Re: Last kernel update leads to emergency mode

On Tue, Aug 29, 2023 at 6:15 PM stan via users wrote: > > > > > Thanks, Stan. I guess the files are almost similar, since they > > > > have almost the same size: > > > > > > I agree. Your issue isn't the issue I had. Debugging these early > > > issues is hard, because it has to be done from the

Re: Last kernel update leads to emergency mode

On Mon, 28 Aug 2023 19:33:41 +0100 Paul Smith wrote: > On Mon, Aug 28, 2023 at 3:25 PM stan wrote: > > > > > Thanks, Stan. I guess the files are almost similar, since they > > > have almost the same size: > > > > I agree. Your issue isn't the issue I had. Debugging these early > > issues i

Re: Last kernel update leads to emergency mode

On Mon, Aug 28, 2023 at 3:25 PM stan wrote: > > > Thanks, Stan. I guess the files are almost similar, since they have > > almost the same size: > > I agree. Your issue isn't the issue I had. Debugging these early > issues is hard, because it has to be done from the emergency console. > But, I th

Re: Last kernel update leads to emergency mode

nitrd | less > > > > > >To display the contents of a file in the initramfs also use > > > the lsinitrd tool: > > > > > ># lsinitrd -f /etc/ld.so.conf > > >include ld.so.conf.d/*.conf > > > > Thanks to all for your

Re: Last kernel update leads to emergency mode

also use > > the lsinitrd tool: > > > ># lsinitrd -f /etc/ld.so.conf > > include ld.so.conf.d/*.conf > > Thanks to all for your help! > > I have meanwhile been able to take photos from the > > journalctl -xb > > output, and I think

Re: Last kernel update leads to emergency mode

lay the contents of a file in the initramfs also use the > lsinitrd tool: > ># lsinitrd -f /etc/ld.so.conf >include ld.so.conf.d/*.conf Thanks to all for your help! I have meanwhile been able to take photos from the journalctl -xb output, and I think that now the

Re: Last kernel update leads to emergency mode

On Thu, 24 Aug 2023 17:44:52 +0100 Paul Smith wrote: > I have been able to take a screen-shot: > > https://i.imgur.com/nAsE6i6.jpg This means that dracut was unable to start systemd in order to continue the boot once the initramfs was finished creating the bootstrap. I have had this happen, b

Re: Last kernel update leads to emergency mode

ually means that grub did not finish installing the new kernel update. Try reinstalling perhaps? Or rebuild grub? Thanks, Rajan and old sixpack13. I have tried to remove and then install the problematic kernel, but that does not fix the problem, unfortunately. I have been able to take a screen

Re: Last kernel update leads to emergency mode

On 08/24/2023 10:44 AM, Paul Smith wrote: I have been able to take a screen-shot: https://i.imgur.com/nAsE6i6.jpg Were you able to save the report and if so, can you attach it to your reply? I doubt that I'll be able to make use of it, but with luck, somebody here will. ___

Re: Last kernel update leads to emergency mode

that. > > > > > > > > Thanks, Patrick: My bad: the problematic kernel is: > > > > > > > > kernel-6.4.11-200.fc38.x86_64 > > > > > > Can you boot into the older kernel? > > > > Yes, Ranjan, I can boot into an older kernel.

Re: Last kernel update leads to emergency mode

> Dear All, > > Are other also experience that with the new kernel: > > 6.4.10-200.fc38.x86_64 > > I have already file a bug but no answer: > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > Have a nice day, > > Paul Personal I do not have trouble with kernel > 6.4.8, but my brother

Re: Last kernel update leads to emergency mode

On Tue Aug22'23 04:19:23PM, Paul Smith wrote: > From: Paul Smith > Date: Tue, 22 Aug 2023 16:19:23 +0100 > To: Community support for Fedora users > Reply-To: Community support for Fedora users > Subject: Re: Last kernel update leads to emergency mode > > On Tue, Aug

Re: Last kernel update leads to emergency mode

On Tue, Aug 22, 2023 at 6:21 PM Samuel Sieb wrote: > > >>> Are other also experience that with the new kernel: > >>> > >>> 6.4.10-200.fc38.x86_64 > >>> > >>> I have already file a bug but no answer: > >>> > >>> https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > >> > >> You didn't really provide

Re: Last kernel update leads to emergency mode

On 8/22/23 03:37, Paul Smith wrote: On Tue, Aug 22, 2023 at 4:31 AM Samuel Sieb wrote: Are other also experience that with the new kernel: 6.4.10-200.fc38.x86_64 I have already file a bug but no answer: https://bugzilla.redhat.com/show_bug.cgi?id=2232838 You didn't really provide any inf

Re: Last kernel update leads to emergency mode

On Tue, Aug 22, 2023 at 2:26 PM Ranjan Maitra wrote: > > > > > Are other also experience that with the new kernel: > > > > > > > > 6.4.10-200.fc38.x86_64 > > > > > > > > I have already file a bug but no answer: > > > > > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > > > > > I didn'

Re: Last kernel update leads to emergency mode

On Mon Aug21'23 05:13:34PM, Paul Smith wrote: > From: Paul Smith > Date: Mon, 21 Aug 2023 17:13:34 +0100 > To: Community support for Fedora users > Reply-To: Community support for Fedora users > Subject: Re: Last kernel update leads to emergency mode > > On Mon, Aug 2

Re: Last kernel update leads to emergency mode

On Tue, Aug 22, 2023 at 4:31 AM Samuel Sieb wrote: > > > Are other also experience that with the new kernel: > > > > 6.4.10-200.fc38.x86_64 > > > > I have already file a bug but no answer: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > You didn't really provide any info that would

Re: Last kernel update leads to emergency mode

On Mon, 21 Aug 2023 20:30:44 -0700 Samuel Sieb wrote: > On 8/21/23 08:56, Paul Smith wrote: > > Are other also experience that with the new kernel: > > > > 6.4.10-200.fc38.x86_64 > > > > I have already file a bug but no answer: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > >

Re: Last kernel update leads to emergency mode

On 8/21/23 08:56, Paul Smith wrote: Are other also experience that with the new kernel: 6.4.10-200.fc38.x86_64 I have already file a bug but no answer: https://bugzilla.redhat.com/show_bug.cgi?id=2232838 You didn't really provide any info that would help. Can you get any journal output or

Re: Last kernel update leads to emergency mode

On Mon, 2023-08-21 at 17:13 +0100, Paul Smith wrote: > On Mon, Aug 21, 2023 at 5:10 PM Patrick O'Callaghan > wrote: > > > > > Are other also experience that with the new kernel: > > > > > > 6.4.10-200.fc38.x86_64 > > > > > > I have already file a bug but no answer: > > > > > > https://bugzilla

Re: Last kernel update leads to emergency mode

On Mon, Aug 21, 2023 at 5:10 PM Patrick O'Callaghan wrote: > > > Are other also experience that with the new kernel: > > > > 6.4.10-200.fc38.x86_64 > > > > I have already file a bug but no answer: > > > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > > I didn't have any problems, but I upd

Re: Last kernel update leads to emergency mode

On Mon, 2023-08-21 at 16:56 +0100, Paul Smith wrote: > Dear All, > > Are other also experience that with the new kernel: > > 6.4.10-200.fc38.x86_64 > > I have already file a bug but no answer: > > https://bugzilla.redhat.com/show_bug.cgi?id=2232838 > I didn't have any problems, but I updated

Last kernel update leads to emergency mode

Dear All, Are other also experience that with the new kernel: 6.4.10-200.fc38.x86_64 I have already file a bug but no answer: https://bugzilla.redhat.com/show_bug.cgi?id=2232838 Have a nice day, Paul ___ users mailing list -- users@lists.fedoraproje

Re: f36 - kernel update breaks resolv.conf

On 31/05/2022 22.25, Eyal Lebedinsky wrote: I am on f36 for a few weeks now, upgraded from f34. This is the second time this happened. A 'dnf update' runs fine but hangs at the very end, after the list of 'Veritying'. dnf (the python3 process) is in state D+ (though I could kill it). dnf.log

Re: f36 - kernel update breaks resolv.conf

Tom Horsley writes: On Tue, 31 May 2022 18:38:54 -0400 Sam Varshavchik wrote: > It keeps finding its way back on my systems, even after I uninstalled it Uninstalling is probably hopeless. I don't bother with uninstalling things like that, but disabling and masking them seems to work well, and

Re: f36 - kernel update breaks resolv.conf

On Tue, 31 May 2022 18:38:54 -0400 Sam Varshavchik wrote: > It keeps finding its way back on my systems, even after I uninstalled it Uninstalling is probably hopeless. I don't bother with uninstalling things like that, but disabling and masking them seems to work well, and that leaves all the fil

Re: f36 - kernel update breaks resolv.conf

Roger Heflin writes: « HTML content follows » once you update the file to be a good one, then do this: chattr +i /etc/resolv.conf  (that sets the immutable bit that disallows rename, write, delete). That should prevent anything from overwriting the file.  If you need to change the fi

Re: f36 - kernel update breaks resolv.conf

once you update the file to be a good one, then do this: chattr +i /etc/resolv.conf (that sets the immutable bit that disallows rename, write, delete). That should prevent anything from overwriting the file. If you need to change the file you will have to -i the file first. It is kind of crude

Re: f36 - kernel update breaks resolv.conf

> Am 31.05.2022 um 14:25 schrieb Eyal Lebedinsky : > > ... > dnf.rpm.log ends with this interesting line > 2022-05-31T21:37:06+1000 INFO '/etc/resolv.conf' -> > '../run/systemd/resolve/stub-resolv.conf' This is expected behaviour. systemd-resolved with resolv.conf linked to that stub is

f36 - kernel update breaks resolv.conf

I am on f36 for a few weeks now, upgraded from f34. This is the second time this happened. A 'dnf update' runs fine but hangs at the very end, after the list of 'Veritying'. dnf (the python3 process) is in state D+ (though I could kill it). dnf.log ends with 2022-05-31T21:32:33+1000 DDE

Re: laptop failing with latest kernel update

On 2/8/22 16:10, Anil Felipe Duggirala wrote: How should I report this issue in this case? One way is to god directly to Bugzilla and open the report yourself. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to use

laptop failing with latest kernel update

hello, I performed a normal update today after some time without updating, which I believed contained a kernel update (to 5.16.5-100.fc34.x86_64 I believe). After doing the update and rebooting my pc started behaving erratically. Bootup time was longer, then it sort of got stuck, then some

Re: Fw: Kernel update again (solved)

On Sat, Jul 31, 2021 at 9:19 AM jarmo wrote: > > Now working. Just changed screen resolution from 1280x720 16:9 > which was good for my old eyes :) to 1920x1080. Only bad thing > is, that texts are so small, have to tri increas font size... > But, booting and running, so SOLVED... It's a work aro

Fw: Kernel update again (solved)

viesti: Päiväys: Fri, 30 Jul 2021 09:27:38 +0300 Lähettäjä: jarmo Vastaanottaja: users@lists.fedoraproject.org Aihe: Kernel update again Got new kernel and that stil won't work with my HP laptop. It boots so far, that I get login window, I give passwd after that, black window, nothing else ha

Re: Kernel update again

On Fri, Jul 30, 2021 at 12:28 AM jarmo wrote: > > Got new kernel and that stil won't work with > my HP laptop. > It boots so far, that I get login window, I give passwd > after that, black window, nothing else happens, except ctl+alt+del > works. > What I have last working kernel in that laptop, i

Kernel update again

Got new kernel and that stil won't work with my HP laptop. It boots so far, that I get login window, I give passwd after that, black window, nothing else happens, except ctl+alt+del works. What I have last working kernel in that laptop, is 5.12.15-300.fc34.x86_64 I'm not any programmer nor bugzilla

f33::k10temp-pci-00c3 :: after kernel update {V,I}{core,soc} lost

Hi! On a laptop with Ryzen 7 3700U, after kerenel update, lm_sensors k10temp-pci-00c3 module no longer report the {V,I}{core,soc} metrics .. did anyone seen this? is it expected somehow or is a regression? (i redid the detecion procedure) Thank you! Adrian __

Re: Need help with a weird kernel update panic.

All it takes is one systemd bug, or any number of other conditions that prevent a proper umount. I have seen various kernel bugs cause it, I have seen the hw operating the disks stop working. In general using ext4+journal and/or xfs under the exact wrong conditions can result in an unbootable sys

Re: Need help with a weird kernel update panic.

On 5/12/20 4:38 PM, John Mellor wrote: Hi Samuel, But that's the point.  A default install uses LVM, and therefore constructs a separate /boot partition running EXT4 with a journal.  You may of course decide to do your own partitions, but that setup is highly unusual and rare.  Most people wil

Re: Need help with a weird kernel update panic.

Hi Samuel, But that's the point. A default install uses LVM, and therefore constructs a separate /boot partition running EXT4 with a journal. You may of course decide to do your own partitions, but that setup is highly unusual and rare. Most people will have the default partitioning, and therefo

Re: Need help with a weird kernel update panic.

On 5/12/20 5:15 AM, John Mellor wrote: On 2020-05-09 5:53 p.m., Ed Greshko wrote: On 2020-05-09 21:01, John Mellor wrote: Now I need to wait for the next kernel upgrade, and see if that change fixes my crash/panic issue. Of course you could boot to the previous kernel, remove the latest one, r

Re: Need help with a weird kernel update panic.

On 2020-05-09 5:53 p.m., Ed Greshko wrote: On 2020-05-09 21:01, John Mellor wrote: Now I need to wait for the next kernel upgrade, and see if that change fixes my  crash/panic issue. Of course you could boot to the previous kernel, remove the latest one, reboot again to the previous kernel and

Re: Need help with a weird kernel update panic.

On 2020-05-09 21:01, John Mellor wrote: > Now I need to wait for the next kernel upgrade, and see if that change fixes  > my crash/panic issue. Of course you could boot to the previous kernel, remove the latest one, reboot again to the previous kernel and allow the upgrade to test. -- The key

Re: Need help with a weird kernel update panic.

Roger Heflin writes: I never said that it does not get unmounted, but unmounting does not mean the journal got replayed. Note the first thing ext4/xfs does on a mount/fsck is replays the journal, the read-only mount would replay the journal, but indications are that that fails often enough tha

Re: Need help with a weird kernel update panic.

I never said that it does not get unmounted, but unmounting does not mean the journal got replayed. Note the first thing ext4/xfs does on a mount/fsck is replays the journal, the read-only mount would replay the journal, but indications are that that fails often enough that the replay does not ge

Re: Need help with a weird kernel update panic.

Ok, I think I've finally managed to remove the journal on /boot. I did it by rebooting into an old F30 boot media in troubleshooting mode using 'tune2fs -O ^has_journal'.  I was unable to do this on the disk even in single user mode, as it always marked the /boot partition as unclean, and alway

Re: Need help with a weird kernel update panic.

On 5/8/20 8:59 PM, Sam Varshavchik wrote: I have used ext4 for /boot for 20+ years on Fedora, and can't say that I ever had this happen. And I always reboot after installing updates. I've never had this happen over all the very many computers I've worked with. Long term the solution is to m

Re: Need help with a weird kernel update panic.

ut from a reboot after a kernel update yesterday? May 08 15:55:11 meimei.greshko.com systemd[1]: Unmounting /boot... May 08 15:55:11 meimei.greshko.com systemd[1]: boot.mount: Succeeded. May 08 15:55:11 meimei.greshko.com systemd[1]: Unmounted /boot. May 08 15:55:11 meimei.greshko.com systemd[1]

Re: Need help with a weird kernel update panic.

Roger Heflin writes: What you are saying does not exactly match what I have previously seen, but there is a known feature with using a journaling filesystem (ext4-journal, or xfs) for /boot, if only the journal is updated and if it is not yet replayed into the non-journal then grub will not be

Re: Need help with a weird kernel update panic.

Did you do a lazy unmount? Any other umount will fail if there are open files, and lazy does not actually unmount it until whatever has the files open closes them, which generally means it never gets unmounted. On Fri, May 8, 2020 at 5:53 PM John Mellor wrote: > > I like the idea of just removi

Re: Need help with a weird kernel update panic.

I like the idea of just removing the journal tag, but I don't think that I can modify the /boot filesystem.  Doing a umount works, but tune2fs claims that an e2fsck is required.  Running e2fsck says that the filesystem is still mounted, even though it is not.  Doing a fuser /dev/sda1 shows a la

Re: Need help with a weird kernel update panic.

You have to hit the timing right. ie install the kernel package and as quickly as possible reboot (automated, or very efficient). And if the update is more than just kernel, that may slowdown the process enough that the immediate reboot won't be quick enough. I have seen it 3-5 times and that is

Re: Need help with a weird kernel update panic.

On Fri, May 8, 2020 at 12:12 PM Roger Heflin wrote: > > A sync will flush the writes to the journal were the data is safe. It > will not force a replay of the journal. > > Nothing except removing the journal from the ext4 filesystem will fix it. > > This is not a fedora bug, this is a long standi

Re: Need help with a weird kernel update panic.

A sync will flush the writes to the journal were the data is safe. It will not force a replay of the journal. Nothing except removing the journal from the ext4 filesystem will fix it. This is not a fedora bug, this is a long standing kernel/grub/filesystem interaction bug (all who use a journale

Re: Need help with a weird kernel update panic.

Interesting!  This machine does reboot in about 5secs and the other machines take longer, so it makes sense.  My /boot is mounted just like /home and / as follows:    /dev/sda1 on /boot type ext4 (rw,relatime,seclabel) I assume that a symple sync would flush the journal.  Its pretty easy to d

Re: Need help with a weird kernel update panic.

What you are saying does not exactly match what I have previously seen, but there is a known feature with using a journaling filesystem (ext4-journal, or xfs) for /boot, if only the journal is updated and if it is not yet replayed into the non-journal then grub will not be able to find the new fil

Need help with a weird kernel update panic.

I have one completely stock workstation F32 machine where kernel updates almost always cause a multiple-reboot panic problem.  This problem also occurred on F31, but not on releases before that. I'm stumped and need some help in figuring it out. The symptoms vary in the number of reboots and t

Re: Last kernel update 5.5.5

Samuel Sieb writes: On 2/29/20 9:52 AM, Sam Varshavchik wrote: Samuel Sieb writes: On 2/25/20 12:11 AM, jarmo wrote: HP 15-DW021NO laptop Fedora 31 Updated kernel to 5.5.5. After update and reboot Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) stopp

Re: Last kernel update 5.5.5

On 2/29/20 9:52 AM, Sam Varshavchik wrote: Samuel Sieb writes: On 2/25/20 12:11 AM, jarmo wrote: HP 15-DW021NO laptop Fedora 31 Updated kernel to 5.5.5. After update and reboot Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) stopped working. Lspci show

Re: Last kernel update 5.5.5

Sat, 29 Feb 2020 19:56:06 +0100 Alessio kirjoitti: > Updated today to 5.5.6-201 (from stable updates repository) and the > problem has gone away. Yes, update solved problem, thanks... Jarmo ___ users mailing list -- users@lists.fedoraproject.org To u

Re: Last kernel update 5.5.5

On Feb 25, 2020 11:48 AM, jarmo wrote: > > Tue, 25 Feb 2020 00:23:47 -0800 > Samuel Sieb kirjoitti: > > > https://bugzilla.kernel.org/show_bug.cgi?id=206329 > > Thanks, waiting for offial update Same problem here on a similar laptop model with Intel Wireless-AC 3168NGW Updated today to 5.5

Re: Last kernel update 5.5.5

Samuel Sieb writes: On 2/25/20 12:11 AM, jarmo wrote: HP 15-DW021NO laptop Fedora 31 Updated kernel to 5.5.5. After update and reboot Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) stopped working. Lspci shows, that card found... https://bugzilla.ker

Re: Last kernel update 5.5.5

Tue, 25 Feb 2020 00:23:47 -0800 Samuel Sieb kirjoitti: > https://bugzilla.kernel.org/show_bug.cgi?id=206329 Thanks, waiting for offial update Jarmo ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lis

Re: Last kernel update 5.5.5

kernel-5.5.6-201.fc31 in koij should fix it Antonio Montagnani Linux Fedora 31 Workstation da/from Gmail Il giorno mar 25 feb 2020 alle ore 09:24 Samuel Sieb ha scritto: > On 2/25/20 12:11 AM, jarmo wrote: > > HP 15-DW021NO laptop

Re: Last kernel update 5.5.5

On 2/25/20 12:11 AM, jarmo wrote: HP 15-DW021NO laptop Fedora 31 Updated kernel to 5.5.5. After update and reboot Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) stopped working. Lspci shows, that card found... https://bugzilla.kernel.org/show_bug.cgi?i

Last kernel update 5.5.5

HP 15-DW021NO laptop Fedora 31 Updated kernel to 5.5.5. After update and reboot Network controller: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] (rev 10) stopped working. Lspci shows, that card found... With kernel 5.4.20-200.f31.x86_64 wireless is working ok. Anyone else noticed

Re: Latest kernel update Removing dependent package kmod-wl

On 7/15/19 9:22 AM, Ed Greshko wrote: On 7/15/19 8:33 PM, Robert Moskowitz wrote: Installing:  kernel x86_64 5.1.17-300.fc30 updates15 k  kernel-corex86_64 5.1.17-300.fc30 updates26 M  kernel-devel   x86_64 5.1.17-

Re: Latest kernel update Removing dependent package kmod-wl

On 7/15/19 9:11 AM, francis.montag...@inria.fr wrote: HI. On Mon, 15 Jul 2019 08:33:04 -0400 Robert Moskowitz wrote: Installing: kernel x86_64 5.1.17-300.fc30 updates15 k ... Removing: kernel x86_64 5.1.12-300.fc30 @updates

Re: Latest kernel update Removing dependent package kmod-wl

On 7/15/19 8:33 PM, Robert Moskowitz wrote: > Installing: >  kernel x86_64 5.1.17-300.fc30 updates15 k >  kernel-corex86_64 5.1.17-300.fc30 updates26 M >  kernel-devel   x86_64 5.1.17-300.fc30 updates13 M >  kernel-

Re: Latest kernel update Removing dependent package kmod-wl

HI. On Mon, 15 Jul 2019 08:33:04 -0400 Robert Moskowitz wrote: > Installing: > kernel x86_64 5.1.17-300.fc30 updates15 k ... > Removing: > kernel x86_64 5.1.12-300.fc30 @updates0 ... > Removing dependent packages: > kmod-wl-5.1

Re: Latest kernel update Removing dependent package kmod-wl

Installing:  kernel x86_64 5.1.17-300.fc30 updates    15 k  kernel-core    x86_64 5.1.17-300.fc30 updates    26 M  kernel-devel   x86_64 5.1.17-300.fc30 updates    13 M  kernel-modules x86_64 5.1.17-300.fc30 update

Re: Latest kernel update Removing dependent package kmod-wl

On 7/15/19 5:47 PM, Robert Moskowitz wrote: > This is for my broadcom wifi from non-free rpmfusion. > > It seems a bad thing for me to do this update. > > Recommendations? > > thanks Maybe show us what you're seeing? [root@f29bk ~]# uname -r 5.1.16-300.fc30.x86_64 [root@f29bk ~]# rpm -q kmod-wl

Latest kernel update Removing dependent package kmod-wl

This is for my broadcom wifi from non-free rpmfusion. It seems a bad thing for me to do this update. Recommendations? thanks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fe

Re: initramfs: kernel update adds unwanted driver?

On 2018-04-14, francis.montag...@inria.fr wrote: > Thus, for the running kernel: > > /bin/kernel-install add $(uname -r) /lib/$(uname -r)/vmlinuz > > It will regenerate the initramfs and eventually other things like the > grub.cfg. > > I tested to add a /etc/dracut.conf.d/test.conf to omit a dr

Re: initramfs: kernel update adds unwanted driver?

You can also use lsinitrd to show the current files in any initramfs and/or cat out the contents of single files you see in the initramfs. On Sat, Apr 14, 2018 at 10:43 AM, wrote: > > On Sat, 14 Apr 2018 15:07:28 - Grant Edwards wrote: >> On 2018-04-14, francis.montag...@inria.fr wrote: >>>

Re: initramfs: kernel update adds unwanted driver?

On Sat, 14 Apr 2018 15:07:28 - Grant Edwards wrote: > On 2018-04-14, francis.montag...@inria.fr wrote: >> Thus, for the running kernel: >> /bin/kernel-install add $(uname -r) /lib/$(uname -r)/vmlinuz > Thanks! That looks like a good option. I may prompt the user for > confirmation befo

Re: initramfs: kernel update adds unwanted driver?

On 2018-04-14, francis.montag...@inria.fr wrote: > On Fri, 13 Apr 2018 21:03:34 - Grant Edwards wrote: > >> First create a file named /etc/dracut.conf.d/foo containing the line >> omit_drivers+="foo". Then either > > Bexware, this file should have .conf as suffix. Ah yes, thanks for pointing

Re: initramfs: kernel update adds unwanted driver?

Hi. On Fri, 13 Apr 2018 21:03:34 - Grant Edwards wrote: > First create a file named /etc/dracut.conf.d/foo containing the line > omit_drivers+="foo". Then either Beware, this file should have .conf as suffix. > 1. Rebuild the initramfs with the 'dracut' command. I haven't tested >thi

Re: initramfs: kernel update adds unwanted driver?

On 2018-04-13, Rick Stevens wrote: > On 04/13/2018 09:34 AM, Grant Edwards wrote: >> What's the best way to remove the old, broken driver from the >> initramfs so that the driver in the root filesystem is used on boot? >> >> Is there a way to prevent the kerne

Re: initramfs: kernel update adds unwanted driver?

> shipped with the kernel package, but I've never seen it included in > the initramfs before. > > What's the best way to remove the old, broken driver from the > initramfs so that the driver in the root filesystem is used on boot? > > Is there a way to prevent the

initramfs: kernel update adds unwanted driver?

y to remove the old, broken driver from the initramfs so that the driver in the root filesystem is used on boot? Is there a way to prevent the kernel update process from adding the driver back to the initramfs the next time a kernel is updated? Alternatively, I suppose I could add a "service&

Re: warning about spectre with last kernel update

On 02/19/18 04:59, Stephen Morris wrote: >> >> strings /usr/lib/modules/4.15.3-300.fc27.x86_64/extra/nvidia/nvidia.ko | >> grep gcc > > I get my nvidia source from the negativo17 repository and all this command > does is > list the version of gcc used And that was the entire purpose of asking t

Re: warning about spectre with last kernel update

On 18/2/18 9:14 pm, François Patte wrote: Le 18/02/2018 à 10:54, Ed Greshko a écrit : On 02/18/18 17:01, François Patte wrote: $ strings /usr/lib/modules/4.15.3-300.fc27.x86_64/extra/nvidia-340xx/nvidia.ko | grep gcc gcc version 7.2.1 20170915 (Red Hat 7.2.1-2) (GCC) OK.   I believe that RET

Re: warning about spectre with last kernel update

On 18/2/18 8:28 am, Ed Greshko wrote: On 02/18/18 05:12, François Patte wrote: Le 17/02/2018 à 20:31, Ed Greshko a écrit : On 02/18/18 02:10, François Patte wrote: returns that virtualbox drivers (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) and nvidia driver were not compiled with a retpoline co

Re: warning about spectre with last kernel update

spectre v2 What do they mean and what to do? Waiting for next kernel update? It may mean that your particular CPU is not fully protected by the recent kernel patches. Cat the files in /sys/devices/system/cpu/vulnerabilities FWIW, my systems have [egreshko@acer vulnerabilities]$ cat

Re: warning about spectre with last kernel update

Le 18/02/2018 à 14:22, Ed Greshko a écrit : > On 02/18/18 21:03, François Patte wrote: >> Le 18/02/2018 à 11:20, Ed Greshko a écrit : >>> On 02/18/18 18:14, François Patte wrote: fc27 is the last "stable" version of fedora, and gcc-7.3 seems to have a patch for retpoline, why the patched

Re: warning about spectre with last kernel update

On 02/18/18 21:55, François Patte wrote: > Le 18/02/2018 à 14:36, Ed Greshko a écrit : >> On 02/18/18 21:03, François Patte wrote: >>> but I am unable to reinstall virtualbox >> >> For the virtualbox drivers just run... >> >> sudo /usr/lib/virtualbox/vboxdrv.sh setup > This file (vboxdrv.sh) does n

Re: warning about spectre with last kernel update

Le 18/02/2018 à 14:36, Ed Greshko a écrit : > On 02/18/18 21:03, François Patte wrote: >> but I am unable to reinstall virtualbox > > > For the virtualbox drivers just run... > > sudo /usr/lib/virtualbox/vboxdrv.sh setup This file (vboxdrv.sh) does not exist on my system... Are we running the s

Re: warning about spectre with last kernel update

On 02/18/18 21:03, François Patte wrote: > but I am unable to reinstall virtualbox For the virtualbox drivers just run... sudo /usr/lib/virtualbox/vboxdrv.sh setup This will rebuild the modules for the running kernel only. -- A motto of mine is: When in doubt, try it out signature.asc Desc

Re: warning about spectre with last kernel update

On 02/18/18 21:03, François Patte wrote: > Le 18/02/2018 à 11:20, Ed Greshko a écrit : >> On 02/18/18 18:14, François Patte wrote: >>> fc27 is the last "stable" version of fedora, and gcc-7.3 seems to have a >>> patch for retpoline, why the patched version is not available in fedora >>> repos? >> >

  1   2   3   >