The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » [SOLVED] I installed gnome, now I can't use XFCE » 2022-03-11 09:10:41

If you have once installed Gnome, you will have it forever. Whatever you will do beside Gnome - Gnome is already there. Scary!
Remove it as long you will be ablte to do. :-)

Berni, Gnome-hater.

#2 Re: Off-topic » Loss of a friend » 2022-03-08 08:42:54

So sad to loose a good friend!
In January I lost Yellow, a Samojede mix from Romania. He was not my dog, but I visited Yello every day and we made long walks together. In the beginning Yellow was a problematic dog and his owner, a middleaged Lady, had diffculties to hande the dog.
After some years however Yellow was one of the best dogs in town. I miss Yellow and I understand zephyr.
Still sad, Berni

#3 Re: Hardware & System Configuration » [SOLVED] nfs trouble on Chimaera » 2022-02-20 07:50:10

Does it mean hat the rpc.mountd was not started due to the unknown option?

#4 Re: Off-topic » The seitan conundrum » 2022-02-17 15:14:45

Nice thread, and it reminds me to my macrobiotical start in the early 70s. Firstly I was a hardcore macrobiotic man, later I was more softly. However some food from this period accompanies me till today. It was one of the best choices in my life and the Oshawa cookbook has, beside others, still on its place on my shelf.

#6 Re: Installation » xorg start only as super user! why? » 2022-01-07 22:13:57

Head_on_a_Stick wrote:

OpenBSD can also run startx as the normal user. But xenodm(1) is recommended for that operating system.

No, the normal user without root privileges cannot start X via startx - not ex works. This has changed in 6.6 or 6.7 already. SO a dm is a MUST quasi.

#7 Re: Installation » xorg start only as super user! why? » 2022-01-07 14:22:12

You are right, off course! I had OpenBSD in my mind, where the setuid bit was removed from the X server some years ago. mad

#8 Re: Installation » xorg start only as super user! why? » 2022-01-07 08:34:59

startx need root permissions to start X. If you do not want to use ugly tricks, you must let do the display manager the job. Try it by starting, lets say slim or xdm, and the it must work.

#10 Off-topic » Colour of the future? » 2021-12-22 09:22:14

Replies: 9

OK, this is NOT a serious question - however: Is there already a color for the corporate identity of Daedalus selected by the veterans? What will come after Gray, Red and Blue?


#11 Re: Other Issues » pxe boot hangs in busybox » 2021-12-17 11:33:00

I tried and (off course) it works. When I build my own image for my purposes this solution is good enough for me. Thanks for your kind help

#12 Re: Other Issues » pxe boot hangs in busybox » 2021-12-14 19:38:51

Thanks a lot, Ralph, I will try this tonight.


#13 Re: Other Issues » pxe boot hangs in busybox » 2021-12-14 11:26:06

Thanks @FM81. The last line in the log is the very last cry from dnsmasq:When I exit the busybox I get a warning that the /root could not be mounted. The next exit causes a kernel dump and that killed dnsmasq.

All output was logged into /var/log/dnsmasq.log. The client screen shows that the kernel is loaded and then initram.img, which ended in the busybox because the /root could not be mounted.


#14 Other Issues » pxe boot hangs in busybox » 2021-12-12 16:30:59

Replies: 5

I tried to realize a diskless client (Intel NUC). The NUC shall pxe boot chimaera_4.0.0._amd64-desktop-live.iso or chimaera-4-0-0_amd64_minimal-live.iso.
As the dnsmaq- and tftp server I selected a raspberrypi 4 with 8 GB of RAM.

So I installed dnsmasq, pxelinux and syslinux-efi and followed these instructions: … oot-server. On the Pi also Devuan Chimaera is running.

Then the first boot of the NUC machine. I saw my menu with the 3 entries (desktop-live & minimal-live), I could select an entry and the the boot procedure startet. It looked like a normal Devuan start, but when the system detected the usb ports with keyboard and mouse, it hangs and I ended up in the initramfs busybox.

This happens with desktop-live as well as with minimal-live. The logfile on the Pi said:

Dec 12 13:44:34 dnsmasq[1826]: started, version 2.85 DNS disabled
Dec 12 13:44:34 dnsmasq[1826]: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify dumpfile
Dec 12 13:44:34 dnsmasq-dhcp[1826]: DHCP, proxy on subnet
Dec 12 13:44:34 dnsmasq-tftp[1826]: TFTP root is /home/data/netboot  
Dec 12 13:46:25 dnsmasq-dhcp[1826]: PXE(eth0) 94:c6:91:11:06:22 proxy
Dec 12 13:46:30 dnsmasq-dhcp[1826]: PXE(eth0) 94:c6:91:11:06:22 bios/pxelinux.0
Dec 12 13:46:31 dnsmasq-tftp[1826]: error 0 TFTP Aborted received from
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/pxelinux.0 to
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/pxelinux.0 to
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/ldlinux.c32 to
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/7ea11317-78b9-28a5-9593-94c691110622 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/01-94-c6-91-11-06-22 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0A80047 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0A8004 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0A800 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0A80 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0A8 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0A not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C0 not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: file /home/data/netboot/bios/pxelinux.cfg/C not found
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/pxelinux.cfg/default to
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/vesamenu.c32 to
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/libcom32.c32 to
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/libutil.c32 to
Dec 12 13:46:31 dnsmasq-tftp[1826]: sent /home/data/netboot/bios/pxelinux.cfg/default to
Dec 12 13:46:52 dnsmasq-tftp[1826]: sent /home/data/netboot/boot/amd64/devuan/minimal-live/live/vmlinuz to
Dec 12 13:48:46 dnsmasq-tftp[1826]: sent /home/data/netboot/boot/amd64/devuan/minimal-live/live/initrd.img to
Dec 12 14:03:23 dnsmasq[1826]: exiting on receipt of SIGTERM

