The officially official Devuan Forum!

You are not logged in.

#1 Re: Installation » First experiences and contact with Daedalus » 2023-12-08 23:47:41

aluma wrote:

Until now, TPM was turned off by default.
Apparently the developers decided to fix this.

On my laptop I enabled TPM in the BIOS, the messages disappeared, nothing bad happened yet. smile

Okay. :-)

#2 Re: Installation » First experiences and contact with Daedalus » 2023-12-08 00:03:52

aluma wrote:

We are forced to enable Intel TPM.

But why is that?

aluma wrote:

If you don’t want to enable it in the BIOS, you can simply turn off messages during boot.
In

/etc/default/grub

change

quiet splash

to

quiet loglevel=0 splash

and run

update-grub

https://linuxconfig.org/introduction-to … log-levels

Okay, thanks for the advice to simply hide the notifications.
But I'll rather leave the notifications to stay informed ;-)

#3 Re: Installation » First experiences and contact with Daedalus » 2023-12-07 23:47:29

GlennW wrote:

I think that ima: error, has something to do with your systems sensors (TPM chip) for Trusted Platform Modules (etc)

that could be due to bios version, firmware updates (search that topic here at Dev1 for apt source list, it changed with Devuan Daedalus)

You may be able to switch it off in bios, but maybe required for M$Win OS's validity!

Maybe my PC doesn't have any TPM chips, I don't know. I looked in the bios and didn't find anything about TPM there.

Apparently TPM is only responsible for signing or something. So it's not really that important for a working old system.

When upgrading from Chimaera to Daedalus, I adapted my sources.list accordingly as prescribed by entering "contrib non-free non-free-firmware" after each line.

#4 Re: Installation » First experiences and contact with Daedalus » 2023-12-03 23:10:03

To the graphics driver:

I initially opted for the free graphics driver. However, I have since realized that the font is not displayed so well on some websites. So I decided to install the Nvidia driver. "nvidia-detect" showed that I should install the driver: "nvidia-tesla-470-driver". The installation was actually problem-free, but in the end there was an error because "nvidia-persistenced" could not be installed. Even after restarting the computer, this remained unsuccessful. So I decided to uninstall this service from nvidia. This was crowned with success, because the "nvidia-persistenced - Service" could be deleted without any problems. Now Nvidia works without any problems.

Another problem that did not exist under Chimaera:

When starting the computer, the following is now written in several lines:

ima: error communicating to tpm chip
ima: error communicating to tpm chip
ima: error communicating to tpm chip
ima: error communicating to tpm chip
ima: error communicating to tpm chip

What is this error and how can I fix it? I did not have such an error under Chimaera.

#5 Re: Installation » First experiences and contact with Daedalus » 2023-11-29 21:56:59

golinux wrote:

That is because I reused the "Deep Sea" icon set from Chimaera with the "Sapphire" theme. wink

Oh, I see. ;-)

golinux wrote:

All the previous customized Devuan themes including icons will still be available.

That's good news. :-)

Camtaf wrote:

Grub, by default, no longer looks for other operating systems....

I know that.
But what about the new Grub, which is in a new directory and has a new name. Does it recognize other operating systems by default?

#6 Re: Installation » First experiences and contact with Daedalus » 2023-11-28 18:20:31

golinux wrote:

Yes, there is a Daedalus "Sapphire" theme and it is in the repos. It should be the default with an Xfce install.

I have now looked at lxappearance and obconf and indeed there is a theme there, that is called Clearlooks-Phenix-Sapphire. But the theme looks slightly different from the conventional Clearlooks theme. But under icons there is no Sapphire theme.

golinux wrote:

That being said . . . beginning with Excalibur there will no longer be custom theming unless someone steps up to do it. The previous themes will remain in the repos/git until they no longer function properly with gtk3 "advances".

And if there are no more user-defined themes in the future, then all we have left is Clearlooks ;-)

#7 Installation » First experiences and contact with Daedalus » 2023-11-28 13:11:02

Dev1User
Replies: 12

So, I have already updated two computers from "chimaera" to "daedalus". There were actually no problems. Only I had problems with the Nvidia driver. In the end I decided to use the free driver after the installation, because sooner or later it would happen anyway. So far everything is running smoothly.

But there were some things that seemed strange to me and others:

During the update, a reference to "eudev" appeared. The names currently used are no longer used. Instead of "enp0s3" it will become "eth0" again. I had always had the old names and they are much easier to remember and read.

Shortly before finishing the installation, another message about "grub" appeared. The old path to grub is: /etc/default/grub. Now, however, the file is to be given a completely new directory and the name is also quite strange. New directory and name: /tmp/grub.eT2LnZEMv6. Who always comes up with such strange changes and names? The old names are much more logical. In any case, I left the old file and did not install the new one from the package maintainer.

I bet that in the newer "Excalibur" version of Devuan, this will go back to the old name, like the "eudev" thing.

Comparison between Chimaera and Daedalus:

If the Lan cable is not plugged into the PC, Chimaera starts just as quickly as if it were connected with a Lan cable. Daedalus, on the other hand, starts up extremely slowly without a LAN cable. It takes a few minutes for the system to boot up. It was similar with Beowulf.

All the previous versions always had newer themes and icons after the update. Daedalus has nothing of the sort. Somehow Daedalus doesn't really seem to be finished.

Also, the other operating systems were not recognized after installation. This was also the case with Arch Linux. But this could be solved quickly.

#8 Re: Installation » [SOLVED] Where did obmenu go? » 2022-05-30 16:59:37

I have now taken a closer look at jgmenu. It seems to work fine. I installed jgmenu from Daedalus packages on Chimaera. After a few tries, I managed to get it to look good by my standards. Actually I wanted to make it even better, but somehow it didn't quite work out yet. In that area obmenu was already much easier.
I have a submenu, but how can I actually make another submenu from the submenu?

I used now the old XML obmenu file parallel with jgmenu. Jgmenu is anchored in the Tint2 bar. What else I noticed is that jgmenu can also read the XML file without any problem and can also display it just like obmenu. I like that jgmenu has a search function integrated. That is already very practical. I have set it so that jgmenu uses the same optics settings of obconf and tint2.

MiyoLinux wrote:

...and I shouldn't have said anything. I just tried it on chimaera, and it didn't work due to a missing dependency --> python-glade2.

I use obmenu-generator and/or jgmenu on Openbox. Sorry for the interruption. I'll bow out of the discussion now...

Ah good to know that it no longer works.

#9 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-30 16:10:23

So I have now completely solved the UFW problem. After several different attempts in the virtual machine, I noticed the problem. Actually, the problem cause was constantly seen. First a pure Beowulf installation and then an upgrade to Chimaera or even a pure Chimaera installation, brought success. The culprit was nftables. A new, clean Chimaera installation does not contain nftables. Only when I completely removed nftables on my two laptops, the error messages disappeared immediately. UFW is now running fine, with no problems. There are no problems when booting.

I have never heard about Firehol. I will have a look at the links. Thanks pcalvert.

#10 Re: Installation » [SOLVED] Where did obmenu go? » 2022-05-25 15:28:59

I also miss obmenu. Unfortunately, there isn't really an alternative in Devuan's packages. In the virtual machine I looked at jgmenu under Artix. At first glance, quite okay, but it is not as simple as obmenu. I will continue to use my XML file and modify it as needed and wait until a decent replacement comes along.

#11 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-25 15:13:32

So actually I just wanted to get UFW running, and not mess around with nfttables. I have neither the desire nor the time to deal with it in detail. Nevertheless, thank you Marjorie for this tip. I'll keep it in mind and when the time is right, I'll take a closer look. May be that nfs settings don't seem so hard for others, but for newbies it's just different.

I made two attempts yesterday in a virtual machine. On the first attempt I installed Ascii. Then upgraded Ascii to Beowulf and then to Chimaera. Then activated UFW and when booting the system there were no errors, but then when I looked in the terminal to see if it remained activated, it finally did not. The terminal said inactive.

On the second try I reinstalled Chimaera completely. Activated UFW and restarted the virtual machine. When booting, there were no problems and when I looked in the terminal, it actually said active.

So probably I have to reinstall Devuan Chimaera for this to work. But that can not be that I now have to set up everything completely new after every new version in case there are problems. This can't be true, it takes a lot of time and is very stressful and annoying.

