bazzite won't boot after installation (watchdog,..)

Hi : ) have bazzite for a while now on my HTPC and am really loving it! Now i am trying to install bazzite (Nvidia RTX Series | GTX 16xx Series+, KDE) on my new SSD (NTFS) as dualboot beside my WIN 10. Tried to follow the YT-Tutorial and the installation manual on bazzite.gg. After the installation went through it just resboots again and again. hitting ESC brought up several messages, i tried to capture some. What am i doing wrong here? πŸ€” Specs: MSI B450 TOMAHAWK MAX AMD Ryzen 7 3700X 8-Core Processor NVIDIA GeForce RTX 2070 SUPER Soundblaster AE-7 2x 8GB DDR4 SDRAM SSD WIN 10 1TB SSD bazzite 2TB (Lexar NM790) Thanks in advance for the help
No description
No description
No description
No description
No description
14 Replies
Mamoulian
MamoulianOPβ€’4d ago
hm, as far as my "research" is progressing the "nvidia-gpu 0000:26:00.3: i2c timeout error..." is irrelevant?! but the "watchdog: watchdog detected hard LOCKUP on cpu X" seems to be the problem? πŸ€” ok, now i have updated to the latest bios-version which sadly had no effect 😒 is there any bios-setting i should look into or change? what i did in the meantime: update bios to the latest version downloaded a fresh ISO an compared the checksums did a fresh installation (interestingly i don't get the screen with the blue border, but maybe thats because i don't have secure boot enabled?!) but sadly, i still get the same "[ 37.645042] watchdog: Watchdog detected hard LOCKUP on cpu 2" and after that the reboot-loop starts again..
wolfyreload
wolfyreloadβ€’4d ago
I would try something different. Try install the normal non-nvidia version of Bazzite desktop. See if it boots and that you can set it up. Then see if you can just rebase to the nvidia version afterwards (use the instructions on the website for rebasing). This route will tell you if there is an nvidia problem or some other issue altogether.
Mamoulian
MamoulianOPβ€’4d ago
thanks for your reply πŸ™‚ by "normal" you mean the AMD-GPU version, right? and for rebasing you mean the part under "Existing Fedora Atomic Desktop Users" right next to the download?
wolfyreload
wolfyreloadβ€’4d ago
Yup. Thats what I'm thinking, maybe you can get in and get a basic set up then follow those instructions and switch to the nvidia image.
Mamoulian
MamoulianOPβ€’4d ago
Ok, i will try that, thx! i just installed the normal version: same issue 🫣
Kyle Gospo
Kyle Gospoβ€’4d ago
That at least confirms it's a you problem Not sure what's up with your hardware, but at least you can do some research now outside of Bazzite to try and figure it out
Mamoulian
MamoulianOPβ€’3d ago
Even if i knew that answer was coming i was afraid of it. πŸ˜… Because now, i have no clue where to start looking and how. What baffles me is that i have zero issues with Windows
wolfyreload
wolfyreloadβ€’3d ago
Next step would be to try Fedora Kiniote and see if you have the same problem, if so your system just might not like Fedora atomic. I would then try Nobara, then you can tell if your issue is something Fedora based (but not atomic). If none of those work you could go further out with something like Linux Mint. Windows 10 is always an option for a bit and try again later.
asen23
asen23β€’3d ago
i found this thread https://askubuntu.com/questions/1278399/dual-system-ubuntu-20-04nvidia-gpu-i2c-timeout-error-ucsi-ccg-i2c-transfer looks like its nvidia driver issue, but im not sure how to do the step if you cant even boot
Ask Ubuntu
[Dual system, Ubuntu 20.04]nvidia-gpu: i2c timeout error; ucsi_ccg:...
I have been tortured by a tiny bug for a long time. Now I really hope to fix it. They only shows when I boot/turn off my computer, although it doesn't influence anything. when I boot my pc, it usu...
wolfyreload
wolfyreloadβ€’3d ago
I found this thread, https://forum.proxmox.com/threads/watchdog-watchdog-detected-hard-lockup-on-cpu-all-how-solve-it.121812/ This user was getting your error, turns out his Linux kernel didn't like the way his RAM was installed if I'm getting the gist of the thread
Mamoulian
MamoulianOPβ€’3d ago
yeah, i found and read both these threads as well. the first left me more confused to be honest. the second told me, that they had crashes caused by faulty ram? i mean, i thought about switching ram modules (have two 8 GB modules).. i added those in the specs, and the soundblaster AE-7 i forgot to mention - but this should not cause this, right? next, i will try the other distros as @wolfyreload suggested so far, thank you all! 😊 Fedora Konoite: i don't get the "watchdog..." but other then that it behaves the same.. Nobara actually shows the "Watchdog..." before the installation starts and then goes to reboot
wolfyreload
wolfyreloadβ€’3d ago
That at least saves a bunch of time not having to install to see the error Try Linux Mint so you trying something that isn't in the Fedora family. If that still fails try having one RAM module plugged in and see what happens and go on from there
Mamoulian
MamoulianOPβ€’2d ago
i did a full memtest86 run over night which passed flawlessly will try a mint or ubuntu install next i just tried installing POP OS because i already had it on my stick with now lots of other different ISOs 🫣 and it brought up "the watchdog detected hard LOCKUP on cpu 8" before entering the installation menu 😳
wolfyreload
wolfyreloadβ€’2d ago
Maybe it's time to try the RAM thing then. Leave one RAM stick installed and see if POP OS boots.
Want results from more Discord servers?
Add your server