Re: Dysfunctional ne (RTL8019AS)
Make sure nothing is trying irq 7 and then give it a shot. Double check
to see if the sblive is NOT trying to use 0x300 for it's midi port.
Does the ne need to be isapnp enabled or is it a jumpered card?
--mike
On 09 Aug 2001 02:07:22 +0200, Hugo van der Merwe wrote:
> Hello,
>
> I recently replaced my old SB16 with a Sound Blaster Live, which caused
> quite some reassignments of IRQ's etc. I have two network cards in the
> machine, one that "ne2k-diag" claims is an RTL8019AS (bought as an
> ne2000 compatible, and served faithfully until now). (The other is an
> rtl8139, and I use the 8139too driver.)
>
> I've now shifted the ne to IRQ 5, it's base is still 0x300 - it seems to
> work fine, but if I try to use it, I get e.g. the following:
>
> hugo@baboon[4]:~/znobackup$ ssh chimp
> NETDEV WATCHDOG: eth1: transmit timed out
> NETDEV WATCHDOG: eth1: transmit timed out
> ...
>
> Should I simply go on and try different IRQ's? (IRQ 7 is for parallel
> port, right? So that won't work?) Or how else can I diagnose this
> problem?
>
> Oh, another thing, my rtl8139 causes the following when the network is
> heavily congested:
>
> Aug 8 22:22:52 baboon kernel: NETDEV WATCHDOG: eth0: transmit timed out
> Aug 8 22:22:52 baboon kernel: eth0: Tx queue start entry 407299 dirty entry 407295.
> Aug 8 22:22:52 baboon kernel: eth0: Tx descriptor 0 is 00002000.
> Aug 8 22:22:52 baboon kernel: eth0: Tx descriptor 1 is 00002000.
> Aug 8 22:22:52 baboon kernel: eth0: Tx descriptor 2 is 00002000.
> Aug 8 22:22:52 baboon kernel: eth0: Tx descriptor 3 is 00002000. (queue head)
> Aug 8 22:22:52 baboon kernel: eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
>
> Any ideas?
>
> Thanks a lot,
> Hugo van der Merwe
>
> --
> To send me private (non-world-readable) mail, GPG encrypt it.
> 1024D/60715698: 5F2E 8EC2 E0A4 5D25 0569 F281 4A6C D76D 6071 5698
Reply to: