Re: Testing: NVidia closed driver fails.

[Jochen Reinwand <jbr.1-hi6Y0CQ0nG0@public.gmane.org>]

Just an idea:

I read somewhere that NVidia kernel drivers make problems with apm.
In the syslog appears the following when starting X:

kernel: apm: set display: Power management disabled

It's a few seconds after the modules are inserted, so perhaps SuSE does it 
somewhere in the startup scripts... Have not found it yet...


I have a KT133 (Asus A7V) and also a Geforce 2 MX.
With ACPI enabled X gets slow. I mean REALLY SLOW! It needs up to 20 seconds 
to start and then consumes as much CPU time as possible. It's an adventure to 
try to hit something with the mouse pointer.
Everything is funktioning perfectly without ACPI.
Perhaps an interrupt problem. ACPI shares an interrupt with a bttv card. The 
GeForce has it's own interrupt.

Jochen

Am Donnerstag, 19. September 2002 17:06 schrieb Ducrot Bruno:
> On Thu, Sep 19, 2002 at 03:38:16PM +0300, P. Christeas wrote:
> > > I wanted to make a special request for testing of the 2.4 patch (or
> > > should I say, MEGA-patch).
> > >
> > >
> > > - DOES IT BOOT?
> > > - DOES IT ASSIGN INTERRUPTS PROPERLY?
> >
> > I have tried the 2.4.20-pre7 + acpi-20020918 patch on a single Athlon XP
> > 1.7+, VIA VT8637 KT266 chipset. The system boots and displays some ACPI
> > info that looks fine.
> > However, the proprietary NVidia video driver (I have a Geforce 2 MX card
> > and the newest 1.0.3123 proprietary driver) fails to start the X system.
> > I strongly suspect (although I don't have enough debug info yet) that the
> > acpi patch is the one that makes NVidia fail. The 2.4.19 worked until the
> > acpi patch was applied to it.
>
> I suspect an interrupt trouble.  Could you 'lspci -xxx -vvv' the device
> with and without acpi?



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf