switching to debian (... and installing the NVIDIA GeForce4)

switching to debian (... and installing the NVIDIA GeForce4)

[Karthik Vishwanath]

Hello,

I recently installed the 3.0 debian linux (on an AMD 1500 pc) and am
learning the ways of debian packaging. I obtained a netinst iso, burned
the image and successfully rebooted back into debian. Next, I used tasksel
get all the packages that seemed relevant. Somehow I missed choosing
XFree86 (I think), initially. dselect along with the debian reference
manual helped me fix that (by installing x-window-system-core,
xfree86-common, etc). During the setup process I selected GeForce as my
video card. startx did work - XFree86.0.log told me the error was:  (EE)
No devices detected. Googling for "GeForce4 debian configuration" gave me 
hits - the first one indicated that I must:

# cd /usr/src
# apt-get install nvidia-glx-src nvidia-kernel-src
# tar -zxf nvidia-kernel-src.tar.gz
# cd linux
# make-kpkg clean
# make-kpkg modules_image

I do not have the kernel source (I installed a pre-configured kernel -
kernel-image-2.4.18-k7) installed, and therefore do not have a
/usr/src/linux. Must I download the kernel source and follow the
instructions above? Is there an alternative way of enabling this card by
inserting a (precompiled?) module (is the above asking me to do exactly
that?)?

Require guidance...

Thanks,

-K

PS: Must I have my /etc/sources.list updated periodically? Is there a 
utility to have it updated automatically? 

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[joy]

Karthik Vishwanath wrote:

>Hello,
>
>I recently installed the 3.0 debian linux (on an AMD 1500 pc) and am
>learning the ways of debian packaging. I obtained a netinst iso, burned
>the image and successfully rebooted back into debian. Next, I used tasksel
>get all the packages that seemed relevant. Somehow I missed choosing
>XFree86 (I think), initially. dselect along with the debian reference
>manual helped me fix that (by installing x-window-system-core,
>xfree86-common, etc). During the setup process I selected GeForce as my
>video card. startx did work - XFree86.0.log told me the error was:  (EE)
>No devices detected. Googling for "GeForce4 debian configuration" gave me 
>hits - the first one indicated that I must:
>  
>
I see that you are using a Geforce 4 in a debian woody system. the 
Xfree86 along with the stable distro does
not support the GF4. so you better get the latest nvidia drivers for 
linux from nvidia.com and install it.
that should( no, will ;-) clear up your problem.

>-
>To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.linux-learn.org/faqs
>
>  
>



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Karthik Vishwanath]

Which driver(s) must I get from nvidia? I can get to their download site 
(nvidia.com/object/linux.html), but am unsure what I need to download. 

I got the latest version which gives me a file:  
NVIDIA-Linux-x86-1.0-5336-pkg1.run.  

# sh NVIDIA-Linux-x86-1.0-5336-pkg1.run

quits with a series of errors saying that "no matching precompiled kernel
interface was found", followed by "unable to find your kernel source
tree".

Now, I think a part of the problem here is that I do not have a matching
kernel that is running with a kernel source. 'uname -r ' gives 2.4.18-k7.  
I can find (and have installed) a kernel-source-2.4.18 package, but not a
kernel-source-2.4.18-k7 package. How to fix it?

Thanks,

-K

On Tue, 23 Mar 2004, at 8:47am, joy wrote:

> I see that you are using a Geforce 4 in a debian woody system. the
> Xfree86 along with the stable distro does not support the GF4. so you
> better get the latest nvidia drivers for linux from nvidia.com and
> install it. that should( no, will ;-) clear up your problem.
> 

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 11:44 PM 3/22/2004 -0500, Karthik Vishwanath wrote:
>Which driver(s) must I get from nvidia? I can get to their download site
>(nvidia.com/object/linux.html), but am unsure what I need to download.
>
>I got the latest version which gives me a file:
>NVIDIA-Linux-x86-1.0-5336-pkg1.run.
>
># sh NVIDIA-Linux-x86-1.0-5336-pkg1.run
>
>quits with a series of errors saying that "no matching precompiled kernel
>interface was found", followed by "unable to find your kernel source
>tree".
>
>Now, I think a part of the problem here is that I do not have a matching
>kernel that is running with a kernel source. 'uname -r ' gives 2.4.18-k7.
>I can find (and have installed) a kernel-source-2.4.18 package, but not a
>kernel-source-2.4.18-k7 package. How to fix it?


Short answer: to use the nVidia proprietary X driver, you need on your 
system the kernel source that matches your installed kernel. This is so 
because part of what the nVidia package provides is a customized 
framebuffer in the form of a kernel module called "nvidia".

How did you install the kernel-source-2.4.18 package you mention? If you 
just did the apt-get (or dselect, if you do it that way) part, you did not 
un'tar the source tree. You just have a package called something like 
/usr/src/kernel-source-2.4.18.tar.bz2 . You need to do two things for the 
nvidia installer to run properly:

         1. un'tar the source in the usual way.
         2. make the customary symlink:
                 ln -s /usr/src/kernel-source-2.4.18 linux

Then the nvidia installer should succeed.

(NOTE: The one thing I cannot vouch for is that kernel-source-2.4.18 and 
kernel-image-2.4.18-k7 packages actually match up. I always compile my own 
kernels after installing, so I have no actual experience with using the 
Debian kernel-image-* packages.)



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Tuesday 23 March 2004 05:44, Karthik Vishwanath wrote:
> Which driver(s) must I get from nvidia? I can get to their download site
> (nvidia.com/object/linux.html), but am unsure what I need to download.
>
> I got the latest version which gives me a file:
> NVIDIA-Linux-x86-1.0-5336-pkg1.run.

I have this one on a slackware 9 system using a TI4200
and on suse 9 with a FX5200 works fine.

> # sh NVIDIA-Linux-x86-1.0-5336-pkg1.run
>
> quits with a series of errors saying that "no matching precompiled kernel
> interface was found", followed by "unable to find your kernel source
> tree".
>
> Now, I think a part of the problem here is that I do not have a matching
> kernel that is running with a kernel source. 'uname -r ' gives 2.4.18-k7.
> I can find (and have installed) a kernel-source-2.4.18 package, but not a
> kernel-source-2.4.18-k7 package. How to fix it?

If you installed the source for 2.4.18 then you should be able to do the 
following and get away with it;

cd /usr/src/linux
make mrproper
cp /boot/config-xx .config
edit Makefile
change line 4 from 
EXTRAVERSION =
To
EXTRAVERSION = -k7
save file;
make oldconfig
make dep
Thats it, now rerun
sh NVIDIA-Linux-x86-1.0-5336-pkg1.run

Note;
i am presuming that debian has the default kernel config in /boot, most 
systems do store it there for your convinance.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[joy]

Ray Olszewski wrote:

> Short answer: to use the nVidia proprietary X driver, you need on your 
> system the kernel source that matches your installed kernel. This is 
> so because part of what the nVidia package provides is a customized 
> framebuffer in the form of a kernel module called "nvidia".
>
> How did you install the kernel-source-2.4.18 package you mention? If 
> you just did the apt-get (or dselect, if you do it that way) part, you 
> did not un'tar the source tree. You just have a package called 
> something like /usr/src/kernel-source-2.4.18.tar.bz2 . You need to do 
> two things for the nvidia installer to run properly:
>
>         1. un'tar the source in the usual way.
>         2. make the customary symlink:
>                 ln -s /usr/src/kernel-source-2.4.18 linux
>
> Then the nvidia installer should succeed.
>
> (NOTE: The one thing I cannot vouch for is that kernel-source-2.4.18 
> and kernel-image-2.4.18-k7 packages actually match up. I always 
> compile my own kernels after installing, so I have no actual 
> experience with using the Debian kernel-image-* packages.)

