LinuxQuestions.org
Review your favorite Linux distribution.
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 03-02-2010, 03:05 PM   #16
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553

Well, I am not amused about that -- I am as we speak, running through xconfig prior to building 2.6.33, and I am leaving my preempt the way it is (CONFIG_PREEMPT) until I see it fail because I want to experience this firsthand.

FWIW, a couple years ago, when I came up with a few workarounds for the Intel 536EP modem driver on various kernel versions, that driver at some stage in its life, and with certain new kernel release, also would not work with the PREEMPT kernel options set to "low latency" and it gave "invalid module format" too; but it DID work with the other available preempt option(s). A few kernel versions later, that problem was rectified.

I am currently (have been for a long time) using the "low-latency" model, so we'll see.. Maybe I'm a sucker for punishment. Must try for myself though.

Off Topic slightly -- I see that the "Anticipatory" I/O scheduler has 'disappeared' from the new kernel; only Deadline and CFQ remain. Hmmm..
 
Old 03-02-2010, 03:09 PM   #17
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,164

Original Poster
Rep: Reputation: 165Reputation: 165
Quote:
Originally Posted by GrapefruiTgirl View Post
Well, I am not amused about that -- I am as we speak, running through xconfig prior to building 2.6.33, and I am leaving my preempt the way it is (CONFIG_PREEMPT) until I see it fail because I want to experience this firsthand.

FWIW, a couple years ago, when I came up with a few workarounds for the Intel 536EP modem driver on various kernel versions, that driver at some stage in its life, and with certain new kernel release, also would not work with the PREEMPT kernel options set to "low latency" and it gave "invalid module format" too; but it DID work with the other available preempt option(s). A few kernel versions later, that problem was rectified.

I am currently (have been for a long time) using the "low-latency" model, so we'll see.. Maybe I'm a sucker for punishment. Must try for myself though.

Off Topic slightly -- I see that the "Anticipatory" I/O scheduler has 'disappeared' from the new kernel; only Deadline and CFQ remain. Hmmm..
I worked on this late last night, so I might have not been thinking straight when I first posted my problem. lol Anyway, it appears that my problem was solved by making that change. I am interested though in what kind of results you get.
 
Old 03-02-2010, 03:16 PM   #18
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,593

Rep: Reputation: Disabled
I think problems can arise *maybe* if nvidia modules are built with multilib gcc when the kernel has been built probably with the stock gcc from current: that could be the reason of the "invalid module format" message.

I rebuild usually my custom kernel with zen patches and I have done the same this time (with a "make oldconfig" based on slackware stock /proc/config.gz) and the nvidia module inserted fine in the kernel.
maybe also rebuilding the stock kernel with the same config but with alien's gcc can solve, have to try.

on huge 2.6.33 shipped with slackware I had that message too at first after upgrading everything on my multilib install.

btw, I have CONFIG_PREEMPT=y (and CONFIG_HZ_2000=y )

Last edited by ponce; 03-02-2010 at 03:20 PM.
 
Old 03-02-2010, 03:17 PM   #19
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,164

Original Poster
Rep: Reputation: 165Reputation: 165
Quote:
Originally Posted by ponce View Post
I think problems can arise *maybe* if nvidia modules are built with multilib gcc when the kernel has been built probably with the stock gcc from current: that could be the reason of the "invalid module format" message.

I rebuild usually my custom kernel with zen patches and I have done the same this time (with a "make oldconfig" based on slackware stock /proc/config.gz) and the nvidia module inserted fine in the kernel.

on huge 2.6.33 shipped with slackware I had that message too at first after upgrading everything on my multilib install.

btw, I have CONFIG_PREEMPT=y (and CONFIG_HZ_2000=y )
I'm not using a multilib enviroment though.
 
Old 03-02-2010, 03:34 PM   #20
disturbed1
Senior Member
 
Registered: Mar 2005
Location: USA
Distribution: Slackware
Posts: 1,133
Blog Entries: 6

Rep: Reputation: 223Reputation: 223Reputation: 223
Quote:
Originally Posted by GrapefruiTgirl View Post
Well, I am not amused about that -- I am as we speak, running through xconfig prior to building 2.6.33, and I am leaving my preempt the way it is (CONFIG_PREEMPT) until I see it fail because I want to experience this firsthand.
It works fine with Preemptive enabled. The huge kernel had to be rebuilt to work. Made no changes, just copied the config over, rebuilt, installed, edit lilo, reboot. Should be using the generic kernel, or building your own anyways
Attached Thumbnails
Click image for larger version

Name:	snapshot1.png
Views:	38
Size:	97.3 KB
ID:	2880  
 
Old 03-02-2010, 03:42 PM   #21
AlleyTrotter
Member
 
Registered: Jun 2002
Location: Coal Township PA
Distribution: Slackware64-14.2 (5.8.9) UEFI enabled
Posts: 568

Rep: Reputation: 245Reputation: 245Reputation: 245
works here

Not sure about everything in this thread but this worked for me

NVIDIA-Linux-x86_64-190.53-pkg2.run --apply-patch nvidia-190.53-2.6.33.patch.txt

This produces NVIDIA-Linux-x86_64-190.53-pkg2-custom.run

which installs and works fine for me
the patch is attached I think

john

Last edited by AlleyTrotter; 07-23-2013 at 01:23 PM.
 
2 members found this post helpful.
Old 03-02-2010, 05:54 PM   #22
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,477

Rep: Reputation: Disabled
If you do not need 3D acceleration, better use the "nouveau" driver, it works very well. You'll find it under "staging drivers" in the kernel tree.
 
