855GM and DRI support - confused

[the_enigma]

Ok, I'm sure I've done something silly, but here goes.
I've got a Thinkpad R51 with an inbuilt 855GM video adapter. It works, but I don't have direct rendering as reported by glxinfo. Here's what I do have:
AGP support as module (intel-agp) - shows up as

Code: Select all

agpgart: Detected an Intel 855 Chipset.

in dmesg
DRM support for i915 (i915) - shows up as

Code: Select all

[drm] Initialized i915 1.1.0 20040405 on minor 0: Intel Corp. 82852/855GM Integrated Graphics Device
[drm] Initialized i915 1.1.0 20040405 on minor 1: Intel Corp. 82852/855GM Integrated Graphics Device (#2)

in dmesg.
I get a total of 9 WW-style warnings in Xorg.0.log. 4 of those are fonts directories being non-existant. One is /dev/apm_bios non-existant, because I didn't compile support for it. Then I get the following for i810 (the Xorg driver)

Code: Select all

(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Bad V_BIOS checksum
(WW) I810(0): Not attempting to override default refresh on non-CRT clone head

None of that looks bad, right?

Code: Select all

enigma@delta /var/log $ cat Xorg.0.log | grep direct\ rendering
(II) I810(0): direct rendering: Enabled

Hey, that looks right ...

Code: Select all

enigma@delta /var/log $ DISPLAY=:0 LIBGL_DEBUG=verbose glxinfo  | head -n 3
libGL: XF86DRIGetClientDriverName: 1.3.0 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/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
name of display: :0.0
display: :0  screen: 0
direct rendering: No

There's my 'what the'.
I can't find any errors or warnings about DRI/DRM or anything. glxgears gets me ~200fps in a small window. I've everything I can think of and I still can't find any details.
Here are some links to some more debugging stuff:
Xorg.0.log
xorg.conf
dmesg output
.config file

Anyone have any ideas?
Anyone know anything I could try to get DRI working?

[the_enigma]

Been working on something on IRC maybe, but probably not.
I've tried adding VideoRam settings in xorg.conf. Both 32mb and 64mb don't change anything.
I've tried changing the depth from 24bit to 16bit. No luck.

[Logge]

Hi...

You and I got similar HW. I'm giving it a shot to help you out here...

I saw something in your xorg.conf looking like this:

Code: Select all

Section "Device"
	Identifier "Intel Extreme 1"
	VendorName "Intel"
	Driver "i810"
	BusId "PCI:0:2:0"
	Screen 0
	Option "MonitorLayout" "LFP,CRT"
	Option "Clone" "On"
	Option "DevicePresence" "On"
EndSection

(Maybe You should rethink the conf about the USB-mouse entries in your xorg.conf - they seem to give You errors...)

Try changing it to:

Code: Select all

Section "Device"
	Identifier "Intel Extreme 1"
	VendorName "Intel"
	Driver "i810"
	BusId "PCI:0:2:0"
EndSection

You should also edit your kernel-config from:

Code: Select all

#
# Ftape, the floppy tape device driver
#
# CONFIG_DRM_I810 is not set
CONFIG_DRM_I830=m
CONFIG_DRM_I915=m

to:

Code: Select all

#
# Ftape, the floppy tape device driver
#
CONFIG_DRM_I810=y
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=y

I personally don't like using modules thereby the =y. Shouldn't make any difference - use whatever.

After doing these steps - reboot new kernel/ load correct modules and try to restart xorg.

[the_enigma]

Hi...

You and I got similar HW. I'm giving it a shot to help you out here...

I saw something in your xorg.conf looking like this:
-snip-
I personally don't like using modules thereby the =y. Shouldn't make any difference - use whatever.

After doing these steps - reboot new kernel/ load correct modules and try to restart xorg.

Ok, I'll try the xorg.conf part now. The USB mouse errors are only because I have a mouse which I occasionally use. The way it's set up with the mice now means it starts/stops working when I plug/unplug it, without having to change anything. And I can't see how it could affect the video anyway. As to the module thing, the i830 module never gets used, so it should be the same, but I'll try that as well.

[Logge]

Im with you about the mouse, but still - an error is an error... In this case it shouldn't mess with the display though...

Tell Us if You fix the problem of yours...

//Logge

[the_enigma]

I changed my xorg.conf, but that didn't change one thing. I'm just going to wait for the next Xorg and see what that does.

[torshind]

I changed my xorg.conf, but that didn't change one thing. I'm just going to wait for the next Xorg and see what that does.

Have you checked permissions on /dev/dri/card*?

[Logge]

Hmm... I was thinkin'...

Are You a member of the group "video" on Your system???

'Cause I can't find anything wrong acctually...

Did you change your kernel-config to

<*> Intel I810
<*> Intel 830M, 845G, 852GM, 855GM, 865G (i915 driver) --->

Under Location:
-> Device Drivers
-> Character devices
-> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)


// Logge

[the_enigma]

Yes I am in the group 'video'
I'm yet to try the kernel config change, I'll try that next

[torshind]

Yes I am in the group 'video'
I'm yet to try the kernel config change, I'll try that next

I have the same chipset; udev sometimes set /dev/dri/card0 in the root group, perhaps you have the same problem.

[the_enigma]

Torshind .. you are right. card0 is owned by root:root.
But the perms on it are 666, aka everyone has read/write access.

Just tried with that new kernel config, no luck still.
Btw, why do you enable the i810 driver? Yes I did enable it so I could copy your config, but the i855 uses the i915 driver, the i810 doesn't get touched.

[Logge]

The I810-driver made some difference for me somehow...

What about re-emerging xorg??

[the_enigma]

Emerged 6.8.2 only a few days ago, after moving to ~x86. Might try that though.

[the_enigma]

Just bumping this to see if anyone has any ideas.

I've now tested with starting X as root, didn't change anything.
I've also tried emerging xorg as ~x86, which used 6.8.99. That didn't help either, so I moved back to 6.8.2.
So I'm running out of ideas real fast, and I really want to play TuxRacer. Anyone?

[zieloo]

The following setup works for me (at last):
xorg.conf:

Code: Select all

Section "Module"
    SubSection  "extmod"
              #  Option    "omit xfree86-dga"
    EndSubSection
Load     "dri"
Load	"GLcore"
Load	"glx"
EndSection 

Code: Select all

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

Chipset		"i915"
#  Driver     "i810"
    Driver	"i915"

Code: Select all

Section "Device"
	Identifier  "video"
	Driver      "i810"
	VideoRam    32768
	Option      "NoAccel"       "false"
        Option      "DRI"           "true"
EndSection

Code: Select all

Section "dri"
	Group        0
	Mode         0666
EndSection

Looking at your files I didn't notice anything exceptional, looks as if everything is ok...
However I did notice the lack of Section "dri" in your xorg.conf...

Could you post a complete output of glxinfo? What kernel are you using, btw? I'm also experiencing weird problems with the modules (2.6.11-ck8), but it's too soon to say something concrete...

[the_enigma]

Using 2.6.11-rc4-love1
My DRI section is actually up top of the xorg.conf file

I'll try that i915 driver though, see if that makes any difference.

My full glxinfo

Code: Select all

name of display: :0.0
libGL: XF86DRIGetClientDriverName: 1.3.0 i915 (screen 0)
libGL: OpenDriver: trying /usr/X11R6/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
display: :0  screen: 0
direct rendering: No
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:
    GLX_ARB_multisample, GLX_EXT_visual_info, GLX_EXT_visual_rating, 
    GLX_EXT_import_context, GLX_OML_swap_method, GLX_SGI_make_current_read, 
    GLX_SGIS_multisample, GLX_SGIX_fbconfig
client glx vendor string: SGI
client glx version string: 1.2
client glx extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_MESA_swap_control, GLX_MESA_swap_frame_usage, GLX_OML_swap_method, 
    GLX_OML_sync_control, GLX_SGI_make_current_read, GLX_SGI_swap_control, 
    GLX_SGI_video_sync, GLX_SGIS_multisample, GLX_SGIX_fbconfig, 
    GLX_SGIX_visual_select_group
GLX extensions:
    GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, 
    GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_allocate_memory, 
    GLX_SGI_make_current_read, GLX_SGIS_multisample
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)
OpenGL extensions:
    GL_ARB_depth_texture, GL_ARB_imaging, GL_ARB_multitexture, 
    GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow, 
    GL_ARB_shadow_ambient, GL_ARB_texture_border_clamp, 
    GL_ARB_texture_cube_map, GL_ARB_texture_env_add, 
    GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, 
    GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, 
    GL_ARB_transpose_matrix, GL_ARB_window_pos, GL_EXT_abgr, GL_EXT_bgra, 
    GL_EXT_blend_color, GL_EXT_blend_func_separate, GL_EXT_blend_logic_op, 
    GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_clip_volume_hint, 
    GL_EXT_copy_texture, GL_EXT_draw_range_elements, GL_EXT_fog_coord, 
    GL_EXT_multi_draw_arrays, GL_EXT_packed_pixels, GL_EXT_polygon_offset, 
    GL_EXT_rescale_normal, GL_EXT_secondary_color, 
    GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, 
    GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_subtexture, 
    GL_EXT_texture, GL_EXT_texture3D, GL_EXT_texture_edge_clamp, 
    GL_EXT_texture_env_add, GL_EXT_texture_env_combine, 
    GL_EXT_texture_env_dot3, GL_EXT_texture_lod_bias, GL_EXT_texture_object, 
    GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_APPLE_packed_pixels, 
    GL_ATI_texture_mirror_once, GL_ATI_texture_env_combine3, 
    GL_IBM_texture_mirrored_repeat, GL_MESA_pack_invert, 
    GL_MESA_ycbcr_texture, GL_NV_blend_square, GL_NV_point_sprite, 
    GL_NV_texgen_reflection, GL_NV_texture_rectangle, GL_SGIS_generate_mipmap, 
    GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, 
    GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, 
    GL_SGIX_shadow_ambient
