William Kenworthy <[email protected]> [13-08-25 15:16]: > On 25/08/13 20:50, [email protected] wrote: > > Mick <[email protected]> [13-08-25 13:44]: > ... > > Hi Mick, > > > > this "MoBo" has neither a BIOS and therefore no BIOS battery. > > I added the DS3231 rtc myself to get a battery buffered rtc. > > > > Best regards, > > mcc > > > > > > > > > > > > What is the device ... a raspberry pi? > > A pi also has a rtc thats not battery backed so the first thing you need > to do is set the time as soon as the network comes up with the results > you describe ... nobody cares and the device works fine. > > Under what circumstances is this a problem? - I see where you say some > files have an epoch date, but again thats normal for a pi and doesn't > cause any problems. > > This might help us understand what you are trying to do ... > > BillK > > > >
Hi BillK, nearly.... ;) Its a Beaglebone Black... Regarding the situation of rtcs it is the same as with the Raspi. Changing between "bein connected to the internet" and "being not" creates a chaos is correctly and incorrectly time stamped files. Previously I got headaches while trying to figure out why certain things (emerging, compiling etc.) does not work properly. Secondly I feel be far more comfortably knowing that I do not have to care about the correct time stamps. Thirdly I dont like such a mess on my system... But the question remains: How can I can introduce the existing of a I2C device (the DS3231) to the system as soon as possible? Since the kernel can be configured to not only care about rtc0 but to use any other rtc, it must be possible to introduce/initiate such a device to the kernel in a pre-filesystem-mount state of booting the system...I simply dont know how... Best regards, mcc
