Question Description
Have you searched the community for related issues?
- No similar issues found.
Please describe the problem you’ve encountered in detail:
- Description:
FydeOS is bootlooping continuously. It just won’t boot to the setup environment either. It’s crashing the initial time for like 5-10 times, after which it booted up somehow. I was setting up a local user on the pendrive and getting FydeOS and suddenly, it shut itself immediately on its own. Now this some “Your system is repairing itself. Please wait.” and a 4 minute timer popped on the corner of my laptop’s screen. It never booted up to login screen ever again, and it kept bootlooping. This was initially flashed with balenaEtcher for the first time. For the second time, I repeated the whole flashing process by using some good old GNOME Disks app, which came up from Open with > Disk Image Writer in “nemo” file manager from cinnamon desktop on my main Debian 13 system. The flash worked again. The issue still persisted. This time I attempted to install FydeOS for Multi-boot with Debian, BlissOS and Windows. The installation unexpectedly took about 30 seconds to complete. This seemed suspicious as my laptop runs on 11-year-old WD Blue 1TB HDD, which is in good condition according to CrystalDiskInfo in Windows 11. I tried booting from the GRUB bootloader that got installed from the live USB installation. Booting from A or B both fail indicating unknown filesystem and booting to it’s recovery tools restarts the laptop entirely. I tried using rEFInd which I had installed earlier on my laptop using Debian 13. I’ve carefully noticed this one thing while FydeOS crashing everytime, which was the “pop” sound that came from the laptop’s speakers. If didn’t crash on the first “pop” sound, it occurs again and keeps on bootlooping, which also includes this “Your system is repairing itself. Please wait.” with a 4-minute timer. One more thing, I was unable to get to TTY shell to execute “hwtuner” as the keyboard (noticed by showing of black screen and, CapsLock and NumLock not turning on)
System & Device Information
-
Hardware & System Configuration:
- Processor: Intel Pentium N3540 (4-cores, burst speed: 2.66 GHz, normal top speed: 2.16 GHz)
- Graphics Card(Please specify if there’s a discrete graphics card): Intel HD Graphics (acc. to fastfetch and neofetch on Debian 13, it was something like “Intel Atom Graphics Z36xxx Series”)
- RAM: 4GB (Debian indicates 3.71GB for some reason)
- FydeOS Version: FydeOS For PC v19
-
Relevant System Logs:
- Open the Chromium browser and enter
/var/log/messagesto retrieve logs. - Log Details:
(could not retrieve any logs due to rapid bootlooping after the appearing or basically the completion of the FydeOS logo animation)
- Open the Chromium browser and enter
Note: If you’ve lost your FydeOS subscription, please refer to this FAQ for assistance.
Extra Question regarding this: could this be for the pendrive’s fault that it’s not working anyway? This is because I tried Windows To Go on this drive and when I tried to boot, not only did it fail to boot, it also broke the boot menu of Windows Boot Manager on the main HDD ({bootmgr} key deleted)
Some more stuff to let everyone help me:
- Long back, probably 3-6 months ago, I had tried FydeOS v22 but I did not face any such issue other than networks not being detected but according to instructions, I did not initially know that my processor was meeting the needs of Intel Legacy, and not Intel Slim.
- Brunch installation into a single disk image normally without running into any issues. But in 22 Slim, I still had networking issues.
- Installing FydeOS with Brunch onto that same pendrive just works without any issues. (Probably because it’s not detecting the fact that its not running on a removable device? I guessed so because The installation screen did not show up)