Re: [Dri-devel] First experience with binary shapshot
oops, forgot to cc: the list... On Thu, 6 Dec 2001, Manuel Teira wrote: [snip] > BTW, Leif, have you investigated any further on the VT change locks. Perhaps > we have forgot to lock some other function... I haven't done much with this lately, as I've been waiting for the DMA stuff first. I think the consensus was that it would be better to sort out the locking once that's done. Also, I've been working on adapting the experimental tv-out hack for r128 and radeon in gatos to mach64 with some success. I was able to play accelerated quake on my tv yesterday without using a framebuffer driver :) It's using a VESA bios function to set the mode, but it still requires rebooting with the tv connected. Also, it ends up garbling the text console. I hope to have a patch ready soon. > And Frank. when do you estimate we could play with your DMA code? > > Sorry, but I've been busy at work lately and also thought that it would be > better for me to keep my strength for the new DMA code. > > Go on, Frank! ;-) -- Leif Delgass http://www.retinalburn.net ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
El Mié 05 Dic 2001 15:02, escribiste: > Sergey V. Udaltsov wrote: > >Hi all > > > >Thanks to Jose, I got some binary stuff to test: > > > >lib/modules/2.4.9-13/kernel/drivers/char/drm/mach64.o > >usr/X11R6/lib/modules/drivers/ati_drv.o > >usr/X11R6/lib/modules/drivers/atimisc_drv.o > >usr/X11R6/lib/modules/drivers/r128_drv.o > >usr/X11R6/lib/modules/drivers/radeon_drv.o > > > >But I did not have much success: > >1. The kernel module loaded perfectly. No complains. > >2. The driver uses ABI v 5 but XFree 4.1.0 gives ABI version 4. First > > I had a similar problem until recognizing that I alwas started the old > X-Server with the new modules because I just edited the > /etc/X11/XF86Config file. Try to start e.g. /usr/X11R6-DRI/bin/XFree86 > explictly... > Just a thought ;-) > > BTW my X-Server is running now but I get strange authentification failures: > the DRM module isn't allowed to write to X while I'm not logged in as root. > kdm also fails on startup with XDM-AUTHENTIFICATION failure > Does anybody know how to fix this quick ( I haven't had time yet to read > something about that issue ) > > --Andreas Karrenbauer > > PS: Because of a new job I haven't had much time the past month, but > congratulations to Manuel Teira. He's done very well. I'm listening to > the list and hope to find time to contribute in any way Thank you, Andreas. It's nice to hear about you again. I think we're on the way for an stable DRI support for our Mach64 cards. What I use to do for testing the unstable driver is using a different init script for the DRI XServer. Something like: #!/bin/bash export LD_LIBRARY_PATH=/usr/X11R6-DRI/lib xinit /home/mteira/bin/xinitdri -- /usr/X11R6-DRI/bin/XFree86 I call this script: XDRI.sh And /home/mteira/bin/xinitdri is just an .xinitrc init script for starting the window manager, something like: #!/bin/bash WMANAGER=wmaker xmodmap ~/.Xmodmap xrdb ~/.Xresources if ["$WMANAGER" = "wmaker" \ -o "$WMANAGER" = "icewm" \ -o "$WMANAGER" = "blackbox" \ -o "$WMANAGER" = "pwm" ]; then xconsole -bg black -fg green -geometry 600x150+0+0 -fn 6x10 -file /dev/xconsole & aterm -geometry 80x24+0+180 -sl 500 -bg black -fg yellow -fn fixed & fi exec $WMANAGER In this way, I have a different window manager (WindowMaker) for my 3D tests, than the one I have for my everyday work (KDE). BTW, Leif, have you investigated any further on the VT change locks. Perhaps we have forgot to lock some other function... And Frank. when do you estimate we could play with your DMA code? Sorry, but I've been busy at work lately and also thought that it would be better for me to keep my strength for the new DMA code. Go on, Frank! ;-) ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
Dieter Nützel wrote: >Am Donnerstag, 6. Dezember 2001 17:16 schrieb Andreas Karrenbauer: > >>Dieter Nützel wrote: >> >>>Jose Fonseca wrote: >>> >BTW my X-Server is running now but I get strange authentification >failures: >the DRM module isn't allowed to write to X while I'm not logged in as >root. kdm also fails on startup with XDM-AUTHENTIFICATION failure >Does anybody know how to fix this quick ( I haven't had time yet to read >something about that issue ) > Andreas, in your own login (i.e., not as root) type something like: xauth +your_hostname >>>No, I think you are wrong: >>> >>>/home/nuetzel> hostname >>>SunWave1 >>>/home/nuetzel> xauth +SunWave1 >>>xauth: (argv):1: unknown command "+SunWave1" >>> >>>Andreas have a look into your ~/.Xauthority file. I am sure your_hostname >>>is already in it, no? >>> >>>My solution: >>> >>>Andreas are you running SuSE??? >>> >>yeah that's the point. I tried to use the generate command of xauth but >>that doesn't work at all. >> > >We know. See below. > >>>Then you need as myself as well a patch from SuSE for the XFree86/XFree86 >>>DRI CVS tree that enables the XDM-AUTHENTIFICATION (DES encryption for >>>better security) to get KDM running, again. >>> >>>I've looked into the SuSE 7.3 XFree86 (xf86-4.1.0-45.src.rpm) package but >>>didn't found the right stuff, yet :-( >>> >>I always had problems with kdm if I installed the compiled DRI X-Server. >> > >Stefan send me the right stuff and I will be working on that. >Stay tuned. >So we didn't have to CC "all" in this list. >Only someone speaks up and tell he/she/it needs to be CCed :-) > >>But this time the kernel module is also blocked: >> >>ndk@laptop:~> xhost +localhost >>localhost being added to access control list >>ndk@laptop:~> glxinfo >>name of display: :0.0 >>libGL error: failed to open DRM: Operation not permitted >>libGL error: reverting to (slow) indirect rendering >>display: :0 screen: 0 >>direct rendering: No >> > >That's a different thing and you should start with "insmod your_driver" and >send me (DRI list) your logs. Have a look into /var/log/XFree86.0.log, too. >...when we know what's going wrong we can solve... > >>[...] >>ndk@laptop:~> su >>Password: >>laptop:/home/ndk/ # glxinfo >>name of display: :0.0 >>display: :0 screen: 0 >>direct rendering: Yes >> > >Have you the right permissions for the /dev/dri/ folder? >After you had it running for the first time the access bits for your card >should be set. > >/home/nuetzel> l /dev/dri/ >insgesamt 59 >drwxrwx---2 root video 72 Dez 4 16:46 . >drwxr-xr-x 20 root root59472 Dez 6 15:52 .. >crw-rw1 root video226, 0 Sep 24 03:55 card0 >/home/nuetzel> l /dev/dri/card0 >crw-rw1 root video226, 0 Sep 24 03:55 /dev/dri/card0 > >Check your /etc/X11/XF86Config file. On SuSE it should look like this. >Especially the last three lines are importend. > >Section "Module" ># Load "pex5" > Load "xie" ># Load "record" > Load "extmod" > Load "type1" > Load "speedo" > Load "freetype" > Load "dbe" > Load "glx" > Load "dri" >EndSection > >Section "DRI" >Group "video" >Mode 0660 >EndSection > >Lets take this off line, know. > >Cheers, > Dieter > I solved the problem: I wasn't member of the "video" group by default. Obviously this has changed form SuSE 7.2 to 7.3 --Andreas Karrenbauer ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
Am Donnerstag, 6. Dezember 2001 17:16 schrieb Andreas Karrenbauer: > Dieter Nützel wrote: > >Jose Fonseca wrote: > >>>BTW my X-Server is running now but I get strange authentification > >>>failures: > >>>the DRM module isn't allowed to write to X while I'm not logged in as > >>>root. kdm also fails on startup with XDM-AUTHENTIFICATION failure > >>>Does anybody know how to fix this quick ( I haven't had time yet to read > >>>something about that issue ) > >> > >>Andreas, in your own login (i.e., not as root) type something like: > >> > >>xauth +your_hostname > > > >No, I think you are wrong: > > > >/home/nuetzel> hostname > >SunWave1 > >/home/nuetzel> xauth +SunWave1 > >xauth: (argv):1: unknown command "+SunWave1" > > > >Andreas have a look into your ~/.Xauthority file. I am sure your_hostname > > is already in it, no? > > > >My solution: > > > >Andreas are you running SuSE??? > > yeah that's the point. I tried to use the generate command of xauth but > that doesn't work at all. We know. See below. > >Then you need as myself as well a patch from SuSE for the XFree86/XFree86 > > DRI CVS tree that enables the XDM-AUTHENTIFICATION (DES encryption for > > better security) to get KDM running, again. > > > >I've looked into the SuSE 7.3 XFree86 (xf86-4.1.0-45.src.rpm) package but > >didn't found the right stuff, yet :-( > > I always had problems with kdm if I installed the compiled DRI X-Server. Stefan send me the right stuff and I will be working on that. Stay tuned. So we didn't have to CC "all" in this list. Only someone speaks up and tell he/she/it needs to be CCed :-) > But this time the kernel module is also blocked: > > ndk@laptop:~> xhost +localhost > localhost being added to access control list > ndk@laptop:~> glxinfo > name of display: :0.0 > libGL error: failed to open DRM: Operation not permitted > libGL error: reverting to (slow) indirect rendering > display: :0 screen: 0 > direct rendering: No That's a different thing and you should start with "insmod your_driver" and send me (DRI list) your logs. Have a look into /var/log/XFree86.0.log, too. ...when we know what's going wrong we can solve... > [...] > ndk@laptop:~> su > Password: > laptop:/home/ndk/ # glxinfo > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes Have you the right permissions for the /dev/dri/ folder? After you had it running for the first time the access bits for your card should be set. /home/nuetzel> l /dev/dri/ insgesamt 59 drwxrwx---2 root video 72 Dez 4 16:46 . drwxr-xr-x 20 root root59472 Dez 6 15:52 .. crw-rw1 root video226, 0 Sep 24 03:55 card0 /home/nuetzel> l /dev/dri/card0 crw-rw1 root video226, 0 Sep 24 03:55 /dev/dri/card0 Check your /etc/X11/XF86Config file. On SuSE it should look like this. Especially the last three lines are importend. Section "Module" # Load "pex5" Load "xie" # Load "record" Load "extmod" Load "type1" Load "speedo" Load "freetype" Load "dbe" Load "glx" Load "dri" EndSection Section "DRI" Group "video" Mode 0660 EndSection Lets take this off line, know. Cheers, Dieter -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: [EMAIL PROTECTED] ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
On Thu, 2001-12-06 at 16:16, Andreas Karrenbauer wrote: ... > I always had problems with kdm if I installed the compiled DRI X-Server. > But this time the kernel module is also blocked: > > ndk@laptop:~> xhost +localhost > localhost being added to access control list > ndk@laptop:~> glxinfo > name of display: :0.0 > libGL error: failed to open DRM: Operation not permitted > libGL error: reverting to (slow) indirect rendering > display: :0 screen: 0 > direct rendering: No > [...] > ndk@laptop:~> su > Password: > laptop:/home/ndk/ # glxinfo > name of display: :0.0 > display: :0 screen: 0 > direct rendering: Yes > > Any ideas? > > --Andreas Karrenbauer > Have you enable all user access to DRI by putting: Section "DRI" Mode 0666 EndSection in your /etc/X11/XFree86[-4] as recommended in the DRI User's Guide? Jose Fonseca ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
Dieter Nützel wrote: >Jose Fonseca wrote: > >>>BTW my X-Server is running now but I get strange authentification >>>failures: >>>the DRM module isn't allowed to write to X while I'm not logged in as >>>root. kdm also fails on startup with XDM-AUTHENTIFICATION failure >>>Does anybody know how to fix this quick ( I haven't had time yet to read >>>something about that issue ) >>> >>Andreas, in your own login (i.e., not as root) type something like: >> >>xauth +your_hostname >> > >No, I think you are wrong: > >/home/nuetzel> hostname >SunWave1 >/home/nuetzel> xauth +SunWave1 >xauth: (argv):1: unknown command "+SunWave1" > >Andreas have a look into your ~/.Xauthority file. I am sure your_hostname is >already in it, no? > >My solution: > >Andreas are you running SuSE??? > yeah that's the point. I tried to use the generate command of xauth but that doesn't work at all. > >Then you need as myself as well a patch from SuSE for the XFree86/XFree86 DRI >CVS tree that enables the XDM-AUTHENTIFICATION (DES encryption for better >security) to get KDM running, again. > >I've looked into the SuSE 7.3 XFree86 (xf86-4.1.0-45.src.rpm) package but >didn't found the right stuff, yet :-( > I always had problems with kdm if I installed the compiled DRI X-Server. But this time the kernel module is also blocked: ndk@laptop:~> xhost +localhost localhost being added to access control list ndk@laptop:~> glxinfo name of display: :0.0 libGL error: failed to open DRM: Operation not permitted libGL error: reverting to (slow) indirect rendering display: :0 screen: 0 direct rendering: No [...] ndk@laptop:~> su Password: laptop:/home/ndk/ # glxinfo name of display: :0.0 display: :0 screen: 0 direct rendering: Yes Any ideas? --Andreas Karrenbauer ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] First experience with binary shapshot: part 3, success
> BTW - I found the matter of problem. I have 8M video RAM. And use > resolution 1280x1024 (I have LCD so lower resolutions look > bad). Even in > 16bpp, all buffers take almost 8M - so only 192K remains for textures > (actually, on 32bpp the server does not start at all). When I > experimentally changed resolution to 800x600 (giving ~5M video RAM for > textures) - some textures appeared (but not all - for > example, half-life and celestia are still not working). rough estimation: 800 pixels/line x 600 lines x 2 byte/pixel x 2 buffers = 1,9 MB You should expect to have less than 6 MB for textures. (some video memory might be occupied for other purposes like an OpenGL depth buffer, stipple patterns, icons or other objects.) So you observations meet the state that has to be expected. > So my question is - will at some point driver use system RAM > for buffers > and/or textures etc? I thought AGP technology can help here. > Correct me if I am wrong. i dont know those specifics driver's state. AGP means two things: - high speed transfers (AGP 1x, 2x, 4x, sidebanding, fast writes, ...) - a paging logic that does provide consecutive page ranges (GART) built upon the systems main memory presented to CPU and grafics. Those Grafics Aperture Range Table system just creates an "un-scrambled" alias view of the main memory that typcially portraits parts of CPU paging. The first is often simply a question of switching on a few bits in the northbridge and the grafics controller. The location of the related bits in the integrated circuts do follow a standard. The second thing was implemented because Intel(?) thougt that it was a bad idea to have grafics adapters that are able to access scattered pages from anywhere in the system memory (even if most vendors already hat respective logic due to their PCI designs). So Intel required all mainboard chipset vendors to add paging shemes that were already present in CPU and grafics chips. Concerning your comment on texture organisation and AGP i've to comment, its just a question of program code in the driver. Anytime a texture is used, it is best to have it on the grafics adapter. As long as there is enough memory anything is fast. You best compare it to swapping - anytime you use something that is not present, the system hast to reload it with some timing penalty. In worst case you will trash and reload anything on any single frame, in worsest case you will do this multiple times. Having not enough memory is a big performance issue. Having a too dumb texture manager could be slowing down as well. In short words - the texture manager in your driver doesnt look like he is using all availabel resources for the purpose. BTW, geometry data and screen<->memory blits should be able to use the GART paged memory pool as well and the high speed AGP bus protocolls as well. Regards Alex. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot: part 3,success
> 3. There are serious problems with textures - in most (all?) apps they > are not loaded. Is it me or server or ...? BTW - I found the matter of problem. I have 8M video RAM. And use resolution 1280x1024 (I have LCD so lower resolutions look bad). Even in 16bpp, all buffers take almost 8M - so only 192K remains for textures (actually, on 32bpp the server does not start at all). When I experimentally changed resolution to 800x600 (giving ~5M video RAM for textures) - some textures appeared (but not all - for example, half-life and celestia are still not working). So my question is - will at some point driver use system RAM for buffers and/or textures etc? I thought AGP technology can help here. Correct me if I am wrong. Cheers, Sergey PS BTW, dpms seems to be working too - my laptop was able to suspend and resume correctly. Just in case someone is interested... ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot: part 3,success
On Thu, 2001-12-06 at 11:24, Michel Dänzer wrote: > On Thu, 2001-12-06 at 01:00, Sergey V. Udaltsov wrote: > > > 1. Probably, we could investigate the issue with striping. What could be > > wrong here? > > Nothing. Obviously strip removes information needed by the XFree86 > module loader, so XFree86 shouldn't be stripped, at least not with those > options. ^^^ This should read "XFree86 modules" of course. Sorry for any confusion. :) -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot: part 3,success
On Thu, 2001-12-06 at 01:00, Sergey V. Udaltsov wrote: > 1. Probably, we could investigate the issue with striping. What could be > wrong here? Nothing. Obviously strip removes information needed by the XFree86 module loader, so XFree86 shouldn't be stripped, at least not with those options. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] First experience with binary shapshot: part 3, success
Hi all Now I can state I have my DRI working. Thanks again to Jose for non-striped libGLcore. It seems striping is not loseless operation. So, finally my results: 1. glxinfo shows everything as necessary. 2. gl-dependant apps are really faster. 3. There are serious problems with textures - in most (all?) apps they are not loaded. Is it me or server or ...? 4. Even half-life works in opengl mode! No textures yet. I can see my handgun only:) 5. Strange things with cursor happen, as it was noted in this mailing list before (I had to set "SWCursor" option) 6. gltron freezes the server. Though I am still able to switch to another console, kill gltron and return back. But at this point the mouse is dead:( I don't know whether it's the app or the server or me... 6. The speed of 2D seems to be a bit slower (earlier I used drivers from www.linuxvideo.org). Is it true or just my illusion? In general, what I have to say is great THANKS to everyone involved. With this high speed of development we users have got real chances to get hardware-accelerated 3D on mach64. I'm just afraid 4.2 is very soon so these ATI drivers will not be there... So what I ask is: 1. Probably, we could investigate the issue with striping. What could be wrong here? 2. Could please someone make these binary snapshots periodically (probably, some cleanup of /usr/X11R6-DRI is necessary - I am still not sure everything is necessary there). About kernel modules: for me, RH7.2 with the latest kernel update would be good but probably a couple of other standard distros could be supporter as well... Thanks to everyone again. Keep on fighting! Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
On 2001.12.06 05:59 Dieter Nützel wrote: > Jose Fonseca wrote: > > > > BTW my X-Server is running now but I get strange authentification > > > failures: > > > the DRM module isn't allowed to write to X while I'm not logged in as > > > root. kdm also fails on startup with XDM-AUTHENTIFICATION failure > > > Does anybody know how to fix this quick ( I haven't had time yet to > read > > > something about that issue ) > > > > > > > Andreas, in your own login (i.e., not as root) type something like: > > > > xauth +your_hostname > > No, I think you are wrong: > > /home/nuetzel> hostname > SunWave1 > /home/nuetzel> xauth +SunWave1 > xauth: (argv):1: unknown command "+SunWave1" > Yes, you are right. I wanted to say: xhost +your_hostname The both commands are somewhat related therefore my confusion, sorry.. :) > Andreas have a look into your ~/.Xauthority file. I am sure > your_hostname is > already in it, no? > > My solution: > > Andreas are you running SuSE??? > > Then you need as myself as well a patch from SuSE for the XFree86/XFree86 > DRI > CVS tree that enables the XDM-AUTHENTIFICATION (DES encryption for better > > security) to get KDM running, again. > > I've looked into the SuSE 7.3 XFree86 (xf86-4.1.0-45.src.rpm) package but > > didn't found the right stuff, yet :-( > > > Perhaps this is sufficient. > > No, see above. > > Stefan can you help, here? Maybe these patches are under closure (NDA)? > > Regards, > Dieter Regards, Jose Fonseca _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
Jose Fonseca wrote: > > BTW my X-Server is running now but I get strange authentification > > failures: > > the DRM module isn't allowed to write to X while I'm not logged in as > > root. kdm also fails on startup with XDM-AUTHENTIFICATION failure > > Does anybody know how to fix this quick ( I haven't had time yet to read > > something about that issue ) > > > > Andreas, in your own login (i.e., not as root) type something like: > > xauth +your_hostname No, I think you are wrong: /home/nuetzel> hostname SunWave1 /home/nuetzel> xauth +SunWave1 xauth: (argv):1: unknown command "+SunWave1" Andreas have a look into your ~/.Xauthority file. I am sure your_hostname is already in it, no? My solution: Andreas are you running SuSE??? Then you need as myself as well a patch from SuSE for the XFree86/XFree86 DRI CVS tree that enables the XDM-AUTHENTIFICATION (DES encryption for better security) to get KDM running, again. I've looked into the SuSE 7.3 XFree86 (xf86-4.1.0-45.src.rpm) package but didn't found the right stuff, yet :-( > Perhaps this is sufficient. No, see above. Stefan can you help, here? Maybe these patches are under closure (NDA)? Regards, Dieter -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: [EMAIL PROTECTED] ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] First experience with binary shapshot: part 2
Hi all Finally, I took the stripped binaries (7M). Thanks to Jose again. What's the result? Nothing good. The server starts, but no dri. Actially some gl-related modules have got some problems on load: (II) Loading sub module "GLcore" (II) LoadModule: "GLcore" (II) Loading /usr/X11R6-DRI/lib/modules/extensions/libGLcore.a No symbols found in this module Failed to load debug_xform.o (EE) Failed to load /usr/X11R6-DRI/lib/modules/extensions/libGLcore.a (II) UnloadModule: "GLcore" (II) UnloadModule: "glx" (II) Unloading /usr/X11R6-DRI/lib/modules/extensions/libglx.a (EE) Failed to load module "glx" (a required submodule could not be loaded, -1073744008) So later atimisc_drv.o and others have a lot of troubles (errors) resolving gl-related symbols... I checked several times - ldconfig cache does not contain "old" Xfree/GL stuff. Any ideas/comments? I know I must look pretty dumb... Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
On Wed, 5 Dec 2001, Michael Thaler wrote: > I am new on the list. I am also very interested to test the mach64 dri > drivers. I have a Sony Vaio F212K with an Ati Rage Mobiltiy P/M. Where > can I get the drivers? What else do I need to test the drivers? You can check out the branch in CVS using the mach64-0-0-2-branch tag. Check dri.sf.net for compilation instructions. Note that you now need an existing X installation (4.1.0), e.g. one from your distro, to build DRI from CVS, so you'll need to make /usr/X11R6/include and /usr/X11R6/lib available to the build process. I did this by creating /usr/X11R6-DRI/lib and /usr/X11R6-DRI/include and using lndir to populate these directories with links. btw, is someone planning on updating the compilation guide to reflect this change? -- Leif Delgass http://www.retinalburn.net ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
> Sergey, it seems that you'll have to download the complete X server or > wait... OK. Anyway /usr/X11R6/bin/XFree86 is not that big. Or there are some other files I forgot. Also, could you please add /usr/X11R6/lib/modules/dri/*? I am sure - in the end we'll find the minimal list of binaries necessary for dri/mach64:) Thanks. Cheers, Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
Hi all, > Thanks to Jose, I got some binary stuff to test: > > lib/modules/2.4.9-13/kernel/drivers/char/drm/mach64.o > usr/X11R6/lib/modules/drivers/ati_drv.o > usr/X11R6/lib/modules/drivers/atimisc_drv.o > usr/X11R6/lib/modules/drivers/r128_drv.o > usr/X11R6/lib/modules/drivers/radeon_drv.o I am new on the list. I am also very interested to test the mach64 dri drivers. I have a Sony Vaio F212K with an Ati Rage Mobiltiy P/M. Where can I get the drivers? What else do I need to test the drivers? Thank you very much, Michael ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
On Wed, 2001-12-05 at 14:02, Andreas Karrenbauer wrote: > Sergey V. Udaltsov wrote: > > >Hi all > > > >Thanks to Jose, I got some binary stuff to test: > > > >lib/modules/2.4.9-13/kernel/drivers/char/drm/mach64.o > >usr/X11R6/lib/modules/drivers/ati_drv.o > >usr/X11R6/lib/modules/drivers/atimisc_drv.o > >usr/X11R6/lib/modules/drivers/r128_drv.o > >usr/X11R6/lib/modules/drivers/radeon_drv.o > > > >But I did not have much success: > >1. The kernel module loaded perfectly. No complains. > >2. The driver uses ABI v 5 but XFree 4.1.0 gives ABI version 4. First > > > I had a similar problem until recognizing that I alwas started the old > X-Server with the new modules because I just edited the > /etc/X11/XF86Config file. Try to start e.g. /usr/X11R6-DRI/bin/XFree86 > explictly... > Just a thought ;-) > Sergey, it seems that you'll have to download the complete X server or wait... > BTW my X-Server is running now but I get strange authentification failures: > the DRM module isn't allowed to write to X while I'm not logged in as root. > kdm also fails on startup with XDM-AUTHENTIFICATION failure > Does anybody know how to fix this quick ( I haven't had time yet to read > something about that issue ) > Andreas, in your own login (i.e., not as root) type something like: xauth +your_hostname Perhaps this is sufficient. > --Andreas Karrenbauer > > PS: Because of a new job I haven't had much time the past month, but > congratulations to Manuel Teira. He's done very well. I'm listening to > the list and hope to find time to contribute in any way > Regards, Jose Fonseca ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] First experience with binary shapshot
> > Probably, I also need X11R6/lib/modules/dri? > > Yes. > > driver -> dri -> kernel module > OpenGL -> dri -> kernel module Jose, please... Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Dri-devel] First experience with binary shapshot
Sergey V. Udaltsov wrote: >Hi all > >Thanks to Jose, I got some binary stuff to test: > >lib/modules/2.4.9-13/kernel/drivers/char/drm/mach64.o >usr/X11R6/lib/modules/drivers/ati_drv.o >usr/X11R6/lib/modules/drivers/atimisc_drv.o >usr/X11R6/lib/modules/drivers/r128_drv.o >usr/X11R6/lib/modules/drivers/radeon_drv.o > >But I did not have much success: >1. The kernel module loaded perfectly. No complains. >2. The driver uses ABI v 5 but XFree 4.1.0 gives ABI version 4. First > I had a similar problem until recognizing that I alwas started the old X-Server with the new modules because I just edited the /etc/X11/XF86Config file. Try to start e.g. /usr/X11R6-DRI/bin/XFree86 explictly... Just a thought ;-) BTW my X-Server is running now but I get strange authentification failures: the DRM module isn't allowed to write to X while I'm not logged in as root. kdm also fails on startup with XDM-AUTHENTIFICATION failure Does anybody know how to fix this quick ( I haven't had time yet to read something about that issue ) --Andreas Karrenbauer PS: Because of a new job I haven't had much time the past month, but congratulations to Manuel Teira. He's done very well. I'm listening to the list and hope to find time to contribute in any way ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
RE: [Dri-devel] First experience with binary shapshot
> From: Sergey V. Udaltsov [mailto:[EMAIL PROTECTED]] > > Probably, I also need X11R6/lib/modules/dri? Yes. driver -> dri -> kernel module OpenGL -> dri -> kernel module in the source tree you will find dri and kernel module at a subdir called os-support/. ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] First experience with binary shapshot
Hi all Thanks to Jose, I got some binary stuff to test: lib/modules/2.4.9-13/kernel/drivers/char/drm/mach64.o usr/X11R6/lib/modules/drivers/ati_drv.o usr/X11R6/lib/modules/drivers/atimisc_drv.o usr/X11R6/lib/modules/drivers/r128_drv.o usr/X11R6/lib/modules/drivers/radeon_drv.o But I did not have much success: 1. The kernel module loaded perfectly. No complains. 2. The driver uses ABI v 5 but XFree 4.1.0 gives ABI version 4. First problem. I had to use -ignoreABI switch. Probably, all subsequent issues causes by this option. 3. A lot of unresolved symbols. Complains about DRILock and DRIUnlock, also drmMach64InitDMA, drm*, DRI*... Did I forgot something to do/download? Probably, I also need X11R6/lib/modules/dri? Or something else? Or should I givup and not test with XFree 4.1.0 (waiting for 4.2.0)? Any comments are more than welcome. Sergey ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
