mach64 - dri2 trouble

Fred Scali <[email protected]> Fri, 22 Feb 2008 15:33:53 +0000 (GMT)
Newsgroups gmane.comp.video.dri.user
Message-ID <[email protected]>
--===============0620375368==
Content-Type: multipart/alternative; boundary="0-192931251-1203694433=:77893"

--0-192931251-1203694433=:77893
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hello to everybody,=0A=0Athis my first post on this list, because I've have=
 already successfully build (on Slackware based Zenwalk) the mach64 dri dri=
ver (with git, following the DRI wiki) on a old Sony 1GHz laptop for a few =
weeks, even with the version mismatch problem (  [dri] mach64.o kernel modu=
le version is 2.0.0, but version 1.0 or greater is needed). Not a real help=
, this error message, and somehow not logical at all (2.0 IS greater than 1=
.0!!!).=0AUpgrading to Xorg 7.3 did the trick and I was happy!=0ABut now th=
at I'm trying again the same way in a Ubuntu Gutsy, I'm having a new (and u=
nknown) error, when I try to load it from my building directory:=0A=0AlibGL=
: XF86DRIGetClientDriverName: 6.7.197 mach64 (screen0)=0AlibGL: OpenDriver:=
 trying /root/mesa/lib/mach64_dri.so=0AlibGL error: dlopen /root/mesa/lib/m=
ach64_dri.so failed (/root/mesa/lib/mach64_dri.so: undefined symbol: __dri2=
DriverInitScreen)=0AlibGL error: unable to load driver: mach64_dri.so=0A=0A=
I mean, in all my trying and error to get that thing working, I've already =
got, as I said before, the version mismatch (which need Xorg upgrade), and =
also the module not found (which need a copy in the right place or a symlin=
k) and perhaps I've forgotten some others...=0ABut this one is really a new=
 and a weird one. By searching on the Web, I've found that somebody on the =
dri-devel list got that too, for the r300_dri.so module here in the DRI IRC=
 log: =0A=0Ahttp://people.freedesktop.org/~cbrill/dri-log/index.php?date=3D=
2008-02-20=0A=0AThe relevant part:=0A=0A 11:04 #dri-devel: < krh> MrCooper:=
 what is this breakage that you speak of? =0A11:24 #dri-devel: < math_b> kr=
h: I can confirm this undefined __dri2DriverInitScreen symbol here on r300 =
=0A11:25 #dri-devel: < math_b> the __DRI2_CREATE_NEW_SCREEN functions calls=
  __dri2DriverInitScreen which is not defined in non DRI2 drivers =0A11:26 =
#dri-devel: < math_b> this create undefined symbol in r300_dri.so here =0A1=
1:27 #dri-devel: < krh> math_b: in libGL? =0A11:28 #dri-devel: < math_b> kr=
h: I don't think so: lbGL tries to dlopen r300_dri.so but can't due to this=
 missing symbol in r300_dri.so =0A11:28 #dri-devel: < math_b> the missing s=
ymbol is not in libGL =0A11:28 #dri-devel: < krh> math_b: ok =0A=0ASo, what=
 did I made wrong? Why does that brand new DRI2  stuff (that I don't even r=
eally know for what it is used, just that is relatively new) make some chao=
s like this now, even on old hardware? =0AI mean, I can understand the secu=
rity concern about the mach64, and the fact that is an old crap. But a crap=
 that a lot of people still use, especially in old laptops. And Linux is pe=
rfect to giving them back some life. I'm also agree that I can't (and don't=
 want) to play 3D games or use Compiz on it. But I want to have the choice =
between security concerns (for the moment, because some people are still wo=
rking hard to get it secure) and 3D. =0AAnd for a non programmer like me, i=
t's interesting to discovering git, and to build your own driver, even if i=
t's a bit complicate at the very beginning. But that's getting to far, I th=
ink the mach64 users don't need that new headache!!! =0A=0ASo any help woul=
d be appreciated, but don't get me wrong: it's perhaps my fault and I'm doi=
ng something completely false, but I really can't see what! And I'm French,=
 so I hope it's not sounding to rough (especially for people working or usi=
ng DRI2), but I'm really getting mad with this new error, and find no infor=
mations on it...=0A=0ASalut =C3=A0 tous,=0AFSW=0A=0A=0A=0A=0A      ________=
_____________________________________________________________________ =0ANe=
 gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail =
