| View previous topic :: View next topic |
| Author |
Message |
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
 Posted: Wed Dec 01, 2004 3:32 pm Post subject: Xorg, i810, |
 |
|
Hello, I can't get Xorg 6.8.0-r3 to run on my workstation. I don't know why this occurs and how to fix it. The same basic kernel configuration used to work fine with XFree86.
startx yields:
| Code: | Using vt 7
dlopen: /usr/X11R6/lib/modules/drivers/i810_drv.so: undefined symbol: drmGetLibVersion
(EE) Failed to load /usr/X11R6/lib/modules/drivers/i810_drv.so
(EE) Failed to load module "i810" (loader failed, 7)
(EE) No drivers available. |
In the kernel:
| Code: | CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_DRM=y
CONFIG_DRM_I810=y
CONFIG_FB=y
CONFIG_FB_I810=y |
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 "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/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
# FontPath "/usr/share/fonts/CID/"
# FontPath "/usr/share/fonts/75dpi/"
# FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/local/"
# FontPath "/usr/share/fonts/Speedo/"
# FontPath "/usr/share/fonts/TrueType/"
# FontPath "/usr/share/fonts/freefont/"
# 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 <Crtl><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 <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.
# Option "DontZap"
# Uncomment this to disable the <Crtl><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" "pc102"
# 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" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Option "XkbRules" "xorg"
Option "XkbModel" "pc102"
Option "XkbLayout" "us_intl"
EndSection
# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************
Section "InputDevice"
# Identifier and driver
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/input/mouse"
# Mouse-speed setting for PS/2 mouse.
# Option "Resolution" "256"
# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.
# Option "Protocol" "Xqueue"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Emulate3Buttons is an option for 2-button Microsoft 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 "S710"
# 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 30-70
# 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-160
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 "i810"
# 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 810"
Driver "i810"
VideoRam 4096
# 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 810"
Monitor "S710"
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 |
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
 |
