The officially official Devuan Forum!

You are not logged in.

#802 Re: Other Issues » Scrolling Output in the Console Window » 2022-04-03 09:28:28

Well, there is no generic Devuan console. I guess you are talking about the terminals you can open on the graphical DE. There may of them, Gnome Terminal, Mate Terminal, xterm ....

Why don't you tell us a bit about the environment you are working on?

rolfie

#803 Re: Installation » [SOLVED] ceres sid update errors » 2022-03-23 21:15:25

Clean out your sources.list so that only the relevant entries remain.

In Ceres you should only have:

deb http://deb.devuan.org/merged ceres main contrib non-free

active. There are no security updates, no updates, no backports.

rolfie

#804 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 17:33:54

SCNR: Thats why I don't use NVidea at all.

Well, maybe you need to run a setup for your drivers that builds the modules. And you probably also need the headers for the new kernel to do that. I know that I need them for building the VBox kernel modules. Also a manual process.

Try that:
# apt -t beowulf-backports install linux-headers-amd64

rolfie

#805 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 13:19:12

Altoid wrote:

How can I get this done?

Run the previously posted command, that will  do the job.

rolfie

#806 Re: Installation » [SOLVED] Backported kernel update » 2022-03-20 11:00:27

fsmithred wrote:

There's no metapackage for backports kernels like there is for the main kernel. The only updates you would get would be if the kernel version didn't change. ...

I fear that is not 100% true. Besides the backports kernel you may also install the backports metapackage. In case of Beowulf:

# apt -t beowulf-backports install linux-image-amd64

Then you will lose the updates of the main kernel packages, but get the updates from backports. You can't have both. This way you get the signed versions of the backports kernels.

I am using backports headers and kernels only, my Chimaera is running now with 5.16.

rolfie

#807 Re: Installation » Chimaera: xfce4 and changing to another window manager » 2022-03-17 20:50:00

migf wrote:

I tried to find in the syslog something about this but to no avail. Can this be a problem with the new linux kernel (5.10.0-12)?

Most likely not.

#808 Re: Installation » [SOLVED] any chances to install nvidia-legacy-340xx on Devuan chimaera? » 2022-03-17 20:47:56

Search the forum, I think there is one or the other thread about this topic.

#809 Re: Other Issues » How can we get Parent release name in devuan , for example Bullseye? » 2022-03-15 11:28:53

Not sure if this is a Devuan topic. I guess this file is a copy of the corresponding file from Debian. Just verified with a Bullseye installation in my VBox. There I also get 11.2.

rolfie

#810 Re: Other Issues » [ceres] X session hang [SOLVED] » 2022-03-02 15:27:12

AFAIK slim is depracated, no more maintained for many years now. Give lightdm a try if that works.

#811 Re: Other Issues » Featured in Discover (KDE Plasma) not working » 2022-03-02 14:17:15

swarfendor437 wrote:
rolfie wrote:

Can't comment on Discover and KDE, not my DE.

But what hits my eyes is that for Chimaera you just have enabled main. And for the others also contrib nonfree. Does not make sense. Either all in or all out.

rolfie

That is all that is available to me - should I keep the 'sources' in? Guess it's because I have come from a different GNU/Linux prior to Devuan.

Thanks for your time and input.

Looks like I wasn't clear enough. You wrote:

Chimaera (main)
Chimaera security (main contrib non-free)
Chimaera updates (main contrib non-free)

This is inconsistant. Your entries in the sources.list should read either full blown:

deb http://deb.devuan.org/merged chimaera main non-free contrib
deb http://deb.devuan.org/merged chimaera-security main non-free contrib
deb http://deb.devuan.org/merged chimaera-updates main non-free contrib
deb http://deb.devuan.org/devuan chimaera-proposed-updates main non-free contrib
deb http://deb.devuan.org/merged chimaera-backports main non-free contrib

which I would suggest or

deb http://deb.devuan.org/merged chimaera main 
deb http://deb.devuan.org/merged chimaera-security main 
deb http://deb.devuan.org/merged chimaera-updates main 
deb http://deb.devuan.org/devuan chimaera-proposed-updates 
deb http://deb.devuan.org/merged chimaera-backports main 

if you don't want non-free packages or packages with other licences on your computer. It simply has to be all the same through the lines. As long as you do not compile your own packages, you do not need the sources.

Further readings at: https://www.devuan.org/os/packages

I hope I have made my point clear now.

rolfie

#812 Re: Installation » Question about netinstall to existing UEFI-based system » 2022-03-02 09:32:31

Well, in EFI mode the two installations are completely independent from each other. There is no detection of another Linux, this only works with Windose. You will either have to use the computers BIOS Boot override key or set up a manual grub config. With the downside that you have to modify this with every new kernel manually, there will be no automatic configuration possible.

Apart from that: use manual partitioning, make sure you hit p3 for Chimaera. Note: I have made the experience that with the first boot past the install the efivars are not mounted. I am adding that to the fstab. There are threads about that here in the forum.

If you have further questions, please ask.

rolfie

#813 Re: Other Issues » Featured in Discover (KDE Plasma) not working » 2022-03-01 22:05:35

Can't comment on Discover and KDE, not my DE.

But what hits my eyes is that for Chimaera you just have enabled main. And for the others also contrib nonfree. Does not make sense. Either all in or all out.

rolfie

#814 Re: Installation » [SOLVED] How to blow away efi partition using live-install iso? » 2022-02-24 12:37:17

