Hey Dirk. Thank you! That worked, it compiles! And I don't have to get
my hands dirty with a patch. :)
On Fri, Oct 28, 2016 at 9:11 PM, Dirk Laebisch wrote:
> > Anyone else run into this on Sid very recently? Any hints or pointers?
>
> Yup.
> Providing some compile flags in:
> /usr/src/linux
On 10/28/2016 08:11 PM, Dirk Laebisch wrote:
Anyone else run into this on Sid very recently? Any hints or pointers?
Yup.
Providing some compile flags in:
/usr/src/linux/Makefile
around line 614 fixed it for me.
614 # force no-pie for distro compilers that enable pie by default
615 KBUILD_CF
> Anyone else run into this on Sid very recently? Any hints or pointers?
Yup.
Providing some compile flags in:
/usr/src/linux/Makefile
around line 614 fixed it for me.
614 # force no-pie for distro compilers that enable pie by default
615 KBUILD_CFLAGS += $(call cc-option, -fno-pie)
616 KBU
Will wrote on 10/28/16 17:21:
> Greetings,
>
> I usually have to run the NVIDIA installer after a kernel update, but
> something has changed that has broken the process to build the
> proprietary Nvidia kernel module. I've searched around a bit on the
> Intarwebs before coming to the list, so her
Greetings,
I usually have to run the NVIDIA installer after a kernel update, but
something has changed that has broken the process to build the
proprietary Nvidia kernel module. I've searched around a bit on the
Intarwebs before coming to the list, so here goes.
Installer: NVIDIA-Linux-x86_64-3
On Wed, Jul 10, 2013 at 10:13:01AM +0200, Ralf Mardorf wrote:
> On Wed, 2013-07-10 at 14:58 +1200, Chris Bannister wrote:
> > On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
> > > From the package description of dkms (Dynamic Kernel Module Support
> > > Framework);
> >
> > Then why is
On Wed, 10 Jul 2013 14:58:03 +1200
Chris Bannister wrote:
Hello Chris,
>On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
>> From the package description of dkms (Dynamic Kernel Module Support
>> Framework);
>Then why isn't it dkmsf?
:-)
--
Regards _
/ ) "The b
On Wed, 2013-07-10 at 14:58 +1200, Chris Bannister wrote:
> On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
> > From the package description of dkms (Dynamic Kernel Module Support
> > Framework);
>
> Then why isn't it dkmsf?
Why is it
mkdir
and not
md
or
mdir
resp. why isn't
m
On Tue, Jul 09, 2013 at 05:03:40PM +0100, Brad Rogers wrote:
> From the package description of dkms (Dynamic Kernel Module Support
> Framework);
Then why isn't it dkmsf?
--
"If you're not careful, the newspapers will have you hating the people
who are being oppressed, and loving the people who a
upgrade kernels.
The upgrade for kernel 3.2.* to 3.9.* broke the nvidia module, which has
to be recompiled at every kernel upgrade. Installing nvidia-kernel-dkms
brings in nearly everything you need to ensure that the nvidia kernel
module is automatically upgraded every time the kernel changes
thing is ok. And i have not any xorg.conf.
That's contrary to everything I've ever heard about running the nvidia
module. If you say you haven't got an xorg.conf I have to believe you.
>> the *-dkms nvidia kernel modules, as that way, it's all taken care of
>> for y
and nvidia videocards. For running applications on nvidia card i use
optiran command from shell.
> As for stopping working after upgrade, you are aware that the nVidia
> module needs to be recompiled after a kernel update? It's why I use the
> *-dkms nvidia kernel modules, as that wa
On 07/07/2013 12:01 PM, andrey.ry...@bilkent.edu.tr wrote:
i have jessy. why modprobe cannot find nvidia_drv.so? when i used wheezy i
didnot need the xorg.conf. it stopped to work after upgrading. There was
no problem when i had upgraded from wheeze to jessy. But when kernel
version was changed t
onf file to allow the use of the
nVidia driver.
As for stopping working after upgrade, you are aware that the nVidia
module needs to be recompiled after a kernel update? It's why I use the
*-dkms nvidia kernel modules, as that way, it's all taken care of for
you.
--
Regards _
On Sun, 07 Jul 2013, andrey.ry...@bilkent.edu.tr wrote:
>
> > Check to see if you have a symbolic link "nvidia"
> > in /usr/lib/nvidia which eventually points
> > to /usr/lib/nvidia/current/nvidia_drv.so
> yes i have:
>
> /usr/lib/nvidia/nvidia: symbolic link to `/etc/alternatives/nvidia'
> /etc
> Check to see if you have a symbolic link "nvidia"
> in /usr/lib/nvidia which eventually points
> to /usr/lib/nvidia/current/nvidia_drv.so
yes i have:
/usr/lib/nvidia/nvidia: symbolic link to `/etc/alternatives/nvidia'
/etc/alternatives/nvidia: symbolic link to `/usr/lib/nvidia/current'
# file /
On Sun, 07 Jul 2013, andrey.ry...@bilkent.edu.tr wrote:
> hi!
> if i do command:
> # modprobe nvidia
> i retrieve next message:
>
> FATAL: Module nvidia not found.
>
> but i have many nvidia-* packages installed
> and between them:
>
> ii nvidia-kernel-common
> 20130505+1 i386 NVIDIA b
> For what Debian release, resp. from what repository?
#lsb_release -a
Release:testing
Codename: jessie
# uname -a
Linux hostname 3.9-1-686-pae #1 SMP Debian 3.9.6-1 i686 GNU/Linux
> The module might be somewhere in /lib/modules/$(uname -r)/ .
#ls /lib/modules/$(uname -r)/
build
On Sun, 2013-07-07 at 17:19 +0300, andrey.ry...@bilkent.edu.tr wrote:
> hi!
> if i do command:
> # modprobe nvidia
> i retrieve next message:
>
> FATAL: Module nvidia not found.
>
> but i have many nvidia-* packages installed
> and between them:
>
> ii nvidia-kernel-common
hi!
if i do command:
# modprobe nvidia
i retrieve next message:
FATAL: Module nvidia not found.
but i have many nvidia-* packages installed
and between them:
ii nvidia-kernel-common 20130505+1
i386 NVIDIA binary kernel module support files
Hugo Vanwoerkom wrote:
Vincent Lefevre wrote:
On 2012-11-13 15:51:11 -0600, Hugo Vanwoerkom wrote:
But when I startx, X can't find the nvidia module:
...
(EE) Failed to load module "nvidia" (module does not exist, 0)
...
Any suggestions as to what to do next?
You probably ne
Vincent Lefevre wrote:
On 2012-11-13 15:51:11 -0600, Hugo Vanwoerkom wrote:
But when I startx, X can't find the nvidia module:
...
(EE) Failed to load module "nvidia" (module does not exist, 0)
...
Any suggestions as to what to do next?
You probably need xserver-xorg-vide
On 2012-11-13 15:51:11 -0600, Hugo Vanwoerkom wrote:
> But when I startx, X can't find the nvidia module:
>
> ...
> (EE) Failed to load module "nvidia" (module does not exist, 0)
> ...
>
> Any suggestions as to what to do next?
You probably need xserver-xorg
...
and lsmod shows:
...
nvidia 11186000 0
...
But when I startx, X can't find the nvidia module:
...
(EE) Failed to load module "nvidia" (module does not exist, 0)
...
Any suggestions as to what to do next?
Hugo
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.deb
Sean Whalen wrote:
> Hello All,
>
> I recently made the switch from Kubuntu 11.10 to Debain stable.
> Everything was running very well until I installed the Nvidia module
> "the Debian way". Then, the system became highly unstable. I noticed
> that the system would
Hi Sean,
For the past few days, I've been trying to install Squueze on my PC and have
experienced very similar troubles. My card is a GeForce 8400 GS. The screen and
the whole system freeze as soon as gdm3 starts. I installed the Nvidia module
"the Debian Way", and also (after
Hello All,
I recently made the switch from Kubuntu 11.10 to Debain stable.
Everything was running very well until I installed the Nvidia module
"the Debian way". Then, the system became highly unstable. I noticed
that the system would become very sluggish during simple tasks The
most
Richard wrote:
Hi
I had to purge everything I downloaded previously, blacklist nouveau, kill X &
gdm3, the run
NVIDIA-Linux-x86_64-290.10.run, then reboot.
No more shakey display and I can watch TV again without X crashing.
Good news. IMO the reboot is not necessary, just run
NVIDIA-Linux-x86
On Thu, 2011-11-24 at 20:32 +, Richard wrote:
> Hi
> I had to purge everything I downloaded previously, blacklist nouveau, kill X
> & gdm3, the run
> NVIDIA-Linux-x86_64-290.10.run, then reboot.
> No more shakey display and I can watch TV again without X crashing.
Good news :)
- Ralf
--
T
Hi
I had to purge everything I downloaded previously, blacklist nouveau, kill X &
gdm3, the run
NVIDIA-Linux-x86_64-290.10.run, then reboot.
No more shakey display and I can watch TV again without X crashing.
--
Best wishes / 73
Richard Bown
e-mail: rich...@g8jvm.com or richard.b...@blueyond
On Sat, 08 Oct 2011 15:51:30 +0200, Hans-J. Ullrich wrote:
>> I dunno how nor what "dkms" does but I would first check for the
>> basics, for instance, is nouveau module unloaded? Have you restared the
>> computer (or at least the X server) after installing -and setting as
>> default- the nvidia d
> I dunno how nor what "dkms" does but I would first check for the basics,
> for instance, is nouveau module unloaded? Have you restared the computer
> (or at least the X server) after installing -and setting as default- the
> nvidia driver?
DKMS is just building and installing the modulel. Howev
On Sat, 08 Oct 2011 15:10:36 +0200, Hans-J. Ullrich wrote:
> Me again!
:-)
(let me change the subject for this thread to avoid mixing with the other
one)
> Now I went back to the latest nvidia driver. Building went fine (I am
> using dkms), but it inhibits to load.
>
> See the last strace ou
I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.
First of, Debian has the following versions of nvidia-kernel-dkms packages:
squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1
The version in squeeze fail on anything above
I switched to custom kernel and came across this thread. I also use
squeeze and this is what I have found.
First of, Debian has the following versions of nvidia-kernel-dkms packages:
squeeze: 195.36.31-6
sid/wheezy: 260.19.44-1
experimental: 270.30-1
The version in squeeze fail on anything above
MRH writes:
>On 23/01/11 04:53, Cameron Hutchison wrote:
>> and I had to revert two commits to fix it:
>>
>> 7b8ea53d7f1865cd8f05dfb8f706a4ff5a72abcf (makefile: not need to
>> regenerate kernel.release file when make kernelrelease)
>>
>> 01ab17887f4cdcb8bb5a5d1bc3b160d186e6e99b (Makefile: "make ke
On 23/01/11 04:53, Cameron Hutchison wrote:
"tv.deb...@googlemail.com" writes:
The problem with extraversion and 2.6.37 is known, it's been reported
here if I remember, look for a message starting with "kernel-package:
2.6.37" in the archives. But since it seems to affect only proprietary
soft
On 22/01/11 23:03, tv.deb...@googlemail.com wrote:
[...]
I have the same setup, I build my kernel (2.6.37 currently) with
kernel-package and both nvidia and VirtualBox 4 work fine (they build
automatically with dkms). I don't use extraversion, only
--append-to-version and --revision.
The problem
"tv.deb...@googlemail.com" writes:
>The problem with extraversion and 2.6.37 is known, it's been reported
>here if I remember, look for a message starting with "kernel-package:
>2.6.37" in the archives. But since it seems to affect only proprietary
>software I guess they'll have to adapt.
Since
On Saturday 22 January 2011 13:24:08 MRH wrote:
> Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
> that moment it stopped working, saying that the kernel driver (vboxdrv)
> is not loaded and suggesting to run /etc/init.d/vboxdrv setup
>
> This fails:
> --
> Stopping V
>On the 22/01/2011 23:20, MRH wrote:
>> On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
>> In<4d3b20c8.3080...@o2.pl>, MRH wrote:
>>>CC [M]
>>> /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
>>> In file included from
>>> /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox
On 22/01/11 19:42, Boyd Stephen Smith Jr. wrote:
In<4d3b20c8.3080...@o2.pl>, MRH wrote:
CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
In file included from
/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
from
/var/lib/dkms/vboxho
In <4d3b20c8.3080...@o2.pl>, MRH wrote:
> CC [M] /var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/SUPDrv-linux.o
>In file included from
>/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/include/VBox/types.h:30,
> from
>/var/lib/dkms/vboxhost/4.0.2/build/vboxdrv/linux/../SUPDrvInternal
Hi,
You're not gonna get much help using non-free software on a tarnished
kernel. That said, when i have problems with VBox i just purge
everything, dkms included, make sure the drivers are actually deleted,
then reinstall, with dkms. Usually does the trick.
HTH,
Nuno
--
Mars 2 Stay!
http://xkc
Recently I updated VirtualBox from 3.2 to 4.0 (non OSE version). From
that moment it stopped working, saying that the kernel driver (vboxdrv)
is not loaded and suggesting to run /etc/init.d/vboxdrv setup
This fails:
--
Stopping VirtualBox kernel modules:done..
Uninstalling old VirtualBo
On Sat, 27 Jun 2009 23:20:04 +0200, Norbert Zeh wrote:
>> 'aptitude search nvidia' showed the following packages as installed:
>> nvidia-settings
>> nvidia-kernel-common
>> nvidia-xconfig
>> nvidia-glx
>> nvidia-kernel-2.6.26-1-amd64
>
> I'm just guessing, but shouldn't you install
> nv
> 'aptitude search nvidia' showed the following packages as installed:
> nvidia-settings
> nvidia-kernel-common
> nvidia-xconfig
> nvidia-glx
> nvidia-kernel-2.6.26-1-amd64
I'm just guessing, but shouldn't you install
nvidia-kernel-2.6.26-2-amd64 if you run linux-image-2.6.26-2-amd64? A
n quit, displaying only a command-line login prompt.
syslog and Xorg.0.log both indicated that the system couldn't find the
nvidia module (the open source version from the Debian repositories).
Here are the last few lines from Xorg.0.log:
--
(EE) NVIDIA(0): Failed to load the NVIDIA kerne
On Fri, 2007-06-15 at 11:57 +0200, Eeltje wrote:
> Did you get the nvidia module working again? It would be nice if you told
> whether you were successful or not...
> --
> Eeltje de Vries
>
>
I am sorry not to reply early. I was busy for some personal business.
Yes, this
Did you get the nvidia module working again? It would be nice if you told
whether you were successful or not...
--
Eeltje de Vries
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The link is:
[url]http://www.debianhelp.org/node/8092[/url]
To repeat the story written there:
I send a bug report (see:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=428731) and within minutes I
got a work around!
What one has to do (as 'root') is:
# cd /usr/lib/xorg/modules/drivers
#
arijit wrote:
Hi all,
I've just updated Xorg packages though synaptic.
But after system restart, i am unable to start X-server.
Error shown : unable to load module: nvidia
Exact same problem in my Etch box too. The work around for now is to run
dpkg-reconfigure xserver-xorg and to select "nv"
Can you post the link of that thread?
On 6/14/07, Eeltje <[EMAIL PROTECTED]> wrote:
I had the same problem, see a different thread. There you can also find
how it can be solved!
--
Eeltje de Vries
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Conta
I had the same problem, see a different thread. There you can also find how it
can be solved!
--
Eeltje de Vries
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
; ':0.0'.
> > -
> >
> > Here's the some output from Xorg.log:-
> > -------------
--
>
> Here's the some output from Xorg.log:-
> -
> II) LoadModule: "nvidia"
---
II) LoadModule: "nvidia"
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: "nvidia"
(EE) Failed to load module "nvidia" (module does not exist, 0)
II) LoadModule: "nvidia"
(WW) Warning, couldn't open module nvidia
(II) UnloadModule: "nvidia"
(EE) Failed to load module "nvidia" (module does not exist, 0)
---
On Wed October 25 2006 06:39, David Baron wrote:
> On Wednesday 25 October 2006 13:29, Chris Bannister wrote:
> > On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
> > > With this install of Debian I decided to stick to what I know, and
> > > grabbed the binary installer direct from NVidia.
On Wednesday 25 October 2006 13:29, Chris Bannister wrote:
> On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
> > With this install of Debian I decided to stick to what I know, and
> > grabbed the binary installer direct from NVidia. I ran that, and in
> > less than two minutes I was up a
* Chris Bannister ([EMAIL PROTECTED]) wrote:
>
> Apparently the binary installer from NVidia messes with the libraries on
> the system and is not the recommended method for installing.
>
> Read http://home.comcast.net/~andrex/Debian-nVidia/
>
> The Debian way is certainly a lot easier. Now where
On Mon, Oct 23, 2006 at 11:31:46PM -0500, cothrige wrote:
> With this install of Debian I decided to stick to what I know, and
> grabbed the binary installer direct from NVidia. I ran that, and in
> less than two minutes I was up and running. No complaints from Debian
> and no complaints from NVi
Tim Wood wrote:
I decided to follow the advise in one of Florian' links (Thanks Florian)
and use the NVIDIA_kernel-1.0-8178-1444349.diff.txt patch to the 7676
driver. After fixing a few links, it's up and running.
Must say that I'm a bit bemused at applying an 8178 patch to the 7676
driver,
I decided to follow the advise in one of Florian' links (Thanks Florian)
and use the NVIDIA_kernel-1.0-8178-1444349.diff.txt patch to the 7676
driver. After fixing a few links, it's up and running.
Must say that I'm a bit bemused at applying an 8178 patch to the 7676
driver, but have not gone
I receive the digest, so hope this reads ok.
Tim Wood wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some
H.S. wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined
H.S. wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined
Tim Wood wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Searching google has
to be able to fix this problem.
>
> What exactly does this message mean and how can "configure kernel source"
> so that module-assistant is happy.
>
> R.Parr
> Temporal Arts
I got this problem too. But the very first time when I tried to compile
and install the nvidia mo
H.S. wrote:
> I have installed the new 2.6.16 kernel on two machines running Debian
> Sid and tried to install nvidia module. On both machines, the module
> compilation (using module-assistant) fails with some error messages
> (IIRC there was some error about rlim structure not b
H.S. wrote:
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined
I have installed the new 2.6.16 kernel on two machines running Debian
Sid and tried to install nvidia module. On both machines, the module
compilation (using module-assistant) fails with some error messages
(IIRC there was some error about rlim structure not being defined).
Searching google has
start. The
> error log indicated that the Nvidia module couldnot be loaded. Below are
> the last few lines from the XFree86 log:
>
> (II) Setting vga for screen 0.
> (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
> (==) NVIDIA(0): RGB weight 888
> (==) NVIDIA(0): Default v
Hi,
I thought of restarting my machine after the browser was getting stuck
at some websites since last night. On restarting, X couldn't start. The
error log indicated that the Nvidia module couldnot be loaded. Below are
the last few lines from the XFree86 log:
(II) Setting vga for scr
I fixed the problem, but I still don't know what
caused it. The nvidia module failed to load. I also
notice my soundcard module (i810_audio) wasn't loaded.
I added "nvidia' and "i810_audio" to /etc/modules,
and now everything is working as before. These
modules we
The previous upgrade was done only a few days ago
(Sunday or Monday I think). Whatever is causing the
problem was loaded into Debian unstable in the past
week or less.
I have a custom kernel that wasn't upgraded by apt and
the Nvidia module was directly from nvidia.com, so it
wasn'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew Yates wrote:
| Does anyone know how I can check to see which packages
| were upgraded last night? I didn't keep track of it,
| but it may be helpful in figuring out the source of
| the problem. My kernel is custom, so it was not
| upgraded.
I
I run Debian unstable on my desktop at home. I did an
"apt-get upgrade" last night and this morning my
Nvidia module failed to load. The "nv" module works
OK, but I need TV-out functionality. My kernel is
2.6.7 and the Nvidia module was downloaded from
nvidia.com and insta
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Collet Brunel wrote:
| Check if the nvidia-kernel-source version matches with
| the nvidia-glx package version.. there may be a
| conflict there..
Not in my case;
[EMAIL PROTECTED]:~$ dpkg -l nvidia-kernel-source
Desired=Unknown/Install/Remove/Purge/Hol
Check if the nvidia-kernel-source version matches with
the nvidia-glx package version.. there may be a
conflict there..
___
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora!
http://b
pic pci=noacpi pci=biosirq
recompile kernel without any modules, without APIC
module-assistant auto-install nvidia
(kernel already compiled without 4K stacks)
(have not included rivafb)
the nvidia module installs fine but still get a blank screen.
I'm going off the nvidia hardware, my mother also c
> apt-get install kernel-source-2.6.7 nvidia-kernel-source
> nvidia-kernel-common
> tar xvjf kernel-source-2.6.7.bz2
> tar xvzf nvidia-kernel-source.tar.gz
> ln -s kernel-source-2.6.7 linux
> cd linux
> (fakeroot make-kpkg clean)
> make menuconfig
> fakeroot make-kpkg --revision=20041201 kernel_ima
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Olle Eriksson wrote:
| On Tuesday 30 November 2004 22.18, Tim Beauregard wrote:
|>I am unable to use the nvidia module compiled from nvidia-kernel-source
|>that is used with the nvidia-glx package. On boot-up, the computer
|>freezes when g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I am unable to use the nvidia module compiled from nvidia-kernel-source
that is used with the nvidia-glx package. On boot-up, the computer
freezes when gdm starts. The error message I get in the logs is
Failed to initialize the NVIDIA
On 31. December 2003 at 4:50AM -0400,
Stephen Cormier <[EMAIL PROTECTED]> wrote:
> On December 29, 2003 10:59 pm, Bradley Alexander wrote:
> >When I tried to load the module under 2.6.0, I got the message
> >FATAL: Error inserting nvidia
> >(/lib/modules/2.6.0/nvidia/nvidia.ko): Invalid module fo
On December 29, 2003 10:59 pm, Bradley Alexander wrote:
>When I tried to load the module under 2.6.0, I got the message
> FATAL: Error inserting nvidia (/lib/modules/2.6.0/nvidia/nvidia.ko):
> Invalid module format
>
Starting with about test7 and onwards I had to us modprobe -f nvidia to
get the
On Mon, Dec 29, 2003 at 10:39:11PM -0700, Jamin W. Collins wrote:
> On Mon, Dec 29, 2003 at 09:59:58PM -0500, Bradley Alexander wrote:
> > On Mon, 29 Dec 2003 14:32:08 -0700
> > "Jamin W. Collins" <[EMAIL PROTECTED]> wrote:
> > >
> > > When you load the module manually, does it show in the output
On Mon, Dec 29, 2003 at 09:59:58PM -0500, Bradley Alexander wrote:
> On Mon, 29 Dec 2003 14:32:08 -0700
> "Jamin W. Collins" <[EMAIL PROTECTED]> wrote:
> >
> > When you load the module manually, does it show in the output of lsmod?
>
> Yep. That was the first thing I checked when looking under 2.
On Monday December 29 at 09:59pm
Bradley Alexander <[EMAIL PROTECTED]> wrote:
> Yep. That was the first thing I checked when looking under 2.4.23.
> When I tried to load the module under 2.6.0, I got the message
>
> FATAL: Error inserting nvidia (/lib/modules/2.6.0/nvidia/nvidia.ko):
> Invalid
On Mon, 29 Dec 2003 14:32:08 -0700
"Jamin W. Collins" <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 29, 2003 at 04:18:40PM -0500, Bradley M Alexander wrote:
> > I just built a sid box from bare metal last week, and am having
> > problems getting the nVidia drivers to load. I tried this under 2.4.23
> >
On Mon, Dec 29, 2003 at 04:18:40PM -0500, Bradley M Alexander wrote:
> I just built a sid box from bare metal last week, and am having problems
> getting the nVidia drivers to load. I tried this under 2.4.23 and 2.6.0,
> and in both cases, the module refuses to load. At this point, I'm not sure
> i
uot;
Then there pages of
Not loading .note.GNU-stack
Not loading .note.GNU-stack
...and finally...
(EE) Failed to load module "nvidia" (module does not exist, 0)
Not loading .note.GNU-stack
(EE) No drivers available.
Fatal server error:
no screens found
This happens whether I load th
On Fri, 2003-02-07 at 16:54, Alan Thompson wrote:
> On Sat, Feb 08, 2003 at 12:26:29AM +, Nic Strong wrote:
> > Hi,
> >
> > Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
> > whenever I start x the nvidia module does not auto load i have to
On Sat, Feb 08, 2003 at 12:26:29AM +, Nic Strong wrote:
> Hi,
>
> Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
> whenever I start x the nvidia module does not auto load i have to do an
> explicit 'insmod nvidia' (i never had to do this in the
t 01:26, Nic Strong wrote:
> Hi,
>
> Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
> whenever I start x the nvidia module does not auto load i have to do an
> explicit 'insmod nvidia' (i never had to do this in the past).
>
> /etc/modules has the
re
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.
nvidia
-Luck
On Fri, 2003-02-07 at 18:26, Nic Strong wrote:
> Hi,
>
> Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
> whenever
Hi,
Ever since compiling 2.4.20 kernel and the nvidia module/glx (4191)
whenever I start x the nvidia module does not auto load i have to do an
explicit 'insmod nvidia' (i never had to do this in the past).
/etc/modules has the following lines:
### update-modules: start processing /et
98 matches
Mail list logo
