#asahi · 2023-08-04 14:54
sid-linuxhow is the UTC time being maintained ? Does it not derive from RTC or there is some other clock#asahi · 2023-08-04 14:53
sid-linuxbtw... when I do `timedatectl` i notice a ~4 second difference between RTC time and UTC time... is that expected/normal ?#asahi · 2023-08-04 14:42
sid-linuxjournald entries getting lost could be a plausible explanation also. thanks for helping out ! wonder what happend...#asahi · 2023-08-04 14:35
sid-linux*where I can see#asahi · 2023-08-04 14:35
sid-linuxI have timestamps on my system for files that are August 3. Those timestamps make sense. But I'm not able to find a `journalctl -b X` where X=some integer I can see August 3 mention#asahi · 2023-08-04 14:33
sid-linuxyes -- good point. But here the BS time fixed itself. In journalctl -b -1 and journalctl -b -2 the fictional old time is never fixed#asahi · 2023-08-04 14:31
sid-linuxbut the funny thing is i have BS time in my journalctl -b -1 , journalctl -b -2 also#asahi · 2023-08-04 14:12
sid-linuxthe most puzzling thing for me _jannau__has been the fact that seeing entries in /var/log/pacman.log, other time stamps for other applications are all correct and i see a good distribution from Aug 02 - August 04. So it seems the rest of the system seemed to be getting the time correct but `journalctl -b` got it wrong#asahi · 2023-08-04 14:05
sid-linuxyes. there is /usr/lib/modules/6.3.0-asahi-13-1-edge-ARCH/kernel/drivers/rtc/rtc-macsmc.ko#asahi · 2023-08-04 14:05
sid-linuxsorry wrong one#asahi · 2023-08-04 14:04
sid-linux*macsmc-rtkit.ko#asahi · 2023-08-04 14:04
sid-linuxI see macsmc.ko and macsmc-rtkit.so in initrd (/usr/lib/modules/6.3.0-asahi-13-1-edge-ARCH/kernel/drivers/platform/apple)#asahi · 2023-08-04 13:54
sid-linuxAug 04 14:47:58 <some-hostname> kernel: macsmc-rtc macsmc-rtc: setting system clock to 2023-08-04T09:17:58 UTC (1691140678)#asahi · 2023-08-04 13:54
sid-linuxAug 04 14:47:58 <some-hostname> systemd-resolved[537]: Clock change detected. Flushing caches.#asahi · 2023-08-04 13:54
sid-linuxAug 04 14:47:34 <some-hostname> kernel: hci_bcm4377 0000:01:00.1: enabling device (0000 -> 0002)#asahi · 2023-08-04 13:54
sid-linuxAug 04 14:47:34 <some-hostname> kernel: macsmc-rtc macsmc-rtc: registered as rtc0#asahi · 2023-08-04 13:51
sid-linuxim using asahi linux ALARM#asahi · 2023-08-04 13:51
sid-linuxthis is log is for a single boot btw. `journalctl -b`#asahi · 2023-08-04 13:50
sid-linuxtz could have been a possible explanation what explains the jump in 2 days?#asahi · 2023-08-04 13:49
sid-linuxThere is a big jump from Aug 02 -> Aug 04#asahi · 2023-08-04 13:48
sid-linuxthe funny thing is that my system time was not out of sync AFAIK. Looking at /var/log/pacman, other logs and files, they have the correct times on them#asahi · 2023-08-04 13:47
sid-linuxAug 04 14:47:34 <my-hostname> systemd-timesyncd[539]: System clock time unset or jumped backwards, restored from recorded timestamp: Fri 2023-08-04 14:47:34 <my-timezone>#asahi · 2023-08-04 13:47
sid-linuxAug 04 14:47:34 <my-hostname> systemd-resolved[537]: Clock change detected. Flushing caches.#asahi · 2023-08-04 13:47
sid-linuxAug 02 05:24:48 <my-hostname> systemd[1]: Reached target Host and Network Name Lookups.#asahi · 2023-08-04 13:47
sid-linux--- snip ... 10 lines later ---#asahi · 2023-08-04 13:47
sid-linuxAug 02 05:24:48 <my-hostname> systemd[1]: Starting Network Time Synchronization...#asahi · 2023-08-04 13:47
sid-linuxI noticed a strange journalctl time discontinuity issue#asahi · 2023-07-12 18:31
sid-linux*going to be like that#asahi · 2023-07-12 18:31
sid-linuxso I hope its not going that again#asahi · 2023-07-12 18:30
sid-linuxlast time updates ceased for weeks (!)#asahi · 2023-07-12 18:28
sid-linuxanybody knows what's up with ALARM. There was a steady stream of package updates which seems to have stopped again... any idea of whats happening?#asahi · 2023-07-11 07:13
sid-linuxAndrewYu: the first step is to get your kernel back. Since /boot is a simply a fat partition on your nvme drive all you need to do is add back the kernel in it. Yes, its probably simpler to restart from scratch as you suggest...#asahi · 2023-07-11 06:51
sid-linuxso both u-boot and grub can be used to boot from an alternate USB media to rescue your main installation.#asahi · 2023-07-11 06:50
sid-linuxI did some investigation that might be pertinent for AndrewYu. 1. u-boot will detect any USB storage device plugged in m1/m2 in advance. 2. grub on m1/m2 also is able to read any USB storage (it supports ext4 and fat)#asahi · 2023-07-11 06:20
sid-linuxmps: thanks for the link -- this seems more like a full setup kind of blog post. I think all AndrewYu needs is to add the file vmlinuz-linux-asahi back to the Asahi boot partition#asahi · 2023-07-11 06:03
sid-linuxDoes anybody know if u-boot and/or grub on will be able to read a ext4/fat formatted usb drive on an m1/m2 asahi?#asahi · 2023-07-11 06:01
sid-linuxYou can also try entering the grub command line and try your luck from there. grub is probably more user friendly also.#asahi · 2023-07-11 06:01
sid-linuxWhen you are in u-boot you might be able to to do more things -- perhaps put in a USB drive with a recovery kernel etc. and boot that. Again, this is something I have not tried with Asahi so your mileage may vary. (The usual warnings apply: when you are doing something low level you should be careful not to mess up things further.)#asahi · 2023-07-11 06:00
sid-linuxAndrewYu: disclaimer -- I'm not sure if this is the best way (or it even works) but you can get into the u-boot shell. You should just press <space> as soon as you see the u-boot icon#asahi · 2023-06-19 14:21
sid-linuxmy system btw seems to be working well. should i be running `update-grub` myself or should i just let it be? (if it aint broke :-)... )#asahi · 2023-06-19 14:08
sid-linuxbut ignored it. It turned out to be harmless for me.#asahi · 2023-06-19 14:08
sid-linuxwhen I was updating#asahi · 2023-06-19 14:08
sid-linux $ grub-mkconfig -o /boot/grub/grub.cfg#asahi · 2023-06-19 14:08
sid-linux $ grub-install ...#asahi · 2023-06-19 14:08
sid-linux of configuration:#asahi · 2023-06-19 14:08
sid-linux incompatibilities, it is advised to run both, installation and generation#asahi · 2023-06-19 14:08
sid-linux to install it to the MBR or UEFI. Due to potential configuration#asahi · 2023-06-19 14:08
sid-linux:: To use the new features provided in this GRUB update, it is recommended#asahi · 2023-06-19 14:07
sid-linuxI did see the following message:#asahi · 2023-06-19 14:07
sid-linuxseems like seb91nihel got unlucky. I wonder what was different in his asahi setup that caused things to fail. Mine worked well.