[sarge] kernel source 2.6.14

2005-12-12 Thread fredantispam
Hi all,

Where can I get kernel source for 2.6.14 release ?

I tried to compile from kernel.org, but it fails (I have no err msg at the
hand),
and it seems, to me, that there is only kernel source 2.6.8 for amd64/EM64T.

I apt-get update for unstable  testing, but no result.

What's wrong ?

Any idea ? Url ?

Thanks in advance.

PS : kernel source 2.6.14 compiles fine for i386, so I think this is peculiar
to amd64/EM64T arch, and maybe kernel source 2.6.14 needs some patch...
PS2 : kernel source 2.6.8 compiles fine too.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread Gilles

 
 Where can I get kernel source for 2.6.14 release ?


Cf. below.
 
 I tried to compile from kernel.org, but it fails (I have no err msg at the
 hand),

$ uname -a
Linux dusk 2.6.14-vs2.1.0-rc5+g3 #1 SMP Sat Nov 5 18:01:33 CET 2005 x86_64 
GNU/Linux
   ^^
   from kernel.org

 and it seems, to me, that there is only kernel source 2.6.8 for amd64/EM64T.


$ apt-cache search ^linux-source
linux-source-2.6.12 - Linux kernel source for version 2.6.12 with Debian patches
linux-source-2.6.14 - Linux kernel source for version 2.6.14 with Debian patches


(Name change: kernel-source - linux-source)


Best,
Gilles


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread fred
Ok, I don't know where, but I made a mistake.

Now, kernel 2.6.14 compiles fine.
Good.

But... now I have a problem with nvidia module (1.0.7174) :-(
After a modprobe nvidia, kernel complains :
  Unknown symbol register_ioctl32_conversion
  Unknown symbol unregister_ioctl32_conversion

What's wrong ?

Thanks in advance.

-- 
Fred.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread Gilles

 
 But... now I have a problem with nvidia module (1.0.7174) :-(
 After a modprobe nvidia, kernel complains :
   Unknown symbol register_ioctl32_conversion
   Unknown symbol unregister_ioctl32_conversion
 
 What's wrong ?

It doesn't work ;-/

You have to use at least 1.0.7676.


Gilles


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread fred
Gilles a écrit :

 You have to use at least 1.0.7676.

Thanks, Gilles.
I have the last 1.0.8174, not in deb but in pkg from nvidia website.

Anybody have tested SLI with this release ?

-- 
Fred.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread Lennart Sorensen
On Mon, Dec 12, 2005 at 09:06:42PM +0100, fred wrote:
  You have to use at least 1.0.7676.

Actually the 7174-4 package does compile with 2.6.14, at least on i386
(I have a TNT2 and need the 71xx version).

 Thanks, Gilles.
 I have the last 1.0.8174, not in deb but in pkg from nvidia website.

Installing using nvidia's package is highly discouraged due to the mess
it makes and that future upgrades from debian are perfectly entitled to
overwrite its files since they are in the wrong place.

 Anybody have tested SLI with this release ?

I wish.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread fred
Lennart Sorensen a écrit :
 On Mon, Dec 12, 2005 at 09:06:42PM +0100, fred wrote:
 
You have to use at least 1.0.7676.
 
 
 Actually the 7174-4 package does compile with 2.6.14, at least on i386
 (I have a TNT2 and need the 71xx version).
 
 
Thanks, Gilles.
I have the last 1.0.8174, not in deb but in pkg from nvidia website.
 
 
 Installing using nvidia's package is highly discouraged due to the mess
 it makes and that future upgrades from debian are perfectly entitled to
 overwrite its files since they are in the wrong place.
Hmmm, there is no 1.0.7676 for amd64, even in unstable :-(
 
Anybody have tested SLI with this release ?
 
 
 I wish.
Me too. Before buy my second 6800GT :-)

-- 
Fred.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread Lennart Sorensen
On Mon, Dec 12, 2005 at 10:07:15PM +0100, fred wrote:
 Hmmm, there is no 1.0.7676 for amd64, even in unstable :-(

Building from the source deb is not hard though and works fine.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread fred
Nelson Menezes a écrit :
 On 12/12/05, fred [EMAIL PROTECTED] wrote:
 
Lennart Sorensen a écrit :
Hmmm, there is no 1.0.7676 for amd64, even in unstable :-(
 
 
 deb  http://people.debian.org/~rdonald/nvidia/   unstable/amd64/
 deb  http://people.debian.org/~rdonald/nvidia/   unstable/all/
Ok, thanks.
 
Anybody have tested SLI with this release ?


I wish.

Me too. Before buy my second 6800GT :-)
 
 
 Maybe I should start a new thread for this, but is anyone else
 having stability issues with nVidia drivers? My X session occasionally
 restarts itself when running a GL screensaver.
 
 Also, I can consistently make X restart if I have a GL screensaver
 being displayed in the little preview window in xscreensaver and I use
 the mouse wheel to scroll up/down the screensaver list.
I have no problem (but I don't use GL screensaver : I use DPMS :-)
Though, X for x86 seems to be more stable than amd64.

-- 
Fred.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: [sarge] kernel source 2.6.14

2005-12-12 Thread fred
Lennart Sorensen a écrit :

 Building from the source deb is not hard though and works fine.
Sure ;-)

-- 
Fred.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]