Old 03-02-2010, 06:02 PM   #23
samac
Senior Member
 
Registered: Mar 2004
Location: Westray, Orkney
Distribution: Linux Mint 17.1
Posts: 1,424

Rep: Reputation: 138Reputation: 138
Quote:
Not sure about everything in this thread but this worked for me

NVIDIA-Linux-x86_64-190.53-pkg2.run --apply-patch nvidia-190.53-2.6.33.patch.txt

This produces NVIDIA-Linux-x86_64-190.53-pkg2-custom.run

which installs and works fine for me
the patch is attached I think
Didn't work for me. I am getting an Invalid module format message
Quote:
root@quad:/home/samac# modprobe nvidia
WARNING: Error inserting agpgart (/lib/modules/2.6.33/kernel/drivers/char/agp/agpgart.ko): Invalid module format
FATAL: Error inserting nvidia (/lib/modules/2.6.33/kernel/drivers/video/nvidia.ko): Invalid module format
samac
 
Old 03-02-2010, 06:05 PM   #24
botnet
Member
 
Registered: May 2009
Posts: 158

Rep: Reputation: 40
i can confirm, cp /boot/config-huge-2.6.33 /usr/src/linux-2.6.33/.config && cd /usr/src/linux-2.6.33 && make && make modules_install && cp arch/x86_64/boot/bzImage /boot/vmlinuz && lilo && echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf && telinit 6 will allow the patched 190.53 nvidia drivers to work

patched as per AlleyTrotters post above.

this is with multilib enabled on slackware64-current
 
1 members found this post helpful.
Old 03-02-2010, 06:08 PM   #25
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

Rep: Reputation: 62
I upgraded to -current last night also and I am unable to build my nvidia driver with ./NVIDIA**.sh.

I am on 32bit current with no multilib.

The error I get is that the kernel source version is not properly identified/configured or something to that effect.

I haven't tried any of the suggestions mentioned above yet -- but typically there are no issues compiling my NVIDIA driver after a -current update.
 
Old 03-02-2010, 06:09 PM   #26
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
I've been running 2.6.33-rc5 for a month now and both 190.53 and the beta drivers will build with the patch. There is also a workaround (nothing more than creating a symlink) needed for the Vbox kernel module on the 2.6.33 kernel unless that has been recently addressed on the Vbox side.
 
Old 03-02-2010, 06:10 PM   #27
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,164

Original Poster
Rep: Reputation: 165Reputation: 165
Quote:
Originally Posted by samac View Post
Didn't work for me. I am getting an Invalid module format message

samac
Try adding blacklist nouveau to /etc/modprobe.d/blacklist.conf. Reboot and try it again.
 
Old 03-02-2010, 06:44 PM   #28
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Quote:
Originally Posted by GrapefruiTgirl View Post
Well, I am not amused about that -- I am as we speak, running through xconfig prior to building 2.6.33, and I am leaving my preempt the way it is (CONFIG_PREEMPT) until I see it fail because I want to experience this firsthand.
Code:
Linux i7 2.6.33-rc5 #1 SMP PREEMPT Wed Jan 27 22:47:34 CST 2010 x86_64 Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz GenuineIntel GNU/Linux
It's been running with 190.53 as well as the 195.30 beta drivers for a month. It may be different in the final release, but I doubt it. The .config started as a slack generic 2.6.32.x and then had a lot of stuff removed and filesystem support added, plus customization for processor.

Quote:
I haven't tried any of the suggestions mentioned above yet -- but typically there are no issues compiling my NVIDIA driver after a -current update.
I read somewhere that the NVIDIA unix/linux driver team were having some issues getting the betas stablilized, which was preventing the betas from getting released in a timely fashion. This might be the reason that 2.6.33 support wasn't immediately available in the stable driver since it may have been intended to be replaced prior to the 2.6.33 release.

Last edited by damgar; 03-02-2010 at 06:49 PM.
 
Old 03-02-2010, 07:18 PM   #29
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,164

Original Poster
Rep: Reputation: 165Reputation: 165
Quote:
Originally Posted by damgar View Post
I've been running 2.6.33-rc5 for a month now and both 190.53 and the beta drivers will build with the patch. There is also a workaround (nothing more than creating a symlink) needed for the Vbox kernel module on the 2.6.33 kernel unless that has been recently addressed on the Vbox side.
Oh, do share on that one. I'm having that issue now with vbox.
 
Old 03-02-2010, 07:26 PM   #30
damgar
Senior Member
 
Registered: Sep 2009
Location: dallas, tx
Distribution: Slackware - current multilib/gsb Arch
Posts: 1,949
Blog Entries: 8

Rep: Reputation: 201Reputation: 201Reputation: 201
Create this symlink to build the virtualbox kernel module for 2.6.33 since the 2.6.33 kernel no longer has autoconf.h
Quote:
/usr/src/linux-2.6.33/include/linux/autoconf.h -> version.h

Last edited by damgar; 03-02-2010 at 07:29 PM.
 
1 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
(EE) NVIDIA(0): Failed to initialize the NVIDIA Kernel module latino Linux - Hardware 5 06-03-2008 03:55 AM
(EE) NVIDIA(0): Failed to initialize the nvidia kernel module necbrownie Slackware 18 06-16-2006 02:20 AM
nvidia 6106, kernel 2.6.7, slackware 10, failure to load nvidia.ko Tarball_Phreak Linux - Hardware 3 08-04-2004 03:16 PM
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
(EE) NVIDIA (0) Failed to initialize the NVIDIA kernel module Isjhe Mandriva 14 09-25-2003 09:29 PM

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

All times are GMT -5. The time now is 03:14 AM.

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