Slackware64-current boot and video issue on HP Z600

the_zone · 01-30-2022, 08:44 AM

Hello,

I have an older hp z600, with quadro fx 3800, which I want to use a test machine.
It does not boot correctly and I can not install the nvidia drivers on.

#1
I did a clean install of slackware64-current (29/01/2022) on this machine.
The machine got stuck at some uhci_hcd USB / IRQ enumeration.
I have no idea how to get a log, in text, after the machine hangs.

Click image for larger version

Name: Boot.jpg
Views: 25
Size: 235.9 KB
ID: 38227

When I tell the kernel to boot with "nomodeset", either as boot argument or lilo config, the machine continues to boot.

#2
Since the machine has a quadro fx-3800 video card I can either use the nouveau driver or the proprietry nvidia driver.
However the previous option in #1 prohibits the machine using the nouveau driver.

I succesfully installed the installed the nvidia 340 driver with sbopkg.
However, when using this driver, after executing nvidia-xconfig, I get :

Code:

xauth:  file /root/.serverauth.1649 does not exist


X.Org X Server 1.20.14
X Protocol Version 11, Revision 0
Build Operating System: Slackware 15.0 Slackware Linux Project
Current Operating System: Linux testserver.noyc.local 5.15.17 #1 SMP PREEMPT Thu Jan 27 12:22:59 CST 2022 x86_64
Kernel command line: BOOT_IMAGE=Linux ro root=805 nomodeset
Build Date: 26 December 2021  04:51:07PM
 
Current version of pixman: 0.40.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jan 30 16:30:52 2022
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.15.17
modprobe: FATAL: Module nvidia not found in directory /lib/modules/5.15.17
(EE) 
Fatal server error:
(EE) no screens found(EE) 
(EE) 
Please consult the The X.Org Foundation support 
	 at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.

Anyone suggestions?

best regards

Simon

MDKDIO · 01-30-2022, 09:26 AM

Try build the legacy driver manually instead
Using

KERNEL=5.15.17 ./nvidia-kernel.SlackBuild

And don't forget the...
"The xf86-video-nouveau-blacklist package from /extra is required."

as the README says.

See if that helps

the_zone · 01-31-2022, 04:11 AM

I did exactly that and it keeps complaining that the modules can not be found.

The number of threads on nvidia issues are enormous and do not make things less complicated

LuckyCyborg · 01-31-2022, 05:19 AM

@OP

You need to use the legacy NVIDIA driver 340.108 from Ponce's SBo repository

https://github.com/Ponce/slackbuilds...gacy340-driver
https://github.com/Ponce/slackbuilds...gacy340-kernel

the_zone · 01-31-2022, 06:17 AM

@LuckyCyborg
How is that package any different from either slackbuilds or sbopkg ?

As a test I installed I installed Slackware64-14.2. The driver installed without any issues.
Even from the NVIDIA*.run script.

So either is has to do with:
- the supported kernel
- the way the package (sbopkg/slackbuilds) is created and installs the modules in the correct path

br,

ST

LuckyCyborg · 01-31-2022, 06:23 AM

@OP

Slackware (soon to be) 15.0 is highly different of Slackware 14.2 (after over 5 years of evolution) and Ponce adapts the SBo packages to work with -current.

As you certainly know, the SBo still targets the 14.2 release.

Anyway, I for one I would look for patches for the kernel modules. From what I know, 340.x series is already abandoned by NVIDIA and I doubt that there is native support for the 5.15.x kernels.

the_zone · 01-31-2022, 07:11 AM

Quote:

Slackware (soon to be) 15.0 is highly different of Slackware 14.2 (after over 5 years of evolution)

That is what is to be expected

Quote:

and Ponce adapts the SBo packages to work with -current.
As you certainly know, the SBo still targets the 14.2 release.

Even with the adjustments in the sbopkg.conf script, being REPO_NAME, REPO_BRANCH, to -current ?

Quote:

Anyway, I for one I would look for patches for the kernel modules. From what I know, 340.x series is already abandoned by NVIDIA and I doubt that there is native support for the 5.15.x kernels.

Indeed, Ah well this again is to be expected when working with old hardware.

br

ST

JayByrd · 01-31-2022, 11:33 AM

Quote:

Originally Posted by LuckyCyborg

@OP...Anyway, I for one I would look for patches for the kernel modules. From what I know, 340.x series is already abandoned by NVIDIA and I doubt that there is native support for the 5.15.x kernels.

@OP
This is correct: see this page.

Quote:

Originally Posted by the_zone

Indeed, Ah well this again is to be expected when working with old hardware.

True, but these drivers can be made to work with Slackware -current by applying some patches.

I've gotten the even older 304.x series nVidia kernel module built and running on -current. (Tested on kernels 5.13.x through 5.17-rc2.)

You might want to have a look at my patches, as many of them probably can be adapted to work with the 340.x series. (In fact, several of "my" patches were actually written for 340.x and I had to adapt them to work on 304.x. As to the ones I developed myself specifically for the 304.x, I'm confident they could be similarly adapted to the 340.x series.)

UPDATE: It turns out that minimyth2 on github has been back at work these last months and has developed more patches specifically for nvidia 340.x series, presumably keeping it working up to kernel v5.16.x. You can get them here.