LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-09-2014, 06:00 PM   #31
WhiteWolf1776
Member
 
Registered: Oct 2010
Location: Bowling Green, KY
Distribution: Slackware
Posts: 288

Rep: Reputation: 95

I can also verify building nvidia driver with bumblebee support no longer works for the -current kernel.
 
Old 05-09-2014, 06:33 PM   #32
W4LK
LQ Newbie
 
Registered: Mar 2004
Location: South Carolina, USA
Distribution: Slackware Current
Posts: 14

Rep: Reputation: 1
willsr, Your comment about the 304.121 driver working for you is true for me, also. None of the newer versions worked for me. 304.121 has me back up and running. Thanks
 
Old 05-09-2014, 06:49 PM   #33
metaschima
Senior Member
 
Registered: Dec 2013
Distribution: Slackware
Posts: 1,982

Rep: Reputation: 492Reputation: 492Reputation: 492Reputation: 492Reputation: 492
Quote:
Originally Posted by turtleli View Post
The debug options also causes the broadcom-sta wl driver to fail as well (See this thread).
That's true, after researching it a bit more, many proprietary drivers are affected.
 
Old 05-09-2014, 06:51 PM   #34
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
OK, then...

I refined my kernel build, based on generic smp config of current 3.14.3, and looks like the minimal intervention path, if we do not want to disable entirely the kernel debug (and to stay entirely away of Linus debug jokes with the closed source developers), is to disable the following options:

CONFIG_DEBUG_WW_MUTEX_SLOWPATH
CONFIG_DEBUG_LOCK_ALLOC


The offending option is colored in red, but it is automatically selected also by the other option.
 
Old 05-09-2014, 06:53 PM   #35
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,828

Rep: Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463Reputation: 4463
Just FTR I have a custom built 3.12.0 RT Low-Latency kernel with

Code:
CONFIG_DEBUG_KERNEL=y
and have nVidia 331.67 installed from Runlevel 3 and working with zero problems. It is doubtful that this one line is the problem.

However
Code:
CONFIG_DEBUG_LOCK_ALLOC is not set

Last edited by enorbet; 05-09-2014 at 06:55 PM. Reason: follow up
 
Old 05-09-2014, 06:56 PM   #36
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Quote:
Originally Posted by enorbet View Post
Just FTR I have a custom built 3.12.0 RT Low-Latency kernel with

Code:
CONFIG_DEBUG_KERNEL=y
and have nVidia 331.67 installed from Runlevel 3 and working with zero problems. It is doubtful that this one line is the problem.
Sure! But, you have CONFIG_DEBUG_LOCK_ALLOC enabled, also?

----

Edit: Also, follow up... Sorry, enorbet!

Last edited by Darth Vader; 05-09-2014 at 06:58 PM.
 
Old 05-09-2014, 07:36 PM   #37
turtleli
Member
 
Registered: Aug 2012
Location: UK
Posts: 206

Rep: Reputation: Disabled
CONFIG_DEBUG_MUTEXES, CONFIG_DEBUG_SPINLOCK and CONFIG_LOCKDEP (not sure this can be manually selected) may also be the culprits, since they are selected by CONFIG_DEBUG_LOCK_ALLOC.

I didn't really test the options very thoroughly, I just suspected the problem was in the lock debugging options for the broadcom-sta driver and after reproducing the fault I decided that I didn't want to spend extra time on it.

EDIT: Okay, after scanning the source I think it's CONFIG_DEBUG_LOCK_ALLOC for the NVIDIA driver and CONFIG_LOCKDEP for the broadcom-sta driver that causes problems. For the nitty gritty details, CONFIG_DEBUG_LOCK_ALLOC changes mutex_lock calls to mutex_lock_nested, and CONFIG_LOCKDEP changes a no-op to lockdep_init_map. mutex_lock_nested and lockdep_init_map can only be used by GPL-compliant modules, whereas mutex_lock can be used by any external module. Other functions may also be affected in similar ways.

Last edited by turtleli; 05-09-2014 at 08:05 PM.
 
2 members found this post helpful.
Old 05-10-2014, 07:24 AM   #38
rg3
Member
 
Registered: Jul 2007
Distribution: Fedora
Posts: 527

Rep: Reputation: Disabled
I'm just dropping by to say I'm also affected by this problem. I couldn't build the NVIDIA driver after upgrading the kernel in my slackware64-current system today. Unfortunately, I don't have time at this moment to check a custom build with debugging disabled, but thanks to everyone who's investing time and helping here. I went the quick and dirty (and probably illegal?) route of running the installer with the -x option to extract the archive, changed the MODULE_LICENSE lines to GPL and ran the installer by hand.
 
Old 05-10-2014, 08:46 AM   #39
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247Reputation: 1247
Another quick and dirty workaround, on NVIDIA Linux drivers vs. the Slackware kernel 3.14.3.

This time, it's about one unexpected and full GPL driver...

If you have a NVIDIA chipset motherboard and, while using kernel 3.14.3, your hibernation kicked the bucket, you have to disable the serial port on motherboard, or to rebuild the kernel... without serial port support.

Yep, I talk about that little remnant from 90', and almost unchanged from this era, used to connect serial modems or other lovely things like debugging an another computer...

Now, the full native & GPL NVIDIA serial driver do not accept to be disabled, so your hibernation will go south.


BTW, talking about hibernation, if still, the hibernation (on disk) work, I believe that do the things now, maybe making a 32678 bits RSA checksum for every byte of memory, because now spend few minutes to go to sleep. Tested on NVIDIA and AMD chipsets. Both with 8G RAM and quad-cores...

Last edited by Darth Vader; 05-10-2014 at 08:53 AM.
 
Old 05-10-2014, 09:45 AM   #40
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,236

Rep: Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443
Quote:
Originally Posted by willysr View Post
lucky me then
304.121 works OK with Linux Kernel 3.14.3
I was surprised to see that the 304.xxx driver had been "tweaked" as recently as two months ago, resulting in the 304.121 version, so I tried it and and it did build and worked... to a point.
However, now WINE refuses to work. Interestingly, wine-pipelight works, but regular WINE does not. Re-installing WINE doesn't fix the problem.

At this point I'm going back to the previous kernel and will wait until the Gurus work out a solution.

Last edited by cwizardone; 05-10-2014 at 11:29 AM.
 
Old 05-10-2014, 10:12 AM   #41
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,846

Rep: Reputation: 456Reputation: 456Reputation: 456Reputation: 456Reputation: 456
304.121 works for me as well. I don't do wine, but wine-pipelight is fine. I'm golden for now. Then again, I have an older card - Geforce 9 series.
 
Old 05-10-2014, 11:41 AM   #42
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,236

Rep: Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443
Well, I'm back to the 3.10.30 kernel and the NVIDIA 325.15 driver.

Both the 331.49 and 331.67 drivers worked, without a problem, prior to trying the 3.14.3 kernel, but now, after reverting to the 3.10.30 kernel, neither driver will install without issuing errors during the installation of the 32-bit compatible drivers. The error, repeated 4 or 5 times, was,

Quote:
Unable to determine the architecture of the file '/usr/lib64/libEGL.la,' which has an architecture-specific conflict.
So I worked my way back to the 325.15 driver which installed without error and WINE is now working as it should.

One interesting side note, I thought. After installing the 3.14.3 kernel it was necessary, of course, to re-install VirtualBox. However, after reverting to the 3.10.30 kernel it was not necessary to re-install VirtualBox and it is running just fine. Odd, I thought.
 
Old 05-10-2014, 11:58 AM   #43
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675

Rep: Reputation: Disabled
Methinks 304.121 is kind of long-life support version. 337.19 builds fine with 3.14.
 
Old 05-10-2014, 12:05 PM   #44
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,236

Rep: Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443Reputation: 7443
I've tried the 337.19 driver, which NVIDIA has labeled as, "BETA," and it didn't build with the 3.14.3 kernel.

Last edited by cwizardone; 05-10-2014 at 12:07 PM.
 
Old 05-10-2014, 12:33 PM   #45
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~amd64
Posts: 7,675

Rep: Reputation: Disabled
Works here ...
Code:
$ modinfo nvidia
filename:       /lib/modules/3.14.3-gentoo/video/nvidia.ko
alias:          char-major-195-*
version:        337.19
supported:      external
license:        NVIDIA
alias:          pci:v000010DEd00000E00sv*sd*bc04sc80i00*
alias:          pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00*
alias:          pci:v000010DEd*sv*sd*bc03sc02i00*
alias:          pci:v000010DEd*sv*sd*bc03sc00i00*
depends:        
vermagic:       3.14.3-gentoo SMP mod_unload 
parm:           NVreg_Mobile:int
parm:           NVreg_ResmanDebugLevel:int
parm:           NVreg_RmLogonRC:int
parm:           NVreg_ModifyDeviceFiles:int
parm:           NVreg_DeviceFileUID:int
parm:           NVreg_DeviceFileGID:int
parm:           NVreg_DeviceFileMode:int
parm:           NVreg_RemapLimit:int
parm:           NVreg_UpdateMemoryTypes:int
parm:           NVreg_InitializeSystemMemoryAllocations:int
parm:           NVreg_RMEdgeIntrCheck:int
parm:           NVreg_UsePageAttributeTable:int
parm:           NVreg_MapRegistersEarly:int
parm:           NVreg_RegisterForACPIEvents:int
parm:           NVreg_CheckPCIConfigSpace:int
parm:           NVreg_EnablePCIeGen3:int
parm:           NVreg_EnableMSI:int
parm:           NVreg_MemoryPoolSize:int
parm:           NVreg_RegistryDwords:charp
parm:           NVreg_RmMsg:charp
parm:           NVreg_AssignGpus:charp
 
  


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
NVIDIA kernel module version is different from NVIDIA driver lalik Linux - Newbie 2 09-16-2010 03:32 PM
Nvidia Driver will not install for Dual Screen LCD - Driver is mde for Xen Kernel isinkaye Linux - Software 1 02-20-2010 04:31 AM
Kernel 2.6.8 Nvidia Driver Thoron Debian 1 05-05-2005 10:05 PM
Nvidia driver and Kernel 2.6.3 jriis Debian 6 04-15-2004 03:00 AM
kernel 2.6.3--bk8 and NVIDIA-Linux-x86-1.0-5336 video driver from Nvidia zdenkod Linux - Hardware 2 03-09-2004 05:38 AM

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

All times are GMT -5. The time now is 06:02 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
Open Source Consulting | Domain Registration