Widescreen resolution

trashbird1240 · 01-24-2007, 10:19 AM

Dear Forum,

I just got a widescreen monitor on my workplace box running Slackware 11.0, kernel 2.6.17.13, with an Intel 845G graphics card (using the i810 driver). After searching the web and the forums I tried 915resolution, tweaking the modelines, using the VESA driver (no good) and nothing has gotten me into a working X-Server with true widescreen resolution (either 1280x800 or the manufacturer recommended 1440x900).

Does anybody have a surefire solution? One that has worked for you?

(not valid responses: switch to Ubuntu, buy a different monitor, any of the solutions I listed above)

I am now using it at 1024x768, which is very nice, only slight distortion and pleasing to my eyes. However, if you know of a solution, please tell me.

Thanks,
Joel

nadroj · 01-24-2007, 10:35 AM

i realize you said not to suggest tasks that you have previously stated, however..

i have an acer widescreen monitor, native resolution is 1400x900 as well. in both windows and linux i dont use 1400x900 because i find it way to small. in windows i used my nvidia software to add a custom resolution for 1280*800@75Hz. in linux i used a modeline calculator to create a modeline and fooled around with the X11 config file for a while in order to get KDE to recognize the 1280x800@75hz, and it works. i think i used 2 websites, i can only remember one of them: http://xtiming.sourceforge.net/cgi-bin/xtiming.pl. the other had more variables and therefore was more accurate but this one worked fine.

did you use a website like this and get the EXACT values from your monitors official users manual/documentation?

edit: i dont have access to the file and therefore the complete configuration of my Xconfig file but i do have this line: Modeline "1280x800@75" 111.50 1280 1312 1728 1760 800 815 825 841

bioe007 · 01-24-2007, 11:13 AM

Quote:

(not valid responses: switch to Ubuntu, buy a different monitor, any of the solutions I listed above)

does that mean asking you what happened when you used 915resolution is off limits?

I have 2 laptops. Either with i830 or i945 chipsets and that is the problem solver for me. (Where I find difficulty is finding a place to put the 915resolution command before X starting up.)

chess · 01-24-2007, 11:50 AM

I have a Dell laptop with the same Intel 845 chip using the i810 driver and 1280x800 widescreen and the 855resolution (now the 915resolution) patch worked beautifully. I just added the command to rc.local to have it start up at boot and I have had no problems whatsoever.

trashbird1240 · 01-24-2007, 12:17 PM

Quote:

Originally Posted by bioe007

does that mean asking you what happened when you used 915resolution is off limits?

No; I saw another thread where somebody offered that solution: that sounds more like running away from a problem or creating new problems than it sounds like solving it.

Mr. Griffin, I wish I had your luck -- does luck play a part here?

Here's what I did:
1. Download and build 915resolution
2. Entered two new modes: 1440x900, 1280x800
3. Edited xorg.conf so that each display section now includes "1440x900" and "1280x800"
4. startx: the screen flickers or just the corner of the screen appears. I exit X by hitting CTL-ALT-backspace

I'll try it again, sometimes writing about it in a forum is enough to make it work.

Joel

chess · 01-24-2007, 02:57 PM

Can you provide the output of 915resolution -l before and after you run the patch? And maybe provide the exact command to run the patch? Lastly, a print out of your xorg.conf should help diagnose the problem.

bioe007 · 01-24-2007, 03:18 PM

Quote:

Originally Posted by Jackson1995

... added the command to rc.local ...

thanks for the tip! it works great.

Quote:

Originally Posted by trashbird1240

that sounds more like running away from a problem or creating new problems than it sounds like solving it.

i agree it is a hackish sort of way to resolve the problem, but my understanding is that the video BIOS is responsible for reporting the correct available screen modes. And the intel chips (or Xorg drivers) do not agree on this format (?) i guess. So there isn't much to be done about it.

I have done a good bit of searching on this and never found an alternative (to 915resolution) that worked.

trashbird1240 · 01-25-2007, 11:59 AM

Currently I'm only using 1024x768. Here's my current xorg.conf:

Code:

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
#    Load       "dri"

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.

    RgbPath	"/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath   "/usr/X11R6/lib/X11/fonts/TTF/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath   "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi/"
    FontPath   "/usr/X11R6/lib/X11/fonts/local/"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo/"
    FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/"

# The module search path.  The default path is shown here.

#    ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option	"Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"	"xorg"
    Option "XkbModel"	"pc104"
    Option "XkbLayout"	"us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "ExplorerPS/2"	# Explorer PS/2
    Option "Device"      "/dev/mouse"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"	"Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"	"256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"	"9600"
#    Option "SampleRate"	"150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

