You are not logged in.
- Topics: Active | Unanswered
#176 Re: Installation » [SOLVED] devuan netinstall iso auto selects installation media for partitioning » 2024-05-29 17:45:20
I think I know where your problem comes from. For Guided Partitioning, do not use the option "Largest free space" but try "Complete disk" (maybe the wording in the installer is slightly different, I did use the German language).
When you select "Complete disk" you are getting asked which device to use for installation.
To avoid later disappointment I vote for manual partitioning.
Cook recipe:
Select your HD (sda) with the cursor and apply a GPT partition table. I think the installer does that automagically on efi installs.
Select the free space and add 1024M as new partition, use as EFI system partition.
Select the remaining free space and add 8192M, use as swap.
Select the remaining free space and add 32738M, use as ext4, mount point /
Select the remaining free space and add the rest, use as ext4, mount point /home
Good luck.
#177 Re: Installation » [SOLVED] devuan netinstall iso auto selects installation media for partitioning » 2024-05-29 11:46:22
I tried expert install and it too shows both sda and sdb on the partitioning page and there is no way to deselect sdb (installation usb)
You will always be shown all detected devices, including the installation stick. That does not mean they are all used.
As I said, I don't trust any of the automatisms. You should use manual partitioning, normal or expert mode does not matter. Is that an efi PC or do you want a legacy installation? Encrypted or standard? How much RAM is available?
#178 Re: Installation » [SOLVED] devuan netinstall iso auto selects installation media for partitioning » 2024-05-29 11:17:52
How to edit topic?
Refer to my previous post #9.
I guess you are using Guided Partitioning. Have you got sufficient free space on your sda drive? Is this a dual boot possibly?
It would make sense if you would be a bit more responsive and open with the information you are disclosing here.
#179 Re: Installation » [SOLVED] devuan netinstall iso auto selects installation media for partitioning » 2024-05-29 08:16:32
To correct your own contributions: there is an "Edit" button inside the frame of your entries. In the initial post you can also edit the headline.
What the release is concerned, do you want to use Daedalus, or Excalibur (Testing) or Chimaera or anything older?
I am not aware about some "official" guide for manual partitioning. On the Devuan website there are installation guides with screenshots, but they use guided partitioning there. You might look at Debian, if they have some document. Or search for a video on YT. It does not matter if Devuan or Debian, the procedure is the same, and the chance to find something or Debian is much higher.
#180 Re: Installation » [SOLVED] devuan netinstall iso auto selects installation media for partitioning » 2024-05-29 07:37:35
Would you please correct the typo in your headline? The distro is Devuan, not devaun.
Well, lets start with determining what we are talking about. There are five or six netinstalls around. Which release do you talk about? Where did you get the iso from?
Then: standard installation or expert install?
Guided partitioning or manual partitioning?
I've been through some installs with Daedalus netinstall recently, no problems in expert mode with manual partitioning. I dislike using any automatism, they all have their limitations and disadvantages.
#181 Re: Other Issues » desktop dress-up » 2024-05-28 12:39:42
You can put images into /usr/share/backgrounds and then use them as background image for your desktop.
#182 Hardware & System Configuration » [SOLVED] Suspend lockup lately » 2024-05-24 11:47:16
- rolfie
- Replies: 18
On 6.6. and 6.7 kernels from backports I see frequent lockups when the computer goes into suspend.
Update: its not only the backports kernels, also the stock kernel does it.
Involved HW: X570 main board, Ryzen 9 5900X 12-core CPU, RX6700XT graphics, an illuminated keyboard.
Involved SW: Devuan Daedalus in efi mode, Lighdm/Cinnamon as DE, linux-image-amd64 from backports is installed.
In the Engergy Settings the monitor is blanked after 15m, suspend starts at 20m. That setting was executed as desired usually. When suspend starts the keyboard lights go off and the power on LED on the case starts to blink. I can wake up the PC by using any key on the keyboard which happens pretty fast. Mouse movements do nothing. When I am away from the PC for longer than half an hour or so, the system goes into hibernate, don't know exactly how long the delay really is. In this case wake up performs a reboot, I see the bios screen, and finally I am back on the user login and find what I have left after logging in. Used to work fine with some rare exceptions with the early backports kernels.
With the 6.6. and 6.7 kernels I am frequently faced with a PC that is completely locked, a hard reset is required to get it back to work. The monitor LED shows no input signal, the keyboard light still are on, the PC does not react to any key, Numlock isn't working. For the time being I have disabled suspend/hibernate.
I have digged out about 900 lines from the syslog that show that there is a problem with the GPU. Here are the first 100 lines that end in a crash dump. Comments?
BTW: Is there something like a NoPaste area for longer outputs like there is on the German Debian forum?
2024-05-22T10:57:06.865339+02:00 rh060 dbus-daemon[5722]: [session uid=1000 pid=5720] Successfully activated service 'org.cinnamon.ScreenSaver'
2024-05-22T10:57:06.898671+02:00 rh060 x-session-manager[5684]: WARNING: t+5027,65597s: Detected that screensaver has appeared on the bus
2024-05-22T11:02:06.825480+02:00 rh060 ModemManager[4834]: <info> [sleep-monitor-systemd] system is about to suspend
2024-05-22T11:02:06.825488+02:00 rh060 NetworkManager[4816]: <info> [1716368526.8254] manager: sleep: sleep requested (sleeping: no enabled: yes)
2024-05-22T11:02:06.832353+02:00 rh060 kernel: [ 5974.632834] igb 0000:06:00.0 eth0: left promiscuous mode
2024-05-22T11:02:06.900347+02:00 rh060 kernel: [ 5974.697940] PM: suspend entry (deep)
2024-05-22T11:02:06.912345+02:00 rh060 kernel: [ 5974.712957] Filesystems sync: 0.015 seconds
2024-05-22T11:02:12.547957+02:00 rh060 kernel: [ 5974.713615] Freezing user space processes
2024-05-22T11:02:12.548013+02:00 rh060 kernel: [ 5974.715469] Freezing user space processes completed (elapsed 0.001 seconds)
2024-05-22T11:02:12.548014+02:00 rh060 kernel: [ 5974.715471] OOM killer disabled.
2024-05-22T11:02:12.548014+02:00 rh060 kernel: [ 5974.715472] Freezing remaining freezable tasks
2024-05-22T11:02:12.548016+02:00 rh060 kernel: [ 5974.716849] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
2024-05-22T11:02:12.548017+02:00 rh060 kernel: [ 5974.716866] printk: Suspending console(s) (use no_console_suspend to debug)
2024-05-22T11:02:12.548017+02:00 rh060 kernel: [ 5974.793519] sd 9:0:0:0: [sdd] Synchronizing SCSI cache
2024-05-22T11:02:12.548017+02:00 rh060 kernel: [ 5974.795481] ata10.00: Entering standby power mode
2024-05-22T11:02:12.548018+02:00 rh060 kernel: [ 5974.801022] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
2024-05-22T11:02:12.548018+02:00 rh060 kernel: [ 5974.801046] sd 8:0:0:0: [sdb] Synchronizing SCSI cache
2024-05-22T11:02:12.548018+02:00 rh060 kernel: [ 5974.801046] sd 5:0:0:0: [sda] Synchronizing SCSI cache
2024-05-22T11:02:12.548019+02:00 rh060 kernel: [ 5974.801338] ata9.00: Entering standby power mode
2024-05-22T11:02:12.548020+02:00 rh060 kernel: [ 5974.802907] ata6.00: Entering standby power mode
2024-05-22T11:02:12.548020+02:00 rh060 kernel: [ 5974.804526] ata5.00: Entering standby power mode
2024-05-22T11:02:12.548021+02:00 rh060 kernel: [ 5974.925255] xhci_hcd 0000:05:00.0: PM: pci_pm_suspend(): hcd_pci_suspend+0x0/0x20 [usbcore] returns -16
2024-05-22T11:02:12.548023+02:00 rh060 kernel: [ 5974.925280] xhci_hcd 0000:05:00.0: PM: dpm_run_callback(): pci_pm_suspend+0x0/0x170 returns -16
2024-05-22T11:02:12.548023+02:00 rh060 kernel: [ 5974.925287] xhci_hcd 0000:05:00.0: PM: failed to suspend async: error -16
2024-05-22T11:02:12.548023+02:00 rh060 kernel: [ 5975.432312] PM: Some devices failed to suspend, or early wake event detected
2024-05-22T11:02:12.548024+02:00 rh060 kernel: [ 5975.432975] [drm] PCIE GART of 512M enabled (table at 0x0000008000300000).
2024-05-22T11:02:12.548024+02:00 rh060 kernel: [ 5975.432995] [drm] PSP is resuming...
2024-05-22T11:02:12.548025+02:00 rh060 kernel: [ 5975.441679] nvme nvme0: Shutdown timeout set to 10 seconds
2024-05-22T11:02:12.548025+02:00 rh060 kernel: [ 5975.442611] nvme nvme0: 8/0/0 default/read/poll queues
2024-05-22T11:02:12.548026+02:00 rh060 kernel: [ 5975.442907] nvme nvme0: Ignoring bogus Namespace Identifiers
2024-05-22T11:02:12.548026+02:00 rh060 kernel: [ 5975.466719] nvme nvme1: 31/0/0 default/read/poll queues
2024-05-22T11:02:12.548027+02:00 rh060 kernel: [ 5975.467043] [drm] reserve 0xa00000 from 0x82fd000000 for PSP TMR
2024-05-22T11:02:12.548027+02:00 rh060 kernel: [ 5975.599145] amdgpu 0000:0c:00.0: amdgpu: RAS: optional ras ta ucode is not available
2024-05-22T11:02:12.548028+02:00 rh060 kernel: [ 5975.621369] amdgpu 0000:0c:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
2024-05-22T11:02:12.548028+02:00 rh060 kernel: [ 5975.621371] amdgpu 0000:0c:00.0: amdgpu: SMU is resuming...
2024-05-22T11:02:12.548029+02:00 rh060 kernel: [ 5975.621374] amdgpu 0000:0c:00.0: amdgpu: smu driver if version = 0x0000000e, smu fw if version = 0x00000012, smu fw program = 0, version = 0x00413900 (65.57.0)
2024-05-22T11:02:12.548029+02:00 rh060 kernel: [ 5975.621377] amdgpu 0000:0c:00.0: amdgpu: SMU driver if version not matched
2024-05-22T11:02:12.548030+02:00 rh060 kernel: [ 5975.621449] amdgpu 0000:0c:00.0: amdgpu: use vbios provided pptable
2024-05-22T11:02:12.548030+02:00 rh060 kernel: [ 5975.909281] ata10: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-05-22T11:02:12.548031+02:00 rh060 kernel: [ 5975.909289] ata10.00: Entering active power mode
2024-05-22T11:02:12.548031+02:00 rh060 kernel: [ 5975.909458] ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-05-22T11:02:12.548032+02:00 rh060 kernel: [ 5975.909459] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2024-05-22T11:02:12.548033+02:00 rh060 kernel: [ 5975.909464] ata6.00: Entering active power mode
2024-05-22T11:02:12.548033+02:00 rh060 kernel: [ 5975.909480] ata9: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-05-22T11:02:12.548034+02:00 rh060 kernel: [ 5975.909487] ata9.00: Entering active power mode
2024-05-22T11:02:12.548034+02:00 rh060 kernel: [ 5975.909492] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
2024-05-22T11:02:12.548034+02:00 rh060 kernel: [ 5975.909503] ata5: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
2024-05-22T11:02:12.548035+02:00 rh060 kernel: [ 5975.909511] ata5.00: Entering active power mode
2024-05-22T11:02:12.548035+02:00 rh060 kernel: [ 5975.910024] ata5.00: supports DRM functions and may not be fully accessible
2024-05-22T11:02:12.548035+02:00 rh060 kernel: [ 5975.910229] ata10.00: supports DRM functions and may not be fully accessible
2024-05-22T11:02:12.548036+02:00 rh060 kernel: [ 5975.910252] ata6.00: supports DRM functions and may not be fully accessible
2024-05-22T11:02:12.548036+02:00 rh060 kernel: [ 5975.911149] ata10.00: supports DRM functions and may not be fully accessible
2024-05-22T11:02:12.548037+02:00 rh060 kernel: [ 5975.911186] ata6.00: supports DRM functions and may not be fully accessible
2024-05-22T11:02:12.548037+02:00 rh060 kernel: [ 5975.911861] ata10.00: configured for UDMA/133
2024-05-22T11:02:12.548037+02:00 rh060 kernel: [ 5975.911920] ata6.00: configured for UDMA/133
2024-05-22T11:02:12.548038+02:00 rh060 kernel: [ 5975.912293] ata4.00: configured for UDMA/133
2024-05-22T11:02:12.548038+02:00 rh060 kernel: [ 5975.914896] ata3.00: configured for UDMA/100
2024-05-22T11:02:12.548039+02:00 rh060 kernel: [ 5975.915152] ata5.00: supports DRM functions and may not be fully accessible
2024-05-22T11:02:12.548039+02:00 rh060 kernel: [ 5975.919948] ata5.00: configured for UDMA/133
2024-05-22T11:02:12.548040+02:00 rh060 kernel: [ 5975.930160] ata5.00: Enabling discard_zeroes_data
2024-05-22T11:02:12.548040+02:00 rh060 kernel: [ 5978.356220] ata9.00: configured for UDMA/133
2024-05-22T11:02:12.548040+02:00 rh060 kernel: [ 5980.329904] amdgpu 0000:0c:00.0: amdgpu: SMU: I'm not done with your previous command: SMN_C2PMSG_66:0x00000036 SMN_C2PMSG_82:0x00000000
2024-05-22T11:02:12.548041+02:00 rh060 kernel: [ 5980.329906] amdgpu 0000:0c:00.0: amdgpu: RunDcBtc failed!
2024-05-22T11:02:12.548041+02:00 rh060 kernel: [ 5980.329907] amdgpu 0000:0c:00.0: amdgpu: Failed to setup smc hw!
2024-05-22T11:02:12.548041+02:00 rh060 kernel: [ 5980.329908] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <smu> failed -62
2024-05-22T11:02:12.548042+02:00 rh060 kernel: [ 5980.330026] amdgpu 0000:0c:00.0: amdgpu: amdgpu_device_ip_resume failed (-62).
2024-05-22T11:02:12.548042+02:00 rh060 kernel: [ 5980.330027] amdgpu 0000:0c:00.0: PM: dpm_run_callback(): pci_pm_resume+0x0/0xf0 returns -62
2024-05-22T11:02:12.548042+02:00 rh060 kernel: [ 5980.330031] amdgpu 0000:0c:00.0: PM: failed to resume async: error -62
2024-05-22T11:02:12.548043+02:00 rh060 kernel: [ 5980.330604] igb 0000:06:00.0 eth0: igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
2024-05-22T11:02:12.548043+02:00 rh060 kernel: [ 5980.348488] OOM killer enabled.
2024-05-22T11:02:12.552348+02:00 rh060 kernel: [ 5980.348490] Restarting tasks ... done.
2024-05-22T11:02:12.552350+02:00 rh060 kernel: [ 5980.351845] random: crng reseeded on system resumption
2024-05-22T11:02:12.552351+02:00 rh060 kernel: [ 5980.351849] PM: suspend exit
2024-05-22T11:02:12.552351+02:00 rh060 kernel: [ 5980.351907] PM: suspend entry (s2idle)
2024-05-22T11:02:12.556342+02:00 rh060 kernel: [ 5980.355931] amdgpu: Move buffer fallback to memcpy unavailable
2024-05-22T11:02:12.560343+02:00 rh060 kernel: [ 5980.360945] snd_hda_intel 0000:0c:00.1: Refused to change power state from D0 to D3hot
2024-05-22T11:02:32.570256+02:00 rh060 kernel: [ 5980.366015] Filesystems sync: 0.014 seconds
2024-05-22T11:02:32.570269+02:00 rh060 kernel: [ 5980.366280] Freezing user space processes
2024-05-22T11:02:32.570340+02:00 rh060 kernel: [ 5982.489672] igb 0000:06:00.0: exceed max 2 second
2024-05-22T11:02:32.570344+02:00 rh060 kernel: [ 5990.601623] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, signaled seq=5850, emitted seq=5852
2024-05-22T11:02:32.570345+02:00 rh060 kernel: [ 5990.601949] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process pid 0 thread pid 0
2024-05-22T11:02:32.570346+02:00 rh060 kernel: [ 5990.602173] amdgpu 0000:0c:00.0: amdgpu: GPU reset begin!
2024-05-22T11:02:32.570350+02:00 rh060 kernel: [ 5990.602373] amdgpu 0000:0c:00.0: amdgpu: Failed to disallow df cstate
2024-05-22T11:02:32.570350+02:00 rh060 kernel: [ 5990.906203] ------------[ cut here ]------------
2024-05-22T11:02:32.570351+02:00 rh060 kernel: [ 5990.906204] WARNING: CPU: 3 PID: 11 at drivers/gpu/drm/amd/amdgpu/amdgpu_irq.c:615 amdgpu_irq_put+0x49/0x70 [amdgpu]
2024-05-22T11:02:32.570352+02:00 rh060 kernel: [ 5990.906320] Modules linked in: qrtr nct6775 nct6775_core hwmon_vid lm92 vboxnetflt(OE) vboxnetadp(OE) vboxdrv(OE) parport_pc ppdev lp parport nfsd auth_rpcgss nfs_acl nfs lockd grace fscache netfs sunrpc nls_ascii nls_cp437 vfat fat pktcdvd amdgpu drm_exec amdxcp drm_buddy snd_hda_codec_realtek intel_rapl_msr gpu_sched intel_rapl_common snd_hda_codec_generic drm_suballoc_helper snd_hda_codec_hdmi edac_mce_amd drm_display_helper kvm_amd cec snd_hda_intel rc_core snd_intel_dspcfg drm_ttm_helper snd_intel_sdw_acpi kvm ttm snd_hda_codec drm_kms_helper snd_hda_core eeepc_wmi asus_wmi joydev asus_ec_sensors evdev snd_hwdep irqbypass battery drm snd_pcm ledtrig_audio sparse_keymap platform_profile snd_timer sp5100_tco rfkill snd rapl video pcspkr wmi_bmof mxm_wmi watchdog efi_pstore acpi_cpufreq k10temp soundcore ccp button efivarfs ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod hid_generic usbhid crc32_pclmul hid crc32c_intel sg uas ghash_clmulni_intel sr_mod sha512_ssse3 usb_storage sd_mod cdrom sha256_ssse3
2024-05-22T11:02:32.570354+02:00 rh060 kernel: [ 5990.906380] sha1_ssse3 nvme ahci nvme_core xhci_pci libahci t10_pi xhci_hcd libata crc64_rocksoft_generic crc64_rocksoft aesni_intel crc_t10dif igb usbcore crct10dif_generic scsi_mod crypto_simd crct10dif_pclmul cryptd i2c_algo_bit crc64 i2c_piix4 scsi_common dca usb_common crct10dif_common wmi
2024-05-22T11:02:32.570357+02:00 rh060 kernel: [ 5990.906398] CPU: 3 PID: 11 Comm: kworker/u64:0 Tainted: G OE 6.6.13+bpo-amd64 #1 Debian 6.6.13-1~bpo12+1
2024-05-22T11:02:32.570357+02:00 rh060 kernel: [ 5990.906400] Hardware name: System manufacturer System Product Name/PRIME X570-PRO, BIOS 5013 03/22/2024
2024-05-22T11:02:32.570358+02:00 rh060 kernel: [ 5990.906402] Workqueue: amdgpu-reset-dev drm_sched_job_timedout [gpu_sched]
2024-05-22T11:02:32.570359+02:00 rh060 kernel: [ 5990.906407] RIP: 0010:amdgpu_irq_put+0x49/0x70 [amdgpu]
2024-05-22T11:02:32.570360+02:00 rh060 kernel: [ 5990.906518] Code: 48 8b 4e 10 48 83 39 00 74 2c 89 d1 48 8d 04 88 8b 08 85 c9 74 14 f0 ff 08 b8 00 00 00 00 74 05 e9 9c d0 d2 d1 e9 57 fd ff ff <0f> 0b b8 ea ff ff ff e9 8b d0 d2 d1 b8 ea ff ff ff e9 81 d0 d2 d1
2024-05-22T11:02:32.570361+02:00 rh060 kernel: [ 5990.906519] RSP: 0018:ffffb6c780147c88 EFLAGS: 00010246
2024-05-22T11:02:32.570361+02:00 rh060 kernel: [ 5990.906521] RAX: ffff8c79811eaaa8 RBX: ffff8c798ba00000 RCX: 0000000000000000
2024-05-22T11:02:32.570362+02:00 rh060 kernel: [ 5990.906522] RDX: 0000000000000000 RSI: ffff8c798ba27988 RDI: ffff8c798ba00000
2024-05-22T11:02:32.570362+02:00 rh060 kernel: [ 5990.906523] RBP: ffff8c798ba00000 R08: 00000000000395c0 R09: 0000000000000006
2024-05-22T11:02:32.570363+02:00 rh060 kernel: [ 5990.906524] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000001050
2024-05-22T11:02:32.570364+02:00 rh060 kernel: [ 5990.906525] R13: ffff8c798ba414c8 R14: ffff8c7a588d7800 R15: 0000000000000000
2024-05-22T11:02:32.570364+02:00 rh060 kernel: [ 5990.906526] FS: 0000000000000000(0000) GS:ffff8c886eac0000(0000) knlGS:0000000000000000
2024-05-22T11:02:32.570364+02:00 rh060 kernel: [ 5990.906527] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
2024-05-22T11:02:32.570365+02:00 rh060 kernel: [ 5990.906528] CR2: 00007f42e27fe990 CR3: 00000002165c0000 CR4: 0000000000750ee0
2024-05-22T11:02:32.570365+02:00 rh060 kernel: [ 5990.906529] PKRU: 55555554#183 Re: Installation » Install from Ventoy » 2024-05-20 21:05:10
I am sorry, I just reported my recent observation which took me as surprise. I am a user with no real insight how things really work together.
#184 Re: Installation » [SOLVED] No exit from sleep after devuan installation » 2024-05-20 20:53:01
Maybe it would make sense to first check the basics: the Engergy Settings on your desktop?
Which DE are you using? How have you configured the Energy Settings?
#185 Re: Installation » Install from Ventoy » 2024-05-20 08:45:03
Update with an interesting observation on a Daedalus 5.0.1 netinstall: had to use the resuce mode, a legacy install. The Devuan preamble is displayed and then the same error message that appears in Ventoj:
mount: mounting LABEL=DEVUAN501 on /cdrom failed: No such file or directory
506635 blocks shows up.
After some thinking then the language selection menu pops up. This is repeatable.
@ralph ronnquist: maybe this observation is a handle to fix this issue?
#186 Re: Off-topic » [SOLVED] Installing devuan on vps » 2024-05-13 11:38:34
You obviously try to pull Bullyeye packages instead of Chimaera packages.
Check your sources.list, make sure only Devuan Chimaera is active. And also check /etc/apt/sources.list.d again if there are entries present that call for Debian.
Then perform an apt update before trying to install any packages.
#187 Re: Installation » [SOLVED] Save an installation protocol » 2024-05-11 10:12:08
Thanks for the feedback, I'll dig through that.
Anyhow, I am a step further today when I was yesterday. New questions arise now, new post to be written. I will close this one.
BTW: installation protocol in my understanding is a listing of commands and outputs of the system as you get on F4, just all logged into a file for later analysis.
#188 Re: Installation » Irrational Diff in adm user PERMISSIONS between LXQt and others » 2024-05-11 10:09:07
Installed twice before - once with User as admin and root - without automatic login and arrested at tty and installed again User with Sudo as Root
The normal Debian/Devuan way is to establish a root account, and a normal user account. Assign a root password during installation different from the user password. Then you work normally as user, and do administrative stuff as root in a root terminal. This way you do not need this sudo stuff.
Neither time have I been able to control change add etc involving 2nd and 3rd users ( which i HAD intended to use separately for each desktop).
Even with a cli installation without any desktop, the command line tools for adding/modyfing users and groups will be present (see Delgados response). Downside: you need to log-in in a root terminal and do the work by typing.
Depending on the desktop you will find one or the other graphical tool, e.g. Cinnamon brings a limited user/group graphical tool.
Gnome-system-tools is the more convienent tool, I also add this tool to my installations sort of at the end of the fine tuning.
BTW: For a multiuser-installation I would go away from slim (which isn't maintained any more anyhow) and use lightdm instead. Or sddm for KDE, which isn't my personal preference.
And it is not recognizing my data drives which have ALWAYS been instantly recognized and accessible no matter who is logged in, what desktop.
The desktop permissions are typically set by policykit. Each desktop should come with some set of rules to allow for user access to removable drives in combination with group permissions.
#189 Installation » [SOLVED] Save an installation protocol » 2024-05-10 15:41:41
- rolfie
- Replies: 3
I tried twice now to install a Daedalus encrypted w/o separate /boot in a luks container holding a LVM for / and swap. Both legacy as efi installs fail from the 501 netinstall when writing the grub. Both in a Virtualbox VM.
With some poking around I managed to open a console with messages, I guess it was right CTRL F4. These messages do not really tell whats wrong, at least I can't see the reason for failure. I'd like to understand what is going wrong.
As far as I remember somebody told me that there also is some sort of protocol which I possibly could save. How do I get there?
#190 Re: Hardware & System Configuration » Error building nVidia module after kernel update in Chimaera » 2024-05-09 15:28:42
Normal process, new stuff goes into sid at first, then eventually in testing, later into proposed-updates or backports.
239 is not in backports but in proposed-updates!!!
#191 Re: Hardware & System Configuration » Error building nVidia module after kernel update in Chimaera » 2024-05-09 11:32:53
Yes, I have seen a similar topic in the German Debian Forum. There seems to be a new version 239 of the 470 driver package dripping down from sid. As far as I understood the discussion the new package is in proposed updates.
#192 Re: Hardware & System Configuration » [SOLVED] python3-apt stuck on my Excalibur VMs » 2024-05-07 21:02:07
Thats why I am running Excalibur in VMs. Will keep that for a while ...
#193 Re: Hardware & System Configuration » [SOLVED] python3-apt stuck on my Excalibur VMs » 2024-05-07 18:12:38
Looks like I wasn't patient enough. Running another update this evening fixed the issue. python3-apt has been upgraded in both VMs now, no more hold back packages.
#194 Hardware & System Configuration » [SOLVED] python3-apt stuck on my Excalibur VMs » 2024-05-07 16:16:18
- rolfie
- Replies: 5
Since some weeks I am getting the info that python3-apt is hold back from upgrading. I was waiting for a solution over time which did not happen.
# apt-mark unhold python3-apt tells me that the hold mark already has been removed.
Got two encrypted VMs, installed Dec last year, one with Mate, one with Cinnamon. Both show the same problem, both are up-to-date.
What can I do to solve the issue?
#195 Re: Hardware & System Configuration » How to enter root password in bash script? » 2024-05-04 21:38:13
username ALL=(root) NOPASSWD: /usr/bin/setpci
#196 Re: Other Issues » Will I Need to Do Anything Special if I switch Motherboards? » 2024-05-04 20:55:07
Don't think you will have many issues. SATA2 or SATA3 does not really matter, CPUs are of same brand and similar generation. The only issue could be graphics, especially NVidea. But if you are running Chimaera or Daedalus, the old stuff should be supported as far as integrated graphics is concerned.
You should be able to plug in the drive into the new MB and it should work.
#197 Re: Installation » devuan_chimaera_4.0.0_amd64_desktop.iso installation freezes » 2024-04-26 16:57:40
@fsmithred: never tried this yet because I wanted to used luks2. Is the grub as shipped with Daedalus now able to decipher luks2?
#198 Re: Installation » devuan_chimaera_4.0.0_amd64_desktop.iso installation freezes » 2024-04-26 15:45:17
Yes, the traditional setup requires an unencrypted /boot partition. I use that setup. In the encrypted partition I do setup a LVM with 2 logical devices for / and swap. /home always is on a separate device, except for in a VM.
There is no need for special "early short command line detour for device mapping". You go through the installer step by step, and everything thats needed is prepared, no matter if legacy or efi installs.
With Arch Linux I could get away without that, but that requires a grub that can decipher luks2 and I think some tweaks inside of systemd.
#199 Re: Installation » devuan_chimaera_4.0.0_amd64_desktop.iso installation freezes » 2024-04-26 11:11:37
Just my two cents: FDE works fine when pre-partitioning with a GParted Live and manual partitioning in the installer. Valid all along from ASCII to Daedalus.
#200 Re: Installation » devuan_chimaera_4.0.0_amd64_desktop.iso installation freezes » 2024-04-26 10:01:16
You might consider that Chimaera even is too old for that laptop. Chimaera is oldstable anyhow, Daedalus is stable.
Board footer
