Nouveau - Jul 2011 - [Bug 39498] New: nouveau hangs on unresponsive black screen at startup

https://bugs.freedesktop.org/show_bug.cgi?id=39498

           Summary: nouveau hangs on unresponsive black screen at startup
           Product: xorg
           Version: git
          Platform: Other
        OS/Version: Linux (All)
            Status: NEW
          Severity: blocker
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau at lists.freedesktop.org
        ReportedBy: guido at trentalancia.com
         QAContact: xorg-team at lists.x.org


The Nouveau driver hangs on unresponsive black screen at startup (though it is
backlit).

None of ctrl-alt-del, ctrl-alt-fX works. The computer can only be rebooted by
pressing the power button.

I am using the Nouveau driver from git, libdrm from git and the nouveau kernel
module from version 2.6.39.3 (cannot try 3.0 yet, thus no out-of-tree git from
freedesktop either).

The card is an NVidia GeForce GT 330M. It should have Optmimus but with the
hardware mux (BIOS configured to "discrete" instead of
"switchable").

The "nv" driver works fine. The binary NVidia driver also ends up with
an
unresponsive black screen.

I have checked most (perhaps all) things on the Nouveau Troubleshooting page
without success.

I have tried with and without the "vga=775" option.

I am going to quote the output of lspci below and attach a few log files
(output of dmesg, Xorg.log and lsmod).

The log files collected without the vga=775 kernel option are divide the dmesg
output before and after starting X. The other two log files are obtained
without passing any "vga=" option at boot and should be similar.

01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M]
(rev a2) (prog-if 00 [VGA controller])
        Subsystem: Acer Incorporated [ALI] Device 035a
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort-
<MAbort- >SERR- <PERR- INTx-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 7
        Region 0: Memory at b2000000 (32-bit, non-prefetchable) [size=16M]
        Region 1: Memory at a0000000 (64-bit, prefetchable) [size=256M]
        Region 3: Memory at b0000000 (64-bit, prefetchable) [size=32M]
        Region 5: I/O ports at 3000 [size=128]
        Expansion ROM at b3080000 [disabled] [size=512K]
        Capabilities: [60] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
                Address: 0000000000000000  Data: 0000
        Capabilities: [78] Express (v2) Endpoint, MSI 00
                DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s
unlimited, L1 <64us
                        ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
                        RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                        MaxPayload 128 bytes, MaxReadReq 512 bytes
                DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr-
TransPend-
                LnkCap: Port #0, Speed 5GT/s, Width x16, ASPM L0s L1, Latency
L0 <256ns, L1 <4us
                        ClockPM+ Surprise- LLActRep- BwNot-
                LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain-
CommClk+
                        ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+
DLActive- BWMgmt- ABWMgmt-
                DevCap2: Completion Timeout: Not Supported, TimeoutDis+
                DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-
                LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-,
Selectable De-emphasis: -6dB
                         Transmit Margin: Normal Operating Range,
EnterModifiedCompliance- ComplianceSOS-
                         Compliance De-emphasis: -6dB
                LnkSta2: Current De-emphasis Level: -6dB
        Capabilities: [b4] Vendor Specific Information: Len=14 <?>
        Capabilities: [100 v1] Virtual Channel
                Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1
                Arb:    Fixed- WRR32- WRR64- WRR128-
                Ctrl:   ArbSelect=Fixed
                Status: InProgress-
                VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
                        Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
                        Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=01
                        Status: NegoPending- InProgress-
        Capabilities: [128 v1] Power Budgeting <?>
        Capabilities: [600 v1] Vendor Specific Information: ID=0001 Rev=1
Len=024 <?>
        Kernel modules: nouveau, nvidiafb

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