#    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "Samsung"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 64.3

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-60

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"Standard VGA"
    VendorName	"Unknown"
    BoardName	"Unknown"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset	"generic"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "** Intel i810 (generic)               [i810]"
    Driver      "i810"
    #VideoRam    32768
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "** Intel i810 (generic)               [i810]"
    Monitor     "Samsung"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1024x768"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1024x768"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1024x768"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
#    Mode 0666
# EndSection

Currently (with 1280x800 added to screen section in the above file) the screen just flickers.

And here's the output of 915resolution -l:

Code:

/home/joel/data/adhd/txsud Super-User > 915resolution -l
Intel 800/900 Series VBIOS Hack : version 0.5.2

Chipset: 845G
BIOS: TYPE 3
Mode Table Offset: $C0000 + $4d2
Mode Table Entries: 25

Mode 30 : 640x480, 8 bits/pixel
Mode 31 : 640x400, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x1024, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1280x800, 8 bits/pixel
Mode 40 : 640x480, 15 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 42 : 800x600, 15 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 44 : 1024x768, 15 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 48 : 1280x1024, 15 bits/pixel
Mode 49 : 1280x1024, 16 bits/pixel
Mode 4a : 1600x1200, 15 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4c : 1280x800, 15 bits/pixel
Mode 4d : 1280x800, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x1024, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1280x800, 32 bits/pixel

that's from after I set it into rc.local -- showing you the output without the patch would require a reboot and I don't have time for that right now.

One funny thing you'll notice is that I have four bits/pixel settings: 8,15,16,32, and my defaultdepth is 24.

Any help is greatly appreciated.

Joel

bioe007 · 01-25-2007, 03:34 PM

just for comparison sake:

my rc.local commands:

Code:

#!/bin/sh
#
# /etc/rc.d/rc.local:  Local system initialization script.
#
# Put any local startup commands in here.  Also, if you have
# anything that needs to be run at shutdown time you can
# make an /etc/rc.d/rc.local_shutdown script and put those
# commands in there.
/usr/sbin/915resolution 38 1280 800
/usr/sbin/915resolution 58 1280 800

my 915 resolution output:

Code:

root@bcslk:/home/perry# 915resolution -l
Intel 800/900 Series VBIOS Hack : version 0.5.2

Chipset: 945GM
BIOS: TYPE 1
Mode Table Offset: $C0000 + $269
Mode Table Entries: 36

Mode 30 : 640x480, 8 bits/pixel
Mode 32 : 800x600, 8 bits/pixel
Mode 34 : 1024x768, 8 bits/pixel
Mode 38 : 1280x800, 8 bits/pixel
Mode 3a : 1600x1200, 8 bits/pixel
Mode 3c : 1920x1440, 8 bits/pixel
Mode 41 : 640x480, 16 bits/pixel
Mode 43 : 800x600, 16 bits/pixel
Mode 45 : 1024x768, 16 bits/pixel
Mode 49 : 1280x800, 16 bits/pixel
Mode 4b : 1600x1200, 16 bits/pixel
Mode 4d : 1920x1440, 16 bits/pixel
Mode 50 : 640x480, 32 bits/pixel
Mode 52 : 800x600, 32 bits/pixel
Mode 54 : 1024x768, 32 bits/pixel
Mode 58 : 1280x800, 32 bits/pixel
Mode 5a : 1600x1200, 32 bits/pixel
Mode 5c : 1920x1440, 32 bits/pixel
root@bcslk:/home/perry#

other questions;
- did you compile your kernel?
- Is the i810 driver built as a module?
- what happens when you:
add the 1280 x 800 mode to your xorg.conf then, from the console

Code:

# su
Password: ---------
# 915resolution 38 1280 800
# 915resolution -l

## should show you your available modes with #38 being 1280 x 800 
# exit
# startx

essentially can you get 915resolution to work at all (without adding it to a script)?

chess · 01-25-2007, 08:59 PM

Trashbird, I don't see where you added the Modeline for 1280x800 in your "Monitor" section like nadroj mentioned. Have you done that? In my Dell laptop's xorg.conf, I have something like this:

Modeline "1280x800" 83.46 1280 1344 1480 1680 800 801 804 848 -hsync +vsync

in the "Monitor" section.

trashbird1240 · 01-26-2007, 08:03 AM

Quote:

Originally Posted by Jackson1995

Trashbird, I don't see where you added the Modeline for 1280x800 in your "Monitor" section like nadroj mentioned.

Yeah, you don't see it because it's not there

When I added new modelines, in addition to patching with 915resolution, I got even worse results. I got "not using mode 1280x800," etc. Instead of the monitor just flickering, it slowly went between light and dark, looking like it was going to explode. I let it go for a while and it failed to explode, however it was unusable

Then I noticed that the 915resolution README.txt does not mention adding modelines, so I took them out.

