Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Getting DRI working with Intel Sonoma (i915GM) chipset
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next  
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks
View previous topic :: View next topic  
Author Message
c_t
n00b
n00b


Joined: 29 Oct 2003
Posts: 36
Location: Berlin, Germany

PostPosted: Fri Dec 02, 2005 1:48 pm    Post subject: Reply with quote

Hi guys!
First of all thanks vinz for this great HOWTO! I have followed all described steps, patching and compiling xorg worked without any problems, unfortunately I cannot start the X-Server after compiling xorg with the patch applied.

Here is what I did:

Installed gentoo-sources-2.6.14-r2 with the following options:
Code:
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# 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=y
# 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=y
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set


Now I've tried to install xorg-x11-6.8.2-r6 and xorg-x11-6.8.99.15-r4 both with the dri-patch applied. In both cases when I try to startx I get the following errorlog (the errormessages are pretty much the same with both xorg-versions!):
Code:

X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.14-gentoo-r2 i686 [ELF]
Current Operating System: Linux spock.nemata.lan 2.6.14-gentoo-r2 #19 PREEMPT Thu Dec 1 14:37:56 CET 2005 i686
Build Date: 01 December 2005
   Before reporting problems, check http://wiki.X.Org
   to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec  2 14:15:34 2005
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "SingleHeadLayout"
(**) |-->Screen "LaptopScreen" (0)
(**) |   |-->Monitor "LaptopTFT"
(**) |   |-->Device "i915Chipset"
(**) |-->Input Device "LogitechClickPlus"
(**) |-->Input Device "LaptopKeyboard"
(**) FontPath set to "/usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/Type1/,/usr/share/fonts/75dpi/,/usr/share/fonts/100dpi/"
(**) RgbPath set to "/usr/lib/X11/rgb"
(**) ModulePath set to "/usr/lib/modules"
(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
   X.Org ANSI C Emulation: 0.2
   X.Org Video Driver: 0.7
   X.Org XInput driver : 0.4
   X.Org Server Extension : 0.2
   X.Org Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: "bitmap"
(II) Loading /usr/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   Module class: X.Org Font Renderer
   ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: "pcidata"
(II) Loading /usr/lib/modules/libpcidata.a
(II) Module pcidata: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   ABI class: X.Org Video Driver, version 0.7
Using vt 7
(--) using VT number 7

(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 8086,2590 card 144d,c01a rev 03 class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 8086,2592 card 144d,c01a rev 03 class 03,00,00 hdr 80
(II) PCI: 00:02:1: chip 8086,2792 card 144d,c01a rev 03 class 03,80,00 hdr 80
(II) PCI: 00:1c:0: chip 8086,2660 card 0000,0000 rev 03 class 06,04,00 hdr 81
(II) PCI: 00:1d:0: chip 8086,2658 card 144d,c01a rev 03 class 0c,03,00 hdr 80
(II) PCI: 00:1d:1: chip 8086,2659 card 144d,c01a rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:2: chip 8086,265a card 144d,c01a rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:3: chip 8086,265b card 144d,c01a rev 03 class 0c,03,00 hdr 00
(II) PCI: 00:1d:7: chip 8086,265c card 144d,c01a rev 03 class 0c,03,20 hdr 00
(II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev d3 class 06,04,01 hdr 81
(II) PCI: 00:1e:2: chip 8086,266e card 144d,c01a rev 03 class 04,01,00 hdr 00
(II) PCI: 00:1e:3: chip 8086,266d card 144d,2115 rev 03 class 07,03,00 hdr 00
(II) PCI: 00:1f:0: chip 8086,2641 card 144d,c01a rev 03 class 06,01,00 hdr 80
(II) PCI: 00:1f:1: chip 8086,266f card 144d,c01a rev 03 class 01,01,8a hdr 00
(II) PCI: 00:1f:3: chip 8086,266a card 144d,c01a rev 03 class 0c,05,00 hdr 00
(II) PCI: 06:05:0: chip 14e4,170c card 144d,c01a rev 02 class 02,00,00 hdr 00
(II) PCI: 06:07:0: chip 8086,4220 card 8086,2731 rev 05 class 02,80,00 hdr 00
(II) PCI: 06:09:0: chip 1180,0476 card 4000,0000 rev b3 class 06,07,00 hdr 82
(II) PCI: 06:09:1: chip 1180,0552 card 144d,c01a rev 08 class 0c,00,10 hdr 80
(II) PCI: 06:09:2: chip 1180,0822 card 144d,c01a rev 17 class 08,05,00 hdr 80
(II) PCI: 06:09:3: chip 1180,0592 card 144d,c01a rev 08 class 08,80,00 hdr 80
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,7), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
   [0] -1   0   0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) Bus 0 non-prefetchable memory range:
   [0] -1   0   0x00000000 - 0xffffffff (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
   [0] -1   0   0x00000000 - 0xffffffff (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 2: bridge is at (0:28:0), (0,2,2), BCTRL: 0x0004 (VGA_EN is cleared)
(II) Bus 2 I/O range:
   [0] -1   0   0x00003000 - 0x000030ff (0x100) IX[B]
   [1] -1   0   0x00003400 - 0x000034ff (0x100) IX[B]
   [2] -1   0   0x00003800 - 0x000038ff (0x100) IX[B]
   [3] -1   0   0x00003c00 - 0x00003cff (0x100) IX[B]
(II) Bus 2 non-prefetchable memory range:
   [0] -1   0   0xb4000000 - 0xb7ffffff (0x4000000) MX[B]
(II) Bus 2 prefetchable memory range:
   [0] -1   0   0xd0000000 - 0xd3ffffff (0x4000000) MX[B]
(II) Subtractive PCI-to-PCI bridge:
(II) Bus 6: bridge is at (0:30:0), (0,6,6), BCTRL: 0x0004 (VGA_EN is cleared)
(II) Bus 6 I/O range:
   [0] -1   0   0x00004000 - 0x000040ff (0x100) IX[B]
   [1] -1   0   0x00004400 - 0x000044ff (0x100) IX[B]
   [2] -1   0   0x00004800 - 0x000048ff (0x100) IX[B]
   [3] -1   0   0x00004c00 - 0x00004cff (0x100) IX[B]
(II) Bus 6 non-prefetchable memory range:
   [0] -1   0   0xb8000000 - 0xb80fffff (0x100000) MX[B]
(II) Bus 6 prefetchable memory range:
   [0] -1   0   0x50000000 - 0x52ffffff (0x3000000) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(II) PCI-to-CardBus bridge:
(II) Bus 7: bridge is at (6:9:0), (6,7,10), BCTRL: 0x0700 (VGA_EN is cleared)
(II) Bus 7 I/O range:
   [0] -1   0   0x00004000 - 0x000040ff (0x100) IX[B]
   [1] -1   0   0x00004400 - 0x000044ff (0x100) IX[B]
(II) Bus 7 prefetchable memory range:
   [0] -1   0   0x50000000 - 0x51ffffff (0x2000000) MX[B]
(--) PCI:*(0:2:0) Intel Corp. unknown chipset (0x2592) rev 3, Mem @ 0xb0080000/19, 0xc0000000/28, 0xb0000000/18, I/O @ 0x1800/3
(--) PCI: (0:2:1) Intel Corp. unknown chipset (0x2792) rev 3, Mem @ 0x53000000/19
(II) Addressable bus resource ranges are
   [0] -1   0   0x00000000 - 0xffffffff (0x0) MX[B]
   [1] -1   0   0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:
   [0] -1   0   0xffe00000 - 0xffffffff (0x200000) MX[B](B)
   [1] -1   0   0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
   [2] -1   0   0x000f0000 - 0x000fffff (0x10000) MX[B]
   [3] -1   0   0x000c0000 - 0x000effff (0x30000) MX[B]
   [4] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX[B]
   [5] -1   0   0x0000ffff - 0x0000ffff (0x1) IX[B]
   [6] -1   0   0x00000000 - 0x000000ff (0x100) IX[B]
(II) Active PCI resource ranges:
   [0] -1   0   0xb8003c00 - 0xb8003cff (0x100) MX[B]
   [1] -1   0   0xb8003800 - 0xb80038ff (0x100) MX[B]
   [2] -1   0   0xb8003000 - 0xb80037ff (0x800) MX[B]
   [3] -1   0   0xb8002000 - 0xb8002fff (0x1000) MX[B]
   [4] -1   0   0xb8000000 - 0xb8001fff (0x2000) MX[B]
   [5] -1   0   0xb0040400 - 0xb00404ff (0x100) MX[B]
   [6] -1   0   0xb0040800 - 0xb00409ff (0x200) MX[B]
   [7] -1   0   0xb0040000 - 0xb00403ff (0x400) MX[B]
   [8] -1   0   0xb0000000 - 0xb003ffff (0x40000) MX[B](B)
   [9] -1   0   0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
   [10] -1   0   0xb0080000 - 0xb00fffff (0x80000) MX[B](B)
   [11] -1   0   0x000018a0 - 0x000018bf (0x20) IX[B]
   [12] -1   0   0x00001810 - 0x0000181f (0x10) IX[B]
   [13] -1   0   0x00002000 - 0x0000207f (0x80) IX[B]
   [14] -1   0   0x00002400 - 0x000024ff (0x100) IX[B]
   [15] -1   0   0x000018c0 - 0x000018ff (0x40) IX[B]
   [16] -1   0   0x00001c00 - 0x00001cff (0x100) IX[B]
   [17] -1   0   0x00001880 - 0x0000189f (0x20) IX[B]
   [18] -1   0   0x00001860 - 0x0000187f (0x20) IX[B]
   [19] -1   0   0x00001840 - 0x0000185f (0x20) IX[B]
   [20] -1   0   0x00001820 - 0x0000183f (0x20) IX[B]
   [21] -1   0   0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) Inactive PCI resource ranges:
   [0] -1   0   0x53000000 - 0x5307ffff (0x80000) MX[B](B)
(II) Active PCI resource ranges after removing overlaps:
   [0] -1   0   0xb8003c00 - 0xb8003cff (0x100) MX[B]
   [1] -1   0   0xb8003800 - 0xb80038ff (0x100) MX[B]
   [2] -1   0   0xb8003000 - 0xb80037ff (0x800) MX[B]
   [3] -1   0   0xb8002000 - 0xb8002fff (0x1000) MX[B]
   [4] -1   0   0xb8000000 - 0xb8001fff (0x2000) MX[B]
   [5] -1   0   0xb0040400 - 0xb00404ff (0x100) MX[B]
   [6] -1   0   0xb0040800 - 0xb00409ff (0x200) MX[B]
   [7] -1   0   0xb0040000 - 0xb00403ff (0x400) MX[B]
   [8] -1   0   0xb0000000 - 0xb003ffff (0x40000) MX[B](B)
   [9] -1   0   0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
   [10] -1   0   0xb0080000 - 0xb00fffff (0x80000) MX[B](B)
   [11] -1   0   0x000018a0 - 0x000018bf (0x20) IX[B]
   [12] -1   0   0x00001810 - 0x0000181f (0x10) IX[B]
   [13] -1   0   0x00002000 - 0x0000207f (0x80) IX[B]
   [14] -1   0   0x00002400 - 0x000024ff (0x100) IX[B]
   [15] -1   0   0x000018c0 - 0x000018ff (0x40) IX[B]
   [16] -1   0   0x00001c00 - 0x00001cff (0x100) IX[B]
   [17] -1   0   0x00001880 - 0x0000189f (0x20) IX[B]
   [18] -1   0   0x00001860 - 0x0000187f (0x20) IX[B]
   [19] -1   0   0x00001840 - 0x0000185f (0x20) IX[B]
   [20] -1   0   0x00001820 - 0x0000183f (0x20) IX[B]
   [21] -1   0   0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) Inactive PCI resource ranges after removing overlaps:
   [0] -1   0   0x53000000 - 0x5307ffff (0x80000) MX[B](B)
(II) OS-reported resource ranges after removing overlaps with PCI:
   [0] -1   0   0xffe00000 - 0xffffffff (0x200000) MX[B](B)
   [1] -1   0   0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
   [2] -1   0   0x000f0000 - 0x000fffff (0x10000) MX[B]
   [3] -1   0   0x000c0000 - 0x000effff (0x30000) MX[B]
   [4] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX[B]
   [5] -1   0   0x0000ffff - 0x0000ffff (0x1) IX[B]
   [6] -1   0   0x00000000 - 0x000000ff (0x100) IX[B]
(II) All system resource ranges:
   [0] -1   0   0xffe00000 - 0xffffffff (0x200000) MX[B](B)
   [1] -1   0   0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B)
   [2] -1   0   0x000f0000 - 0x000fffff (0x10000) MX[B]
   [3] -1   0   0x000c0000 - 0x000effff (0x30000) MX[B]
   [4] -1   0   0x00000000 - 0x0009ffff (0xa0000) MX[B]
   [5] -1   0   0xb8003c00 - 0xb8003cff (0x100) MX[B]
   [6] -1   0   0xb8003800 - 0xb80038ff (0x100) MX[B]
   [7] -1   0   0xb8003000 - 0xb80037ff (0x800) MX[B]
   [8] -1   0   0xb8002000 - 0xb8002fff (0x1000) MX[B]
   [9] -1   0   0xb8000000 - 0xb8001fff (0x2000) MX[B]
   [10] -1   0   0xb0040400 - 0xb00404ff (0x100) MX[B]
   [11] -1   0   0xb0040800 - 0xb00409ff (0x200) MX[B]
   [12] -1   0   0xb0040000 - 0xb00403ff (0x400) MX[B]
   [13] -1   0   0xb0000000 - 0xb003ffff (0x40000) MX[B](B)
   [14] -1   0   0xc0000000 - 0xcfffffff (0x10000000) MX[B](B)
   [15] -1   0   0xb0080000 - 0xb00fffff (0x80000) MX[B](B)
   [16] -1   0   0x53000000 - 0x5307ffff (0x80000) MX[B](B)
   [17] -1   0   0x0000ffff - 0x0000ffff (0x1) IX[B]
   [18] -1   0   0x00000000 - 0x000000ff (0x100) IX[B]
   [19] -1   0   0x000018a0 - 0x000018bf (0x20) IX[B]
   [20] -1   0   0x00001810 - 0x0000181f (0x10) IX[B]
   [21] -1   0   0x00002000 - 0x0000207f (0x80) IX[B]
   [22] -1   0   0x00002400 - 0x000024ff (0x100) IX[B]
   [23] -1   0   0x000018c0 - 0x000018ff (0x40) IX[B]
   [24] -1   0   0x00001c00 - 0x00001cff (0x100) IX[B]
   [25] -1   0   0x00001880 - 0x0000189f (0x20) IX[B]
   [26] -1   0   0x00001860 - 0x0000187f (0x20) IX[B]
   [27] -1   0   0x00001840 - 0x0000185f (0x20) IX[B]
   [28] -1   0   0x00001820 - 0x0000183f (0x20) IX[B]
   [29] -1   0   0x00001800 - 0x00001807 (0x8) IX[B](B)
