Xorg & i810 graphics / loader.conf / kldstat

[OgreNaut]

Hi, I'm somewhat of a FreeBSD noob, but not a *nix noob.

I'm having problems getting Xorg to work properly with my hardware. I'm running 7.0 on an old Compaq Deskpro EN 733PIII. It has i815 Intel graphics, which is supported by the i810 driver packaged with 7.0.

I've been reading copious amounts of documentation and experimenting to get this going. With both Gnome and KDE, I just get a messed up screen; I can see bits of each desktop environment and the mouse works, but they're unusable. I have my monitor settings perfect, including the arcane Modeline settings.

Following the FreeBSD X11 config guide (http://www.freebsd.org/doc/en/books/.../x-config.html), I have set agp_load="YES" in /boot/loader.conf, but when I do a kldstat, the agp.ko module isn't listed. This agp.ko module is essential to getting the i810 driver to work. What gives? Why isn't agp.ko loaded, even though I've specified it in loader.conf???

- Ogre

[Carpetsmoker]

The agp module is part of the GENERIC kernel, you don't need to load it.
kldstat doesn't show the modules built in the kernel, to show the modules in the kernel, use the -v flag.

I'm having problems getting Xorg to work properly with my hardware.

What problems exactly?

[OgreNaut]

What problems exactly?

With both Gnome and KDE, I just get a messed up screen; I can see bits of each desktop environment and the mouse works, but they're unusable.

Indeed, you're right about the kldstat flag! There's my i810 driver!

$ kldstat -v | grep agp
                408 hostb/agp_ali
                409 hostb/agp_amd
                410 hostb/agp_amd64
                411 hostb/agp_ati
                412 vgapci/agp_i810
                413 hostb/agp_intel
                414 hostb/agp_nvidia
                415 hostb/agp_sis
                416 hostb/agp_via

Some more specifics on the hardware:
Monitor: Sceptre 19" 4:3 1280x1024
Video: Onboard Intel 815 4MB RAM. Max bit depth: 16

Here's my xorg.conf:

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

Section "Files"
        RgbPath      "/usr/local/share/X11/rgb"
        ModulePath   "/usr/local/lib/xorg/modules"
        FontPath     "/usr/local/lib/X11/fonts/misc/"
        FontPath     "/usr/local/lib/X11/fonts/TTF/"
        FontPath     "/usr/local/lib/X11/fonts/OTF"
        FontPath     "/usr/local/lib/X11/fonts/Type1/"
        FontPath     "/usr/local/lib/X11/fonts/100dpi/"
        FontPath     "/usr/local/lib/X11/fonts/75dpi/"
EndSection

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

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

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

Section "Monitor"
        Identifier   "Monitor0"
        VendorName   "Monitor Vendor"
        ModelName    "Monitor Model"
        HorizSync       24-80
        VertRefresh     50-75
        ModeLine        "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066
EndSection

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

Section "Screen"
        Identifier "Screen0"
        Device     "Card0"
        Monitor    "Monitor0"
        DefaultDepth    16
        SubSection "Display"
                Viewport   0 0
                Depth     1
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     4
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     8
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     15
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     16
                Modes   "1280x1024" "1024x768" "800x600" "640x480"
                #Virtual        1280 1024
        EndSubSection
        SubSection "Display"
                Viewport   0 0
                Depth     24
        EndSubSection
EndSection

Here's some interesting stuff from my Xorg.0.log. Important?

...
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: Open failed
[drm] failed to load kernel module "i810"
(EE) [drm] drmOpen failed.
(EE) I810(0): [dri] DRIScreenInit failed.  Disabling DRI.
...

Any ideas??? I've been working at this for a few days.

- Ogre

[Oko]

You should use intel driver instead of obsolete i810. In my experience one of the common
reason for failure of X server with intel driver that it supports only DefaultDepts up to
24 even though your hardware might support something higher (32).
Force X server to use DefaultDepth 24 by editing xorg.conf file. Also try to increase
vertical and horizontal refreshing rates.
Finally put something reasonable for Modes "1024x768" comes to mind.

And did I say that you sould read your xorg.log file:--)

