On Tue, 17 Mar 2020 at 14:47, home user <mattisonw@xxxxxxxxxxx> wrote:
(On 3/16/20 11:36 PM, Samuel wrote)
> I assume you're using the original released F31 live image.
No, I'm using whatever F-30 live image the Fedora Media Writer grabbed
on March 12. Ah, here it is:
Fedora-Workstation-Live-x86_64-30-1.2.iso
I do not know how up-to-date that actually is.
> Or you could try out the F32 beta live.
That goes in the opposite direction from what I believe is best for my
intended use. I really believe f30 would be best.
> ... One possibility is that the monitor takes too long to sync up
> and the prompt has already gone. I suggest pressing the key as
> soon as the computer beeps.
I'll keep that in mind the next time it gets in to one of them moods.
> You could also check if there's an option in the bios to give
> you more time for pressing it.
It's an ASUS Sabertooth Z77. I checked. In the Advanced Mode, the Boot
screen, the Post Delay Time is set to 8 seconds. I set that years ago,
when it was not in one of them moods. (yes, I've seen this problem before.)
ASUS has weird power management, see:
I was looking at the asus_atk0110 driver when trying to figure out why fan control is not possible on my ASUS M5A78L-MUSB3 and it comes down to the fact that the IC on the MB which is responsible for hardware monitoring and fan control is taken exclusive control over by the BIOS so the kernel has to communicate with the BIOS over ACPI instead of talking with the chip directly.
The asus_atk0110 driver does this but is only reading sensors and nothing else. There is no documentation for the ASUS ACPI tables, which means they have to be reverse engineered.
Just the sort of kernel tweak that can suffer collateral damage after more than 5 years of kernel development:
For background: https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/tsc-resynchronization:
The Linux kernel uses different time sources. The most interesting are the HPET (High Precision Event Timer) and the TSC (Time Stamp Counter).The TSC is the preferred clocksource between the two counters, as it is the fastest one, however it can only be used if it is stable. Currently there are 4 types of TSC present:
- Constant. Constant TSC means that the TSC does not change with CPU frequency changes, however it does change on C state transitions.
- Invariant. As described in the Intel manual: “The invariant TSC will run at a constant rate in all ACPI P-, C- and T-states”
- Non-stop. The Non-stop TSC has the properties of both Constant and Invariant TSC.
- None of the above. The TSC changes with the C, P and S state transitions.
By looking into the flags entry in /proc/cpuinfo we can determine what type of TSC the current processor has (possible values we check for are constant_tsc, nonstop_tsc)
My desktop does have both: constant_tsc, nonstop_tsc
From https://www.phoronix.com/scan.php?page=news_item&px=Linux-Disabling-HPET-CoffeeLake (discussing lnux 5.4 and recent stable kernels):
Some Coffee Lake systems have a skewed HPET timer when entering the PC10 power state and that in turn marks the time stamp counter (TSC) as unstable.
Workarounds from Intel for issues like this can result in collateral damage for older systems. The bug seems to be with Intel firmware, so workarounds may be temporary.
I'll respond to George and Tom, and then come back to netinstall.
[...]
George N. White III
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
