Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 May 2005 18:37:51 -0500
From:      Jonathan Noack <noackjr@alumni.rice.edu>
To:        Jiawei Ye <leafy7382@gmail.com>
Cc:        Jeff Roberson <jroberson@chesapeake.net>
Subject:   Re: ULE, 4BSD and xorg
Message-ID:  <4282974F.9090205@alumni.rice.edu>
In-Reply-To: <c21e92e2050510192516a76cd9@mail.gmail.com>
References:  <20050503022632.R36718@it.hackers> <20050503022532.F48828@mail.chesapeake.net> <c21e92e2050510002951d737c7@mail.gmail.com>	 <20050510175056.T672@sotec.home> <c21e92e2050510192516a76cd9@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigB3D18D07355EF3078D7403DC
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 05/10/05 21:25, Jiawei Ye wrote:
> On 5/11/05, Mikko Ty=F6l=E4j=E4rvi <mbsd@pacbell.net> wrote:
>>On Tue, 10 May 2005, Jiawei Ye wrote:
>>FWIW, I get this too on my laptop.  Basic troubleshooting shows that
>>it is DRI that blows up.  Removing 'Load "dri"' from Xorg's config was
>>not sufficient, as the server will try to autoload the "sis" kmod
>>anyway.  Had to delete "sis.ko" as well.
>=20
> I use SIS630 on this machien too, so the confirmed fact is that SIS
> chipset doesn't work in X under -current?

Have you tried the xorg-server-snap and dri-devel ports?  The DRM code=20
was updated recently and could be to blame, although testing it with=20
newer code would be an interesting data point.

Also, try loading the module at boot by putting 'sis_load=3D"YES"' in=20
/boot/loader.conf.  Does X work then?  The reason I ask is that I have a =

machine with an r128 card that displays garbage when the module is=20
loaded by X but works perfectly when the module is loaded beforehand.=20
I've been told that when the module is loaded should make no difference, =

but my experience tells me otherwise...

>>I think it is unrelated to the scheduler (I'm using 4BSD). Current
>>from late March worked fine with DRI, current from late April does
>>not.

See note above about DRM being updated recently.

--=20
Jonathan Noack | noackjr@alumni.rice.edu | OpenPGP: 0x991D8195


--------------enigB3D18D07355EF3078D7403DC
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

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

iD8DBQFCgpdZUFz01pkdgZURAoVqAJ97xk4xo6649FFHOPcL1/UnT/i9ogCg3Iie
GLJP9SmRJkArmSLmDzD2Jqk=
=ecW4
-----END PGP SIGNATURE-----

--------------enigB3D18D07355EF3078D7403DC--



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