On Sat, Nov 09, 2002 at 04:27:27PM -0500, N. Thomas wrote: > * Edward Guldemond <[EMAIL PROTECTED]> [2002-11-09 14:57:26 -0500]: > > On Sat, Nov 09, 2002 at 09:45:36AM -0500, N. Thomas wrote: > > > Debian <-> RedHat = 200Kbs ??? > > > Debian <-> Windows = 200Kbs ??? > > > > Maybe it's not the Debian box that is misconfigured, maybe it's the > > RedHat or Windows boxen? Are there any weird messages in the Linux > > syslogs, or the Windows log viewer? What NICs are you using on the > > machines? > > Actually, apart from a CD burner on the Redhat box, it and the Debian > machines are identical. The NICS are built into the motherboard, the company > is called SiS. > > The RedHat/Windows logs revealed nothing, but I found this nugget in > /var/log/syslog of the Debian box: > > Nov 9 12:54:39 seneca kernel: sis900.c: v1.06.09 09/28/2001 > Nov 9 12:54:39 seneca kernel: eth0: SiS 900 PCI Fast Ethernet at 0xcc00, IRQ 5, >00:0a:e6:12:e3:cd. > Nov 9 12:54:39 seneca kernel: eth0: Unknown PHY transceiver found at address 1. > Nov 9 12:54:39 seneca kernel: eth0: Using transceiver found at address 1 as >default > > What does it mean? I saw it upon bootup as well.
It just means that the driver was confused about that it was supposed to
find on the chip. It found what it needed though, so it looks like
everything is fine here. A question though: Does this appear when you
start transferring the file, or only at bootup?
> > One thing I would suggest is to try a different hub. I doubt it's the hub
> > though...
>
> I'm using a switch, and swapping ports doesn't seem to change anything.
> Still, I might end up having to return it to the store if the problem
> persists. =-(
I meant to say switch instead of hub, but here's one more thing to try
when diagnosing the problem. Try connecting the machines with crossover
cables. You might not get full-duplex, but see if the numbers go up at
all. If they don't try installing a good PCI network card into the
Debian machine and see if that helps.
--
------------------------------------------
Edward Guldemond
GPG Key: 0x4E505B0F
Key fingerprint: 4CAC 6740 C1CD 3CE4 6CA0
34E9 B3B7 18EC 4E50 5B0F
msg12023/pgp00000.pgp
Description: PGP signature
