* [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1
@ 2010-09-08 15:10 Woody Suwalski
2010-09-08 15:19 ` Chris Wilson
0 siblings, 1 reply; 3+ messages in thread
From: Woody Suwalski @ 2010-09-08 15:10 UTC (permalink / raw)
To: Chris Wilson; +Cc: linux-kernel, intel-gfx
I have a system where display is connected as LVDS1, however LVDS
seems to be still detectable.
The problem was present in 2.6.31, then fixed in 2.6.32, still working
in 2.6.35, broken in 2.6.36, still broken in 2.6.36-rc3-git1.
from dmesg 2.6.35:
[ 0.749174] Linux agpgart interface v0.103
[ 0.749231] agpgart-intel 0000:00:00.0: Intel 945GME Chipset
[ 0.749555] agpgart-intel 0000:00:00.0: detected 7932K stolen memory
[ 0.755069] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
[ 0.755395] [drm] Initialized drm 1.1.0 20060810
[ 0.755460] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 0.755475] i915 0000:00:02.0: setting latency timer to 64
[ 0.775954] [drm] set up 7M of stolen space
[ 1.299163] fbcon: inteldrmfb (fb0) is primary device
[ 1.559095] [drm] LVDS-8: set mode 1440x900 c
[ 1.827032] Console: switching to colour frame buffer device 180x56
[ 1.861877] fb0: inteldrmfb frame buffer device
[ 1.861884] registered panic notifier
[ 1.861976] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
xrandr on 2.6.35
Screen 0: minimum 320 x 200, current 1440 x 900, maximum 4096 x 4096
VGA1 disconnected (normal left inverted right x axis y axis)
LVDS1 connected 1440x900+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1440x900 60.0*+ 59.9
1360x768 59.8
1152x864 100.0 85.1 85.0 75.0 75.0 70.0 60.0
1024x768 85.0 75.0 70.1 60.0
832x624 74.6
800x600 85.1 72.2 75.0 60.3 56.2
640x480 85.0 72.8 75.0 59.9
720x400 85.0
640x400 85.1
640x350 85.1
dmesg on 2.6.36-rc3-git1
[ 1.518997] ACPI: Video Device [IGD] (multi-head: yes rom: no post: no)
[ 1.519266] ERST: Table is not found!
[ 1.718700] Linux agpgart interface v0.103
[ 1.719778] agpgart-intel 0000:00:00.0: Intel 945GME Chipset
[ 1.720594] agpgart-intel 0000:00:00.0: detected 7932K stolen memory
[ 1.726546] agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xc0000000
[ 1.727743] [drm] Initialized drm 1.1.0 20060810
[ 1.728175] [drm] VGACON disable radeon kernel modesetting.
[ 1.729679] pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 1.729773] pci 0000:00:02.0: setting latency timer to 64
[ 1.816591] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
same xrandr on 2.6.36 - bogus LVDS prebenting LVD1 to run correctly:
Screen 0: minimum 320 x 200, current 800 x 600, maximum 2048 x 2048
VGA disconnected (normal left inverted right x axis y axis)
LVDS connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
840x1050 60.0 +
832x624 74.6
800x600 85.1 72.2 75.0 60.3* 56.2
640x480 85.0 72.8 75.0 59.9
720x400 85.0
640x400 85.1
640x350 85.1
LVDS-1 connected 800x600+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1440x900 60.0 + 59.9
1360x768 59.8
1152x864 60.0
1024x768 60.0
800x600 60.3*
640x480 59.9
If I boot "normally" - I get a black screen (maybe crashed?)
I can only boot if "nomodeset=y" is added to the command line... But
then it runs in this 800x600 mode...
Woody
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1
2010-09-08 15:10 [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1 Woody Suwalski
@ 2010-09-08 15:19 ` Chris Wilson
2010-09-08 15:52 ` Woody Suwalski
0 siblings, 1 reply; 3+ messages in thread
From: Chris Wilson @ 2010-09-08 15:19 UTC (permalink / raw)
To: Woody Suwalski; +Cc: linux-kernel, intel-gfx
On Wed, 8 Sep 2010 11:10:42 -0400, Woody Suwalski <terraluna977@gmail.com> wrote:
> LVDS connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
> LVDS-1 connected 800x600+0+0 (normal left inverted right x axis y
The -intel driver does not generate either of these names, it strictly
uses "%s%d" or "UNKNOWN" for the output name. Maybe an Xorg.log would
help identify the issue?
--
Chris Wilson, Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1
2010-09-08 15:19 ` Chris Wilson
@ 2010-09-08 15:52 ` Woody Suwalski
0 siblings, 0 replies; 3+ messages in thread
From: Woody Suwalski @ 2010-09-08 15:52 UTC (permalink / raw)
To: Chris Wilson; +Cc: linux-kernel, intel-gfx
On Wed, Sep 8, 2010 at 11:19 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> On Wed, 8 Sep 2010 11:10:42 -0400, Woody Suwalski <terraluna977@gmail.com> wrote:
>> LVDS connected 800x600+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
>> LVDS-1 connected 800x600+0+0 (normal left inverted right x axis y
>
> The -intel driver does not generate either of these names, it strictly
> uses "%s%d" or "UNKNOWN" for the output name. Maybe an Xorg.log would
> help identify the issue?
>
> --
> Chris Wilson, Intel Open Source Technology Centre
>
Correct about naming.
However it is same X, only the kernel is changed.
The issue is that kernel reports 2 displays connected, when in fact
there is only one.
Here is the part from Xorg.log on 2.6.36:
(II) intel(0): Creating default Display subsection in Screen section
"Builtin Default intel Screen 0" for depth/fbbpp 24/32
(==) intel(0): Depth 24, (--) framebuffer bpp 32
(==) intel(0): RGB weight 888
(==) intel(0): Default visual is TrueColor
(II) intel(0): Integrated Graphics Chipset: Intel(R) 945GME
(--) intel(0): Chipset: "945GME"
(--) intel(0): Linear framebuffer at 0xC0000000
(--) intel(0): IO registers at addr 0xDFE80000 size 524288
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(II) intel(0): the SDVO device with slave addr 70 is found on DVO 1 port
(II) intel(0): 2 display pipes available.
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Module "ddc" already built-in
(II) Loading sub module "i2c"
(II) LoadModule: "i2c"
(II) Module "i2c" already built-in
(II) intel(0): Output VGA has no monitor section
(II) intel(0): Output LVDS has no monitor section
(II) intel(0): I2C bus "LVDSDDC_C" initialized.
(II) intel(0): Attempting to determine panel fixed mode.
(II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0.
(II) intel(0): EDID for output LVDS
(II) intel(0): found backlight control method /sys/class/backlight/acpi_video0
xf86TokenToOptinfo: table is NULL
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B"
registered at address 0x70.
(II) intel(0): I2C bus "SDVOB DDC Bus" initialized.
(II) intel(0): Output LVDS-1 has no monitor section
(II) intel(0): SDVOB: device VID/DID: 02:41.01, clock range 25.0MHz - 200.0MHz
(II) intel(0): SDVOB: 1 input channel
(II) intel(0): SDVOB: LVDS0 output reported
xf86TokenToOptinfo: table is NULL
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized.
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C"
registered at address 0x72.
(II) intel(0): No SDVO device found on SDVOC
(II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed.
(II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed.
(II) intel(0): Current clock rate multiplier: 1
The real issue is that kernel is most likely crashing if KMS is used -
I can see big cursor before KMS, then cursor disappears (if I run in
noquiet mode, the last line will be about drm), and from now on I have
a black screen. Can not ssh into the box, so probably is dead... No
USB kbd seems alive - X input was not run either?
As such - the box is undebugable...
I agree that probably hardware is wired incorrectly, yet "the other
OS" seems to cope with it.
As were kernels 2.6.33...2.6.35.
I just checked the history - I had to backport LVDS detection from
2.6.33 to 2.6.32 to make it work.
Thanks, Woody
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-09-08 15:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-08 15:10 [regression] i915 incorrectly detects bogus LVDS connection instead of LVDS1 Woody Suwalski
2010-09-08 15:19 ` Chris Wilson
2010-09-08 15:52 ` Woody Suwalski
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®