Open ggardet opened 3 years ago
I am running multiple distros as well as ESXi without issues, this is including 5.11.9 on Fedora 34 without issues.
[ 0.973595] rtc-efi rtc-efi.0: registered as rtc0
[ 0.975773] rtc-efi rtc-efi.0: setting system clock to 2021-03-25T10:28:28 UTC (1616668108)
Not sure if it could be related, but I noticed the following error message:
ERROR: No descriptor returned from SEC
between:
EFI stub: Booting Linux Kernel...
EFI stub: Using DTB from configuration table
and:
EFI stub: Exiting boot services and installing virtual address map...
Nope that is fine. That just means your are running edk2 without secure storage and no signed certificates are available.
You should probably drop into the uefi shell and verify your date and time are working there.
From the UEFI shell, date
returns 08/28/2028
and time
returns 28:28:28 (LOCAL)
which looks wrong!
please set them manually to something close to normal and see if that fixes the issue.
please set them manually to something close to normal and see if that fixes the issue.
Unfortunately, Shell> date 03/26/2021
returns date: Invalid argument - '03/26/2021'
And time 13:53
returns no error, but has no effect.
Were you previously running u-boot on this system? Are you running one of our prebuilt uefi images?
Were you previously running u-boot on this system? Are you running one of our prebuilt uefi images?
I tried u-boot when I got the system long time ago, but switched to edk2 based uefi long time ago. I built locally the firmware from latest sources. I can try a pre-built image if you point me to it.
Same behavior with pre-built image lx2160acex7_2000_700_2600_8_5_2_sd_4a89463.img.xz
From openSUSE Tumbleweed (kernel 5.11.6) with latest firmware, I cannot read
rtc-efi
.Kernel log:
And if I try to read it from user-space:
Is it something known?