You are not logged in.
its not "random" script
its working solution
its working for me at Artix(6.4kernel) and Fedora(6.4kernel) but not at Devuan(6.4kernel)
6.3 its mean 6.3+ kernel support
source for patch is here
https://aur.archlinux.org/packages/nvidia-340xx
After upgrade Devuan to 6.4 kernel
and install driver from here(usual it works good)
https://www.if-not-true-then-false.com/ … a-patcher/
Xorg trying but not start
here logs
https://pastebin.com/raw/Cfi8rWLi
[ 35.081] (EE) NVIDIA(GPU-0): EVO Push buffer channel allocation failed
[ 35.085] (EE) NVIDIA(GPU-0): Failed to allocate EVO core DMA push bufferNot a thing. Have never had a display issue on Devuan.
o really?:)
may be its because you not using gf9800gtx with standalone drivers!?:)
Are you really admin here? i am not sure because you do not answer to subject but spaming flood:)
If you cant give true help - pass throgh with silence.
its not unstable issue
what you can say about xorg logs?
use nouveau
desktop not load
console is working
cant upgrade now
https://ibb.co/sPYkHH2
kernel panic resolved
installed driver 340.108 6.3+
now Xorg not starting
here Xorg logs
https://fex.net/s/kaa6r4s
kernel panic after reboot
https://ibb.co/wK4Nhwn
Hi again Folks!)
I have situation upgrading Ceres from kernel 6.1 to 6.4
Is there solution for that?
Why its happens?
I use standalone patched legacy 340 driver for my gf9800gtx
https://aur.archlinux.org/packages/nvidia-340xx
https://www.if-not-true-then-false.com/ … dia-guide/
root@home:/# dpkg -l *nvidia*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================================-============-============-=================================
un libgldispatch0-nvidia <none> <none> (no description available)
un libnvidia-encode1 <none> <none> (no description available)
un nvidia-alternative <none> <none> (no description available)
un nvidia-legacy-340xx-vdpau-driver <none> <none> (no description available)
un nvidia-legacy-390xx-vdpau-driver <none> <none> (no description available)
un nvidia-libopencl1-dev <none> <none> (no description available)
un nvidia-tesla-418-vdpau-driver <none> <none> (no description available)
un nvidia-tesla-440-vdpau-driver <none> <none> (no description available)
un nvidia-vdpau-driver <none> <none> (no description available)
root@home:/# dkms status
nvidia/340.108, 6.1.0-9-amd64, x86_64: installed
root@home:/# root@home:/home/freeartist-devuan# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
clearlooks-phenix-deepsea-theme g++-12 gcc-12-base:i386 glx-alternative-mesa libavdevice59 libavfilter8 libavformat59 libcaca-dev libcodec2-1.0 libjpeg-turbo-progs libmujs2 libnetpbm11
libnvidia-legacy-340xx-eglcore libnvidia-legacy-340xx-eglcore:i386 libnvidia-legacy-340xx-glcore libnvidia-legacy-340xx-glcore:i386 libplacebo208 libpostproc56 libqt5sql5
libqt5sql5-sqlite libslang2-dev libstdc++-12-dev libswscale6 libturbojpeg0 linux-image-5.10.0-21-amd64 linux-image-6.1.0-7-amd64 netpbm update-glx
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up linux-headers-6.4.0-2-amd64 (6.4.4-3) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.4.0-2-amd64.
Sign command: /lib/modules/6.4.0-2-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.4.0-2-amd64 -j4 module KERNEL_UNAME=6.4.0-2-amd64; make -C uvm module KERNEL_UNAME=6.4.0-2-amd64 KBUILD_EXTMOD=/var/lib/dkms/nvidia/340.108/build/uvm...(bad exit st
atus: 2)
Error! Bad return status for module build on kernel: 6.4.0-2-amd64 (x86_64)
Consult /var/lib/dkms/nvidia/340.108/build/make.log for more information.
dkms autoinstall on 6.4.0-2-amd64/x86_64 failed for nvidia(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.4.0-2-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.4.0-2-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.4.0-2-amd64 (--configure):
installed linux-headers-6.4.0-2-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-amd64:
linux-headers-amd64 depends on linux-headers-6.4.0-2-amd64 (= 6.4.4-3); however:
Package linux-headers-6.4.0-2-amd64 is not configured yet.
dpkg: error processing package linux-headers-amd64 (--configure):
dependency problems - leaving unconfigured
Setting up linux-image-6.4.0-2-amd64 (6.4.4-3) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.4.0-2-amd64.
Sign command: /lib/modules/6.4.0-2-amd64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub
Building module:
Cleaning build area...
make -j4 KERNELRELEASE=6.4.0-2-amd64 -j4 module KERNEL_UNAME=6.4.0-2-amd64; make -C uvm module KERNEL_UNAME=6.4.0-2-amd64 KBUILD_EXTMOD=/var/lib/dkms/nvidia/340.108/build/uvm...(bad exit st
atus: 2)
Error! Bad return status for module build on kernel: 6.4.0-2-amd64 (x86_64)
Consult /var/lib/dkms/nvidia/340.108/build/make.log for more information.
dkms autoinstall on 6.4.0-2-amd64/x86_64 failed for nvidia(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.4.0-2-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.4.0-2-amd64 (--configure):
installed linux-image-6.4.0-2-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-amd64:
linux-image-amd64 depends on linux-image-6.4.0-2-amd64 (= 6.4.4-3); however:
Package linux-image-6.4.0-2-amd64 is not configured yet.
dpkg: error processing package linux-image-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-headers-6.4.0-2-amd64
linux-headers-amd64
linux-image-6.4.0-2-amd64
linux-image-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@home:/home/freeartist-devuan# how you install nvidia 340 driver on Chimaera?
https://dev1galaxy.org/viewtopic.php?id=5553
what relations between "SATA 'AHCI' mode" and "nvidia-legacy-340xx"?
340.108 last legacy supported driver by linux for this GPU
thouse was my thread at mint forum and there problem was not with Qt
make bug report
https://bugs.debian.org/cgi-bin/bugrepo … ug=1031489
ps Olav, anyway thank you for attention for my question
ok, thank you
use reportbug tool but have error
Default preferences file written. To reconfigure, re-run reportbug with the "
--configure" option.
Please enter the name of the package in which you have found a problem, or type
'other' to report a more general problem. If you don't know what package the
bug is in, please contact debian-user@lists.debian.org for assistance.
> other
Please enter the name of the package in which you have found a problem, or
choose one of these bug categories:
1 amprolla Everything related to amprolla
2 arm-sdk The ARM SDK and images (RPI & Co.)
3 bugs.devuan.org Issues related to Devuan BTS itself
4 devuan-desktop Anything related to Devuan desktop
5 devuan-installer Anything related to the Devuan installer
6 devuan-project everything Devuan-related which is not otherwise
categorised
7 devuan-www Everything related to the websites
8 iso-mirrors Everything relating to the ISO media mirrors
9 minimal-live The Devuan minimal live image
10 package-mirrors Everything related to package repository mirrors
Enter a package: 3
*** Welcome to reportbug. Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of the submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.
Using 'deepforest <a.v.procenko@gmail.com>' as your from address.
Traceback (most recent call last):
File "/usr/bin/reportbug", line 2392, in <module>
main()
File "/usr/bin/reportbug", line 1092, in main
return iface.user_interface()
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/bin/reportbug", line 1737, in user_interface
elif 'devuan' in pkgversion:
^^^^^^^^^^^^^^^^^^^^^^
TypeError: argument of type 'NoneType' is not iterable
freeartist-devuan@home:~$ also qtdiag not work
freeartist-devuan@home:~$ qtdiag
qtdiag: could not find a Qt installation of ''
freeartist-devuan@home:~$ On Ceres same situation that at Sid
https://unix.stackexchange.com/question … t-software
With nouveau all working good. But after installing legacy 340.108 nvidia driver for my gf9800 i have Segmentation Fault at launching all Qt GUI software. And opposite, Qt works again after uninstalling nvidia driver.
But very strange that if i run Qt soft via debugging tools such gdb or strace i have no errors.
gdb ./doomseeker
strace ./doomseekerSame is with Qbittorrent
https://i.stack.imgur.com/ehbCm.png
and 2048-Qt
https://i.stack.imgur.com/OTV6q.png
Only two Qt application starting normally - CMake GUI and Audacious Qt theme
Segmentation fault
#include <QApplication>
int main(int argc, char **argv)
{
QApplication app(argc, argv);
return 0;
}Who can fix this? Debian or Qt developers?
its only at Ceres, not Chimaera
Devuan drop 340.108 like Debian at stable and leave it at unstable
?
apt-cache search nvidia-legacy-340xx
https://pastebin.com/raw/q3D8v15P
root@home:/etc/apt# apt install nvidia-legacy-340xx-kernel-dkms --no-install-recommends
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package nvidia-legacy-340xx-kernel-dkms
root@home:/etc/apt# sources.list
# deb cdrom:[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012]/ chimaera contrib main non-free
# deb cdrom:[Devuan GNU/Linux 4.0 chimaera amd64 - desktop 20211012]/ chimaera contrib main non-free
deb http://deb.devuan.org/merged chimaera main contrib non-free
deb-src http://deb.devuan.org/merged chimaera main contrib non-free
deb http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
deb-src http://pkgmaster.devuan.org/merged chimaera-security main contrib non-free
# chimaera-updates, to get updates before a point release is made;
# see https://www.debian.org/doc/manuals/debian-reference/ch02.en.html#_updates_and_backports
deb http://deb.devuan.org/merged chimaera-updates main contrib non-free
deb-src http://deb.devuan.org/merged chimaera-updates main contrib non-free@blackhole reported
nobody knows?
soory, my mistake, i mean what difference between
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.0.0_amd64_desktop.iso 3.5gb
and
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.1_0_amd64_pool1.iso 4.7gb
why so different size?
both using non fefracta installer?
Thanks.
So, may be this script not working on chimaera(stable) because this driver is dropped on stable debian?
But still supported on sid and because working on ceres?
So, no way to make it working on chimaera?
Or just true way is using 340.108 from devuan repo?
But from devuan repo 340.108 is working but not perfectlly installs (nvidia-settings launch only from terminal and i need to delete some modprobe nvidia files because do not want see warnings during booting process)
deepforest wrote:why i cant here do the same?
As HoaS implied in the very first reply to this thread, you can. With the not-refracta bootable install image.
If you insist on using the live image, a workaround has already been suggested.
Complaining about a missing feature in refracta installer achieves nothing. If you really want it, nobody is stopping you from implementing it yourself.
Thank you.
This is non refracta?
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/
and what difference between
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.0.0_i386_desktop.iso
and
https://mirror.leaseweb.com/devuan/devuan_chimaera/installer-iso/devuan_chimaera_4.1_0_amd64_pool1.iso
?
aluma wrote:1. During installation, formatting is mandatory for the "/" partition and is not allowed without a direct user selection for the /home partition.
I don't understand what you are saying here, but it sounds wrong.
It is not mandatory for the installer to format the chosen partition(s) but it is mandatory for them to have a filesystem if you want them to contain files, and formatting is the default setting.
You can partition and format before running the installer and tell the installer not to format. That's a checkbox in the options menu of the graphical installer and it's a config file setting in the cli installer.
You have the choice to install the entire system to one partition, or you could optionally have separate partitions for /boot and/or /home.
The installer doesn't know what to do with your old home or the user configs it contains. It's up to you to figure out any conflicts caused by mismatched or missing config files caused by sharing a home between two different operating systems.
as usual, on others distros i can use one /home partition for many linux os with separeted user folders, why i cant here do the same?
steve_v the first make offencive to me
i am just ask, have someone experience with script from first post?
and why if it worked on unstable, not working at stable?
driver from script is successfully installed but after, X do not starting.
deepforest wrote:solution for normal distros but not for "knee develop" semi working devuan
ROFL. Devuan not including out-of-tree kernel patches for fossilised proprietary drivers is not a bug. Go hassle Nvidia to fix their trash.
All your threads are this same BS. Vague problem descriptions with insufficient debugging information, pigheaded insistence on doing things some $other_os way, then a bunch of complaining when you inevitably break your install. I'm done trying to help you, you just don't listen.
Bye now, have fun. I await your next reinstall thread with bated breath (and popcorn).
no, its devuan piece of glitch bull shit
deepforest wrote:340.108 driver
You won't get that version to run with a 5.5 or newer kernel without a kernel patch and recompile of the kernel. I believe the release you are running is based on the 5.10 kernel.
Try searching the web for "Linux 5.10 nvidia 340.108"
you read thouse solution with attention? old driver patched for new kernels!
Because following some random blog post and using third-party executable installers rather than the repos is a sure-fire way to mess up your install?
The debian documentation and discussion boards are replete with warnings not to do this, and for good reason.Other than that, if you want help you will need to provide a whole lot more information (with command output and such in code tags, not blurry screenshots) than just "why not working". Nobody here is psychic, and I for one am all out of patience for guessing games.
its not random solution
its fully 100% solution for normal distros but not for "knee develop" semi working devuan