Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

deepforest · 2023-08-16 19:39:16

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 buffer

Last edited by deepforest (2023-08-16 19:40:54)

boughtonp · 2023-08-16 21:55:51

deepforest wrote:

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/

https://www.if-not-true-then-false.com/2020/inttf-nvidia-patcher/ wrote:

inttf NVIDIA 340.xx, 390.xx, 470.xx Patcher for Kernel 6.3/6.2/5.19/5.14/5.13 [BASH Script]

So you've run a random patch script for specific kernel versions against a kernel version it does not support, and are surprised that it doesn't work?

What makes you think this is in any way Devuan related? Have you tested against an equal Debian version and found it worked there?

Last edited by boughtonp (2023-08-16 21:57:00)

deepforest · 2023-08-16 22:13:19

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

Segfault · 2023-08-16 22:28:24

What's the big idea using nVidia blob with this old card. Use nouveau or Xorg modesetting driver. My laptop has newer card than yours, I tested it with blob and nouveau and modesetting and for 2D applications there is no difference, actually FOSS drivers are snappier.
Note, no FOSS Xorg driver will run if you pass nomodesetting to your kernel.

deepforest · 2023-08-17 21:59:52

syslog
https://pastebin.com/raw/zLGET6dY

watchdog: BUG: soft lockup - CPU#2 stuck for 78s! [Xorg:2143]

Segfault · 2023-08-18 14:38:34

So your nvidia kernel module is crashing. Not that unexpected with obsolete driver and newer operating system. I recite, ditch it. There is nothing to win by using the blob on this old card. Any hardware acceleration it may have had in its heyday is obsolete and useless now. Getting rid of proprietary driver which taints your system is a plus.

Last edited by Segfault (2023-08-18 14:40:55)

stopAI · 2023-08-18 16:02:37

deepforest wrote:

After upgrade Devuan to 6.4 kernel

Why do you need such a new kernel if you use old video card?

golinux · 2023-08-18 16:05:02

Humans are not rational . . .

deepforest · 2023-08-21 18:28:50

stopAI wrote:

deepforest wrote:
After upgrade Devuan to 6.4 kernel
Why do you need such a new kernel if you use old video card?

its simple only unstable have support of my legacy card
https://wiki.debian.org/NvidiaGraphicsD … on_340.108

golinux wrote:

Humans are not rational . . .

i see that you really "pro":)
https://wiki.debian.org/NvidiaGraphicsD … on_340.108

deepforest · 2023-08-21 18:31:48

Segfault wrote:

So your nvidia kernel module is crashing. Not that unexpected with obsolete driver and newer operating system. I recite, ditch it. There is nothing to win by using the blob on this old card. Any hardware acceleration it may have had in its heyday is obsolete and useless now. Getting rid of proprietary driver which taints your system is a plus.

Problem only at Devuan Ceres, at Artix and Fedora 38 all works good with 6.4 kernel + 340.108 patched

deepforest · 2023-08-21 18:35:58

Something progress in my question
This https://www.if-not-true-then-false.com/ … dia-guide/
not working at Ceres but working at Deadalus

PS at Ceres working this solution

apt install nvidia-legacy-340xx-driver

but have issue with

nvidia-persistenced failed to initialize

https://dev1galaxy.org/viewtopic.php?id=5881

Marjorie · 2023-08-24 14:58:18

deepforest wrote:

Something progress in my question
This https://www.if-not-true-then-false.com/ … dia-guide/
not working at Ceres but working at Deadalus
PS at Ceres working this solution
apt install nvidia-legacy-340xx-driver 
but have issue with
nvidia-persistenced failed to initialize
https://dev1galaxy.org/viewtopic.php?id=5881

If you use apt to install nvidia-legacy-340xx-driver it may well pull in the original unpatched /etc/init.d/nvidia-persistenced.
Have you tried replacing it with my patched version and then restarting it?

:~$ sudo service nvidia-persistenced restart

Last edited by Marjorie (2023-08-24 14:59:51)

deepforest · 2023-08-25 19:02:39

are you mean this script?
https://dev1galaxy.org/viewtopic.php?pid=20903#p20903
how use it?
now i am on Deadalus and cant chek it.
but i can do it in future if you talk me how to use those script.

Last edited by deepforest (2023-08-25 19:03:34)

golinux · 2023-08-25 19:17:17

@deepforest . . . There is no "Deadalus" at Devuan (or anyplace else afaik).

PLEASE stop posting erroneous technical information on this forum and correct your previous spelling errors that might confuse other users. I am tired of cleaning up your mess.

Then . . . learn how to spell DAEDALUS correctly so our search engine will find the actual Devuan distribution to which you are referring.

Thanks for helping to make this forum a more accurate resource for other users.

deepforest · 2023-08-26 01:46:09

ok, sorry:)
I'm not attentive and I don't know well English, its not my native language.

golinux · 2023-08-26 02:25:30

Well . . . your English is better than my Ukrainian and we can understand what you are trying to say. Thing is that if information related to your installation is misspelled, our search engine won't be able to find solutions to any problems you might solve. Just a bit more attention would be really appreciated. Thanks.

deepforest · 2023-08-26 19:03:17

thank you for your kindness and understanding

Marjorie · 2023-08-26 19:55:47

deepforest wrote:

are you mean this script?
https://dev1galaxy.org/viewtopic.php?pid=20903#p20903
how use it?
now i am on Deadalus and cant chek it.
but i can do it in future if you talk me how to use those script.

OK. I'm assuming that the only problem we are trying to address is with nvidia-persistenced.

My modiified nvidia-persistenced init script is as follows:

#!/bin/sh -e
#
# NVIDIA Persistence Daemon Init Script
#
# Copyright (c) 2013 NVIDIA Corporation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
# AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
# LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
# FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
# DEALINGS IN THE SOFTWARE.
#
# This is a sample System V init script, designed to show how the NVIDIA
# Persistence Daemon can be started.
#
# This sample does not rely on any init system functions, to ensure the
# widest portability possible.
#
# chkconfig: 2345 99 01
# description: Starts and stops the NVIDIA Persistence Daemon
# processname: nvidia-persistenced
#
### BEGIN INIT INFO
# Provides:         nvidia-persistenced
# Required-Start:   $local_fs
# Required-Stop:    $local_fs
# Default-Start:    2 3 4 5
# Default-Stop:     0 1 6
# Short-Description: Starts and stops the NVIDIA Persistence Daemon
# Description:      Starts and stops the NVIDIA Persistence Daemon
### END INIT INFO

NVPD=nvidia-persistenced
NVPD_BIN=/usr/bin/${NVPD}
NVPD_RUNTIME=/var/run/${NVPD}
NVPD_PIDFILE=${NVPD_RUNTIME}/${NVPD}.pid
NVPD_USER=nvpd
NVPD_ACTION=${1}

# Gracefully exit if the package has been removed.
test -x $NVPD_BIN || exit 0

# Get the value of the PID
if [ -f ${NVPD_PIDFILE} ]; then
 read -r NVPD_PID < "${NVPD_PIDFILE}"
# Is the daemon already running?
 if [ "${NVPD_PID}" ] ;then 
  if [ -d /proc/${NVPD_PID} ]
# Daemon is running, so stop it then start anew instance
   then
    case "${1}" in
     start)
      echo "NVIDIA Persistence Daemon already running" 
      NVPD_ACTION=restart
      ;;
     *)
      ;;
    esac
# Daemon not running, but there is a stale PID
   else
    echo "NVIDIA Persistence Daemon, stale PID removed"			
    unset NVPD_PID
    rm -rf "${NVPD_RUNTIME}"
  fi
 fi
fi

case "${NVPD_ACTION}" in
 start)
  echo "Starting NVIDIA Persistence Daemon"
# Execute the daemon as the intended user
  ${NVPD_BIN} --user ${NVPD_USER}
  ;;
 stop)
   echo "Stopping NVIDIA Persistence Daemon"
# Stop the daemon - its PID should have been read in
   [ ! -z "${NVPD_PID}" ] && kill ${NVPD_PID} &> /dev/null
    ;;
  restart)
   $0 stop
   sleep 2
   $0 start
    ;;		
  *) echo "usage: $0 {start|stop|restart}"
    ;;
esac

exit 0

1) With your mouse select all of the script and then copy it, using the "Control" and "c" keys together.

I use Cinnnamon, sudo and the gedit editor and will illustrate using these. If you use su - rather than sudo and another text editor just change to suit.

2) Open a terminal window.

3) in the terminal type:

sudo gedit /etc/init.d/nvidia-persistenced

This should open the nvidia-persistenced init code in the editor.

4) Select all the text with your mouse.

5) Press the 'Control' and' v' keys together to paste my version in place of the existing text.

6) Save the updated code. In 'gedit' there is a save button.

7) Close gedit.

7) in the terminal restart nvidia-persistenced by typing:

sudo service nvidia-persistenced restart

8) Close the terminal.

Last edited by Marjorie (2023-08-26 19:58:11)

deepforest · 2023-08-30 01:05:37

@Marjorie
Understood, replace original content ofsudo gedit /etc/init.d/nvidia-persistenced with yours version of script
Thank you i will try when will be at unstable

Last edited by deepforest (2023-08-30 01:06:38)

The officially official Devuan Forum!

#1 2023-08-16 19:39:16

Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#2 2023-08-16 21:55:51

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#3 2023-08-16 22:13:19

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#4 2023-08-16 22:28:24

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#5 2023-08-17 21:59:52

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#6 2023-08-18 14:38:34

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#7 2023-08-18 16:02:37

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#8 2023-08-18 16:05:02

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#9 2023-08-21 18:28:50

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#10 2023-08-21 18:31:48

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#11 2023-08-21 18:35:58

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#12 2023-08-24 14:58:18

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#13 2023-08-25 19:02:39

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#14 2023-08-25 19:17:17

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#15 2023-08-26 01:46:09

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#16 2023-08-26 02:25:30

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#17 2023-08-26 19:03:17

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#18 2023-08-26 19:55:47

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

#19 2023-08-30 01:05:37

Re: Devuan Ceres - X not starting at kernel 6.4 + 340.108 driver

Board footer