http://mail.yahoo.fr
--0-192931251-1203694433=:77893
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman,new york,times,serif;fon=
t-size:12pt"><div>Hello to everybody,<br><br>this my first post on this lis=
t, because I've have already successfully build (on Slackware based Zenwalk=
) the mach64 dri driver (with git, following the DRI wiki) on a old Sony 1G=
Hz laptop for a few weeks, even with the version mismatch problem (  [dri] =
mach64.o kernel module version is 2.0.0, but version 1.0 or greater is need=
ed). Not a real help, this error message, and somehow not logical at all (2=
.0 IS greater than 1.0!!!).<br>Upgrading to Xorg 7.3 did the trick and I wa=
s happy!<br>But now that I'm trying again the same way in a Ubuntu Gutsy, I=
'm having a new (and unknown) error, when I try to load it from my building=
 directory:<br><br>libGL: XF86DRIGetClientDriverName: 6.7.197 mach64 (scree=
n0)<br>libGL: OpenDriver: trying /root/mesa/lib/mach64_dri.so<br>libGL
 error: dlopen /root/mesa/lib/mach64_dri.so failed (/root/mesa/lib/mach64_d=
ri.so: undefined symbol: __dri2DriverInitScreen)<br>libGL error: unable to =
load driver: mach64_dri.so<br><br>I mean, in all my trying and error to get=
 that thing working, I've already got, as I said before, the version mismat=
ch (which need Xorg upgrade), and also the module not found (which need a c=
opy in the right place or a symlink) and perhaps I've forgotten some others=
...<br>But this one is really a new and a weird one. By searching on the We=
b, I've found that somebody on the dri-devel list got that too, for the r30=
0_dri.so module here in the DRI IRC log: <br><br><span><a target=3D"_blank"=
 href=3D"http://people.freedesktop.org/%7Ecbrill/dri-log/index.php?date=3D2=
008-02-20">http://people.freedesktop.org/~cbrill/dri-log/index.php?date=3D2=
008-02-20</a></span><br><br>The relevant part:<br><br> 11:04 #dri-devel: <a=
 style=3D"color: black;" href=3D"javascript:addUser('< krh>');">&lt; krh&gt=
;</a>
 MrCooper: what is this breakage that you speak of? <br>11:24 #dri-devel: <=
a style=3D"color: black;" href=3D"javascript:addUser('< math_b>');">&lt; ma=
th_b&gt;</a> krh: I can confirm this undefined __dri2DriverInitScreen symbo=
l here on r300 <br>11:25 #dri-devel: <a style=3D"color: black;" href=3D"jav=
ascript:addUser('< math_b>');">&lt; math_b&gt;</a> the __DRI2_CREATE_NEW_SC=
REEN functions calls  __dri2DriverInitScreen which is not defined in non DR=
I2 drivers <br>11:26 #dri-devel: <a style=3D"color: black;" href=3D"javascr=
ipt:addUser('< math_b>');">&lt; math_b&gt;</a> this create undefined symbol=
 in r300_dri.so here <br>11:27 #dri-devel: <a style=3D"color: black;" href=
=3D"javascript:addUser('< krh>');">&lt; krh&gt;</a> math_b: in libGL? <br>1=
1:28 #dri-devel: <a style=3D"color: black;" href=3D"javascript:addUser('< m=
ath_b>');">&lt; math_b&gt;</a> krh: I don't think so: lbGL tries to dlopen =
r300_dri.so but can't due to this missing symbol in r300_dri.so <br>11:28 #=
dri-devel: <a
 style=3D"color: black;" href=3D"javascript:addUser('< math_b>');">&lt; mat=
h_b&gt;</a> the missing symbol is not in libGL <br>11:28 #dri-devel: <a sty=
le=3D"color: black;" href=3D"javascript:addUser('< krh>');">&lt; krh&gt;</a=
> math_b: ok <br><br>So, what did I made wrong? Why does that brand new DRI=
2&nbsp; stuff (that I don't even really know for what it is used, just that=
 is relatively new) make some chaos like this now, even on old hardware? <b=
r>I mean, I can understand the security concern about the mach64, and the f=
act that is an old crap. But a crap that a lot of people still use, especia=
lly in old laptops. And Linux is perfect to giving them back some life. I'm=
 also agree that I can't (and don't want) to play 3D games or use Compiz on=
 it. But I want to have the choice between security concerns (for the momen=
t, because some people are still working hard to get it secure) and 3D. <br=
>And for a non programmer like me, it's interesting to discovering git, and
 to build your own driver, even if it's a bit complicate at the very beginn=
ing. But that's getting to far, I think the mach64 users don't need that ne=
w headache!!! <br><br>So any help would be appreciated, but don't get me wr=
ong: it's perhaps my fault and I'm doing something completely false, but I =
really can't see what! And I'm French, so I hope it's not sounding to rough=
 (especially for people working or using DRI2), but I'm really getting mad =
with this new error, and find no informations on it...<br><br>Salut =C3=A0 =
tous,<br>FSW<br></div></div><br>=0A=0A=0A=0A      <hr size=3D"1"> =0ANe gar=
dez plus qu'une seule adresse mail ! <a href=3D"http://fr.rd.yahoo.com/mail=
/mail_taglines/trueswitch/SIG=3D11gshn0bu/**http%3A%2F%2Fwww.trueswitch.com=
%2Fyahoo-fr%2F">Copiez vos mails</a> vers Yahoo! Mail </body></html>
--0-192931251-1203694433=:77893--


--===============0620375368==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
--===============0620375368==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
_______________________________________________
Dri-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-users

--===============0620375368==--