(Not so) funny problems with xorg-7.4 autodetection

[Robert Noland]

On Wed, 2009-01-28 at 19:42 -0600, Rick Voland wrote:
> Robert Noland wrote:
> > On Tue, 2009-01-27 at 20:17 -0600, Rick Voland wrote:
> >> I, too, am having trouble with autodetection with xorg-7.4.
> >>
> >> After I type "startx", I see the usual blank, then text, then blank, but
> >> X stops at a blank screen.  It does not respond to cntl-alt-backspace,
> >> and only sometimes responds to the power-off button.
> >>
> >> I attach a tar file that contains output from dmesg, pciconf,
> >> xorgconfig, and Xorg.0.log.
> > 
> > The attached log does not indicate any input devices.  So either it is
> > hanging just before it reaches that stage or hald and dbus are not
> > running, or at least have not had adequate time to finish initializing.
> > 
> > X -configure is the preferred way to generate a config these days.
> > xf86config is going away, it may already be gone in server 1.6, but I'm
> > sure it is already gone in master.
> > 
> > The I915 should be fine, though the configless log seems a bit strange.
> > I'll should have access to a 915gm based dell this weekend to check
> > that.
> > 
> > If the above is of no help, you could try to ssh in from another machine
> > and see if you can tell what is going on, or better yet attach to the
> > Xorg process with gdb and get a backtrace.
> > 
> > robert.
> 
> The last message in /var/log/messages is as follows.  It is the only
> item after the usual boot messages.  This message only occurs after I
> type "startx".
> 
> 
> Jan 28 19:35:23 karl kernel: drmsub0: <Intel i915GM>: (child of
> agp_i810.c) on agp0
> Jan 28 19:35:23 karl kernel: info: [drm] AGP at 0xb0080000 0MB
> Jan 28 19:35:23 karl kernel: info: [drm] Initialized i915 1.5.0 20060119
> Jan 28 19:35:23 karl kernel: error: [drm:pid1127:i915_getparam] *ERROR*
> i915_getparam called with no initialization
> 
> 
> I have
> libpciaccess-0.10.5_1
> 
> Do I need to do a recursive update for all ports that depend on this?

Nope, this is a drm compatibility issue with the intel driver.  Your
current options are to either update to releng_7 (STABLE) or disable drm
Option "DRI" "off" in the device section of your xorg.conf.

One other possible option is to go back to xf86-video-intel 2.4.3.  I'll
look at this as a possibility as well as take a look at the ancient drm
code and see if I can do something there.

robert.

> 
> -------
> $ tail -40 Xorg.0.log
> (II) intel(0): 0x00733000-0x00733fff: overlay registers (4 kB,
> 0x000000003ff33000 physical
> )
> (II) intel(0): 0x007bf000:            end of stolen memory
> (II) intel(0): 0x01000000-0x01ffffff: front buffer (10240 kB) X tiled
> (II) intel(0): 0x02000000-0x03dfffff: exa offscreen (30720 kB)
> (II) intel(0): 0x04000000-0x04ffffff: back buffer (10240 kB) X tiled
> (II) intel(0): 0x05000000-0x05ffffff: depth buffer (10240 kB) X tiled
> (II) intel(0): 0x06000000-0x07ffffff: classic textures (32768 kB)
> (II) intel(0): 0x10000000:            end of aperture
> (II) intel(0): using SSC reference clock of 100 MHz
> (II) intel(0): Selecting standard 18 bit TMDS pixel format.
> (II) intel(0): Output configuration:
> (II) intel(0):   Pipe A is off
> (II) intel(0):   Display plane A is now disabled and connected to pipe A.
> (II) intel(0):   Pipe B is on
> (II) intel(0):   Display plane B is now enabled and connected to pipe B.
> (II) intel(0):   Output VGA is connected to pipe none
> (II) intel(0):   Output LVDS is connected to pipe B
> (II) intel(0):   Output TV is connected to pipe none
> (II) intel(0): [drm] dma control initialized, using IRQ 16
> (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled
> message.
> (II) intel(0): DPMS enabled
> (II) intel(0): Set up textured video
> (II) intel(0): Set up overlay video
> (II) intel(0): direct rendering: Enabled
> (--) RandR disabled
> (II) Initializing built-in extension MIT-SHM
> (II) Initializing built-in extension XInputExtension
> (II) Initializing built-in extension XTEST
> (II) Initializing built-in extension XKEYBOARD
> (II) Initializing built-in extension XINERAMA
> (II) Initializing built-in extension XFIXES
> (II) Initializing built-in extension RENDER
> (II) Initializing built-in extension RANDR
> (II) Initializing built-in extension COMPOSITE
> (II) Initializing built-in extension DAMAGE
> (II) Initializing built-in extension XEVIE
> (II) AIGLX: Loaded and initialized /usr/local/lib/dri/swrast_dri.so
> (II) GLX: Initialized DRISWRAST GL provider for screen 0
> (II) intel(0): Setting screen physical size to 305 x 183
> $
> ------
> 
> I think the screen should be 1280x768.
> 
> ----
> 
> Rick Voland
> rpvoland at spamcop.net
> 
> 
> 
> 
> > 
> >> The computer is an HP dv1000 with product number dv1331se.  It has the
> >> GM915 video chip and 1 GB of RAM.
> >>
> >> I used no xorg.conf configuration file for xorg-7.3.x because X
> >> autodetected chip, resolution, and 24-bit color just fine.
> >>
> >> Thanks,
> >>
> >> Rick Voland
> >> rpvoland at spamcop.net
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-x11/attachments/20090129/dfb82bcc/attachment.pgp