Subject: Re: Qube2 Network Performance & Forwarding
To: None <port-cobalt@NetBSD.org>
From: Izumi Tsutsui <firstname.lastname@example.org>
Date: 04/28/2006 17:41:33
In article <0BBE9272-AE52-43DB-A255-09F8574F3D71@pacang.com>
> I've always felt that the chipset needs to be re-initialized during
> boot, instead of relying on the rom initialization; the linux version
> for the qube2 does this re-initialization. One symptom of this are
> the lights on the ethernet ports: on my qube, one of them doesn't
> have connected light turned on due to incorrect autosense detection.
> One Linux, eeprom fixups are performed to fix this.
With a quick grance, if cobalt quirk is handled in
sys/dev/pci/if_tlp_pci.c, no other SROM contents are
used in sys/dev/ic/tulip.c, and if it always uses 10baseT
we can't get rate >1MB/sec, I think.
What does "ifconfig -m tlp1" say on your Qube (or Qube2)?
Can you check SROM contents of both tlp by enabling
"tlp_srom_debug = 1" in tulip.c?