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, 07:30 PM   #31
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
Create this symlink to build the virtualbox kernel module for 2.6.33 since the 2.6.33 kernel no longer has autoconf.h
Very nice! Thanks a bunch!
 
Old 03-02-2010, 07:43 PM   #32
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
No problem. If it works don't forget the thumbs up If it doesn't it's the middle finger
 
Old 03-02-2010, 07:49 PM   #33
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
No problem. If it works don't forget the thumbs up If it doesn't it's the middle finger
Already gave you the thumbs up...no middle fingers though.
 
Old 03-02-2010, 07:51 PM   #34
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
LOL, must've been someone else
 
Old 03-02-2010, 07:51 PM   #35
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 229Reputation: 229Reputation: 229
If you are having issues building "out of tree" kernel stuff you might try the following steps.

Make a symlink /usr/src/linux => /path/to/your/kernel_source
Backup your .config file (or use /boot/config if you use the stock kernel)

Code:
cd /usr/src/linux
make mrproper
cp /your/.config_backup .config
make oldconfig
make prepare
make scripts
That generally solves a lot of issues.
 
Old 03-02-2010, 09:08 PM   #36
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

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

samac
I also got the same error when I applied the nvidia patch.
 
Old 03-02-2010, 09:10 PM   #37
smoooth103
Member
 
Registered: Aug 2009
Location: NC, USA
Distribution: Slackware (64 bit)
Posts: 242

Rep: Reputation: 62
Quote:
Originally Posted by AlleyTrotter View Post
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
This did not work for me. I got the same two errors described below:

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

smoooth
 
Old 03-02-2010, 09:18 PM   #38
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,164

Original Poster
Rep: Reputation: 165Reputation: 165
Quote:
Originally Posted by smoooth103 View Post
This did not work for me. I got the same two errors described below:

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

smoooth
Have you made the changes to the .config file and rebuilt the kernel? Once I did that, I did not have to use the patch. What I did have to do though was to blacklist the nouveau driver from loading.
 
Old 03-02-2010, 09:28 PM   #39
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 stormtracknole View Post
Have you made the changes to the .config file and rebuilt the kernel? Once I did that, I did not have to use the patch. What I did have to do though was to blacklist the nouveau driver from loading.
Was this the case before or after you made the aoutconf.h -> version.h symlink? I'm wondering because I was looking at the patch and it has several instances regarding autoconf.h.
 
Old 03-02-2010, 10:09 PM   #40
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
Was this the case before or after you made the aoutconf.h -> version.h symlink? I'm wondering because I was looking at the patch and it has several instances regarding autoconf.h.
Well, in my case, I ran both patches but did not have success with either one. I did not try to manually do a symlink though, but if the patch was already doing that, then it didn't work.
 
Old 03-02-2010, 11:10 PM   #41
ginkgo
LQ Newbie
 
Registered: Sep 2009
Posts: 18

Rep: Reputation: 1
Pat. should consider this problem. As a normal desktop user I hate to recompile the kernel.

when I want to use the nouveau driver, also mention me the modules format error. [ can not run the "modprobe nouveau" command ]

Please consider for the new linux user.
 
Old 03-02-2010, 11:19 PM   #42
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,367

Rep: Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841Reputation: 841
And this is why this is in -current and not stable. I'm sure the problem will be rectified but I don't understand why you are complaining about the 'new linux user' when -current is supposed to be for the advanced Linux user for testing.
 
Old 03-02-2010, 11:34 PM   #43
mRgOBLIN
Slackware Contributor
 
Registered: Jun 2002
Location: New Zealand
Distribution: Slackware
Posts: 999

Rep: Reputation: 229Reputation: 229Reputation: 229
Yes welcome to current =)
 
Old 03-03-2010, 12:12 AM   #44
GrapefruiTgirl
LQ Guru
 
Registered: Dec 2006
Location: underground
Distribution: Slackware64
Posts: 7,594

Rep: Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553Reputation: 553
Quote:
Originally Posted by bathory View Post
Yup, with CONFIG_PREEMPT set, you'll get the invalid module format.

Cheers
OK, Finally, after some unplanned frigging around, I am running 2.6.33 and the patched 190.53 nvidia driver (not the BETA) and I still have my PREEMPT setting in my kernel; so, I can attest that it appears PREEMPT is not causing the "invalid module format" messages that some of you are having.

Code:
sasha@reactor: uname -a
Linux reactor 2.6.33-01 #1 SMP PREEMPT \
Wed Mar 3 01:56:22 AST 2010 x86_64 \
Genuine Intel(R) CPU

# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
CONFIG_PREEMPT=y

sasha@reactor: glxinfo
GL_VERSION: 2.1.2 NVIDIA 190.53
Some of the 'frigging around' I refer to, was because I discovered the 'nouveau' driver in the staging area and thought (yeah I know: don't think!) I'd compile it as a module to play with and compare to the nvidia binary. Well, it took over the framebuffer early in boot (and spewed a couple pages worth of FIFO errors too) and ultimately not only did my console font look like they had gone under a steamroller (all smudged/mushed and unreadable) but then the nvidia driver wouldn't modprobe (of course) so I rebuilt again (silly me, should have downloaded the nvidia patch BEFORE I rebuilt my kernel, to save myself the trouble of having to locate/download it using Links in the VT :/ ) and here I am now.

FWIW 2.6.33 seems to work A-OK so far. Nothing to report about it specifically at this time.

And now.... To look for an updated -current mirror!!

Sasha

Last edited by GrapefruiTgirl; 03-03-2010 at 12:14 AM. Reason: include nvidia version info
 
Old 03-03-2010, 12:37 AM   #45
ponce
LQ Guru
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 5,604

Rep: Reputation: Disabled
I am only (wild) guessing but I think maybe kernel-huge-2.6.33-x86_64-1 has been built with gcc-4.4.3-x86_64-1 (instead of -2).
(please don't beat me, I wear glasses)

Last edited by ponce; 03-03-2010 at 01:05 AM.
 
  


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:05 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