glu version: 1.3
glu extensions:
    GLU_EXT_nurbs_tessellator, GLU_EXT_object_space_tess

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
0x22 24 tc  0 32  0 r  y  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
0x23 24 tc  0 32  0 r  .  .  8  8  8  8  0  0  0  0  0  0  0  0 0 None
0x24 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x25 24 tc  0 32  0 r  .  .  8  8  8  8  0 24  8  0  0  0  0  0 0 None
0x26 24 tc  0 32  0 r  y  .  8  8  8  8  0  0  0 16 16 16 16  0 0 Slow
0x27 24 tc  0 32  0 r  .  .  8  8  8  8  0  0  0 16 16 16 16  0 0 Slow
0x28 24 tc  0 32  0 r  y  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow
0x29 24 tc  0 32  0 r  .  .  8  8  8  8  0 24  8 16 16 16 16  0 0 Slow

[zieloo]

Using 2.6.11-rc4-love1
My DRI section is actually up top of the xorg.conf file
I'll try that i915 driver though, see if that makes any difference.

i915 seems to solve many xorg-related problems (at least for me:P). If don't like using it - switch back to XFree (nothing like that happened there...) , unless you use all those 'outstanding' xorg-addons.

[the_enigma]

I might've missed something here, but using the i915 driver gives me

