The officially official Devuan Forum!

You are not logged in.

#1 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2019-09-14 19:27:27

Terence wrote:

2. Check 'OpenRC' is parallelized:

(ps -eo "ppid,args" 2>/dev/null || echo "ps call error") \
| awk 'NR==1 || $1==1' | less

Output:

Again, this has nothing to do with openrc either. And even if would be correct, it wouldn't mean "openrc" is "parallelised". It just shows you the processes that have a parent pid (ppid) of 1, e.g., that have been started by init (whichever that is) directly, parallel or not.

So, you are just listing a bunch of processes that have been started by init.You might as well run ps --ppid 1, it's the same think, you don't need that hugeload of command.

Guess what happens on Ubuntu with no openrc installed (and with systemd init):

# (ps -eo "ppid,args" 2>/dev/null || echo "ps call error") | awk 'NR==1 || $1==1'
 PPID COMMAND
    1 /usr/sbin/cron -f
    1 /usr/sbin/ModemManager --filter-policy=strict
    1 /usr/sbin/irqbalance --foreground
    1 /usr/sbin/acpid
    1 /usr/sbin/atd -f
[...]

Guess what we see on Devuan with Sys V and no openrc ever installed:

 (ps -eo "ppid,args" 2>/dev/null || echo "ps call error") \
> | awk 'NR==1 || $1==1' 
 PPID COMMAND
    1 udevd --daemon
    1 /sbin/dhclient -4 -v -pf /run/dhclient.eth0.pid -lf /var/lib/dhcp/dhclient.eth0.leases -I -df /var/lib/dhcp/dhclient6.eth0.leases eth0
    1 /usr/sbin/rsyslogd
    1 /usr/sbin/cron
    1 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 101:106
[...]

Please don't get me wrong, there is nothing personal here, but please make sure you understand what you are posting before making it a tutorial.

#2 Re: Other Issues » Devuan + paralleized OpenRC + KDE » 2019-09-14 18:55:30

Terence wrote:
pidof /sbin/init && echo "openrc" || echo "other"

That shell command doesn't have much to do with openrc. You only check the PID of /sbin/init, which is almost always 1, even with the default Sys V or systemd or whatever, and then you print a random message, in this case "openrc". Could as well be anything else. Just run the same command as root on a Devuan, Debian, Ubuntu, CentOS or any other Linux that does not even has openrc installed, and check the results for yourself.
Guess what happens on a Ubuntu 18.04 with systemd:

# pidof /sbin/init && echo "openrc" || echo "other"
1
openrc

roll

You might want to try something else, like seeing where init is actually pointing:

# ls -alh /sbin/init 
lrwxrwxrwx 1 root root 20 sep  5 06:59 /sbin/init -> /lib/systemd/systemd

See? It points to systemd on Ubuntu here.

In case it doesn't, you might want to check the executable yourself. For example, on Devuan with Sys V and no OpenRC installed:

# strings /proc/1/exe | grep INIT_VERSION
INIT_VERSION=sysvinit-2.88

See? Here we have Sys V /sbin/init.

Also, if I remember correctly, OpenRC doesn't always replace init...?

#3 Re: Hardware & System Configuration » [CLOSED] secure erase failure - unlock ssd with hdparm not possible » 2019-09-14 18:29:58

Just for future reference, indeed it appears your SATA to USB adapter was the problem. Never ever use advanced SATA features over such an adapter:
https://sourceforge.net/p/hdparm/support-requests/7/

#4 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-12 16:40:14

Ozi wrote:

copy-root-overlay and postbuild-clean currectly don't exist, so added them should remove the errors.

copy-root-overlays and postbuild-clean are both defined in helpers... I'm looking at them right now. You should not have received those error messages if you followed all the instructions correctly.

P.S.: I already told you, I build images for raspi 4 with no errors or warning whatsoever.

#5 Re: Hardware & System Configuration » [CLOSED] secure erase failure - unlock ssd with hdparm not possible » 2019-09-11 05:27:40

nogeek wrote:

I have a Toshiba device here and figured out that "the" masterpassword (it is the only one I have found in several lists) is 32 spaces, but that did not work:

$ hdparm --user-master m --security-set-pass                                  /dev/sdb
missing PASSWD

I tried 34 spaces between "--security-set-pass" and "/dev/sdb", because you need a space after each option/parameter and 32 spaces (because the first logical did not work and I am frustrated...).

That's not what 32 spaces on a command line do... Just try:

echo                   x

and see what you get. The error message above is pretty clear: missing PASSWD
Try:

$ hdparm --user-master m --security-set-pass "                                " /dev/sdb

Observe the 32 spaces in quotes.

#6 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-08 09:36:15

