Subject: Re: rtk0 and swap space problems, along with a question about wscons
To: Josh Tolbert <hemi@scoundrelz.net>
From: Marcus Comstedt <marcus@mc.pp.se>
List: port-dreamcast
Date: 09/01/2002 23:41:44
Josh Tolbert <hemi@scoundrelz.net> writes:

> 2) Aug 31 21:31:39 dreamcast /netbsd: rtk0: transmit underrun; new
> threshold: 320 bytes
> Aug 31 21:35:17 dreamcast /netbsd: nfs server
> 192.168.0.21:/mnt/exports/dc: not responding
> Aug 31 21:39:08 dreamcast /netbsd: nfs server
> 192.168.0.21:/mnt/exports/dcswap/swap: not responding
> Aug 31 21:39:08 dreamcast /netbsd: nfs server
> 192.168.0.21:/mnt/exports/dc: is alive again
> Aug 31 21:39:08 dreamcast /netbsd: nfs server
> 192.168.0.21:/mnt/exports/dcswap/swap: is alive again
> 
> Those transmit underrun/new threshold messages make me nervous. The fact
> that I lost / and swap NFS shares really makes me nervous. Are the two
> missing shares a result of the rtk0 message? The spacing seems to be a
> pattern; rtk0 changes the threshold, about four minutes later
> /mnt/exports/dc goes away, and about four minutes after that swap goes
> away, both of which return apparently as soon as network traffic dies off.
> There's nothing in the nfs/dhcpd server's logs about network errors or the
> like. The nfs/dhcpd NetBSD machine has an Intel Pro/100+ NIC.
> 	Is the Realtek network hardware choking? It appears to be. Is
> there a workaround or anything I can do? Someone get Intel to make some
> BBAs. :)

Yeah, the Realtek chip can't really sustain a 100 Mbps link.  Talk 10
Mbps to it and it should behave better.


> 	Now, wscons...How do we get it to work? Is it strictly a hardware
> driver problem, or is there something inherent to wscons that specifically
> precludes support for the PowerVR2 video hardware in the Dreamcast? I've

Uh, no, since the Dreamcast port _is_ using wscons, I dare say there's
nothing precluding support for it.  :-)


> been poking around in #linuxdc on irc.openprojects.net and they apparently
> have a good framebuffer driver for this video hardware (among other things
> that our port currently lacks).

It might be useful if you explain what you find lacking in the current
driver.  (I'm not saying that it _isn't_, just that it helps if you
are a bit more specific...)  Are you talking about hardware 3D
support?


  // Marcus