LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-06-2019, 11:43 AM   #16
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,483

Rep: Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528

Quote:
Originally Posted by rogan View Post
They've had maybe 25 years to join the train, or at least release info, to get their
chips supported natively. One of the last dinosaurs in the business.
I wan't offended being well aware and even understanding of Linus's position and frustration. I'm also a big fan of OSS but realize the GPL was crafted exactly as it is to allow companies, even proprietary ones, to profit from Linux support. I'm not a kernel developer so I don't share Linus's frustration as a simple User. I doubt his 2012 rant did much to change nVidia's stance but it is possible that AMD/Ati's efforts in OSS might. I have spent thousands of dollars on nothing but nVidia graphics since 1995 but I am beginning to consider AMD and I very much doubt I am alone in this. Every time I bought a new card I wrote nVidia to tell them I'd bought yet another exactly because of their Linux support. If I switch to AMD I will write both of them to tell them why.

In the meantime I am just incredibly grateful to nVidia for being THE early supporter of almost every so-called "alternative" OpSys ever made with quality drivers. Had they not, it is unlikely that AMD/Ati ever would have. If we consider the value and importance of ANY accelerated 3D drivers to the viability and success of Linux, it seems to me Linus may have been just "flexing" AFTER Linux already had grown partly, maybe largely, because of nVidia's expense and efforts to support anything but MS.
 
3 members found this post helpful.
Old 11-06-2019, 12:12 PM   #17
cwizardone
Senior Member
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" & Xfce.
Posts: 4,960
Blog Entries: 1

Rep: Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399Reputation: 2399
@enorbet,
Well said!
 
Old 11-06-2019, 02:15 PM   #18
rogan
Member
 
Registered: Aug 2004
Distribution: Slackware
Posts: 197

Rep: Reputation: 84
enorbet: I mostly agree with you stance on this, but I still consider theirs an outdated and in the long run impossible attitude. They are BIG contributors to the kernel project, yet they won't release a single spec on any of their graphics products so someone can write an open driver for it... Why ?

Their attitude towards this project is to contribute when there is a clear and immediate gain for them in doing so, as with ARM, and to contribute absolutely nothing otherwise. I'm not saying that they should be obliged to do so, but I for one don't particularly trust binary only drivers and the hassle that follows, so I avoid using them if there's a way.
 
Old 11-07-2019, 12:03 AM   #19
Lockywolf
Member
 
Registered: Jul 2007
Posts: 272

Rep: Reputation: 79
The nvidia-legacy390-kernel doesn't build with the following error:

Code:
CC [M]  /tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.o
In file included from /tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.c:13:
/tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/common/inc/nv-linux.h:1799:6: error: "NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef]
 1799 | #if (NV_BUILD_MODULE_INSTANCES != 0)
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.c:39:6: error: "NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef]
   39 | #if (NV_BUILD_MODULE_INSTANCES != 0)
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.c: In function ‘nv_init_module’:
/tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.c:349:6: error: "NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef]
  349 | #if (NV_BUILD_MODULE_INSTANCES != 0)
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
/tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.c: In function ‘nv_exit_module’:
/tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.c:364:6: error: "NV_BUILD_MODULE_INSTANCES" is not defined, evaluates to 0 [-Werror=undef]
  364 | #if (NV_BUILD_MODULE_INSTANCES != 0)
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:266: /tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel/nvidia/nv-frontend.o] Error 1
make[1]: *** [Makefile:1649: /tmp/SBo/NVIDIA-Linux-x86_64-390.129/kernel] Error 2
make[1]: Leaving directory '/usr/src/linux-5.4-rc6'
make: *** [Makefile:81: modules] Error 2
Where exactly this NV_BUILD_MODULE_INSTANCES has to be defined I am not sure. The Makefile suggests that some versions of Kbuild read the Kbuild file, and some read the Makefile, so the patch should be trivial, but I am not that familiar with Kbuild.
 
Old 11-07-2019, 02:43 AM   #20
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 95

Rep: Reputation: Disabled
How about these patchs https://git.archlinux.org/svntogit/p...s/nvidia-390xx for nvidia-390xx?
 