Ozi wrote:

Would you consider pulling down the vc tools source and compiling, install the 64bit executables?

I don't have a 64-bit Raspberry at this point to test on... and also this:

Note that this repository does not contain the source for the edidparser and vcdbg binaries due to licensing restrictions.

Ozi wrote:

SHould I be running with using sudo?

Yes of course! See the docs.

Ozi wrote:
chroot: failed to run command '/debootstrap/debootstrap': Exec format error
 [E] error in: qemu_install_user
 [W] called in: raspi4 build script loaded
 [W] called in: running debootstrap stage 2
 [E] error reported, operation aborted.
 

Run as root/with sudo? modprobe binfmt_misc? Do you see other errors above what you posted?

P.S.: I also clear the dist/ and tmp/ folders before each build. Just in case, because I spotted something weird happening a few times.

#8 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-06 12:32:12

FYI I enabled ccache for compiling cache in my fork:
https://git.devuan.org/b3bgd/arm-sdk

Works like a charm, after the first build I get compiling times about 5x better. I needed this because I made round 50 builds from scratch in the last week or so.

P.S.: in that fork you will also find that I put vc tools for raspi 1 & 2 (because they are 32-bit, and there are no 64-bit executables and I don't know if they will work for 64-bit), and I fixed the raspi 2 image & modules.

#9 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-05 05:18:37

Ozi wrote:

Is raspberry-pi4.sh a file I need to make, or is it init.sh?
?

It's in /boards, e.g.:
https://git.devuan.org/b3bgd/arm-sdk/tree/master/boards

#10 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-04 04:18:09

Ozi wrote:

Where is the variable to set the compress option?

In your raspberry-pi4.sh, near the top, before function definitions, add the lines:

vars+=(nocompressimage)
nocompressimage="true"

#11 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-03 05:43:28

Ozi wrote:

Is there anything in the sdk config file that needs to be changed?

Well... a lot of things are missing: the /opt/vc tools (dtparam/dtoverlay, vcdbg, tvservice etc); installing libgl1-mesa-dri tries to install Radeon and geForce drivers; wpa_supplicant is missing config; groups mentioned above are not created; xrandr is missing; etc. So not sure what to say here, there are lots of things to fix with Devuan for arm. Btw, trying to set the variable to not compress images (forgot which it was) still creates the compressed images (but also leaves the original).

Lots of things to fix.

#12 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-09-01 06:35:03

Hi again. I'm gonna answer here directly, maybe others will find this useful too.

If you setup up an amd64 machine to build, everything will be OK, because the script will use cross-compiling to the correct arm architecture (armel/armhf/arm64) depending on your board.

Please look closely at the issues and merge requests on Git. For raspi 2 I found out the partitions were not aligned correctly and the kernel modules were not handled properly, resulting in an unusable image (the image posted on Devuan site right now for Raspi2 doesn't even boot). I fixed the problems, and made a merge request. For raspi 4 things seem in order, but there is a merge request for 4G RAM limit. You might want to look at that.

Also, something else to consider:
1. Even if not mentioned in the readme, you will also need the following packages on the build host installed:

quilt bison flex chrpath gawk texinfo libsdl1.2-dev whiptail diffstat cpio libssl-dev

2. On the arm image itself, after booting, you should create the groups for the bus interfaces, because they are not included:

groupadd --system spi
groupadd --system i2c
groupadd --system gpio

3. See net.ifnames in cmdline.txt and adjust as needed for predictable or classic net names - I myself find the old classic way more predictable on raspi, because it only has one interface of each type.

4. On the raspi 2 image at least, locales are kinda missing. Setting the keyboard doesn't work either.

#13 Other Issues » [armhf] raspi2: dpkg-reconfigure keyboard-configuration not workin » 2019-08-31 15:11:59

b3bgd
Replies: 1

Hi.
I built a working ASCII image for Raspberry 2 using arm-sdk.
Nevertheless, I'm unable to configure the keyboard no matter what:
dpkg-reconfigure keyboard-configuration does not work because keyboard-configuration is not installed (in amd64 image it is present).
Installing keyboard-configuration did not solve the problem unfortunately - it silently fails with no error whatsoever, also without displaying anything, and with return code 0. Installing the whole suite of packages it might depend on (console-setup console-setup-linux kbd keyboard-configuration xkb-data) also didn't fix the problem.

Any ideas please?

#14 Re: Hardware & System Configuration » arm-sdk + rapsberry pi 4 » 2019-08-31 14:50:44

Hi.
For Raspi2, I just use a virtual Devuan ASCII macine for building, am follow the instructions in the arm-sdk Readme (with some initial quirks, that is).
Where are you stuck?

Board footer

Forum Software