On 11/16/18 4:50 AM, Stephen Morris wrote:
On 14/11/18 8:46 am, Ed Greshko wrote:
> On 11/14/18 5:32 AM, Stephen Morris wrote:
>> My hardware clock is running a couple of seconds slow as well.
>>
>> Just as a matter of curiosity, when you say if you issue hwclock from the bios
(how have
>> you done that) what does journalctl show for the same time? Does it show, using
your
>> example, 2018-11-12 21:47 or does it show 2018-11-13 21:47?
> I did not say what you think I said.
>
> I said, "But if I reboot and go into the BIOS
it will show 2018-11-12 21:47", which I
> thought was clear.
>
> To expound. I reboot, enter F2 when the Boot (not grub) splash screen comes up and
enter
> the BIOS setup of the motherboard.
I've checked my bios and the bios home screen shows the date and time as local time
(I
also don't remember seeing any functionality on any bios screen to change that. I
have
had motherboards in the past that have provided that functionality.).
There must be a way to change it since someone must have set it at some point in time.
Until you get it set to GMT/UTC you're going to have strange times in your logs.
Going into a terminal shell once KDE had started up and issuing the hwclock command I
get the following output which is not an issue:
bash-4.4$ sudo hwclock
2018-11-16 07:21:53.014617+11:00
From the same terminal, issuing journalctl -b 0 I get the following messages as the
first set of messages it displays. The time at the beginning of the messages as to when
the system was booted, being 18:17:18, is correct as GMT time relative to my time zone,
which is GMT+11 as hwclock shows, but the date of Nov 16 is wrong for GMT, it should be
Nov 15. The correct GMT time for my time zone relative to when I booted is Nov 15
18:17:18. Hence the question of exactly what is that format supposed to be?
When looking at journalctl messages to try to determine why my vpns are timing out,
where the vpn was started after KDE was active, the time in the messages were definitely
local time.
bash-4.4$ journalctl -b 0
-- Logs begin at Wed 2016-01-06 07:29:31 AEDT, end at Fri 2018-11-16 07:22:16 AEDT. --
Nov 16 18:17:18 localhost.localdomain kernel: Linux version 4.18.14-200.fc28.x86_64
(mockbuild(a)bkernel03.phx2.fedoraproject.org) (gcc version 8.1.1 20180712 (Red Hat
8.1.1-5) (GCC)) #1 SMP Mon Oct >
Nov 16 18:17:18 localhost.localdomain kernel: Command line:
BOOT_IMAGE=/vmlinuz-4.18.14-200.fc28.x86_64
root=UUID=8dae94dc-1c3e-4be1-b1f8-b146f094314b ro rd.driver.blacklist=nouveau
modprobe.blackl>
Nov 16 18:17:18 localhost.localdomain kernel: random: get_random_u32 called from
bsp_init_amd+0x20b/0x2b0 with crng_init=0
Nov 16 18:17:18 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x001:
'x87 floating point registers'
Nov 16 18:17:18 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x002:
'SSE registers'
Nov 16 18:17:18 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x004:
'AVX registers'
Nov 16 18:17:18 localhost.localdomain kernel: x86/fpu: xstate_offset[2]: 576,
xstate_sizes[2]: 256
Nov 16 18:17:18 localhost.localdomain kernel: x86/fpu: Enabled xstate features 0x7,
context size is 832 bytes, using 'standard' format.
Nov 16 18:17:18 localhost.localdomain kernel: BIOS-provided physical RAM map:
regards,
Steve
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://getfedora.org/code-of-conduct.html
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
--
Fedora Users - The place to go to beat OT dead horses :-) :-)