You are not logged in.
- Topics: Active | Unanswered
#1 Re: Installation » Black screen afte boot » Today 11:02:48
Ah ok, you have used the live version to install. That has some deficincies when trying to setup an encrypted PC. One of them being that the swap partition isn't encrypted which is a big loophole. I am not aware about any method of easily encrypting the swap partition and adding that to an encrypted root. Adding it unencrypted is possible. Format partition2 as swap and include it into the fstab.
The normal installer, no matter if you use netinstall, the CD or the DVD version, they support an encrypted luks container as physical volume for a LVM holding logical volumes for / and swap. Thats what I use and the live version does not support. Just /boot isn't encrypted. When the PC is off swap is locked inside the encrypted container and can't be read.
Your choice if you can live with what you got. I would recommend an installation from any regular medium.
To the root access problems: the sudo method works, you have to use sudo before any single admin command you want to issue. User password is required. This is the so called "Ubuntu" method.
When you have assigned a password to root, you can become superuser with the su command in a user terminal. You will be asked for the root password and then can issue an endless number of admin commands as you like without being asked for passwords again. There is a problem though: from Debian 10 Buster/Devuan 3 Beowulf onward Debian did move the su command code to a different package. An underlying change is related to the path: simply using su now uses the user path setting, and not the admin path anymore, resulting in many "command not found" messages. Now only with su - the path is set correctly. Workaround: edit /etc/login.defs and add a line with ALWAYS_SET_PATH yes where the paths are defined.
#2 Re: Devuan » Why are systemd files present in Devuan? » Today 09:57:09
@blackhole: well done, nicely summarized.
#3 Re: Installation » [SOLVED]Can't access deb.devuan.org/* daedalus repositories » Yesterday 18:36:27
Is there a list of alternative update/software package repo mirror sites somewhere?
Look at the top of the forum page, there is a link to Devuan.org, and read the Packages page.
#4 Re: Installation » Black screen afte boot » Yesterday 18:30:52
@Tweedlewise: your post #7 is confusing me. I carefully try to give some answers, maybe they help.
Obviously you have managed to install Devuan, congratulations. Did you use netinstall, CD, DVD or the live version? Makes slight differences here and there in what you need to do and what you get.
How do I install additional programs?
Third question answered first: you found the graphical tool Synaptics yourself. On the console the most commonly use tools are apt, apt-get or aptitude. Look into the man pages. What also is a good source of information is the Ubuntu wiki. Most of what is written there is also valid for Debian/Devuan. I assumne that you are not afraid of working with the terminal as former sysop.
During install I gave it separate passwords for the disk, partitions, root, and user/self.
The installer asks you very early in the installtion if you want a root password. If you deny you have to use the Ubuntu way with sudo for administrative tasks. I guess you have said yes, so root has a password and you must also have generated at least one user and password.
What are passwords for disks and partitions? I think the terminology is wrong. Maybe you have encrypted your system, then you need a key (and not a password) to decrypt the drive during booting. If you haven't encrypted your system: What are passwords for disks and partitions?
It would help a lot if you could try to use the correct terms and sort of same language. Avoids guessing for the supporter, and false advice for the poster who is seeking advice.
I made 3 partitions root, swap, home
I set the 2nd as linux-swap, but is not being used as swap, just sits there, showing up as a partition that I cannot access,
1. How can I get the system to recognize it as swap when booting?
How did you create these 3 partitions? And how did you use the partitioner inside the installer? Did you use manual or guided partitioning?
Guided partitioning sets up the disks sort of automatically, no matter if encrypted or not. Swap is automatically included. You have no choice and cannot make a mistake (but using guided which is fine for the unexperienced user, but for me that sets partition size too small often for nowadays disk sizes). I only use manual partitioning because I want to have control. But to successfully practise manual partitioning requires knowledge and experience, especially when we are talking about encryption.
To be able to answer the question how to add swap, you owe us some information about which kind of boundary condition we are facing in your case. How does the installation look alike currently?
A good start would be the output from
~$ inxi -Fzrand
# fdisk -l
Note: the first command is run on the user account, the second one as root, indicated by the prompt before the command.
PS: I do set up my system with the traditional so called full disk encryption with luks, having an unencrypted /boot, and I am decrypting the computer with hidden keys sitting on USB sticks. When the stick is removed the PC does not boot.
#5 Re: Installation » How re-run the hardware detection and drivers install ? » Yesterday 12:38:24
lspci and lsusb to find out what adapter is used? And from there install the relevant firmware and drivers?
#6 Re: Installation » Black screen afte boot » 2025-01-20 20:49:01
Well amd64 is the 64bit Linux for AMD and Intel processors. It serves both brands. Download that version.
To inxi: that is no traditional command but a collection of scripts that collects information about the PC and prints it on the terminal. Very useful. I don't think it works in recovery mode, but give it a try. If it works you might be able to capture the output in a txt file.
To NVidia: these cards cause a lot of fun, and your black screen might be some of that ...
BTW: inxi output looks like this (cut off):
~$ inxi -Fzr
System:
Kernel: 6.11.10+bpo-amd64 arch: x86_64 bits: 64 Desktop: Cinnamon v: 5.6.8
Distro: Devuan GNU/Linux 5 (daedalus)
Machine:
Type: Desktop Mobo: ASUSTeK model: PRIME X570-PRO v: Rev X.0x
serial: <superuser required> UEFI: American Megatrends v: 5021
date: 09/29/2024
CPU:
Info: 12-core model: AMD Ryzen 9 5900X bits: 64 type: MT MCP cache:
L2: 6 MiB
Speed (MHz): avg: 677 min/max: 550/4951 cores: 1: 550 2: 550 3: 550 4: 550
5: 550 6: 550 7: 550 8: 550 9: 3600 10: 550 11: 550 12: 550 13: 550 14: 550
15: 550 16: 550 17: 550 18: 550 19: 550 20: 550 21: 550 22: 550 23: 550
24: 550
Graphics:
Device-1: AMD Navi 14 [Radeon RX 5500/5500M / Pro 5500M] driver: amdgpu
v: kernel
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
resolution: 2560x1440~60Hz
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 5500 XT (navi14
LLVM 15.0.6 DRM 3.59 6.11.10+bpo-amd64)
....You possibly need to run a live system to get that info.
#7 Re: Installation » Black screen afte boot » 2025-01-20 18:49:26
Hi there, welcome to the dev1galaxy forum.
Well, some questions: is your computer really about ten years old? Then why do you want to install the 32bit version? Why not amd64? Any ten year old PC will be able to use that (except some very crude simple outdated stuff). And why use a DVD? Booting from an USB stick should also be fully supported from such kind of hardware.
A guess: NVidia graphics involved?
It would be perfect for support if we knew more about the involved components. Please can you add here the output from
inxi -Fzr? It may be neccesary to install this package first.
#8 Re: Installation » Cannot install HPLIP Plugin on Devuan » 2025-01-19 13:00:36
@wingcommander1999: you have confirmed that you try to install stuff coming directly from the HP website. Get rid of that and try to work with the tested stuff from inside the repo. Chances are good that that will work.
#9 Re: Installation » Cannot install HPLIP Plugin on Devuan » 2025-01-18 22:44:24
Is that plugin from the Devuan repo or have you downloaded it from the HP home page?
#10 Re: Hardware & System Configuration » best way to install kernel 6.12 in Daedalus » 2025-01-17 16:12:26
Currently you will find 6.11 kernels in the Daedalus backports. When Debian decides that 6.12 is suitable for backports, you may get it in Daedalus too. Devuan kernels are Debian kernels.
Testing/Trixie/Excalibur do run on a 6.12 kernel currently. When you are running on brand new hardware, upgrading to Excalibur might be an option.
#11 Re: Hardware & System Configuration » [SOLVED] Suspend lockup lately » 2025-01-14 06:55:21
Hibernation is back to success, worked over night.
#12 Re: Hardware & System Configuration » [SOLVED] Suspend lockup lately » 2025-01-13 15:14:25
Late follow up on the problem: looks like the problem is due to a combination of a Toshiba Transmemory USB3 stick connected to a Sempre UP33-I19 USB3-card with a NEC 720201 chipset that is installed in my PC case to serve an Akasa USB-C output.
pm-hibernate as root
2025-01-13T14:38:03.015716+01:00 rh060 kernel: [18658.266669] PM: hibernation: hibernation entry
2025-01-13T14:38:03.015733+01:00 rh060 kernel: [18658.267856] Filesystems sync: 0.000 seconds
2025-01-13T14:38:03.015733+01:00 rh060 kernel: [18658.267940] Freezing user space processes
2025-01-13T14:38:03.015795+01:00 rh060 kernel: [18658.269309] Freezing user space processes completed (elapsed 0.001 seconds)
2025-01-13T14:38:03.015797+01:00 rh060 kernel: [18658.269311] OOM killer disabled.
2025-01-13T14:38:03.015799+01:00 rh060 kernel: [18658.269853] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
2025-01-13T14:38:03.015800+01:00 rh060 kernel: [18658.269856] PM: hibernation: Marking nosave pages: [mem 0x000a0000-0x000fffff]
2025-01-13T14:38:03.015800+01:00 rh060 kernel: [18658.269859] PM: hibernation: Marking nosave pages: [mem 0x09d1f000-0x09ffffff]
2025-01-13T14:38:03.015800+01:00 rh060 kernel: [18658.269874] PM: hibernation: Marking nosave pages: [mem 0x0a200000-0x0a20dfff]
2025-01-13T14:38:03.015801+01:00 rh060 kernel: [18658.269876] PM: hibernation: Marking nosave pages: [mem 0xc3273000-0xc3273fff]
2025-01-13T14:38:03.015801+01:00 rh060 kernel: [18658.269877] PM: hibernation: Marking nosave pages: [mem 0xc8a4f000-0xc8a4ffff]
2025-01-13T14:38:03.015801+01:00 rh060 kernel: [18658.269879] PM: hibernation: Marking nosave pages: [mem 0xc9f76000-0xcb9fefff]
2025-01-13T14:38:03.015802+01:00 rh060 kernel: [18658.270001] PM: hibernation: Marking nosave pages: [mem 0xcd000000-0xffffffff]
2025-01-13T14:38:03.015802+01:00 rh060 kernel: [18658.271592] PM: hibernation: Basic memory bitmaps created
2025-01-13T14:38:03.015803+01:00 rh060 kernel: [18658.272090] PM: hibernation: Preallocating image memory
2025-01-13T14:38:03.015803+01:00 rh060 kernel: [18660.242343] PM: hibernation: Allocated 1215042 pages for snapshot
2025-01-13T14:38:03.015803+01:00 rh060 kernel: [18660.242347] PM: hibernation: Allocated 4860168 kbytes in 1.97 seconds (2467.09 MB/s)
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.242350] Freezing remaining freezable tasks
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.243553] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.297203] printk: Suspending console(s) (use no_console_suspend to debug)
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.503010] xhci_hcd 0000:05:00.0: PM: pci_pm_freeze(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503027] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503032] xhci_hcd 0000:05:00.0: PM: failed to freeze async: error -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.527764] amdgpu 0000:0c:00.0: amdgpu: MODE1 reset
2025-01-13T14:38:03.015806+01:00 rh060 kernel: [18660.527767] amdgpu 0000:0c:00.0: amdgpu: GPU mode1 reset
2025-01-13T14:38:03.015806+01:00 rh060 kernel: [18660.527841] amdgpu 0000:0c:00.0: amdgpu: GPU psp mode1 reset
2025-01-13T14:38:03.015806+01:00 rh060 kernel: [18661.042508] [drm] psp mode1 reset succeed
2025-01-13T14:38:03.015807+01:00 rh060 kernel: [18661.360235] usb usb3: root hub lost power or was reset
2025-01-13T14:38:03.015807+01:00 rh060 kernel: [18661.360239] usb usb4: root hub lost power or was reset
2025-01-13T14:38:03.015807+01:00 rh060 kernel: [18661.360310] usb usb5: root hub lost power or was reset
2025-01-13T14:38:03.015808+01:00 rh060 kernel: [18661.360313] usb usb6: root hub lost power or was reset
2025-01-13T14:38:03.015808+01:00 rh060 kernel: [18661.360367] usb usb7: root hub lost power or was reset
2025-01-13T14:38:03.015808+01:00 rh060 kernel: [18661.360369] usb usb8: root hub lost power or was reset
2025-01-13T14:38:03.015809+01:00 rh060 kernel: [18661.370639] nvme nvme0: D3 entry latency set to 10 seconds
2025-01-13T14:38:03.015809+01:00 rh060 kernel: [18661.371566] nvme nvme0: 8/0/0 default/read/poll queues
2025-01-13T14:38:03.015809+01:00 rh060 kernel: [18661.371873] nvme nvme0: Ignoring bogus Namespace Identifiers
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.392492] nvme nvme1: 24/0/0 default/read/poll queues
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.654600] usb 5-4: reset full-speed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.654603] usb 3-2: reset high-speed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015810+01:00 rh060 kernel: [18661.654606] usb 7-4: reset full-speed USB device number 6 using xhci_hcd
2025-01-13T14:38:03.015821+01:00 rh060 kernel: [18661.834233] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015822+01:00 rh060 kernel: [18661.834262] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015823+01:00 rh060 kernel: [18661.834353] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015823+01:00 rh060 kernel: [18661.834380] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T14:38:03.015823+01:00 rh060 kernel: [18661.834674] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015824+01:00 rh060 kernel: [18661.835016] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015824+01:00 rh060 kernel: [18661.835141] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015825+01:00 rh060 kernel: [18661.835858] sd 8:0:0:0: [sdb] Starting disk
2025-01-13T14:38:03.015825+01:00 rh060 kernel: [18661.835866] sd 5:0:0:0: [sdc] Starting disk
2025-01-13T14:38:03.015826+01:00 rh060 kernel: [18661.835962] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015826+01:00 rh060 kernel: [18661.836033] sd 9:0:0:0: [sdd] Starting disk
2025-01-13T14:38:03.015826+01:00 rh060 kernel: [18661.836133] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015827+01:00 rh060 kernel: [18661.836693] ata6.00: configured for UDMA/133
2025-01-13T14:38:03.015827+01:00 rh060 kernel: [18661.836864] ata10.00: configured for UDMA/133
2025-01-13T14:38:03.015828+01:00 rh060 kernel: [18661.837367] ata9.00: configured for UDMA/133
2025-01-13T14:38:03.015828+01:00 rh060 kernel: [18661.838231] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T14:38:03.015829+01:00 rh060 kernel: [18661.838259] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T14:38:03.015829+01:00 rh060 kernel: [18661.839512] sd 4:0:0:0: [sda] Starting disk
2025-01-13T14:38:03.015829+01:00 rh060 kernel: [18661.839728] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T14:38:03.015830+01:00 rh060 kernel: [18661.841066] ata4.00: configured for UDMA/133
2025-01-13T14:38:03.015830+01:00 rh060 kernel: [18661.841448] ata3.00: configured for UDMA/100
2025-01-13T14:38:03.015830+01:00 rh060 kernel: [18661.844526] ata5.00: configured for UDMA/133
2025-01-13T14:38:03.015831+01:00 rh060 kernel: [18661.854762] ata5.00: Enabling discard_zeroes_data
2025-01-13T14:38:03.015831+01:00 rh060 kernel: [18661.930270] usb 7-1: reset high-speed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015831+01:00 rh060 kernel: [18661.930483] usb 4-2: reset SuperSpeed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015832+01:00 rh060 kernel: [18662.100380] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
2025-01-13T14:38:03.015832+01:00 rh060 kernel: [18662.100413] amdgpu 0000:0c:00.0: amdgpu: PSP is resuming...
2025-01-13T14:38:03.015832+01:00 rh060 kernel: [18662.206308] usb 7-3: reset full-speed USB device number 3 using xhci_hcd
2025-01-13T14:38:03.015833+01:00 rh060 kernel: [18662.255679] amdgpu 0000:0c:00.0: amdgpu: reserve 0x900000 from 0x81fd000000 for PSP TMR
2025-01-13T14:38:03.015833+01:00 rh060 kernel: [18662.298741] amdgpu 0000:0c:00.0: amdgpu: RAS: optional ras ta ucode is not available
2025-01-13T14:38:03.015833+01:00 rh060 kernel: [18662.304815] amdgpu 0000:0c:00.0: amdgpu: RAP: optional rap ta ucode is not available
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304816] amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304819] amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304858] amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable
2025-01-13T14:38:03.015834+01:00 rh060 kernel: [18662.304860] amdgpu 0000:0c:00.0: amdgpu: smc_dpm_info table revision(format.content): 4.5
2025-01-13T14:38:03.015835+01:00 rh060 kernel: [18662.336805] amdgpu 0000:0c:00.0: amdgpu: SMU is resumed successfully!
2025-01-13T14:38:03.015835+01:00 rh060 kernel: [18662.483338] usb 8-1: reset SuperSpeed USB device number 2 using xhci_hcd
2025-01-13T14:38:03.015835+01:00 rh060 kernel: [18662.582272] usb 7-1.4: reset high-speed USB device number 5 using xhci_hcd
2025-01-13T14:38:03.015836+01:00 rh060 kernel: [18662.759659] [drm] kiq ring mec 2 pipe 1 q 0
2025-01-13T14:38:03.015837+01:00 rh060 kernel: [18662.761300] amdgpu 0000:0c:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
2025-01-13T14:38:03.015837+01:00 rh060 kernel: [18662.761302] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
2025-01-13T14:38:03.015837+01:00 rh060 kernel: [18662.761303] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
2025-01-13T14:38:03.015838+01:00 rh060 kernel: [18662.761304] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0
2025-01-13T14:38:03.015838+01:00 rh060 kernel: [18662.761305] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0
2025-01-13T14:38:03.015838+01:00 rh060 kernel: [18662.761306] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761307] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761308] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761309] amdgpu 0000:0c:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0
2025-01-13T14:38:03.015839+01:00 rh060 kernel: [18662.761310] amdgpu 0000:0c:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 11 on hub 0
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761311] amdgpu 0000:0c:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761312] amdgpu 0000:0c:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761312] amdgpu 0000:0c:00.0: amdgpu: ring vcn_dec uses VM inv eng 0 on hub 8
2025-01-13T14:38:03.015840+01:00 rh060 kernel: [18662.761313] amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 1 on hub 8
2025-01-13T14:38:03.015841+01:00 rh060 kernel: [18662.761314] amdgpu 0000:0c:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 4 on hub 8
2025-01-13T14:38:03.015841+01:00 rh060 kernel: [18662.761315] amdgpu 0000:0c:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 on hub 8
2025-01-13T14:38:03.015841+01:00 rh060 kernel: [18662.762324] usb 7-1.2: reset full-speed USB device number 4 using xhci_hcd
2025-01-13T14:38:03.015842+01:00 rh060 kernel: [18662.866598] snd_hda_intel 0000:0c:00.1: CORB reset timeout#2, CORBRP = 65535
2025-01-13T14:38:03.015842+01:00 rh060 kernel: [18662.922449] PM: hibernation: Basic memory bitmaps freed
2025-01-13T14:38:03.015842+01:00 rh060 kernel: [18662.922562] OOM killer enabled.
2025-01-13T14:38:03.019240+01:00 rh060 kernel: [18662.922563] Restarting tasks ... done.
2025-01-13T14:38:03.019249+01:00 rh060 kernel: [18662.923108] PM: hibernation: hibernation exit
2025-01-13T14:38:03.419377+01:00 rh060 kernel: [18663.323104] usb 7-1.2: usbfs: process 3842 (pcscd) did not claim interface 0 before use
2025-01-13T14:38:04.234946+01:00 rh060 ntpd[3872]: IO: Deleting interface #3 eth0, 10.6.6.60#123, interface stats: received=819, sent=820, dropped=0, active_time=18628 secs
2025-01-13T14:38:04.234961+01:00 rh060 ntpd[3872]: PROTO: 78.47.249.55 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234964+01:00 rh060 ntpd[3872]: PROTO: 51.75.67.47 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234967+01:00 rh060 ntpd[3872]: PROTO: 148.251.5.46 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234970+01:00 rh060 ntpd[3872]: PROTO: 79.133.44.137 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234972+01:00 rh060 ntpd[3872]: PROTO: 185.252.140.125 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234975+01:00 rh060 ntpd[3872]: PROTO: 78.47.56.71 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234977+01:00 rh060 ntpd[3872]: PROTO: 10.6.6.1 unlink local addr 10.6.6.60 -> <null>
2025-01-13T14:38:04.234982+01:00 rh060 ntpd[3872]: IO: Deleting interface #7 eth0, fe80::6d9:f5ff:fef7:e393%2#123, interface stats: received=0, sent=0, dropped=0, active_time=18625 secs
2025-01-13T14:38:04.387263+01:00 rh060 kernel: [18664.291086] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2025-01-13T14:38:04.492192+01:00 rh060 NetworkManager[3754]: <info> [1736775484.4921] device (eth0): carrier: link connected
2025-01-13T14:38:06.235158+01:00 rh060 ntpd[3872]: IO: Listen normally on 8 eth0 10.6.6.60:123
2025-01-13T14:38:06.235188+01:00 rh060 ntpd[3872]: IO: Listen normally on 9 eth0 [fe80::6d9:f5ff:fef7:e393%2]:123
2025-01-13T14:38:06.235276+01:00 rh060 ntpd[3872]: IO: new interface(s) found: waking up resolver
Enable Hibernation 5min in Power Settings, no reset
2025-01-13T15:01:13.570268+01:00 rh060 dbus-daemon[4639]: [session uid=1000 pid=4637] Activating service name='org.cinnamon.ScreenSaver' requested by ':1.117' (uid=1000 pid=4803 comm="/usr/bin/python3 /usr/bin/cinnamon-screensaver-com")
2025-01-13T15:01:13.660005+01:00 rh060 dbus-daemon[4639]: [session uid=1000 pid=4637] Successfully activated service 'org.cinnamon.ScreenSaver'
2025-01-13T15:01:13.686837+01:00 rh060 x-session-manager[4580]: WARNING: t+20007,36655s: Detected that screensaver has appeared on the bus
2025-01-13T15:01:13.980097+01:00 rh060 NetworkManager[3754]: <info> [1736776873.9800] manager: sleep: sleep requested (sleeping: no enabled: yes)
2025-01-13T15:01:14.063242+01:00 rh060 kernel: [20053.972322] PM: suspend entry (deep)
2025-01-13T15:01:15.143872+01:00 rh060 kernel: [20053.979809] Filesystems sync: 0.007 seconds
2025-01-13T15:01:15.143886+01:00 rh060 kernel: [20053.980366] Freezing user space processes
2025-01-13T15:01:15.143915+01:00 rh060 kernel: [20053.981758] Freezing user space processes completed (elapsed 0.001 seconds)
2025-01-13T15:01:15.143921+01:00 rh060 kernel: [20053.981760] OOM killer disabled.
2025-01-13T15:01:15.143922+01:00 rh060 kernel: [20053.981761] Freezing remaining freezable tasks
2025-01-13T15:01:15.143922+01:00 rh060 kernel: [20053.982365] Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
2025-01-13T15:01:15.143923+01:00 rh060 kernel: [20053.982383] printk: Suspending console(s) (use no_console_suspend to debug)
2025-01-13T15:01:15.143923+01:00 rh060 kernel: [20054.074417] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
2025-01-13T15:01:15.143923+01:00 rh060 kernel: [20054.074593] ata6.00: Entering standby power mode
2025-01-13T15:01:15.143924+01:00 rh060 kernel: [20054.078380] sd 8:0:0:0: [sdb] Synchronizing SCSI cache
2025-01-13T15:01:15.143924+01:00 rh060 kernel: [20054.078753] ata9.00: Entering standby power mode
2025-01-13T15:01:15.143925+01:00 rh060 kernel: [20054.086362] sd 9:0:0:0: [sdd] Synchronizing SCSI cache
2025-01-13T15:01:15.143925+01:00 rh060 kernel: [20054.086541] ata10.00: Entering standby power mode
2025-01-13T15:01:15.143926+01:00 rh060 kernel: [20054.090369] sd 4:0:0:0: [sda] Synchronizing SCSI cache
2025-01-13T15:01:15.143926+01:00 rh060 kernel: [20054.090627] ata5.00: Entering standby power mode
2025-01-13T15:01:15.143927+01:00 rh060 kernel: [20054.234346] xhci_hcd 0000:05:00.0: PM: pci_pm_suspend(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T15:01:15.143927+01:00 rh060 kernel: [20054.234363] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
2025-01-13T15:01:15.143927+01:00 rh060 kernel: [20054.234368] xhci_hcd 0000:05:00.0: PM: failed to suspend async: error -16
2025-01-13T15:01:15.143928+01:00 rh060 kernel: [20054.855196] PM: Some devices failed to suspend, or early wake event detected
2025-01-13T15:01:15.143928+01:00 rh060 kernel: [20054.860801] nvme nvme0: D3 entry latency set to 10 seconds
2025-01-13T15:01:15.143928+01:00 rh060 kernel: [20054.861745] nvme nvme0: 8/0/0 default/read/poll queues
2025-01-13T15:01:15.143929+01:00 rh060 kernel: [20054.862081] nvme nvme0: Ignoring bogus Namespace Identifiers
2025-01-13T15:01:15.143929+01:00 rh060 kernel: [20054.885984] nvme nvme1: 24/0/0 default/read/poll queues
2025-01-13T15:01:15.143930+01:00 rh060 kernel: [20054.959228] snd_hda_intel 0000:0c:00.1: CORB reset timeout#2, CORBRP = 65535
2025-01-13T15:01:15.143930+01:00 rh060 kernel: [20055.054817] OOM killer enabled.
2025-01-13T15:01:15.147256+01:00 rh060 kernel: [20055.054819] Restarting tasks ... done.
2025-01-13T15:01:15.147261+01:00 rh060 kernel: [20055.055356] random: crng reseeded on system resumption
2025-01-13T15:01:15.147262+01:00 rh060 kernel: [20055.055360] PM: suspend exit
2025-01-13T15:01:15.147263+01:00 rh060 kernel: [20055.055417] PM: suspend entry (s2idle)
2025-01-13T15:01:15.423267+01:00 rh060 kernel: [20055.330670] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:15.423281+01:00 rh060 kernel: [20055.330671] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423282+01:00 rh060 kernel: [20055.330705] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423282+01:00 rh060 kernel: [20055.330710] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:15.423285+01:00 rh060 kernel: [20055.330736] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423285+01:00 rh060 kernel: [20055.330766] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:15.423286+01:00 rh060 kernel: [20055.331358] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423286+01:00 rh060 kernel: [20055.331448] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423286+01:00 rh060 kernel: [20055.331690] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423287+01:00 rh060 kernel: [20055.332045] sd 8:0:0:0: [sdb] Starting disk
2025-01-13T15:01:15.423287+01:00 rh060 kernel: [20055.332470] sd 5:0:0:0: [sdc] Starting disk
2025-01-13T15:01:15.423288+01:00 rh060 kernel: [20055.332583] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423288+01:00 rh060 kernel: [20055.332641] sd 9:0:0:0: [sdd] Starting disk
2025-01-13T15:01:15.423294+01:00 rh060 kernel: [20055.332740] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333344] ata9.00: configured for UDMA/133
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333368] ata6.00: configured for UDMA/133
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333397] ata6.00: Entering active power mode
2025-01-13T15:01:15.423295+01:00 rh060 kernel: [20055.333415] ata9.00: Entering active power mode
2025-01-13T15:01:15.423296+01:00 rh060 kernel: [20055.333477] ata10.00: configured for UDMA/133
2025-01-13T15:01:15.423296+01:00 rh060 kernel: [20055.333500] ata4.00: configured for UDMA/133
2025-01-13T15:01:15.423296+01:00 rh060 kernel: [20055.333947] ata3.00: configured for UDMA/100
2025-01-13T15:01:15.427250+01:00 rh060 kernel: [20055.336285] sd 4:0:0:0: [sda] Starting disk
2025-01-13T15:01:15.427255+01:00 rh060 kernel: [20055.336497] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:15.431247+01:00 rh060 kernel: [20055.341294] ata5.00: configured for UDMA/133
2025-01-13T15:01:15.443248+01:00 rh060 kernel: [20055.351586] ata5.00: Enabling discard_zeroes_data
2025-01-13T15:01:18.896987+01:00 rh060 kernel: [20055.356135] Filesystems sync: 0.300 seconds
2025-01-13T15:01:18.897006+01:00 rh060 kernel: [20055.356412] Freezing user space processes
2025-01-13T15:01:18.897035+01:00 rh060 kernel: [20055.482804] Freezing user space processes completed (elapsed 0.126 seconds)
2025-01-13T15:01:18.897035+01:00 rh060 kernel: [20055.482811] OOM killer disabled.
2025-01-13T15:01:18.897038+01:00 rh060 kernel: [20055.482813] Freezing remaining freezable tasks
2025-01-13T15:01:18.897038+01:00 rh060 kernel: [20055.484402] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
2025-01-13T15:01:18.897039+01:00 rh060 kernel: [20055.484408] printk: Suspending console(s) (use no_console_suspend to debug)
2025-01-13T15:01:18.897039+01:00 rh060 kernel: [20057.767244] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2025-01-13T15:01:18.897040+01:00 rh060 kernel: [20057.874382] sd 4:0:0:0: [sda] Synchronizing SCSI cache
2025-01-13T15:01:18.897040+01:00 rh060 kernel: [20057.874384] sd 5:0:0:0: [sdc] Synchronizing SCSI cache
2025-01-13T15:01:18.897041+01:00 rh060 kernel: [20057.874411] sd 8:0:0:0: [sdb] Synchronizing SCSI cache
2025-01-13T15:01:18.897041+01:00 rh060 kernel: [20057.874411] sd 9:0:0:0: [sdd] Synchronizing SCSI cache
2025-01-13T15:01:18.897042+01:00 rh060 kernel: [20057.874704] ata5.00: Entering standby power mode
2025-01-13T15:01:18.897042+01:00 rh060 kernel: [20057.874751] ata9.00: Entering standby power mode
2025-01-13T15:01:18.897043+01:00 rh060 kernel: [20057.875206] ata6.00: Entering standby power mode
2025-01-13T15:01:18.897044+01:00 rh060 kernel: [20057.875368] ata10.00: Entering standby power mode
2025-01-13T15:01:18.897044+01:00 rh060 kernel: [20058.034207] xhci_hcd 0000:05:00.0: PM: pci_pm_suspend(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T15:01:18.897045+01:00 rh060 kernel: [20058.034223] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -16
2025-01-13T15:01:18.897046+01:00 rh060 kernel: [20058.034228] xhci_hcd 0000:05:00.0: PM: failed to suspend async: error -16
2025-01-13T15:01:18.897046+01:00 rh060 kernel: [20058.508340] PM: Some devices failed to suspend, or early wake event detected
2025-01-13T15:01:18.897047+01:00 rh060 kernel: [20058.518054] nvme nvme0: D3 entry latency set to 10 seconds
2025-01-13T15:01:18.897047+01:00 rh060 kernel: [20058.518998] nvme nvme0: 8/0/0 default/read/poll queues
2025-01-13T15:01:18.897048+01:00 rh060 kernel: [20058.519304] nvme nvme0: Ignoring bogus Namespace Identifiers
2025-01-13T15:01:18.897048+01:00 rh060 kernel: [20058.538917] nvme nvme1: 24/0/0 default/read/poll queues
2025-01-13T15:01:18.897049+01:00 rh060 kernel: [20058.807923] OOM killer enabled.
2025-01-13T15:01:18.897141+01:00 rh060 ntpd[3872]: IO: Deleting interface #8 eth0, 10.6.6.60#123, interface stats: received=9, sent=9, dropped=0, active_time=1390 secs
2025-01-13T15:01:18.897154+01:00 rh060 ntpd[3872]: PROTO: 10.6.6.1 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897157+01:00 rh060 ntpd[3872]: PROTO: 78.47.56.71 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897160+01:00 rh060 ntpd[3872]: PROTO: 185.252.140.125 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897163+01:00 rh060 ntpd[3872]: PROTO: 79.133.44.137 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897165+01:00 rh060 ntpd[3872]: PROTO: 148.251.5.46 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897168+01:00 rh060 ntpd[3872]: PROTO: 51.75.67.47 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897171+01:00 rh060 ntpd[3872]: PROTO: 78.47.249.55 unlink local addr 10.6.6.60 -> <null>
2025-01-13T15:01:18.897175+01:00 rh060 ntpd[3872]: IO: Deleting interface #9 eth0, fe80::6d9:f5ff:fef7:e393%2#123, interface stats: received=0, sent=0, dropped=0, active_time=1390 secs
2025-01-13T15:01:18.899242+01:00 rh060 kernel: [20058.807924] Restarting tasks ... done.
2025-01-13T15:01:18.899246+01:00 rh060 kernel: [20058.808548] random: crng reseeded on system resumption
2025-01-13T15:01:18.899247+01:00 rh060 kernel: [20058.808558] PM: suspend exit
2025-01-13T15:01:19.071283+01:00 rh060 kernel: [20058.978687] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071294+01:00 rh060 kernel: [20058.978688] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:19.071295+01:00 rh060 kernel: [20058.978722] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071296+01:00 rh060 kernel: [20058.978723] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2025-01-13T15:01:19.071296+01:00 rh060 kernel: [20058.978754] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071298+01:00 rh060 kernel: [20058.978789] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2025-01-13T15:01:19.071298+01:00 rh060 kernel: [20058.979358] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071299+01:00 rh060 kernel: [20058.979623] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071299+01:00 rh060 kernel: [20058.979639] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071299+01:00 rh060 kernel: [20058.979956] sd 8:0:0:0: [sdb] Starting disk
2025-01-13T15:01:19.071300+01:00 rh060 kernel: [20058.980613] sd 5:0:0:0: [sdc] Starting disk
2025-01-13T15:01:19.071300+01:00 rh060 kernel: [20058.980627] sd 9:0:0:0: [sdd] Starting disk
2025-01-13T15:01:19.071301+01:00 rh060 kernel: [20058.980728] ata10.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071301+01:00 rh060 kernel: [20058.980736] ata6.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.071301+01:00 rh060 kernel: [20058.981253] ata9.00: configured for UDMA/133
2025-01-13T15:01:19.071302+01:00 rh060 kernel: [20058.981321] ata9.00: Entering active power mode
2025-01-13T15:01:19.071302+01:00 rh060 kernel: [20058.981455] ata10.00: configured for UDMA/133
2025-01-13T15:01:19.071302+01:00 rh060 kernel: [20058.981523] ata4.00: configured for UDMA/133
2025-01-13T15:01:19.071303+01:00 rh060 kernel: [20058.981536] ata6.00: configured for UDMA/133
2025-01-13T15:01:19.071313+01:00 rh060 kernel: [20058.981565] ata6.00: Entering active power mode
2025-01-13T15:01:19.071314+01:00 rh060 kernel: [20058.981970] ata3.00: configured for UDMA/100
2025-01-13T15:01:19.075238+01:00 rh060 kernel: [20058.984345] sd 4:0:0:0: [sda] Starting disk
2025-01-13T15:01:19.075240+01:00 rh060 kernel: [20058.984558] ata5.00: supports DRM functions and may not be fully accessible
2025-01-13T15:01:19.079235+01:00 rh060 kernel: [20058.989351] ata5.00: configured for UDMA/133
2025-01-13T15:01:19.091249+01:00 rh060 kernel: [20058.999602] ata5.00: Enabling discard_zeroes_data
2025-01-13T15:01:21.655274+01:00 rh060 kernel: [20061.563217] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2025-01-13T15:01:21.760159+01:00 rh060 NetworkManager[3754]: <info> [1736776881.7601] device (eth0): carrier: link connected
2025-01-13T15:01:23.235138+01:00 rh060 ntpd[3872]: IO: Listen normally on 10 eth0 10.6.6.60:123
2025-01-13T15:01:23.235168+01:00 rh060 ntpd[3872]: IO: Listen normally on 11 eth0 [fe80::6d9:f5ff:fef7:e393%2]:123
2025-01-13T15:01:23.235268+01:00 rh060 ntpd[3872]: IO: new interface(s) found: waking up resolver
Illuminated keyboard shortly goes off, comes on again, screen saver is back, PC is working.These messages made me wonder:
2025-01-13T14:38:03.015804+01:00 rh060 kernel: [18660.503010] xhci_hcd 0000:05:00.0: PM: pci_pm_freeze(): hcd_pci_suspend [usbcore] returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503027] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -16
2025-01-13T14:38:03.015805+01:00 rh060 kernel: [18660.503032] xhci_hcd 0000:05:00.0: PM: failed to freeze async: error -16The stick was present for some decryption experiments in a VBox VM I started some months ago. I never would have thought that leaving the stick connected to the Sempre adapter could cause suspend to hang. Anyhow, at least pm-hibernate now does its job, lets see how the Cinnamon based energy settings mechnism performs.
#13 Re: Off-topic » Thoughts on Pipewire » 2025-01-12 16:40:57
Just switched to Pipewire on my Daedalus workstation re-install. Works fine, easy start, same on my travelling laptop. I can't complain about any sound change or deficiency. Audacious immedialtely played my ripped CD files (wav), I can't say anything bad about quality.
Edith: pulse wasn't installed.
#14 Re: Other Issues » [SOLVED] Mounting HDD in a USB cradle » 2025-01-12 14:17:45
Yes, LVM is an additional layer. But as it looks like you have not really seen any issues for many years with it, so what? Ok it has its own terms you need to get used to like physical volume, volume group, logical volume, etc. Can be learned, there is a LVM HowTo in the internet. Just look for it. BTW: I am using LVM for many many years by now, no real issues with it.
#15 Re: Other Issues » [SOLVED] Mounting HDD in a USB cradle » 2025-01-11 21:13:28
vgchange -a y will do the job. Quote the output here please.
#16 Re: Hardware & System Configuration » [SOLVED] Entry in fstab but Authentication is still required to mount partition » 2025-01-08 17:09:12
When you write a partition table on a device no matter if its new or used already, create a new partition, format a partition, all of these are root tasks. There is no automatic permission for user access past that process.
To allow unprivileged user access to new drives/partitions, you will have to (as root again) change the ownership of the mount point in a single user case or for multiple users to create new directories on the device and assign individual user ownership with e.g. chown.
In addition, all modern desktops like Mate, Cinnamon, Gnome, KDE ... have automounter features that mount for example any USB stick with user rights to the desktop. At least for vfat, exfat drives. It becomes a bit more complicated with ntfs or Linux file systems like ext2/3/4.
You see its complex, depending on.
If you want that device LinuxDataExt-4TB to be permanently connected, I would first of all suggest to use a dedicated subdirectory under /mnt for that drive. Then it makes sense to create a fstab entry like:
Dev-UUID /mnt/xyz ext4 defaults 0 2
The 2 on the end makes sure the file system on the device is checked regularly. Nothing else is required.
In case its an external drive via USB, I do not use any fstab entry, I'll leave opening/mounting when connected to the automounter. They usually create something like /media/$USER/LinuxDataExt-4TB assuming "LinuxDataExt-4TB" is the label that is set on the device.
During the installation it is not directly possible to create/partition/include something like backup drives not really related to the system setup. That's a task for past the first successful boot of the system.
#17 Re: Installation » new installation with iso Devuan i386 Daedalus » 2025-01-07 09:35:04
Sorry, you sound like you take my comment very personally. Don't do that please. I try to help ...
I have seen these temporary failures myself every now and then. A simple repetition of the apt command worked fine for me. I never had a consistent blockage like several others. And yes, I have a mirror close by my location, but I stick to deb.devuan.org.
Some background: http://deb.devuan.org/merged does not represent a single dedicated server but stands for a list of servers all around the world that host a Devuan mirror. Somewhere on the Devuan website (you can find a link on top of this website) you can find this list:
https://www.devuan.org/get-devuan. Resolving this "round robin" scenario seems to cause issues in certain locations and with certain providers.
You have the following choices:
1.) Repeat the command until it works.
2.) Use another DNS like 8.8.8.8 or Quad Nine or anything you like.
3.) Try something like de.deb.devuan.org in your sources.list. Its not recommended by Devuan, but it may be worth a try.
4.) Select one of mirrors from the available ones and enter this into your sources.list.
Good luck
#18 Re: Installation » after the new installation, all my old entries in grub are erased! » 2025-01-06 21:19:31
Do you mean access to other operating systems? If yes that normal now ith Bookworm/Daedalus. Refer to the release notes. os-prober has been de-activated by default. To get that back you have to enable os-prober again and perform an update-grub.
#19 Re: Installation » new installation with iso Devuan i386 Daedalus » 2025-01-06 21:16:44
Why? DNS issues:
Temporary failure resolving 'deb.devuan.org'
Check your network settings and try again. Worked for me here in Germany with a German internet provider.
If it does not work, use a different DNS provider/resolver. Recently there have been several issues. Search the forum for threads.
#20 Re: Installation » [SOLVED] cannot boot netinstall iso » 2025-01-02 09:55:03
Well, a Ryzen 7700 is something pretty new. Maybe the CPU is not supported by the kernel that comes with Daedalus. The stick should boot.
Anyhow, CSM support has been removed for every new computer design past about 2020 based on a decision by the big industry protagonists. It will not come back. I also own an Acer laptop bought in 2020 that is UEFI only.
About writing the iso image to the stick: make sure you use the raw device, not any partition. Example: of=/dev/sda is correct, of=/dev/sda1 is wrong, won't work. Also make sure to use the 5.01 version.
Also Ventoy is useless since Daedalus.
Good luck.
#21 Re: Installation » [SOLVED] Sources.list hates me! » 2024-12-31 13:01:38
... the initial attempt was made as root and it came up in Libre Office Writer when moused ...
Take this as learning. Never ever attempt to modify any Linux conf or script file with anything else but a pure text editor. These kinda files are pure ASCII text, no control characters allowed but CR LF and maybe TAB. LO and like as Windows editors add characters that are not welcome in the Linux world.
Opposite to steve_v's opinion I am using geany as a gui multi-tab text editor to edit my confs and scripts as root for convenience. I am setting up a root terminal and a policy kit policy to enable to do that. When I call up geany from this root terminal I am getting all the files I ever fooled with on my system (unless I did not remove them from the list of files). This setup also allows easy copy/paste into the files.
#22 Re: Installation » [SOLVED] Sources.list hates me! » 2024-12-31 12:50:35
whatever happened to gksudo and kdsudo for elevated privileges in gui applications(i.e. mousepad, synaptic, etc.)?
gksu and so on have been replaced by pkexec and polkit policies some time ago. Somewhere in the release notes should be a note telling that gksu is depracated and removed from the distribution (inherited from Debian).
#23 Re: Hardware & System Configuration » Instructions for installing lightdm on new Devuan 5 installation? » 2024-12-30 11:07:29
Apt also provides a log, refer to /var/log/apt/history.log.
#24 Re: Freedom Hacks » Amazon mydedia » 2024-12-29 19:25:15
My private suggestion: look into free tools and devices instead of that proprietary stuff. You will be much happier.
I have a file server in the basement where I store my music files. And I use Audacious and a play list to play that music over my network on my PC.
#25 Re: Hardware & System Configuration » Instructions for installing lightdm on new Devuan 5 installation? » 2024-12-29 10:29:31
The command I gave installs all required dependencies. I never drilled any deeper. You may look them up with Synaptics if you like.
To the conf file: the default is that user names are hidden. You need to enable that line and set it to false.
BTW: the conf file is confusing. In the beginning there is a lot of comments to all the settings. The relevant line is some way down the file under the [seats] section.
Board footer