[phoenix]

If you're getting a "mixed up desktop" with multiple images showing, then your resolution and refresh rate are set incorrectly, which points to either an invalid ModeLine setting, or an incorrect resolution setting.

What happens if you comment the VertRefresh, HorizSync, and ModeLine lines?

[OgreNaut]

What happens if you comment the VertRefresh, HorizSync, and ModeLine lines?

This is what I get, with no inkling of GUI loading:

Fatal server error:
AddScreen/ScreenInit failed for driver 0

Isn't THIS message a major indicator of what's going on?:
(From my previously posted Xorg.0.log)

[drm] failed to load kernel module "i810"

Kind of a strange message. Hmmm...just looked in /boot/kernel for i810 module. Found i915.ko, but not i810.ko. Normal, or weird? Perhaps i915.ko IS the module file that contains the i810 driver, as well as a few others?

[OgreNaut]

If you're getting a "mixed up desktop" with multiple images showing, then your resolution and refresh rate are set incorrectly

Forgot to mention that this has been checked and double checked. The detected values by "Xorg -configure" match the manufacturer's specs:
HorizSync: 24-80
VertRefresh: 50-75

I checked it against the monitor's manual.

[OgreNaut]

BTW Carpetsmoker, badass Rutger Hauer avatar.

- Ogre

[adamk]

Have you tried the "intel" driver yet? It really is recommended over the unsupported and unmaintained i810 driver.

Also, the i810 kernel module Xorg is trying to load is for 3D functionality. It really should not be impacting your normal gnome or KDE desktop.

Adam

[richardpl]

DRI/DRM is not enabled (causing various errors on screen)

Add this to your xorg.conf

Section "DRI"
	     Mode 0666
EndSection

[OgreNaut]

Originally Posted by richardpl

DRI/DRM is not enabled (causing various errors on screen)

Add this to your xorg.conf

Section "DRI"
	     Mode 0666
EndSection

Already fixed this. No dice.

- Joe

[adamk]

The reason that DRI/DRM is not enabled is due to this:

[drm] failed to load kernel module "i810"

And I really doubt it has anything to do with his normal 2D desktop corruption, though I have been wrong in the past.

Adam

[richardpl]

You missed fact that following lines are displayed before error you mentioned.

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: Open failed
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: open result is -1, (No such file or directory)
drmOpenDevice: Open failed

[richardpl]

To OP:

Make sure that drm.ko & i915.ko are displayed in kldstat output.

[OgreNaut]

Originally Posted by richardpl

To OP:

Make sure that drm.ko & i915.ko are displayed in kldstat output.

Neither of these are present in output from kldstat OR "kldstat-v". I grep'd 'em to make sure.

Now what? Manually load those in loader.conf?

- Ogre

[richardpl]

Originally Posted by OgreNaut

Neither of these are present in output from kldstat OR "kldstat-v". I grep'd 'em to make sure.

Now what? Manually load those in loader.conf?

Yes, load them manually:
# kldload drm i915

and add following lines in /boot/loader.conf:

drm_load="YES"
i915_load="YES"

After loading drm and i915 please post output of:

$ dmesg|tail

[adamk]

That's the result of the i810 kernel module not being loaded and being unloadable.

[richardpl]

There is no i810 kernel module.

[adamk]

That's my point :-) Which is one of the reasons I suggest he move to the "intel" driver... Well, other than the fact that the intel driver is newer and actually maintained.

[OgreNaut]

Originally Posted by adamk

That's my point :-) Which is one of the reasons I suggest he move to the "intel" driver... Well, other than the fact that the intel driver is newer and actually maintained.

Where might I find this mythical intel driver thou speakest of? From what I can tell, there is no maintained "intel" driver for FreeBSD anymore. The FreeBSD ports archive states that it was last released in 2007 and has now been deemed deprecated (http://www.freebsdsoftware.org/x11-d...deo-intel.html). Of course, I could always try building from source using the code from the good folks at http://intellinuxgraphics.org, but that seems like it should be unnecessary if the FreeBSD folks have decided to omit it from 7.0.

-Ogre