I used three different sources for genering modelines: gtf and two online modeline generators. None of them worked. It's hard to tell if it was the modelines getting mixed up or something else.

Do I need them? Let me know where to get modelines that will work.

Thanks,
Joel

bioe007 · 01-26-2007, 05:58 PM

trashbird... i do not use modelines - and it works just fine. But you do have to have 1280x800 as a "Modes" in xorg.conf, or else X will never try and start 1280x800...

snippet from my xorg.conf:

Code:

Subsection "Display"
         Depth 24
         Modes "1280x800" # probably could have this also -> "1024x768"
         Viewport 0 0
EndSubsection

try this sequence, from CLI as root (x not running):
1) modify your xorg.conf (like i suggest above - or whatever widescreen res is appropriate)
2) 915resolution 38 1280 800
3) 915resolution -l # should show 38=1280 800 8 option
4) exit, relogin as normal user, then startx

- you should have 1280x800.

if that works, then add the '/usr/sbin/915resolution 38 1280 800' command to rc.local. voila.

erklaerbaer · 01-28-2007, 09:29 AM

try X -configure; i get way better results with it.

Code:

 this is my xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig:  version 1.0  (buildmeister@builder3)  Tue Aug  1 21:11:12 PDT 2006


Section "ServerLayout"
    Identifier     "X.org Configured"
    Screen      0  "Screen0" 0 0
    InputDevice    "Mouse0" "CorePointer"
    InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
    RgbPath         "/usr/X11R6/lib/X11/rgb"
    ModulePath      "/usr/X11R6/lib/modules"
    FontPath        "/usr/X11R6/lib/X11/fonts/misc/"
    FontPath        "/usr/X11R6/lib/X11/fonts/TTF/"
    FontPath        "/usr/X11R6/lib/X11/fonts/Type1/"
    FontPath        "/usr/X11R6/lib/X11/fonts/CID/"
    FontPath        "/usr/X11R6/lib/X11/fonts/75dpi/"
    FontPath        "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
    Load           "glx"
    Load           "extmod"
    Load           "xtrap"
    Load           "record"
    Load           "dbe"
    Load           "freetype"
    Load           "type1"
EndSection

Section "InputDevice"
    Identifier     "Keyboard0"
    Driver         "kbd"
EndSection

Section "InputDevice"
    Identifier     "Mouse0"
    Driver         "mouse"
    Option         "Protocol" "auto"
    Option         "Device" "/dev/mouse"
    Option         "ZAxisMapping" "4 5"
EndSection

Section "Monitor"

        #DisplaySize      320   240     # mm
    Identifier     "Monitor0"
    VendorName     "OEC"
    ModelName      "706"
    Option         "DPMS" 
EndSection

Section "Device"

        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "SWcursor"                  # [<bool>]
        #Option     "HWcursor"                  # [<bool>]
        Option "CursorShadow" "true"
        #Option     "NoAccel"                   # [<bool>]
        #Option     "ShadowFB"                  # [<bool>]
        #Option     "UseFBDev"                  # [<bool>]
        #Option     "Rotate"                    # [<str>]
        #Option     "VideoKey"                  # <i>
        #Option     "FlatPanel"                 # [<bool>]
        #Option     "FPDither"                  # [<bool>]
        #Option     "CrtcNumber"                # <i>
        #Option     "FPScale"                   # [<bool>]
        #Option     "FPTweak"                   # <i>
    Identifier     "Card0"
    Driver         "nvidia"
    VendorName     "nVidia Corporation"
    BoardName      "NV20 [GeForce3 Ti 200]"
EndSection

Section "Screen"
    Identifier     "Screen0"
    Device         "Card0"
    Monitor        "Monitor0"
   DefaultDepth    24 
    Option         "NoLogo" "True"
    Option         "IgnoreEDID" "True"
    SubSection     "Display"
        Viewport    0 0
        Depth       1
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       4
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       8
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       15
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       16
    EndSubSection
    SubSection     "Display"
        Viewport    0 0
        Depth       24
        Modes      "1024x768"  
    EndSubSection
EndSection

#Section "Extensions"
#    Option         "Composite" "Enable"
#EndSection

the bold parts are the important

trashbird1240 · 01-29-2007, 09:04 AM

Hmmm...great suggestions, I will try them again, however I have tried all of them already and got the results that I posted originally.

To answer your questions: no, this is not a custom kernel, it's the 2.6.17.13 huge26.s kernel with generic modules installed.

915resolution works fine from the command line and in rc.local.

I did add 1280x800 under "Modes" and got the behavior I described.

I tried X -configure, and got even worse results (blnk screen, I believe).

The only exception to what you've mentioned above is that I started X as root, instead of logging out and restarting X as a user.

I should try that.