Any idea what's going wrong here? Did I a big mistake or are the initramfs images not suitable for pxe boot?


#16 Re: Installation » [SOLVED] migrate from Beowulf to Chimaera: dual-boot? » 2021-11-10 09:40:12

As you I use external SSDs for different systems. When I upgraded my (external) Beowulf installations, I ended up in dual-boot grub entries.
But I must say that I did not care about that during the upgrade process.

#17 Re: Installation » No more wlan after upgrade » 2021-10-24 07:21:00

Thanks @Head_on_a_Stick. The problem was that I could not find any error message. Wpa_supplicant was running, as well as dhclient, but they never were able to connect the machine.
I did what you said and disabled avahi, network-manager and modem-manager, step by step and one after the other. After that and without any further other changing the wpa_supplicant connects the machine as all the years before.

Did the upgrade process started all these daemons?

#18 Installation » No more wlan after upgrade » 2021-10-23 13:26:20

Replies: 3

During the last days I upgraded 7 machines from beowulf or chimaera-testing to the stable chimaera version - without any problem - perfect.
And today I did the upgrade on the last machine - an old Asus eee701, running chimaere-beta-386.
Upgrade went fine, but after the following reboot I had no connection to the internet. Ifconfig showed why: No IP address for wlan0.

The network handling for wlan0 was made by the wpa_supplicant, also perfect and stable. Now I saw that the wpa_supplicant was running on wlan0, but the dhclient was unable to give an ip.
Then I saw that further daemons were :
- avahi-daemon, which created an own interface wlan0:avahi with a fall-back ip adress from a wrong range.

I never ever had configured this daemons to run and to handle my wlan interface - but they did. However none of the programs were able to fire up wlan0 and connect to my dhcp server. OK, to many cooks probably.

All this only happened on the old eee701 Asus machine, other computer with wlan interface are still running fine with wpa_supplicant.

What is the best way to connect to the internet? Is it time to say good-bye to the wpa_supplicant? Or shall I deactivate network-manager and modem-manager and let still do wpa_supplicant the job?
Hints are highly appreciated.


#19 Re: Desktop and Multimedia » What games do you play on Devuan?? » 2021-10-18 07:53:28

I play AisleRiot too, beside gnome-mahjongg, Solitaire Klondike (xpat2) and cuyo. That's it.

#20 Re: Installation » minimal-live issue » 2021-09-13 14:34:05

Thanks @fsmithred, so I will do.

#21 Installation » minimal-live issue » 2021-09-12 17:03:50

Replies: 2

Yesterday I installed the latest minimal-live image onto an older Gigabyte Brix machine with 8GB of RAM and Celeron N2807. The Brix is from 2015 and is able to boot BIOS and UEFI. However the UEFI boot will not always work and therefore I made a BIOS installation.

This was not my first minimal-live installation and it is the best option for my personal Devuan.
OK, I started installation and everything seems to be fine - no errors, no problems.

But when I booted into the new system, grub starts, loads the kernel, and the the system hung! The last message was:

Kernel Panic: VFS: unable to mount root-fs on unknown block (0,0)

I tried multi- and single user mode, I repeated the grub-install, but nothing helped.

Later on, when I had no more ideas, I downloaded the refracta_11_nox image, which has the same kernel version. Installation was OK - and the system started perfectly. No kernel panic, nothing. Everything fine.

Any idea what went wrong with my minimal-live installation?


#23 Re: Installation » Could not install under UEFI with chimera netinstall » 2021-09-11 09:15:48

After several installations of Devuan in UEFI mode with the refractainstaller my experience is as follows:
- better make the disk partioning before running the installer
- never forget the EFI partition
- also never forget to write a fat filesystem onto the EFI partition
- run the installer
- repeat the install-grub procedure manually after installation
- boot the machine in EFI mode

Running only the installer I often had the situation, that the system did not boot: No boot device found, Grub Rescue or a fragmented Grub screen - all this has happened in the past.

Honestly the Grub installation of the refractainstaller seems to be not perfect.


PS: Using the lates minimal-live I ran into a problem when choosing GParted during installation. GParted was not part of minimal-live, and the refractainstaller ended in an endless loop between selecting the partition tool and going ahed without partitioning. Choosing another tool (gdisk, cfdisk) always brought the indication "GParted is not installed".
That happened yesterday when setting up a Daedalus system, based on minimal live.
Finally some manual work as described afore was successful.

#24 Re: Off-topic » [SOLVED] Devuan GNU/Linux 5 (daedalus) Released as Next Testing! » 2021-09-09 07:40:50

Don't be suprised, @zapper. smile

Off course my Beowulf- and Chimaera machines will be untouched, but an Alpha-installation with Daedalus on an external SSD is quite nice. A good toy for gray and boring autumn evenings, which will come soon.

Berni (just preparing a SSD)

Board footer

Forum Software