Code: Select all

(II) LoadModule: "i915"
(WW) Warning, couldn't open module i915
(II) UnloadModule: "i915"
(EE) Failed to load module "i915" (module does not exist, 0)

Is there a special USE flag or something to build this? I've got the i915 driver enabled in my .config file, and it's built into my kernel, same as the i810, but I dunno if Xorg needs to build it as well.

[zieloo]

I might've missed something here, but using the i915 driver gives me

Code: Select all

(II) LoadModule: "i915"
(WW) Warning, couldn't open module i915
(II) UnloadModule: "i915"
(EE) Failed to load module "i915" (module does not exist, 0)

Is there a special USE flag or something to build this? I've got the i915 driver enabled in my .config file, and it's built into my kernel, same as the i810, but I dunno if Xorg needs to build it as well.

Check (and possibly post a part of) you kernel config. It obviously lacks of the module so it's not got created. Did you 'make modules_install"?:P

[ihtruelsen]

What I had to do, using similar hardware, was to load the i915 module at boot and use the i810 module in xorg.conf. I don't know why, but this gives me direct rendering.

YMMV

[the_enigma]

.config

Code: Select all

CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=y
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=y

So they're compiled in ...
Should I try using them as modules?
Do I need the DRM_I810 at all, or just DRM_I915?

Ok, I just tried with

Code: Select all

CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=m
# CONFIG_DRM_I830 is not set
CONFIG_DRM_I915=m

I loaded the module fine, but Xorg still failed to start, couldn't find module
Now it looks like Xorg is looking for the driver in /usr/lib/modules, which makes sense.
So I'm pretty sure that I'm meant to have Driver "i810".
I just can't work out why Xorg.0.log says

Code: Select all

(II) I810(0): direct rendering: Enabled

but glxinfo says

Code: Select all

direct rendering: No

.
That's the real annoying part. Seems like Xorg is finding/using DRI fine, but OpenGL isn't.

