Re: [DNG] Devuan Jessie End of Life (EOL) archiving

2020-07-12 Thread richard lucassen via Dng
On Sun, 12 Jul 2020 05:58:11 -0300
pekman  wrote:

> Slitaz is very good Linux distribution for old computers. See
> slitaz.org

The latest "news" is from 20 May 2015:

http://slitaz.org/en/news/

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] terminal paste failure

2020-07-02 Thread richard lucassen via Dng
On Thu, 2 Jul 2020 10:02:05 -0400
Haines Brown  wrote:

> This morning I find that the wiress mouse can cut and paste between 
> terminals or nano sessions even with the wired mouse disconnected. 
> Whether the problem is permanently in the past remains to be seen.

Try "reset" in the terminal, sometimes this helps. See "man reset" for
more info.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Orange Pi Zero/Orange Pi PC

2020-06-15 Thread richard lucassen via Dng
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.
 
> That in so many boards,... it could be a batch that went wrong, or  
> badly designed boards..

Must be someting like that. One of these board just stopped replying to
pings and is not accessible through ssh, but each night it sends an
email telling me there are updates for that board.

I'm running Devuan Beowulf with an Armbian kernel and a "performance"
governor. Someone said that switching to "performance" seems to resolve
the issue.

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-15 Thread richard lucassen via Dng
On Mon, 15 Jun 2020 13:15:57 +0100
g4sra via Dng  wrote:

> > No need IMHO, it was the core issue...
> 
> So you have solved the issue, great!

Nope, we found a Quick and Dirty workaround

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-15 Thread richard lucassen via Dng
On Mon, 15 Jun 2020 12:48:16 +0100
g4sra via Dng  wrote:

> >> How do you know the mount is failing ?
> > 
> > It's not mounted after mount command.
> 
> I have not seen any evidence of that, can you point me to it please.

No need IMHO, it was the core issue...

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 21:49:50 +0200
"J. Fahrner via Dng"  wrote:

> > And an earlier suggestion to copy important things to a smaller disk
> > and use that disk, does that probably solve the issue?
> 
> A smaller disk is no option, since this is my media server at home.
> It is filled with 66%.

I meant just to find out if a smaller disk was mounting correctly.

> My mount scripts seem to work around this problem, so I give up in 
> further investigating what is happening.

Ok, I understand that you get moreorless crazy of this issue.
Fortunately the nofail option brought you a bit further.

HAND

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 20:31:22 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-14 20:07, schrieb d...@d404.nl:
> > It is a kernel parameter not a module parameter. You have to add it
> > to your kernel boot line.
> 
> Ok, I found out how to do that. It's in /boot/boot.ini
> But that made no difference to my problem.
> 
> This is my current setup:
> /etc/fstab has the mount option nofail, so the boot does not hang on 
> mountall.
> 
> I have a additional init script mounthdd:

What happens if you change the content of that script:

#!/bin/dash
echo 5 > /sys/module/usb_storage/parameters/delay_use

in a script /etc/rcS.d/00test.sh, just for test, normally you must set
a link.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 19:11:38 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-14 19:07, schrieb J. Fahrner via Dng:
> > modinfo: ERROR: Module usb_storage not found.
> 
> Maybe they have their own drivers for usb?
> 
> # find /lib/modules/3.16.82+/kernel/drivers -name '*storage*'
> /lib/modules/3.16.82+/kernel/drivers/usb/gadget/g_mass_storage.ko
> /lib/modules/3.16.82+/kernel/drivers/usb/gadget/usb_f_mass_storage.ko

$ find /lib/modules/5.6.0-2-amd64/kernel/drivers -name '*storage*'
/lib/modules/5.6.0-2-amd64/kernel/drivers/usb/storage
/lib/modules/5.6.0-2-amd64/kernel/drivers/usb/storage/usb-storage.ko
/lib/modules/5.6.0-2-amd64/kernel/drivers/usb/gadget/function/usb_f_mass_storage.ko

Or the module is built in the kernel.
What tells "modinfo g_mass_storage"? If it's the same module as
usb_storage having the same parameters, then:

echo "options g_mass_storage delay_use=5" > \
  /etc/modprobe.d/g_mass_storage.conf

It's a pretty old kernel, if it doesn't work and the module is built
in, one thing you might try is to put:

#!/bin/dash
echo 5 > /sys/module/usb_storage/parameters/delay_use

in a script /etc/rcS.d/00test.sh

HTH

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 18:38:48 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-14 17:25, schrieb richard lucassen via Dng:
> > echo "options usb_storage delay_use=5" > 
> > /etc/modprobe.d/usb_storage.conf
> 
> seems not to work.
> 
> After boot:
> 
> cat /sys/module/usb_storage/parameters/delay_use
> 1

That's rather strange. From "modinfo usb_storage":

parm: delay_use:seconds to delay before using a new device (uint)

And what happens if you load the module in advance?:

echo "usb_storage" >> /etc/modules



-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 17:24:01 +0200
richard lucassen via Dng  wrote:

Oops:

echo "options usb_storage delay_use=5" /etc/modprobe.d/usb_storage.conf

must be:

