Hello Camtaf,
Take a look at this image here:
https://dev1galaxy.org/viewtopic.php?id=3209&p=3

see the last 2 posts, and test it on raspberrypi 4

You welcome,
The important thing is that you managed to take some conclusions from it, and see the limitations you have on your config..

I also tested a lot, but with the power supply I have.. no way( I need to find another way.. ), I have rpi1, which I believe is more limited than rpi3..
The hard-drives disks, don't spin..

An example case:
I have a NAS( 3 Seagate Ironworlf disks ),
After startup, power consumption goes around 22-25Watts( normal operation ),
But when disks start spinning at beginning... I see in my PowerMeter spikes of around ~60Watts.. which is more than 2x the power consumption in operation..
Yes they are brief, but they are there..
Then around 40watts, after that they start consuming ~20-25watts( normal operation )..

My NAS disks are 3.5"( with 2.5"  disks numbers are off-course a lot lower accordingly.. ), but it gives me the notion of power needed to start a drive vs normal utilization( after spinning up the plates )..

The USB 2.0 Specification says that is can deliver "5 units of 100mA each", so by the Specification we are talking about 500mA Max( I believe its per port.. ).
One thing are Specifications, other thing is the real hardware around which is made to be cheap, so it can be competitive..
chargers,power regulators, usb hubs, circuitry limitation designs, Lots of factors..

Yeah,
I would say that, if it has a Global limitation of 600mA,
The best option would be to find a hard drive that is very very low power( which nowadays will be each time more difficult to find.. ).

If you find a very low power harddrive, that works well on this devices,
Please let us know

hello Altoid,

It could be..
But I would experiment in the rpi3 with a flash pen drive, just in case, to check if it works..

Anyway,
You can sort that out, maybe( if the config is present in the kernel.. )..

zgrep -Ei "_USB_STORAGE|_BLK_DEV_SD" /proc/config.gz

1) If its not present then its what we were expecting..
You will need that module..

2) If everything seems ok to you,
With is been available, compiled not as a module[ =y ]
then I advice to test with a usb pendrive

Check if it was compiled in the kernel

you welcome,
nice you succeded

yeah the udev rule is not shipped by default,
Because its very difficult to create a udev rule for all boards..
Each one is using a different mac-address and the static udev rule would fail..

yup with eth0,
Now everything should work ok( even firewall( iptables ) will work now )..

It was an attempt to generate a always persistent name between reboots, to machines that have several Ethernet Ports..
But in RaspberryPi is gets ugly,
And doesn't make sense, since we only have one Ethernet port, it will always be 'eth0', no need for generating names..

Also, the automatic persistent names generation,
Breaks compatibility with lots of software( you were experiencing that.. )

Almost everyone out there is experiencing problems with that, at some point..

Regards,

Predictable?
that name is everything but not predictable( 'enxb827eb14085f' )..
your madaddress is: b8:27:eb:14:08:5f

Remember to change it in the heredocument.. like this:

cat - <<EOF > /etc/udev/rules.d/70-persistent-net.rules 
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="b8:27:eb:14:08:5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
EOF

After this you should get the network name correctly( 'eth0' ),
reboot the system and check..

Also to get a login prompt via serial, you need in the '/etc/inittab' something like:
T0:23:respawn:/sbin/agetty -L ttyAMA0 115200 vt100

restart the system and check if you get a login tty via serial..

you can bringup the ethernet with that "marvelous" name, with:
ifdown enxb827eb14085f && ifup enxb827eb14085f
but that should not be needed, after the udev rule in place..

After renaming the Ethernet to a sane name,  you should only maintain in '/etc/network/interfaces' ,
(...)
allow hotplug eth0
iface eth0 inet dhcp

you need a login tty in the inittab, for serial login
its above the line you need

it would be configured to work with dhcp I guess.
it could be the strange naming of the network..

do a 'ifconfig', and post the result..
A 'dmesg' would also be great

it could be that you need to rename the interface, try with this:

cat - <<EOF >> /etc/udev/rules.d/70-persistent-net.rules 
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="yours_maccaddress", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
EOF

You have a rpi2B right?
this image is known to work well with rpi1..
It would be interesting to get a 'dmesg'  output from this image, running in your board,
Also a 'cat /proc/cpuinfo'

You can access it via serial right?

There are there arm64 devuan images for rpi3

Like this one

No problem arilogue
you welcome..

When you can

hello mmaglis,
Does you have a usb-serial cable to do some debug on that Image?

Does you experimented the image here: http://arm-files.devuan.org/

Hello arilogue,
The link for download the image is in the page, or here, its a recent image with beowulf..

Its a description of it in this thread.

You don't have indeed wlan0..
The Wireless device is BCM4343x WiFi..

The dmesg, would be better to post it in a service like https://paste2.org/
its better to analyze

hello wtf,
Can you boot and have Ethernet in Devuan xu4 image?

Because that seems to be a difference,
Illegalum detected that he doesn't have Ethernet, on the devuan xu4 image.

Perhaps because of Power supply differences,
The supply voltage to the usb-ethernet controller comes from different places and so, Ethernet is not power properly..

Can you check with devuan xu4 image?
if that doesn't work( xua devuan image...ethernet ), can you install my compiled kernel and check if everything works then?

Thanks in advance,

EDIT: there are there a HC1 dts file even in hardkernel '4.14.165':
https://github.com/hardkernel/linux/blo … oidhc1.dts