You are not logged in.
- Topics: Active | Unanswered
#1501 Re: Forum Feedback » Unable to edit any of my own posts » 2020-09-20 00:27:23
Hello:
... suggest time limits for consideration.
I think that posts which have not received an answer should have no time limit for edition by the OP, who should also be able to delete it if deemed necessary.
But, if a post has received an answer the OP should not be able to delete it.
With respect to editing a post that has received an answer, I'd say that it depends on the forum.
I have had a forum member (not here, of course ...) edit his original post and in doing so make my answer look out of place.
ie: like if I was replying to something that he did not write, to the extent of making me doubt for a second as to what I had read.
It's only happened to me once in more that 20 years of participating in different fora, but I found it to be rather unsettling.
I'm sure that here at Dev1 it could be allowed (with the provision of automatic edit notices) for as long as it takes for a second reply to come in.
From the on, that particular post would be closed to editing.
Make sense?
Cheers,
A.
#1502 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 23:40:01
Hello:
Thank you for documenting ...
You're welcome ...
But the merit is all HeavyDevy's.
I would not have known where to start.
Cheers,
A.
#1503 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 16:11:56
Hello:
... the debian wiki guide that this needs to be done as a separate set of commands/instruction ...
I see ...
But I have not had to do this in any of the other instances where I installed these same legacy-340xx drivers in other Linux distributons.
It did not happen when I moved from Linux Mint to a fresh Devuan Jesse installation either.
So why does it happen now in Beowulf?
The legacy-340xx driver is in the Beowulf distribution just as it was in the Jesse distribution.
Thanks for the heads-up, I'll keep the link in the Devuan bookmarks folder.
Once again, thanks for your help.
I certainly would not have my three screens in Beowulf without it.
Cheers,
A.
#1504 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 13:43:48
Hello:
... install the linux-headers first, i dont know ...
I would think that anything that was needed by the installer would have been listed as a dependency.
Or a warning that linux-headers were not installed issued and the installation aborted.
... definetly something buggy going on due to that nvidia-persistenced ...
Indeed ...
There was that post last year to which I made reference in this thread.
But it seems no one at Debian took notice.
... few of the steps i did were probably not needed ...
... depmod, update-initramfs and update-grub ...
Well ...
And it got me through. ;- )
I worry things such as these ie: a severely broken installation, don't get looked at by maintainers.
I expect to be using the same box with the same perfectly working video cards when I switch to Ceres.
Cheers,
A.
#1505 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-17 12:39:55
Hello:
... glad it worked for ya.
I would not have know how to fix it.
It is a severe issue, no clues anywhere.
Thanks again. =^)
... setup X from nvidia-settings for the 3 monitors ...
No.
In my experience, you have to get xorg.conf right first.
This could be (?) because the xserver disables RandR if Xinerama is enabled.
[ 29.157] (WW) NVIDIA: The Composite and Xinerama extensions are both enabled, which
[ 29.157] (WW) NVIDIA: is an unsupported configuration. The driver will continue
[ 29.157] (WW) NVIDIA: to load, but may behave strangely.
[ 29.157] (WW) NVIDIA: Xinerama is enabled, so RandR has likely been disabled by the NVIDIA: X server.When I got this box and got the twin Nvidia cards, I had to go through literally dozens of re-boots while testing an xorg.conf file I went along patching together with bits of different samples posted online. You would think that being to identical Nvidia cards it would be a simpler task with nvidia-xsettings.
Once you get xorg.conf right, you can play with nvidia-settings but I just use them to get an idea of what is going on.
The good thing is that (for now) I just cp the xorg.conf from one drive to the other and it works and as I don't play games or use anything of the sort, I really don't have to touch it once it is working properly.
... about the driver, i have no idea sorry.
There must be a maintainer for this at Debian, maybe there is one here at Devuan who should know about this.
Q:
The process you wrote up to install this driver, how does it differ from what the installer does?
I mean, besides working properly ... 8^*
Thanks in advance,
A.
#1506 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-16 13:19:36
Hello:
... managed to get it working.
This is what i did.
Great ! =-D!
Here's the terminal printout of the same process in my Beowulf installation:
groucho@devuan3:~$ su -
Password:
root@devuan3:~#root@devuan3:~# jed /etc/modprobe.d/nvidia-blacklist-nouveau.conf
root@devuan3:~#
root@devuan3:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64root@devuan3:~# apt install linux-headers-$(uname -r) build-essential
Reading package lists... Done
Building dependency tree
Reading state information... Done
build-essential is already the newest version (12.6).
build-essential set to manually installed.
The following additional packages will be installed:
linux-compiler-gcc-8-x86 linux-headers-4.19.0-9-common linux-kbuild-4.19
The following NEW packages will be installed:
linux-compiler-gcc-8-x86 linux-headers-4.19.0-9-amd64 linux-headers-4.19.0-9-common linux-kbuild-4.19
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.4 MB of archives.
After this operation, 57.9 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-compiler-gcc-8-x86 amd64 4.19.132-1 [458 kB]
Get:2 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-headers-4.19.0-9-common all 4.19.118-2+deb10u1 [8,371 kB]
Get:3 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-kbuild-4.19 amd64 4.19.132-1 [691 kB]
Get:4 http://pkgmaster.devuan.org/merged beowulf/main amd64 linux-headers-4.19.0-9-amd64 amd64 4.19.118-2+deb10u1 [917 kB]
Fetched 10.4 MB in 8s (1,265 kB/s)
Selecting previously unselected package linux-compiler-gcc-8-x86.
(Reading database ... 75161 files and directories currently installed.)
Preparing to unpack .../linux-compiler-gcc-8-x86_4.19.132-1_amd64.deb ...
Unpacking linux-compiler-gcc-8-x86 (4.19.132-1) ...
Selecting previously unselected package linux-headers-4.19.0-9-common.
Preparing to unpack .../linux-headers-4.19.0-9-common_4.19.118-2+deb10u1_all.deb ...
Unpacking linux-headers-4.19.0-9-common (4.19.118-2+deb10u1) ...
Selecting previously unselected package linux-kbuild-4.19.
Preparing to unpack .../linux-kbuild-4.19_4.19.132-1_amd64.deb ...
Unpacking linux-kbuild-4.19 (4.19.132-1) ...
Selecting previously unselected package linux-headers-4.19.0-9-amd64.
Preparing to unpack .../linux-headers-4.19.0-9-amd64_4.19.118-2+deb10u1_amd64.deb ...
Unpacking linux-headers-4.19.0-9-amd64 (4.19.118-2+deb10u1) ...
Setting up linux-compiler-gcc-8-x86 (4.19.132-1) ...
Setting up linux-kbuild-4.19 (4.19.132-1) ...
Setting up linux-headers-4.19.0-9-common (4.19.118-2+deb10u1) ...
Setting up linux-headers-4.19.0-9-amd64 (4.19.118-2+deb10u1) ...
root@devuan3:~#root@devuan3:~# apt install nvidia-legacy-340xx-kernel-dkms --no-install-recommends
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-kernel-support nvidia-modprobe update-glx
Suggested packages:
python3-apport menu nvidia-driver
Recommended packages:
linux-headers-686-pae | linux-headers-amd64 | linux-headers-generic | linux-headers nvidia-legacy-340xx-driver
| libnvidia-legacy-340xx-cuda1
The following NEW packages will be installed:
dkms glx-alternative-mesa glx-alternative-nvidia glx-diversions nvidia-installer-cleanup nvidia-kernel-common
nvidia-legacy-340xx-alternative nvidia-legacy-340xx-kernel-dkms nvidia-legacy-340xx-kernel-support nvidia-modprobe update-glx
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4,313 kB of archives.
After this operation, 16.6 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Preconfiguring packages ...
Selecting previously unselected package update-glx.
(Reading database ... 92511 files and directories currently installed.)
Preparing to unpack .../update-glx_1.0.0_amd64.deb ...
Unpacking update-glx (1.0.0) ...
Selecting previously unselected package glx-alternative-mesa.
Preparing to unpack .../glx-alternative-mesa_1.0.0_amd64.deb ...
Unpacking glx-alternative-mesa (1.0.0) ...
Selecting previously unselected package nvidia-installer-cleanup.
Preparing to unpack .../nvidia-installer-cleanup_20151021+9_amd64.deb ...
Unpacking nvidia-installer-cleanup (20151021+9) ...
Setting up nvidia-installer-cleanup (20151021+9) ...
Selecting previously unselected package glx-diversions.
(Reading database ... 92612 files and directories currently installed.)
Preparing to unpack .../0-glx-diversions_1.0.0_amd64.deb ...
Unpacking glx-diversions (1.0.0) ...
Selecting previously unselected package glx-alternative-nvidia.
Preparing to unpack .../1-glx-alternative-nvidia_1.0.0_amd64.deb ...
Unpacking glx-alternative-nvidia (1.0.0) ...
Selecting previously unselected package nvidia-legacy-340xx-alternative.
Preparing to unpack .../2-nvidia-legacy-340xx-alternative_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Selecting previously unselected package dkms.
Preparing to unpack .../3-dkms_2.6.1-4_all.deb ...
Unpacking dkms (2.6.1-4) ...
Selecting previously unselected package nvidia-kernel-common.
Preparing to unpack .../4-nvidia-kernel-common_20151021+9_amd64.deb ...
Unpacking nvidia-kernel-common (20151021+9) ...
Selecting previously unselected package nvidia-modprobe.
Preparing to unpack .../5-nvidia-modprobe_418.56-1_amd64.deb ...
Unpacking nvidia-modprobe (418.56-1) ...
Selecting previously unselected package nvidia-legacy-340xx-kernel-support.
Preparing to unpack .../6-nvidia-legacy-340xx-kernel-support_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-kernel-support (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-kernel-dkms.
Preparing to unpack .../7-nvidia-legacy-340xx-kernel-dkms_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-kernel-dkms (340.108-3~deb10u1) ...
Setting up nvidia-kernel-common (20151021+9) ...
Setting up update-glx (1.0.0) ...
Setting up dkms (2.6.1-4) ...
Setting up nvidia-modprobe (418.56-1) ...
Setting up glx-alternative-mesa (1.0.0) ...
Setting up glx-diversions (1.0.0) ...
Processing triggers for desktop-file-utils (0.23-4) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for glx-alternative-mesa (1.0.0) ...
update-alternatives: using /usr/lib/mesa-diverted to provide /usr/lib/glx (glx) in auto mode
Setting up glx-alternative-nvidia (1.0.0) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Setting up nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-kernel-support (340.108-3~deb10u1) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-kernel-dkms (340.108-3~deb10u1) ...
Loading new nvidia-legacy-340xx-340.108 DKMS files...
Building for 4.19.0-9-amd64
Building initial module for 4.19.0-9-amd64
Done.
nvidia-legacy-340xx.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-9-amd64/updates/dkms/
nvidia-legacy-340xx-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-9-amd64/updates/dkms/
depmod.......
DKMS: install completed.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
root@devuan3:~#root@devuan3:~# apt install nvidia-legacy-340xx-driver --no-install-recommends
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libegl1-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-glcore
libnvidia-legacy-340xx-ml1 nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-driver-libs nvidia-legacy-340xx-vdpau-driver
nvidia-support xserver-xorg-video-nvidia-legacy-340xx
Recommended packages:
nvidia-settings-legacy-340xx nvidia-persistenced nvidia-legacy-340xx-driver-libs-i386 libgles1-nvidia-legacy-340xx
libgles2-nvidia-legacy-340xx libnvidia-legacy-340xx-cfg1
The following NEW packages will be installed:
libegl1-nvidia-legacy-340xx libgl1-nvidia-legacy-340xx-glx libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-glcore
libnvidia-legacy-340xx-ml1 nvidia-legacy-340xx-driver nvidia-legacy-340xx-driver-bin nvidia-legacy-340xx-driver-libs
nvidia-legacy-340xx-vdpau-driver nvidia-support xserver-xorg-video-nvidia-legacy-340xx
0 upgraded, 11 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/19.4 MB of archives.
After this operation, 121 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Preconfiguring packages ...
Selecting previously unselected package libnvidia-legacy-340xx-glcore:amd64.
(Reading database ... 92882 files and directories currently installed.)
Preparing to unpack .../00-libnvidia-legacy-340xx-glcore_340.108-3~deb10u1_amd64.deb ...
Unpacking libnvidia-legacy-340xx-glcore:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-support.
Preparing to unpack .../01-nvidia-support_20151021+9_amd64.deb ...
Unpacking nvidia-support (20151021+9) ...
Selecting previously unselected package libgl1-nvidia-legacy-340xx-glx:amd64.
Preparing to unpack .../02-libgl1-nvidia-legacy-340xx-glx_340.108-3~deb10u1_amd64.deb ...
Unpacking libgl1-nvidia-legacy-340xx-glx:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package libnvidia-legacy-340xx-eglcore:amd64.
Preparing to unpack .../03-libnvidia-legacy-340xx-eglcore_340.108-3~deb10u1_amd64.deb ...
Unpacking libnvidia-legacy-340xx-eglcore:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package libegl1-nvidia-legacy-340xx:amd64.
Preparing to unpack .../04-libegl1-nvidia-legacy-340xx_340.108-3~deb10u1_amd64.deb ...
Unpacking libegl1-nvidia-legacy-340xx:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-libs:amd64.
Preparing to unpack .../05-nvidia-legacy-340xx-driver-libs_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver-libs:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package libnvidia-legacy-340xx-ml1:amd64.
Preparing to unpack .../06-libnvidia-legacy-340xx-ml1_340.108-3~deb10u1_amd64.deb ...
Unpacking libnvidia-legacy-340xx-ml1:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-driver-bin.
Preparing to unpack .../07-nvidia-legacy-340xx-driver-bin_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver-bin (340.108-3~deb10u1) ...
Selecting previously unselected package xserver-xorg-video-nvidia-legacy-340xx.
Preparing to unpack .../08-xserver-xorg-video-nvidia-legacy-340xx_340.108-3~deb10u1_amd64.deb ...
Unpacking xserver-xorg-video-nvidia-legacy-340xx (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-vdpau-driver:amd64.
Preparing to unpack .../09-nvidia-legacy-340xx-vdpau-driver_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-vdpau-driver:amd64 (340.108-3~deb10u1) ...
Selecting previously unselected package nvidia-legacy-340xx-driver.
Preparing to unpack .../10-nvidia-legacy-340xx-driver_340.108-3~deb10u1_amd64.deb ...
Unpacking nvidia-legacy-340xx-driver (340.108-3~deb10u1) ...
Setting up nvidia-support (20151021+9) ...
Setting up libnvidia-legacy-340xx-ml1:amd64 (340.108-3~deb10u1) ...
Setting up libnvidia-legacy-340xx-glcore:amd64 (340.108-3~deb10u1) ...
Setting up libgl1-nvidia-legacy-340xx-glx:amd64 (340.108-3~deb10u1) ...
Setting up xserver-xorg-video-nvidia-legacy-340xx (340.108-3~deb10u1) ...
Setting up libnvidia-legacy-340xx-eglcore:amd64 (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-vdpau-driver:amd64 (340.108-3~deb10u1) ...
Setting up libegl1-nvidia-legacy-340xx:amd64 (340.108-3~deb10u1) ...
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for nvidia-legacy-340xx-alternative (340.108-3~deb10u1) ...
update-alternatives: using /usr/lib/nvidia/legacy-340xx to provide /usr/lib/nvidia/nvidia (nvidia) in auto mode
Processing triggers for man-db (2.8.5-2) ...
Setting up nvidia-legacy-340xx-driver-bin (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-driver-libs:amd64 (340.108-3~deb10u1) ...
Setting up nvidia-legacy-340xx-driver (340.108-3~deb10u1) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
Processing triggers for update-glx (1.0.0) ...
Processing triggers for glx-alternative-nvidia (1.0.0) ...
update-alternatives: using /usr/lib/nvidia to provide /usr/lib/glx (glx) in auto mode
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
root@devuan3:~# root@devuan3:~# depmod
root@devuan3:~# root@devuan3:~#
root@devuan3:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64
root@devuan3:~#
root@devuan3:~# update-grub
Generating grub configuration file ...
Found theme: /usr/share/desktop-base/grub-themes/desktop-grub-theme/theme.txt
Found linux image: /boot/vmlinuz-4.19.0-9-amd64
Found initrd image: /boot/initrd.img-4.19.0-9-amd64
Found Devuan GNU/Linux ascii on /dev/sde1
done
root@devuan3:~# Just to see, I tried to run nvidia-xconfig but had to install it because it was not there.
It does not detect my three monitors, only one so it is not much use.
groucho@devuan3:~$ lspci -knn | grep -iA3 nvidia
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1)
Subsystem: NVIDIA Corporation G96GL [Quadro FX 580] [10de:063a]
Kernel driver in use: nvidia
Kernel modules: nvidia
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96GL [Quadro FX 580] [10de:0659] (rev a1)
Subsystem: NVIDIA Corporation G96GL [Quadro FX 580] [10de:063a]
Kernel driver in use: nvidia
Kernel modules: nvidia
--- snip ---
groucho@devuan3:~$ This may work ...
It did ... 8-D!
Thanks a lot for your effort.
Now it should just be a matter of setting up xorg.conf and everything should be allright.
A transplant from my ascii setup should do, as always.
Should not (?) need any changes, but you never know with Nvidia.
--->
Edit:
Transplanted the ascii /etc/X11/xorg.conf to Beowulf and it all works perfectly well.
Main difference is that now I'll be using Openbox, so I have to configure it and Tint2 for three screens.
The /var/log/xorg.0.log file has the same warnings related to Composite+Xinerama, disabled RandR, missing cyrilic fonts and fbGetGCPrivateKey unresolved, so it seems that there's nothing new there.
<---
Q:
Am I correct in assuming that this is a problem with the installer scripts in the nvidia-legacy-340xx-driver package in the Beowulf repository?
I say this is probably so because the nvidia 340xx driver has not been updated by Nvidia for a few years now.
ie: it is the same code, has not had any maintenance.
So if there's anything that has changed, I can only think that it has been something within the Devuan/Debian distribution and/or the installer scripts in the package.
A Debian issue then?
Once again, thanks a lot for your help.
Cheers,
A.
#1507 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-16 12:32:11
Hello:
Maybe let sgfxi handle it?
I'll have a look ...
But I recall having used it once but unless I'm not remembering right, sgfxi is for getting xorg.conf set up properly.
I used it when I was setting up my first devuan (Jesse) and it did no better than my efforts with a xorg.conf file patched together with bits from web examples.
Methinks this is an installer problem.
Thanks for your input.
A.
#1508 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-16 01:35:26
Hello:
... hope that they remove it from Beowulf stable.
May not be necessary?
As luck (or whatever it is) would have it, I found an interesting post right here: --> https://dev1galaxy.org/viewtopic.php?pid=20903#p20903
Yes, under my nose.
A Dev1 member (Marjorie) had more or less the same problem a bit over a year ago.
Found out that nvidia-persistenced is a suggested package so simply did not install it ...
ie: apt-get --no-install-recommends install nvidia-legacy-340xx-driver
... which solved the issue I had with nvidia-persistenced itself.
ie:
~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---There was another problem related to stopping an existing nvidia-persistenced service for which she modified an installation script, but as mine is a clean netinstall (uses nouveau), it was not required.
The driver apparently installed with no issues.
I rebooted but SLiM did not start and startx showed errors.
So feeling very confident, I transplanted the xorg.conf file from ascii and rebooted.
No cigar ...
Unfortunately, this did not solve my problem which revealed to have yet another part to it.
At the very start of the /var/log/Xorg.0.log file, this is what you see:
modprobe: FATAL: module nvidia-legacy-340xx not found in directory /lib/modules/4.19.0-9-amd64
I checked and, as the output clearly states, the module is not there.
Now I've run out of ideas ...
Anyone?
Thanks in advance,
A.
#1509 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-15 16:20:13
Hello:
... look at the debian package tracker ...
... issues with nvida-persistence ...
... being removed ...
Then I hope that they remove it from Beowulf stable.
asap.
... dont know how this affects Beowulf stable ...
Evidently, not in a good way.
... if you are using a kernel from testing or ...
No ...
Not that adventurous, bleeding edge is not where I want or need to be.
I'm a Debian user/greybeard at heart.
I always found the (original) Debian (pre systemd) philosophy to be the way to do things.
Cheers,
A.
#1510 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-15 16:12:26
Hello:
What kernel ...
Devian3 - Beowulf stable.
groucho@devuan3:~$ uname -a
Linux devuan3 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07) x86_64 GNU/Linux
groucho@devuan3:~$ Will try to install nvidia again on the machine i have that uses 340xx again with beowulf ...
Thanks for the effort ... ;- )
... can you confirm where the nvidia-persistenced binary is located ...
I installed the driver again (but no reboot) and this is what I get:
root@devuan3:~# locate nvidia-persistenced
/etc/init.d/nvidia-persistenced
/etc/rc0.d/K01nvidia-persistenced
/etc/rc1.d/K01nvidia-persistenced
/etc/rc2.d/S02nvidia-persistenced
/etc/rc3.d/S02nvidia-persistenced
/etc/rc4.d/S02nvidia-persistenced
/etc/rc5.d/S02nvidia-persistenced
/etc/rc6.d/K01nvidia-persistenced
/lib/systemd/system/nvidia-persistenced.service
/run/nvidia-persistenced
/usr/bin/nvidia-persistenced <- here it is
/usr/share/doc/nvidia-legacy-340xx-driver/html/nvidia-persistenced.html
/usr/share/doc/nvidia-persistenced
/usr/share/doc/nvidia-persistenced/changelog.Debian.gz
/usr/share/doc/nvidia-persistenced/copyright
/usr/share/lintian/overrides/nvidia-persistenced
/usr/share/man/man1/nvidia-persistenced.1.gz
/var/cache/apt/archives/nvidia-persistenced_418.56-1_amd64.deb
/var/lib/dpkg/info/nvidia-persistenced.conffiles
/var/lib/dpkg/info/nvidia-persistenced.list
/var/lib/dpkg/info/nvidia-persistenced.md5sums
/var/lib/dpkg/info/nvidia-persistenced.postinst
/var/lib/dpkg/info/nvidia-persistenced.postrm
/var/lib/dpkg/info/nvidia-persistenced.prerm
root@devuan3:~# Thanks for your help,
A.
#1511 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-15 15:12:07
Hello:
... an issue with the legacy driver, I don't know.
As the driver will not install properly, would seem so.
... combining the official repoes and backports may result in conflicts ...
... disable the backports repo and start a fresh.
This is my /etc/apt/sources.list:
groucho@devuan3:~$ cat /etc/apt/sources.list
deb http://pkgmaster.devuan.org/merged beowulf main non-free contrib
deb http://pkgmaster.devuan.org/merged beowulf-security main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-updates main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-backports main contrib non-free
groucho@devuan3:~$ According to https://pkginfo.devuan.org/ the Nvidia driver version in beowulf is 340.108-3-deb10u1 and the version in beowulf-backports is 340.108-6-bpo10+1.
I had thought about this beowulf vs. beowulf-backports you mention and as I do have beowulf-backports in my /etc/apt/sources.list I looked to see what version apt was installing.
groucho@devuan3:~$ apt list | grep 340xx-driver
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
nvidia-legacy-340xx-driver-bin/stable 340.108-3~deb10u1 amd64
nvidia-legacy-340xx-driver-libs/stable 340.108-3~deb10u1 amd64
nvidia-legacy-340xx-driver/stable 340.108-3~deb10u1 amd64 <---- this is the version apt will install
groucho@devuan3:~$ When I look at the driver version that would install via synaptic, I get the same result: synaptic installs version 340.108-3~deb10u1 by default and to install version 340.108-6-bpo10+1 you have to use the force version option.
Thanks for your input.
Cheers,
A.
#1512 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-15 13:42:09
Hello:
... download and open up the *.deb file from the Beowulf repository ...
Not possible to see the files.
So I reinstalled the driver and stopped before rebooting the system.
First I opened a terminal and looked for the nvidia.conf file and found it in two instances:
root@devuan3:~# updatedb
root@devuan3:~# locate nvidia.conf
/etc/modprobe.d/nvidia.conf <-- here
/etc/modules-load.d/nvidia.conf <-- here
root@devuan3:~# I opened them up to see what was there:
root@devuan3:~# cat /etc/modprobe.d/nvidia.conf
install nvidia modprobe -i nvidia-legacy-340xx $CMDLINE_OPTS
install nvidia-uvm modprobe nvidia ; modprobe -i nvidia-legacy-340xx-uvm $CMDLINE_OPTS
remove nvidia modprobe -r -i nvidia-uvm nvidia
# These aliases are defined in *all* nvidia modules.
# Duplicating them here sets higher precedence and ensures the selected
# module gets loaded instead of a random first match if more than one
# version is installed. See #798207.
alias pci:v000010DEd00000E00sv*sd*bc04sc80i00* nvidia
alias pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00* nvidia
alias pci:v000010DEd*sv*sd*bc03sc02i00* nvidia
alias pci:v000010DEd*sv*sd*bc03sc00i00* nvidia
root@devuan3:~#root@devuan3:~# cat /etc/modules-load.d/nvidia.conf
nvidia
root@devuan3:~# Neither file had the data I expected to find (see previous post) so I looked to see what else was in /etc/modprobe.d and /etc/modules-load.d and found this:
root@devuan3:~# ls /etc/modprobe.d
dkms.conf nvidia-blacklists-nouveau.conf nvidia.conf nvidia-kernel-common.conf
root@devuan3:~# root@devuan3:~# ls /etc/modules-load.d
cups-filters.conf nvidia.conf
root@devuan3:~# I then opened them up to see what was there and found this:
root@devuan3:~# cat /etc/modprobe.d/dkms.conf
# modprobe information used for DKMS modules
#
# This is a stub file, should be edited when needed,
# used by default by DKMS.
root@devuan3:~# root@devuan3:~# cat /etc/modprobe.d/nvidia-blacklists-nouveau.conf
# You need to run "update-initramfs -u" after editing this file.
# see #580894
blacklist nouveauroot@devuan3:~# cat /etc/modprobe.d/nvidia-kernel-common.conf
alias char-major-195* nvidia
#options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660
# To enable FastWrites and Sidebus addressing, uncomment these lines
# options nvidia NVreg_EnableAGPSBA=1
# options nvidia NVreg_EnableAGPFW=1
root@devuan3:~# root@devuan3:~# cat /etc/modules-load.d/cups-filters.conf
# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc
root@devuan3:~# This file nvidia-kernel-common.conf had the data I was looking for:
options nvidia NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=44 NVreg_DeviceFileMode=0660ie:
The options that are related to how the driver installer sets up /dev/nvidia* and its permissions.
NVreg_DeviceFileUID=0 <--- keeps the installer from creating /dev/nvidia*. Should be =1 (?)
NVreg_DeviceFileMode=0660 <--- allows the installer to write what it needs where it needs it.
BUT the options nvidia line is commented out so none of the options are set, the most important being the creation of /dev/nvidia*, which is what nvidia-persistenced looks for but cannot find.
That's all I have been able to weed out.
But don't know how to go on from here.
Any ideas?
Thanks in advance,
A.
#1513 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 22:58:46
Hello:
here's what a backup looks like...
there isn't one on my system in use atm.
It does not seem to have the contents of the files I have seen on the web.
eg: here.
FILE /etc/modprobe.d/nvidia.confSetting nvidia NVreg_EnableMSI
# Nvidia drivers support
alias char-major-195 nvidia
alias /dev/nvidiactl char-major-195
# To tweak the driver the following options can be used, note that
# you should be careful, as it could cause instability!! For more
# options see /usr/share/doc/nvidia-drivers-337.19/README
#
# !!! SECURITY WARNING !!!
# DO NOT MODIFY OR REMOVE THE DEVICE FILE RELATED OPTIONS UNLESS YOU KNOW
# WHAT YOU ARE DOING.
# ONLY ADD TRUSTED USERS TO THE VIDEO GROUP, THESE USERS MAY BE ABLE TO CRASH,
# COMPROMISE, OR IRREPARABLY DAMAGE THE MACHINE.
options nvidia NVreg_DeviceFileMode=0660 NVreg_DeviceFileUID=0 NVreg_DeviceFileGID=27 NVreg_ModifyDeviceFiles=1 NVreg_EnableMSI=0
I'll see if I can download and open up the *.deb file from the Beowulf repository to see what is inside.
Thanks for your input.
Cheers,
A.
#1514 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 21:47:24
Hello:
I hate quoting myself ...
~# cat /var/log/syslog --- snip --- Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411) Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files. Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411) --- snip ---
As I wrote previously, the NVIDIA device files (/dev/nvidia*) do not exist.
Now, looking around the web I found this: https://forums.developer.nvidia.com/t/d … t/110139/4
The content of your /etc/modprobe.d/nvidia.conf file is not correct. It should read options nvidia NVreg_DeviceFileMode=0660 You forgot ‘nvidia’ – and NVreg_ModifyDeviceFiles=0 means to not create /dev/nvidia* nodes at all.
Also this:
You need to recreate your initrd to make the changes to /etc/modprobe.d/nvidia.conf effective.
Note that there is no proper rights management for the nvidia device files. They are expected to be rw for everyone, otherwise things don’t work. That’s why nvidia-modprobe exists. It’s suid root and will (among other things) fixup everything to be 0666. nvidia-smi calls it if necessary.
If I get (?) the idea behind these texts, /etc/modprobe.d/nvidia.conf (probably part of the drivers installation) could be incorrect and reading something other than nvidia NVreg_DeviceFileMode=0660 and have NVreg_ModifyDeviceFiles option set to =0.
If this is so (fail to understand how this could be) this, it would explain why the /dev/nvidia* files are missing.
Any idea as to how to proceed and check the /etc/modprobe.d/nvidia.conf?
I don't have one in my Beowulf installation.
Thanks in advance,
A.
#1515 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 16:32:54
Hello:
what does your ascii installation have to ...
Nothing.
I was comparing my working ascii installation with what nvidia drivers was installing in Beowulf.
... using beowulf or ascii ?
Like I mention in my OP, my working installation is ascii and I'm installing Beowulf on a separate drive to see how it goes.
Also, why not follow this guide ?
https://wiki.debian.org/NvidiaGraphicsDrivers
I installed the these nvidia-340XX legacy drivers in Beowulf in the very same way I have done it in Devaun ascii, Jesse, PCLinuxOS, Linux Mint and others. ie: ever since I retired my old rig with 'ancient' Matrox G550 PCI cards as there were no available drivers for Linux.
I'll have a look at the guide (*) but if these drivers installed with no issues on this box (exact same hardware) running ascii, I'd say there is a high probability that the problem lies with the Beowulf Nvidia-340xx package or something that has changed in Beowulf that creates some incompatibility.
There has been an important change in Beowulf wrt how su works, now we have to use su - instead.
Could this output from var/log/syslog be a clue?
~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---Thanks for your input.
Cheers,
A.
(*)
--- snip ---
DKMS will build the nvidia module for your system, via the nvidia-legacy-340xx-kernel-dkms package.
--- snip ---
This is what (for whatever reason) is not happening.
#1516 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 15:16:49
Hello:
Do you have https://packages.debian.org/buster/libn … 340xx-cfg1 installed ?
nvidia-xconfig is there https://packages.debian.org/buster/nvidia-xconfig
My ascii installation has both.
groucho@devuan:~$ apt list | grep libnvidia-legacy-340xx-cfg1
libnvidia-legacy-340xx-cfg1/oldstable,now 340.108-3~deb9u1 amd64 [installed,automatic]
groucho@devuan:~$ groucho@devuan:~$ apt list | grep nvidia-xconfig
nvidia-xconfig/oldstable 390.87-1~deb9u1 amd64
groucho@devuan:~$ nvidia-xconfig was there when I tried to install the driver (sorry for the lapse) but it would not work.
My sources list (from the Devuan GNU/Linux 3.0 (beowulf) amd64 - netinstall 20200526) are these:
deb http://pkgmaster.devuan.org/merged beowulf main non-free contrib
deb http://pkgmaster.devuan.org/merged beowulf-security main contrib non-free
# beowulf-updates, previously known as 'volatile'
deb http://pkgmaster.devuan.org/merged beowulf-updates main contrib non-free
deb http://pkgmaster.devuan.org/merged beowulf-backports main contrib non-freeI saw no reason to modify them as I understand that if a package is in the Debian repository it will then be in the Devuan repositories, save for the systemd stuff.
Thanks for your input.
Cheers,
A.
#1517 Re: Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-14 14:10:48
Hello:
Maybe need to modprobe /dev/nvidia* ?
Yes.
But like I mentioned previously, the files are not there.
... tried nvidia-xconfig ...
Not there either.
Before rebooting (and after) I tried apt purge nvidia-persistenced and then apt install nvidia-persistenced but it does not nstall.
The issue E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1 remains.
The only way out is apt purge *nvidia* to recover the desktop.
There seems to be a problem with the nvidia-persistenced package (seems to be a daemon) which will not start because the nvidia device files (/dev/nvidia*) are not where they should be.
Maybe a bug in the package?
Thanks for your input.
A.
#1518 Installation » [Solved] Beowulf - Nvidia legacy 340XX driver will not install. » 2020-09-13 22:50:50
- Altoid
- Replies: 45
Hello:
I'm attempting to install the Nvidia legacy 340XX driver to be able to use my three monitor setup in Beowulf.
The two or three times I have done this with different Linux distributions, it was a matter of transplanting a previously working xorg.conf file and 'maybe' tweaking it a bit, never had serious issues.
The first transplant to a Devuan installation was from PCLinuxOS to the Devuan Jesse and from then onwards.
This is the second time I am attempting to install the proprietary driver in Beowulf and as I know what will happen, I have avoided a reboot so I can get the data. ='7
Here's what synaptic had to say (previous driver installation was with apt but the printout was lost):
E: nvidia-persistenced: installed nvidia-persistenced package post-installation script subprocess returned error exit status 1
I then opened a terminal to see what was going on:
oot@devuan3:~# dkms status
nvidia-legacy-340xx, 340.108: added
root@devuan3:~# Seems the driver is installed (?)
So then I tried to see if anything was missing:
groucho@devuan3:~$ su -
Password:
root@devuan3:~# apt install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed. <--- THIS seems to be the problem.
After this operation, 0 B of additional disk space will be used.
Setting up nvidia-persistenced (418.56-1) ...
Starting NVIDIA Persistence Daemon
nvidia-persistenced failed to initialize. Check syslog for more details. <--- THIS seems to have caused the problem.
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
Errors were encountered while processing:
nvidia-persistenced
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@devuan3:~# This confirmed what synaptic said.
~# cat /var/log/syslog
--- snip ---
Sep 13 22:24:09 devuan3 nvidia-persistenced: Started (9411)
Sep 13 22:24:09 devuan3 nvidia-persistenced: Failed to query NVIDIA devices. Please ensure that the NVIDIA device files (/dev/nvidia*) exist, and that user 110 has read and write permissions for those files.
Sep 13 22:24:09 devuan3 nvidia-persistenced: Shutdown (9411)
--- snip ---root@devuan3:/# ls /dev/nvidia
ls: cannot access '/dev/nvidia': No such file or directory
root@devuan3:/# What's going on?
I will leave this here, reboot and see about cleaning up, otherwise I will not have X.
Any ideas welcome.
Thanks in advance,
A.
#1519 Re: Installation » openbox menu issue » 2020-09-13 22:12:08
Hello:
Found it: Command: pkexec pluma %f ...
... does not work.
According to the xfce page it should work:
Edit file as root
Name: Edit as root
Command: gksu put-your-favourite-text-editor-here %f
File pattern: *
Appears if selection contains: Text filesNote: You'll need to replace put-your-favourite-text-editor-here with your favourite text editor (e.g. mousepad or geany). Also, see previous note about gksu. -> Note: Some distributions no longer include gksu. Use pkexec instead.
https://docs.xfce.org/xfce/thunar/custo … le_as_root
What am I missing?
Thanks in advance,
A.
#1520 Re: Installation » openbox menu issue » 2020-09-13 02:06:53
Hello:
But the 'Custom actions' I hace set up in Thunar, such as "Edit as root" or "Open root Thunar here" use gksudo.
Command: gksu -l pluma %f and Command: gksu thunar %f in 'Edit' -> 'Configure custom actions ...'
How do I get them working with polkit?
Found it: Command: pkexec -l pluma %f and Command: pkexec thunar %f in 'Edit' -> 'Configure custom actions ...'
A question remains:
Would it be better to run lxpolkit instead of gnome-polkit?
Thanks for your input.
Cheers,
A.
#1521 Re: Installation » openbox menu issue » 2020-09-12 23:48:10
Hello:
So is the policykit-1 package installed?
Yes.
The gnome version.
That OnlyShowIn bit indicates that the program will only be autostarted for the listed desktops ...
... policykit-1 package and a graphical authentication agent need to be running ...
Both gparted and synaptic are working now.
Would it be better to run lxpolkit instead of this one?
Polkit is the modern way to run graphical applications ...
... minimises the security risks in comparison to su &sudo or gksu & gksudo.
Yes, I understand.
But the 'Custom actions' I hace set up in Thunar, such as "Edit as root" or "Open root Thunar here" use gksudo.
Command: gksu -l pluma %f and Command: gksu thunar %f in 'Edit' -> 'Configure custom actions ...'
How do I get them working with polkit?
... gparted running with su but ...
Why would I want to do that?
It is stupid! 8-D!
Thanks for your input.
Cheers,
A.
#1522 Re: Installation » openbox menu issue » 2020-09-12 22:22:09
Hello:
... any error messages if you run /usr/sbin/gparted directly in a terminal?
Yes.
groucho@devuan3:~$ /usr/sbin/gparted
localuser:root being added to access control list
Error executing command as another user: No authentication agent found.
localuser:root being removed from access control list
groucho@devuan3:~$ groucho@devuan3:~$ su
Password:
root@devuan3:/home/groucho# /usr/sbin/gparted
sh: 1: dmidecode: not found
======================
libparted : 3.2
======================In this last instance, via su (not su -), gparted ran.
root@devuan3:/home/groucho# su -
root@devuan3:~# /usr/sbin/gparted
(gpartedbin:2414): Gtk-WARNING **: 21:52:42.365: cannot open display:
root@devuan3:~# Can we see
grep -A2 gparted ~/.config/openbox/menu.xml
Of course ...
groucho@devuan3:~$ grep -A2 gparted ~/.config/openbox/menu.xml
<item label="gparted">
<action name="Execute">
<execute>/usr/sbin/gparted</execute>
</action>
</item>
groucho@devuan3:~$ Looking around I found /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop and the the executable is there.
But it's not being run:
/usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list pgrep -a polkit
Hmm ...
groucho@devuan3:~$ /usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list pgrep -a polkit
ERROR: openbox-xdg-autostart requires PyXDG to be installed
groucho@devuan3:~$ Interesting ...
But I previously ran apt-update, apt-upgrade and apt install -f and everything seemed to be right.
Seems the Openbox package needs to add this missing package to the depends list?
root@devuan3:~# apt update && apt upgrade && apt install -f
Hit:1 http://pkgmaster.devuan.org/merged beowulf InRelease
Hit:2 http://pkgmaster.devuan.org/merged beowulf-security InRelease
Hit:3 http://pkgmaster.devuan.org/merged beowulf-updates InRelease
Hit:4 http://pkgmaster.devuan.org/merged beowulf-backports InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@devuan3:~# groucho@devuan3:~$ su -
Password:
root@devuan3:~# apt install python-xdg
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
python-xdg
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 35.9 kB of archives.
After this operation, 169 kB of additional disk space will be used.
Get:1 http://pkgmaster.devuan.org/merged beowulf/main amd64 python-xdg all 0.25-5 [35.9 kB]
Fetched 35.9 kB in 1s (35.7 kB/s)
Selecting previously unselected package python-xdg.
(Reading database ... 64424 files and directories currently installed.)
Preparing to unpack .../python-xdg_0.25-5_all.deb ...
Unpacking python-xdg (0.25-5) ...
Setting up python-xdg (0.25-5) ...
root@devuan3:~# Right, now that python-xdg is installed, we continue and get this:
groucho@devuan3:~$ /usr/lib/x86_64-linux-gnu/openbox-xdg-autostart --list pgrep -a polkit
[ ]
File: /home/groucho/.config/autostart/xscreensaver.desktop
* Excluded by: Missing Exec field
[*]
File: /home/groucho/.config/autostart/xfce4-clipman-plugin-autostart.desktop
Executes: xfce4-clipman
[*] User folders update
File: /etc/xdg/autostart/xdg-user-dirs.desktop
Executes: xdg-user-dirs-update
[*] Wicd Network Manager Tray
File: /etc/xdg/autostart/wicd-tray.desktop
Executes: wicd-gtk --tray
[*] PulseAudio Sound System
File: /etc/xdg/autostart/pulseaudio.desktop
Executes: start-pulseaudio-x11
[ ] PolicyKit Authentication Agent
File: /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop
Executes: /usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
* Excluded by: OnlyShowIn (XFCE, Unity, X-Cinnamon)
[*] AT-SPI D-Bus Bus
File: /etc/xdg/autostart/at-spi-dbus-bus.desktop
Executes: /usr/lib/at-spi2-core/at-spi-bus-launcher --launch-immediately
[ ] gnome-disk-utility notification plugin for GNOME Settings Daemon
File: /etc/xdg/autostart/org.gnome.SettingsDaemon.DiskUtilityNotify.desktop
Executes: /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
* Excluded by: OnlyShowIn (GNOME)
[ ] Xfsettingsd
File: /etc/xdg/autostart/xfsettingsd.desktop
Executes: xfsettingsd
* Excluded by: OnlyShowIn (XFCE)
groucho@devuan3:~$ I removed XFCE to see if I could just use Openbox, which is probably the cause of what is happening.
Thanks for your input.
Cheers,
A.
#1523 Re: Installation » openbox menu issue » 2020-09-12 20:06:21
Hello:
... run the wrapper script at /usr/sbin/gparted directly from the menu entry.
obmenu -> /usr/sbin/gparted in the 'Execute' box does not work.
... install a graphical polkit authentication agent ...
Looking around I found /etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop and the the executable is there.
groucho@devuan3:~$ locate gnome-authentication-agent
/etc/xdg/autostart/polkit-gnome-authentication-agent-1.desktop
/usr/lib/policykit-1-gnome/polkit-gnome-authentication-agent-1
groucho@devuan3:~$ I also came upon lxpolkit on the web which in 2010 replaced gnome-polkit in LXDE.
Seems it is leaner and more suited to LXDE.
*Do not* use su or sudo to launch graphical applications with elevated permissions, it is stupid and dangerous.
Good to know.
But it was the only way I got synaptic and gparted to run in my VM with Openbox.
I now have the same problem ...
Thanks for your input.
A.
#1524 Installation » openbox menu issue » 2020-09-12 16:26:51
- Altoid
- Replies: 11
Hello:
I'm (slowly) installing Devuan3 on a spare drive in my ascii box so I can eventually migrate without any headaches.
One of the things I want to do is use Openbox instead of Xfce of which I have grown rather tired.
I have it on a skeleton VM installation albeint on a single screen (vis-a-vis my 3-screen ascii) and it works well enough form the time being.
I can start gparted there via lxterminal -e su - gparted but I would like to avoid using sudo.
Same with synaptic, which I keep to use as a GUI to look for applications as I am getting used to apt or apt-get.
So I try using lxterminal -e su - gparted but I only get a flicker on the screen.
My DM is SLiM and I wonder if this is not due to its starting X as root?
If I open the terminal and try to start gparted I get this:
~$ su -
Password:
~# gparted
(gpartedbin:3660): Gtk-WARNING **: 16:23:29.432: cannot open display:
~# Is there a way around this or do I have to install sudo and a set up sudoers?
Thanks in advance.
A.
#1525 Re: Installation » [Solved] Beowulf Netinstaller problem » 2020-09-07 00:29:01
Hello:
Any idea as to what may be going on here?
Solved by burning the *.iso to the SD Card again.
Curious thing as it did not happen the first time I installed Beowulf.
The installer was skipping a step, the one where it loaded applications, among them probably the one needed to format the drive to ext 3/4.
Otherwise (up to that point) it seemed to work properly.
Maybe some part of the SD Card got corrupted?
Cheers,
CIV
Board footer