yup, I suggest the same. get your own kernel sources and compile them. 
if you get a 2.6 series kernel, you need to upgrade a few packages on 
the system( the version numbr of the software  required is found in the 
sources in /Documentation/Changes.I suggest you get a 2.6, it's worth 
the download and you will really feel the difference and also the 5336 
version has support for the 2.6 series and I see no reason you shuld not 
take advantage of this.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 10:49 PM 3/23/2004 +0530, joy wrote:
[...]
>>(NOTE: The one thing I cannot vouch for is that kernel-source-2.4.18 and 
>>kernel-image-2.4.18-k7 packages actually match up. I always compile my 
>>own kernels after installing, so I have no actual experience with using 
>>the Debian kernel-image-* packages.)
>
>yup, I suggest the same. get your own kernel sources and compile them. if 
>you get a 2.6 series kernel, you need to upgrade a few packages on the 
>system( the version numbr of the software  required is found in the 
>sources in /Documentation/Changes.I suggest you get a 2.6, it's worth the 
>download and you will really feel the difference and also the 5336 version 
>has support for the 2.6 series and I see no reason you shuld not take 
>advantage of this.

I haven't myself switched to the 2.6.x kernel series yet, but I have seen 
reports warning of problems with some external add-in modules, including 
the nvidia drivers ... showing up as high CPU loads caused, I think, by 
context switching not being handled efficiently. (Also problems with ivtv 
and lirc, if memory serves, and maybe some of the wlan stuff.)

Caution ... or, better, patience, as this stuff will certainly get worked 
out ... *may* be indicated here.

Joy - do you actually have an nvidia framebudffer module running with 2.6.x?



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Tuesday 23 March 2004 18:19, joy wrote:
> yup, I suggest the same. get your own kernel sources and compile them.
> if you get a 2.6 series kernel, you need to upgrade a few packages on
> the system( the version numbr of the software  required is found in the
> sources in /Documentation/Changes.I suggest you get a 2.6, it's worth
> the download and you will really feel the difference and also the 5336
> version has support for the 2.6 series and I see no reason you shuld not
> take advantage of this.

I dont want to sound like a wet blanket, however i have a machine here running 
a 2.6 kernel, be aware there are issues with the nvidia video drivers, or at 
least i have some.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[joy]

Ray Olszewski wrote:

> I haven't myself switched to the 2.6.x kernel series yet, but I have 
> seen reports warning of problems with some external add-in modules, 
> including the nvidia drivers ... showing up as high CPU loads caused, 
> I think, by context switching not being handled efficiently. (Also 
> problems with ivtv and lirc, if memory serves, and maybe some of the 
> wlan stuff.)
>
> Caution ... or, better, patience, as this stuff will certainly get 
> worked out ... *may* be indicated here.
>
> Joy - do you actually have an nvidia framebudffer module running with 
> 2.6.x?

yes, have been using the 2.6 series almost as soon as it was released 
and used to use the patches from minion.de until the
5336 nvidia driver was released. I don't exactly understand your Q (too 
hitech for me ;-) however I figure you are asking
 me about it's (kernel's) performance under heavy loads. well I ran 3 
instances of xine playing (what else) 'Highway Star'
at the same time on KDE which I think should put the cpu under load, Kde 
being the major load :) with no problems.
this was . 2.6.1or .2 maybe...........

>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[joy]

pa3gcu wrote:

>I dont want to sound like a wet blanket, however i have a machine here running 
>a 2.6 kernel, be aware there are issues with the nvidia video drivers, or at 
>least i have some.
>  
>
I too had some problems in the beginning, but I believe APIC support on 
uniprocessor systems breaks the driver...
try disabling it and see if there is any difference coz after I did the 
same, X has never hung on me ( it used to do so very often before)
and thats atleast a month or two

>  
>



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 06:47 PM 3/24/2004 +0530, joy wrote:
>Ray Olszewski wrote:
>
>>I haven't myself switched to the 2.6.x kernel series yet, but I have seen 
>>reports warning of problems with some external add-in modules, including 
>>the nvidia drivers ... showing up as high CPU loads caused, I think, by 
>>context switching not being handled efficiently. (Also problems with ivtv 
>>and lirc, if memory serves, and maybe some of the wlan stuff.)
>>
>>Caution ... or, better, patience, as this stuff will certainly get worked 
>>out ... *may* be indicated here.
>>
>>Joy - do you actually have an nvidia framebudffer module running with 2.6.x?
>
>yes, have been using the 2.6 series almost as soon as it was released and 
>used to use the patches from minion.de until the
>5336 nvidia driver was released. I don't exactly understand your Q (too 
>hitech for me ;-) however I figure you are asking
>me about it's (kernel's) performance under heavy loads. well I ran 3 
>instances of xine playing (what else) 'Highway Star'
>at the same time on KDE which I think should put the cpu under load, Kde 
>being the major load :) with no problems.
>this was . 2.6.1or .2 maybe...........

Hard to say from this description if you are seeing the problems I read 
about or not. With a sufficiently fast CPU ... a 3 GHz P4, say ... I could 
run xine this way using xshm, and that video method is a real CPU hog. A 
better test would be something like this:

1. run a single instance of xine in the current display, playing back 
something suitable (I don't know what "Highway Star" is ... or, more 
important to the test, how it is encoded (what resolution, what bitrate, 
what codec)). Make sure xine is using xVideo ("xine -V xv 
filename_to_play"). Have xine resizing the video ... double size if that 
works to keep everything actually visible onscreen.

2. also in the current display, run "top". With the entire xie playback 
visible onscreen, note both total CPU use and its components. The total 
should be quite low, under 5% usually, if all is working smoothly. If the 
total is high, and both the "system" and "user" components contribute 
significantly to it, you are seeing the problem I've read about, even if 
the system is managing to keep up.

3. Mention what CPU -- type and speed -- is involved. The faster the CPU, 
the lower the number should be in step 2.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Karthik Vishwanath]

I installed the 2.4.18 source by 'apt-get install kernel-source-2.4.18', 
extracted the source and made a symbolic /usr/src/linux -> 
/usr/src/kernel-source-2.4.18/, and followed all the instructions below
as is. 

sh NVIDIA-Linux-x86-1.0-5336-pkg1.run quits with an error. 

# cat /var/log/nvidia-installer.log | grep ^ERROR
ERROR: Unable to determine the NVIDIA kernel module filename.


How to proceed? 

Thanks,

-K

On Tue, 23 Mar 2004, at 3:49pm, pa3gcu wrote:

> If you installed the source for 2.4.18 then you should be able to do the 
> following and get away with it;
> 
> cd /usr/src/linux
> make mrproper
> cp /boot/config-xx .config
> edit Makefile
> change line 4 from 
> EXTRAVERSION =
> To
> EXTRAVERSION = -k7
> save file;
> make oldconfig
> make dep
> Thats it, now rerun
> sh NVIDIA-Linux-x86-1.0-5336-pkg1.run
> 
> Note;
> i am presuming that debian has the default kernel config in /boot, most 
> systems do store it there for your convinance.
> 
> 



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 09:46 AM 3/25/2004 -0500, Karthik Vishwanath wrote:

>I installed the 2.4.18 source by 'apt-get install kernel-source-2.4.18',
>extracted the source and made a symbolic /usr/src/linux ->
>/usr/src/kernel-source-2.4.18/, and followed all the instructions below
>as is.
>
>sh NVIDIA-Linux-x86-1.0-5336-pkg1.run quits with an error.
>
># cat /var/log/nvidia-installer.log | grep ^ERROR
>ERROR: Unable to determine the NVIDIA kernel module filename.
>
>
>How to proceed?

Preliminary question: Are you using an installer you got from nVidia, or 
are you using the Debian package nvidia-kernel-source (from non-free/X11)?

Second question: Did you edit the Makefile in /usr/src/linux so it matches 
the version of the running kernel EXACTLY (as reported by "uname -a"; I 
don't care what name the kernel file has)? I ask in part because Richard's 
instructions contain a small typo you may have missed. He says to edit the 
Makefile as follows:
         > change line 4 from
         > EXTRAVERSION =
         > To
         > EXTRAVERSION = -k7

In fact, it should read

         EXTRAVERSION =-k7

(without the space before the hyphen).

Third, I think we are going to have to see the context of the error 
message. I can't find in the nVidia installer where that message is 
generated, so it must come from the binary portion somewhere. The preceding 
lines in the log (or onscreen) probably give some context for interpreting 
the message. If the log file is small (mine is, but from a successful 
install of 4363), include it all. IF it is too long for that, include the 
immediate context of the error.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 16:42, Ray Olszewski wrote:
> In fact, it should read
>
>          EXTRAVERSION =-k7
>
> (without the space before the hyphen).

No sorry Ray its not a typo, its how it should be a as matter of fact,
It possably works without a white space but AFAIK white spaces are ignored.

If for example you look into any Topdir Makefile you will note that lines 1, 
2, and 3 have white spaces after the =  and the 4th line should comply as 
well or so i was once told.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 15:46, Karthik Vishwanath wrote:
> I installed the 2.4.18 source by 'apt-get install kernel-source-2.4.18',
> extracted the source and made a symbolic /usr/src/linux ->
> /usr/src/kernel-source-2.4.18/, and followed all the instructions below
> as is.
>
> sh NVIDIA-Linux-x86-1.0-5336-pkg1.run quits with an error.
>
> # cat /var/log/nvidia-installer.log | grep ^ERROR
> ERROR: Unable to determine the NVIDIA kernel module filename.


No No No, /usr/src/kernel-source-2.4.18/ is NOT what you want i can assure 
you.

When you untarred the source a directory called linux-2.4.18 should have been 
created you then need to create a symlink to "linux" for my example 
underneat, so lets start again.


cd /usr/src
tar xvzf /path/to/linux-2.4.18.tar.gz
A directory will be created called linux-2.4.18 which now contains the source, 
so you now need to do;
ln -s linux-2.4.18 linux
cd linux
Now edit the Makefile and do like i said.

You can also use the installer with the  --help option you will see that one 
can use switches to direct the installer to "uncommon" directorys, however 
belive me its better to do as i say because sooner or later you WILL get 
problems.

>
> How to proceed?
>
> Thanks,
>
> -K
>
> On Tue, 23 Mar 2004, at 3:49pm, pa3gcu wrote:
> > If you installed the source for 2.4.18 then you should be able to do the
> > following and get away with it;
> >
> > cd /usr/src/linux
> > make mrproper
> > cp /boot/config-xx .config
> > edit Makefile
> > change line 4 from
> > EXTRAVERSION =
> > To
> > EXTRAVERSION = -k7
> > save file;
> > make oldconfig
> > make dep
> > Thats it, now rerun
> > sh NVIDIA-Linux-x86-1.0-5336-pkg1.run
> >
> > Note;
> > i am presuming that debian has the default kernel config in /boot, most
> > systems do store it there for your convinance.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 05:15 PM 3/25/2004 +0100, pa3gcu wrote:
>On Thursday 25 March 2004 15:46, Karthik Vishwanath wrote:
> > I installed the 2.4.18 source by 'apt-get install kernel-source-2.4.18',
> > extracted the source and made a symbolic /usr/src/linux ->
> > /usr/src/kernel-source-2.4.18/, and followed all the instructions below
> > as is.
> >
> > sh NVIDIA-Linux-x86-1.0-5336-pkg1.run quits with an error.
> >
> > # cat /var/log/nvidia-installer.log | grep ^ERROR
> > ERROR: Unable to determine the NVIDIA kernel module filename.
>
>
>No No No, /usr/src/kernel-source-2.4.18/ is NOT what you want i can assure
>you.
>
>When you untarred the source a directory called linux-2.4.18 should have been
>created you then need to create a symlink to "linux" for my example
>underneat, so lets start again.

Actually, Richard, this is just a Debian naming convention that you are 
unfamiliar with. Here, for example, is a relevant portion of my /usr/src 
directory:

autovcr@kuryakin:~$ ls -l /usr/src
[...]
drwxr-xr-x   15 root     root         4096 Mar  4 10:59 kernel-source-2.4.19
-rw-r--r--    1 root     root     25652223 Dec  5 15:59 
kernel-source-2.4.19.tar.bz2
lrwxrwxrwx    1 root     src            20 Aug 19  2002 linux -> 
kernel-source-2.4.19

In Debian when you un'tar (for example) kernel-source-2.4.19.tar.bz2 you 
get a directory tree named kernel-source-2.4.19, NOT one named linux-2.4.19.

I'm so used to this convention that I'd quite forgotten that other distros 
don't follow it.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 05:07 PM 3/25/2004 +0100, pa3gcu wrote:
>On Thursday 25 March 2004 16:42, Ray Olszewski wrote:
> > In fact, it should read
> >
> >          EXTRAVERSION =-k7
> >
> > (without the space before the hyphen).
>
>No sorry Ray its not a typo, its how it should be a as matter of fact,
>It possably works without a white space but AFAIK white spaces are ignored.
>
>If for example you look into any Topdir Makefile you will note that lines 1,
>2, and 3 have white spaces after the =  and the 4th line should comply as
>well or so i was once told.

Have you tried it, though? I recall actually having that problem once, 
though quite a few years ago (that is, back whenever it was I first used 
the EXTRAVERSION setting with my kernels). The prior three lines did get 
any spaces cleaned out, but as I recall, EXTRAVERSION was handled differently.

I specifically saw the problem as an inability to load modules, because the 
embedded space in the modules directory didn't work with the Debian init 
script that loads modules.

It's been a long time since I saw this problem, though, and it is certainly 
possible that my memory is wrong, or that Makefile processing has changed 
along the way ... and I'm unwilling to take the time to compile a kernel 
just to see what happens. I did look, though, and confirmed that all my 
kernel Makefile entries for EXTRAVERSION follow the form I suggest.

In any case, I don't actually know if this has anything to do with 
Karthik's problem, whichever of us is correct.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Karthik Vishwanath]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2125 bytes --]

I tried adding/removing spaces from the Makefile and I still cannot get
'sh NVIDIA-Linux-x86-1.0-5336-pkg1.run' to function alright. I did 
download NVIDIA-Linux-x86-1.0-5336-pkg1.run from nvidia's website and have 
not installed the Debian package nvidia-kernel-source. 

'uname -r' gives 2.4.18-k7. The Makefile in /usr/src/linux at its top 
reads: 

VERSION = 2
PATCHLEVEL = 4
SUBLEVEL = 18
EXTRAVERSION =-k7

I have attached the nvidia-installer.log as an attachment (as its about 
~2K). I could'nt spot anything significant in that log -- perhaps my eyes 
are unfamiliar wrt to what to seek... 

I did not follow Richards suggestion below since the untarring of the 
zipped source did create /usr/src/kernel-source-2.4.18/. 

-K

On Thu, 25 Mar 2004, at 8:28am, Ray Olszewski wrote:

> At 05:15 PM 3/25/2004 +0100, pa3gcu wrote:

> >
> >No No No, /usr/src/kernel-source-2.4.18/ is NOT what you want i can assure
> >you.
> >
> >When you untarred the source a directory called linux-2.4.18 should have been
> >created you then need to create a symlink to "linux" for my example
> >underneat, so lets start again.
> 
> Actually, Richard, this is just a Debian naming convention that you are 
> unfamiliar with. Here, for example, is a relevant portion of my /usr/src 
> directory:
> 
> autovcr@kuryakin:~$ ls -l /usr/src
> [...]
> drwxr-xr-x   15 root     root         4096 Mar  4 10:59 kernel-source-2.4.19
> -rw-r--r--    1 root     root     25652223 Dec  5 15:59 
> kernel-source-2.4.19.tar.bz2
> lrwxrwxrwx    1 root     src            20 Aug 19  2002 linux -> 
> kernel-source-2.4.19
> 
> In Debian when you un'tar (for example) kernel-source-2.4.19.tar.bz2 you 
> get a directory tree named kernel-source-2.4.19, NOT one named linux-2.4.19.
> 
> I'm so used to this convention that I'd quite forgotten that other distros 
> don't follow it.
> 
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
> 





[-- Attachment #2: Type: TEXT/PLAIN, Size: 1792 bytes --]

nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Thu Mar 25 11:53:12 2004

option status:
  license pre-accepted    : false
  update                  : false
  force update            : false
  expert                  : false
  uninstall               : false
  driver info             : false
  no precompiled interface: false
  no ncurses color        : false
  query latest driver ver : false
  OpenGL header files     : false
  no questions            : false
  silent                  : false
  XFree86 install prefix  : /usr/X11R6
  OpenGL install prefix   : /usr
  Installer install prefix: /usr
  kernel source path      : (not specified)
  kernel install path     : (not specified)
  proc mount point        : /proc
  ui                      : (not specified)
  tmpdir                  : /tmp
  ftp site                : ftp://download.nvidia.com

Using: nvidia-installer ncurses user interface
-> License accepted.
-> No precompiled kernel interface was found to match your kernel; would you li
   ke the installer to attempt to download a kernel interface for your kernel f
   rom the NVIDIA ftp site (ftp://download.nvidia.com)? (Answer: Yes)
-> No matching precompiled kernel interface was found on the NVIDIA ftp site;
   this means that the installer will need to compile a kernel interface for
   your kernel.
-> Kernel source path: '/usr/src/linux'
-> Performing cc_version_check with CC="cc".
ERROR: Unable to determine the NVIDIA kernel module filename.
ERROR: Installation has failed.  Please see the file
       '/var/log/nvidia-installer.log' for details.  You may find suggestions
       on fixing installation problems in the README available on the Linux
       driver download page at www.nvidia.com.

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 11:46 AM 3/25/2004 -0500, Karthik Vishwanath wrote:
>I tried adding/removing spaces from the Makefile and I still cannot get
>'sh NVIDIA-Linux-x86-1.0-5336-pkg1.run' to function alright. I did
>download NVIDIA-Linux-x86-1.0-5336-pkg1.run from nvidia's website and have
>not installed the Debian package nvidia-kernel-source.
>
>'uname -r' gives 2.4.18-k7. The Makefile in /usr/src/linux at its top
>reads:
>
>VERSION = 2
>PATCHLEVEL = 4
>SUBLEVEL = 18
>EXTRAVERSION =-k7
>
>I have attached the nvidia-installer.log as an attachment (as its about
>~2K). I could'nt spot anything significant in that log -- perhaps my eyes
>are unfamiliar wrt to what to seek...
>
>I did not follow Richards suggestion below since the untarring of the
>zipped source did create /usr/src/kernel-source-2.4.18/.

Hmmm ... the log itself is not very informative, and I find that the 
specific error message you're getting does not appear anywhere in the older 
nvidia package I have here ... at least not in any form that "grep" or 
"strings" can find.

Tracking this down involves looking at the source for the nvidia-installer. 
It turns out that this is a 2.6 change ... apparently 2.4.x modules are 
named nvidia.o, while 2.6.x modules are named nvidia.ko, and the installer 
is trying to figure out which name to use. For some reason, the function 
build_kernel_module() is not getting a usable value for this choice.

This is the code fragment that's burning you:

     cmd = nvstrcat("cd ", p->kernel_module_build_directory,
                    "; make print-module-filename", NULL);

     ret = run_command(op, cmd, &p->kernel_module_filename, FALSE, 0, FALSE);

     free(cmd);

     if (ret != 0) {
         ui_error(op, "Unable to determine the NVIDIA kernel module 
filename.");
         /* XXX need more descriptive error message */
         return FALSE;

(Note the comment near the end. I second it.)

  Why this fails is not readily apparent. The first thing to check, I 
suppose, is that you have "make" installed on your system. If not, install 
it ("apt-get install make").

If that's not it, try pecifying the kernel name as a command-line option. 
It's something like the following:

         sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=[KERNELNAME]

replacing [KERNELNAME] with the actual name.

If neither of these tactica work, consider dropping back to an eariler 
version of the NVIDIA package, one known to work with 2.4.x kernels (like 
the 4363 I have working here with a bespoke 2.4.19 .



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 17:40, Ray Olszewski wrote:
> At 05:07 PM 3/25/2004 +0100, pa3gcu wrote:
> >On Thursday 25 March 2004 16:42, Ray Olszewski wrote:
> > > In fact, it should read
> > >
> > >          EXTRAVERSION =-k7
> > >
> > > (without the space before the hyphen).
> >
> >No sorry Ray its not a typo, its how it should be a as matter of fact,
> >It possably works without a white space but AFAIK white spaces are
> > ignored.
> >
> >If for example you look into any Topdir Makefile you will note that lines
> > 1, 2, and 3 have white spaces after the =  and the 4th line should comply
> > as well or so i was once told.
>
> Have you tried it, though? I recall actually having that problem once,
> though quite a few years ago (that is, back whenever it was I first used
> the EXTRAVERSION setting with my kernels). The prior three lines did get
> any spaces cleaned out, but as I recall, EXTRAVERSION was handled
> differently.

I always use that method, yes it works and whats more i always use it that 
way, i use it that way because i was told to do so many moons ago when the 
EXTRAVERTION was first introduced into the Makefile, i was told that by its 
authour.

> I specifically saw the problem as an inability to load modules, because the
> embedded space in the modules directory didn't work with the Debian init
> script that loads modules.

Now that i cant understand, anyway strange things can and i suppose will 
always happen.

>
> It's been a long time since I saw this problem, though, and it is certainly
> possible that my memory is wrong, or that Makefile processing has changed
> along the way ... and I'm unwilling to take the time to compile a kernel
> just to see what happens. I did look, though, and confirmed that all my
> kernel Makefile entries for EXTRAVERSION follow the form I suggest.

Like i said they both work.

>
> In any case, I don't actually know if this has anything to do with
> Karthik's problem, whichever of us is correct.

No i dont think so as you can read in my reply to that mail later.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 17:46, Karthik Vishwanath wrote:
> I tried adding/removing spaces from the Makefile and I still cannot get
> 'sh NVIDIA-Linux-x86-1.0-5336-pkg1.run' to function alright. I did
> download NVIDIA-Linux-x86-1.0-5336-pkg1.run from nvidia's website and have
> not installed the Debian package nvidia-kernel-source.
>
> 'uname -r' gives 2.4.18-k7. The Makefile in /usr/src/linux at its top
> reads:
>
> VERSION = 2
> PATCHLEVEL = 4
> SUBLEVEL = 18
> EXTRAVERSION =-k7

I said;
EXTRAVERSION = -k7
i meant it.

A question to you, did you do;

make oldconfig
make dep
like i suggested, ????

The above does not mean you need to do the rest of a kernel compile ie, make 
bzImage modules modules_install etc etc, you need to configure the source 
thats all.
Files get created by make oldconfig and make dep which the nvidia installer 
gets information from.

> I have attached the nvidia-installer.log as an attachment (as its about
> ~2K). I could'nt spot anything significant in that log -- perhaps my eyes
> are unfamiliar wrt to what to seek...
>
> I did not follow Richards suggestion below since the untarring of the
> zipped source did create /usr/src/kernel-source-2.4.18/.

If you do not follow what i wrote then you will have problems period.
You can however ensure that /usr/src/kernel-source-2.4.18 has a symlink called 
linux pointing to it, or use the installers options to define where the 
source is, whichever way you choose you MUST reconfigure the kernel source 
and edit the makefile otheriwse it WILL NOT WORK.

About your directory /usr/src/kernel-source-2.4.18 if thats what you got when 
unpacking the source then it looks like you dont have the "offical" kernel 
source available from kernel.org as that i can assure you the offical source 
of 2.4.18 creates a directory called linux-2.4.18 and i cannot stress it 
enough but to say period.

Ray suggested to fall back on an older driver, i do not suggest that at all as 
i have 5336 running here on a slackware 9 system and a suse 9 system.
Like i mentioned before there are some issues with the driver itself in the 
way it works, BUT there are issues with all nvidia's drivers, just because i 
said there are issues with tis driver "here" does NOT mean you will have 
problems.

As i said before and i repeat, if you follow my instrutions then it will work 
i can assure you.

You MUST assure that the installer can find the kernel source AND that the 
kernel source is configured with the SAME options your running kernel has, 
thats it really.

If only you was next door i would come and show you how to do it there is no 
secret.
After all if you read;
 ftp://download.nvidia.com/XFree86/Linux-x86/1.0-5336/README
You will see that my examples are written there, they are not there for the 
duration, they are there to help you.

It even states that you need to have the source installed, make sure the 
installer knows where they are AND that the sources have been configured 
peropery by;
coping the config file of your running kernel to /usr/src/linux or the place 
where you tell the installer they are and that you have configured the 
sources with make oldconfig and make dep, if you dont do that your buggered 
period.


> -K
>
> On Thu, 25 Mar 2004, at 8:28am, Ray Olszewski wrote:
> > At 05:15 PM 3/25/2004 +0100, pa3gcu wrote:
> > >No No No, /usr/src/kernel-source-2.4.18/ is NOT what you want i can
> > > assure you.
> > >
> > >When you untarred the source a directory called linux-2.4.18 should have
> > > been created you then need to create a symlink to "linux" for my
> > > example underneat, so lets start again.
> >
> > Actually, Richard, this is just a Debian naming convention that you are
> > unfamiliar with. Here, for example, is a relevant portion of my /usr/src
> > directory:
> >
> > autovcr@kuryakin:~$ ls -l /usr/src
> > [...]
> > drwxr-xr-x   15 root     root         4096 Mar  4 10:59
> > kernel-source-2.4.19 -rw-r--r--    1 root     root     25652223 Dec  5
> > 15:59
> > kernel-source-2.4.19.tar.bz2
> > lrwxrwxrwx    1 root     src            20 Aug 19  2002 linux ->
> > kernel-source-2.4.19
> >
> > In Debian when you un'tar (for example) kernel-source-2.4.19.tar.bz2 you
> > get a directory tree named kernel-source-2.4.19, NOT one named
> > linux-2.4.19.
> >
> > I'm so used to this convention that I'd quite forgotten that other
> > distros don't follow it.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 17:28, Ray Olszewski wrote:
> >No No No, /usr/src/kernel-source-2.4.18/ is NOT what you want i can assure
> >you.
> >
> >When you untarred the source a directory called linux-2.4.18 should have
> > been created you then need to create a symlink to "linux" for my example
> > underneat, so lets start again.
>
> Actually, Richard, this is just a Debian naming convention that you are
> unfamiliar with. Here, for example, is a relevant portion of my /usr/src
> directory:

If you retrive the offical kernel source from www.kernel.org and use 'tar' to 
extracht the archive then a directory called linux-2.4.18 is created that is 
a linux FAQ of cource if one retrives some or other distro RPM then your on 
your own. The nvidia installer wants to find a /usr/src/linux or 
/lib/modules/'uname -r'/build
.
I am sure i dont need to give you Ray an example but for others heres what i 
have.

In /usr/src
linux-2.4.22-ac4/
linux -> linux-2.4.22-ac4/

So that means i have /usr/src/linux pointing to /usr/src/linux-2.4.22-ac4

Uname -r shows 2.4.22-ac4-2

if we look at /lib/modules we see;

build -> /usr/src/linux-2.4.22-ac4/

My Makefile has.

EXTRAVERSION = -ac4-2

Works like a charm.

cat /proc/driver/version
pa3gcu@localhost:/lib/modules/2.4.22-ac4-2$ cat /proc/driver/nvidia/version
NVRM version: NVIDIA Linux x86 NVIDIA Kernel Module  1.0-5336  Wed Jan 14 
18:29:26 PST 2004
GCC version:  gcc version 3.2.3

cat: /proc/driver/nvidia/cards/: Is a directory
pa3gcu@localhost:/lib/modules/2.4.22-ac4-2$ cat /proc/driver/nvidia/cards/0
Model:           GeForce4 Ti 4200
IRQ:             16
Video BIOS:      04.25.00.30.00
Card Type:       AGP

This is my slackware system, i can assure you my suse 9 system looks the same.

Yes one can do it in otherways i suppose, i say do it my way because i know it 
works period.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 17:28, Ray Olszewski wrote:
> >No No No, /usr/src/kernel-source-2.4.18/ is NOT what you want i can assure
> >you.

AH!!!!, now i dont know how i missed it, however i now see what Ray meant, you 
seem to be talking about an RPM install, ok anyway soory for the miscomm, 
however the point is the symlink it needs to be /usr/src/linux .

Ok so i also misread but i think most of you know that already.
the heart of the problem here is not doing what one is told to that i am sure 
of as thousands of nvidia owners use the way i have described, after all its 
described that way in the README.


-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

On Thursday 25 March 2004 21:06, pa3gcu wrote:
> After all if you read;
>  ftp://download.nvidia.com/XFree86/Linux-x86/1.0-5336/README
> You will see that my examples are written there, they are not there for the
> duration, they are there to help you.

I am glad i did not write this README, i have just discovered a somewhat BAD 
and rather misleading point, in that readme which i decided to study just to 
make sure i got my facts correct, i see the following under section;
sec-04 (if the file is in an editor its +/- line 772)

It says;
    cd /lib/modules/`uname -r`/build/
    cp configs/kernel-2.4.18-i686-bigmem.config .config
    make mrproper oldconfig dep

It an example for redhat but the problems is universal as it concerns 
'make mrproper'

make mrproper removes .config meaning if one follows that example ALL will 
fail misarably as kernel defaults contained in the different kernel Config.in 
files will be used and i can assure you thats not much.

I will send a report to nvidia about it.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Karthik Vishwanath]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1609 bytes --]

make is (was) installed.

sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=2.4.18-k7, did not 
work. 

So, I obtained  NVIDIA-Linux-x86-1.0-4363.run from nvidia.com, and ran as:
sh NVIDIA-Linux-x86-1.0-4363.run  --kernel-name=2.4.18-k7, and this worked 
(seemingly). 

I set my X driver to be nvidia (as indicated) but could not startx. 

I tried: # modprobe nvidia and came up with a list of "unresolved 
symbols". 

I taken the liberty of attaching both the nvidia-installer.log, as well as 
the output of modprobe nvidia to this message. 

Please tell me what to attempt next. 

Thanks,

-K

PS: Richard, I followed your instructions line for line: 

> cd /usr/src/linux
> make mrproper
> cp /boot/config-xx .config
> edit Makefile
> change line 4 from 
> EXTRAVERSION =
> To
> EXTRAVERSION = -k7
> save file;
> make oldconfig
> make dep

yet, # sh NVIDIA-Linux-x86-1.0-5336-pkg1.run would not work. 

On Thu, 25 Mar 2004, at 10:25am, Ray Olszewski wrote:

> 
>   Why this fails is not readily apparent. The first thing to check, I 
> suppose, is that you have "make" installed on your system. If not, install 
> it ("apt-get install make").
> 
> If that's not it, try pecifying the kernel name as a command-line option. 
> It's something like the following:
> 
>          sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=[KERNELNAME]
> 
> replacing [KERNELNAME] with the actual name.
> 
> If neither of these tactica work, consider dropping back to an eariler 
> version of the NVIDIA package, one known to work with 2.4.x kernels (like 
> the 4363 I have working here with a bespoke 2.4.19 .
> 
k


[-- Attachment #2: Type: TEXT/PLAIN, Size: 1415 bytes --]

/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol devfs_register_chrdev_R20a18c11
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol mem_map_R22d9a713
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol devfs_register_R523235af
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol irq_stat_R6cdfcf3e
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol init_mm_R33601568
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol devfs_unregister_R8e255fa4
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol remove_proc_entry_R5d34571b
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol __pollwait_Rf0ced4f0
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol create_proc_entry_Rea80db1e
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: unresolved symbol proc_root_driver_R4e04d290
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: 
Hint: You are trying to load a module without a GPL compatible license
      and it has unresolved symbols.  Contact the module supplier for
      assistance, only they can help you.

/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: insmod /lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o failed
/lib/modules/2.4.18-k7/kernel/drivers/video/nvidia.o: insmod nvidia failed

[-- Attachment #3: Type: TEXT/PLAIN, Size: 4230 bytes --]

nvidia-installer log file '/var/log/nvidia-installer.log'
creation time: Fri Mar 26 01:11:51 2004

option status:
  license pre-accepted    : false
  update                  : false
  force update            : false
  expert                  : false
  uninstall               : false
  driver info             : false
  no precompiled interface: true
  no ncurses color        : false
  query latest driver ver : false
  OpenGL header files     : false
  no questions            : false
  silent                  : false
  XFree86 install prefix  : /usr/X11R6
  OpenGL install prefix   : /usr
  Installer install prefix: /usr
  kernel include path     : (not specified)
  kernel install path     : (not specified)
  proc mount point        : /proc
  ui                      : (not specified)
  tmpdir                  : /tmp
  ftp site                : ftp://download.nvidia.com

Using: nvidia-installer ncurses user interface
-> License accepted.
-> Not probing for precompiled kernel interfaces.
-> Kernel include path: '/usr/src/linux/include'
-> Cleaning kernel module build directory.
   executing: 'cd ./usr/src/nv; make clean'...
   rm -f nv.o os-agp.o os-interface.o os-registry.o  nv-linux.o nv_compiler.h *
   .d NVdriver nvidia.o
-> Building kernel module:
   executing: 'cd ./usr/src/nv; make nvidia.o SYSINCLUDE=/usr/src/linux/include
   '...
   echo \#define NV_COMPILER \"`cc -v 2>&1 | tail -1`\" > nv_compiler.h
   cc -c -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wp
   arentheses -Wpointer-arith -Wcast-qual -Wno-multichar  -O -MD -D__KERNEL__ -
   DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_SOURCE -D_LOOSE_KERNEL_NAMES -D_
   _KERNEL__ -DMODULE  -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVE
   L=4363  -DNV_UNIX   -DNV_LINUX   -DNV_INT64_OK   -DNVCPU_X86      -DREMAP_PA
   GE_RANGE_4  -I. -I/usr/src/linux/include -Wno-cast-qual nv.c
   cc -c -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wp
   arentheses -Wpointer-arith -Wcast-qual -Wno-multichar  -O -MD -D__KERNEL__ -
   DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_SOURCE -D_LOOSE_KERNEL_NAMES -D_
   _KERNEL__ -DMODULE  -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVE
   L=4363  -DNV_UNIX   -DNV_LINUX   -DNV_INT64_OK   -DNVCPU_X86      -DREMAP_PA
   GE_RANGE_4  -I. -I/usr/src/linux/include -Wno-cast-qual os-agp.c
   cc -c -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wp
   arentheses -Wpointer-arith -Wcast-qual -Wno-multichar  -O -MD -D__KERNEL__ -
   DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_SOURCE -D_LOOSE_KERNEL_NAMES -D_
   _KERNEL__ -DMODULE  -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVE
   L=4363  -DNV_UNIX   -DNV_LINUX   -DNV_INT64_OK   -DNVCPU_X86      -DREMAP_PA
   GE_RANGE_4  -I. -I/usr/src/linux/include -Wno-cast-qual os-interface.c
   cc -c -Wall -Wimplicit -Wreturn-type -Wswitch -Wformat -Wchar-subscripts -Wp
   arentheses -Wpointer-arith -Wcast-qual -Wno-multichar  -O -MD -D__KERNEL__ -
   DMODULE -D_LOOSE_KERNEL_NAMES -DNTRM -D_GNU_SOURCE -D_LOOSE_KERNEL_NAMES -D_
   _KERNEL__ -DMODULE  -DNV_MAJOR_VERSION=1 -DNV_MINOR_VERSION=0 -DNV_PATCHLEVE
   L=4363  -DNV_UNIX   -DNV_LINUX   -DNV_INT64_OK   -DNVCPU_X86      -DREMAP_PA
   GE_RANGE_4  -I. -I/usr/src/linux/include -Wno-cast-qual os-registry.c
   ld -r -o nv-linux.o nv.o os-agp.o os-interface.o os-registry.o 
   ld -r -o nvidia.o nv-linux.o nv-kernel.o
-> done.
-> Kernel module compilation complete.
-> Installing classic TLS OpenGL libraries.
-> Installing 'NVIDIA Accelerated Graphics Driver for Linux-x86' (1.0-4363):
   executing: './usr/src/nv/makedevices.sh'...
   depmod: *** Unresolved symbols in /lib/modules/2.4.18-k7/kernel/drivers/vide
   o/nvidia.o
   executing: '/sbin/ldconfig'...
   executing: '/sbin/depmod -aq'...
-> done.
-> Driver file installation is complete.
-> Running post-install sanity check:
-> done.
-> Sanity check passed.
-> Installation of the NVIDIA Accelerated Graphics Driver for Linux-x86
   (version: 1.0-4363) is now complete.  Please update your XF86Config file as
   appropriate; see the file /usr/share/doc/NVIDIA_GLX-1.0/README for details.

Re: switching to debian (... and installing the NVIDIA GeForce4)

[joy]

Ray Olszewski wrote:

>
> Hard to say from this description if you are seeing the problems I 
> read about or not. With a sufficiently fast CPU ... a 3 GHz P4, say 
> ... I could run xine this way using xshm, and that video method is a 
> real CPU hog. A better test would be something like this:
>
> 1. run a single instance of xine in the current display, playing back 
> something suitable (I don't know what "Highway Star" is ... or, more 
> important to the test, how it

It's apparent that you are not a great fan of rock music....;-)

> is encoded (what resolution, what bitrate, what codec)). Make sure 
> xine is using xVideo ("xine -V xv filename_to_play"). Have xine 
> resizing the video ... double size if that works to keep everything 
> actually visible onscreen.

did that..... OK

>
> 2. also in the current display, run "top". With the entire xie 
> playback visible onscreen, note both total CPU use and its components. 
> The total should be quite low, under 5% usually, if all is working 
> smoothly. If the total is high, and both the "system" and "user" 
> components contribute significantly to it, you are seeing the problem 
> I've read about, even if the system is managing to keep up.

in the output of top, I found the xine part of it and it takes up very 
little, around 3-4% max whereas libarts, which I guess is the Kde libs 
takes up 50%(too much, IMHO) so I guess it is mem hogs like KDE that 
constitute the problem......

>
> 3. Mention what CPU -- type and speed -- is involved. The faster the 
> CPU, the lower the number should be in step 2.

Cpu- athlon 2400+
video- geforce4 64 mb ram
512 mb ddr main mem

>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[Ray Olszewski]

At 01:30 AM 3/26/2004 -0500, Karthik Vishwanath wrote:
>make is (was) installed.
>
>sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=2.4.18-k7, did not
>work.
>
>So, I obtained  NVIDIA-Linux-x86-1.0-4363.run from nvidia.com, and ran as:
>sh NVIDIA-Linux-x86-1.0-4363.run  --kernel-name=2.4.18-k7, and this worked
>(seemingly).
>
>I set my X driver to be nvidia (as indicated) but could not startx.
>
>I tried: # modprobe nvidia and came up with a list of "unresolved
>symbols".
>
>I taken the liberty of attaching both the nvidia-installer.log, as well as
>the output of modprobe nvidia to this message.
>
>Please tell me what to attempt next.

In general, this sort of result means one of two things:

1. You failed to load some needed modules before loading nvidia. In this 
instance, this appears NOT to be the actual problem, since

         (a) the nvidia installer runs "depmod" for you
         (b) 0y install of 4363 here indicates that nvidia has no dependencies

2. A kernel mismatch. Since you are trying to use source to add in modules 
to a pre-compiled, stock kernel, it is at least possible that this sort of 
mismatch is occurring. It MAY be as simple as the kernel cource having a 
.config file that does not match the compiled kernel ... I suggest this 
only because I see "devfs" mentioned in some of the unresolved symbols, and 
from my setup I know nvidia can run with a kernel that does not have devfs 
support compiled in.

Anyway, my best GUESS is that you're running into a problem based on your 
wanting to use a precompiled kernel, something I have no experience with 
(not in the last few years, anyway). I don't know if you are using Woody, 
Sarge, or Sid ... I just checked Sid and see that it does not at the moment 
have any kernel-image-2.4.18-k7 package but does have a 
kernel-source-2.4.18 ... so there may be a version mismatch problem that 
derives from image and souce being at different patchlevels *within* 2.4.18 
(Debian occasionally does this, mainly as backpatches for security issues).

So, I can only suggest two options.

First, compile a kernel locally and then try to run the nvidia installer 
and to install the nvidia module against it.

Two, try using the nvidia-kernel-source Debian package (with make-kpkg) to 
see if doing it "the Debian way" solves some hidden problem.

Other than that, you're sufficiently outside my experience that I cannot 
offer suggestions. Sorry.

BTW, my running version of nvidia is the same nvidia version number, but 
with a bespoke 2.4.19 kernel.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

> make is (was) installed.
>
> sh NVIDIA-Linux-x86-1.0-5336-pkg1.run --kernel-name=2.4.18-k7, did not
> work.

That opption is NOT what you want to use, its for a "non-running kernel".

>
> So, I obtained  NVIDIA-Linux-x86-1.0-4363.run from nvidia.com, and ran
> as: sh NVIDIA-Linux-x86-1.0-4363.run  --kernel-name=2.4.18-k7, and this
> worked (seemingly).

There is no need to try lower version numbers of the driver as the problem is 
on your computer itself and not the obtained software.

>
> I set my X driver to be nvidia (as indicated) but could not startx.

That figures as the log you sent shows that the module was not loaded by the 
installer.

>
> I tried: # modprobe nvidia and came up with a list of "unresolved
> symbols".

Indeed you did and as you see it says "unresolved symbols" concerning devfs, 
why i ask should it do that because devfs should never be installed as a 
module as a matter of fact i dont belive it can, now having said that this 
gives me a hint that you have possably used a kernel configuration from a 
kernel "other" than your running kernel, meaning you copied the wrong 
configuration file to /usr/src/linux before doing 'make oldconfig'.

>
> I taken the liberty of attaching both the nvidia-installer.log, as well
> as the output of modprobe nvidia to this message.

As i explained, the modprobe command shows you have a version mismatch,
you are doing something wrong.
The log shows that you have the kernel source in /usr/src/linux and includes 
in /usr/include, the rest does not show much else.

Now what can you do to find your problem, if i can say it without being rude, 
you need to Read The Fine Manual, (again i dont mean to be rude) read it and 
the output of;
sh NVIDIA-Linux-x86-1.0-5328-pkg1.run --advanced-options
WITH CARE, because your answer(s) are there i can assure you.

If it were me i would try;

Firstly to ensure we start at the beginning;

sh NVIDIA-Linux-x86-1.0-5328-pkg1.run --uninstall

sh NVIDIA-Linux-x86-1.0-5328-pkg1.run \
  --kernel-include-path=/lib/modules/2.4.18-k7/build/include
  ( one one line of course)..

Prereq's are that you have the full kernel source in place and that you have 
the configuration file named .config for your running kernel in /usr/src/
linux or where the   --kernel-include-path= points to and that you have a 
Makefile with line 4 as;
EXTRAVERSION = -k7
and that you did 'make oldconfig' 'make dep' as well.

If all that fails then try;

sh NVIDIA-Linux-x86-1.0-5328-pkg1.run \
  --add-this-kernel

When finished you should end up with a file called;

NVIDIA-Linux-x86-1.0-5328-pkg1-custom.run

Try that...

>
> Please tell me what to attempt next.

Try reading.

>
> Thanks,
>
> -K
>
> PS: Richard, I followed your instructions line for line:
> > cd /usr/src/linux
> > make mrproper
> > cp /boot/config-xx .config
> > edit Makefile
> > change line 4 from
> > EXTRAVERSION =
> > To
> > EXTRAVERSION = -k7
> > save file;
> > make oldconfig
> > make dep
>
> yet, # sh NVIDIA-Linux-x86-1.0-5336-pkg1.run would not work.

Then i am sorry to say you have NOT followed them to the "Tee".

>

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: switching to debian (... and installing the NVIDIA GeForce4)

[pa3gcu]

[-- Attachment #1: Type: text/plain, Size: 1989 bytes --]

On Saturday 27 March 2004 08:19, pa3gcu wrote:
> > yet, # sh NVIDIA-Linux-x86-1.0-5336-pkg1.run would not work.
>
> Then i am sorry to say you have NOT followed them to the "Tee".

I need to rephrase, i have just discovered another descrepancy, or at least it 
looks like it to me, let me explain.

The nvidia install file has precompiled kernel modules for a lot of 
distribution installed kernels from Redhat Mandrake and Suse, i have attached 
a list.
If no running kernel is found of that nature then the installer ftp's to 
nvidia's site (if thats possable) and automaticly checks to see if a kernel 
module is available, if no kernel modules for the running kernel is found on 
nvidia's site then one needs the source of the running kernel installed and 
it needs to be configured and dependancy files created, one of which i belive 
is modversions.h .

Somewhere back in the past the kernel source changed, the file modversions.h 
(AFAIK) used to get created by make dep, however i now see it does not, it 
gets created when one starts to compile the kernel itself with 'make bzImage' 
or which ever option is used.

Now to solve that problem you can of course simply issue;
make bzImage
to create /usr/src/linux/include/linux/modversions.h
OR you can cheat because we do NOT want to install the kernel we are making 
because it is already in use (if you follow me).
So here is how you can cheat, cheat i suppose is the wrong word, we simply 
take a shortcut and save time.

Do:
touch /usr/src/linux/include/linux/modversions.h
echo "#include <linux/modsetver.h> > /usr/src/linux/include/linux/ 
modversions.h"
(above all on one line).

So to recap;

mke oldconfig
make dep
touch as per above example
echo idem dito.

That could very well be the problem.

-- 
If the Linux community is a bunch of theives because they
try to imitate windows programs, then the Windows community
is built on organized crime.

Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/


[-- Attachment #2: me --]
[-- Type: text/plain, Size: 2917 bytes --]

 rh72up_2.4.7-10_i386
 rh72up_2.4.7-10_i686
 rh72up_2.4.7-10_athlon
 rh72smp_2.4.7-10_i686
 rh72smp_2.4.7-10_athlon
 rh72enterprise_2.4.7-10_i686
 rh73up_2.4.18-3_i386
 rh73up_2.4.18-3_i686
 rh73up_2.4.18-3_athlon
 rh73smp_2.4.18-3_i586
 rh73smp_2.4.18-3_i686
 rh73smp_2.4.18-3_athlon
 rh73bigmem_2.4.18-3_i686
 rh73up_2.4.20-19.7_i386
 rh73up_2.4.20-19.7_i586
 rh73up_2.4.20-19.7_i686
 rh73up_2.4.20-19.7_athlon
 rh73smp_2.4.20-19.7_i586
 rh73smp_2.4.20-19.7_i686
 rh73smp_2.4.20-19.7_athlon
 rh73bigmem_2.4.20-19.7_i686
 rh73boot_2.4.20-19.7_i386
 rh80up_2.4.18-14_i586
 rh80up_2.4.18-14_i686
 rh80up_2.4.18-14_athlon
 rh80smp_2.4.18-14_i686
 rh80smp_2.4.18-14_athlon
 rh80bigmem_2.4.18-14_i686
 rh80up_2.4.20-19.8_i386
 rh80up_2.4.20-19.8_i586
 rh80up_2.4.20-19.8_i686
 rh80up_2.4.20-19.8_athlon
 rh80smp_2.4.20-19.8_i586
 rh80smp_2.4.20-19.8_i686
 rh80smp_2.4.20-19.8_athlon
 rh80bigmem_2.4.20-19.8_i686
 rh80boot_2.4.20-19.8_i386
 rh9up_2.4.20-6_i586
 rh9up_2.4.20-6_i686
 rh9up_2.4.20-6_athlon
 rh9smp_2.4.20-6_i686
 rh9smp_2.4.20-6_athlon
 rh9bigmem_2.4.20-6_i686
 rh9up_2.4.20-8_i586
 rh9up_2.4.20-8_i686
 rh9up_2.4.20-8_athlon
 rh9smp_2.4.20-8_i686
 rh9smp_2.4.20-8_athlon
 rh9bigmem_2.4.20-8_i686
 rh9up_2.4.20-24_i386
 rh9up_2.4.20-24_i586
 rh9up_2.4.20-24_i686
 rh9up_2.4.20-24_athlon
 rh9smp_2.4.20-24_i586
 rh9bigmem_2.4.20-24_i686
 rh9smp_2.4.20-24_athlon
 rh9boot_2.4.20-24_i386
 rhel30_2.4.21-4.EL_i686
 rhel30_2.4.21-4.EL_athlon
 rhel30smp_2.4.21-4.EL_i686
 rhel30smp_2.4.21-4.EL_athlon
 rhel30hugemem_2.4.21-4.EL_i686
 rhel30boot_2.4.21-4.EL_i386
 fedora1up_2.4.22-1.2115.nptl_i586
 fedora1up_2.4.22-1.2115.nptl_i686
 fedora1up_2.4.22-1.2115.nptl_athlon
 fedora1smp_2.4.22-1.2115.nptl_i686
 fedora1smp_2.4.22-1.2115.nptl_athlon
 fedora1boot_2.4.22-1.2115.nptl_i386
 mdk81up_2.4.8-26_i586
 mdk81smp_2.4.8-26_i586
 mdk81enterprise_2.4.8-26_i586
 mdk82up_2.4.18-6_i586
 mdk82smp_2.4.18-6_i586
 mdk82enterprise_2.4.18-6_i586
 mdk82secure_2.4.18-6_i586
 mdk90up_2.4.19-16_i586
 mdk90smp_2.4.19-16_i586
 mdk90enterprise_2.4.19-16_i586
 mdk91up_2.4.21-0.13_i586
 mdk91smp_2.4.21-0.13_i586
 mdk91enterprise_2.4.21-0.13_i586
 mdk92_2.4.22.10mdk-1-1mdk
 mdk924G_2.4.22.10mdk-1-1mdk
 mdk92enterprise_2.4.22.10mdk-1-1mdk
 mdk92secure_2.4.22.10mdk-1-1mdk
 mdk92smp_2.4.22.10mdk-1-1mdk
 suse-8.2-k_deflt
 suse-8.2-k_athlon
 suse-8.2-k_psmp
 suse-8.2-k_smp
 suse-8.2-2.4.20-86-k_deflt
 suse-8.2-2.4.20-86-k_athlon
 suse-8.2-2.4.20-86-k_psmp
 suse-8.2-2.4.20-86-k_smp
 suse-8.2-2.4.20-96-k_deflt
 suse-8.2-2.4.20-96-k_athlon
 suse-8.2-2.4.20-96-k_psmp
 suse-8.2-2.4.20-96-k_smp
 suse-8.2-2.4.20-98-k_deflt
 suse-8.2-2.4.20-98-k_athlon
 suse-8.2-2.4.20-98-k_psmp
 suse-8.2-2.4.20-98-k_smp
 suse-9.0-2.4.21-99-k_deflt
 suse-9.0-2.4.21-99-k_athlon
 suse-9.0-2.4.21-99-k_smp
 suse-9.0-2.4.21-99-k_smp4G
 suse-9.0-2.4.21-144-k_deflt
 suse-9.0-2.4.21-144-k_athlon
 suse-9.0-2.4.21-144-k_smp
 suse-9.0-2.4.21-144-k_smp4G