Good news I now have the network working. I'm seeing a number of
transmit timeouts (see below) but don't seem to be losing packets.
I found that as well as clearing bit 21 in csr0 that I also had to
clear bit 24. That makes the csr0 assignment
static int csr0 = 0x0080 | 0x9000
I suspect that
David Smith <[EMAIL PROTECTED]> writes:
> Today I performed a fresh install of sid on an ultra1 200e creator
> and I upgraded the kernel to the CVS version of vger.samba.org. I
> couldn't find any reference to the bugs below in the database, has
> anyone else experienced these?
>
> 1) Running any
Hi again.
I installed a fresh copy of Woody on my blade, and immediately changed
the sources.list to reference sid. (I could not install sid from the
tftpboot images due to the script's failure to "mount -t proc proc
/proc" which apparently was already mounted.)
Everything upgraded fine, but onc
On Wed, 1 Aug 2001, David Smith wrote:
> not only given in the framerate difference (~350 vs. 60) but also in the
> XFree86.0.log (as you can see in the bottom of
> http://ultrasoul.com/ultra1/XFree86.0.log) when it creates the DRI GLX
> context:
> FFB: Allocated WID 1 for DRI window.
ok, i am no
Thus spake John Wood ([EMAIL PROTECTED]):
>
>
>
> i have found that i am unable to get any gl based x applications to use
> the hardware. i was mostly testing with xscreensaver-gl applications.
> later, i was able to get some results from the evas stuff, but only when i
> select something bes
hi david
On Wed, 1 Aug 2001, David Smith wrote:
> find any reference to the bugs below in the database, has anyone else
> experienced these?
yes and no. i have a ultra1/170 & creator 3d. i am running unstable with
vgers kernel as well.
> 1) Running any OpenGL program with DRI hardware acclerat
6 matches
Mail list logo