thanks,
Joel

bioe007 · 01-29-2007, 03:26 PM

trashbird,

I don't know if this makes a difference or not, but you are using different VBIOS modes than I am, have you tried modifying modes 38 and 58 to 1280x800?

Another question, since you didn't compile your own kernel, can you:

# modprobe i915
# modprobe i830 # this might be the wrong module name, but its something i8xx
# lsmod | grep i

? do you see the intel modules?

I do not know if they are compiled in or built as modules in the huge26.s.

Could that be another difference? I build them as modules.

I should have done this earlier, sorry, my xorg.conf:

Code:

Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
	RgbPath      "/usr/X11R6/lib/X11/rgb"
	ModulePath   "/usr/X11R6/lib/modules"
	FontPath     "/usr/X11R6/lib/X11/fonts/misc/"
	FontPath     "/usr/X11R6/lib/X11/fonts/TTF/"
	FontPath     "/usr/X11R6/lib/X11/fonts/Type1/"
	FontPath     "/usr/X11R6/lib/X11/fonts/CID/"
	FontPath     "/usr/X11R6/lib/X11/fonts/75dpi/"
	FontPath     "/usr/X11R6/lib/X11/fonts/100dpi/"
EndSection

Section "Module"
	Load  "glx"
	Load  "extmod"
	Load  "xtrap"
	Load  "record"
	Load  "dbe"
	Load  "dri"
	Load  "freetype"
	Load  "type1"
EndSection

Section "InputDevice"
	Identifier  "Keyboard0"
	Driver      "kbd"
	Option       "XkbModel"  "pc101"
	Option       "XkbLayout"  "us"
EndSection

Section "InputDevice"
	Identifier  "Mouse0"
	Driver      "mouse"
	Option	    "Protocol" "auto"
	Option	    "Device" "/dev/mouse"
	Option	    "ZAxisMapping" "4 5 6 7"
EndSection

Section "Monitor"
	#DisplaySize	  330   210	# mm
	Identifier   "Monitor0"
	VendorName   "CPT"
	ModelName    "13a6"
EndSection

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz"
        ### [arg]: arg optional
        #Option     "NoAccel"            	# [<bool>]
        #Option     "SWcursor"           	# [<bool>]
        #Option     "ColorKey"           	# <i>
        #Option     "CacheLines"         	# <i>
        #Option     "Dac6Bit"            	# [<bool>]
        #Option     "DRI"                	# [<bool>]
        #Option     "NoDDC"              	# [<bool>]
        #Option     "ShowCache"          	# [<bool>]
        #Option     "XvMCSurfaces"       	# <i>
        #Option     "PageFlip"           	# [<bool>]
	Identifier  "Card0"
	Driver      "i810"
	VendorName  "Intel Corporation"
	BoardName   "Mobile Integrated Graphics Controller"
	BusID       "PCI:0:2:0"
EndSection

Section "Screen"
	Identifier "Screen0"
	Device     "Card0"
	Monitor    "Monitor0"
	DefaultDepth 24
	SubSection "Display"
		Viewport   0 0
		Depth     16
		Modes	"1280x800" 
	EndSubSection
	SubSection "Display"
		Viewport   0 0
		Depth     24
		Modes	"1280x800"
	EndSubSection
	Subsection "Display"
		Viewport   0 0
		Depth     32
		Modes	"1280x800"
	EndSubSection
EndSection

Section "DRI"
	Mode 0666
EndSection

when I lsmod:

Code:

perry@bcslk:~$ lsmod
Module                  Size  Used by
i915                   20352  1
drm                    78100  2 i915
snd_pcm_oss            44192  0
snd_mixer_oss          18176  1 snd_pcm_oss
ipv6                  243104  12
snd_hda_intel          21912  0
snd_hda_codec         165424  1 snd_hda_intel
snd_pcm                76164  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              24836  1 snd_pcm
snd                    55396  6 snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_pcm,snd_timer
i2c_i801                8076  0
snd_page_alloc         10632  2 snd_hda_intel,snd_pcm
tg3                   106756  0
serio_raw               7684  0
perry@bcslk:~$

the things I think are wrong now:

- Your xorg.conf is using a generic i810 driver, and unless i'm mistaken, you need the actual i810 - you can get this by using xorgconfig and selecting it, do not pick the first one in the list, there is another one further down: i810 (like mine) i think.

You also definitely need the i915 module. (see my lsmod output)

and while at it you may want to add the drm module and uncomment your 'Section "DRI"' lines. But you could do that later.

I hope this is helping, i'm sorry that its not working yet but as no one else has interrupted with a 'gee whiz - why don't you do this...' I think the only solution is to get 915resolution working.

btw- ignore my 'depth 32' section, the i810 driver does not apparently work at this depth at all.