>You can always try writing all the registers with "good" values.
No good - nothing actually changes except 16 bits at 0x6C, and that doesn't
change to anything useful.
>> Is there a reset 'thing' for thses chips, that sets them back to
>> factory tests (like switching them off)?
>[snip]
>>
On Sat, 3 Feb 2001 [EMAIL PROTECTED] wrote:
> I noticed that the mac address was stored in the registers and
> eprom. I guess it would not be as easy as just writing the mac
> back in the blank eprom and registers?
What my changed via-diag tries to do is to tell the chip to reload things
from
On 3 Feb 2001, at 14:02, Urban Widmark wrote:
> This is intresting. Your card reports that it is stopped while the
> other report show normal values on most things. Does this change if
> you try and send something (like a ping)? Common to both reports is
> that the transceivers don't respond.
>
On Sat, 3 Feb 2001, Jonathan Morton wrote:
> Do you want me to try this again, after first setting the card into
> non-working condition?
Yes, the idea was to start from non-working, test -I and then ifconfig
down/up. Getting the working card to work is a much simpler problem :)
/Urban
-
To
>The attached patch for the via-daig program plays with a few registers.
>
>Run it as 'via-diag -aaeemm -I' then do a 'ifconfig eth0 down; ifconfig
>eth0 up' and see if anything happens.
OK, after a little trouble applying the patch, here's what I found:
Starting with the card in working
On Sat, 3 Feb 2001 [EMAIL PROTECTED] wrote:
> VIA VT3065 Rhine-II chip registers at 0xd400
> 0x000: 0804
>
> 0x020: 0400
>
> 0x040:
On Sat, 3 Feb 2001 [EMAIL PROTECTED] wrote:
VIA VT3065 Rhine-II chip registers at 0xd400
0x000: 0804
0x020: 0400
0x040:
The attached patch for the via-daig program plays with a few registers.
Run it as 'via-diag -aaeemm -I' then do a 'ifconfig eth0 down; ifconfig
eth0 up' and see if anything happens.
OK, after a little trouble applying the patch, here's what I found:
Starting with the card in working condition,
On Sat, 3 Feb 2001, Jonathan Morton wrote:
Do you want me to try this again, after first setting the card into
non-working condition?
Yes, the idea was to start from non-working, test -I and then ifconfig
down/up. Getting the working card to work is a much simpler problem :)
/Urban
-
To
On 3 Feb 2001, at 14:02, Urban Widmark wrote:
This is intresting. Your card reports that it is stopped while the
other report show normal values on most things. Does this change if
you try and send something (like a ping)? Common to both reports is
that the transceivers don't respond.
The
You can always try writing all the registers with "good" values.
No good - nothing actually changes except 16 bits at 0x6C, and that doesn't
change to anything useful.
Is there a reset 'thing' for thses chips, that sets them back to
factory tests (like switching them off)?
[snip]
So.How
On 2 Feb 2001, at 20:17, Urban Widmark wrote:
>
> > >I did this and compiled it into the kernel. It detects it at boot
> > >(via- rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
> > >hardware address (mac address?) is 00-00-00-00-00-00.
>
> This is a good example of what is missed by
> >I did this and compiled it into the kernel. It detects it at boot (via-
> >rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
> >hardware address (mac address?) is 00-00-00-00-00-00.
This is a good example of what is missed by not copying the exact message.
For example, mine says:
>I have a D-Link DFE-530TX Rev A, PCI ethernet card, but it refuses
>to work.
>
>I have looked at http://www.scyld.com/network/index.html#pci
>which sugests using the via-rhine driver.
>
>I did this and compiled it into the kernel. It detects it at boot (via-
>rhine v1.08-LK1.1.6 8/9/2000 Donald
hi,
I have a D-Link DFE-530TX Rev A, PCI ethernet card, but it refuses
to work.
I have looked at http://www.scyld.com/network/index.html#pci
which sugests using the via-rhine driver.
I did this and compiled it into the kernel. It detects it at boot (via-
rhine v1.08-LK1.1.6 8/9/2000 Donald
hi,
I have a D-Link DFE-530TX Rev A, PCI ethernet card, but it refuses
to work.
I have looked at http://www.scyld.com/network/index.html#pci
which sugests using the via-rhine driver.
I did this and compiled it into the kernel. It detects it at boot (via-
rhine v1.08-LK1.1.6 8/9/2000 Donald
I have a D-Link DFE-530TX Rev A, PCI ethernet card, but it refuses
to work.
I have looked at http://www.scyld.com/network/index.html#pci
which sugests using the via-rhine driver.
I did this and compiled it into the kernel. It detects it at boot (via-
rhine v1.08-LK1.1.6 8/9/2000 Donald Becker)
I did this and compiled it into the kernel. It detects it at boot (via-
rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
hardware address (mac address?) is 00-00-00-00-00-00.
This is a good example of what is missed by not copying the exact message.
For example, mine says:
eth0: VIA
On 2 Feb 2001, at 20:17, Urban Widmark wrote:
I did this and compiled it into the kernel. It detects it at boot
(via- rhine v1.08-LK1.1.6 8/9/2000 Donald Becker) but says the
hardware address (mac address?) is 00-00-00-00-00-00.
This is a good example of what is missed by not copying
19 matches
Mail list logo
