Mh .. setting the default to r_smp 1 when SMP detected may have been an oversight. This has been tested to work on nvidia cards, it's likely to break on anything else. I'd be interested to hear about work/not work in various situations.
Use +set developer 1 +set logfile 2 on the command line to get a log file from q3. TTimo On 08 Oct 2002 16:30:58 +0200 Mourad De Clerck <[EMAIL PROTECTED]> wrote: > Hi, > > I was quite interested to see this in the changelog of the latest Quake3 > point release: > > - SMP support in the renderer. Detects CPU count, r_smp 1 default if > available. (thanks to Gareth Hughes for contributing this) > > Starting up with +set r_smp 0 is still ok. However, when I start up > trying to use r_smp 1 quake3 exits (not very cleanly, but ok) it tells > me: > > mga_get_buffer_ioctl: flush ret=-22 > > bang. dead. It doesn't lock my computer, but mouse input etc doesn't > work till I restart X. > > hardware is: > - 2x P3-800 on a BX chipset (not overclocked or anything - running > 100mhz FSB) > - a matrox G550 > > software is: > - Debian with Xfree 4.2.1 (I tried both the matrox distributed drivers > and the Xfree ones.) > - Linux 2.4.19 SMP > > One final note: since it is the default behaviour of quake3 to start > with r_smp 1 when >1 cpu's are detected, I'd expect it to break for > everyone using SMP and matrox. (maybe it even only works on nvidia?) > > Thanks, > > -- Mourad > > > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
