Bug 23009 - KMS drives monitor out of range
Summary: KMS drives monitor out of range
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-28 13:50 UTC by Radu Benea
Modified: 2009-07-30 15:10 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log - without KMS (99.44 KB, patch)
2009-07-28 13:50 UTC, Radu Benea
no flags Details | Splinter Review
dmesg from KMS kernel (32.43 KB, text/plain)
2009-07-29 00:46 UTC, Radu Benea
no flags Details
Xorg log - with KMS (47.54 KB, patch)
2009-07-29 00:49 UTC, Radu Benea
no flags Details | Splinter Review

Description Radu Benea 2009-07-28 13:50:11 UTC
Created attachment 28131 [details] [review]
Xorg log - without KMS

I have a benq monitor and a (RV380 3E50) PCIE card which if I understood correctly should be supported by the kernel 2.6.31-rc4 so I decided to try it.

As soon as the module auto-loaded the monitor was driven out of range.

I attached the Xorg log so you can take a look at the reported EDID info (I'm not sure about it but I think it should be ok since it works fine with a lot of cards without any "tuning" in X)

Let me know if you need anymore information and I'll see what I can do to get it.
Comment 1 Alex Deucher 2009-07-28 14:10:43 UTC
Can you attach your dmesg and xorg log when kms is active?
Comment 2 Radu Benea 2009-07-28 14:12:10 UTC
I'll try tomorrow, should be able to ssh in from another machine
Comment 3 Radu Benea 2009-07-29 00:46:19 UTC
Created attachment 28139 [details]
dmesg from KMS kernel

the log sends out an error about not finding i2c data, that's because there's nothing connected to DVI output, my monitor is connected to VGA connector
Comment 4 Radu Benea 2009-07-29 00:49:34 UTC
Created attachment 28140 [details] [review]
Xorg log - with KMS

I don't know if this is very helpful the log suggests that the driver went around KMS instead of using it and initialized succesfully (not for long though), maybe I should have recompiled some stuff?
if yes let me know what to recompile to work with KMS
Comment 5 Radu Benea 2009-07-30 14:26:34 UTC
$ fbset --info

mode "1920x1080-0"
    # D: 0.000 MHz, H: 0.000 kHz, V: 0.000 Hz
    geometry 1920 1080 1920 1080 32
    timings -1 0 0 0 0 0 0
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : radeondrmfb
    Address     : 0xd80c0000
    Size        : 8294400
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 7680
    Accelerator : No
Comment 6 Alex Deucher 2009-07-30 14:38:31 UTC
Do you have fbcon loaded?  You won't get a frame buffer console without it.
Comment 7 Radu Benea 2009-07-30 15:10:25 UTC
as soon as I loaded fbcon it worked, thanks


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.