Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Enabling WXGA (1240x768) on Packard Bell EasyNote under Fedora Core 3

Posted on 2006-04-11
6
Medium Priority
?
1,223 Views
Last Modified: 2013-12-27
I have tried all kinds of things to enable the display at 1240x768px (the exact pixel size of my panel).  The machine is a Packard Bell EasyNote and I am running:

xorg-x11-6.8.2-1 with kernel 2.6.12-1.1381_FC3

These are the monitor and screen parts of xorg.conf:

Section "Monitor"
      Identifier   "Monitor0"
      VendorName   "Monitor Vendor"
      ModelName    "LCD Panel 1280x800"
      HorizSync    31.5 - 90.0
      VertRefresh  60.0 - 60.0
      ModeLine     "1280x768" 103.0 1280 1360 1496 1712 768 769 772 802 -hsync +vsync
      ModeLine     "1280x768_75" 103.0 1280 1360 1496 1712 768 769 772 802 -hsync +vsync
      ModeLine     "1280x768_60" 80.1 1280 1344 1480 1680 768 769 772 795 -hsync +vsync
      ModeLine     "1280x768_50" 65.2 1280 1336 1464 1648 768 769 772 791 -hsync +vsync
EndSection

Section "Screen"
      Identifier "Screen0"
      Device     "Videocard0"
      Monitor    "Monitor0"
      DefaultDepth     24
      SubSection "Display"
            Depth     8
            Modes    "1280x768"
      EndSubSection
      SubSection "Display"
            Depth     15
            Modes    "1280x768"
      EndSubSection
      SubSection "Display"
            Depth     16
            Modes    "1280x768"
      EndSubSection
EndSection

Here is an extract from the Xorg log which may help (?):

(II) I810(0): Display Info: CRT: attached: FALSE, present: TRUE, size: (720,400)
(II) I810(0): Display Info: TV: attached: FALSE, present: TRUE, size: (800,600)
(II) I810(0): Display Info: DFP (digital flat panel): attached: FALSE, present: FALSE, size: (0,2059)
(II) I810(0): Display Info: LFP (local flat panel): attached: TRUE, present: TRUE, size: (1280,800)
(II) I810(0): Display Info: CRT2 (second CRT): attached: FALSE, present: FALSE, size: (0,2059)
(II) I810(0): Display Info: TV2 (second TV): attached: FALSE, present: FALSE, size: (0,2059)
(II) I810(0): Size of device LFP (local flat panel) is 1280 x 800
(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 1280 x 800
(==) I810(0): Display is using Pipe B
(--) I810(0): Maximum frambuffer space: 65368 kByte
(II) I810(0): VESA VBE PanelID read successfully
(II) I810(0): PanelID returned panel resolution : 1280x800
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/X11R6/lib/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
      compiled for 6.8.2, module version = 1.0.0
      ABI class: X.Org Video Driver, version 0.7
(II) I810(0): VESA VBE DDC supported
(II) I810(0): VESA VBE DDC Level none
(II) I810(0): VESA VBE DDC transfer in appr. 0 sec.
(II) I810(0): VESA VBE DDC read failed
(--) I810(0): A non-CRT device is attached to pipe B.
      No refresh rate overrides will be attempted.
(--) I810(0): Maximum space available for video modes: 32576 kByte

....

(II) I810(0): Monitor0: Using hsync range of 31.50-90.00 kHz
(II) I810(0): Monitor0: Using vrefresh value of 60.00 Hz
(II) I810(0): Not using mode "1920x1440" (no mode of this name)
(II) I810(0): Not using mode "1600x1200" (no mode of this name)
(II) I810(0): Not using mode "1280x1024" (no mode of this name)
(II) I810(0): Not using mode "1280x960" (no mode of this name)
(II) I810(0): Not using mode "800x600" (no mode of this name)
(--) I810(0): Virtual size is 1024x768 (pitch 1024)
(**) I810(0): *Built-in mode "1024x768"
(**) I810(0): *Built-in mode "640x480"
(==) I810(0): DPI set to (75, 75)


Here is the entire contents of /usr/share/rhpl/extramodes :

ModeLine "1280x768"  102.98  1280 1360 1496 1712  768 769 772 802  -HSync +Vsync
ModeLine "1280x768_75"  102.98  1280 1360 1496 1712  768 769 772 802  -HSync +Vsync
ModeLine "1280x768_60"  80.14  1280 1344 1480 1680  768 769 772 795  -HSync +Vsync
ModeLine "1280x768_50"  65.18  1280 1336 1464 1648  768 769 772 791  -HSync +Vsync
0
Comment
Question by:vincevincevince
  • 4
5 Comments
 
LVL 62

Expert Comment

by:gheist
ID: 16429472
Your intel onboard videocard does not have BIOS mode to display on your LCD panel. Modelines do not help.
Download i915 driver from Intel, it does any resolution, but last time right in this site it was checked as nonworking under 2.6 kernel

0
 
LVL 62

Expert Comment

by:gheist
ID: 16429525
> (II) I810(0): PanelID returned panel resolution : 1280x800
Your panel is broke as it returns wrong data - even windows will have edge of desktop detached, since you counted 1240 and 768.

Go first without modelines and custom resolutions and post i810 driver chipset identifications, right above first lines you posted, smth like this:
(--) RADEON(0): Chipset: "ATI Radeon 9200SE 5964 (AGP)" (ChipID = 0x5964)
0
 
LVL 1

Author Comment

by:vincevincevince
ID: 16432923
Thanks for your advice.  These lines appear to be related to the chipset identifications.  Under windows (it's a dual boot system) the screen works fine.

(II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100,
      i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915),
      915GM, 945G
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(--) Chipset 852GM/855GM found

....

(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
(II) I810(0): VESA BIOS detected
(II) I810(0): VESA VBE Version 3.0
(II) I810(0): VESA VBE Total Mem: 32576 kB
(II) I810(0): VESA VBE OEM: Intel(r)852GM/852GME/855GM/855GME Graphics Chip Accelerated VGA BIOS
(II) I810(0): VESA VBE OEM Software Rev: 1.0
(II) I810(0): VESA VBE OEM Vendor: Intel Corporation
(II) I810(0): VESA VBE OEM Product: Intel(r)852GM/852GME/855GM/855GME Graphics Controller
(II) I810(0): VESA VBE OEM Product Rev: Hardware Version 0.0
(II) I810(0): Integrated Graphics Chipset: Intel(R) 852GM
(--) I810(0): Chipset: "852GM/855GM"

...

(II) I810(0): [drm] loaded kernel module for "i915" driver
(II) I810(0): [drm] DRM interface version 1.2
(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"

...

0
 
LVL 62

Accepted Solution

by:
gheist earned 2000 total points
ID: 16434129
Let me assune 1280x800 instead, as read from panel by videocard.
this is rather wrong - default depth has no resolutions:
Section "Screen"
     Identifier "Screen0"
     Device     "Videocard0"
     Monitor    "Monitor0"
     DefaultDepth     24
     SubSection "Display"
          Depth     8
          Modes    "1280x768"
     EndSubSection
     SubSection "Display"
          Depth     15
          Modes    "1280x768"
     EndSubSection
     SubSection "Display"
          Depth     16
          Modes    "1280x768"
     EndSubSection
EndSection

Suggested - remove or comment modelines,
add Option      "DPMS" where modelines was  - not required for your problem, but will fix blanking screen when overriding DDC info.
and add resolutions to your default color depth.

Section "Screen"
     Identifier "Screen0"
     Device     "Videocard0"
     Monitor    "Monitor0"
     DefaultDepth     24
     SubSection "Display"
          Depth     24
          Modes    "1280x800" "640x480"
     EndSubSection
EndSection

640x480 is intended as fallback, in case 1280x800 does not display as intended, then you will need modeline

Post back results you get
0
 
LVL 62

Expert Comment

by:gheist
ID: 16626351
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup topic area:

Accept gheist http:#16434129

Any objections should be posted here in the next 4 days. After that time, the question will be closed.

gheist
EE Cleanup Volunteer
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Using libpcap/Jpcap to capture and send packets on Solaris version (10/11) Library used: 1.      Libpcap (http://www.tcpdump.org) Version 1.2 2.      Jpcap(http://netresearch.ics.uci.edu/kfujii/Jpcap/doc/index.html) Version 0.6 Prerequisite: 1.      GCC …
Every server (virtual or physical) needs a console: and the console can be provided through hardware directly connected, software for remote connections, local connections, through a KVM, etc. This document explains the different types of consol…
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Learn how to get help with Linux/Unix bash shell commands. Use help to read help documents for built in bash shell commands.: Use man to interface with the online reference manuals for shell commands.: Use man to search man pages for unknown command…
Suggested Courses

581 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question