(II) LoadModule: "glx"
(II) Loading /usr/lib/modules/extensions/libglx.a
(II) Module glx: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   ABI class: X.Org Server Extension, version 0.2
(II) Loading sub module "GLcore"
(II) LoadModule: "GLcore"
(II) Loading /usr/lib/modules/extensions/libGLcore.a
(II) Module GLcore: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   ABI class: X.Org Server Extension, version 0.2
(II) Loading extension GLX
(II) LoadModule: "extmod"
(II) Loading /usr/lib/modules/extensions/libextmod.a
(II) Module extmod: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 0.2
(II) Loading extension SHAPE
(II) Loading extension MIT-SUNDRY-NONSTANDARD
(II) Loading extension BIG-REQUESTS
(II) Loading extension SYNC
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XC-MISC
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension TOG-CUP
(II) Loading extension Extended-Visual-Information
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "xtrap"
(II) Loading /usr/lib/modules/extensions/libxtrap.a
(II) Module xtrap: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 0.2
(II) Loading extension DEC-XTRAP
(II) LoadModule: "record"
(II) Loading /usr/lib/modules/extensions/librecord.a
(II) Module record: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.13.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 0.2
(II) Loading extension RECORD
(II) LoadModule: "dri"
(II) Loading /usr/lib/modules/extensions/libdri.a
(II) Module dri: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   ABI class: X.Org Server Extension, version 0.2
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/modules/linux/libdrm.a
(II) Module drm: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   ABI class: X.Org Server Extension, version 0.2
(II) Loading extension XFree86-DRI
(II) LoadModule: "dbe"
(II) Loading /usr/lib/modules/extensions/libdbe.a
(II) Module dbe: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   Module class: X.Org Server Extension
   ABI class: X.Org Server Extension, version 0.2
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "freetype"
(II) Loading /usr/lib/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
   compiled for 6.8.2, module version = 2.1.0
   Module class: X.Org Font Renderer
   ABI class: X.Org Font Renderer, version 0.4