#12 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-24 13:20:16

Dev1User wrote:

On my other laptop, where UFW is constantly disabled at startup, I removed Iptables completely with its dependencies. This laptop now has no internet connection. With the removal of Iptables was also removed Nftables, Connman internet service, UFW .... . I can't connect to the internet with it now. It looks like I have to reinstall Devuan completely. Or is there another step to establish an internet connection?

I have fixed the internet problem. I then started a trial. I installed Iptables, UFW, again. But after booting UFW was not activated. Then again removed Iptables, Nftables, UFW. This time installed only Nftables. After that UFW. UFW installed Iptables as a required package. After that UFW activated and after booting the laptop UFW was deactivated again. Through the links of Head_on_a_Stick I came to the Firwall Firewalld and its graphical interface Firewall-config. I could not start this firewall, it was always disabled. This firewall seems to be really only for SystemD. Could it perhaps be that Chimaera is no longer compatible with older hardware? My second laptop is a Dell. Although Beowulf was still running fine. Chimaera runs, but UFW seems to have problems with it.

On my first laptop, a Lenovo, UFW also has problems. It's strange that an upgrade from Beowulf to Chimaera suddenly causes problems on both devices.

#13 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-23 19:55:06

Head_on_a_Stick wrote:

I don't use {G,}UFW but that looks like an invalid configuration file, probably from the older version. Move the file and create a new configuration from scratch.

Unfortunately, I don't know what file exactly to move now and how to create something new.

#14 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-23 19:13:46

My output in /var/log/boot looks like this:

Mon May  9 16:57:59 2022: [....] Starting Setting kernel variables: sysctl??7[ ok 8??.
Mon May  9 16:57:59 2022: [....] Setting up resolvconf.../etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /etc/resolvconf/run/resolv.conf
Mon May  9 16:57:59 2022: ??7[ ok 8??done.
Mon May  9 16:57:59 2022: [....] Starting firewall: ufw...Setting kernel variables (/etc/ufw/sysctl.conf)...??7[ ok 8??done.
Mon May  9 16:58:00 2022: [....] Configuring network interfaces...ifup: waiting for lock on /run/network/ifstate.eth0
Mon May  9 16:58:06 2022: ifup: interface eth0 already configured
Mon May  9 16:58:06 2022: ??7[ ok 8??done.
Mon May  9 16:58:06 2022: [....] Cleaning up temporary files...??7[ ok 8??.
Mon May  9 16:58:06 2022: [....] Setting up ALSA...??7[ ok 8??done.
Mon May  9 16:58:06 2022: [....] Setting sensors limits...??7[ ok 8??done.
Mon May  9 16:58:06 2022: [....] Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix??7[ ok 8??.
Mon May  9 16:58:06 2022: INIT: Entering runlevel: 2
Marjorie wrote:

Are you using UFW in default mode or have you added rules?

Marjorie wrote:

Have you tried reinstalling ufw and iptables?

No, I have not added my own rules. I use the default setting with UFW. I have already uninstalled and reinstalled UFW several times with all its dependencies. But the error still persists. It is because of UFW that the errors appear. If I disable UFW, then there are no more error warnings. If I enable it, then the errors come again when I boot the laptop. After booting the laptop, however, UFW remains active.

Output:

root@Lenovo:~# ufw status
Status: active
root@Lenovo:~# /usr/sbin/ufw status
Status: active
Marjorie wrote:

What output do you get if you run: sudo service ufw start

Output looks like this:

root@Lenovo:~# service ufw start
Starting firewall: ufw...Setting kernel variables (/etc/ufw/sysctl.conf)...Firewall already started, use 'force-reload'...done.

On my other laptop, where UFW is constantly disabled at startup, I removed Iptables completely with its dependencies. This laptop now has no internet connection. With the removal of Iptables was also removed Nftables, Connman internet service, UFW .... . I can't connect to the internet with it now. It looks like I have to reinstall Devuan completely. Or is there another step to establish an internet connection?

#15 Re: Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-22 15:43:09

czeekaj wrote:

Try removing and then re-adding the option to append to iptables.

Where exactly and where should I make a change? I have looked at all the files in the folders and got nowhere.

czeekaj wrote:

I might just have to migrate to biting the bullet and learning iptables and nftables.
That way you have less overhead and less to worry about.

Yes, you seem to be right. But unfortunately it is not that easy. Until it is, I will rather switch to another Linux than deal with Iptables and Nftables.

I hope that the bug will eventually go away after all. I mean, the other versions of Devuan had no problems with UFW.

#16 Installation » [SOLVED] UFW causes errors under Chimaera » 2022-05-17 18:25:14

Dev1User
Replies: 14

Hello,

since upgrading from Beowulf to Chimaera, UFW keeps causing errors. When rebooting the system, I was able to photograph the error messages. Unfortunately, I can't do anything with these error warnings, because I don't know what to do exactly. But it is interesting that despite the error warning UFW remains active after booting the PC. Is this now a serious error, or can it be left at that?

However, on my other laptop, UFW is constantly disabled at boot up. That's why there is no error warning when the PC boots up.

Both laptops are running the default sysvinit system.

Everything ran fine under Ascii and Beowulf. There were no errors. But under Chimaera it seems to be different still unfortunately. It seems that under Chimaera not all errors are fixed yet.

As an attachment, I wanted to upload two photos where you can see the error warnings, but unfortunately I could not find a function how to upload the pictures here. Therefore I typed the start screen with the error warnings.

Failure Number 1:
Configure network interfaces...done.
Cleaning up temporary files...
Starting nftables: none.
Setting sensores limits...done.
Setting up X socket directories... /tmp/ .X11-unix /tmp/ .ICE-unix.
Setting up ALSA...done.
Starting firewall: ufw...iptables-restore v1.8.7 (nf_tables): Chain ´ufw-logging-deny´ does not exist
Error occurred at line: 75
Try ´iptables-restore -h´ or ´iptables-restore --help´ for more Information.
iptables-restore v1.8.7 (nf_tables): Chain ´ufw-skip-to-policy-input´ does not exist
Error occurred at line: 30
Try ´iptables-restore -h´ or ´iptables-restore --help´ for more Information.
iptables-restore: line 5 failed
...
Problem running ´/etc/ufw/before.rules´...
Problem running ´/etc/ufw/after.rules´...
failed
startpar: service(s) returned failure: ufw ... failed!
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Enabling additional executable binary formats: binfmt-support.
Setting up console font and keymap...done.
...
Failure Number 2:
Cleaning up temporary files ... /tmp.
Loading kernel module lp.
Loading kernel module ppdev.
Loading kernel module parport_pc.
Mounting local filesystems...done.
Activating swapfile swap, if any..done.
Cleaning up temporary files...
Starting up resolvconf.../etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf
done.
Starting: AppArmorLoading AppArmor profile...done.
.
Configuring network interfaces...done.
Cleaning up temporary files....
Setting up ALSA...done.
Setting sensors limits...done.
Starting nftables: none.
Setting up X socket directories... /tmp/.X11-unix /tmp/.ICE-unix.
Starting firewall: ufw...
iptables-restore v1.8.7 (nf-tables):
line 75: CHAIN_USER_ADD failed (No such file or directory): chain ufw-before-input
line 75: CHAIN_USER_ADD failed (No such file or directory): chain ufw-before-output
line 75: CHAIN_USER_ADD failed (No such file or directory): chain ufw-before-forward
line 75: CHAIN_USER_ADD failed (No such file or directory): chain ufw-not-local
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-output
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-output
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-forward
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 75: RULE_APPEND failed (No such file or directory): rule in chain ufw-before-input
line 75: RULE_APPEND failed (No such file or directory): rule in chain
iptables-restore v1.8.7 (nf_tables): Chain ´ufw-skip-to-policy-input´ does not exist
Error occurred at line: 30
Try ´iptables-restore -h´ or ´iptables-restore --help´ for more information.
iptables-restore: line 5 failed
...
Problem running ´/etc/ufw/before.rules´ ...Problem running ´/etc/ufw/after.rules´...
failed.
startpar: service(s) returned failure: ufw ... failed!
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Enabling additional executable binary formats: binfmt-support.
Setting up console font and keymap...done.
...

Board footer

Forum Software