Old 11-07-2019, 05:12 AM   #21
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,048

Rep: Reputation: Disabled
Quote:
Originally Posted by TurboBlaze View Post
How about these patchs https://git.archlinux.org/svntogit/p...s/nvidia-390xx for nvidia-390xx?
the only one of them that's actually applied in the PKGBUILD is for kernels < 4.16.
AFAIK there are no patches available that let 390.129 build on kernels 5.4.x (for previous versions they still build) yet (hope someone can provide them soon)...

Last edited by ponce; 11-07-2019 at 05:14 AM.
 
Old 11-07-2019, 07:47 AM   #22
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware
Posts: 1,968
Blog Entries: 5

Rep: Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114Reputation: 2114
First issue running this kernel - 24 hours or so after install. I was working away doing nothing in particular [browsing, Telegram] - laptop screen goes black, couldn't get to a terminal, nothing would bring it back. Had to REISUB.

Back to 4.19.76 for now.

Quote:
Originally Posted by AlleyTrotter View Post
nearly 700 views and 17 reply and not one person thought this was a useful post
SHEESE!
I found out about it in the main kernel thread, others may have seen the changelog. People are more likely to first read a thread they have already subscribed to since they get notifications.

Last edited by Lysander666; 11-07-2019 at 07:56 AM.
 
2 members found this post helpful.
Old 11-08-2019, 10:50 AM   #23
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys for decades while testing others to keep up
Posts: 2,483

Rep: Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528Reputation: 2528
Quote:
Originally Posted by rogan View Post
enorbet: I mostly agree with you stance on this, but I still consider theirs an outdated and in the long run impossible attitude. They are BIG contributors to the kernel project, yet they won't release a single spec on any of their graphics products so someone can write an open driver for it... Why ?
We could ask IBM if reverse engineering a la Compaq affected their revenue and their market position. Please note that there used to be a dozen graphics systems/chips companies with foundries. Now there are essentially three. It is a highly competitive market area. If secrecy wasn't an important tool to security and longevity, there would never have been laws regarding encryption and some government officials wouldn't be all but demanding back doors in encryption. Are you going to allow backdoors into your PCs? When you park your car in town do you leave the keys in it?

Quote:
Originally Posted by rogan View Post
Their attitude towards this project is to contribute when there is a clear and immediate gain for them in doing so, as with ARM, and to contribute absolutely nothing otherwise. I'm not saying that they should be obliged to do so, but I for one don't particularly trust binary only drivers and the hassle that follows, so I avoid using them if there's a way.
As I mentioned I've spent thousands of dollars since 1995 and all of them with nVidia and since 1999 all of those have run Linux. Prior to that I ran IBM's OS/2 which nVidia also supported with a binary driver. Since 1995 I can count on one hand the number of problems I've had with these drivers. Appropriate to this thread, my install of -Current is now successfully running 5.4-rc6 (compiled from source) with the NVIDIA-linux-X86_64.run blob installer. No issues once nVidia quickly addressed the "Module.symvers" change.

FWIW I am attracted to the ease provided by current development of OSS kernel support of AMD/Ati and will be watching that carefully even if it will likely be 3-5 years before I seek an upgrade for my Main's GTX-1070 Ti. I suspect this will be pressure where it counts for nVidia (and for we Linux users), not so much just from me, but as a trend.

Last edited by enorbet; 11-08-2019 at 10:53 AM.
 
1 members found this post helpful.
Old 11-09-2019, 12:48 AM   #24
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,309

Rep: Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938
Failure to boot on 32-bit

Anybody else having trouble booting the generic 5.4.0-rc6-smp kernel from /testing in Slackware-current? I am getting a kernel panic (see attached screenshots)
I have no problems with the 4.19.82 kernel on this 32-bit hardware.
Also no problems with the generic 5.4.0-rc6 kernel on 64-bit hardware.
Attached Thumbnails
Click image for larger version

Name:	wsnapshot5.png
Views:	35
Size:	191.9 KB
ID:	31792   Click image for larger version

Name:	wsnapshot6.png
Views:	28
Size:	178.8 KB
ID:	31793  
 
