Screen not turned on in kernel 2.6.35

Screen not turned on in kernel 2.6.35

[Paul Neumann]

Hi,

when I use kernel 2.6.35 my screen (connected via DVI) is not turned on. Everything else works fine so I can ssh into the machine and safely shut it down. This did not happen with 2.6.34. However I know that the issue is caused by that commit

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b1083333de5357577c5ec55df6c7efa17bee41c7

If I revert that patch everything works as expected.

My graphics card is

00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)

The interesting dmesg part is

i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
[drm] failed to find VBIOS tables
[drm] initialized overlay support
No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
Console: switching to colour frame buffer device 128x48

and xrandr shows

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA1 disconnected (normal left inverted right x axis y axis)
DVI1 disconnected (normal left inverted right x axis y axis)

Re: Screen not turned on in kernel 2.6.35

[Jesse Barnes]

On Sat, 7 Aug 2010 20:09:32 +0200
Paul Neumann <paul104x@yahoo.de> wrote:

> Hi,
> 
> when I use kernel 2.6.35 my screen (connected via DVI) is not turned on. Everything else works fine so I can ssh into the machine and safely shut it down. This did not happen with 2.6.34. However I know that the issue is caused by that commit
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=b1083333de5357577c5ec55df6c7efa17bee41c7
> 
> If I revert that patch everything works as expected.
> 
> My graphics card is
> 
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
> 
> The interesting dmesg part is
> 
> i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
> [drm] failed to find VBIOS tables
> [drm] initialized overlay support
> No connectors reported connected with modes
> [drm] Cannot find any crtc or sizes - going 1024x768
> Console: switching to colour frame buffer device 128x48
> 
> and xrandr shows
> 
> Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
> VGA1 disconnected (normal left inverted right x axis y axis)
> DVI1 disconnected (normal left inverted right x axis y axis)

Can you file a bug for this at bugs.freedesktop.org so it doesn't get
lost?

Adam's commit looks ok in general, but maybe your VBIOS is lying to us
in this case?

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: Screen not turned on in kernel 2.6.35

[Adam Jackson]

[-- Attachment #1.1: Type: text/plain, Size: 1041 bytes --]

On Mon, 2010-08-09 at 09:39 -0700, Jesse Barnes wrote:
> On Sat, 7 Aug 2010 20:09:32 +0200 Paul Neumann <paul104x@yahoo.de> wrote:
> > i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
> > [drm] failed to find VBIOS tables
> > [drm] initialized overlay support
> > No connectors reported connected with modes
> > [drm] Cannot find any crtc or sizes - going 1024x768
> > Console: switching to colour frame buffer device 128x48
> > 
> > and xrandr shows
> > 
> > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
> > VGA1 disconnected (normal left inverted right x axis y axis)
> > DVI1 disconnected (normal left inverted right x axis y axis)
> 
> Can you file a bug for this at bugs.freedesktop.org so it doesn't get
> lost?
> 
> Adam's commit looks ok in general, but maybe your VBIOS is lying to us
> in this case?

It's not that it's lying, it's that we don't _have_ one.  The "BAR 6"
message is the PCI layer telling us there's no space for the VBIOS.

- ajax

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Re: Screen not turned on in kernel 2.6.35

[Jesse Barnes]

On Mon, 09 Aug 2010 14:08:59 -0400
Adam Jackson <ajax@redhat.com> wrote:

> On Mon, 2010-08-09 at 09:39 -0700, Jesse Barnes wrote:
> > On Sat, 7 Aug 2010 20:09:32 +0200 Paul Neumann <paul104x@yahoo.de> wrote:
> > > i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
> > > [drm] failed to find VBIOS tables
> > > [drm] initialized overlay support
> > > No connectors reported connected with modes
> > > [drm] Cannot find any crtc or sizes - going 1024x768
> > > Console: switching to colour frame buffer device 128x48
> > > 
> > > and xrandr shows
> > > 
> > > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
> > > VGA1 disconnected (normal left inverted right x axis y axis)
> > > DVI1 disconnected (normal left inverted right x axis y axis)
> > 
> > Can you file a bug for this at bugs.freedesktop.org so it doesn't get
> > lost?
> > 
> > Adam's commit looks ok in general, but maybe your VBIOS is lying to us
> > in this case?
> 
> It's not that it's lying, it's that we don't _have_ one.  The "BAR 6"
> message is the PCI layer telling us there's no space for the VBIOS.

Oops missed that, yeah it would cause problems unless we could get at
the shadow at 0xc0000.

-- 
Jesse Barnes, Intel Open Source Technology Center

Re: Screen not turned on in kernel 2.6.35

[Paul Neumann]

On Mon, Aug 09, 2010 at 11:19:43AM -0700, Jesse Barnes wrote:
> On Mon, 09 Aug 2010 14:08:59 -0400
> Adam Jackson <ajax@redhat.com> wrote:
> 
> > On Mon, 2010-08-09 at 09:39 -0700, Jesse Barnes wrote:
> > > On Sat, 7 Aug 2010 20:09:32 +0200 Paul Neumann <paul104x@yahoo.de> wrote:
> > > > i915 0000:00:02.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
> > > > [drm] failed to find VBIOS tables
> > > > [drm] initialized overlay support
> > > > No connectors reported connected with modes
> > > > [drm] Cannot find any crtc or sizes - going 1024x768
> > > > Console: switching to colour frame buffer device 128x48
> > > > 
> > > > and xrandr shows
> > > > 
> > > > Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
> > > > VGA1 disconnected (normal left inverted right x axis y axis)
> > > > DVI1 disconnected (normal left inverted right x axis y axis)
> > > 
> > > Can you file a bug for this at bugs.freedesktop.org so it doesn't get
> > > lost?
> > > 
> > > Adam's commit looks ok in general, but maybe your VBIOS is lying to us
> > > in this case?
> > 
> > It's not that it's lying, it's that we don't _have_ one.  The "BAR 6"
> > message is the PCI layer telling us there's no space for the VBIOS.
> 
> Oops missed that, yeah it would cause problems unless we could get at
> the shadow at 0xc0000.
> 
> -- 
> Jesse Barnes, Intel Open Source Technology Center

Alright I have filed a bug (https://bugs.freedesktop.org/show_bug.cgi?id=29499), please let me know if I missed something.