Guido Trentalancia <guido at trentalancia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|medium                      |highest

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #1 from Guido Trentalancia <guido at trentalancia.com>
2011-07-23 15:38:47 PDT ---
Created an attachment (id=49450)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49450)
logs for vga=775 before starting X

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #2 from Guido Trentalancia <guido at trentalancia.com>
2011-07-23 15:39:57 PDT ---
Created an attachment (id=49451)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49451)
logs for vga=775 after starting X (stuck on black screen)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #3 from Guido Trentalancia <guido at trentalancia.com>
2011-07-23 15:40:54 PDT ---
Created an attachment (id=49452)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49452)
logs without "vga=" boot option (first attempt)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #4 from Guido Trentalancia <guido at trentalancia.com>
2011-07-23 15:41:38 PDT ---
Created an attachment (id=49453)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49453)
logs without "vga=" boot option (second attempt)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #5 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 05:36:09 PDT ---
I have only managed to get it working for the first time with the original
kernel driver from vanilla kernel 3.0.0 by using the "NoAccel" option
set to
"True" in xorg.conf at section "Device". However everything
is very slow.

I am now going to attach the output log collected from Xorg.log, dmesg and
lsmod (filename nouveau-discrete-3.0.0-NoAccel-no_glx_module.txt).

But I would like to use acceleration, so this is not a stable situation... The
bug remains open. Next I am going to try the git kernel driver from freedesktop
built out-of-place.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #6 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 05:37:08 PDT ---
Created an attachment (id=49468)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49468)
logs when the driver is working with the NoAccel option (very slow)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #7 from Emil Velikov <emil.l.velikov at gmail.com> 2011-07-24
10:12:20 PDT ---
Hi Guido

Can you try booting into runlevel 3 - append " 3" to your kernel
command line

If the above produces working system (i.e. the display is not black) please try
the following

1 Note that there is something a bit odd in your Xorg.log as libglx.so tries to
load twice. In may be good idea trying the minimal xorg.conf [1]

2. Try disabling AIGLX in your xorg.conf

Cheers
Emil

[1] http://nouveau.freedesktop.org/wiki/InstallNouveau

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #8 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 10:43:23 PDT ---
Just finished trying the kernel module from snapshot
master-4fc2e2fc0157433883f10e0d7327c73069c66d63 instead of module from vanilla
kernel 3.0.0 and it does not work either.

I can still try out the freedesktop git trying to build only that module
out-of-place or otherwise I could try the upstream kernel 3.0.0-git3.

Emil, thanks very much for your advice. I always start from runlevel 3 until
things are stable. I tried disabling AIGLX several times before, without any
benefit. I will now disable it permanently and also double-check that glx is
not invoked twice from xorg.conf. If glx is loaded twice because of a problem
that does not depend on the configuration, then I suppose there is little I can
do about it...

Any other idea ?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #9 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 12:08:25 PDT ---
Emil, I tried following your advice, using the original driver which comes with
kernel 3.0.0-git3 but the problem is still there (it gets stuck on an
unresponsive black screen which only displays a small underscore "_"
in the top
left corner and I do not get the gdm greeter).

I am going to attach the logs (as file
nouveau-discrete-with_Accel-kernel_3.0.0-git3-driver-no-aiglx-do_not_require_glx.txt),
but I am sure they are very similar to the previous ones except from AIGLX
being disabled and GLX loading only once (by default).

I will keep those two settings as you suggested from now on, but so far nothing
has changed unfortunately !

Next I will try the kernel driver from the snapshot (commit
4fc2e2fc0157433883f10e0d7327c73069c66d63) on the 3.0.0-git3, but at this point
I really doubt it would sort things out.

I am not sure but perhaps the only difference between the kernel module shipped
with the upstream kernel and the out-of-place kernel module from the snapshot
is that the following line is missing in the snapshot:

[drm] nouveau 0000:01:00.0: Pointer to BIT loadval table invalid