echo "options usb_storage delay_use=5" > /etc/modprobe.d/usb_storage.conf

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 14:12:21 +0200
"J. Fahrner via Dng"  wrote:

> Very big device. Trying to use READ CAPACITY

You may try this:

echo "options usb_storage delay_use=5" /etc/modprobe.d/usb_storage.conf

https://bbs.archlinux.org/viewtopic.php?id=125831

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 13:03:13 +0200
"J. Fahrner"  wrote:

> But if I do it interactively with "sudo mount /hdd" the drive gets 
> mounted and the waiting daemons are started.
> 
> I'm very confused...

When you mount it interactively the path is different and maybe it's
waiting for some input.

Try to add to the script:

PATH=${PATH}:/sbin:/usr/sbin

and

mount /dev/disk/ /mnt/mountpoint http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 13:03:13 +0200
"J. Fahrner"  wrote:

> But if I do it interactively with "sudo mount /hdd" the drive gets 
> mounted and the waiting daemons are started.
> 
> I'm very confused...

It's weird. What does "dmesg" tell?

dmesg > /tmp/dmesg

and look if there are any messages there

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-14 Thread richard lucassen via Dng
On Sun, 14 Jun 2020 08:21:51 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-13 22:10, schrieb richard lucassen via Dng:
> > I have no idea. But mountall is in runlevel S, not 2. What if you
> > mount it explicitely in a temporary script
> > called /etc/rcS.d/99mount.sh ? That
> > is before runlevel 2 starts.
> 
> Looks like it has something to do with huge_file support:
> https://forums.gentoo.org/viewtopic-t-905312-start-0.html

Yes, I already ran into such an issue a few years ago. I mounted a disk
created ext4 with a newer Debian on a machine running an older Debian
and it would not mount (at all). I looked it up in a script I made and
for me it was the metadata_csum option that was inserted by the newer
Debian and the old one did not support this. So the trick was to format
the disk without that option:

-- 8< -

mkfs.ext4 -O '^metadata_csum' /dev/mmcblk0p3 https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 21:09:06 +0200
"J. Fahrner"  wrote:

> > No, but I asked you why not create the root filesystem on that disk.
> 
> If "mount -a" does not work in runlevel 2, why should it work in boot 
> stage 1?

I have no idea. But mountall is in runlevel S, not 2. What if you mount
it explicitely in a temporary script called /etc/rcS.d/99mount.sh ? That
is before runlevel 2 starts.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 21:07:37 +0200
richard lucassen via Dng  wrote:

> No, maybe it has got something to do with these "big disk" messages.
> Wouldn't it be an idea to copy a part of that dist to a "not such a
> big disk" and see what happens? 

s/dist/disk/ 


-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 20:28:03 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-13 20:18, schrieb richard lucassen via Dng:
> > That was the "rootwait" parameter as I said somewhere. Used for USB
> > and MMC disks.
> 
> "The rootwait kernel parameter only affects the first stage of boot, 
> while the kernel is waiting for its initial root device"
> 
> https://stackoverflow.com/questions/14806294/linux-kernel-parameter-rootwait-being-ignored#14806347
> 
> That has nothing to do with my problem.

No, maybe it has got something to do with these "big disk" messages.
Wouldn't it be an idea to copy a part of that dist to a "not such a
big disk" and see what happens? 

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 20:28:03 +0200
"J. Fahrner via Dng"  wrote:

> "The rootwait kernel parameter only affects the first stage of boot, 
> while the kernel is waiting for its initial root device"
> 
> https://stackoverflow.com/questions/14806294/linux-kernel-parameter-rootwait-being-ignored#14806347
> 
> That has nothing to do with my problem.

No, but I asked you why not create the root filesystem on that disk. I
have several Orange Pi's using a USB disk as root device. That works
perfectly well. Also on PCEngine's Apu, see its lilo config:

image=/boot/vmlinuz-4.9.223
label=4.9.223
read-only
append="rootwait root=/dev/sda3 console=ttyS0,115200n8"

R.

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 16:50:29 +0200
Didier Kryn  wrote:

>     I had a problem around 15 years ago booting a Powerpc SBC with
> rootfs on a USB disk and without initramfs. around 15 years ago. Even
> though the disk was powered on its own, it didn't start spinning
> before the driver started it. I solved it by adding a delay to the
> kernel before mounting the rootfs - there was a parameter for that.
> 
>     Maybe it's just enough to add such a delay before trying to mount
> your USB disk.

That was the "rootwait" parameter as I said somewhere. Used for USB and
MMC disks.

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 10:20:46 +0200
"J. Fahrner via Dng"  wrote:

> Thats exactly what I'm expecting, waiting indefinitely. The same as 
> mounting in fstab without nofail option.

The nofail means that it wil mount automatically, but if the disk
is absent it won't give errors. But it does not wait for the device! 

> I can't experiment here. If it does not boot I have to remove the
> emmc card and undo the change on my pc.

ok, I assume it's u-boot? In that case you can easily try to boot from
another disk. But apparently you do not have access to the device?

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 09:55:54 +0200
"J. Fahrner"  wrote:

> Am 2020-06-13 09:49, schrieb richard lucassen:
> > What is on that disk? Why not make that disk the root filesystem and
> > pass "rootwait" to the kernel?
> 
> I'm afraid that won't work either. If there are problems mounting the 
> disk at this early stage, even the root filesystem will not mount.

That is why there is a rootwait option:

rootwait[KNL] Wait (indefinitely) for root device to show up.
Useful for devices that are detected asynchronously (e.g. USB and MMC
devices).

It waits for the USB HDD to spin up.

R.

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-13 Thread richard lucassen via Dng
On Sat, 13 Jun 2020 08:52:18 +0200
"J. Fahrner via Dng"  wrote:

> Am 2020-06-13 08:25, schrieb J. Fahrner via Dng:
> > nofail was a good hint. Now the system boots, but the usb disk is
> > still not mounted. "mount -a" mounts it without errors after boot.
> 
> What is the best way to run "mount -a" before any initscripts in 
> runlevel 2?
> 
> There is a script /etc/init.d/mountall.sh, but this only runs in 
> runlevel S. Whats the purpose of this script?

/etc/rcS.d/ contains scripts that run before any other runlevel. That's
why "mountall" is there.

> The script provides "mountall". Can I make daemons that need the 
> external disk dependend on "mountall".

What is on that disk? Why not make that disk the root filesystem and
pass "rootwait" to the kernel?

Anyhow, you may try this:


#/bin/dash

### BEGIN INIT INFO
# Provides:  disk
# Required-Start:
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: prepare disk at boot time
### END INIT INFO

case $1 in

start)
  # Edit this:
  /bin/mount /dev/disk /mnt/mountpoint
;;

esac



put this in /etc/init.d/mount-disk.sh
run: update-rc.d mount-disk.sh defaults

and check if there is a link in /etc/rcS.d/ called S00mount-disk.sh

Just a guess. Not tested of course.

My 2cts,

R.

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Orange Pi Zero/Orange Pi PC

2020-06-12 Thread richard lucassen via Dng
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 -- but I'd personally rather
> have and use full NTP tools, and, given that the later are around and
> standard, I don't also need one that does just SNTP (or that plus RFC
> 868 Time Protocol).

I run openntpd and on boards without RTC I made
a /etc/init.d/setboottime using rdate that is started right after the
network comes up. After that openntpd and all other scripts find a
clock that is not at 1-1-1970 01:00. I know openntpd has an option to
set the clock before it starts but at that time I had some problems
with it so I stayed with rdate.

I used to use ntp and ntpdate -B, but as I switched to openntpd I
resolved the non-RTC issue with rdate. Remember that is just the clock
of a small board, not a stratum 1 server ;-)

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Boot hangs with usb disk active in fstab

2020-06-12 Thread richard lucassen via Dng
On Fri, 12 Jun 2020 17:01:14 +0200
"J. Fahrner via Dng"  wrote:

> Any ideas how to debug this problem?
> 
> This is the fstab entry:
> 
> LABEL=Elements /hdd ext4 defaults  0 2

Try to add "nofail" or "noauto":

LABEL=Elements /hdd ext4 defaults,nofail  0 2

LABEL=Elements /hdd ext4 defaults,noauto  0 2

Just to see if it comes up.

Just my 2 cts,

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Orange Pi Zero/Orange Pi PC

2020-06-12 Thread richard lucassen via Dng
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 implementations available.

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

:-)

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Orange Pi Zero/Orange Pi PC

2020-06-12 Thread richard lucassen via Dng
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 host

I use it on boards without RTC, just after the network comes up and
before openntpd takes over. No need for "fake-hwclock".

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Orange Pi Zero/Orange Pi PC

2020-06-11 Thread richard lucassen via Dng
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?
> 
> 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  
> Voltage/Current..
> 
> Try to update the date with something like 'ntpdate ntp_server_ip'
> And see is that helps, if yes then you can run it via a cronjob,
> from time to time..

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 module.

> For beowulf only orangepi_zero_plus2 image is available..
> 
> Try to install the Devuan ascii image:
> https://mirror.leaseweb.com/devuan/devuan_ascii/embedded/README.txt

The ASCII image is ok, but I updated this image to Beowulf and I used
Armbian kernel with it. But I fear it will crash again. Anyway, I just
got some Rasberry Pi Zero-W now and I think I will stay with these
boards. Remember I have also Orange Pi PC, different CPU, suffering
from the same issues.

R.

-- 
richard lucassen
https://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


Re: [DNG] Orange Pi Zero/Orange Pi PC

2020-06-01 Thread richard lucassen via Dng
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
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng


[DNG] Orange Pi Zero/Orange Pi PC

2020-06-01 Thread richard lucassen via Dng
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 not help. To get things back in order a power cycle is necessary.
The Orange Pi PC also suffers from this phenomenon (H3 CPU). Switching
on the wireless interface speeds up the appearance of the problem. When
it's idle there's no problem. I also tried to set the max CPU freq to
800 MHz, but no way. These devices have different tasks and thus
different user space software.

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?  

R.

-- 
richard lucassen
http://contact.xaq.nl/
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng