Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-30 Thread Alexandre Belloni
On 30/09/2019 11:53:16+0200, Uwe Kleine-König wrote: > Hello, > > On 9/30/19 10:37 AM, Rick Thomas wrote: > > Another case where this argument falls down is the Cubox-iPro which has two > > hardware clocks. The first, labeled /dev/rtc0 by the Debian kernel, is > > accurate as long as the power

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-30 Thread Uwe Kleine-König
Hello, On 9/30/19 10:37 AM, Rick Thomas wrote: > Another case where this argument falls down is the Cubox-iPro which has two > hardware clocks. The first, labeled /dev/rtc0 by the Debian kernel, is > accurate as long as the power is up, but it has no battery backup, so when > the power fails t

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-30 Thread Rick Thomas
> On Sep 30, 2019, at 12:41 AM, Alexandre Belloni > wrote: > > My opinion is that distributions should stop relying on HCTOSYS and do > the RTC read from userspace. This is especially important because > distros are hardcoding rtc0 as the RTC to read from which is most likely > to not be the

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-30 Thread Rick Thomas
Thanks for the explanation! > On Sep 30, 2019, at 12:22 AM, Uwe Kleine-König wrote: > > IIRC systemd-timesyncd fast forwards the time at boot time to be not > earlier than before the last shutdown. Maybe this is not active for you? > (There is > /lib/systemd/system/systemd-timesyncd.service.d/di

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-30 Thread Alexandre Belloni
On 29/09/2019 22:05:38+0200, Uwe Kleine-König wrote: > Hello, > > [I repaired the quoting style and expanded To: a bit] > > On Sun, Sep 29, 2019 at 07:36:27PM +, John Blake wrote: > > On Saturday, September 28, 2019, 3:52:11 PM MDT, Rick Thomas > > wrote: > > > On Sep 28, 2019, at 1:14 PM,

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-30 Thread Uwe Kleine-König
Hello Rick, On Sun, Sep 29, 2019 at 07:47:40PM -0700, Rick Thomas wrote: > > On Sep 29, 2019, at 1:05 PM, Uwe Kleine-König > > wrote: > > > > The step from 4.19.67-2 to 4.19.67-2+deb10u1 is harmless for this > > problem. The issue that John is describing comes from a change by Roger > > Shimizu

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-29 Thread Rick Thomas
> On Sep 29, 2019, at 1:05 PM, Uwe Kleine-König wrote: > > The step from 4.19.67-2 to 4.19.67-2+deb10u1 is harmless for this > problem. The issue that John is describing comes from a change by Roger > Shimizu to reduce the kernel size[1]. I guess there is some difference > in userspace that is

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-29 Thread Uwe Kleine-König
Hello, [I repaired the quoting style and expanded To: a bit] On Sun, Sep 29, 2019 at 07:36:27PM +, John Blake wrote: > On Saturday, September 28, 2019, 3:52:11 PM MDT, Rick Thomas > wrote: > > On Sep 28, 2019, at 1:14 PM, John Blake wrote: > > > > > > After upgrading my Sheevaplug from S

Re: SheevaPlug, hctosys: unable to open rtc device, after Buster upgrade

2019-09-28 Thread Rick Thomas
I do not have this problem on my sheevaplug running kernel ‘4.19.67-2’ . I see that ‘4.19.67-2+deb10u1’ is available, but not yet installed on this machine. I think I’ll hold off on installing that update for a while! And, FWIW: rbthomas@sheeva:~$ grep RTC_DRV_CMOS /boot/config-4.19.0-6