(II) Loading font FreeType
(II) LoadModule: "type1"
(II) Loading /usr/lib/modules/fonts/libtype1.a
(II) Module type1: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.2
   Module class: X.Org Font Renderer
   ABI class: X.Org Font Renderer, version 0.4
(II) Loading font Type1
(II) Loading font CID
(II) LoadModule: "i810"
(II) Loading /usr/lib/modules/drivers/i810_drv.o
(II) Module i810: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.3.0
   Module class: X.Org Video Driver
   ABI class: X.Org Video Driver, version 0.7
(II) LoadModule: "mouse"
(II) Loading /usr/lib/modules/input/mouse_drv.o
(II) Module mouse: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   Module class: X.Org XInput Driver
   ABI class: X.Org XInput driver, version 0.4
(II) LoadModule: "kbd"
(II) Loading /usr/lib/modules/input/kbd_drv.o
(II) Module kbd: vendor="X.Org Foundation"
   compiled for 6.8.2, module version = 1.0.0
   Module class: X.Org XInput Driver
   ABI class: X.Org XInput driver, version 0.4
(II) I810: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100,
   i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G
(II) Primary Device is: PCI 00:02:0
(--) Assigning device section with no busID to primary device
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(EE) No devices detected.

Fatal server error:
no screens found

Please consult the The X.Org Foundation support
    at http://wiki.X.Org
 for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.


