jon | 1 Apr 2002 20:11

NetbSD1.5.2/Geforce3 // X garbled screen problem

Apologies in advance if this is stupid or redundant.  =/

X throws up garbage all over the screen which I can't get rid of. I'm using
a Geforce3 on AGP, and neither the Geforce256 nor the GeforceDDR drivers
(447+448 I think) are working.

Please CC any replies to tyr124840 <at> tyler.net as I'm not on the mailing list.

Brian A. Seklecki | 1 Apr 2002 20:55

Re: NetbSD1.5.2/Geforce3 // X garbled screen problem

On Mon, 1 Apr 2002, jon wrote:

> Apologies in advance if this is stupid or redundant.  =/
>
> X throws up garbage all over the screen which I can't get rid of. I'm using
> a Geforce3 on AGP, and neither the Geforce256 nor the GeforceDDR drivers

Check PR 15482:

"Environment:
System: NetBSD silenus 1.5ZA NetBSD 1.5ZA (LOCAL) #0: Tue Jan 29 00:28:04
CET 2002 root <at> silenus:/usr/src/sys/arch/i386/compile/LOCAL i386
Architecture: i386
Machine: i386
Graphics Card: NVidia GeForce II MX 100
"

http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=15482

There have been many reports w/ problems related to 4.2.0, i think the
main PR is 15404 (for the nv driver, at least).

> (447+448 I think) are working.
>
> Please CC any replies to tyr124840 <at> tyler.net as I'm not on the mailing list.
>

jon | 2 Apr 2002 01:34

Not using 4.2.0

I'm using the one in the standard 1.5.2 distribution, 3.3.6. XF86 4.2.0
works fine, at least it does when run on Linux.

Perry E. Metzger | 2 Apr 2002 04:39
Gravatar

Re: Transparent consoles.


Richard Rauch <rauch <at> rice.edu> writes:
> My impression/assumption is that this should make the background of the
> terminal transparent to whatever is behind it.  However, with *any* such
> terminal, it only provides me with the root window's contents.  (I.e., it
> won't show any underlying windows.)

The issue is that older X servers (older than nearly the most recent
ones, in fact) have no notion of alpha channel/transparency at
all. The latest ones do, but the clients haven't caught
up. Transparency on such things is managed with horrible hacks, and
thus the results you see.

Perry

Richard Rauch | 2 Apr 2002 05:13
Favicon

Re: Transparent consoles.

> > My impression/assumption is that this should make the background of the
 [...]
> The issue is that older X servers (older than nearly the most recent
> ones, in fact) have no notion of alpha channel/transparency at
> all. The latest ones do, but the clients haven't caught
> up. Transparency on such things is managed with horrible hacks, and
> thus the results you see.