Edit: I also tried playing with the Chipset option. But I couldn't find anything that the driver supported, I think that option isn't supported at all, given 'man i810' doesn't mention it.

[zieloo]

What I've got in the kernel is:

Code: Select all

Graphics Support ->
[*] Intel 810/815 support (EXPERIMENTAL)
[*] Intel 830M/845G/852GM/855GM/865G support (EXPERIMENTAL)

Code: Select all

Character Devoces ->
[M] Intel i865 chipset support
[M] Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
[M] Intel I810
[M] Intel 830M, 845G, 852GM, 855GM, 865G
[M] i915 driver
[ ] i830 driver

Modules are said to be easier to handle by xorg, therefore should be used in this case.

And Xorg sais:

Code: Select all

(==) I810(0): Backing store disabled
(==) I810(0): Silken mouse enabled
(II) I810(0): Initializing HW Cursor
(II) I810(0): X context handle = 0x00000001
(II) I810(0): [drm] installed DRM signal handler
(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled

Notice the i810 driver reports...

And Xorg.conf:

Code: Select all

Section "Device"
Identifier	"Standard VGA"
VendorName	"Unknown"
BoardName	"Unknown"
# Chipset line does not stand for anything - change it to "/me rocks" or anything you want;)
#Chipset	"i810"
Chipset		"i915"

#Driver     "i810"
Driver	"i915"
EndSection

Section "Device"
	Identifier  "video"
# Hmmm, thought i915 should be here, too...
	Driver      "i810"
	VideoRam    32768
	Option      "NoAccel"       "false"
        Option      "DRI"           "true"
EndSection

Splitted section? Whatever - it works...

Code: Select all

Section "dri"
	Group        0
	Mode         0666
EndSection

Note the small letters - 'dri' not 'DRI' - if it does change anything...

glxinfo:

Code: Select all

direct rendering: Yes

Try these settings as they are proven to work (at least) on my box. Mine is i865GV chip, but as they're all the same (all sucks) it should work on i855 as well.

Good luck...

[the_enigma]

The main issue I have seems to be that glxinfo doesn't report the same as Xorg.0.log, it always says Direct rendering: No, even if Xorg.0.log says it is enabled.
Anyway, I haven't tried setting up a framebuffer yet, that's being compiled now, but apart from that I used your config. The intel-mch-agp driver didn't work for me (Xorg reported no DRI as well) but intel-agp lets Xorg see the DRI at least.

Edit: Just tried some more stuff. I've gotten a framebuffer working using intelfb. I can't return to it, or even close X without everything dying though. And no, using a framebuffer doesn't change anything to my DRI issues. I still have Xorg saying I have DRI, and glxinfo saying I don't.

Just for some clarification. Xorg hasn't been shutting down for about a week, but it's changed since I started playing with the drivers. So I've broken something. I can't return to a console with Ctrl+Alt+F1 either, the laptop locks up.

And since using the framebuffer, even XVideo will lockup the whole laptop, no response.

So I've broken something real bad, I just don't know what.

[bonbons]

For me too the Xorg.0.log and glxinfo don't say the same...
X log says DRI enabled (eventually complaining about older DRI version in kernel, but snapshot drivers don't help)

I have even tried out XOrg 6.8.99.8, but still the same.

Don't remember exactly, but the last version of X where DRI worked was either 6.7 or 6.8.0...

Does anyone have an idea on where to search for the solution?
(When I have time I may try to manually compile "original" XOrg packages, that is without any gentoo packages, just to see if the problem comes from Gentoo, or right from XOrg)

[the_enigma]

Just an added tip, I found http://astronomy.swin.edu.au/staff/cthom/laptop/ but no matter what combination of things I tried, it didn't help.
I tried using the i830 module too. Now the i915 was auto-loaded by Xorg, so I had to modprobe the i830 module. So it loaded fine, but when Xorg started, I got a real small (1cmx1cm) square in the middle, mainly white. It had some stuff in it, didn't look like anything recognizable. I couldn't get back to a terminal either. So I hit the power switch, and I noticed something scrolling through that little screen in the middle of my screen. Don't know whether that was just me or not.

Anyway, the log from Xorg had

Code: Select all

(EE) I810(0): I830 Dma Initialization Failed

and

Code: Select all

(EE) I810(0): [drm] Failed to initialized agp heap manager

extra, when compared to the i915 log file, but that was all that changed.

So yeah, still no luck, but I found a few more ways of not enabling DRI at least.