Old 11-09-2019, 01:10 AM   #25
Lockywolf
Member
 
Registered: Jul 2007
Posts: 272

Rep: Reputation: 79
Did you try booting without a microcode update?
 
Old 11-09-2019, 02:09 AM   #26
TurboBlaze
Member
 
Registered: Jan 2018
Location: Russian Federation, Lipetsk region, Dankov
Distribution: Porteus
Posts: 95

Rep: Reputation: Disabled
Quote:
Originally Posted by ponce View Post
AFAIK there are no patches available that let 390.129 build on kernels 5.4.x
NVIDIA 390.132 Linux Driver Released For Legacy Fermi Support
 
2 members found this post helpful.
Old 11-09-2019, 03:22 AM   #27
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,309

Rep: Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938Reputation: 1938
@Lockywolf - I have not attempted to put a microcode update on this PC.
 
Old 11-09-2019, 04:32 AM   #28
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 195

Rep: Reputation: 131Reputation: 131
Quote:
Originally Posted by allend View Post
Anybody else having trouble booting the generic 5.4.0-rc6-smp kernel from /testing in Slackware-current? I am getting a kernel panic (see attached screenshots)
I have no problems with the 4.19.82 kernel on this 32-bit hardware.
Also no problems with the generic 5.4.0-rc6 kernel on 64-bit hardware.
Yup, same thing happened to me when testing 5.4.0-rc6-huge-smp on an old 32-bit netbook. The huge non-smp kernel boots OK, though.
 
1 members found this post helpful.
Old 11-09-2019, 02:03 PM   #29
ttk
Member
 
Registered: May 2012
Location: Sebastopol, CA
Distribution: Slackware64
Posts: 886
Blog Entries: 27

Rep: Reputation: 1242Reputation: 1242Reputation: 1242Reputation: 1242Reputation: 1242Reputation: 1242Reputation: 1242Reputation: 1242Reputation: 1242
Just noticed this thread, and making a note to post later about my adventures getting this kernel working on a Lenovo P73 with D620 GPU and hybrid graphics management.

I'd posted a bit on the "Latest Kernel Release" thread but was wary of polluting it with marginally off-topic content. This thread seems like a better fit.
 
Old 11-09-2019, 04:40 PM   #30
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.2 Slackware 14.2, Slackware{32,64}-current
Posts: 914
Blog Entries: 9

Rep: Reputation: 393Reputation: 393Reputation: 393Reputation: 393
I'm definitely excited about 5.4 possibility as LTS, and landing in 15.0. If only I had a miniITX mobo for this ITX case so I can test (HINT! HINT!). It might be time to dual boot my main box by putting current on the spare NVME drive.

Although I agree with enorbet as I too have run Nvidia GPU for a long time (TNT2, GeforceDDR 256 upgrades from Paradise Bahamas S3 Trio64 and 3DFX Voodoo), I am still excited about the possibility to switch to AMD Navi GPU in my next build. Nvidia's support has been excellent (after all, I maintain the scripts on SBo). Without that, AMD would never be a contender. Still, my gaming addiction, desire to move to 4K, and Nvidia's price are in conflict. If AMD GPU works OOTB for my game titles on Slackware with no additional drivers...heck, I'll switch. AMD just has currently a better bang for my limited buck.
 
2 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Kernel 4.19.0 breaks system boot - looking for kernel-huge-smp-4.14.78_smp-i686-1.txz rwyarbrough Slackware 6 10-25-2018 12:44 AM
xf86-video-intel-2.99.914-x86_64-1.txz breaks GL grissiom Slackware 2 07-29-2014 11:55 PM
Slackware -current 32 bit holds pan-0.134-x86_64-1.txz package gianco Slackware 4 02-25-2011 01:41 PM
Uneeded "/usr/lib64//firefox-3.6.10" directory in mozilla-firefox-4.0b6-x86_64-1.txz michelino Slackware 0 09-21-2010 06:20 AM
libstdc++.so.5 is missing from gcc-4.3.3_multilib-x86_64-4alien.txz samac Slackware 5 08-31-2009 07:57 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:56 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration