Bug 75425 - xorg-server: i810 broken on 16/24bpp with XAA.
Summary: xorg-server: i810 broken on 16/24bpp with XAA.
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-23 10:10 UTC by Marc Silver
Modified: 2005-01-06 17:50 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Silver 2004-12-23 10:10:27 UTC
	Problem with i810 driver?! in Xorg 6.8.1?

	Since upgrading to this I am unable to start Xorg at all, and it
	complains about kernel module i915 and then core dumps with a
	signal 11.  The previous port of Xorg was working fine, so my
	guess is that something is either missing in this new port, or
	there's a bug?

	The script output follows:

Script started on Thu Dec 23 12:01:16 2004
bsd# Xorg -config /root/xorg.conf.new 
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/bsd.domain.com:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6

X Window System Version 6.8.1
Release Date: 17 September 2004
X Protocol Version 11, Revision 0, Release 6.8.1
Build Operating System: FreeBSD 5.3 i386 [ELF] 
Current Operating System: FreeBSD bsd.domain.com 5.3-STABLE FreeBSD 5.3-STABLE #17: Wed Dec 15 16:30:54 SAST 2004     root@bsd.domain.com:/usr/src/sys/i386/compile/BSD i386
Build Date: 23 December 2004
	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: Thu Dec 23 12:01:22 2004
(++) Using config file: "/root/xorg.conf.new"
[drm] failed to load kernel module "i915"
(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


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.

Fix: 

I have no idea on a fix... but would appreciate if some
	Xorg/XFree Guru could look at this please...
How-To-Repeat: 	Upgrade to 6.8.1 if you have an Intel i810 graphic card?!
Comment 1 Eric Anholt 2004-12-23 21:37:09 UTC
Does it still happen if you remove Load "dri" from your config file?

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2004-12-23 22:04:22 UTC
Responsible Changed
From-To: freebsd-ports-bugs->freebsd-x11

Over to maintainer(s).
Comment 3 amatveev 2004-12-23 22:33:23 UTC
I am not original submitter for that bug, just having the same problem
(laptop Sony R505-EL).

Here is what I found so far:

1. If you disable DRI it still happens.
2. If you add option "NoAccel" you are able to start xorg. Just no
acceleration obviously.

Alex
Comment 4 Eric Anholt 2004-12-24 22:21:51 UTC
The conclusion of this so far has been that there's some bug in our
6.8.1 such that i810s are crashing at 16 and 24 depth.  So, an ugly
workaround is to run at 8bpp for now.  I posted a patch at
http://people.freebsd.org/~anholt/X/patch-i810-6_8 to update the i810
bits to the latest CVS, and it has helped 0/1 people so far.  At this
point, the best bet for debugging this is probably to do a dlloader
build so that gdb can be used.  One bit of info about the dlloader is
at:
http://lists.freedesktop.org/pipermail/xorg/2004-November/004566.html.

If people seeing this problem could post to this gnats entry with what
iXXX integrated graphics they happen to have, that could be useful.  

-- 
Eric Anholt                                eta@lclark.edu          
http://people.freebsd.org/~anholt/         anholt@FreeBSD.org
Comment 5 Peter Thoenen 2004-12-25 23:25:20 UTC
Seeing this also.  Chipset is: 852GM/855GM.

In addition to the issues mentioned above (DRI False, NoAccel True), I also
have to set SWCursor True otherwise I get a hardware cursor error and X fails
to start.  Only warnings in log (with above settings) follows:

(WW) I810(0): Bad V_BIOS checksum
(II) I810(0): Primary V_BIOS segment is: 0xc000
Comment 6 dave 2004-12-31 12:43:37 UTC
[ Re-sent, due to mail-server problems]

Same problem observed on Thinkpad R31 with 830M graphics chip.

Commenting out 'Load "dri"' and setting "SWCursor" fixed the error 
messages.

Interestingly enough, setting "NoAccel" stopped the SIGSEGV and I was able 
to get the server started.  Before trying out the patch (the original was 
installed from packages so I'll need a massive compile) I'll see if I can 
bootstrap the configuration by hand, since xorgcfg falls over the same 
way.


-- Dave
Comment 7 dave 2004-12-31 12:47:44 UTC
[ Re-sent again ]

> Interestingly enough, setting "NoAccel" stopped the SIGSEGV and I was 
> able to get the server started.  Before trying out the patch (the 
> original was installed from packages so I'll need a massive compile) 
> I'll see if I can bootstrap the configuration by hand, since xorgcfg 
> falls over the same way.

The compile went quicker than I thought, but not much difference:

-----

# xorgcfg

[...]

(EE) I810(0): Failed to allocate HW (ARGB) cursor space.
[drm] failed to load kernel module "i915"
(EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI.

    *** If unresolved symbols were reported above, they might not
    *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting

-----

Basically, the X server is still unable to bootstrap itself.  I'll keep 
plodding along with constructing an xorg.conf file by hand, but it won't 
be done any time this year :-)

-- Dave
Comment 8 Eric Anholt freebsd_committer freebsd_triage 2005-01-02 00:18:19 UTC
State Changed
From-To: open->analyzed

The patch at http://people.freebsd.org/~anholt/X/xorg-server-update.diff 
fixes it for me, and is waiting for portmgr approval.
Comment 9 Eric Anholt freebsd_committer freebsd_triage 2005-01-02 00:32:47 UTC
State Changed
From-To: analyzed->closed

Shoudl be fixed in CVS.  Thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=75425 

Adding (in case it is needed) to audit trail from misfiled PR 75659:
Date: Thu, 30 Dec 2004 17:57:41 +0200
Comment 10 falkenbe 2005-01-03 21:53:04 UTC
I have an i830 video card.  I upgraded to xorg-server 6.8.1_1 but I'm
still having the same problem, I must set "NoAccel" in order for X to
start.  Commenting out the load  dri instruction and adding the
SWCursor does not work for me, "NoAccel" is the only thing that will
get X to start.

Is there anything else I can try to fix this?
Comment 11 falkenbe 2005-01-06 17:44:42 UTC
The modules/drivers directory for 6.8.1_1 was not being installed
properly and so I was using the old 6.8.1 video drivers.  Now that I'm
actually using the correct drivers everything is working properly. 
Thanks.