Ah, so maybe someday this will work as I expected.  Cool.  (^&

(I somehow had the vague impression of seeing screenshots a year or so
back, showing Eterm or similar getting the kind of transparency that I was
expecting.  But my memory is fuzzy even at best.)

Thanks for the updated information, in any case.

  ``I probably don't know what I'm talking about.'' --rauch <at> math.rice.edu

Brieuc Jeunhomme | 3 Apr 2002 19:32
Picon
Picon

X server quits with memory error

Hi. I have a strange problem with the XF86_SVGA X server shipped with
NetBSD-1.5.2 (the recommended server for my neomagick card): when I run
startx, the server immediately quits with a memory error message:

$ startx
XFree86 Version 3.3.6a / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: November 30 2000
	If the server is older than 6-12 months, or if your card is newer
	than the above date, look for a newer version before reporting
	problems.  (see http://www.XFree86.Org/FAQ)
Operating System: NetBSD/i386 1.5.2 [ELF] The NetBSD Foundation, Inc.
Configured drivers:
  SVGA: server for SVGA graphics adaptors (Patchlevel 1):
      NV1, STG2000, RIVA 128, RIVA TNT, RIVA TNT2, RIVA ULTRA TNT2,
      RIVA VANTA, RIVA ULTRA VANTA, RIVA INTEGRATED, GeForce 256,
      GeForce DDR, Quadro, GeForce2 GTS, GeForce2 GTS (rev1),
      GeForce2 Ultra, Quadro 2 Pro, GeForce2 MX, GeForce2 MX DDR,
      Quadro 2 MXR, ET4000, ET4000W32, ET4000W32i, ET4000W32i_rev_b,
      ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, ET4000W32p_rev_b,
      ET4000W32p_rev_c, ET4000W32p_rev_d, ET6000, ET6100, et3000, pvga1,
      wd90c00, wd90c10, wd90c30, wd90c24, wd90c31, wd90c33, gvga, r128, ati,
      sis86c201, sis86c202, sis86c205, sis86c215, sis86c225, sis5597,
      sis5598, sis6326, sis530, sis620, sis300, sis630, sis540, tvga8200lx,
      tvga8800cs, tvga8900b, tvga8900c, tvga8900cl, tvga8900d, tvga9000,
      tvga9000i, tvga9100b, tvga9200cxr, tgui9400cxi, tgui9420, tgui9420dgi,
      tgui9430dgi, tgui9440agi, cyber9320, tgui9660, tgui9680, tgui9682,
      tgui9685, cyber9382, cyber9385, cyber9388, cyber9397, cyber9520,
      cyber9525, 3dimage975, 3dimage985, cyber9397dvd, blade3d, cyberblade,
      clgd5420, clgd5422, clgd5424, clgd5426, clgd5428, clgd5429, clgd5430,
(Continue reading)

Sean Davis | 4 Apr 2002 03:33

Crashes in X 4.1.0, 4.2.0 on i386

Hi, I'm wondering what the deal is with all the instability in X 4.x lately.
When xsrc was 4.1.0, X _NEVER_ crashed, unless I ran quake3a-demo. Since
4.2.0 went in, X crashes periodically, but not often while I'm doing the
same kind of thing - so it isn't repeatable. Typically, X will crash at
least once every two days. I have since backed out to 4.1.0, because the
problem seemed more frequent in 4.2.0, but for the last couple weeks, 4.1.0
is behaving just as badly. My video card is a Riva TNT2 Vanta, if that makes
any difference. Does anyone know why this is happening, or possibly how to
fix it? I need X, and 3.3.6 is not an option due to the fact that it's at
least 30% slower on my TNT2.

Thanks,
-Sean

--

-- 
/~\ The ASCII                         Sean Davis
\ / Ribbon Campaign                    aka dive
 X  Against HTML
/ \ Email!               http://eros.endersgame.net:8000/~dive

Matthias Scheler | 4 Apr 2002 12:40
Picon
Favicon

Re: NetbSD1.5.2/Geforce3 // X garbled screen problem

In article <20020401135233.Q7459-100000 <at> digitalfreaks.org>,
	"Brian A. Seklecki" <lavalamp <at> spiritual-machines.org> writes:
> There have been many reports w/ problems related to 4.2.0, i think the
> main PR is 15404 (for the nv driver, at least).

PR xsrc/15404 was closed as fixed in the meantime. Can somebody please check
if PR xsrc/15482 was really caused by the same error?

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Matthias Scheler | 4 Apr 2002 12:41
Picon
Favicon

Re: X server quits with memory error

In article <20020403193246.A5666 <at> via.ecp.fr>,
	Brieuc Jeunhomme <bbp <at> via.ecp.fr> writes:
> Fatal server error:
> xf86MapVidMem: Address 0xfea00000 outside allowable range

You have to compile your kernel with "options INSECURE" or use the
"aperture" kernel module ("pkgsrc/sysutils/aperture").

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Matthias Scheler | 4 Apr 2002 12:45
Picon
Favicon

Re: Crashes in X 4.1.0, 4.2.0 on i386

In article <20020404013336.GA1496 <at> endersgame.net>,
	Sean Davis <dive-nb <at> endersgame.net> writes:
> Does anyone know why this is happening,

See PR xsrc/15404.

> ... or possibly how to fix it?

Yes. You need to update your math libraries or remove this line from
"/etc/ld.so.conf":

libm.so.0       machdep.fpu_present     1:libm387.so.0,libm.so.0

But because this will slow down any program using floating point math
you should only use it a last resort. Updating the math libraries
- you need to build and install in "src/lib/libm" - is really the
better option.

	Kind regards

--

-- 
Matthias Scheler                                  http://scheler.de/~matthias/


Gmane