citipoy.blogg.se - Surface booting loop trusted platform module windows 10

SURFACE BOOTING LOOP TRUSTED PLATFORM MODULE WINDOWS 10 UPDATE

DMI: Microsoft Corporation Surface Laptop 3/Surface Laptop 3, BIOS 7.100.140

x86/fpu: Enabled xstate features 0x2e7, context size is 2440 bytes, using 'compacted' format. x86/fpu: xstate_offset: 2432, xstate_sizes: 8 x86/fpu: xstate_offset: 896, xstate_sizes: 512 x86/fpu: xstate_offset: 832, xstate_sizes: 64

x86/fpu: xstate_offset: 576, xstate_sizes: 256 x86/fpu: Supporting XSAVE feature 0x200: 'Protection Keys User registers' x86/fpu: Supporting XSAVE feature 0x080: 'AVX-512 ZMM_Hi256' x86/fpu: Supporting XSAVE feature 0x040: 'AVX-512 Hi256' x86/fpu: Supporting XSAVE feature 0x020: 'AVX-512 opmask' x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'

x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Command line: BOOT_IMAGE=/vmlinuz-linux-surface root=UUID=2fa02087-3ae6-4c88-8898-e760360f6c0e rw rootflags=subvol=root loglevel=7 quiet

SURFACE BOOTING LOOP TRUSTED PLATFORM MODULE WINDOWS 10 UPDATE

Kernel version: Linux surfacelaptop3 5.6.5-arch1-1-surface Update to upstream #1 SMP PREEMPT Sat, 09:08:22 +0000 x86_64 GNU/Linux.

Hardware model: Surface Laptop 3 (Intel i5 1037G7).

I'm not sure why changing the timeout of the Grub boot-up has this effect on the keyboard and touch pad working, or why installing the Linux Surface kernel causes this period of unresponsiveness in Grub. After installing the surface Linux kernel grub will take 10-15 seconds to become responsive for any keyboard input (and the countdown timer only starts after it becomes responsive), and turning off the grub menu or setting the wait timeout to 0 seconds skips this period of unresponsiveness however, it results in the keyboard and touch pad being non-functional upon startup. I just want to be able to use my laptop again.Before installing the Arch Linux kernel, grub will be immediately responsive to keyboard input for selection. Note that I don't have any useful data in the laptop, so I'd be fine with reinstalling windows even if I loose all the data. My device (ASUS X205TA) is listed but the recovery key is not.

I even searched for it in my Microsoft account. Either Secure Boot must be re-enabled, or Bitlocker must be suspended for Windows to start normally." On "Disabled" setting, it says "Bitlocker needs your recovery key to unlock your drive because Secure Boot has been disabled. On "Enabled" setting, it says "Bitlocker needs your recovery key to unlock your drive because Secure Boot policy has unexpectedly changed." It's asking me for bitlocker recovery key on both disabled and enabled settings of secure boot. Now I'm not able to login into my laptop. I didn't succeed and I probably did something stupid. So I was playing with BIOS settings for reformatting my laptop and reinstalling Windows using bootable USB drive.