The officially official Devuan Forum!

You are not logged in.

#1 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-12-04 15:17:25

nunya wrote:

... the belena-Etcher to install devuan_ascii_2.0.0_arm64_raspi3.img.xz ...

Think you mean 'balena-Etcher"?
But from my point of view I would not trust this piece of software anymore: https://github.com/balena-io/etcher/issues/2977
The combination of "secretly spies" and pure root-access to raw-devices sounds not good in my ears, no matter under wich operating system?!
Not sure, what they will do in future versions, if nobody would care about ...

Best regards, FM_81

#2 Re: Installation » Problem with *.iso file » 2019-11-30 15:04:04

Typically an ISO-image (with ISOLINUX.BIN) is created by the following:

mkisofs -o NAME_OF_ISOIMAGE -b isolinux/isolinux.bin -no-emul-boot -boot-load-size 4 -boot-info-table ISO_ROOT_OF_FILES

The parameter "-boot-info-table" is essential, to get it working. But this parameter does the following: it modifies isolinux.bin itself during the build of the isofile. A previously created checksum will never match after that! That's why this special file should be always excluded from such checksum-tests.

Or in other words: It is not a bug, it is a feature ...

Best Regards, FM_81

#3 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-11-25 19:26:25

Based on the raspi3-image (same root-password 'toor'), but for model 4:
https://www.file-upload.net/download-13 … mg.gz.html
I replaced/added files from the following debs:

firmware-brcm80211_20190114-1+rpt4_all.deb
libraspberrypi0_1.20190925-2_armhf.deb
libraspberrypi-bin_1.20190925-2_armhf.deb
libraspberrypi-dev_1.20190925-2_armhf.deb
raspberrypi-bootloader_1.20190925-2_armhf.deb
raspberrypi-kernel_1.20190925-2_armhf.deb

from the raspbian downlod-site.

Tested  with SSH and composite-video out, not with HDMI yet, but it should probably work too?
I'm sure, there is a lot of work undone, but as basic image it works and it survived an

apt-get update
apt-get upgrade

but updates are not included in the image ...
MD5-checksum should be

4b38c49972103a4c452212726de01159 *./devuan_ascii_2.0.0_arm64_raspi4.img.gz

Best Regards, FM_81

#4 Re: ARM Builds » RPi3A+/3B/3B+/(4B) » 2019-11-21 18:50:48

You can take the image for the RPi3, replace, firmware, kernel, bootloader as described here https://dev1galaxy.org/viewtopic.php?id=2935
The only difference in my way was, not to install all on a raspberry 2 or 3 as described; instead I've mounted the original image-file an replaced firmware and so on "by hand"

At least it boots, but I can only test it via ssh, because I own no micro-hdmi-cable at the moment ...

Best regards, FM_81

#5 Re: Installation » [SOLVED] Raspberry Pi Zero Wifi using ascii (2.0) » 2018-07-23 09:27:25

Hello all together!

I've downloaded the files, you've described (from the same link) today. The checksum of the bin-file still matches, but this one from the txt-file doesn't? (This makes me a little bit wondering, as they are dated from February 15th?) And of course, if they where copied to the described place, my pi-zero has no WLAN-interface? Some questions remain:

- Can someone provide a working version of the txt-file?
- Is it possible, that something else was going wrong?

The image I've used was devuan_ascii_2.0.0_armel_raspi1.img.xz from the download-zone-site.

Greetings, FM_81

#6 Re: Installation » [bluetooth]# scan on No default controller available, not hci0, why ?? » 2018-07-19 16:18:04

Good evening!

It looks a little bit like https://dev1galaxy.org/viewtopic.php?id=1597 - as there where never an answer, so it seems there is no quick solution?
May be, there is something missing in the kernel-configuration, may be too, you have to build your own.

Sorry for providing not real help, bluetooth wasn't my first, second or third priority ...

Have a nice day, FM_81

#7 Re: Installation » [SOLVED] Devuan 2.0.0 on Raspberry Pi 3 plus with GUI? » 2018-07-15 21:27:25

Hello!

Few days has gone ...

I've repeated all the steps from here https://devuan.org/os/documentation/dev … ce-install with a fresh image and installed xserver-xorg and xinit additional. It worked perfect on the first attempt without any powercycle; I can not declare, what was going wrong in the earlier time ...

Best regards, FM_81

#8 Re: Installation » Deterministic names for network interfaces? » 2018-07-09 19:15:31

@fsmithred: If I try you last variant it starts without any error. But my interfaces are still named 'enp3s0' and 'enp2s0' ??? (No, there is nothing UPPERCASED on any place.)
May be, we should stop searching here, there seems no easy solution? Effort and benefits didn't stand in a acceptable relation for this small problem!

@bbatten: I didn't understand you answer, may be because english isn't my native language; but in none of the files is the keyword GOTO used?

Best Regards, FM_81

#9 Re: Installation » Deterministic names for network interfaces? » 2018-07-09 14:56:32

@fsmithred: I've tried your suggesstion, of course I also made it executable on the new place. It gives during init two messages:

ifup: error trying to execute mapping script /etc/network/interfaces.d/get-mac-address.sh on enp3s0
ifup: error trying to execute mapping script /etc/network/interfaces.d/get-mac-address.sh on enp2s0

and ends with two unconfigured interfaes, still with their old names (enp*). If I execute the script manually (with one or two or three parameters) it simply hangs, there is no returning to the prompt?

@UnclePa: I didn't know about this fact. But all my experiments was done with lowercase (without knowing it before)!

@ralph.ronnquist: I had such an rule on Debian 6 and Debian 7 and Devuan 1.0.0. It was always seen and accepted. So I'm lost at this point and didn't understand, why well working things suddenly didn't work anymore?

Greetings, FM_81

#10 Re: Installation » Deterministic names for network interfaces? » 2018-07-09 08:43:39

Good morning!

As UDEV-rule I've tried this:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", KERNEL=="eth*", NAME=="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:55:44:33:22:11", KERNEL=="eth*", NAME=="eth1"

and this:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", KERNEL=="enp*", NAME=="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:55:44:33:22:11", KERNEL=="enp*", NAME=="eth1"

and this:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", KERNELS=="pci000:00", NAME=="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:55:44:33:22:11", KERNELS=="pci000:00", NAME=="eth1"

and also this:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", KERNELS=="0000:03:00.0", NAME=="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:55:44:33:22:11", KERNELS=="0000:02:00.0", NAME=="eth1"

But none of them had any effect?

The mapping approach sounds good, but I have no expierience of this?
I've found many arcticles in the web, but all of them describe much more complex scenarios than a simple renaming!?
My INTERFACES-file looks as follow:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface, called "eth0" in the good old days!
auto enp3s0
iface enp3s0 inet dhcp

# The secondary network interface, called "eth1" in the good old days!
allow-hotplug enp2s0
iface enp2s0 inet static
	address 192.168.1.17
	netmask 255.255.255.0
	network 192.168.1.0
	broadcast 192.168.1.255

Which changes has to be done, to get 'enp3s0' as 'eth0' and 'enp2s0' as 'eth1'?

Thank you and best regards, FM_81

#11 Re: Installation » [SOLVED] Devuan 2.0.0 on Raspberry Pi 3 plus with GUI? » 2018-07-05 10:08:28

Hello at all!

Sorry for creating confusion; I've powered up yet the same Raspberry 3+ as yesterday, and now the graphical interface starts?
I didn't know why?
The only thing I've never done yesterday was: disconnect power (only  a lot of reboots was performed)
Now is all, as one would expect, but I can not declare why, may be some thing in the detection of the HDMI or what ever?
Keyboard, mouse and screen are all the same ...

I plan to repeat the steps from yesterday, when there is a little bit more time, to make more clear what happened...

Thanks again & sorry, FM_81

#12 Re: Installation » Deterministic names for network interfaces? » 2018-07-05 04:00:22

Good morning!

I put it in

/etc/udev/rules.d/

Is this still guilty or do I have something missed in between?

Best Regards, FM_81

#13 Installation » Deterministic names for network interfaces? » 2018-07-04 09:38:32

FM81
Replies: 13

Hello!

System is Devuan 2.0.0, standard installation with Network-Installer. I have an AMD64-machine, two network interfaces:
A gigabit onboard, lets call it A with DHCP and a 100M on a PCI-slot lets call it B with a static given address in a separate range of course.
If I add net.ifnames=1 to the grub-commandline nearly everything is fine. A is always 'enp3s0' and B is always 'enp2s0'.

How ever, I would prefer to have old style 'eth0' and 'eth1'; I get this if I remove the additional boot-parameter of course!
But in this case it isn't defined which is which, sometimes A = 'eth0' and B = 'eth1' an on next boot it may reversed as B = 'eth0' and A = 'eth1' (or on second or third restart only, you cannot say it, before you test it.).
Now one may think: 'Create an UDEV-rule and everything is nice.' I've created one, but it seems to be ignored completly:

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:55:44:33:22:11", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:11:22:33:44:55", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

(I've also tried several variants of this.)
Is there a chance, to get the normal network-interface-names back in a stable manner?

Thank you and have a nice day ...
FM_81

#14 Installation » [SOLVED] Devuan 2.0.0 on Raspberry Pi 3 plus with GUI? » 2018-07-04 09:08:37

FM81
Replies: 5

Hi at all!

I've tried to add a XFCE-environment on a Pi 3+.
Writing the basic system to the SD-card was no problem, but no I'm stuck with the GUI-installation.
I've followed all the steps from here: https://devuan.org/os/documentation/dev … ce-install
Everything was installed without any error-message.
Additionally installed was xserver-xorg, but this had no positive effect, it didn't work with and also without before ...
But after a reboot no GUI ist starting automatically.
If I try to start it manual after console-login with 'startxfce4' it gives me the message: exec: xinit: not found
It doesn't matter, if I try to do this as root or as non-root-user.
I've also tried to set 'initdefault' to 5 instead of 2 in /etc/inittab also no effect ...

Can anyone explain please, what is going wrong here?
Thank you very much, FM_81

#15 Hardware & System Configuration » Raspberry 3 and internal bluetoothdevice - any chance? » 2017-09-16 14:27:12

FM81
Replies: 0

Hi at all!

First: There is no general bluetooth-problem; if I use an external USB-dongle everything is fine. It is correct shown in bluetoothctl

But as I wan't a low-power-solution, I'd like to use the the INTERNAL bluetooth from my raspberry 3. But it isn't recognized?
I've tested with devuan_jessie_1.0.0_arm64_raspi3.img.xz
But also with devuan_jessie_1.0.0_armhf_raspi2.img.xz
Both see the external bt-device, if there is any, but never the build in one? Is the any "magic stuff" that has to be done?

Thank you very much, best regards, FM_81

Board footer

Forum Software