| 
      
      
      From: David J. <jo...@mc...> - 2004-07-19 17:32:43
      
     | 
| I only changed one line in raptor.cpp (225): #define GETPROCADDRESS(x) glXGetProcAddress((const GLubyte*) x) to #define GETPROCADDRESS(x) glXGetProcAddressARB((const GLubyte*) x) I also did a 'strings /usr/lib/libGL.so', and the only glXGetProcAddress that was listed was glXGetProcAddressARB (ie: nothing listed with the ARB stripped). -Dave On Mon, 19 Jul 2004, Mike Houston wrote: > Hmmm... For linux, I use glXGetProcAddress which should be everywhere. > On windows, wglGetProcAddress *should* work. Does anyone know what > the standard really is here? > > If GetProcAddressARB works for everyone, that's an easy code fix. > > Dave: Which lines in the raptor code are you changing? > > Thanks, > Mike > > David Jones wrote: > > > Ok, now I got it working. It seemed like GetProcAddress isn't in my GL > > distro, but GetProcAddressARB is. Since GetProcAddress is defined in the > > linked cr libs, that was getting invoked and subsequentally calling the > > chromium stuff. > > > > So a non-cr run of raptor *does* work for me when I change GetProcAddress > > to GetProcAddressARB. > > > > Weird. > > > > -Dave > > > > > > On Mon, 19 Jul 2004, Mike Houston wrote: > > > > > >>If you don't feed it "CR" at the end of the command line, there should > >>be no chromium stuff loaded. At least it runs that way for me. Are you > >>using Nvidia's GL library or Chromium's? > >> > >>-Mike > >> > >>David Jones wrote: > >> > >> > >>>I started that from the command line - no mothership. Since it's linked > >>>against the Cr libs, I'm guessing that the crfaker lib is invoking its > >>>opengl stub stuff. > >>> > >>>I don't know a way of getting around this without fiddling with raptor > >>>code.. > >>> > >>>-Dave > >>> > >>> > >>>On Mon, 19 Jul 2004, Mike Houston wrote: > >>> > >>> > >>> > >>>>Can you send me a run not using Chromium? > >>>> > >>>>-Mike > >>>> > >>>>David Jones wrote: > >>>> > >>>> > >>>> > >>>>>Yeah, this is an FX board (5900 Ultra on Linux) that supports > >>>>>GL_ARB_fragment_program and GL_ARB_vertex_program. > >>>>> > >>>>>I've attached the output of a run. I double checked the paths to > >>>>>everything and those seem to look ok. > >>>>> > >>>>>-Dave > >>>>> > >>>>>On Mon, 19 Jul 2004, Mike Houston wrote: > >>>>> > >>>>> > >>>>> > >>>>> > >>>>>>I'm willing to bet the some of the extensions failed to load, but it > >>>>>>should have assert failed... What type of Nvidia board is it? Raptor > >>>>>>requires an NV30+. There are some known issues with the latest Nvidia > >>>>>>drivers, but they shouldn't be causing failures with local rendering. > >>>>>> > >>>>>>Can you send me the output of Raptor please? I'll try to take a guess > >>>>>>at what I might think is happening. When I get back in town, I'll try > >>>>>>to track down an Nvidia board I can run in my Linux box and see if I can > >>>>>>track down these errors. Things seem to work fine with Nvidia hardware > >>>>>>under Windows... > >>>>>> > >>>>>>-Mike > >>>>>> > >>>>>> > >>>>>>David Jones wrote: > >>>>>> > >>>>>> > >>>>>> > >>>>>> > >>>>>>>I gave this a shot on some of our machines. Running it locally without > >>>>>>>any chromium gives me a blank window. Running the raptor_1.conf config > >>>>>>>starts the app. but quickly bails with the crserver dumping: > >>>>>>> > >>>>>>>CR Debug(nitrogen:3568): Done calling crTCPIPConnection > >>>>>>>CR Debug(nitrogen:3568): Done connecting to server. > >>>>>>>CR Debug(nitrogen:3568): Received a drawable: 35651585 > >>>>>>>X Error of failed request: BadMatch (invalid parameter attributes) > >>>>>>>Major opcode of failed request: 144 (GLX) > >>>>>>>Minor opcode of failed request: 5 (X_GLXMakeCurrent) > >>>>>>>Serial number of failed request: 30 > >>>>>>>Current serial number in output stream: 30 > >>>>>>> > >>>>>>>I've tried the raptor_1.conf with both a local and remote 'crappfaker'. > >>>>>>>I'm using a Nvidia 5900 Ultra with the 61.06 Linux drivers. > >>>>>>> > >>>>>>>I've also run raptor on my home desktop (Radeon 9600) under windows and it > >>>>>>>seems to work fine there. > >>>>>>> > >>>>>>>-Dave > >>>>>>> > >>>>>>> > >>>>>>>On Sat, 17 Jul 2004, Mike Houston wrote: > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>>I very happy to announce that Raptor, the parallel volume rendering > >>>>>>>>system written at Stanford using Chromium, has been released. > >>>>>>>> > >>>>>>>>http://graphics.stanford.edu/raptor > >>>>>>>> > >>>>>>>>The source code, (limited) documentation, and some (large) datasets are > >>>>>>>>available. Give it a go and let me know if there are any issues. This > >>>>>>>>has not been thoroughly tested on Nvidia based clusters, so I'm curious > >>>>>>>>how that will go. > >>>>>>>> > >>>>>>>>-Mike > >>>>>>>> > >>>>>>>> > >>>>>>>>------------------------------------------------------- > >>>>>>>>This SF.Net email is sponsored by BEA Weblogic Workshop > >>>>>>>>FREE Java Enterprise J2EE developer tools! > >>>>>>>>Get your free copy of BEA WebLogic Workshop 8.1 today. > >>>>>>>>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > >>>>>>>>_______________________________________________ > >>>>>>>>Chromium-dev mailing list > >>>>>>>>Chr...@li... > >>>>>>>>https://lists.sourceforge.net/lists/listinfo/chromium-dev > >>>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>>------------------------------------------------------- > >>>>>>>This SF.Net email is sponsored by BEA Weblogic Workshop > >>>>>>>FREE Java Enterprise J2EE developer tools! > >>>>>>>Get your free copy of BEA WebLogic Workshop 8.1 today. > >>>>>>>http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click > >>>>>>>_______________________________________________ > >>>>>>>Chromium-users mailing list > >>>>>>>Chr...@li... > >>>>>>>https://lists.sourceforge.net/lists/listinfo/chromium-users > >>>>>> > >> > > |