You are not logged in.
@mamforestcritter,
I'm very happy for you.
I have studied your computer's manual before already.
It's okay to use "UEFI" mode as long as you do not activate the secure boot option to avoid trouble.
Happy Devuan!
Oh ever ranting steve_v,
does it ever come to your mind that this is a forum to help people seeking advice?
You help nobody with your outbursts but poison a nice and good community and forum instead.
And what you shout about is not even always correct.
So if you can help, then help.
And just this:
MBR and EFI mode are fine.
UEFI mode is the devil
MBR disk scheme goes with BIOS-mode
GPT goes with EFI mode
for root (/), /home and /srv, ext4 works really well
Swap partition should be marked as swap by the partiioner.
Avoid "secure-boot", TPM and UEFI mode (these are Windows traps)
And last but not least: if your computer is equipped with ECC RAM modules, enable this feature in the BIOS setup.
Linus Torvalds tells you that. Search the Internet, there are YouTubes on that topic.
Good luck.
Considering all that information.....
why not try to do a proper system setup (BIOS/Firmware) and reset ALL settings to default values?
If you truly know about your specifics, you can make some changes after a restart an re-entering the system setup.
Then, start your system with the external USB-stick containing the Devuan installer image.
Go through all steps, and when it comes to the partition setup: let the setup-program erase the disk completely and install the system. I've never seen a case where that doesn't work.
Should you wish to modify the partition setup, you can restart the installer (reboot) and make your modification of the partition-scheme then.
Usually it's okay to have one / (root) partition of at least 50GB, an adequate swap partition (1-2 times the RAM size), and the rest may be /home or a /home and some other partition like /srv.
The installer knows how to figure out the disk-layout, either MBR or GPT. (BIOS-mode or EFI-mode)
Never ever use things in BIOS setup like "secure boot" or "TPM", it brings nothing but grief.
The reason I recommend all this: who knows what that former Windows setup has done to your beautiful computer.
To all: Happy New Year!
The Devuaners have done a marvelous job, a thriving, good community.
Always think positively and enjoy the message exchanges. A lot of good things come of them.... answers, responses, solutions.
Thank you for that wonderful distribution which is Devuan.
@all
Thank you for your ideas!
Your answers are helpful and I test FF again with your recommendations, in parallel with testing waterfox.
Have a nice weekend!
I just fell on a interesting topic:
Is Mozilla doing enough to avoid AI if not desired?
See the following article:
https://www.theregister.com/2025/12/18/ … _waterfox/
I decided to test it for a while. What's your take?
Have a look in your repos for the packages:
hplip
hplip-gui
(incl. all dependencies)
If there, install them and start hplip-gui.
Configuring your printer should be child's play then.
That works well with devuan, debian, linuxmint, ubuntu etc.
That's an old problem. It's not the Devuan repos, however.
The problems stem from more and more lousy ISP infrastructure set-ups. Kind of round-robin DNS name resolution doesn't work on them.
The solution is simple:
Exactly,
the same old problem with the resolution of these "round-robin" DNS names resurfaces again and again.
I had to switch from my old, trusty own DNS named server (BIND) to the typical service-provider setup and that made me unhappy again.
The only solution was and is to replace "deb.devuan.org" with somewhat "XY.deb.devuan.org" in the /etc/apt/sources.list file, replacing the XY with the nearest mirror-country-code.
I don't know what HPFM is behind all these silly ISPs.
I'm not good enough to know how the Devuan community could set up a /etc/apt/sources.list file that would remedy the situation for once and ever.
Refer to:
https://dev1galaxy.org/viewtopic.php?pid=53413#p53413
Sure, rolfie is right.
The computer's HW clock should be set to UTC. And the timezone (TZ) should be selected as to the standards.
When DST patterns change for some time-zones, the corresponding patches will be distributed. Another reason to update regularly.
And to set ntp right, as you seem to refer to:
it's ntpsec to be installed.
And to check if it works:
ntpq -pAnd in devuan 7 ??? These programs are present in Devuan 6 (Excalibur)
ntpdate was for older ditributions, like RedHat etc.
Roberto,
yes, there is a solution to that problem:
Its the NetworkManager version used in Excalibur.
Look at this thread:
https://dev1galaxy.org/viewtopic.php?pid=59374#p59374
The workaround is (from steve_v):
@Andre4freedom: You might try grabbing that missing file (/etc/NetworkManager/dispatcher.d/01-ifupdown) from the Daedalus network-manager package. Like I said I don't have a system to test it on, but the manual suggests networkmanager should still call it if it exists.
I hope that may be a temporary solution for you too.
I guess there will be a newer or patched network-manager package in some time, possibly a new point-release or a patch.
Good luck.
Your solution sounds very reasonable, fair and sound.
So I will switch to sysvinit on the laptop, and just remove or disable anacron on servers and workstations.
I consider the case as closed, though.
Thank you for your input, rolfie.
I think I marked the topic as "solved" to early.
With the release of Devuan 6 Excalibur, anacron in combination with OpenRC still causes delays at shutdown - sometimes. Not every-time but still sometimes.
The problem can be worked around by disabling anacron (rc-update delete anacron) or by switching to sysvinit.
I guess you have tried to install with a netinstall-iso.
Try your luck with a desktop-iso
i.e. https://files.devuan.org/devuan_excalib … esktop.iso
if you really have to install in a public place or library.
Desktop-isos are fully contained isos for standard hardware.
steve_v:
I am blaming NO one!!
I just want people to avoid the trap of such a case!
I'm no politician and no flamer, so please stay on the subject.
Anyway, you gave me the good hint earlier, thanks for that.
My last thing I could do to bridge the time until a patched networkmanager goes into the update repos:
Suggestion of a modification of the Release-notes.txt the following way:
$ diff Release_notes.txt Release_notes-ak20251109.txt
14a15
> + NetworkManager
189a191,201
>
> ### NetworkManager
>
> The new version of networkmanager (debian) doesn't notify the system of
> completed network setup at boot time. (cause: Debian's systemd)
> As a result network-bound resources are no longer mounted as instructed by
> /etc/fstab at boot time.
> To make it happen again, simply copy a file into the networkmanager's directory.
> The version tested and working is the one from Devuan Daedalus.
> sudo cp 01-ifupdown /etc/NetworkManager/dispatcher.d/
> After a reboot everything should be up again.
$
I have no idea where such a suggestion is to be posted. I think Devuan's administrators could come to the rescue.
Thank you.
Andre
To steve_v, ralph.ronnquist, fsmithred:
There is news about our config NetworkManager-OpenRC-Cinnamon: the differences between Devuan Excalibur and Artix.
See the differences in the following reports I have just written:
Excalibur:
https://pastebin.com/4CcBTkEV
Artix:
https://pastebin.com/3KuU9mUy
In the Artix test-install (~6 month old), there is a additional file in /etc/NetworkManager/dispatcher.d/
-rwxr-xr-x 1 root root 1213 May 14 2021 10-openrc-status
And the version of networkmanager is networkmanager 1.54.1-1
The result is that NFS mounts in /etc/fstab are respected at boot time.
I have the additional file here should you be interested.
I will send the same information to the devuan networkmanager maintainer.
Have a lovely Sunday. Greetings, André.
So, to complete the information, here it is:
Bugreport
https://bugs.devuan.org/cgi/bugreport.cgi?bug=925
So then until an Excalibur patch comes out with future updates, we will have to do as steve_v suggested. I'm happy with that.
I think that what was asked for.
Greetings,
andre4freedom
Fsmithred,
I have just done that. Thank you.
Bugreport sent.
Shall I mark the case as solved?
Thank you for your suggestions and help, to all!
And just a little side-note:
Due to the situation I installed temporarily Linux Mint 22.2 to be able to work. This morning was the first time that my machine hung, just freezed, X11, text consoles, keyboard, mouse - all dead. That machine has never ever done that with Devuan running all these years. How happy I am to re-install Devuan - with your fix. You see, Devuan is worth making the effort and taking a few extra steps to resolve issues.
Happy Devuan
@steve_v
You are true hero, you have nailed it.
I did as you suggested and placed that script /etc/NetworkManager/dispatcher.d/01-ifupdown to the right place and rebooted. And sure enough: BINGO.
Thank you for that precious hint.
@ralph.ronnquist
I did the tests on a spare machine, doing a fresh-install with the excalibur-netinstall-iso and running the the devuan installer's first option: install
Test 1: Excalibur - Cinnamon - OpenRC
Test 2: Excalibur - Cinnamon - sysvinit
In both cases I just edited the hosts file, the fstab, created the mountpoints and rebooted. In both cases NFS was not mounted.
Copying the famous file /etc/NetworkManager/dispatcher.d/01-ifupdown from my local server (daedalus) to the test machine did the trick..
BTW: Editing the /etc/rc.local file didn't change a thing.
Would you like me to write a simple procedure (a text file) how to fix that problem? Then, where could I send it for inclusion to the release readme file?
Unfortunately I'm not able to fix the networkmanager package.
Once again, to all of you: Thank you for your help.
Sincerely, Andre (andre4freedom)
Thank you, steve_v and ralph.ronnquist!
That shows that something is wrong with the default setup.
I will try to find a solution (not sure if I'm up to it).
When and if solved, I will let you know, and post the solution.
Have a good day, andre4freedom
@steve_v : Thank you.
I have tried my luck to upload some files. You can find them here (hopefully):
(dmesg):
https://pastebin.com/V3iQa77z
(fstab):
https://pastebin.com/HiGjWMAj
(hosts):
https://pastebin.com/hX8evCQY
(syslog):
https://pastebin.com/UvuWqyVw
(boot-log):
https://pastebin.com/s6tumGik
Thank you for volunteering into that mystery.
Sincerely, Andre4Freedom
@ralph.ronnquist
I could install excalibur on a spare machine.
Excalibur-openrc-cinnamon-nfs-common
I have extracted 3 log files: dmesg, syslog, boot
Where can I post or send this files?
I found no hints in them at all.
NB, the same problem again, no NFS resource is mounted at boot. But,
sudo mount -a mounts the all
Thanks for your efforts.