[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: nvidia driver compiling problem



Hello

Steve Hargreaves (<steve@hargreavess.freeserve.co.uk>) wrote:

> On Saturday 07 February 2004 5:35 pm, Andreas Janssen wrote:
> 
>> > I have installed the 2.4.24 kernel for i386 from www.backports.org
>> > (I failed miserably trying to compile my own kernel), and since the
>> > nvidia kernel module needs the kernel sources to compile, I
>> > downloaded and installed the accompanying source package. So far so
>> > good.
>>
>> It doesn't need the source. Install the matching kernel-headers
>> package instead:
>>
>> apt-get install kernel-headers-2.4.24-1-386
>>
>>  and call the installer with
>>
>> --kernel-include-path=/usr/src/kernel-headers-2.4.24-1-386/include
> 
> OK - you live and learn - I didn't even know that the header package
> was available (I was looking for kernel-source). Anyway - that's done
> the trick, as far as compiling goes - and the module is now accepted,
> but if I then use the nvidia driver, all I get is a blank screen, and
> I can't even Alt-Fx to a spare console to recover - I have to do a
> hard reset to get back - but read on...

Check the XFree log file /var/log/XFree86.0.log. Also post the screen
and device sections of your XFree config file.

>>> This is getting to be a pain - I've done nothing but download stuff
>>> for 2 days over a 56k dial up connection - it'd be nice if I could
>>> get the right stuff first time :o(
>>
>> I think there are drivers available from Intel for your winmodem that
>> can be compiles using the kernel-headers package. Go to
>> <http://www.windodems.org> to find more info.
> 
> There are - I've got the sources from the Intel site (the only
> binaries are for RedHat - not Debian - but I get a bucketload of
> errors (directory tree problems, I assum) when I try and compile it...
> but as in the "read on" before - see my other posting entitled
> "recomended reading"

If you told us the error messages, maybe we would be able to help you
with this problem. If the driver doesn't have a configure script, you
probably have to edit the Makefile to tell it where the kernel headers
are. Perhaps you can also use some parameter to do that. Check the
README or INSTALL files that came with the driver, if you didn't do
that already.

best regards
        Andreas Janssen

-- 
Andreas Janssen
andreas.janssen@bigfoot.com
PGP-Key-ID: 0xDC801674
Registered Linux User #267976



Reply to: