the standard labs driver checks the speed during auto negotiation. so it is often wrong.
- erik On Feb 18, 2016 3:41 PM, arisawa <aris...@ar.aichi-u.ac.jp> wrote: > > hello, > > rtl8169 is popular in cheap MB, so it is installed in my many MBs. > however, cat /dev/kmesg claims: > rtl8169: oui 0x732 phyno 1, macv = 0x3c000000 phyv = 0x0002 > #l0: rtl8169: 100Mbps port 0xD000 irq 10: 001fd0169891 > > the “100Mbps" in the message is correct or not? > > I also feel rtl8169 is slow, so I replace on-board rtl8169 by intel’s card > if possible. > > > > > 2016/02/18 22:22、erik quanstrom <quans...@quanstro.net> のメール： > > > > the 8169 driver is pretty fast. I've measured it at more than 500mbps. > > it sounds like something else is misbehaving. what does > > /dev/irqstat say. I bet something is stuck. > > > > - erik > > > > > > On Feb 18, 2016 3:30 AM, tlaro...@polynum.com wrote: > >> > >> Hello, > >> > >> I have finally managed to install plan9 on my new workstation. > >> > >> By putting back the keyboard on the PS2 connector, I have solved some > >> unfelicities (with the USB->legacy emulation, the keyboard switched > >> every other typing to UPPERCASE...). > >> > >> The mouse, still USB connected and hence "emulated" by the BIOS, > >> does not react very gracefully but I will see if I can play with > >> the acceleration and the resolution to have a better terminal. (Or > >> if I manage to find a long enough cable to have a COM slot back since > >> there is the bare connector on the motherboard; in this case I will go > >> back to a com mouse and will be able to probe USB for other > >> devices---external disks.) > >> > >> One thing is inconvenient: I have a rtl8169 gbe pci-e ether card, but > >> when testing the compilation of kerTeX (it has been fixed: it works for > >> the last release; rio to come for METAFONT), the throughput with hget is > >> abysmal: 30kB/s... The disk is not a fault, reacting well enough (I have > >> plenty of RAM and the blocks cache for fossil is set to 3000---it could > >> be obviously higher). > >> > >> Setting the mtu to jumbo packet does not help. > >> > >> Is there something to tune or is it simply that the chip is not well > >> supported? > >> > >> TIA > >> -- > >> Thierry Laronde <tlaronde +AT+ polynum +dot+ com> > >> http://www.kergis.com/ > >> http://www.arts-po.fr/ > >> Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C > >> > >> > > >
