From: Chris H. <ch...@ch...> - 2002-07-02 17:04:48
|
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Tuesday 02 July 2002 5:38 pm, Keith Whitwell wrote: > Nobody's really talked about this as a desired feature previously. I'm n= ot > even sure that it *doesn't* work -- it shouldn't be too hard to get worki= ng > if not. Well the reason that it doesn't work at the moment is that DRI seems to det= ect=20 that a DRI session is already in use, and then disables it. e.g. I've just= =20 tried to open a second X session and have done startx -- :1 1>log.txt=20 2>log.txt, and in log.txt I see: (II) R128(0): [drm] drmSetBusid failed (6, PCI:1:0:0) (EE) R128(0): [dri] DRIScreenInit failed. Disabling DRI. If somebody tells me where I can disable that bit of code I wouldn't mind=20 testing :) =2D --=20 Cheers, Chris Howells -- ch...@ch..., ho...@kd... Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://edu.kde.org, http://usability.kde.org =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE9IdwSF8Iu1zN5WiwRAsThAKCNpUJjgIFHnAjf09Dw5d9tcX0A+wCffneL 5mILqPyzhT197YyRjTVvCzY=3D =3D0DOa =2D----END PGP SIGNATURE----- |