Mark C. Allman, PMP, CSM, SSM
Sr. Project Manager/Scrum Master, Allman Professional Consulting, Inc.,
www.allmanpc.com <
http://www.allmanpc.com>
Founder, See How You Ski,
www.seehowyouski.com <
http://www.seehowyouski.com>
Ultra Runner,
www.bostonorbust.run <
http://www.bostonorbust.run>
617-947-4263, Twitter: @allmanpc, LinkedIn:
www.linkedin.com/in/allmanpc
<
http://www.linkedin.com/in/allmanpc>
On 12/8/23 09:07, olivares33561 via users wrote:
On Friday, December 8th, 2023 at 12:08 AM, Samuel Sieb
<samuel(a)sieb.net> wrote:
> On 12/7/23 17:35, olivares33561 via users wrote:
>
>> Dear kind Fedora users,
>>
>> When there was a kernel upgrade from 6.5.12 to 6.6.2, the 6.6.2-fc39 kernel, the
6.6.3, and 6.6.4*.fc39 kernel fail to boot. Machine just hangs. It used to just work
great. Now the machine hangs and I have to install updates and exclude the kernels with
sudo dnf upgrade --exclude=kernel* .
>>
>> I have successfully run the 6.6.x Fedora kernels on a raspberry pi 4. So I know
those kernels work, except on that machine. If I install the new kernels, boot hangs
indefinitely with no response. I will like to find out how I can check what is going on
and successfully boot a newer 6.6.x kernels. I can send information for machine. It is a
Dell XPS 8950 or something like that.
>
> At the boot menu, edit the grub command line and remove the "rghb quiet"
> from the end before booting. Then see where it gets stuck.
> --
Upon installing new kernel 6.6.4-200.fc39.x86_64
It stops at last line and it just sits there :(
Starting systemd-fsck-root.service - File System Check on
/dev/disk/by-uuid/8ff57a6b-2a55-4e9d-870d-855d-855d68d35bee...
[ OK ] Starting systemd-fsck-root.service - File System Check on
/dev/disk/by-uuid/8ff57a6b-2a55-4e9d-870d-855d-855d68d35bee.
I have to reboot and select older kernel 6.5.12-*fc39.x86_64
Best Regards & Thank you for trying to help
Antonio
--
My guess (and that's all it is) is that something in /etc/fstab can't be
mounted after the root filesystem. I'd try adding "noauto" to everything
there except for "/," "/home," etc. Just mount the stuff you must have
to get the system up. Also, maybe (???) set the last arg on the fstab
lines to 0 rather than 1 or 2. Everyone on the list -- please comment on
the last idea. I tried it on a cloud server and it didn't cause a
problem, but better to have the experts here weigh in.
* make a copy of fstab
* make the edits to fstab
* test by booting to the 6.5.?? kernel to be sure that still works
* try a 6.6.?? kernel and see what happens
-- Mark