Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
Guest46 has quit [Quit: Client closed]
lanefu has joined #armbian
archetech has quit [Quit: Konversation terminated!]
califax- has joined #armbian
califax has quit [Ping timeout: 244 seconds]
califax- is now known as califax
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 258 seconds]
<Armbian-Discord>
<NeonFetch> that was an amazing new. long live panfrost! 🙂
archetyp` has joined #armbian
archetyp` has quit [Remote host closed the connection]
archetyp has quit [Ping timeout: 258 seconds]
<Armbian-Discord>
<lanefu> [thebug] someone advised Quectel EC25-A for modem
<Armbian-Discord>
<lanefu> so grabbed one from the ebay
archetyp has joined #armbian
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 240 seconds]
archetech_ has quit [Quit: Konversation terminated!]
archetyp` has joined #armbian
archetyp has quit [Ping timeout: 245 seconds]
archetech has joined #armbian
archetech has quit [Client Quit]
archetech has joined #armbian
archetech has quit [Quit: Leaving]
steev has quit [Ping timeout: 276 seconds]
steev has joined #armbian
wwilly has quit [Ping timeout: 255 seconds]
wwilly has joined #armbian
wwilly has quit [Remote host closed the connection]
<Armbian-Discord>
<djaye> i made these joints 6 years ago back when i was just getting started with soldering
<stipa>
djaye maybe your board has that USB thing to upload the firmware
<stipa>
through USB directly
<stipa>
or, find a datasheet of that rockchip soc and see what pins are uart and try to trace them on the board
<stipa>
is that rockchip the main chip?
<stipa>
what's that big one doing?
<stipa>
in the middle
<Armbian-Discord>
<djaye> yes its a rk3066 chip
<Armbian-Discord>
<djaye> I flash firmware through the microusb port, which is also usb otg
<stipa>
right
<stipa>
try to find in datasheet which pins are uart on rockchip
<Armbian-Discord>
<djaye> the chip is bga so tracing the lines would be quite hard
<stipa>
if you have any better idea go for it
<stipa>
i never did that but i guess when you reboot the device serial port would spit some data that could be probbed by oscope
<stipa>
while probing traces try to guess what each is
<stipa>
and write it down
<stipa>
i guess fast data like buses won't look nice on the oscope if you have a slow one
<stipa>
but serial data should be clear
<stipa>
but even if you found it it might be that it's out of function
<stipa>
or not even soldered to the board
<stipa>
dunno
<stipa>
it's a proper reverse engineering
<stipa>
there are some test points on the back of the board
<stipa>
do you see those four in a row below the power port?
<stipa>
that could be uart
<Armbian-Discord>
<RichNeese> jtag vs console
califax has quit [Remote host closed the connection]
califax has joined #armbian
sven57 has joined #armbian
Guest63 has joined #armbian
<Guest63>
hello
<Guest63>
i need somehelp please
<Guest63>
i m only here ?
<Guest63>
i m new
<Xogium>
don't ask to ask just ask ;)
<Guest63>
hahah
<Guest63>
ok
<Guest63>
sorry
<Guest63>
ok
<Guest63>
i want to install armbian on wince system
<Guest63>
but i don t see the version for
<Xogium>
armbian on wince ?
<Guest63>
on wince device like gps navigator
<Guest63>
it it s 600mhz cpu and 128MB ram
<Guest63>
it can t se the motherboad name on the technical fiche
<Xogium>
well its hard to make a port for such devices considering most of them are probably not even supported by upstream linux and such
<Guest63>
yeah
<Guest63>
but wait llok that
<Guest63>
it s from the site
<Guest63>
Using our automated build system
<Guest63>
If you do not own the proper equipment to build images on your own, you can make use of the automated build system. Packages are recompiled every night (starting at 00:01 CEST) and a few testing images are produced. These images are accessible on the download server under board folder, subfolder “Nightly”.
<Guest63>
it cant see the image
<Xogium>
well, if noone ported your device to armbian, that wouldn't surprise me
<Guest63>
yeah i nown.
<Guest63>
armbian it soo simple
<Xogium>
you would have to make a port of it yourself
<Guest63>
a port ?
<Xogium>
but I don't know any details of this, since I'm neither an user nor a dev of armbian
<Guest63>
do u have a linkplease ?
<Xogium>
porting armbian to your own device
<Armbian-Discord>
<Tonymac32> Yeah, you would need to add a kernel/u-boot etc that supports your device
<Xogium>
including kernel and bootloader and etc.
<Armbian-Discord>
<Tonymac32> I do not believe an Intel StrongARM has any upstream.support. (closest device I can think of at 600-ish mghz from that era)
<Guest63>
the bootloader i will have that with the imager tool but the rest i dont have an image
<Xogium>
if you have the kernel vendor's sources and same for the bootloader it might be workable. Same if upstream linux/bootloader supports your hardware. If you only have binaries that might not work out so well
<Guest63>
ok .
<Guest63>
thanks
<Xogium>
if your kernel is earlier than 3.10, you're out of luck to use armbian
<Guest63>
what s kernel ?
<Xogium>
linux kernel
<Guest63>
yeah but i don t have an image
<Xogium>
vendors tend to fork an old version of it and never update it again
<Guest63>
you have some link please i look ?
<Guest63>
because i have nothing
<Xogium>
well if you don't have even the sources of a kernel or bootloader, you're in for a tough ride
<Xogium>
I'd recommend to check if upstream linux supports the hardware you want to run this on
<Guest63>
with usbimager that create a bootloader no ?
<Guest63>
link rufus or ethcher ?
<Guest63>
just the kernel with the image i don t have
<Guest63>
i check for upstream linux support
<Xogium>
it won't create a bootloader for you
<Xogium>
that will just create a bootable usb drive
<Xogium>
but for it to be bootable you need an actual bootloader in your image
<Guest63>
aah ok.
<Guest63>
i am looking now
<Guest63>
buut
<Guest63>
do i have to switch to and other os ?
<Guest63>
it s other link armbian
<Guest63>
simply root
<Guest63>
?
<Xogium>
I don't understand your question, sorry
<Xogium>
can you try asking another way ?
<Guest63>
yes sorry my bad
<Guest63>
i m looking for an way to find an image. i m looking for linux kernels but do i have to change to an other os no armbian ?
<Xogium>
no the goal would be to integrate this kernel source into your own build
<Xogium>
same for the bootloader
<Guest63>
aaah ok
<Guest63>
i start to underthand
<Guest63>
all the sub os have the same kernel ?
<Guest63>
sorry i use just sometime linux
<Werner>
Buster, Focal, Bullseye... all share the same kernel/uboot package
<Werner>
However these packages are different depending on board family
<Guest63>
aah ok
<Xogium>
thanks Werner ;) you put it in words faster than I could
<Guest63>
now i have to find a 3.10 kernel version
<Xogium>
or later
<Guest63>
ok
<Xogium>
but like I say, it all depends what the vendor of your SoC gives, some don't even publish the source code
<Werner>
you're welcome :)
<Guest63>
and what i do after that ?
<Xogium>
upstream linux is up to 5.13
<Guest63>
thanks a lot
<Xogium>
you do the very same thing for the bootloader
<Xogium>
try to find the sources of the vendor's bootloader, if not, try to see if upstream u-boot -- that is generally the bootloader for ARM is, support your hardware
<Guest63>
ok and armbian in there ?
<Xogium>
if you find all of this, then you might be able to assemble something for armbian, though Werner might be able to help much more on that end since he is a dev of armbian, iirc
<Guest63>
ok
<Guest63>
thanks
<Guest63>
i look for that weekly
<Xogium>
but yeah, one step at a time, as they say ;)
<Guest63>
thanks to take your time for me
<Guest63>
haha
<Xogium>
no problem at all
_whitelogger has joined #armbian
<Guest63>
i have the u boot boot looder
<Guest63>
what format i download ,
<Guest63>
?
<Guest63>
im on windows
<Armbian-Discord>
<IgorPec> we are almost all on linux 😉
<Guest63>
sorry it s ok;
<Guest63>
ok i think i will install that nown
<Guest63>
wait
<Guest63>
i dual boot always
<Armbian-Discord>
<IgorPec> what exactly you want to achive?
<Guest63>
armbian
<Guest63>
on a wince device
<Armbian-Discord>
<IgorPec> with 3.10 kernel and some outdate u-boot --- trash the hw
<Guest63>
i need bootlooker firt with kernel
<Guest63>
newer
<Guest63>
ok
<Armbian-Discord>
<IgorPec> we have trashed Odroid c1 for example for the same reason
<Armbian-Discord>
<IgorPec> and is probably much more populer and used
<Armbian-Discord>
<IgorPec> u-boot was never mainlined, which means death sentence
<Armbian-Discord>
<IgorPec> understand. but hard reality is that whart you want is not simple
<Armbian-Discord>
<IgorPec> and is expensive
<Guest63>
i need just an bootloader u boot ?
<Guest63>
and kernel ?
<Armbian-Discord>
<IgorPec> "just"
<Guest63>
newer better
<Guest63>
no no just
<Guest63>
because i m nob i follow that step
<Armbian-Discord>
<IgorPec> this is hard job for experts
<Guest63>
after that to compile just if i can have more help
<Guest63>
aaah ok
<Guest63>
sorry
<Guest63>
u have a work
<Guest63>
but i start good
<Guest63>
thanks
<Guest63>
a loot for your time
<Werner>
Many of us aren't native English speaker as well. I am German for example and Igor is Slovenia ;)
<Werner>
Porting Armbian to a new/old device can be as easy as a similar image just works OOB up to impossible due to lack of vendor sources and/or configs, hw schematics, device tree and so on...
<Guest63>
ooh ok
<Guest63>
thanks for your explication
<Guest63>
i m from france
<Werner>
Salut :)
<Guest63>
salut
<Guest63>
;)
<Armbian-Discord>
<IgorPec> i drive french car 😉
<Xogium>
ooh, french
<Xogium>
cool
<Guest63>
haha
<Werner>
haha
<Xogium>
I'm french, too !
<Guest63>
i drive a peugeot ,
<Guest63>
?
<Armbian-Discord>
<IgorPec> me 2 308SW
<Guest63>
enchanté
<Guest63>
nice car
<Xogium>
to be fair I did tell him the basic for porting to armbian because I wrongly assumed he knew how ;)
<Armbian-Discord>
<IgorPec> yes, i am pleased. now soncd 308 in a row, after nenault
<Xogium>
so, that's my bad for that
<Werner>
no worries
<Armbian-Discord>
<IgorPec> its hard to know how much persons really know about
<Armbian-Discord>
<IgorPec> its a waya to learn a about hw on the way
<Guest63>
haha i cant code
<Guest63>
or script
<Werner>
Me neither ¯\_(ツ)_/¯
<Guest63>
hahaha
<Guest63>
it s u the erperts
<Guest63>
experts
<Werner>
I wasn't joking actually I have low skills in shell scripting, virtually zero in C or similar. That's it
<Armbian-Discord>
<IgorPec> not many experts / not enough
<Armbian-Discord>
<IgorPec> this means you can learn a massive a lot of things 😉
<Guest63>
yeah sure
<Guest63>
thanks a loot guys
<Guest63>
u do a great job
<Guest63>
continue in that way
<Xogium>
oh, while you guys are around, [TheBug] told me you were in need of some really good build machine for the armbian CI ? I was wondering what specs you guys recommend for this, disk space, ram, cpu
<Xogium>
etc.
<Werner>
main build engine is TR 64 core IIRC
<Armbian-Discord>
<lanefu> 16 CPU 32 gig ram VM would be minimim specs for affing to CI
<Xogium>
oh, is it ? Hmm
<Xogium>
ah well… I was offering because I got this ryzen 7 3700x and 32 gb ram machine right next to me, but I see it won't quite work
<Werner>
If it were dedicated it could be a useful CI runner anyways I think
<Xogium>
yeah… But then it wouldn't do anything else
<Armbian-Discord>
<IgorPec> well, we onlyy use this from time to time
<Xogium>
really ? Hm. I thought CI meant continuous integration so that meant running 24/7
<Xogium>
I probably took the word too litterally
<Armbian-Discord>
<IgorPec> we only rebuild things when its needed
<Armbian-Discord>
<IgorPec> not just like that
<Armbian-Discord>
<IgorPec> kernel changes every few days at best
<Xogium>
would it still be some help though ?
<Xogium>
I'm afraid my ryzen 7 has not much weight against a threadreaper ;)
<Armbian-Discord>
<IgorPec> rootfs rebuild once per month, unless packages are shuffled here and there
<Armbian-Discord>
<IgorPec> it does
<Armbian-Discord>
<IgorPec> i tried to add my NaS as one runner
<Armbian-Discord>
<IgorPec> that was a joke 😉 its 6C Pentium D
<Xogium>
oh wow
<Xogium>
lol
<Armbian-Discord>
<IgorPec> but it has plenty of memory, so i tried
<Xogium>
right so this 3700x has like 8 cores 16 threads and can definitely maintain the 4.2 ghz frequency boost for a while
<Armbian-Discord>
<IgorPec> i have 3950x for workstatuion and its faster then lans dual xeon 😉
<Xogium>
it built a vanilla x86_64 linux defconfig in about 2 minutes
<Xogium>
but I have 1 tb nvme only in there. I did not put any mechanical drive in, although I suppose I could, somehow, maybe. It is my first time using a desktop for years, and I've never put hard drives in there yet
<Armbian-Discord>
<IgorPec> 1h 20m is one threadripper VM, 10h is 1/2 of Pentium D
<Xogium>
yeah, some of them take 4 hours, one took an hour and 40 minutes, something like that ?
<Armbian-Discord>
<IgorPec> for similar job
<Armbian-Discord>
<IgorPec> yes
<Armbian-Discord>
<IgorPec> we have two VM on threadriopper. both has 128C and 80G of memory
<Xogium>
so I guess my ryzen 7 would be closer to the theadreaper ;)
<Armbian-Discord>
<IgorPec> defently
<Xogium>
but not as, er good as it
<Guest63>
u have a link please to assemble kernel and bootlooder with armbian ,
<Armbian-Discord>
<IgorPec> it can be 2-3x slower
<Guest63>
?
<Xogium>
I feel kinda pathetic with my 16 theads 32 gb ram lol
<Armbian-Discord>
<IgorPec> bootloader is diofferent for each hardware
<Guest63>
i use u boot
<Armbian-Discord>
<IgorPec> pathetic is my try with Pentium D 😉 which is much slower
<Xogium>
I have someone with an amd epic server, otherwise, with 40 gb ram…
<Guest63>
^^
<Armbian-Discord>
<IgorPec> Guest63: each hardware different
<Armbian-Discord>
<IgorPec> your hw. no idea
<Xogium>
Model name: AMD EPYC Processor (with IBPB)
<Xogium>
CPU family: 23
<Xogium>
Model: 1
<Werner>
Almost all of our image use uboot too, however the config for every board is different. Since the build script takes care about the process creating uboot and kernel images basically the step by step manual is reading the code: https://github.com/armbian/build
<Guest63>
aah ok
<Guest63>
thanks
<Xogium>
that server is on spinning disk however… and might not be the best choice. Perhaps mine would work faster considering the nvme drive
<Xogium>
but it all depends what disk space requirements you folks have ;)
<Armbian-Discord>
<IgorPec> 250G perhaps?
<Werner>
Spinning disk but good bandwidth would be useful for torrent sharing ;)
<Guest63>
u are on ubuntu or ,
<Guest63>
?
<Armbian-Discord>
<IgorPec> and upload line must be decent since artefacts are uploading to our server
<Xogium>
ah well, hmm
<Xogium>
I don't have decent upload, yet
<Xogium>
250 gb sounds like something I could definitely spare
<Xogium>
I'll see what I can do about getting better connection
<Armbian-Discord>
<IgorPec> how bad it is now?
<Xogium>
erm
<[TheBug]>
:Z
<Xogium>
really really bad
<Xogium>
here, I'll show
<[TheBug]>
simple answer he is on DSL, for $15 more a month can upgrade to fiber I think..
<Xogium>
yep I'd do it but since my income is really new and we did buy the place and are not renting it, we're definitely not sure about the impact going for fiber would make
<Xogium>
not to mention that fiber or not, I'm stuck on wifi because none of the ethernet sockets in the walls work
<[TheBug]>
5Ghz? thats at least 100Mbit
<Xogium>
2.4 ghz only
<[TheBug]>
Ouch
<Xogium>
this wifi router is so crap it is wifi 4
<Armbian-Discord>
<IgorPec> yeah, my 4g connection via vpn is almost 3x faster 😉
<Xogium>
I checked in there and there is litterally not one option to enable anything but 2.4 ghz
<Xogium>
wifi 4, not even wifi 5 let alone wifi 6
<Armbian-Discord>
<IgorPec> upgrade to fiber will cost 150 per year?
<Xogium>
more like 180 euros per year
<Xogium>
it sounds stupid but heh, when you have not a lot of income
<Xogium>
at least with fiber they would be forced to hand a better router
<Armbian-Discord>
<IgorPec> well, we can put that on our bill, you take the rest?
<Xogium>
huh, sorry ?
<Armbian-Discord>
<IgorPec> if you can run one runner at your hw with lets say 95% reliability, we cover you those expenses
<Armbian-Discord>
<IgorPec> but we have to test if it makes sense in term of cpu power
<Xogium>
oh hmm
<Xogium>
how do we test ?
<Armbian-Discord>
<IgorPec> one moment
<Armbian-Discord>
<IgorPec> one VM would be nice to have, so we can ruin it 😉
<Xogium>
heh
<Xogium>
I got debian 11 running over there… I'm er, really not good at debian though so I might act a bit dumbly :p
<Armbian-Discord>
<IgorPec> then i 'll give you instructions how to install github runner
<Xogium>
I'm used to archlinux
<Armbian-Discord>
<IgorPec> this runs on anything
<Xogium>
yeah hmm so
<Xogium>
I could probably make an arch vm in my debian
<Xogium>
but then that would split the cpu power and such. My cpu is only a 8 core 16 threads
<Armbian-Discord>
<IgorPec> your machjine is 24/7 up, right?
<Xogium>
hmm should be, yeah… Unless something bad happens or if I have to shut it down for whatever reason
<Xogium>
but I'd try to warn you guys in advance for that
<Armbian-Discord>
<IgorPec> yeah, that's not a problem. this is 3rd location of runners
<Armbian-Discord>
<IgorPec> if runner is offline its skipped
<Xogium>
ah
<Xogium>
I plan on building stuff using buildroot on there as well, but if you guys build packages and etc only once a month, I figure I can definitely spare a few hours a month just to help you out ;)
<Armbian-Discord>
<IgorPec> a little more often than one per month, but not everyday
<Armbian-Discord>
<IgorPec> kernel packages are rebuild whenever there is a change ion source, once per weekl
<Xogium>
yeah so I can still use it to be my daily driver
<Armbian-Discord>
<IgorPec> yes ofc. lets eveluate some time and we will see
<Xogium>
ah yeah kernels should be no trouble at all… 2 minutes or less to build a vanilla one
<Xogium>
yeah I'll see what I can do for the vm… Given I have only 32 gb ram in total and 16 threads, do you think the vm would work out ok with say, half of this ? That's really the max of my hw
<Xogium>
I'm not sure I could add more ram on my own if I needed that, and my cpu cooler is rather big :D noctua nh-u14-s
<Armbian-Discord>
<IgorPec> give 14 threads to vm
Guest63 has quit [Quit: Client closed]
<Xogium>
huh, and leave 2 for the host ?
<Xogium>
that sounds quite unbalanced
<Armbian-Discord>
<IgorPec> yes, its plenty
<Xogium>
and if I need to take the vm down to build stuff using br and it takes 5 minutes, that would be fine ?
<Werner>
doing a full virtual machine takes ressources. Something simple like lxc would do as well. both host and container could share same ressources as needed
<Armbian-Discord>
<IgorPec> yes, but probably you don't need to
<Xogium>
heh I suppose it the vm doesn't do anything the host is probably free to grab the threads and use them ?
<Xogium>
*if
<Armbian-Discord>
<IgorPec> yes
<Xogium>
fancy
<Armbian-Discord>
<IgorPec> memory can be a bit more tricky to optimise
<Xogium>
yeah…
<Xogium>
random idea though, wouldn't a container work as good ? Like nspawn or lxc
<Xogium>
that way I wouldn't have to carefully share resources between host and vm
<Werner>
downside is that building images wont work without additional hacks or wont work at all. rebuilding kernel is perfectly fine though
<[TheBug]>
Xogium: I will be happy to help you with any setup if you need help -- atm on a meeting so can't really chat but do feel free to ping if you need help
<[TheBug]>
we could also invite him to the server room Igor and talk about that more there?
<[TheBug]>
IgorPec ^
<Armbian-Discord>
<IgorPec> yes, why not.
<Armbian-Discord>
<rpardini> hello
<Armbian-Discord>
<rpardini> i've some N1 cores unused on the Oracle cloud. Should I just up a github runner?
<Xogium>
Werner: why wouldn't rebuilding images work without hacks in a container ?
<[TheBug]>
Manouchehri: it looks like you probably pulled plug on board without shutdown and Armbian tends to do resync of data from memory to hdd on regular basis
<[TheBug]>
if you pulledf power or crash at this time
<[TheBug]>
it could cause the file it mentions to have been corrupt
<[TheBug]>
"It seems that this is related to system time. You can see that restoring time from the RTC failed during boot:"
<[TheBug]>
"When the RTC was not able to keep system time, the system resets to some older date (date at build time). However, the journal on disk has a newer timestamp which makes systemd-journald refusing to load the journal, leading to the messages you are seeing:"
<Armbian-Discord>
<IgorPec> tell raspbian paid staff to fix this
<Manouchehri>
is that sarcasm, or do they actually have paid staff?
<Armbian-Discord>
<IgorPec> they do
<Xogium>
I know why it happens
<Manouchehri>
Xogium: oh?
<Manouchehri>
I just rebooted, fingers crossed if the machine comes back online
<Xogium>
even if you have an rtc in there, whatever they did for detecting it during boot and loading the time from it with hwclock is racy and it does not wait for the rtc devicve to appear
<Manouchehri>
ffs
<Armbian-Discord>
<IgorPec> i think i saw this problem soewhere. you need to sync time ias early as possible
<Xogium>
they could have built the rtc driver in the kernel instead of as a module also, but yeah
<Manouchehri>
and maybe as time goes on, the race happens more often or something?
<Armbian-Discord>
<IgorPec> in init rd
<Armbian-Discord>
<IgorPec> that is rocket scoence for raspbian 😉
<Manouchehri>
ugh
<Manouchehri>
I don't get how armbian is so much better than raspbian.
<Xogium>
yep that's what they are trying to do, but it is loading the module too late, and the udev rule is ran before
<[TheBug]>
simply put it isn't keeping time
<Manouchehri>
Xogium: does it make sense that this happened only after 72 days though?
<[TheBug]>
easiest way around that is use ntpd or regularly run ntpdate
<Xogium>
did you shutdown the pi before those 72 days ?
<Xogium>
no the rtc keeps the time
<Xogium>
it works as intended
<Armbian-Discord>
<IgorPec> raspbiuan is for people to play with
<Manouchehri>
yes, it had been shut down over 72 days ago
<Armbian-Discord>
<IgorPec> its good enough for that
<Xogium>
it is just loaded too late during boot, and the udev rule that tries to restore the time from the rtc using hwclock runs too early so /dev/rtc isn't even present yet
<Manouchehri>
it hasn't been shut down at all in the last 72 days.
<Xogium>
racy, as I said. You might have been very lucky before
<Manouchehri>
how often does the race have a chance of happening?
<Manouchehri>
once a day or something?
<Manouchehri>
if it's an issue during early boot, I thought it would happen only once, during early boot :P
<Manouchehri>
lovely, it's not coming back online (wireguard).
<[TheBug]>
Xogium: do you mean on boot it is basically making the journal before it actually reads current time from rtc into register so you end up with the timestamp always being wrong on the journal?
<[TheBug]>
if so then rming and having it recreate the journal file should be a solution
<[TheBug]>
after boot
<Manouchehri>
yeah I tried that
<Manouchehri>
I removed it
<Xogium>
it's not just that, the rtc at boot is entirely useless
<Xogium>
you could have no rtc connected to the pi, and it wouldn't make one single shred of difference
<Manouchehri>
YESSS
<Manouchehri>
finally
<Manouchehri>
back online
<Xogium>
it is simply not used at boot
<Xogium>
basically when you boot, normally with a proper kernel that has a rtc driver built-in, the kernel itself loads the time from the rtc very, very early at boot, before systemd is even started
<Armbian-Discord>
<IgorPec> what if its a module?
<Armbian-Discord>
<IgorPec> usually that is the case since rtc hw is different
<Xogium>
but since the default kernel is beyond dumb, it has the rtc driver built as a module, and this cannot be performed. The only way to have this, is to have udev run as early as possible during boot, so that it grabs the time using hwclock
<Xogium>
but not too early, or it will not have the kernel module loaded yet
<Manouchehri>
this still doesn't make sense to me why it worked for 72 days
<Armbian-Discord>
<IgorPec> in inird
<Xogium>
well it works fine when the system is up
<Armbian-Discord>
<IgorPec> race conditions are usually act of randomness
<Xogium>
time is saved to the rtc from ntp sync periodically, etc.
<Armbian-Discord>
<IgorPec> power cycle is not reboot
<Manouchehri>
Xogium: right, the system was up
<Xogium>
however restoring time from rtc at boot is where it falls flat
<Xogium>
it may or may not work, as I said, it is very racy
<Manouchehri>
so.. it shouldn't have been a problem?
<Armbian-Discord>
<IgorPec> well, as designed it is a problem
<Xogium>
what do you mean ?
<Manouchehri>
like
<Manouchehri>
we were 72 days past the time it booted
<Xogium>
that does not matter
<Armbian-Discord>
<IgorPec> the problem is related to boot
<Xogium>
as I said when the system runs, the rtc module is loaded, and it is all fine. It even saves the correct time when ntp synced itself
<Armbian-Discord>
<IgorPec> once its up it doesn't matter anymore
<Manouchehri>
IgorPec: right!
<Manouchehri>
the system was up! :P
<Manouchehri>
I only rebooted it *after* this problem happened
<Xogium>
yes, and once you rebooted, it was brought down, then booted again, and this happened. Your system time was not restored from the rtc
<Armbian-Discord>
<IgorPec> you still can have wrong date in journal databnase
<Manouchehri>
but... but... I removed the journal file
<Manouchehri>
and same issue
<[TheBug]>
IgorPec: I think maybe he may be okay cause he removed before reboot, but yeah could end up in same race condition, it makes journal before the clock is updated
<Xogium>
yes
<Manouchehri>
Xogium: no, no, no, the issues started BEFORE I rebooted.
<Xogium>
erm… what ?
<Armbian-Discord>
<IgorPec> same race condition is very possible.