Re: 1400x1050 on Intel i852GM?
From: Ritesh Kumar (ritesh_at_cs.unc.edu)
Date: 09/18/03
- Next message: Alan Connor: "Re: [OT] Not - Re: Searching program to swith to console from X"
- Previous message: Michael Powe: "Re: [OT] Not - Re: Searching program to swith to console from X"
- In reply to: Jesse F. Hughes: "Re: 1400x1050 on Intel i852GM?"
- Next in thread: Jesse F. Hughes: "Re: 1400x1050 on Intel i852GM?"
- Reply: Jesse F. Hughes: "Re: 1400x1050 on Intel i852GM?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 18 Sep 2003 12:00:41 -0400
Jesse F. Hughes wrote:
> Ritesh Kumar <ritesh@cs.unc.edu> writes:
>
>
>>Jesse F. Hughes wrote:
>>
>>>Hey ho.
>>>
>>>I'm still fussing with my new NEC Versa p520. Thanks to a friend's
>>>help, I've learned why the display seems fuzzy. X is displaying at
>>>1280x1024 on a 1400x1050 LCD.
>>>
>>>Windows uses the correct resolution, so it appears to be possible with
>>>this card. I've tried upgrading to the most recent snapshot of
>>>XFree86, hoping that would find the right mode. No luck there.
>>>
>>>Any help or hints would be greatly appreciated. Please let me know
>>>what information is relevant.
>>>
>>
>>Can you post your X config file ... should be something like
>>/etc/X11/XF86Config-4... there is just a minor change required there to
>>change your resolution..
>
>
> Sorry for the dearth of details above. I should do one thing at a
> time. I'm afraid I didn't pay enough attention to my post.
>
> Here's the relevant sections from my XF86Config.
>
> ,----[ XF86Config (excerpt) ]
> |
> | Section "Monitor"
> | Identifier "Monitor0"
> | VendorName "Monitor Vendor"
> | ModelName "Generic Laptop Display Panel 1400x1050"
> | Option "dpms"
> | EndSection
> |
> | Section "Device"
> | Identifier "Videocard0"
> | Driver "i810"
> | VendorName "Videocard vendor"
> | BoardName "Intel 852"
> | VideoRam 65536
> | EndSection
> |
> | Section "Screen"
> | Identifier "Screen0"
> | Device "Videocard0"
> | Monitor "Monitor0"
> | DefaultDepth 16
> | SubSection "Display"
> | Depth 16
> | Modes "1400x1050" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
> | EndSubSection
> | EndSection
> |
> | Section "DRI"
> | Group 0
> | Mode 0666
> | EndSection
> `----
>
> Here's the monitor section from XFree86.0.log.
>
> ,----
> | (II) I810(0): 2 display pipes available.
> | (II) I810(0): Display Info: CRT: attached: FALSE, present: TRUE, size: (0,0)
> | (II) I810(0): Display Info: TV: attached: FALSE, present: FALSE, size: (0,0)
> | (II) I810(0): Display Info: DFP (digital flat panel): attached: FALSE, present: FALSE, size: (0,0)
> | (II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1400,1050)
> | (II) I810(0): Display Info: TV2 (second TV): attached: FALSE, present: FALSE, size: (0,0)
> | (II) I810(0): Display Info: DFP2 (second digital flat panel): attached: FALSE, present: FALSE, size: (0,0)
> | (II) I810(0): Size of device LFP (local flat panel) is 1400 x 1050
> | (II) I810(0): No active displays on Pipe A.
> | (II) I810(0): Currently active displays on Pipe B:
> | (II) I810(0): LFP (local flat panel)
> | (II) I810(0): Lowest common panel size for pipe B is 1400 x 1050
> `----
>
> Later in the log, we see a slew of modes reported, beginning:
>
> ,----
> | (--) I810(0): Maximum space available for video modes: 8000 kByte
> | Mode: 30 (640x480)
> | ModeAttributes: 0x9b
> | WinAAttributes: 0x7
> | WinBAttributes: 0x0
> | WinGranularity: [...]
> `----
>
> 1400x1050 is not on this list (although some greater resolutions *do*
> appear, including 1600x1200 and 1920x1440).
>
> Following this, we see:
>
> ,----
> | (WW) I810(0): Monitor0: Using default hsync range of 28.00-33.00kHz
> | (WW) I810(0): Monitor0: Using default vrefresh range of 43.00-72.00Hz
> | (II) I810(0): Not using mode "1400x1050" (no mode of this name)
> | (II) I810(0): Not using mode "1280x960" (no mode of this name)
> | (II) I810(0): Not using mode "1152x864" (no mode of this name)
> | (II) I810(0): Increasing the scanline pitch to allow tiling mode (1280 -> 2048).
> | (--) I810(0): Virtual size is 1280x1024 (pitch 2048)
> | (**) I810(0): *Built-in mode "1280x1024"
> | (**) I810(0): *Built-in mode "1024x768"
> | (**) I810(0): *Built-in mode "800x600"
> | (**) I810(0): *Built-in mode "640x480"
> | (==) I810(0): DPI set to (75, 75)
> `----
>
> The result is a fairly fuzzy display at 1280x1024. Let me know if I
> need to provide more details.
>
> By the way, I've tried to install the Intel drivers found at their
> website. This results in Signal 11 when I run X, so I uninstalled
> them. I've also tried compiling the Linux kernel and modules myself,
> but I seem to misunderstand how to do this. I lose the ability to
> load agpgart when I use my own modules. I have the following in my
> .config:
>
> ,----
> | CONFIG_AGP=m
> | CONFIG_AGP_INTEL=y
> | CONFIG_AGP_I810=y
> | CONFIG_AGP_VIA=y
> | CONFIG_AGP_AMD=y
> | # CONFIG_AGP_AMD_8151 is not set
> | CONFIG_AGP_SIS=y
> | CONFIG_AGP_ALI=y
> | # CONFIG_AGP_SWORKS is not set
> | CONFIG_DRM=y
> | # CONFIG_DRM_OLD is not set
> |
> | #
> | # DRM 4.1 drivers
> | #
> | CONFIG_DRM_NEW=y
> | CONFIG_DRM_TDFX=m
> | CONFIG_DRM_R128=m
> | CONFIG_DRM_RADEON=m
> | CONFIG_DRM_I810=m
> | # CONFIG_DRM_I810_XFREE_41 is not set
> | CONFIG_DRM_I830=y
> | CONFIG_DRM_MGA=m
> | # CONFIG_DRM_SIS is not set
> | # CONFIG_MWAVE is not set
> `----
>
> Isn't that right? I see that Slackware's default config file has
> CONFIG_DRM unset. Don't I need the DRM modules? Anyway, right now
> I'm using the modules that came with Slackware 9.0, as they seem to
> work and I don't seem to know what I'm doing.
>
You could go step by step at a time. First, try disabling all DRM and
proceed with getting a sharp, unaccelerated display. I have not had
experience with your chipset but seems that the issue is of a similar
kind I faced on my i815 with LGStudioWorks.
Earlier versions of X (I think <4)coudn't autodetect the Horiz and Vert
Refresh ranges for monitors. So X configuration in those times was
pretty tough. You had to give a modeline associated with every screen
mode you used. This used to have an encoding for Horiz and Vert rates
along with many other nitty gritty "monitory" details.
After the advent of X>4 this issue was solved by automatically probing
the monitor for these numbers. I remember that on my LGStudioWorks I had
this problem of getting incorrect guesses about these numbers (This is
generally called VESA GTF which is a formula for deriving The Horiz and
Vert rates). So I tried giving in an explicit Modeline for my monitor
which also didn't solve the problem as the modeline definition didn't
take negative numbers. (I had got the correct numbers using a
framebuffer for the i810/815 chipset from i810fb.sf.net... Thank you
guys for the giving my high resolution display on my Comp!!!)
So most probably the solution to your problem lies now in doing a few
calculations for yourself. Calculate a Modeline for your monitor and
directly feed it in. If that doesn't work try running a framebuffer and
then your X over it. How to calculate a modeline for you (say once you
have got some numbers from a framebuffer module) is given indetail in
XFree Documentation. Or, try to get hold of a person who has a similar
setup and get hold of his modeline!!
Ritesh
--
Ritesh Kumar Graduate Student cs.unc.edu
"The Difference between Insanity and Genius is nothing but of Success"
-- Eliot Carver (Tommorow Never Dies)
- Next message: Alan Connor: "Re: [OT] Not - Re: Searching program to swith to console from X"
- Previous message: Michael Powe: "Re: [OT] Not - Re: Searching program to swith to console from X"
- In reply to: Jesse F. Hughes: "Re: 1400x1050 on Intel i852GM?"
- Next in thread: Jesse F. Hughes: "Re: 1400x1050 on Intel i852GM?"
- Reply: Jesse F. Hughes: "Re: 1400x1050 on Intel i852GM?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
