linux-kernel - Re: Black screen with gma500

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20121022153936.455ac8f8@pyramind.ukuu.org.uk>
Date:	Mon, 22 Oct 2012 15:39:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Guido Günther <agx@...xcpu.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Black screen with gma500_gfx on 3.6.2

> [  689.950596] gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
> [  689.950627] [drm] Initialized gma500 1.0.0 2011-06-06 for 0000:00:02.0 on minor 0

It's got the LVDS configured it seems and the brightness was already set
up. That should be harmless.

> Besides the VGA the driver detects a LVDS as well although there's none
> attached (the board does have a connector for it though):

Ok so it finds both ports which is what I would expect

> # grep -l ^connected /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-*/status
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-LVDS-1/status
> /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-VGA-1/status

This means it found there was a VGA port and from
psb_intel_sdvo_output_setup called psb_intel_sdvo_analog_init.

> 
> It also states that both ports are disabled:

Which would explain the black screen.

> 
> # cat   /sys/devices/pci0000:00/0000:00:02.0/drm/card0/card0-*/enabled
> disabled
> disabled
> 
> I didn't find a way to enable any of these ports via sysfs and X.org's
> modesetting driver fails either. Any pointers on howto debug this
> further are greatly appreciated.

My first guess would be that the detection of the VGA failed. That would
explain all your symptoms and since it relies on the firmware...

First thing to do is turn drm debug on in full and you should then get a
dump of the SDVO capabilities, particulary output_flags as well as an
entry giving the clock range etc if it initialized it ok.

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