I'd like to try to compile my own kernel, using the realtime patch set. At
kernel.org, I see that the 6.6 kernel source is 6.6, but the 6.6 realtime
patch set is 6.6-rt12. Does that matter, or is it enough that both are
given as 6.6? Similarly, if I see that the 6.5 series is at 6.5.10
My thanks to the developing classes of Debian who as together or as one (it only
takes one) fixed this package that fixed the module that fixed the nvidia
driver.
Good show.
--
CK
where should my humble contribution be directed?
signature.asc
Description: PGP signature
the patches I run
- fakeroot debian/rules source
Now I can see that the patches are applied. According to
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html the
patched kernel source is now at debian/build/source. So all I must do
is to create a tarball of that subdirectory. Am I correct so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 20 September 2010, Arthur Machlas was heard to say:
My guess is you need to build the header at least, and perhaps the
source. It depends on how you're building the modules I suppose. In
any case, you'll have to run either
fakeroot
On 9/21/2010 7:27 AM, Curt Howland wrote:
On Monday 20 September 2010, Arthur Machlas was heard to say:
My guess is you need to build the header at least, and perhaps the
source. It depends on how you're building the modules I suppose. In
any case, you'll have to run either
fakeroot make-kpkg
.
nvidia.ko failed to build!
make[1]: *** [module] Error 1
make: *** [module] Error 2
- Error.
ERROR: Unable to build the NVIDIA kernel module.
==
Which I guess means I have to wait for Nvidia to fix a signed vs
unsigned change in the kernel source.
Can folks suggest if it would be worth
On Mon, Sep 20, 2010 at 12:25 PM, Curt Howland howl...@priss.com wrote:
Hi. Up to date Squeeze, compiling the latest 2.6.36-rc4 kernel.
Last time the problem was compiling the kernel at all, which is
working just fine now thank you Debian-User.
fakeroot make-kpkg --append-to-version -curt1.0
On Mon, Sep 20, 2010 at 01:25:45PM -0400, Curt Howland wrote:
Last time the problem was compiling the kernel at all, which is
working just fine now thank you Debian-User.
fakeroot make-kpkg --append-to-version -curt1.0 --initrd kernel_image
creates the .deb file just fine, it installs
On Mon, 20 Sep 2010 13:25:45 -0400 (EDT), Curt Howland wrote:
Hi. Up to date Squeeze, compiling the latest 2.6.36-rc4 kernel.
Last time the problem was compiling the kernel at all, which is
working just fine now thank you Debian-User.
fakeroot make-kpkg --append-to-version -curt1.0
that you specify
--append-to-version and --revision on *every* invocation of make-kpkg. How
are you creating the virtualbox and nvidia packages? Are you using
module-assistant? Or are you compiling a kernel source module package
using the modules_image target of make-kpkg? If you are using
module
means I have to wait for Nvidia to fix a signed vs
unsigned change in the kernel source.
Can folks suggest if it would be worth while reporting this to Nvidia?
Curt-
Hi, I build my kernels with kernel-package, currently a
2.6.35.4-vanilla64 and have no problem. I build the headers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Monday 20 September 2010, Arthur Machlas was heard to say:
And install the debs. Alternatively, build both just to be safe
fakeroot make-kpkg --append-to-version -curt1.0 kernel_headers
kernel_image
Very interesting. Any idea why building the
Hey,
I am just wondering if the problem is me or the package.
Kernel Package:
Package: linux-image-2.6.30-2-amd64
State: installed
Automatically installed: no
Version: 2.6.30-8
[...]
nvidia-kernel-source:
[...]
Version: 180.44-2
[...]
Okay, here my steps:
Installing the kernel+headers
On Sat, Oct 17, 2009 at 12:56 PM, Thomas Jackowski tho...@jackowski.de wrote:
Hey,
I am just wondering if the problem is me or the package.
Kernel Package:
Package: linux-image-2.6.30-2-amd64
State: installed
Automatically installed: no
Version: 2.6.30-8
[...]
nvidia-kernel-source
Automatically installed: no
Version: 2.6.30-8
[...]
nvidia-kernel-source:
[...]
Version: 180.44-2
[...]
Okay, here my steps:
Installing the kernel+headers and nvidia source.
# m-a build -k /usr/src/linux-headers-2.6.30-2-amd64/ nvidia-kernel-source
This error shows up:
[...]
/usr/src
also experimented with kernel-package (with similar results). For
the most common case of compiling an external module, I found that
the package linux-headers-2.6.26-2-arch, symlinked to /usr/src/linux
will do what I need.
I am still looking for a way to get the complete kernel source/.config
results). For
the most common case of compiling an external module, I found that
the package linux-headers-2.6.26-2-arch, symlinked to /usr/src/linux
will do what I need.
I am still looking for a way to get the complete kernel source/.config
that corresponds to the binary kernel packages, preferably
On Wed, Feb 25, 2009 at 12:51:19AM +, Tzafrir Cohen wrote:
On Tue, Feb 24, 2009 at 03:31:38PM -0800, Mike McClain wrote:
I've a mostly etch system and wanted to try the 2.6 kernel.
snip
2.4.27 and 2.6.8 are from Sarge. 2.2.25 is even older.
Thanks for the tip, I hadn't realized 'apt-get
: kernel-source /var/lib/dpkg/available
Package: kernel-source-2.4.27
Package: kernel-source-2.2.25
Package: kernel-source-2.6.8
root@/deb40a:~ apt-get install kernel-source-2.6.8
Reading Package Lists... Done
Building Dependency Tree... Done
Package kernel-source-2.6.8 is not available
contrib non-free
root@/deb40a:~ apt-get update
root@/deb40a:~ grep Package: kernel-source /var/lib/dpkg/available
Package: kernel-source-2.4.27
Package: kernel-source-2.2.25
Package: kernel-source-2.6.8
2.4.27 and 2.6.8 are from Sarge. 2.2.25 is even older.
--
Tzafrir Cohen | tzaf
On Tue, 24 Feb 2009 15:31:38 -0800
Mike McClain mike.j...@nethere.com wrote:
I've a mostly etch system and wanted to try the 2.6 kernel.
...
root@/deb40a:~ apt-get update
root@/deb40a:~ grep Package: kernel-source /var/lib/dpkg/available
Package: kernel-source-2.4.27
Package: kernel-source
i pasted the config file of 18th kernel to kernel source of 26 I ran make
oldconfig , eventhough it is querying for the new options present in that
source for that i didnt know what to do.. i simply gave enter to that
options.
Simply pressing enter will enable the options if not shall I
2008/11/27 boss ganesh [EMAIL PROTECTED]:
i pasted the config file of 18th kernel to kernel source of 26 I ran make
oldconfig , eventhough it is querying for the new options present in that
source for that i didnt know what to do.. i simply gave enter to that
options.
Simply pressing
2008/11/24 boss ganesh [EMAIL PROTECTED]:
I have pasted the config file of 2.6.18 (already compiled working kernel
config file) to kernel source of version 2.6.26 , after that also it is
asking queries without compiling it when i ran the command make ..
why is it happening like that?
Did
On 2008-11-24 09:13 +0100, Adrian Levi wrote:
2008/11/24 boss ganesh [EMAIL PROTECTED]:
I have pasted the config file of 2.6.18 (already compiled working kernel
config file) to kernel source of version 2.6.26 , after that also it is
asking queries without compiling it when i ran the command
On Mon, Nov 24, 2008 at 11:59:26AM +0530, boss ganesh wrote:
I have pasted the config file of 2.6.18 (already compiled working kernel
config file) to kernel source of version 2.6.26 , after that also it is
asking queries without compiling it when i ran the command make ..
why
boss ganesh wrote:
I have pasted the config file of 2.6.18 (already compiled working kernel
config file) to kernel source of version 2.6.26 , after that also it is
asking queries without compiling it when i ran the command make ..
why is it happening like that?
The command you want
I have pasted the config file of 2.6.18 (already compiled working kernel
config file) to kernel source of version 2.6.26 , after that also it is
asking queries without compiling it when i ran the command make ..
why is it happening like that?
--
bossganesh
BOSSTeam
CDAC
On Mon, 2008-10-06 at 22:06 +0900, J.H.Kim wrote:
Is the debian kernel source and the kernel source of same version in
kernel archive(www.kernel.org) same?
I believe there may be some patches involved.
If I want to get debian kernel source code, which source code cd-rom
is needed out
Hi, everyone
Is the debian kernel source and the kernel source of same version in kernel
archive(www.kernel.org) same?
If I want to get debian kernel source code, which source code cd-rom is
needed out of 21CDs?
Thanks in advance.
J.H.Kim wrote:
Hi, everyone
Is the debian kernel source and the kernel source of same version in kernel
archive(www.kernel.org) same?
No, Debian applies some set of patches.
If I want to get debian kernel source code, which source code cd-rom is
needed out of 21CDs?
You can obtain source
If you go over to http://www.debian.org/distrib/packages you should be able to
search for linux-source which will show you the current version of kernel
source available. I think this version will vary depending upon the release you
are searching under.
You might also want to look at the Wiki
Hi all,
I'm facing a problem to build a non-pae kernel from debian kernel
source.
Here's what i have done:
#apt-get source linux-2.6
#cd linux-2.6-2.6.18.dfsg.1
#./debian/rules debian/build debian/stamps
#make -f debian/rules.gen setup-i386-xen-686
#cd build/build-i386-xen-686
#make
bonsoir
jusqu'a présent j'utilisais virtualbox sans probleme
a present j'ai un message d'erreur selon lequel il ne trouve pas le
kernel-source
(aucun paquet ne correspond au kernel-source)
et donc pour virtualbox
vboxdrv setup echoue
mon noyau est 2.6.18.6.686
merci
--
Lisez la FAQ de la
deny a écrit :
bonsoir
jusqu'a présent j'utilisais virtualbox sans probleme
a present j'ai un message d'erreur selon lequel il ne trouve pas le
kernel-source
(aucun paquet ne correspond au kernel-source)
et donc pour virtualbox
vboxdrv setup echoue
mon noyau est 2.6.18.6.686
merci
j'ai
on the differences between the
various kernel source packages in the repository,
kernel-source-* are for sarge and below
linux-source-* are for etch and beyond
Then do
apt-cache show $PACKAGE
and read the Description:
(for example, difference between linux-source-2.6.18 and linux-tree-2.6.18
also sprach Digby Tarvin [EMAIL PROTECTED] [2008.04.14.0252 +0200]:
The example in my Martin Kraft book refers to:
apt-get install kernel-source-2.6.8
but I can't find a 'kernel-source-anything'..
Try linux-source-*. The kernel packaging has changed substantially
since my book
Can anyone shed any light on the differences between the
various kernel source packages in the repository, and which is
the best choice for just being able to reproduce the running kernel?
The example in my Martin Kraft book refers to:
apt-get install kernel-source-2.6.8
but I can't find
Can anyone shed any light on the differences between
the various kernel source packages in the
repository,
and which is the best choice for just being able to
reproduce the running kernel?
The example in my Martin Kraft book refers to:
apt-get install kernel-source-2.6.8
but I
On Mon, Apr 14, 2008 at 12:52:41AM +, Digby Tarvin wrote:
Can anyone shed any light on the differences between the
various kernel source packages in the repository,
kernel-source-* are for sarge and below
linux-source-* are for etch and beyond
Then do
apt-cache show $PACKAGE
and read
'make oldconfig' to use
this configuration then ran the kernel compile for a few minutes to make
the necessary files for the Nvidia driver builder, then run the Nvidia
driver
program with the --kernel-source-path=KERNEL-SOURCE-PATH command
line option so it finds the kernel source.
Pending
the nvidia-installer (sh NVIDIA-Linux-x86-169.09-pkg1.run)
It tries to find kernel source from ftp://download.nvidia.com; and
fails, then bombs out when it cannot find it installed locally...
To build a kernel, I need kernel-source and kernel-devel packages
installed; (something called linux
version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1)
gcc version:
gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)
When I run the nvidia-installer (sh NVIDIA-Linux-x86-169.09-pkg1.run)
It tries to find kernel source from ftp://download.nvidia.com; and
fails, then bombs out when
for a few minutes to make
the necessary files for the Nvidia driver builder, then run the Nvidia
driver
program with the --kernel-source-path=KERNEL-SOURCE-PATH command
line option so it finds the kernel source.
Pending any minor missing items that were show stoppers but easy to find
and install
On Mon, Dec 31, 2007 at 10:14:38PM +0100, Rodolfo Medina wrote:
In Sarge, in order to configure Debian for my modem, I started with:
# apt-get install kernel-source-2.4.27
. Now, in Etch, what should the package be in place of that? I couldn't
find it! I tried with ...2.6, ...2.6.18
Hi to all Debian users.
In Sarge, in order to configure Debian for my modem, I started with:
# apt-get install kernel-source-2.4.27
. Now, in Etch, what should the package be in place of that? I couldn't find
it! I tried with ...2.6, ...2.6.18,... but none was the right one.
Thanks for any
On 22:14 Mon 31 Dec , Rodolfo Medina wrote:
Hi to all Debian users.
In Sarge, in order to configure Debian for my modem, I started with:
# apt-get install kernel-source-2.4.27
. Now, in Etch, what should the package be in place of that? I couldn't find
it! I tried with ...2.6
On Mon, Dec 31, 2007 at 10:14:38PM +0100, Rodolfo Medina wrote:
Hi to all Debian users.
In Sarge, in order to configure Debian for my modem, I started with:
# apt-get install kernel-source-2.4.27
. Now, in Etch, what should the package be in place of that? I couldn't find
it! I
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
one need to patch it with all of the included debian patches when
building a custom kernel?
Everything should be made as simple as possible
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would one
need to patch it with all of the included debian patches when building a
custom kernel?
It's already
Quoting Mumia W.. [EMAIL PROTECTED]:
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
one need to patch it with all of the included debian patches when
On Tue, 28 Aug 2007 15:15:08 -0400
[EMAIL PROTECTED] wrote:
Quoting Mumia W.. [EMAIL PROTECTED]:
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
On 08/28/2007 02:15 PM, [EMAIL PROTECTED] wrote:
Quoting Mumia W.. [EMAIL PROTECTED]:
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote:
I notice there is a source package for the kernel and a package of
debian patches. Has the kernel source already been patched or would
one need to patch
I notice there is a source package for the kernel and a package of debian
patches. Has the kernel source already been patched or would one need to
patch it with all of the included debian patches when building a custom
kernel?
Everything should be made as simple as possible, but not simpler
On Fri, 17 Aug 2007 06:11:08 +0200
Marcus Blumhagen [EMAIL PROTECTED] wrote:
Hi,
First of all, please CC me when replying, since I am not subscribed to
this list.
[...]
And as I rarely decompress files, I have forgotten the command to
decompress tar/bz2 files .
[...]
I just
Hi,
First of all, please CC me when replying, since I am not subscribed to
this list.
[...]
And as I rarely decompress files, I have forgotten the command to
decompress tar/bz2 files .
[...]
I just wanted to add my ¢2. You may want to evaluate the package named
unp and you will never
the
symlink to /usr/src/linux from your kernel-source.
Well then why the warning from the Kernel developers? And what's
this about symlinking? Symlinking what to what ?
Anybody? Where do people dump their kernel source anyway???
Well, the first person that says that the kernel
On Wed, 15 Aug 2007 10:36:52 +0900
Takehiko Abe [EMAIL PROTECTED] wrote:
Frank McCormick wrote:
Well, I always store there all the sources related with my
kernel, modules, etc... I haven't get any problem... BTW,
remember doing the symlink to /usr/src/linux from your
kernel-source
On Tuesday 14 August 2007 21:27, Wayne Topa wrote:
Anybody? Where do people dump their kernel source anyway???
I have always put my kernels in /usr/src. First time I've _ever_
heard of DO NOT USE THE /usr/src area. Just what readme did you
see _that_ in?
From linux-source-2.6.18
Ed Jabbour([EMAIL PROTECTED]) is reported to have said:
On Tuesday 14 August 2007 21:27, Wayne Topa wrote:
Anybody? Where do people dump their kernel source anyway???
I have always put my kernels in /usr/src. First time I've _ever_
heard of DO NOT USE THE /usr/src area. Just what
THE /usr/src area
because that is where the headers for libc I guess are stored.
What is up here ?
Well, I always store there all the sources related with my kernel,
modules, etc... I haven't get any problem... BTW, remember doing the
symlink to /usr/src/linux from your kernel-source
, remember doing the
symlink to /usr/src/linux from your kernel-source.
Well then why the warning from the Kernel developers? And what's
this about symlinking? Symlinking what to what ?
Anybody? Where do people dump their kernel source anyway???
I have always put my kernels
your kernel-source.
Well then why the warning from the Kernel developers? And what's
this about symlinking? Symlinking what to what ?
Anybody? Where do people dump their kernel source anyway???
Cheers
Frank
When I compile my own kernels, I usually put them in /usr/local/src
Frank McCormick wrote:
Well, I always store there all the sources related with my kernel,
modules, etc... I haven't get any problem... BTW, remember doing
the symlink to /usr/src/linux from your kernel-source.
Well then why the warning from the Kernel developers? And what's
this about
I have taken the first steps towards compiling an Nvidia module for my
Quadro-pro card...
I downloaded and installed the source for the current kernel, which
aptitude dumped into /usr/src. Reading the readme, one of the first
things it says is DO NOT USE THE /usr/src area because that is
/src area because that is
where the headers for libc I guess are stored. What is up here ?
Well, I always store there all the sources related with my kernel,
modules, etc... I haven't get any problem... BTW, remember doing the
symlink to /usr/src/linux from your kernel-source.
And as
I rarely
... BTW, remember doing the
symlink to /usr/src/linux from your kernel-source.
Well then why the warning from the Kernel developers? And what's
this about symlinking? Symlinking what to what ?
And as
I rarely decompress files, I have forgotten the command to
decompress tar/bz2 files
Hi,
I am running Sid + Xen and I am used to patch the nvidia-kernel-source [1] in
order to make it Xen friendly [2].
I was surprised to see, when I appliyed the patch that the source are already
patched: I mean patch command tells me so.
Is Xen compliance included or is it just a mistake I
Le Saturday 19 May 2007 11:49:55 Mihamina (R12y) Rakotomandimby, vous avez
écrit :
Hi,
I am running Sid + Xen and I am used to patch the nvidia-kernel-source [1]
in order to make it Xen friendly [2].
I was surprised to see, when I appliyed the patch that the source are
already patched: I
this:
kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22-
| rev | cut -c 2- | rev`
But the build still fails for anything after 2.6.16... since
that is the
last update for the wacom-kernel-source and 2.6.18 (or 20 for
me)
doesn't exist.
Plus, AFAICS, it isn't
On Thu, 2007-04-19 at 11:52 +0100, Emmanuele Massimi wrote:
I have read somewhere that the pen tablet should work out of the box,
after modprobing it. So I did a clean re-installation (since in my
previous one I did not install the Desktop Environment by default)
including the Desktop
On 19/04/07, Greg Folkert [EMAIL PROTECTED] wrote:
On Thu, 2007-04-19 at 11:52 +0100, Emmanuele Massimi wrote:
I have read somewhere that the pen tablet should work out of the box,
after modprobing it. So I did a clean re-installation (since in my
previous one I did not install the Desktop
/include/linux/utsrelease.h | cut -c 22- | rev | cut
-c 2- | rev`
But the build still fails for anything after 2.6.16... since that is the
last update for the wacom-kernel-source and 2.6.18 (or 20 for me)
doesn't exist.
Plus, AFAICS, it isn't needed anymore.
modprobe tells me:
/lib
.
line 48 needs to look like this:
kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut
-c 2- | rev`
But the build still fails for anything after 2.6.16... since that is the
last update for the wacom-kernel-source and 2.6.18 (or 20 for me)
doesn't exist
for the wacom-kernel-source and 2.6.18 (or 20 for me)
doesn't exist.
Plus, AFAICS, it isn't needed anymore.
modprobe tells me:
/lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko
Also found in for me in:
/lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko
a couple of
mistakes
relating to recent kernels.
line 48 needs to look like this:
kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev
| cut -c 2- | rev`
But the build still fails for anything after 2.6.16... since that is
the
last update for the wacom-kernel-source
-c 2- | rev`
But the build still fails for anything after 2.6.16... since that
is the
last update for the wacom-kernel-source and 2.6.18 (or 20 for me)
doesn't exist.
Plus, AFAICS, it isn't needed anymore.
modprobe tells me:
/lib/modules/2.6.18-4-k7/kernel
fails for anything after 2.6.16... since that is the
last update for the wacom-kernel-source and 2.6.18 (or 20 for me)
doesn't exist.
Plus, AFAICS, it isn't needed anymore.
modprobe tells me:
/lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko
Also
Hi all,
I've been browsing around, but I couldn't find anything related to this.
I have been trying to install the wacom-kernel-source package on Etch, but
it fails with the following error:
Setting up wacom-kernel-source (0.7.4.1-5) ...
/var/lib/dpkg/info/wacom-kernel-source.postinst: line 49
Hi all,
I've been browsing around, but I couldn't find anything related to this.
I have been trying to install the wacom-kernel-source package on Etch, but
it fails with the following error:
Setting up wacom-kernel-source (0.7.4.1-5) ...
/var/lib/dpkg/info/wacom-kernel-source.postinst: line 49
to this.
I have been trying to install the wacom-kernel-source package on Etch, but
it fails with the following error:
Setting up wacom-kernel-source (0.7.4.1-5) ...
/var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many
arguments
Warning: kernel headers don't match running Linux
-source package on Etch,
but
it fails with the following error:
Setting up wacom-kernel-source (0.7.4.1-5) ...
/var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many
arguments
Warning: kernel headers don't match running Linux version.
Building wacom modules for Linux _CODE 13262
browsing around, but I couldn't find anything related to this.
I have been trying to install the wacom-kernel-source package on Etch,
but
it fails with the following error:
Setting up wacom-kernel-source (0.7.4.1-5) ...
/var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many
Ok, thanks for your delucidation, I looked at both the lines, but I must
have skipped that word, in fact I couldn't tell the difference between the
two lines. I guess it's time to buy new glasses...
Anyways, this is what I get when I run dpkg-reconfigure wacom-kernel-source:
/usr/sbin/dpkg
when I run dpkg-reconfigure
wacom-kernel-source:
/usr/sbin/dpkg-reconfigure: wacom-kernel-source is broken or not fully
installed
Try
dpkg-reconfigure --force wacom-kernel-source
If anything goes wrong then please copy the complete output of this
command into a mail and send it to the list
time to buy new glasses...
Anyways, this is what I get when I run dpkg-reconfigure
wacom-kernel-source:
/usr/sbin/dpkg-reconfigure: wacom-kernel-source is broken or not fully
installed
Try
dpkg-reconfigure --force wacom-kernel-source
If anything goes wrong then please copy the complete
`
But the build still fails for anything after 2.6.16... since that is the
last update for the wacom-kernel-source and 2.6.18 (or 20 for me)
doesn't exist.
Plus, AFAICS, it isn't needed anymore.
modprobe tells me:
/lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko
Also found in for me in:
/lib
On Thu, Apr 12, 2007 at 03:33:23PM +0200, C. Mourad Jaber wrote:
Bonjour,
Existe-t-il un patch pour permettre la compilation du module nvidia
(1.0.9746) avec le noyau 2.6.20-1 tout fraîchement importé en instable ?
S'il y en a un, je ne l'ai pas trouvé :(
Par contre, j'ai réussi à compiler
Bonjour,
Existe-t-il un patch pour permettre la compilation du module nvidia
(1.0.9746) avec le noyau 2.6.20-1 tout fraîchement importé en instable ?
Merci
Mourad
--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.net/?DebianFrench
Vous pouvez aussi ajouter le
Hello all,
I am trying to use m-a to install ndiswrapper. I am using debian stable
with backports for module-assistant,build-essential,xorg,kde. m-a
prepare says everything is great and I made sure its getting the
linux-headers from backports. My kernel is stock from backports
2.6.18-4-k7 #1
Hello all,
I am trying to use m-a to install ndiswrapper. I am using debian stable
with backports for module-assistant,build-essential,xorg,kde. m-a
prepare says everything is great and I made sure its getting the
linux-headers from backports. My kernel is stock from backports
2.6.18-4-k7
://www.debian-multimedia.org etch main
# root dirs that may contain packages
# deb file:/root/ debs/
Subject: Re: when will nvidai-glx and nvidia-kernel-source hit etch?
From: Florian Kulzer [EMAIL PROTECTED] Date: Thu, 9 Nov
2006 12:26:22 +0100
On Tue, Nov 14, 2006 at 09:30:58 +, Alle Meije Wink wrote:
Apologies if this question has already been answered, but I have not
been able yet to get ANY version of nvidia-glx back on my system!
I run a mix of testing and experimental (?), see my sources.list below.
The nvidia driver
On Thu, Nov 09, 2006 at 08:00:34 +0100, Lubos Vrbka wrote:
hi,
actually, where does /usr/lib/xorg/modules/drivers/nvidia_drv.so come
from? (i hope i wrote the path correctly) is it part of the binary files
from nvidia.com? 'apt-file search' didn't reveal anything relevant.
Florian Kulzer wrote:
Now I am confused:
me too...
$ apt-file search nvidia_drv
nvidia-glx: usr/X11R6/lib/modules/drivers/nvidia_drv.o
nvidia-glx: usr/lib/xorg/modules/drivers/nvidia_drv.o
nvidia-glx-legacy: usr/lib/xorg/modules/drivers/nvidia_drv.o
i get empty output from apt-file.
Maybe
On Thu, Nov 09, 2006 at 10:38:23 +0100, Lubos Vrbka wrote:
Florian Kulzer wrote:
Now I am confused:
me too...
$ apt-file search nvidia_drv
nvidia-glx: usr/X11R6/lib/modules/drivers/nvidia_drv.o
nvidia-glx: usr/lib/xorg/modules/drivers/nvidia_drv.o
nvidia-glx-legacy:
nvidia-glx is a package, created from the nvidia-graphics-drivers source
package. nvidia-graphics-drivers contains the binary .run files from
nvidia.com plus some scripting voodoo used in package creation.
http://packages.debian.org/unstable/source/nvidia-graphics-drivers shows
the four packages
On Wed, Nov 08, 2006 at 19:40:39 +0100, Lubos Vrbka wrote:
nvidia-glx is a package, created from the nvidia-graphics-drivers source
package. nvidia-graphics-drivers contains the binary .run files from
nvidia.com plus some scripting voodoo used in package creation.
hi,
actually, where does /usr/lib/xorg/modules/drivers/nvidia_drv.so come
from? (i hope i wrote the path correctly) is it part of the binary files
from nvidia.com? 'apt-file search' didn't reveal anything relevant.
/usr/lib/xorg/modules/drivers/nvidia_drv.so is indeed part of the nvidia
Where's my source tree? How do I get one if I don't have one?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
1 - 100 of 1089 matches
Mail list logo
