You are not logged in.
deepforest wrote:i.e. using linux - problems should be expected
No, not really.
I have an AMD card that functions perfectly under Linux thanks to the efforts of the (paid!) AMD developers who have open sourced their graphics stack (apart from the firmware) and contribute actively to Linux development.
In Windows I cannot use the open source amdgpu driver so I have to use AMDGPU-PRO instead and the performance is *terrible*, especially in respect of power consumption and temperature management. The blobby driver is shit.
Agree, Can you you explain why linux community hate nvidia? A am also love AMD too for free and opensource politics. But now many software and games developers is nvidia oriented.
Here example https://developer.blender.org/T96614
Devuan aren't going to patch the kernel to fix a problem introduced by NVIDIA. That would be ridiculous.
Problem already fixed https://aur.archlinux.org/packages/nvidia-340xx
Devuan or Devian devs must just add it to repo
ps for me working this solution https://www.if-not-true-then-false.com/ … a-patcher/
it is stuck 18 seconds on "Initializing extension XINERAMA"
try disable, but no result
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Mouse0" "CorePointer"
Option "Xinerama" "0"
EndSection
Section "Files"
EndSection
Section "ServerFlags"
Option "IgnoreABI" "1"
Option "Xinerama" "0"
EndSection
Yes but if the ABI isn't supported then problems should be expected.
i.e. using linux - problems should be expected
deepforest wrote:Head_on_a_Stick wrote:The proprietary drivers are not part of the official Devuan release either.
Why? Devuan not supported any proprietary drivers!?
Because the source code is not available. The drivers are available from the non-free component of the repositories as a convenience for users but that component is not considered part of the official release.
and what? nvidia have linux driver that patched by community for new kernels. so its devuan or debian issue that it not apply patched diver in his repo.
There is also this:
X.Org log wrote:[ 44.886] (II) LoadModule: "nvidia" [ 44.887] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so [ 45.134] (II) Module nvidia: vendor="NVIDIA Corporation" [ 45.134] compiled for 4.0.2, module version = 1.0.0 [ 45.134] Module class: X.Org Video Driver [ 45.134] ================ WARNING WARNING WARNING WARNING ================ [ 45.134] This server has a video driver ABI version of 25.2 that this driver does not officially support. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [ 45.134] =================================================================
its just warning
it is stuck 18 seconds on "Initializing extension XINERAMA"
thanx, i will try to disabe it
1. install an SSD
2. upgrade your hardware
You're welcome
booting is quick but appearing desktop is ~20sec
Have you tried nouveau?
I'll get my coat...
with nouveau is much longer then proprietary, also nouveau have poor performance in games
The proprietary drivers are not part of the official Devuan release either.
Why? Devuan not supported any proprietary drivers!?
ps in my case, 340 is still supported bu Debian Sid, or i am wrong? Sid been supported 340 untill 5.17, what happend now?
legacy PC - c2q(q6600), gf9800gtx, hdd
xorg log https://pastebin.com/raw/wyJC77cb
deepforest wrote:This is Debian issue
Not really. Even if you are correct the proprietary drivers are not part of the official distribution.
So Devuan issue? I have error("driver not installed") after installing 340 driver from Devuan Ceres repo on 5.18. On 5.17 all installing and works good.
This trick is working
https://www.if-not-true-then-false.com/ … a-patcher/
you need add to xorg.conf this lines to working
Section "ServerFlags"
Option "IgnoreABI" "1"
EndSection
This is Debian issue
deepforest wrote:How to fix?
Ask NVIDIA to stop being such a bunch of twats. Or buy a graphics card from a manufacturer that doesn't hate the open source community.
This is not a Devuan problem, it is an NVIDIA problem.
Before 5.18 all works and working on Fedora 36 but not on Ceres. Community patching drivers for new kernels. But now on Ceres drivers not working, why?
On Ceres this driver even installing with error now. On 5.17 all works.
Patched driver for 5.18 installed ok, but not starting.
This is problem of Debian or Devuan?
Ok. For me all works normal until now. Both "unstable" Sid and Ceres, only this two deb based distros that bring me worked nvidia 340 drivers. But now something broken. How to fix?
even this trick not works https://www.if-not-true-then-false.com/tag/debian/
Xorg log https://pastebin.com/raw/pC6yksyD
What is wrong with Ceres?
All working before kernel was updated to 5.18 So this legacy driver from Ceres repo not patched for this kernel?
SO PROBLEM NOT SOLVED, i have same issue
https://dev1galaxy.org/viewtopic.php?id=2259
So. My solution.
1. Install or upgrade to Devuan sid
2. go to recovery mode and install justapt install linux-headers-$(uname -r) build-essential apt install nvidia-legacy-340xx-kernel-dkms
3. after removed nvidia.conf and "update-initramfs -u" from
etc/modules-load.d etc/modprobe.d
All works like a charm! Enjoy of Freedom! Glory and Long live to Devuan team!
SO its no solved yet
Now i have this errors
Fri Mar 18 21:55:14 2022: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.0-12-amd64
Sun Mar 20 02:16:29 2022: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.16.0-5-amd64
Mon May 2 20:15:20 2022: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.17.0-1-amd64
What this files do?
/etc/modprobe.d/nvidia.conf 716/716 100%
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
alias char-major-195* 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
I am on Ceres. I see this messages during boot. Nvidia driver works good. Why i see this messages and how i can remove them?
https://imgur.com/a/GP0lgbG
NO, its old issue(
If i do this manipulation
https://dev1galaxy.org/viewtopic.php?pid=35372#p35372
i have error
Fri Mar 18 21:55:14 2022: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.10.0-12-amd64
Sun Mar 20 02:16:29 2022: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.16.0-5-amd64
Mon May 2 20:15:20 2022: modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.17.0-1-amd64
Its all "red eyed nerding" too complex for me:/
How preset default volume in Audacious? Its always 100% after rebooting.
Pulseaudio volume is controlled by
freeartist@devuan:~$ sudo nano /etc/pulse/default.pa
# Set volume to 50% on boot
set-sink-volume 0 32768
But Audacious volume is reset to 100% after every boot
after xinit command
/usr/local/lib/X11/fvwm95/XClassTaskbar
not found
Apologies, my bad. When i set default FVWM95 i.e.
DEFAULT_SESSION=startfvwm95
case $1 in
lxqt)
exec startlxqt
;;
xfce4)
exec startxfce4
;;
mate)
exec startmate
;;
fvwm95|*)
exec startfvwm95
;;
#exec $DEFAULT_SESSION
#;;
esac
Nothing is happened. After reboot or change session, Slim not enter to fvwm95, Slim sty at login screen.
@ralph.ronnquist
Thank you very much! Now, after clearing /usr/include/ its installs good.
But how now i can use it? When i do logout and press F1 on login Slim screen i do not see FVWM96 session.
Here my /home/freeartist/.xinitrc
DEFAULT_SESSION=startxfce4
case $1 in
lxqt)
exec startlxqt
;;
xfce4|*)
exec startxfce4
;;
mate)
exec startmate
;;
fvwm95)
exec startfvwm95
;;
#exec $DEFAULT_SESSION
#;;
esac