My laptop is a Samsung X20 1730 V.

Now here is the strange part: When I simply replace /usr/X11R6/lib/modules/drivers/i810_drv.o with the binary provided by Alan Hourihane you can download at http://www.fairlite.demon.co.uk/intel.html the X-Server starts properly (without DRI though, glxgears gives around 300fps).

Do you have any suggestions what I should try to do? Do you think this is a kernel-side or an x-org-side problem? Has anyone gotten DRI to work an a Samsung X20? Which steps did exactly take and which versions are you using?

Thanks in advance, Christoph

Edit 1:
This could be interesting, too:
Code:
ct@spock ~ $ dmesg | grep -i agp
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 915GM Chipset.
agpgart: Detected 7932K stolen memory.
agpgart: AGP aperture is 256M @ 0xc0000000
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Fri Dec 02, 2005 2:37 pm    Post subject: Reply with quote

Hmmm... Strange as that error message is typically from 6.8.2. Under 6.8.99.x you should have
Code:
X Window System Version 6.8.99.15
Release Date: 16 July 2005 + cvs
X Protocol Version 11, Revision 0, Release 6.8.99.15
instead of
Code:
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2

which means you're actually running 6.8.2.x. Could you just check that?
Code:
$ equery l xorg-x11
[ Searching for package 'xorg-x11' in all categories among: ]
 * installed packages
[I--] [  ] x11-base/xorg-x11-6.8.99.15-r4 (0)

_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
c_t
n00b
n00b


Joined: 29 Oct 2003
Posts: 36
Location: Berlin, Germany

PostPosted: Fri Dec 02, 2005 2:53 pm    Post subject: Reply with quote

Yes your're right: Actually I'm running 6.8.2-r4, since with 6.8.99* replacing the driver with Alans Binary does not work.

But what I wanted to say: No matter whether I had 6.8.2 or 6.8.99 running, the error-messages which led to the server crash were the same! In both cases the server crashes with:
Code:
(--) Assigning device section with no busID to primary device
(WW) I810: No matching Device section for instance (BusID PCI:0:2:1) found
(EE) No devices detected.

Fatal server error:
no screens found


Edit 1:
I'd be glad if someone could simply mention his combination of kernel-/xorg-versions that currently DO work (including kernel-settings and xorg.conf please)...
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Fri Dec 02, 2005 9:18 pm    Post subject: Reply with quote

Would you mind following the steps for Samsung X20, I think this is exactly what you need. Then post your results.

I also found that link; it is for Debian but can easily be adapted to Gentoo. The link to broadcom drivers for Linux is broken but here it is: http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php .
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
liljohn118th
n00b
n00b


Joined: 31 Aug 2005
Posts: 7

PostPosted: Sun Dec 04, 2005 4:15 pm    Post subject: Reply with quote

Code:
localhost brian # glxinfo|grep direct
direct rendering: Yes
8)

I bow to you, good sir!!! Thank you so much for the help!
Back to top
View user's profile Send private message
c_t
n00b
n00b


Joined: 29 Oct 2003
Posts: 36
Location: Berlin, Germany

PostPosted: Wed Dec 07, 2005 5:48 pm    Post subject: Reply with quote

VinzC wrote:
Would you mind following the steps for Samsung X20, I think this is exactly what you need. Then post your results.

