You are not logged in.
- Topics: Active | Unanswered
#51 Re: Off-topic » troubled of linux behaviour (or is it devuan=?) » 2026-08-05 17:29:29
actually , idont know what the program is doing in the background, aside from apparently computeing;
but if it "survives" a logout, that isn*t a good sign, somehow, sisuppose.
makes one think of running task in background where actually the computer should sit quite still;
such continiuty features, if not advertised, are absolutely unwanted, at least in my book.
but possibly, sinceh the compile has just been matched up (it is supposed to run on "systemd" systems), maybe it got botched to some degree since did only lwave awasy "libsystemd-dev" and the rest is as planned for those OS;
but apart this flaw, it seem to function fine;
or, the mate-desktop has more flaws, than one might expect (the big one seems to be the caja-filemanager).
#52 Off-topic » troubled of linux behaviour (or is it devuan=?) » 2026-08-05 02:19:36
- kapqa
- Replies: 11
Hello ,
please forgive another suspicious post ]
but maybe someone of you can relate and offer an explanation ~
now this eems a recent behaviour,
but maybe not
was running a program in terminal, (not via sudo or the like)
and effecting "log-out"
only to "log-in" but under the same user-name to find out that the program apparently was still running.
(was blocking the resource trying to access again)
effectively until reboot.
anomalie two:
noticed that firefox someimes dows downloads, but not finishes them, (they remain unfinished in download window, and the sand-time-clock is still running)
(even after closing and reopening firefox) (the download still hangs) (no way to "close" download =)Z> effectively unless reboot.
well, i am not used to such behaviour on computer, so it kept me puyyzzled.
#53 Re: Installation » [SOLVED] Installation Problem after selecting Language and Country » 2026-08-03 08:30:58
well, must have gooten it all wrong, sorry for the previous post;
tried again today:
with ventoy-linux (./VentoyGUI.x86_64) the netinstall went through with both MBR and GPT
with ventoy-windows (Ventoy2Disk) the netinstall went through with MBR and NOT with GPT!
if i used GPT (via Ventoy2Disk), receive the same error you posted earliert
"Incorrect installation media detected"
"The detected media cannot be used for installation."
so i suggest you try again format with Ventoy and let use partition Style "MBR" which is standard setting for Ventoy.
that should work.
#54 Re: Installation » [SOLVED] Installation Problem after selecting Language and Country » 2026-08-02 17:35:43
if you still have doubts, you can press "del" for enter bIOS , and then "F5" or similar for default settings, press "F10" for savings setting, that should settle it for you.
Good luck.
Edit: if you really want to use ventoy, then there is option "partition style" in VentoyMenu > it should be set to "GPT" for coexistance with Win11 i suppose; have checked this just yet, on linux there exist such option. otherwise, with standard-setting "MBR" you run into conflict, most probably. but windows-ventoy might handle it differently. just a warning.
Edit2: just tested this with excalibur.netinstall-iso. with ventoy:
when using standard settings (mbr) > it would fail exactly at the point you described;
when formatting with partition style (gpt) > the netinstall would process, you could proceed.
please disregard the upper portion with "default settings" then; you should set most probably BIOS as described earlier, with SecureBoot (ON or OFF) and if (ON) with "Custom" setting; or the like.
#55 Re: Hardware & System Configuration » [SOLVED] upgrade succesful .. or not? (systemd) » 2026-07-31 22:37:07
yeah, might check aout that.
in the meantime , have still strange tidings with upgrades.
now it says "upgrading" , but actually wants to remove it.
(nala removes it straight away; apt-upgrade upgrade first, but says it no longer needed?)
sudo apt upgrade
The following packages were automatically installed and are no longer required:
fonts-glyphicons-halflings libgme0:i386 libsrt1.5-gnutls:i386
fonts-roboto-unhinted libjs-iscroll libssh-4:i386
libaacs0:i386 libkissfft-float131 libswscale7
libavfilter9 libmbedcrypto16:i386 libtinyxml2.6.2v5
libavformat60 libmicrohttpd12t64 libudfread0:i386
libavformat61:i386 libnfs16 libvidstab1.2
libbdplus0:i386 libnorm1t64:i386 libvorbisfile3:i386
libbluray2:i386 libopenmpt0t64:i386 libwayland-client++1
libchromaprint1:i386 libpcre3 libwayland-cursor++1
libcjson1:i386 libpgm-5.3-0t64:i386 libwayland-egl++1
libcrossguid0 libpostproc57 libzmq5:i386
libdate-tz3 librabbitmq4:i386 python3-pycryptodome
libdvdnav4:i386 librist4:i386 wine-devel
libdvdread8t64:i386 librubberband3 wine-devel-amd64
libfdk-aac2t64 libshairplay0 wine-devel-i386:i386
libfftw3-single3:i386 libsodium23:i386
libfstrcmp0 libspdlog1.15
Use 'sudo apt autoremove' to remove them.Upgrading:
librewolf wine-devel wine-devel-amd64 wine-devel-i386:i386
#56 Re: Hardware & System Configuration » [SOLVED] LibreOffice Calc 7.4.7.2 - Slow / laggy scrolling » 2026-07-31 12:18:20
well, i remember my first "suite" °netscape navigator° since then been fond ot it, now it takes two for the tango, and even 1 application alone able to bring the computer to a crawl (thunderbird or firefox, you pick) - seamonkey or iceape would still be favorite, but they are not doing everything, always, sometimes are blocked either, but digress.
my office capabilities stalled long time ago; will see if can catch up to latest advancements. maybe not even needed, after all.
#57 Re: Hardware & System Configuration » Huawei Freebuds » 2026-07-31 08:38:11
rubbish never comes for free.
#58 Re: Hardware & System Configuration » [SOLVED] LibreOffice Calc 7.4.7.2 - Slow / laggy scrolling » 2026-07-31 08:36:49
have preferred the "openoffice" over the libreoffice, but have to admit that the libreoffice has progressed some more and is more advanced;
if you want better performance , you could always try install openoffice next to it and see if you like to differentiate.
there are guides no how to install them completely in parallel, that should still function , too, via the .debs (complete, with menu-integration).
#59 Re: Installation » [SOLVED] Installation Problem after selecting Language and Country » 2026-07-31 08:20:15
as handy as rufus can be , it has issues with linux.iso sometimes, no doubt (if you have set to "MBR" > you need to make afterwards to boot from "UEFI" , someimes it nned to load to download from internet addtiional syslinux etc); ventoy should format for you the usb-stick, no questions asked, but if you have a strange usb-stick, you could always prepare it first via (diskpart > list disk > select disk > clean) just to make sure that ventoy has no trouble formatting;
but if you dont have a DVD drive ad your disposal (which would be a pity for a new computer, of course), you could also use "rpi-imager" or balena etcher, as suggested, and it should get you there. rpi-imager has helped me out where others (also baledna) have failed.
if you have the proper BIOS setting in place, a DVD is the best bet, period. it is slower, takes sometimes long to load, but is quite impeccable for desired usecase.
edit> since have similar similar mainboard (b450m, msi-click-bios) took the freedom to lookup the setting (have windows 11, devuan 6, [ubuntu+] installed) Z here under Windoes OS Configuration ~ {UEFI} ~ {SecureBoot}[Enabled] ~ {SecureBootMode}[Custom]
#60 Re: Installation » [SOLVED] Installation Problem after selecting Language and Country » 2026-07-30 20:21:02
excalibur is picky, you could try a dvd (burn .netinstall or full-iso to dvd) + be amazed.
it should function.
#61 Re: Hardware & System Configuration » [SOLVED] upgrade succesful .. or not? (systemd) » 2026-07-30 17:26:04
thanks , i suppose the upgraded files theat are being pulled like @libpipewire/systemd or something *just one catch
is due to being automatically linked with the debian.system since i had disabled both pulseaduio.pipewire to the best of instructions received.
nothing to be concerned of, i guess, and thanks for the }requiredP{ reading.
much appreciated.
#62 Hardware & System Configuration » [SOLVED] upgrade succesful .. or not? (systemd) » 2026-07-30 10:33:48
- kapqa
- Replies: 6
Hello ,
have discovered the tool "nala" for update/upgrade and trying it out.
today it took some time to finish and left me with this message
Fetched 147.0 MB in 23s (6.4 MB/s)
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│✔ Running dpkg … ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 100.0% • 0:00:00 • 539/539│
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯Warning: unable to delete old directory '/lib/systemd/system': Directory not empty
Warning: unable to delete old directory '/lib/systemd': Directory not empty
Finished Successfully
may question:
am i allowed to delete those folders?
have seen that the upgrades pull quite some packages with "systemd" in namespace in for devuan 7.0 , but have taken notice of them all.
(most will probably be beningn?)
thank you.
#63 Re: Installation » [SOLVED] Installation Problem after selecting Language and Country » 2026-07-29 07:59:15
if you use windows 11 you can use "rufus" to make a bootable copy of devuan installer onto usb. if you have a dvd drive you could burn the iso onto dvd-(rw), that should function best. if it does not function over dvd, then most certainly a BIOS setting is wrong (can happen out of the gate, like "secure boot is enabled > need to change like if you want it enabled to "custom" instead of "windows uefi") etc.
#64 Re: Hardware & System Configuration » Radeon HD 5770 - free driver does not detect refresh rates above 60Hz » 2026-07-28 17:11:15
since was boasting fruitlessly about these card,
have since remembered shis sharedware, which is very handy on the computer )macinjack(
it maybe wont crank up the refresh rate, but atleast on the monitor here (mostly legacy format) it can operate other resoltuions which are native or not native? on the panel/(monitor; which to some degree very handy since it allows to "simulate" other resoultion to see how they would fit into frame, like 2560x1600 on 22 inch etc.
butt since it not native? resoultion, it looks not that genuine.
(noi AI corrigenda=)
https://ibb.co/60vdy1Td
#65 Re: Other Issues » [SOLVED] nvidia-persistenced daemon issue (sysvinit) » 2026-07-26 18:24:58
do also see error for newer graphics card, thought this is relegated to legacy gpu (nvidia-persistenced error)
Installing:
linux-headers-6.12.95+deb13-amd64
Installing dependencies:
libdw1t64 linux-headers-6.12.95+deb13-common linux-kbuild-6.12.95+deb13 pahole
Summary:
Upgrading: 0, Installing: 5, Removing: 0, Not Upgrading: 1
1 not fully installed or removed.
Download size: 16.4 MB
Space needed: 78.6 MB / 89.7 GB available
Continue? [Y/n]
Get:1 http://deb.devuan.org/merged excalibur/main amd64 libdw1t64 amd64 0.192-4 [255 kB]
Get:2 http://it.deb.devuan.org/merged excalibur-security/main amd64 linux-headers-6.12.95+deb13-common all 6.12.95-1 [11.1 MB]
Get:3 http://deb.devuan.org/merged excalibur/main amd64 pahole amd64 1.30-1 [259 kB]
Get:4 http://it.deb.devuan.org/merged excalibur-security/main amd64 linux-kbuild-6.12.95+deb13 amd64 6.12.95-1 [1,730 kB]
Get:5 http://it.deb.devuan.org/merged excalibur-security/main amd64 linux-headers-6.12.95+deb13-amd64 amd64 6.12.95-1 [3,057 kB]
Fetched 16.4 MB in 4s (4,587 kB/s)
Selecting previously unselected package libdw1t64:amd64.
(Reading database ... 208354 files and directories currently installed.)
Preparing to unpack .../libdw1t64_0.192-4_amd64.deb ...
Unpacking libdw1t64:amd64 (0.192-4) ...
Selecting previously unselected package linux-headers-6.12.95+deb13-common.
Preparing to unpack .../linux-headers-6.12.95+deb13-common_6.12.95-1_all.deb ...
Unpacking linux-headers-6.12.95+deb13-common (6.12.95-1) ...
Selecting previously unselected package pahole.
Preparing to unpack .../pahole_1.30-1_amd64.deb ...
Unpacking pahole (1.30-1) ...
Selecting previously unselected package linux-kbuild-6.12.95+deb13.
Preparing to unpack .../linux-kbuild-6.12.95+deb13_6.12.95-1_amd64.deb ...
Unpacking linux-kbuild-6.12.95+deb13 (6.12.95-1) ...
Selecting previously unselected package linux-headers-6.12.95+deb13-amd64.
Preparing to unpack .../linux-headers-6.12.95+deb13-amd64_6.12.95-1_amd64.deb ...
Unpacking linux-headers-6.12.95+deb13-amd64 (6.12.95-1) ...
Setting up nvidia-persistenced (550.163.01-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
Setting up libdw1t64:amd64 (0.192-4) ...
Setting up linux-headers-6.12.95+deb13-common (6.12.95-1) ...
Setting up pahole (1.30-1) ...
Setting up linux-kbuild-6.12.95+deb13 (6.12.95-1) ...
Setting up linux-headers-6.12.95+deb13-amd64 (6.12.95-1) ...
/etc/kernel/header_postinst.d/dkms:
Sign command: /lib/modules/6.12.95+deb13-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Certificate or key are missing, generating self signed certificate for MOK...
Autoinstall of module nvidia-current/550.163.01 for kernel 6.12.95+deb13-amd64 (x86_64)
Building module(s)............. done.
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-modeset.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-drm.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-uvm.ko
Signing module /var/lib/dkms/nvidia-current/550.163.01/build/nvidia-peermem.ko
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-modeset.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-drm.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-uvm.ko.xz
Installing /lib/modules/6.12.95+deb13-amd64/updates/dkms/nvidia-current-peermem.ko.xz
Running depmod.... done.
Autoinstall on 6.12.95+deb13-amd64 succeeded for module(s) nvidia-current.
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Errors were encountered while processing:
nvidia-persistenced
Error: Sub-process /usr/bin/dpkg returned an error code (1)now since the driver is not complete tried with "nvidia-full" only to encounter again the nvidia-persistenced-error.
sudo apt install nvidia-driver-full --no-install-recommends
Installing:
nvidia-driver-full
Installing dependencies:
libcuda1 libnvidia-encode1 nvidia-driver-bin
libcudadebugger1 libnvidia-fbc1 nvidia-driver-libs
libegl-nvidia0 libnvidia-ml1 nvidia-egl-common
libgl1-nvidia-glvnd-glx libnvidia-ngx1 nvidia-egl-icd
libgles-nvidia1 libnvidia-nvvm4 nvidia-opencl-common
libgles-nvidia2 libnvidia-opticalflow1 nvidia-opencl-icd
libglx-nvidia0 libnvidia-pkcs11-openssl3 nvidia-persistenced
libnvcuvid1 libnvidia-ptxjitcompiler1 nvidia-powerd
libnvidia-allocator1 libnvidia-rtcore nvidia-settings
libnvidia-api1 libnvoptix1 nvidia-smi
libnvidia-cfg1 nvidia-cuda-mps nvidia-suspend-common
libnvidia-egl-wayland1 nvidia-detect nvidia-vulkan-common
libnvidia-eglcore nvidia-driver nvidia-vulkan-icd
Recommended packages:
libcuda1:i386 libnvidia-egl-gbm1 nvidia-driver-libs:i386
Summary:
Upgrading: 0, Installing: 40, Removing: 0, Not Upgrading: 0
Download size: 131 MB / 170 MB
Space needed: 482 MB / 85.7 GB available
Continue? [Y/n]
Get:1 http://deb.devuan.org/merged excalibur/non-free amd64 libcudadebugger1 amd64 550.163.01-2 [2,762 kB]
Get:2 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-api1 amd64 550.163.01-2 [375 kB]
Get:3 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-fbc1 amd64 550.163.01-2 [204 kB]
Get:4 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-ngx1 amd64 550.163.01-2 [2,410 kB]
Get:5 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-nvvm4 amd64 550.163.01-2 [21.9 MB]
Get:6 http://deb.devuan.org/merged excalibur/non-free amd64 libnvidia-opticalflow1 amd64 550.163.01-2 [183 kB]
Get:7 http://deb.devuan.org/merged excalibur/non-free amd64 libnvoptix1 amd64 550.163.01-2 [99.0 MB]
Get:8 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-cuda-mps amd64 550.163.01-2 [190 kB]
Get:9 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-detect amd64 550.163.01-2 [166 kB]
Get:10 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-opencl-common amd64 550.163.01-2 [162 kB]
Get:11 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-opencl-icd amd64 550.163.01-2 [2,765 kB]
Get:12 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-powerd amd64 550.163.01-2 [244 kB]
Get:13 http://deb.devuan.org/merged excalibur/non-free amd64 nvidia-driver-full amd64 550.163.01-2 [161 kB]
Fetched 131 MB in 9s (13.9 MB/s)
Extracting templates from packages: 100%
Selecting previously unselected package libnvidia-ptxjitcompiler1:amd64.
(Reading database ... 281657 files and directories currently installed.)
Preparing to unpack .../00-libnvidia-ptxjitcompiler1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-ptxjitcompiler1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-pkcs11-openssl3:amd64.
Preparing to unpack .../01-libnvidia-pkcs11-openssl3_550.163.01-2_amd64.deb ...
Unpacking libnvidia-pkcs11-openssl3:amd64 (550.163.01-2) ...
Selecting previously unselected package libcuda1:amd64.
Preparing to unpack .../02-libcuda1_550.163.01-2_amd64.deb ...
Unpacking libcuda1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-eglcore:amd64.
Preparing to unpack .../03-libnvidia-eglcore_550.163.01-2_amd64.deb ...
Unpacking libnvidia-eglcore:amd64 (550.163.01-2) ...
Selecting previously unselected package libglx-nvidia0:amd64.
Preparing to unpack .../04-libglx-nvidia0_550.163.01-2_amd64.deb ...
Unpacking libglx-nvidia0:amd64 (550.163.01-2) ...
Selecting previously unselected package libgl1-nvidia-glvnd-glx:amd64.
Preparing to unpack .../05-libgl1-nvidia-glvnd-glx_550.163.01-2_amd64.deb ...
Unpacking libgl1-nvidia-glvnd-glx:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-egl-common.
Preparing to unpack .../06-nvidia-egl-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-egl-common (550.163.01-2) ...
Selecting previously unselected package libnvidia-egl-wayland1:amd64.
Preparing to unpack .../07-libnvidia-egl-wayland1_1%3a1.1.18-1_amd64.deb ...
Unpacking libnvidia-egl-wayland1:amd64 (1:1.1.18-1) ...
Selecting previously unselected package libegl-nvidia0:amd64.
Preparing to unpack .../08-libegl-nvidia0_550.163.01-2_amd64.deb ...
Unpacking libegl-nvidia0:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-egl-icd:amd64.
Preparing to unpack .../09-nvidia-egl-icd_550.163.01-2_amd64.deb ...
Unpacking nvidia-egl-icd:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-driver-libs:amd64.
Preparing to unpack .../10-nvidia-driver-libs_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver-libs:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-ml1:amd64.
Preparing to unpack .../11-libnvidia-ml1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-ml1:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-driver-bin.
Preparing to unpack .../12-nvidia-driver-bin_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver-bin (550.163.01-2) ...
Selecting previously unselected package nvidia-driver.
Preparing to unpack .../13-nvidia-driver_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver (550.163.01-2) ...
Selecting previously unselected package libnvidia-cfg1:amd64.
Preparing to unpack .../14-libnvidia-cfg1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-cfg1:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-persistenced.
Preparing to unpack .../15-nvidia-persistenced_550.163.01-1_amd64.deb ...
Unpacking nvidia-persistenced (550.163.01-1) ...
Selecting previously unselected package nvidia-settings.
Preparing to unpack .../16-nvidia-settings_550.163.01-1_amd64.deb ...
Unpacking nvidia-settings (550.163.01-1) ...
Selecting previously unselected package libcudadebugger1:amd64.
Preparing to unpack .../17-libcudadebugger1_550.163.01-2_amd64.deb ...
Unpacking libcudadebugger1:amd64 (550.163.01-2) ...
Selecting previously unselected package libgles-nvidia1:amd64.
Preparing to unpack .../18-libgles-nvidia1_550.163.01-2_amd64.deb ...
Unpacking libgles-nvidia1:amd64 (550.163.01-2) ...
Selecting previously unselected package libgles-nvidia2:amd64.
Preparing to unpack .../19-libgles-nvidia2_550.163.01-2_amd64.deb ...
Unpacking libgles-nvidia2:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvcuvid1:amd64.
Preparing to unpack .../20-libnvcuvid1_550.163.01-2_amd64.deb ...
Unpacking libnvcuvid1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-allocator1:amd64.
Preparing to unpack .../21-libnvidia-allocator1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-allocator1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-api1:amd64.
Preparing to unpack .../22-libnvidia-api1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-api1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-encode1:amd64.
Preparing to unpack .../23-libnvidia-encode1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-encode1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-fbc1:amd64.
Preparing to unpack .../24-libnvidia-fbc1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-fbc1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-ngx1:amd64.
Preparing to unpack .../25-libnvidia-ngx1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-ngx1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-nvvm4:amd64.
Preparing to unpack .../26-libnvidia-nvvm4_550.163.01-2_amd64.deb ...
Unpacking libnvidia-nvvm4:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-opticalflow1:amd64.
Preparing to unpack .../27-libnvidia-opticalflow1_550.163.01-2_amd64.deb ...
Unpacking libnvidia-opticalflow1:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvidia-rtcore:amd64.
Preparing to unpack .../28-libnvidia-rtcore_550.163.01-2_amd64.deb ...
Unpacking libnvidia-rtcore:amd64 (550.163.01-2) ...
Selecting previously unselected package libnvoptix1:amd64.
Preparing to unpack .../29-libnvoptix1_550.163.01-2_amd64.deb ...
Unpacking libnvoptix1:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-cuda-mps.
Preparing to unpack .../30-nvidia-cuda-mps_550.163.01-2_amd64.deb ...
Unpacking nvidia-cuda-mps (550.163.01-2) ...
Selecting previously unselected package nvidia-detect.
Preparing to unpack .../31-nvidia-detect_550.163.01-2_amd64.deb ...
Unpacking nvidia-detect (550.163.01-2) ...
Selecting previously unselected package nvidia-vulkan-common.
Preparing to unpack .../32-nvidia-vulkan-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-vulkan-common (550.163.01-2) ...
Selecting previously unselected package nvidia-vulkan-icd:amd64.
Preparing to unpack .../33-nvidia-vulkan-icd_550.163.01-2_amd64.deb ...
Unpacking nvidia-vulkan-icd:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-smi.
Preparing to unpack .../34-nvidia-smi_550.163.01-2_amd64.deb ...
Unpacking nvidia-smi (550.163.01-2) ...
Selecting previously unselected package nvidia-opencl-common.
Preparing to unpack .../35-nvidia-opencl-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-opencl-common (550.163.01-2) ...
Selecting previously unselected package nvidia-opencl-icd:amd64.
Preparing to unpack .../36-nvidia-opencl-icd_550.163.01-2_amd64.deb ...
Unpacking nvidia-opencl-icd:amd64 (550.163.01-2) ...
Selecting previously unselected package nvidia-powerd.
Preparing to unpack .../37-nvidia-powerd_550.163.01-2_amd64.deb ...
Unpacking nvidia-powerd (550.163.01-2) ...
Selecting previously unselected package nvidia-suspend-common.
Preparing to unpack .../38-nvidia-suspend-common_550.163.01-2_amd64.deb ...
Unpacking nvidia-suspend-common (550.163.01-2) ...
Selecting previously unselected package nvidia-driver-full.
Preparing to unpack .../39-nvidia-driver-full_550.163.01-2_amd64.deb ...
Unpacking nvidia-driver-full (550.163.01-2) ...
Setting up libnvidia-eglcore:amd64 (550.163.01-2) ...
Setting up nvidia-egl-common (550.163.01-2) ...
Setting up libnvidia-ml1:amd64 (550.163.01-2) ...
Setting up nvidia-detect (550.163.01-2) ...
Setting up nvidia-powerd (550.163.01-2) ...
Setting up nvidia-opencl-common (550.163.01-2) ...
Setting up libnvidia-cfg1:amd64 (550.163.01-2) ...
Setting up libnvidia-allocator1:amd64 (550.163.01-2) ...
Setting up libglx-nvidia0:amd64 (550.163.01-2) ...
Setting up libnvidia-egl-wayland1:amd64 (1:1.1.18-1) ...
Setting up libnvidia-pkcs11-openssl3:amd64 (550.163.01-2) ...
Setting up libnvidia-ngx1:amd64 (550.163.01-2) ...
Setting up nvidia-cuda-mps (550.163.01-2) ...
Setting up libgles-nvidia1:amd64 (550.163.01-2) ...
Setting up libnvidia-ptxjitcompiler1:amd64 (550.163.01-2) ...
Setting up nvidia-vulkan-common (550.163.01-2) ...
Setting up libegl-nvidia0:amd64 (550.163.01-2) ...
Setting up nvidia-settings (550.163.01-1) ...
Setting up libnvidia-nvvm4:amd64 (550.163.01-2) ...
Setting up libgles-nvidia2:amd64 (550.163.01-2) ...
Setting up libnvidia-api1:amd64 (550.163.01-2) ...
Setting up libnvidia-rtcore:amd64 (550.163.01-2) ...
Setting up nvidia-suspend-common (550.163.01-2) ...
Processing triggers for nvidia-alternative (550.163.01-2) ...
update-alternatives: updating alternative /usr/lib/nvidia/current because link g
roup nvidia has changed slave links
Setting up nvidia-persistenced (550.163.01-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details.
invoke-rc.d: initscript nvidia-persistenced, action "start" failed.
dpkg: error processing package nvidia-persistenced (--configure):
installed nvidia-persistenced package post-installation script subprocess retur
ned error exit status 1
Processing triggers for hicolor-icon-theme (0.18-2) ...
Setting up libcuda1:amd64 (550.163.01-2) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Setting up nvidia-opencl-icd:amd64 (550.163.01-2) ...
Setting up nvidia-egl-icd:amd64 (550.163.01-2) ...
Processing triggers for man-db (2.13.1-1) ...
Setting up libnvoptix1:amd64 (550.163.01-2) ...
Setting up nvidia-vulkan-icd:amd64 (550.163.01-2) ...
Setting up libnvidia-fbc1:amd64 (550.163.01-2) ...
Setting up libgl1-nvidia-glvnd-glx:amd64 (550.163.01-2) ...
dpkg: dependency problems prevent configuration of nvidia-driver-full:
nvidia-driver-full depends on nvidia-persistenced; however:
Package nvidia-persistenced is not configured yet.
dpkg: error processing package nvidia-driver-full (--configure):
dependency problems - leaving unconfigured
Setting up libcudadebugger1:amd64 (550.163.01-2) ...
Setting up nvidia-smi (550.163.01-2) ...
Setting up nvidia-driver-bin (550.163.01-2) ...
Setting up nvidia-driver-libs:amd64 (550.163.01-2) ...
Setting up libnvcuvid1:amd64 (550.163.01-2) ...
Setting up libnvidia-opticalflow1:amd64 (550.163.01-2) ...
Setting up nvidia-driver (550.163.01-2) ...
Setting up libnvidia-encode1:amd64 (550.163.01-2) ...
Processing triggers for glx-alternative-nvidia (1.2.2) ...
Processing triggers for glx-alternative-mesa (1.2.2) ...
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Processing triggers for update-glx (1.2.2) ...
Processing triggers for glx-alternative-nvidia (1.2.2) ...
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/nvi
dia because link group glx is broken
Processing triggers for libc-bin (2.41-12+deb13u3) ...
Processing triggers for initramfs-tools (0.148.4) ...
update-initramfs: Generating /boot/initrd.img-6.12.96+deb13-amd64
Errors were encountered while processing:
nvidia-persistenced
nvidia-driver-full
Error: Sub-process /usr/bin/dpkg returned an error code (1)when i install "nvidia-driver" it goes through (--no-install-recommends) but afterwards no cuda , no opencl??
when install "nvidia-driver-full" it stops because "nvidia-driver-full" depends on "nvidia-persistenced"?
#66 Re: ARM Builds » [SOLVED] Default password for Arm SSH? » 2026-07-25 14:03:02
i am using somethimes adguard on my miinimall image arm64 pine-a64 running minimal armbian or devuan, like ti better than pihole, but then i uninstall again,since the added value is minimal for my setup; and it adds abit latency;
also it is easier to install;
the raspberry 3 still have a libreelec use soemtimes, since i have bought mpeg-keys for 1-2-3.
#68 Re: ARM Builds » [SOLVED] Default password for Arm SSH? » 2026-07-25 13:44:22
if you have given already your own, ti is yours.
http://jarnotuovinen.com/devuan-4-chima … berry-pi-3
apt-get install ssh
#69 Re: ARM Builds » [SOLVED] Default password for Arm SSH? » 2026-07-25 13:33:47
zou could try root toor
or root 1234
but first probably you would need to enable ssh on the machine since with devuan it could be that it is not enabled by default (as it is easy to setup for raspberry pios)
#70 Re: Packaging for Devuan » [SOLVED] Access to Beowulf packages » 2026-07-24 20:14:29
most likely you need to change "deb.devuan.org" to "archive.devuan.org" or similar,
thats the way debian handled it lately, and i needed to do so also during installer if used an older release, but for some reason devuan-installer doesnt like it so muchh and often the install would fail from netinstall; whereas with debian the "archive" is bit more accessible.
#71 Desktop and Multimedia » [SOLVED] Browser (/no longer) playing audio? » 2026-07-22 22:24:08
- kapqa
- Replies: 0
Hello ,
have made a change in audio setup
now only with monitor audio + dac for some time.
would like be unpretentious;
but this thing a bit strange ,
since am sure that with this browser "nightly" could play audio , but now it seems it no longer plays any audio.
previously had firefox-esr + nightly (compiled via instructions from forum)
now have firefox-esr + nightly (had audio) + firefox developer (has audio).
it is bit strange, because am pretty sure it functioned before, and now it seem no longer;
please just ignore this thread if you like because maybe i am just a bit oomm.
the nighly reports (max channel = 0) - am a bit puzzled.
https://ibb.co/GvpTY1DM
https://ibb.co/PGWVwQBz
https://ibb.co/cS2XQjNC
thanks for ignoring.
#73 Re: Hardware & System Configuration » Radeon HD 5770 - free driver does not detect refresh rates above 60Hz » 2026-07-17 09:48:13
have employed or had so both cards, however for use on an old mac pro;
especially the 6770 was sought after at the time, since it could very well perform for mac os x 10.6+ ]
<>
however have sadly no real high refresh monitor so the "advice" is not tested since my monitor dont go over 75hz (on vga analog only, one monitor can do it also via dvi) ] besides older crt monitor but that one is not in use.
the chit-chat give passable responses for technical question, here is what he responded.
Max Resolution & Refresh Rates by PortDisplayPort 1.2 or Dual-Link DVI: 2560 × 1600 at 60Hz is the hard limit. You cannot run a 4K monitor at native resolution on this card.HDMI (Version 1.4a): 1920 × 1200 at 60Hz. Note that while the port can push standard 1080p (1920 × 1080), it is locked to a max of 60Hz over HDMI due to early generation firmware limitations.VGA (Analog): 2048 × 1536 at 85Hz.
that is what my experience would also have told you, if you have a high refresh monitor , and your resolution is not in the listing of the supported refresh modes (normally found in manual) you most probably would have to lower your resolution to achieve higher refresh rate (as was the case for most not-high-end crt probably)
Max Resolution Limits for HD 5770DisplayPort (or Mini-DisplayPort) & Dual-Link DVI: Hard limited to 2560 × 1600 at 60Hz.HDMI: Hard limited to 1920 × 1200 at 60Hz.VGA (Analog): Hard limited to 2048 × 1536 at 85Hz.
at the moment for the older mac am using hd 4870 since found that the card is still capable and function thad better with newer macos ] but that is not what you have asked for.
basically, you will be "locked" into the capabilities of your gpu, and software-overrides wont "squeeze" the direct high-refresh rates say on one of those newer 100hz monitors it would suggest, but could be wrong on this (since it supporting 2560x1600 at 60hz it could or should very well support 1920x1200x100hz, but you most certainly will find difficulty finding it to support 2560-1600x120hz, if such a panel exists on market outside laptop space yet).
#74 Re: Installation » Which Excalibur install problems fixed by 6.1.1? » 2026-07-12 11:20:39
had my own share of issues with dexcalibure 6.1.1 this week ~
had already a triple boot on am4 inplace but decided to make space for devuan since nowadays can live totally without ubuntu since all software also available to some degree on devuan.
however, it took me several times to install-reinstall since the first two attempts failed for reasons not fully understood.
the first time i made usb stick with mkusb ~ the install probably went through ~ but afterwards grub complained something about shim-something, "you need to load the kernel frist"
made probably another attempt , this time usb stick made with "rufus" - standard settings (mbr > bios or uefi) and made sure it booted via uefi; again, went through, but the same error at grub.
it dawned on me, to change probably the UEFI secure boot setting from "standard" to "custom" in BIOS;
but after another attempt, the same RUFUS made usb image, again the error "you need to load kernel first" ~
luckily i have already burned excalbure 6.1.1 onto dvd-rw (very many thanks for that!=) and with the dvd.iso image it went through and booted;
would like to emphasize that for the usb-stick i used also the full 6.1.1.iso and not the net-install;
in general i have had most luck installing linux with burned .iso onto dvd, no matter the distro;with devuan 6.1. especially had more problems installing overall than with other distro, espcially when compared to previous iterations of devuan; but its worth the effort, devuan function just well after setup, glad have found it.
#75 Re: Installation » [SOLVED] UMAX AstraSlim SE - Invalid argument » 2026-07-09 15:41:35
remember some 5-8 years ago when ürchased the first ecotank printer,
that it was difficult sometime to scan with certain programs, not all would function equal, so i tired them through, (all) the different programs that were available,
and not all would function for the scanner for some reason or another; even the epson program itself would not function; so i started installing drivers etc, but since a lot has changed;
have an old samsung all-in-one here (relegated to shelve, since it laser), might aswell test it wout someday to see if can get scanning to function.
sometimes i do chit-chat-with gemini-chatbot since ma curiuos being;
but it warns that the answers can be inaccurate.
To grant your Linux system permissions to use an Epson scanner without root access, you must create a custom udev rule. This assigns the device to the scanner group and sets appropriate read/write permissions.Step 1: Find your Vendor and Product IDOpen a terminal and type lsusb. Look for your Epson device in the list and note down its IDs, which look similar to 04b8:012f (where 04b8 is the Vendor ID and 012f is the Product ID).Step 2: Create the udev RuleOpen a new rule file in your preferred text editor (e.g., Nano) with superuser privileges:sudo nano /etc/udev/rules.d/99-epson-scanner.rulesAdd the following line (replace YOUR_VENDOR_ID and YOUR_PRODUCT_ID with the numbers from Step 1):SUBSYSTEM=="usb", ATTRS{idVendor}=="YOUR_VENDOR_ID", ATTRS{idProduct}=="YOUR_PRODUCT_ID", MODE="0666", GROUP="scanner", ENV{libsane_matched}="yes"
Save the file and exit the text editor.Step 3: Apply and VerifyReload the udev rules for the changes to take effect:sudo udevadm control --reload-rulesUnplug your scanner's USB cable and plug it back in.Check if your user account is in the scanner group (if not, add it using sudo usermod -a -G scanner $USER).Run scanimage -L in your terminal to verify that your Epson scanner is detected.For more technical background on writing hardware rules, you can refer to general guides on Writing udev rules.Could you tell me the exact model of your Epson scanner and which Linux distribution you are using? This will allow me to provide the exact idVendor and idProduct numbers for your device, or help you troubleshoot specific SANE driver issues if they arise.
Board footer