Other than that with kernel 3.0.0 there was no practical difference between the
two kernel drivers (upstream and freedesktop snapshot).

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #10 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 12:09:41 PDT ---
Created an attachment (id=49476)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49476)
logs with module from kernel 3.0.0-git3 (AIGLX disabled and GLX not required
but loaded by default)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #11 from Emil Velikov <emil.l.velikov at gmail.com> 2011-07-24
12:25:34 PDT ---
(In reply to comment #9)
> Emil, I tried following your advice, using the original driver which comes
with
> kernel 3.0.0-git3 but the problem is still there (it gets stuck on an
> unresponsive black screen which only displays a small underscore
"_" in the top
> left corner and I do not get the gdm greeter).
If you are starting at runlevel 3 there will be no kdm/gdm/xdm greeter

Thus I take that the display is _not_ black but there is still nothing relevant
on it
> ....
> [drm] nouveau 0000:01:00.0: Pointer to BIT loadval table invalid
> 
AFAIK the above message is not crucial

There are a few things you can try - all without loading X

1. Play with the module options "noaccel" and/or "nofbaccel"
(modinfo nouveau
for more info)

2. Select different resolution - append "video=..." [1] to your kernel
command
line

3. Add some printf() statements in the kernel module to narrow in which state
the issue occurs

Cheers
Emil

[1] http://nouveau.freedesktop.org/wiki/KernelModeSetting - Forcing Mode

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #12 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 13:41:25 PDT ---
Hi Emil, thanks once again very much for offering your support !

Yes, there will be no gdm greeter in runlevel 3, but I shall get some
gnome-terminals and the gnome-panel too. Doesn't matter...

By the way, the minimal xorg.conf did not help (and it actually enables AIGLX).

The freedesktop snapshot kernel driver on 3.0.0-git3 did not sort things out
either.

Perhaps, the only difference that I recently noticed is that with NoAccel (only
usable configuration) and AIGLX disabled in xorg.conf, I get:

[   541.369] (**) Option "AIGLX" "off"
...
[   541.562] (**) AIGLX disabled
[   541.562] (II) Loading extension GLX
...
[   542.281] (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
[   542.281] (II) GLX: Initialized DRISWRAST GL provider for screen 0

I think this is not very relevant. Perhaps it just means that it has loaded the
SW rasterizer (the one used by the "nv" driver). It does not speed up
anything
(acceleration is disabled). It could be that earlier on Mesa did not produce
that module after building it and therefore it was not getting loaded.

I will now try to follow your latest advice. I will take some time to play
around with all possible different configurations and options...

However in the earliest logs (at the end of dmesg's output) there is some
extra
debugging output from the kernel drm module. Does that tell you anything ?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #13 from Felix Miata <mrmazda at earthlink.net> 2011-07-24
15:08:39 PDT ---
Created an attachment (id=49480)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49480)
Xorg.0.log & dmesg

I think https://bugzilla.novell.com/show_bug.cgi?id=706305 and
https://bugzilla.novell.com/show_bug.cgi?id=707110 are this, so instead of
filing new as per comment 6 in the latter, attaching messages and Xorg.0.log
here.
http://download.opensuse.org/repositories/home:/jobermayr/openSUSE_Factory/i586/drm-nouveau-kmp-desktop-20110721.2009_k3.0.0_2-2.3.i586.rpm
used instead of normal Factory rpm.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #14 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 15:54:32 PDT ---
Emil, unfortunately I have tried the following options for the kernel module
and none of them works:

msi=1 tv_disable=1 agpmode=0 noaccel=1 nofbaccel=1

except from noaccel=1 which is equivalent to NoAccel in xorg.conf (pointless).

The "video" option in kernel boot, should only affect the framebuffer
console,
therefore I am not sure it would sort out the problem with acceleration, but I
might try it later on...

I could also disseminate printf() in the kernel module, but I do not know
anything about it and in any case, there is no crash as in oops or segfault. As
already pointed out, I believe the drm debug output should be very informative
to the developers, but nobody is getting back...

Felix, the bugs you are describing seem different from mine because:

- I have a different NVidia card (mine is GeForce GT 330M);
- I am not using openSUSE;
- I do not have a blinking cursor in the upper left corner (it's a steady
white
underscore);
- keyboard and mouse are both working fine for me.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #15 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 16:10:55 PDT ---
Felix, just a quick comment on your logs. I am no expert at all, but I noticed
something:

- xserver is trying to load the "nvidia" driver (binary driver from
NVidia) and
fortunately it's failing to load it because it's missing (otherwise it
might
conflict with nouveau); lsmod should not show that "nvidia" kernel
module is
loaded; Xorg.log should not show that it is trying to load nvidia_drv.so
- xserver is loading the "nv" driver (successfully) and that could
interfere
with nouveau. you should avoid loading that. use 'Driver
"nouveau"' in
xorg.conf or otherwise remove the file nv_drv.so from
/usr/lib/xorg/modules/drivers.

Summing up, only the following drivers/modules should be loaded when using
nouveau:

- kernel module (check with lsmod): nouveau, drm, drm_kms_helper, ttm
- Xorg module (check from Xorg.log):
/usr/lib/xorg/modules/drivers/nouveau_drv.so

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #16 from Felix Miata <mrmazda at earthlink.net> 2011-07-24
16:35:25 PDT ---
(In reply to comment #14)
> Felix, the bugs you are describing seem different from mine because:
> - I have a different NVidia card (mine is GeForce GT 330M);
It also happens with a much older GeForce2 MX400.
> - I do not have a blinking cursor in the upper left corner (it's a
steady white
> underscore);
Mine stopped blinking after switching to Jobermayr's drm-nouveau-kmp-desktop
and 3.0.0-2 (both installed at same time).
> - keyboard and mouse are both working fine for me.
PS/2 connected, or USB? Mine are both USB with the 8600GT, but PS/2 on the old
NV11.

(In reply to comment #15)
> Felix, just a quick comment on your logs. I am no expert at all, but I
noticed
> something:
> - xserver is trying to load the "nvidia" driver (binary driver
from NVidia) and
> fortunately it's failing to load it because it's missing (otherwise
it might
> conflict with nouveau); lsmod should not show that "nvidia"
kernel module is
> loaded; Xorg.log should not show that it is trying to load nvidia_drv.so
> - xserver is loading the "nv" driver (successfully) and that
could interfere
> with nouveau. you should avoid loading that. use 'Driver
"nouveau"' in
> xorg.conf or otherwise remove the file nv_drv.so from
> /usr/lib/xorg/modules/drivers.
I only have a vague notion of the inner workings of X as they appear in the
logs, but I think you see the result of prioritization of drivers to try. It
prefers nvidia, regardless whether installed (which is never the case on any of
my systems), next tries nouveau, next nv, and last vesa. I always see their
*.sos listed, but only that actually used shows up in the capitalized repeats
show which is actually used, such as in this case (II) NOUVEAU(0):

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #17 from Guido Trentalancia <guido at trentalancia.com>
2011-07-24 16:52:24 PDT ---
>> - I have a different NVidia card (mine is GeForce GT 330M);
> It also happens with a much older GeForce2 MX400.
Yours is 'NOUVEAU(0): Chipset: "NVIDIA NV84"', mine is
'NOUVEAU(0): Chipset:
"NVIDIA NVa5"'.

The identification from the kernel is similar but not exactly the same: yours
is "Detected an NV50 generation card (0x084200a2)", mine is
"Detected an NV50
generation card (0x0a5480a2)". The BIOS version is also very different.

It could be an issue with similar effects but due to a different bug.

I am not an expert, therefore I have nothing else to add. We should wait for
developers to get back, I suppose...
> Mine stopped blinking after switching to Jobermayr's
drm-nouveau-kmp-desktop
> and 3.0.0-2 (both installed at same time).
Well, at least you can revert back to previous versions ! Mine has never been
working !!
> PS/2 connected, or USB?
I use an internal Touchpad from Synaptics, but external USB mouse also works
fine.
> I only have a vague notion of the inner workings of X as they appear in the
> logs, but I think you see the result of prioritization of drivers to try.
It
> prefers nvidia, regardless whether installed (which is never the case on
any of
> my systems), next tries nouveau, next nv, and last vesa. I always see their
> *.sos listed, but only that actually used shows up in the capitalized
repeats
> show which is actually used, such as in this case (II) NOUVEAU(0):
The file that you attached
(https://bugs.freedesktop.org/attachment.cgi?id=49480) also shows "(II)
NV:"
and not just "(II) NOUVEAU(0):".

But, it's up to you, if you think it's pointless to try adjusting
that...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #18 from Felix Miata <mrmazda at earthlink.net> 2011-07-25
06:48:01 PDT ---
https://bugzilla.novell.com/show_bug.cgi?id=707110 enabled me to get mine
working.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

Guido Trentalancia <guido at trentalancia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #49480|Xorg.0.log & dmesg          |Xorg.0.log & dmesg. The
        description|                            |person that submitted these
                   |                            |logs has now sorted out his
                   |                            |problem.
  Attachment #49480|0                           |1
        is obsolete|                            |

--- Comment #19 from Guido Trentalancia <guido at trentalancia.com>
2011-07-25 10:52:06 PDT ---
(From update of attachment 49480)
The person that submitted these logs has now sorted out his problem.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #20 from Guido Trentalancia <guido at trentalancia.com>
2011-07-25 10:59:15 PDT ---
Emil, unfortunately (and as I was expecting) the "video" option in the
kernel
boot parameters did not sort out anything other than changing the resolution of
the initial framebuffer console. The last option that you proposed was to
disseminate printk() in the kernel module and try to trace the code path and
try to understand where it gets stuck. That's not easy to do without any
indication at all, because the it's several drivers (drm, drm_kms_helper,
nouveau, ttm). Also there is no crash as in kernel oops or userspace segfault
and I have already debug output from drm. I bet the problem lies there (drm or
drm_kms_helper), but I really do not know where to begin without the assistance
of one of the developers.

Felix, I am glad to hear that you managed to sort out your issues. I am quite
sure mine are not exactly related to yours and I am not using openSUSE,
therefore trying the same packages has a very low priority for me now. I would
really need to hear back from the developers...

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #21 from Guido Trentalancia <guido at trentalancia.com>
2011-07-25 11:05:19 PDT ---
Upgrading to kernel version 3.0.0-git4 did not change the situation... I am
quite desperate about this problem. Several hours spent trying different
options and different versions without achieving anything. A lot of money spent
on a graphic card which does not even work with the original driver from its
manufacturer ! Being a laptop, I cannot even smash it against the wall
unfortunately !

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

https://bugs.freedesktop.org/show_bug.cgi?id=39498

--- Comment #22 from Guido Trentalancia <guido at trentalancia.com>
2011-07-25 22:54:32 PDT ---
Let's get to some important conclusions...

https://bugs.freedesktop.org/show_bug.cgi?id=39498

Guido Trentalancia <guido at trentalancia.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|nouveau at lists.freedesktop.o |guido at trentalancia.com
                   |rg                          |

--- Comment #23 from Guido Trentalancia <guido at trentalancia.com>
2011-07-25 23:03:29 PDT ---
Created an attachment (id=49551)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=49551)
Logs for Nouveau driver (git) working with acceleration (after few changes
mainly from openSUSE/jobermayr))

Logs for Nouveau driver (git) working with acceleration (after few changes
mainly from openSUSE/jobermayr and mainly to Mesa build options).

Need to find root cause of the bloody NoAccel problem resulting in black screen
hang. It could be just Mesa build options but it needs to be carefully analysed
and documented where most appropriate.

The only odd thing in Xorg.log is:

[   177.426] (II) AIGLX: Loaded and initialized /usr/lib64/dri/swrast_dri.so
[   177.426] (II) GLX: Initialized DRISWRAST GL provider for screen 0

What does that really mean ? I hope not that it's using the software
rasterizer.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.