Voltago
Advocate
Joined: 02 Sep 2003
Posts: 2593
Location: userland
|
| Posted: Wed Dec 01, 2004 3:58 pm Post subject: |
|
|
Hi! What graphics hardware do you use? What does
and
| Code: | | less /var/log/Xorg.0.log |
tell you?
Last edited by Voltago on Wed Dec 01, 2004 3:59 pm; edited 1 time in total |
|
| Back to top |
|
|
Codo
Apprentice
Joined: 17 May 2004
Posts: 271
|
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Wed Dec 01, 2004 4:10 pm Post subject: |
|
|
lspci:
| Code: | 0000:00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02)
0000:00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset Graphics Controller] (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 01)
0000:00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 01)
0000:00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 01)
0000:00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 01)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio (rev 01)
0000:02:04.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 24)
0000:02:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 01) |
Yes, I know how to configure X. I did a standard xorgconfig and set all options to the same values I used (succesfully) in XFree86. I know it's trying to load the i810_drv.so module; I assume it should use the driver in the kernel, right?
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
dohko
Tux's lil' helper
Joined: 24 Sep 2004
Posts: 112
Location: São Paulo - Brasil
|
| Posted: Wed Dec 01, 2004 7:29 pm Post subject: |
|
|
Hi,
I had a problem with the i810 driver when I updated from xorg-6.7 to xorg-6.8. The newer wouldn't use the i810 kernel module correctly anymore. I solved it by leaving i810 as the video card driver in xorg.conf but selecting i915 (I think this is available only in >=2.6.8 kernels) as kernel module.
Here's the relevant part of my kernel config:
| Code: | CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=m
CONFIG_AGP_INTEL_MCH=m
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_I810 is not set
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set |
and the framebuffer section:
| Code: | CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_VESA=y
# CONFIG_FB_VESA_STD is not set
CONFIG_FB_VESA_TNG=y
CONFIG_FB_VESA_DEFAULT_MODE="640x480@60"
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
CONFIG_FB_I810=m |
And here's the relevant part of my xorg.conf:
| Code: | Section "Device"
Identifier "Card0"
Driver "i810"
Option "NoAccel" "false"
Option "DRI" "true"
EndSection
|
Also, if you want dri enabled, uncomment the last three lines of your xorg.conf. |
|
| Back to top |
|
|
JackDog
Apprentice
Joined: 09 Sep 2004
Posts: 297
Location: St. Louis, Missoura
|
| Posted: Wed Dec 01, 2004 8:44 pm Post subject: |
|
|
| Use the 915 driver. With that and DRM installed you should be able to get ~1000 fps with glxgears. |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Wed Dec 01, 2004 9:24 pm Post subject: |
|
|
Thanks for the replies guys, this is the kind of answer I needed. I will give it a go tomorrow and let you know how it works out. Perhaps this should be fed back upstream into some of the HOWTOs (provided the solution works).
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Thu Dec 02, 2004 10:52 am Post subject: |
|
|
It doesn't work. I copied the settings you posted before and it still borks with 'undefined symbol: drmGetLibVersion'.
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
dohko
Tux's lil' helper
Joined: 24 Sep 2004
Posts: 112
Location: São Paulo - Brasil
|
| Posted: Thu Dec 02, 2004 11:05 am Post subject: |
|
|
Check wheter the intel-agp and i915 modules are loaded by using lsmod. I put the intel-agp module in the modules.autoload/kernel-2.6.
Even if they are already loaded, try putting the intel-agp in the modules.autoload. |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Thu Dec 02, 2004 11:11 am Post subject: |
|
|
| Code: | hva ~ # lsmod
Module Size Used by
i915 80228 0
intel_agp 22560 1
agpgart 33960 1 intel_agp |
Putting it into the autoload has no effect.
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
dohko
Tux's lil' helper
Joined: 24 Sep 2004
Posts: 112
Location: São Paulo - Brasil
|
| Posted: Thu Dec 02, 2004 11:18 am Post subject: |
|
|
| Is there any message in your kernel log related to i915 drm or any other thing that might give any clue about the problem? |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Thu Dec 02, 2004 11:20 am Post subject: |
|
|
Nope, no errors. The only error that appears is the undefined symbol one. Right now the only thing I can think of is that the modules that were built by Xorg have some kind of version mismatch going on. This problem is somewhat reminiscent of the issues you get when changing kernel versions and trying to use old modules...
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
dohko
Tux's lil' helper
Joined: 24 Sep 2004
Posts: 112
Location: São Paulo - Brasil
|
| Posted: Thu Dec 02, 2004 11:28 am Post subject: |
|
|
Well, I got no more ideas here. If you find a solution, post it, I'll be interested in reading it! 
Good luck! |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Thu Dec 02, 2004 11:30 am Post subject: |
|
|
I will... Right now I'm going to try and re-emerge xorg-x11 first; a long shot to see if the version thing is maybe the cause.
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Thu Dec 02, 2004 2:12 pm Post subject: |
|
|
Re-emerging Xorg hasn't helped, still the same error. Can a Gentoo dev or guru please look at this?
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
SPY_jmr1
n00b
Joined: 02 Jan 2004
Posts: 62
|
| Posted: Thu Dec 02, 2004 4:13 pm Post subject: |
|
|
don't know if it would help, but on one of my i810e MB's, in xorg 6.8, i had to explictly define that it had 16 Megs of video ram availible to it... for some reason, it wasn't allocating it dynamicly anymore.
good luck, and if you need any wigs or anything after ripping all your hair out and all, let us know...  |
|
| Back to top |
|
|
zaanpenguin
Apprentice
Joined: 01 Jul 2003
Posts: 203
|
| Posted: Thu Dec 02, 2004 7:16 pm Post subject: |
|
|
This is a Compaq Deskpro EN866 machine. I have no control in the BIOS over the amount of memory that gets assigned to the onboard i810. It always has 4MB.
_________________
Staying crunchy even in milk! |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Fri Dec 03, 2004 8:41 am Post subject: |
|
|
| dohko wrote: | | I had a problem with the i810 driver when I updated from xorg-6.7 to xorg-6.8. The newer wouldn't use the i810 kernel module correctly anymore. I solved it by leaving i810 as the video card driver in xorg.conf but selecting i915 (I think this is available only in >=2.6.8 kernels) as kernel module. |
dohko, what kernel branch are you referring to? i'm using gentoo-dev-sources, and there's no i915 support in this kernel branch. the only intel chipsets supported are: Linux Kernel Configuration --> Device Drivers --> Graphics Support --> <*> Intel 810/815 support (EXPERIMENTAL)
zaanpenguin, i have had nothing but trouble with the i810 chipset in Linux. There seems to be a major problem with X11, as the X11 implementations on the current releases of Mandrake and SuSE all cause video based lockups with this chipset. my primary reason for migrating to Gentoo was to try to get a better handle on eliminating this problem.
i have never gotten the i810 chipset in my Dell Optiplex to work properly in Linux -- the closest that I have come has beren getting framebuffer support working to support Gensplash at bootup, with minor bugs. i have had absolutely no luck getting the i180 chipset working with X11 6.8.0. for some reason, the chipset is rendering all windows and menus as 100% transparent.
in contrast, i can get the system working quite well by stuffing an old matrox card into a PCI expansion slot and by using generic vesa video support.
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
SPY_jmr1
n00b
Joined: 02 Jan 2004
Posts: 62
|
| Posted: Fri Dec 03, 2004 9:06 am Post subject: |
|
|
| zaanpenguin wrote: | | This is a Compaq Deskpro EN866 machine. I have no control in the BIOS over the amount of memory that gets assigned to the onboard i810. It always has 4MB. |
mine is the same way; Irregardless, in the xorg.conf/xfree86.conf file, i think its in devices, you can set VideoRam to something, instead of auto detecting it...
The way I understand it in linux, the bios starts the machine, and after the kernel is running, it basicly says, ok, uhhuh, whatever, and sets its own hardware anyway.
Is MTRR enabled in the kernel? i seem to remember i810's demanding that setting... Take with a grain of salt, though. 
good luck again
EDIT: for reference, this is the device setting off of my 810 box, (can get to it now)
| Code: | 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 Corp."
BoardName "82810E DC-133 CGC [Chipset Graphics Controller]"
BusID "PCI:0:1:0"
#VideoRam 32768
VideoRam 16384
EndSection
|
Hope it helps a bit... |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Fri Dec 03, 2004 9:18 am Post subject: |
|
|
| SPY_jmr1 wrote: | | zaanpenguin wrote: | | This is a Compaq Deskpro EN866 machine. I have no control in the BIOS over the amount of memory that gets assigned to the onboard i810. It always has 4MB. |
mine is the same way; Irregardless, in the xorg.conf/xfree86.conf file, i think its in devices, you can set VideoRam to something, instead of auto detecting it...
...
Is MTRR enabled in the kernel? i seem to remember i810's demanding that setting... Take with a grain of salt, though. |
the i810 driver defaults to a video ram setting of 4 MB. if you don't want the default value, you can explicitly define the amount of video ram that the driver uses by assigning a "vram" value as a kernel parameter. the recommended values are 1 - 4 MB.
the "mtrr" parameter is designed to allow data transfers to the framebuffer memory to occur in bursts. this can typically speed up video performance. on an i810 chipset, however, this is not at all helpful, as the chipset uses conventional memory as video memory. in fact, both the default and recommended parameters are that mtrr is not set as a kernel option.
if anyone is looking for info on troubleshooting the i810 kernel parameters, the docs can be found at:
/usr/src/linux/Documentation/fb/intel810.txt
the fact that you're telling the driver to use 16 MB in your xorg.conf file is interesting. have you checked your memory usage to see if this memory is reserved, and if so, how much of it is actually used? what happens if you decrease the size of the memory to the recommended value of 4096?
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
dohko
Tux's lil' helper
Joined: 24 Sep 2004
Posts: 112
Location: São Paulo - Brasil
|
| Posted: Fri Dec 03, 2004 10:56 am Post subject: |
|
|
| Bob P wrote: | | dohko, what kernel branch are you referring to? i'm using gentoo-dev-sources, and there's no i915 support in this kernel branch. the only intel chipsets supported are: Linux Kernel Configuration --> Device Drivers --> Graphics Support --> <*> Intel 810/815 support (EXPERIMENTAL) |
Bob P,
I'm using gentoo-dev-sources. I'm currently using the 2.6.9-r6 kernel. I had also used the 2.6.9-r1 and 2.6.9-r4 kernels before and the i915 module also worked fine with them.
The i915 module is in Linux Kernel Configuration --> Device Drivers --> Character Devices --> Intel 440LX/BX/GX, I8xx and E7x05 chipset support --> <M> Intel 830M, 845G, 852GM, 855GM, 865G --> <M> i915 driver.
The path in the kernel config you've pointed out in the above quote is the support for i810 framebuffer device (mine is selected as a module). |
|
| Back to top |
|
|
Bob P
Advocate
Joined: 20 Oct 2004
Posts: 3355
Location: Jackass! Development Labs
|
| Posted: Fri Dec 03, 2004 12:41 pm Post subject: |
|
|
| dohko wrote: | | Bob P wrote: | | dohko, what kernel branch are you referring to? i'm using gentoo-dev-sources, and there's no i915 support in this kernel branch. the only intel chipsets supported are: Linux Kernel Configuration --> Device Drivers --> Graphics Support --> <*> Intel 810/815 support (EXPERIMENTAL) |
...
The i915 module is in Linux Kernel Configuration --> Device Drivers --> Character Devices --> Intel 440LX/BX/GX, I8xx and E7x05 chipset support --> <M> Intel 830M, 845G, 852GM, 855GM, 865G --> <M> i915 driver.
The path in the kernel config you've pointed out in the above quote is the support for i810 framebuffer device (mine is selected as a module). |
thanks. i'd like to duplicate the success that you're having, so please let me know if i have your video options listed correctly:
in the kernel config:
1. vesafb and vesafb-tng are not selected
2. i810 framebuffer support is selected as a module
3. i915 character device is selected as a module
in xorg.conf:
1. i810 is listed as the video driver
2. the VideoRam allocation is 4096
i have to admit, i am at a loss to explain why the selection of the i915 character device module would fix the GUI video problem, but i'm so desperate i'll try anything.
now here's an interesting observation: after following the recommendations of SPY_jmr1, I decided to test out the use of "improper" memory allocation to the i810 driver in xorg.conf. so i did the following:
in kernel.config:
1. vesafb and vesafb-tng not selected
2. i810 framebuffer selected
3. i810 character device selected
in xorg.conf:
| Code: | Section "Device"
### Available Driver options are:-
# sw_cursor is needed for some ati and radeon cards
#Option "sw_cursor"
#Option "hw_cursor"
#Option "NoAccel"
#Option "ShowCache"
#Option "ShadowFB"
#Option "UseFBDev"
#Option "Rotate"
Identifier "Card0"
Driver "i810"
VendorName "All"
BoardName "All"
VideoRam 16384
#BusID "PCI:1:0:0"
EndSection |
i have observed, with great amazement, that the appropriate VideoRam setting of 4096 resulted in transparent windows within X. doubling the setting to 8192 (twice the maximum value addressable by the chipset) resulted in no improvement. quadrupling the value to 16384, however, resulted in a perfectly functional X system.
i am at a loss to explain it. dohko, i'd appreciate it if you could help me duplicate your results, as i would prefer not to assign more system memory to the video board than is necessary.
thanks!
_________________
.
Stage 1/3 | Jackass! | Rockhopper! | Thanks | Google Sucks |
|
| Back to top |
|
|
dohko
Tux's lil' helper
Joined: 24 Sep 2004
Posts: 112
Location: São Paulo - Brasil
|
| Posted: Fri Dec 03, 2004 2:11 pm Post subject: |
|
|
Hi guys,
I'll try to describe exactly the configuration that I'm using here. Maybe other configurations may work as well.
First of all, here is my lspci:
| Code: | 0000:00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02)
0000:00:02.0 VGA compatible controller: Intel Corp. 82865G Integrated Graphics Device (rev 02)
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02)
0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2)
0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801EB/ER (ICH5/ICH5R) Ultra ATA 100 Storage Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
0000:03:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 02) |
My kernel is gentoo-dev-sources-2.6.9-r8 (updated this morning). I've compiled it with genkernel.
Video card related configuration in kernel:
character devices:
<M> /dev/agpgart (AGP Support)
<M> Intel i865 chipset support
[*] Direct Rendering Manager
<M> Intel 830M, 845G, 852GM, 855GM, 865G
<M> i915 driver
graphics suppport:
[*] Support for frame buffer devices
<*> VESA VGA graphics support
VESA driver type (vesafb-tng)
<M> Intel 810/815 support
[ ] Support for the framebuffer splash
Some xorg.conf entries:
| Code: | Section "Device"
Identifier "Card0"
Driver "i810"
Option "NoAccel" "false"
Option "DRI" "true"
EndSection
Section "Screen"
# The Identifier, Device and Monitor lines must be present
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
# The favoured Depth and/or Bpp may be specified here
DefaultDepth 24
SubSection "Display"
Depth 8
Modes "800x600" "640x480"
ViewPort 0 0
#Virtual 800 600
EndSubsection
SubSection "Display"
Depth 4
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection |
Note: I don't use 1024x768 because my monitor refresh rate in that mode is too low, but it works.
In grub, I use the following boot parameters (no line break in the kernel line):
| Code: |
title=Gentoo Linux 2.6.9-gentoo-r8
root (hd0,0)
kernel /kernel-2.6.9-gentoo-r8 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/hda6 gentoo=nodevfs
initrd /initrd-2.6.9-gentoo-r8 |
Notice that I don't pass the kernel the "vga=792" parameter. That should make no difference to X, but as I said, I'm describing exactly what I do.
I don't know if that will make a difference to this issue, but I use linux26-headers instead of linux-headers. I've compiled xorg-6.8 after I had changed to linux26-headers.
If that doesn't work for you, Bob P, what kind of error do you get in xorg's log? The same that zaanpenguin gets (symbol error)? |
|
| Back to top |
|
|
SPY_jmr1
n00b
Joined: 02 Jan 2004
Posts: 62
|
| Posted: Fri Dec 03, 2004 5:50 pm Post subject: |
|
|
| Bob P wrote: | | dohko wrote: | | Bob P wrote: | | dohko, what kernel branch are you referring to? i'm using gentoo-dev-sources, and there's no i915 support in this kernel branch. the only intel chipsets supported are: Linux Kernel Configuration --> Device Drivers --> Graphics Support --> <*> Intel 810/815 support (EXPERIMENTAL) |
...
The i915 module is in Linux Kernel Configuration --> Device Drivers --> Character Devices --> Intel 440LX/BX/GX, I8xx and E7x05 chipset support --> <M> Intel 830M, 845G, 852GM, 855GM, 865G --> <M> i915 driver.
The path in the kernel config you've pointed out in the above quote is the support for i810 framebuffer device (mine is selected as a module). |
thanks. i'd like to duplicate the success that you're having, so please let me know if i have your video options listed correctly:
in the kernel config:
1. vesafb and vesafb-tng are not selected
2. i810 framebuffer support is selected as a module
3. i915 character device is selected as a module
in xorg.conf:
1. i810 is listed as the video driver
2. the VideoRam allocation is 4096
i have to admit, i am at a loss to explain why the selection of the i915 character device module would fix the GUI video problem, but i'm so desperate i'll try anything.
now here's an interesting observation: after following the recommendations of SPY_jmr1, I decided to test out the use of "improper" memory allocation to the i810 driver in xorg.conf. so i did the following:
in kernel.config:
1. vesafb and vesafb-tng not selected
2. i810 framebuffer selected
3. i810 character device selected
in xorg.conf:
| Code: | Section "Device"
### Available Driver options are:-
# sw_cursor is needed for some ati and radeon cards
#Option "sw_cursor"
#Option "hw_cursor"
#Option "NoAccel"
#Option "ShowCache"
#Option "ShadowFB"
#Option "UseFBDev"
#Option "Rotate"
Identifier "Card0"
Driver "i810"
VendorName "All"
BoardName "All"
VideoRam 16384
#BusID "PCI:1:0:0"
EndSection |
i have observed, with great amazement, that the appropriate VideoRam setting of 4096 resulted in transparent windows within X. doubling the setting to 8192 (twice the maximum value addressable by the chipset) resulted in no improvement. quadrupling the value to 16384, however, resulted in a perfectly functional X system.
i am at a loss to explain it. dohko, i'd appreciate it if you could help me duplicate your results, as i would prefer not to assign more system memory to the video board than is necessary.
thanks! |
I don't know why it works, i found it on some maillist from google or another, and to be honest, I was happy that it worked, and didn't know it wasn't suposed to be doing so
I had also ripped my hair out with the i915 driver, to no avail, but from what i understood, the 915 is for intel's other intragrated chipsets, other then the i810, but 810's demand the proper driver... I am not sure, though, I get the feeling the drivers are in flux in the newer kernels?
(the machine i did it on for my 810 runs on 2.6.8.1, but for other reasons, it also worked on a 2.6.9-nitro also)
Again, I just knew it worked, i didn't know why though... Now i'm interesrted too |
|
| Back to top |
|
|
uxcv11
n00b
Joined: 04 Dec 2004
Posts: 1
|
| Posted: Sat Dec 04, 2004 1:13 pm Post subject: |
|
|
Hi guys,
I'm completely new to both Gentoo and Linux and have encountered similar difficulties with my i810 on-board video (it's a Dell GX150) after updating to Xorg 6.8.
I originally used the 2004.3 live cd and used genkernel to build my 2.6.9-r1 kernel.
I'm not sure what version of Xorg was on the CD, but I used the prebuilt packages there. It worked great after tweaking the hsync and vsync parameters for my monitor in Xorg.conf. I spent a couple of days playing with KDE and various simpler window managers with no problems.
A couple of days ago I decided to emerge world which updated X. It finished compiling earlier today and I used genkernel to update the kernel to 2.6.9-r6. After that X hung the system with a scrambled screen and nothing interesting in Xorg.0.log.
I found this thread (and many other i810 threads!) and tried the options and parameters given below in my Xorg.conf and now it works again! I tried the VideoRam parameter first on its own and it didn't help.
| dohko wrote: |
Some xorg.conf entries:
| Code: | Section "Device"
Option "NoAccel" "false"
Option "DRI" "true"
VideoRam 16384
EndSection
Section "DRI"
Mode 0666
EndSection |
|
I just thought I should add this experience to the problem solving effort in case it might be of value.
BTW, the forums here are great. Although I'm sure my luck will eventually run out, every problem I've encountered in setting up Gentoo on my system that I couldn't solve using man or the docs at gentoo.org has been answered somewhere in the archives here. This is my first post!
Jeff |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
