3 ms·

If you see the BIOS screen, then it isn't suspended. It could still be suspend-to-disk, but desktop PCs don't do that. Windows 'fast boot' does work by saving

If you see the BIOS screen, then it isn't suspended. It could still be suspend-to-disk, but desktop PCs don't do that. Windows 'fast boot' does work by saving some critical state on shutdown, but it's still a complete shutdown.

genewitch 2y ago
when booting my 5950x into windows, i never see the bios screen. It's about 50/50 if i see the nvidia bios screen, then i see the motherboard logo with the windows spinner under it. there's about 500ms where i can push F2 or whatever between when the logo shows up and the spinner shows up that i can "enter bios" - but that itself takes about 5 seconds to become fully realized on the screen. I know of what you speak, but i don't know if this is universally true.
- fennecbutt 2y ago
  The motherboard or manufacturer logo is the bios running... For example on xps, bios is now just when the plain dell logo displays. Thank Apple for that sort of thing.
lproven 2y ago
> Windows 'fast boot' does work by saving some critical state on shutdown, but it's still a complete shutdown. Nope. The easy way to falsify this is to dual-boot. If you have Windows Fast Boot enabled, Linux will not be able to mount Windows's NTFS drives, because they are still mounted. This tells us the kernel is just hibernated, not stopped. This is one of my personal annoyances with systemd: if a drive in `/etc/fstab` isn't available, systemd waits for it to become available... forever. So if a drive is mounted (because another OS is hibernated), or it's changed UUID because it's been reformatted, or it's been deleted: your computer won't boot, because systemd is trapped in a retry loop. The easy way to disable fast boot is just to open an Admin Command Prompt and type: powercfg /h off This disables Hibernation. The `C:\HIBERFIL.SYS` file is deleted and Windows now will do a full shutdown and full boot every time... and when you boot into Linux, you can now mount the Windows drives. Note, with hibernation as opposed to suspend, you still see the BIOS screen.
- Filligree 2y ago
  That's the exact state I was talking about... but you did go into more detail. :)

genewitch 2y ago

when booting my 5950x into windows, i never see the bios screen. It's about 50/50 if i see the nvidia bios screen, then i see the motherboard logo with the windows spinner under it. there's about 500ms where i can push F2 or whatever between when the logo shows up and the spinner shows up that i can "enter bios" - but that itself takes about 5 seconds to become fully realized on the screen. I know of what you speak, but i don't know if this is universally true.

fennecbutt 2y ago
The motherboard or manufacturer logo is the bios running... For example on xps, bios is now just when the plain dell logo displays. Thank Apple for that sort of thing.

lproven 2y ago

> Windows 'fast boot' does work by saving some critical state on shutdown, but it's still a complete shutdown. Nope. The easy way to falsify this is to dual-boot. If you have Windows Fast Boot enabled, Linux will not be able to mount Windows's NTFS drives, because they are still mounted. This tells us the kernel is just hibernated, not stopped. This is one of my personal annoyances with systemd: if a drive in `/etc/fstab` isn't available, systemd waits for it to become available... forever. So if a drive is mounted (because another OS is hibernated), or it's changed UUID because it's been reformatted, or it's been deleted: your computer won't boot, because systemd is trapped in a retry loop. The easy way to disable fast boot is just to open an Admin Command Prompt and type: powercfg /h off This disables Hibernation. The `C:\HIBERFIL.SYS` file is deleted and Windows now will do a full shutdown and full boot every time... and when you boot into Linux, you can now mount the Windows drives. Note, with hibernation as opposed to suspend, you still see the BIOS screen.

Filligree 2y ago
That's the exact state I was talking about... but you did go into more detail. :)