OK, I now followed once again all steps described in the wiki. I was trying it with the following versions:
Kernel: gentoo-sources-2.6.12-r10
Xorg: xorg-x11-6.8.99.15-r4

My xorg.conf is the one from the wiki. I even completely uninstalled X bevor merging xorg-x11.

I have patched the xorg-ebuild as described in this howto. When I now startx I get this Xorg.0.log:
Xorg.0.log
All the zeros where X tries to find out the valid modes are a bit strange, arent they?

Can anyone explain this? Thanks, Christoph

Edit 1:
Also without the patch I get similar errors. In any case the server refuses to start with the errormessage
Code:
Fatal server error:
no screens found

The only way I've got X working by now was by emerging xorg-x11-6.8.2-r4 and then replacing /usr/lib/modules/drivers/i810_drv.o with the binary from http://www.fairlite.demon.co.uk/intel.html
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Mon Dec 12, 2005 8:57 pm    Post subject: Reply with quote

c_t wrote:
I have patched the xorg-ebuild as described in this howto. When I now startx I get this Xorg.0.log:
Xorg.0.log
All the zeros where X tries to find out the valid modes are a bit strange, arent they?

These zeroes aren't special nor abnormal. I have them too but Xorg works like a charm indeed. I have no explanation on why it wouldn't on yours. Maybe you can try a newer kernel, e.g. vanilla sources 2.6.15-rc[45]. Maybe it's a hardware/driver issue.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
skroll
n00b
n00b


Joined: 13 Dec 2005
Posts: 2

PostPosted: Tue Dec 13, 2005 3:03 am    Post subject: Reply with quote

Figure I would chime in and say that I too managed to get DRI working with modular Xorg (7.0 rc2). I know it's a masked package, however, it worked right out of the box (compile) without any work. I simply had the I915 DRM driver compiled in the kernel, and it worked 100%.
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Tue Dec 13, 2005 6:18 am    Post subject: Reply with quote

skroll wrote:
Figure I would chime in and say that I too managed to get DRI working with modular Xorg (7.0 rc2). I know it's a masked package, however, it worked right out of the box (compile) without any work. I simply had the I915 DRM driver compiled in the kernel, and it worked 100%.

That indeed sounds promising. Many people have reported it works well. I'll update the howto as soon as Xorg gets unmasked (or I get bored waiting ;-) )
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
mr2600
n00b
n00b


Joined: 22 Feb 2004
Posts: 54
Location: Florida

PostPosted: Wed Dec 14, 2005 6:45 pm    Post subject: Reply with quote

Ok I'm stuck.

I got everything working except direct rendering under glxinfo... very puzzled.

Code:
penguin ~ # glxinfo
name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.3.0 i915 (screen 0)
libGL: OpenDriver: trying /usr/lib/modules/dri/i915_dri.so
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 4, (OK)
drmOpenByBusid: drmOpenMinor returns 4
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
Unrecognized deviceID 2772
display: :0  screen: 0
direct rendering: No
... snip ...
OpenGL vendor string: Mesa project: www.mesa3d.org
OpenGL renderer string: Mesa GLX Indirect
OpenGL version string: 1.2 (1.5 Mesa 6.2.1)


Code:
penguin ~ # cat /var/log/Xorg.0.log | grep drm
(II) Loading sub module "drm"
(II) LoadModule: "drm"
(II) Loading /usr/lib/modules/linux/libdrm.so
(II) Module drm: vendor="X.Org Foundation"
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)
drmOpenByBusid: drmOpenMinor returns 6
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) I810(0): [drm] DRM interface version 1.2
(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"
(II) I810(0): [drm] added 8192 byte SAREA at 0xf939f000
(II) I810(0): [drm] mapped SAREA 0xf939f000 to 0xb7cf4000
(II) I810(0): [drm] framebuffer handle = 0xe0020000
(II) I810(0): [drm] added 1 reserved context for kernel
(II) I810(0): [drm] Registers = 0xfeb00000
(II) I810(0): [drm] Back Buffer = 0xef800000
(II) I810(0): [drm] Depth Buffer = 0xef400000
(II) I810(0): [drm] ring buffer = 0xe0000000
(II) I810(0): [drm] textures = 0xe05a0000
(II) I810(0): [drm] dma control initialized, using IRQ 16
(II) I810(0): [drm] Initialized kernel agp heap manager, 119537664
(II) I810(0): [drm] installed DRM signal handler


Code:
penguin ~ # cat /var/log/Xorg.0.log | grep dri
        X.Org XInput driver : 0.4
(II) Loading /usr/lib/modules/drivers/i810_drv.so
        ABI class: X.Org XInput driver, version 0.4
        ABI class: X.Org XInput driver, version 0.4
(II) Loading sub module "dri"
(II) LoadModule: "dri"
(II) Loading /usr/lib/modules/extensions/libdri.so
(II) Module dri: vendor="X.Org Foundation"
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: node name is /dev/dri/card0
(II) I810(0): [drm] created "i915" driver at busid "pci:0000:00:02.0"
(II) I810(0): [dri] visual configs initialized


And finally my xorg.conf...
Code:

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

# **********************************************************************
# 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.
        Load    "extmod"
        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"
#       Load    "drm"

EndSection

... blah blah blah ...

# Section "Monitor"
        #DisplaySize      340   270     # mm
        Identifier      "DELL 1706FPV"
        VendorName      "DELL"
        ModelName       "DELL 1706FPV"
        HorizSync       31.0 - 80.0
        VertRefresh     56.0 - 75.0
        Option          "DPMS"  "true"
EndSection

Section "Device"
        #For troubleshooting
        #Option          "mtrr"          "off"

        Identifier      "GMA 950 DRI"
        Driver          "i810"
        VendorName      "Intel Corp."
        BoardName       "Intel i945 GMA 950 Graphics"
        BusID           "PCI:0:2:0"
        VideoRam        131070
        Option          "NoAccel"       "false"
        Option          "DRI"           "true"
        Option          "XVideo"        "true"
        Option          "VBERestore"    "true"

        #Option  "AGPMode"               "4"
        #Option  "EnablePageFlip"        "True"
        #Option  "IgnoreEDID"            "off"
EndSection

Section "Device"
        Identifier "GMA 950 VESA"
        Driver "vesa"
        # BusID "PCI:0:2:0"
        # VideoRam 32768
EndSection

Section "Screen"
        Identifier "Screen0"
        Device     "GMA 950 DRI"
        Monitor    "DELL 1706FPV"
        DefaultDepth 16

        Subsection "Display"
                Depth       16
                Modes       "1280x1024"
                ViewPort    0 0
        EndSubsection
EndSection

Section "DRI"
    Mode 0666
EndSection


Yes the dri module is commented out because the log complains its trying to load twice if I have dri loaded there and in the Device section the Option "DRI" "true" also being there.

I really have no idea what I'm doing wrong. I used to have this work fine on a slightly older computer (with i915 instead of the newer i945) without even needing the drm patch!

EDIT: I dont think this is very good... If I try to run one of those opengl xscreensaver hacks (like say 'queens') I get this error on the console...
Code:
Unrecognized deviceID 2772
[/code]
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Thu Dec 15, 2005 6:27 am    Post subject: Reply with quote

Try first without the DRI Option (I don't have it), only loading DRI module with Load "dri".
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
purple_monkey
n00b
n00b


Joined: 10 Nov 2005
Posts: 26

PostPosted: Fri Dec 16, 2005 2:12 am    Post subject: Reply with quote

Xorg 7 solved all the problems on my Asus Z33A. I built all the i810 drivers into my kernel (gentoo-sources-2.6.14-r4) including i915 support.

:D

I installed it by following the instructions at http://gentoo-wiki.com/HOWTO_Modular_Xorg. It was a simple procedure, taking less than an hour from start to finish (including compile time).

FYI, I had a problem with the synaptics touchpad driver. X7 looks for it in the wrong place. This can be solved with the following:
Code:
# ln -s /usr/lib/modules/input/synaptics_drv.so /usr/lib/xorg/modules/input/synaptics_drv.so


[Or by getting a more recent version of the synaptics driver - Thanks c_t]

Good luck!


Last edited by purple_monkey on Wed Dec 21, 2005 11:28 pm; edited 1 time in total
Back to top
View user's profile Send private message
c_t
n00b
n00b


Joined: 29 Oct 2003
Posts: 36
Location: Berlin, Germany

PostPosted: Wed Dec 21, 2005 9:07 pm    Post subject: Reply with quote

purple_monkey wrote:
Xorg 7 solved all the problems on my Asus Z33A. I built all the i810 drivers into my kernel (gentoo-sources-2.6.14-r4) including i915 support.

:D

I installed it by following the instructions at http://gentoo-wiki.com/HOWTO_Modular_Xorg. It was a simple procedure, taking less than an hour from start to finish including compile time).

FYI, I had a problem with the synaptics touchpad driver. X7 looks for it in the wrong place. This can be solved with the following:
Code:
# ln -s /usr/lib/modules/input/synaptics_drv.so /usr/lib/xorg/modules/input/synaptics_drv.so

Thanks purple_monkey anall other guys in this Forum! Installing Modular Xorg (7.0.0_RC4) and the synaptics-symlink solved any problems on my Samsung X20 1730 V. Now I get
Code:
spock ~ # glxinfo | grep direct
direct rendering: Yes
spock ~ # glxgears
9880 frames in 5.0 seconds = 1975.806 FPS

Whoooohaaaw, this rocks! (16 Bits Depth though...)

Edit: @purple_monkey: I know this is OT but simply updating synaptics to the most recent version (0.14.4-r2) makes creating a symlink obsolete since synaptics gets installed to /usr/lib/xorg/modules/input now.

Edit 2: FYI: My kernel is gentoo-sources-2.6.14-r4 with DRM for i915 enabled. With 24 Bits Depth I get 1311.949 FPS.
Back to top
View user's profile Send private message
portman
n00b
n00b


Joined: 18 Aug 2005
Posts: 2

PostPosted: Thu Dec 22, 2005 6:10 am    Post subject: Reply with quote

thx guyz for this great info I'm getting right now :
portman@thinkpad ~ $ glxinfo | grep direct
direct rendering: Yes
portman@thinkpad ~ $ glxgears
8890 frames in 5.0 seconds = 1777.853 FPS
8539 frames in 5.0 seconds = 1707.725 FPS
8550 frames in 5.0 seconds = 1709.916 FPS
8545 frames in 5.0 seconds = 1708.918 FPS
8549 frames in 5.0 seconds = 1709.788 FPS
8545 frames in 5.0 seconds = 1708.987 FPS
8671 frames in 5.0 seconds = 1734.173 FPS
20860 frames in 5.0 seconds = 4171.999 FPS
20878 frames in 5.0 seconds = 4175.529 FPS
10980 frames in 5.0 seconds = 2194.860 FPS



before I just had an ~400 fps :S
now it ROCKS!!!! and finally I can play quake3-western :D on my ibm thinkpad t43 :>
of course I'm using kernel 2.6.14 vanilla without any patches ;]
Back to top
View user's profile Send private message
sclark
n00b
n00b


Joined: 25 Dec 2005
Posts: 1

PostPosted: Sun Dec 25, 2005 9:27 pm    Post subject: Reply with quote

confirmed that this patch helped on my IBM Z60T laptop as well.

In 24 color support at least I went from 500fps to 1100fps.

Thanks for the information and saved debugging time :D
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Wed Dec 28, 2005 10:09 pm    Post subject: Reply with quote

c_t wrote:
...
Thanks purple_monkey anall other guys in this Forum! Installing Modular Xorg (7.0.0_RC4) and the synaptics-symlink solved any problems on my Samsung X20 1730 V. Now I get
Code:
spock ~ # glxinfo | grep direct
direct rendering: Yes
spock ~ # glxgears
9880 frames in 5.0 seconds = 1975.806 FPS

Glad you solved all your issues. Just out of curiosity, could you post the result of this command:
Code:
grep -i vesa /var/log/Xorg.0.log

_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
AngryLlama
Tux's lil' helper
Tux's lil' helper


Joined: 30 Sep 2004
Posts: 111

PostPosted: Sun Jan 01, 2006 12:23 am    Post subject: Reply with quote

First, Thanks to everyone for the valuable information in this HOWTO. I also suffer from the i915GM chipset on my Dell B130 laptop. Following the directions in the original post brought my glxgears from ~400FPS to over 1100FPS. Unfortunately, that was not my main concern. I would like to take advantage of my wide screen; I'm running 1024x768 on a 1280x800 screen. I cannot, for the life of me, figure out how to run at my native resolution -- in console or X11 for that matter.

Some information on my setup:
Kernel: gentoo-2.6.14-r5
X: xorg-x11-6.8.99.15-r4
I am running the i915 driver built in to the kernel.
I have tried both vesa and vesa-tng

my xorg.conf:
Code:
Section "ServerLayout"
   Identifier     "X.org Configured"
   Screen      0  "Screen0" 0 0
   InputDevice    "Mouse0" "CorePointer"
   InputDevice    "TouchPad" "AlwaysCore"
   InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

Section "Files"
   RgbPath      "/usr/lib/X11/rgb"
   ModulePath   "/usr/lib/modules"
   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/"
EndSection

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

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

Section "InputDevice"
   Identifier  "Mouse0"
   Driver      "mouse"
   Option       "Protocol" "auto"
   Option       "Device" "/dev/input/mouse0"
EndSection

Section "InputDevice"
   Driver      "synaptics"
   Identifier  "TouchPad"
   Option       "Device"     "/dev/input/mouse0"
   Option       "Protocol"   "auto-dev"
   Option       "LeftEdge"      "1700"
   Option       "RightEdge"     "5000"
   Option       "TopEdge"       "1700"
   Option       "BottomEdge"    "4200"
   Option       "FingerLow"      "25"
   Option       "FingerHigh"   "30"
   Option       "MaxTapTime"   "180"
   Option       "MaxTapMove"   "220"
   Option       "VertScrollDelta"    "100"
   Option       "MinSpeed"      "0.09"
   Option       "MaxSpeed"      "0.18"
   Option       "AccelFactor"   "0.0015"
   Option      "PalmMinWidth"    "70"
   Option      "PalmMinZ"       "200"
   Option       "SHMConfig"      "on"
EndSection

Section "Monitor"
   Identifier   "Monitor0"
   VendorName   "Monitor Vendor"
   ModelName    "Monitor Model"
   Option       "FlatPanelProperties" "Scaling=Centered"
   #UseModes     "16:10"
        #ModeLine    "1280x800"  70 1280 1328 1440 1688  800 801 804 842
        #I've tried about 20 other 1280x800 mode lines, with no luck.

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     "ShadowFB"              # [<bool>]
        #Option     "DefaultRefresh"        # [<bool>]
   Identifier  "Card0"
   Driver      "i810"
   VendorName  "Intel Corp."
   BoardName   "Unknown Board"
   BusID       "PCI:0:2:0"
   Option        "NoAccel" "false"
   Option        "DRI" "true"
        Option        "XVideo" "true"
   Option        "VBERestore" "true"
   VideoRam      131072   
EndSection

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

Section "DRI"
   Mode  0666
EndSection


My vbetest doesn't even show the resolution!
Code:

# vbetest
VBE Version 3.0
Intel(r)915GM/910ML/915MS Graphics Chip Accelerated VGA BIOS
[261] 1024x768 (256 color palette)
[279] 1024x768 (5:6:5)
[280] 1024x768 (8:8:8)
[274] 640x480 (8:8:8)
[276] 800x600 (5:6:5)
[277] 800x600 (8:8:8)
[257] 640x480 (256 color palette)
[259] 800x600 (256 color palette)
[273] 640x480 (5:6:5)


Any ideas? Anything I can check? Thanks in advance.
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Sun Jan 01, 2006 12:50 am    Post subject: Reply with quote

AngryLlama wrote:
First, Thanks to everyone for the valuable information in this HOWTO. I also suffer from the i915GM chipset on my Dell B130 laptop. Following the directions in the original post brought my glxgears from ~400FPS to over 1100FPS. Unfortunately, that was not my main concern. I would like to take advantage of my wide screen; I'm running 1024x768 on a 1280x800 screen. I cannot, for the life of me, figure out how to run at my native resolution -- in console or X11 for that matter.
...
Any ideas? Anything I can check? Thanks in advance.

There are a few things you might try:
  • Upgrade your BIOS - Dell regularly ships new BIOSes with bug fixes aso
  • Use masked kernels (e.g. vanilla sources 2.6.15.x series)

Here are the modes I have for 1280x800:
Code:
[355] 1280x800 (256 color palette)
[356] 1280x800 (5:6:5)
[357] 1280x800 (8:8:8)

They might not work at all since I trust vbetest to read values returned by your video BIOS.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
AngryLlama
Tux's lil' helper
Tux's lil' helper


Joined: 30 Sep 2004
Posts: 111

PostPosted: Sun Jan 01, 2006 1:18 am    Post subject: Reply with quote

I was really excited about the possibility of the BIOS being the problem. Unfortunately, I have the latest revision. In addition, Windows runs in widescreen just fine. If I try using a masked kernel, then I will need to reapply the dri patch, correct? If vbetest reads straight from the BIOS then I don't see how the kernel would fix the problem. I'll try it out anyways... :cry:
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Sun Jan 01, 2006 1:32 am    Post subject: Reply with quote

AngryLlama wrote:
I was really excited about the possibility of the BIOS being the problem. Unfortunately, I have the latest revision.

Ow, too bad. Anyway stay tuned for further BIOS revisions.

AngryLlama wrote:
In addition, Windows runs in widescreen just fine.

That's one of the regular frustrations :? . I'm sure Windows uses (what I'd call) native modes of this chipset instead of VESA - which Xorg uses. And this is also why I'm asking so many times people who have tried the latest Xorg versions to see if the new i915 support now still uses Vesa or native modes...

AngryLlama wrote:
If I try using a masked kernel, then I will need to reapply the dri patch, correct?

No, fortunately. The patch applies to Xorg itself, not the kernel.

AngryLlama wrote:
If vbetest reads straight from the BIOS then I don't see how the kernel would fix the problem. I'll try it out anyways... :cry:

Because recent kernels have better support for i915. They might include patches that previous versions didn't. I hope so ;) .
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
AngryLlama
Tux's lil' helper
Tux's lil' helper


Joined: 30 Sep 2004
Posts: 111

PostPosted: Sun Jan 01, 2006 2:31 am    Post subject: Reply with quote

Just setup 2.6.15_rc7. No luck, vbetest shows the same screen modes and X still comes up in 1024x768. I guess Linux just doesn't support my laptop. Is there anything I can do to expedite support for my cheap laptop? :x

Has anyone tried Intel's driver located at: http://downloadfinder.intel.com/scripts-df-external/filter_results.aspx?strTypes=all&ProductID=1862&OSFullName=Linux*&lang=eng&strOSs=39&submit=Go%21
Back to top
View user's profile Send private message
ExZombie
Apprentice
Apprentice


Joined: 29 May 2004
Posts: 164

PostPosted: Sun Jan 01, 2006 9:46 am    Post subject: Reply with quote

My BIOS doesn't have correct modes for my screen also. I solved the problem with 855resolution. I simply set it to overwrite an unused resolution with my screen's native resolution and voila - xorg can now use it. I haven't tried framebuffer, but it might work, though not at boot time, since changes 855resolution makes are not permanent.
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Sun Jan 01, 2006 11:14 am    Post subject: Reply with quote

AngryLlama wrote:
Just setup 2.6.15_rc7. No luck, vbetest shows the same screen modes and X still comes up in 1024x768. I guess Linux just doesn't support my laptop. Is there anything I can do to expedite support for my cheap laptop? :x

Has anyone tried Intel's driver located at: http://downloadfinder.intel.com/scripts-df-external/filter_results.aspx?strTypes=all&ProductID=1862&OSFullName=Linux*&lang=eng&strOSs=39&submit=Go%21

Have you tried one of the video modes I indicated? All you could get at worst is an error message "unsupported video mode"...
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
AngryLlama
Tux's lil' helper
Tux's lil' helper


Joined: 30 Sep 2004
Posts: 111

PostPosted: Sun Jan 01, 2006 6:53 pm    Post subject: Reply with quote

VinzC wrote:
Have you tried one of the video modes I indicated? All you could get at worst is an error message "unsupported video mode"...

Yes, I tried those modes and I tried converting them to hex and adding 200h to them. They all cause "unsupported video mode". What's even more strange is none of my modes from vbetest work either. Apparantly the only thing setting my console video mode is the VESA default mode (FB_VESA_DEFAULT_MODE) option in the kernel. I do have VIDEO_SELECT=y.
Back to top
View user's profile Send private message
VinzC
Watchman
Watchman


Joined: 17 Apr 2004
Posts: 5021
Location: Dark side of the mood

PostPosted: Sun Jan 01, 2006 10:28 pm    Post subject: Reply with quote

AngryLlama wrote:
What's even more strange is none of my modes from vbetest work either. Apparantly the only thing setting my console video mode is the VESA default mode (FB_VESA_DEFAULT_MODE) option in the kernel. I do have VIDEO_SELECT=y.

It looks like you have enabled VESA-TNG instead of VESAFB. Follow the guide http://gentoo-wiki.com/HOWTO_fbsplash again but enable VESAFB instead.
_________________
Gentoo addict: tomorrow I quit, I promise!... Just one more emerge...
1739!
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Documentation, Tips & Tricks All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
Page 6 of 8

 
Jump to:  
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