Bug 6199 - black screen with nvidia 420go
Summary: black screen with nvidia 420go
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: acpi_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-09 05:42 UTC by Rolf Dubitzky
Modified: 2006-07-28 20:19 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.14
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Rolf Dubitzky 2006-03-09 05:42:49 UTC
Most recent kernel where this bug did not occur: ?2.6.2?
Distribution: fedora core 4
Hardware Environment: samsung x10 laptop
Software Environment: Xorg + CSS nvidia drivers
Problem Description:

First, this problem is only visible when using the closed source
nvidia driver.  Please, instead of flaming me, just stop reading, I have no
other choice since I need the VGA out of the laptop which does not work
with the OSS nv drivers.  

The problem is very simple.  This laptop commes with a broken DSDT so I don't
update kernels often, and since the last update to 2.6.14 (from 2.6.2) the 
screen turns blank when starting X with the proprietary nvidia drivers. 
NVIDIA says it is an ACPI-bug (whatever that means) and can be solved by
turning off acpi.  Now, without ACPI lots of features of the laptop are
unusable.

Many more detailed infos and logs can be found here:
http://www.nvnews.net/vbulletin/showthread.php?t=65308

Please tell me what other info I can provide or what I could try out
to get this running.

Sorry again for asking questions in connection with closed source drivers,
but maybe someone has an idea.

Steps to reproduce:

install any recent nvidia driver on 2.6.10 and later kernels and try to start X
Comment 1 Luming Yu 2006-03-11 08:50:51 UTC
>NVIDIA says it is an ACPI-bug
why this is acpi bug?
care to elaberate.
Comment 2 Adrian Bunk 2006-07-28 20:19:53 UTC
Please reopen this bug if:
- it is still present in kernel 2.6.17 and
- you can provide the requested information.

Note You need to log in before you can comment on or make changes to this bug.