Posts by FM81

FM81 · Installation

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

FM81 · Installation

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

FM81 · Installation

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

FM81 · Installation

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

FM81 · Installation

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

FM81 · Hardware & System Configuration

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

The officially official Devuan Forum!

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

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

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

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

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

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

Board footer