Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 10 Nov 2005 13:38:01 +0100
From:      Roland Smith <rsmith@xs4all.nl>
To:        Will Saxon <WillS@housing.ufl.edu>
Cc:        stable@freebsd.org
Subject:   Re: Anyone having problems with xorg 6.8.2 on 6.0-R
Message-ID:  <20051110123801.GB42080@slackbox.xs4all.nl>
In-Reply-To: <0E972CEE334BFE4291CD07E056C76ED808DB6AE2@bragi.housing.ufl.edu>
References:  <0E972CEE334BFE4291CD07E056C76ED808DB6AE2@bragi.housing.ufl.edu>

next in thread | previous in thread | raw e-mail | index | archive | help

--JP+T4n/bALQSJXh8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Nov 09, 2005 at 08:47:41PM -0500, Will Saxon wrote:
> Hello,
>=20
> I upgraded my amd64 installation to 6.0-RELEASE, and I am no longer=20
> able to use X. It exits with a signal 11 error. I have recompiled from=20
> ports, installed from packages from freebsd.org and performed a clean=20
> installation from an i386 6.0-R cd again installing from both port=20
> compilation and packages. I get the same error every time. This was=20
> all working fine last Thursday on I believe 6.0-BETA5.
>=20
> System is a dual Opteron 244 on an MSI K8T Master2-FAR with an ATI=20
> Radeon 9200SE.=20

I'm using a Radeon 9250 on an amd64 (single athlon64, Asus K8V mobo)
system without problems.

> I've rebuilt xorg with -DWITH_DEBUG and here is a backtrace from the
> core file:
>=20
> #0  0x282384b3 in kill () from /lib/libc.so.6
> #1  0x2822d4f0 in raise () from /lib/libc.so.6
> #2  0x282a7c5c in abort () from /lib/libc.so.6
> #3  0x0806c1d6 in ddxGiveUp () at xf86Init.c:1228
> #4  0x080d945e in AbortServer () at log.c:395
> #5  0x080d9520 in FatalError (
>     f=3D0x8187798 "Caught signal %d.  Server aborting\n") at log.c:541
> #6  0x08081618 in xf86SigHandler (signo=3D11) at xf86Events.c:1298
> #7  0xbfbfff94 in ?? ()
> #8  0x0000000b in ?? ()
> #9  0x0000000c in ?? ()
> #10 0xbfbfe680 in ?? ()
> #11 0x0000022c in ?? ()
> #12 0x080815c0 in xf86InterceptSignals () at xf86Events.c:1270
> #13 0x28632934 in RADEONDisplayDDCConnected (pScrn=3D0x81df800,=20
>     DDCType=3DDDC_VGA, port=3D0x81c2a44) at radeon_driver.c:914
> #14 0x2863e10f in RADEONPreInit (pScrn=3D0x81df800, flags=3D0)
>     at radeon_driver.c:1810
> #15 0x0806dcc0 in InitOutput (pScreenInfo=3D0x81b9ac0, argc=3D4,
> argv=3D0xbfbfed20)
>     at xf86Init.c:588
> #16 0x080c2ae7 in main (argc=3D4, argv=3D0xbfbfed20, envp=3D0xbfbfed34)
>     at main.c:365
>
> As I mentioned earlier, this occurs on i386 and amd64, compiled on the=20
> machine or using packages from freebsd.org. I have tried with and
> without
> dri enabled.

For DRI, you need an extra device on 6.0. On 5.4 it used to be:

device radeondrm

On 6.0 it should be:

device drm
device radeondrm

HTH, Roland

--=20
R.F.Smith (http://www.xs4all.nl/~rsmith/) Please send e-mail as plain text.
public key: http://www.xs4all.nl/~rsmith/pubkey.txt

--JP+T4n/bALQSJXh8
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (FreeBSD)

iD8DBQFDcz8pEnfvsMMhpyURAtLEAJ0e1P2IOGVZJjJqTBX3j+usK5d3qgCfTGhD
MMF2JbTG6f1QQGA84DN+6kw=
=5hxZ
-----END PGP SIGNATURE-----

--JP+T4n/bALQSJXh8--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051110123801.GB42080>