Can you specify your hardware exactly? It should be possible to install Chimaera per netinstall in efi mode. I would first just install the basic system without DE, make sure all drivers for the HW are present, and then add a DE. This approach should help to overcome all issues.

BTW: I have stumbled across an effect that Chimaera in efi mode does not mount the efivars on first real boot. You have to do that manually once I think, then it works.

rolfie

#816 Re: Hardware & System Configuration » [SOLVED] nfs trouble on Chimaera » 2022-02-19 20:54:58

Got the problem. It was a simple "-" in the wrong place in the /etc/default/nfs-kernel-server. I had in there:

RPCMOUNTDOPTS="--manage-gids --debug-all"

Removing the dash in second option changing it to "--debug all" made the script work.

rolfie

#817 Hardware & System Configuration » [SOLVED] nfs trouble on Chimaera » 2022-02-18 17:52:16

rolfie
Replies: 6

Had to freshly install my file server. The system SSD was defective, data isn't affected. Now the nfs server won't start up. Error message is:

# service nfs-kernel-server restart
Stopping NFS kernel daemon: mountd nfsd.
Unexporting directories for NFS kernel daemon....
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd mountdUsage: rpc.mountd [-F|--foreground] [-h|--help] [-v|--version] [-d kind|--debug kind]
	[-o num|--descriptors num]
	[-p|--port port] [-V version|--nfs-version version]
	[-N version|--no-nfs-version version] [-n|--no-tcp]
	[-H prog |--ha-callout prog] [-r |--reverse-lookup]
	[-s|--state-directory-path path] [-g|--manage-gids]
	[-t num|--num-threads=num] [-u|--no-udp]
 failed!
# showmount -e fs090
clnt_create: RPC: Program not registered 

I don't know how to deal with this situation.

Background info: Xeon 4 core CPU on X99-E WS, 32G RAM, 256G Plextor nvme as system disk, LSI9271 supplying a RAID6 with about 5TB space, two more disks for single shares. Installed from Chimaera netinstall, encrypted LVM, openrc as init, manual installation of xorg, lightdm, Mate desktop, nfs-common, nfs-kernel-server. Latest stock kernel and backports kernels available, 5.15 is the default. It does not matter which one I do boot. The RAID6 is nicely decrypted and mounted, also the two other disks. The export file is a copy of the original one from a backup. Most of the setup I have taken from my notes. Everything should work.

The above error is shown as well during boot as when I try to restart the nfs-server. Also showmount throws an error. The duck does not give hints to this error.

Also tried to drill down how the nfs-server is started. The script in /etc/rc0.d does not contain this specific error printout. How can I find the root cause for the startup failure?

Thanks, rolfie

#818 Re: Other Issues » [SOLVED] Login screen appear after 4 min after setting nftable rules. » 2022-02-14 17:32:24

I am using lightdm with Mate or Cinnamon, no issues, uses elogind.

#819 Re: Installation » The best init system » 2022-02-14 17:27:54

I am using openrc since ASCII.

#820 Re: DIY » Nala (a prettier apt?) » 2022-02-10 18:30:02

Don't break your Devuan ...

#821 Re: Installation » chimera 4.0.0 server install -- seeing desktop ackages being installed » 2022-01-28 17:39:14

I guess you overlooked that per Default the XFCE desktop is ticked.

rolfie

#822 Re: Hardware & System Configuration » Micro SD card problem, cannot fix errors. » 2022-01-26 15:53:28

From man wipefs:

wipefs allows to erase filesystem or raid signatures (magic strings) from the device to make the filesystem invisible for libblkid. wipefs does not erase the whole filesystem or any other data from the device. When used without options -a or -o, it lists all visible filesystems and offsets of their signatures.

#823 Re: Hardware & System Configuration » Micro SD card problem, cannot fix errors. » 2022-01-26 15:04:17

I am not 100% sure what you try to tell us. You say are aware of the bit that only on "Apply" the actual changes are written to the SD cards. Ok, another bit: gparted is a tool that works on partition information and everything around that, not on file systems directly. Its basically a graphical interface for fdisk and mkfs.

Well, after the "Apply" has finished gparted re-reads the partitioning information for all the devices that are available. If then the same structures are presented for the SD card, then obviously the write operation wasn't successful. I would claim that gparted works quite well. And I would conclude that the involved HW isn't working correctly. If gparted displays that the SD card now is empty, then that is the information that came back from the HW.

What exactly means:

The bit I have a problem with is that gparted tells me it had success in deleting the partition, when it clearly didnt, if I unplug and then plug it in again, I can read the files straight away, no windows involved.

This would be some sort of miracle. Maybe SD card and reader are not compatible, or some sort of buffer is involved, or the SD cards are simply crap.

You seem to have tried dd also, also with no result.

If you sum up all these bits and bytes, what do you think about cards and reader?

rolfie

#824 Re: Hardware & System Configuration » Micro SD card problem, cannot fix errors. » 2022-01-26 11:29:20

Some thoughts to the issues:

When plugging in the SD card reader and the card itself: inspect dmesg for hints if the device is write protected.

To gparted: I am using gparted for many years and never had it fail. I started of with gparted life versions, still use them every now and then.

There may be a trap for the unexperienced user: you can prepare a lot of operations, but these are not executed on the real HW before you don't tick the apply button. Are you aware of this?

In addition I suggest to tick the Device Information box in the View menu. Gives you confirmation that you are working on the right device.

If that does not work the card may be defective.

rolfie

Board footer

Forum Software