jlobue10

Thanks for getting back to me. Yes, that verbose output looks much more normal than what I'm seeing on the Stable branch. This gives me hope that this is a...

Same output for that. ``` $ pacman -Q|grep efivar efivar 38-2 ``` and kernel is: ``` $ uname -r 5.13.0-valve36-1-neptune ```

``` $ efivar -l |grep BootOrder | xargs -L1 efivar -n GUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c Name: "BootOrder" Attributes: Non-Volatile Boot Service Access Runtime Service Access Value: 00000000 03 00 01 00 00...

Yes, no problem. Not necessarily garbled, but it definitely doesn't look like a normal output to me either (lots of hex characters)... ``` $ efibootmgr -v BootNext: 0001 BootCurrent: 0000...

Understood. I didn't mean to imply that anything was wrong with the verbose output, it's just not the typical verbose output that I've been looking at. If those extra hex...

``` $ efivar -l | grep 0003 8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0003 ```

Yes, I understand that dual boot is not officially supported. I am not going to tinker with deleting the Windows EFI entry (annoying to re-add properly with `diskpart` and `bcdedit`...

Output: ``` $ efivar -n 8be4df61-93ca-11d2-aa0d-00e098032b8c-Boot0003 GUID: 8be4df61-93ca-11d2-aa0d-00e098032b8c Name: "Boot0003" Attributes: Non-Volatile Boot Service Access Runtime Service Access Value: 00000000 00 00 00 00 74 00 57 00 69 00...

I must have been plugged in to my dock with an ethernet cable plugged in. I don't think I've changed anything in BIOS other than setting VRAM to use 4GB.

I do have the official dock, but I never even opened the packaging for it. XD This `efibootmgr -v` output was with a JSAUX dock.