Dan, Thanks for responding to this plea for help... It's appreciated. I had "frozen" this system at the "release" of the 5.18 kernel... but goofed and let the 5.19 kernel get installed. So, by letting the 5.19 kernel get installed, EVERYTHING that uses the kernel headers was upgraded. Yes? In the past I have tried to downgrade from an installed package but got messages about the previous version(s) were not available in the repositories. I suspect that this is also the case with this current situation. Yes? There's no way to go except forward. Am I right? On the 5.19 problems and booting: The boot gets as far as the dracut-pre-mount hook which appears to succeed but then something starts looking at devices(?) vi UUID. In my previous experiences with the 5.19 kernel, this NEVER succeeds. Some kind of bug? Worth reporting? My current grub command line is 3 screen lines long. I had "quiet" added to this line but tried to edit this out temporarily from the command line by typing "e" at the grub menu. I get the requested grub entry but when I try to move the cursor (either forward or backward from the command line, the cursor moves a bit but then the system just freezes. Another bug? Worth reporting? As if this situation isn't bad enough, there are over 4000 upgrades that are broken and/or have dependencies unavailable. This situation began with the perl fiasco. I haven't had the time to figure out just what the problem is now. Otherwise, the system is at the current bleeding edge as far as upgrades are concerned. It really looks like I've stepped in it this time. Any suggestions, help, hints, tips would be greatly appreciated. At least the 5.18 kernel runs... Sigh. Best regards, George... On Sunday, July 10, 2022 at 02:59:54 AM PDT, Dan Horák <dan@xxxxxxxx> wrote: On Sun, 10 Jul 2022 00:28:07 +0000 (UTC) George R Goffe via test <test@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > Hi, > > I'm having trouble with dnf and the 5.19 kernel. > > I have tried to exclude the 5.19 kernel on this system (FC37) because 1) Virtual box doesn't seem to support it yet, 2) the system gets stuck during boot and the boot will NOT succeed (It seems to be running a list of UUIDs). > > The problem: somehow I managed to upgrade to the 5.19 kernel and am now stuck. dnf seems to want to remove EVERYTHING that it thinks is dependent on this kernel.I have used this command "dnf --noautoremove erase kernel-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-core-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-devel-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-headers-5.19.0-0.rc5.git0.1.fc37.x86_64 kernel-modules-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64 kernel-modules-extra-5.19.0-0.rc5.20220707git9f09069cde34.43.fc37.x86_64' > > > which is where the 501 dependencies comes from. > > I am a loss as to just what to do to get 5.19 out of my system. Is this happenstance a bug? Do all these packages REALLY depend on the kernel version? > > "Normally" I would do something like "rpm --nodeps -e kernel*5.19*". Could the solution be that simple? > > Any thoughts/hints/tips/suggestions would be greatly appreciated. do you have a different kernel (eg. 5.18) installed? kernel-headers is Required by glibc-devel, thus if you have any "devel" package installed, then they will be removed when kernel-headers will be removed. There is only one instance of kernel-headers installed at any time. Dan _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/test@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
