On Mon, 15 Jun 2020 21:35:40 +0100
tux...@sapo.pt wrote:
> The devuan images are tested,
> And so, I personally, advise always to stick with its kernels, but
> anyone is free to mix what they want too :)
The Armbian kernel works fine. Remember there is no Beowulf image yet
for the OPi-Zero.
Citando richard lucassen via Dng :
No, even cronjobs do not work or give segmentation fault. It must be
the hardware. There must be a batch with these issues, I'm not the only
one BTW. I wonder if it has got something to do with the wifi chip. A
crash occurs earlier if you load the kernel
On Fri, 12 Jun 2020 04:41:17 -0700
Rick Moen via Dng wrote:
> > Yes and no:
> >
> > -n Use SNTP (old RFC 2030, currently RFC 5905) instead of the RFC
> > 868 time protocol.
> >
> > # rdate -n ntp.xs4all.nl
> > Fri Jun 12 12:07:04 CEST 2020
>
> Point taken. SNTP _is_ worthy of respect
Quoting richard lucassen (mailingli...@lucassen.org):
> Yes and no:
>
> -n Use SNTP (old RFC 2030, currently RFC 5905) instead of the RFC
> 868 time protocol.
>
> # rdate -n ntp.xs4all.nl
> Fri Jun 12 12:07:04 CEST 2020
Point taken. SNTP _is_ worthy of respect -- but I'd personally
On Fri, 12 Jun 2020 01:19:50 -0700
Rick Moen via Dng wrote:
> > Have a look at "rdate":
>
> I'm glad it works for you, but no.
>
> RFC 868 Time Protocol was obsoleted when NTP became ubiquotous in the
> 1980s. IMO, there's no point in keeping rdate(8) around when there
> are multiple good NTP
Quoting richard lucassen (mailingli...@lucassen.org):
> Have a look at "rdate":
I'm glad it works for you, but no.
RFC 868 Time Protocol was obsoleted when NTP became ubiquotous in the
1980s. IMO, there's no point in keeping rdate(8) around when there are
multiple good NTP implementations
On Thu, 11 Jun 2020 15:09:37 -0700
Rick Moen via Dng wrote:
> If running ntpdate, depending on how much skew there is from correct
> time, you might need the '-B' option. Quoting the man page:
Have a look at "rdate":
$ apropos rdate
rdate (8)- set the system's date from a remote
Quoting tux...@sapo.pt (tux...@sapo.pt):
> problems with rtc clock are not uncommon, the need for a power
> cycle, seems to be..
>
> This discrepancies, in the date, .. how many days it takes to
> happen, does you have any Idea?
> does the Boards are properly powerup?I mean suficient levels of
>
On Thu, 11 Jun 2020 03:50:54 +0100
tux...@sapo.pt wrote:
> > As I need to apply a power cycle I suppose it is not a software
> > issue (is that right?). I'm just trying the Ascii image to see what
> > will happen, but I'm not very hopefull.
> >
> > Has anyone seen such issues with these boards?
>
Hello richard,
Citando richard lucassen via Dng :
As I need to apply a power cycle I suppose it is not a software issue
(is that right?). I'm just trying the Ascii image to see what will
happen, but I'm not very hopefull.
Has anyone seen such issues with these boards?
problems with rtc
On Mon, 1 Jun 2020 20:56:30 +0200
richard lucassen via Dng wrote:
Oh, BTW, kudos for the one who made these images. Just the strict
necessary. No bloat or junk.
--
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
Hello list,
I just installed the Ascii image for the Orange Pi Zero (H2 CPU). I have
a bunch (20) of these OPi Zero's, running a SysV version of Debian.
Anyway, in practice *all* of these units are unstable (some services
stop working, clock at a weird time like 1937 or 2134). Even a reboot
does
12 matches
Mail list logo
