[gentoo-dev] 8139too driver

[gentoo-dev] 8139too driver

[Robert Cole]

Does someone here know what compiler options the 1.4 rc3 used for the 8139too 
network driver by chance? I've tried everything I can think of with the 
gentoo-sources and I can only get the driver to work when I boot the rc3 CD 
but not when I boot into the system after an emerge system.

Did they use a different version than whats in the 2.4.20 gentoo sources?

I keep getting a watchdog timeout error message.
NETDEV WATCHDOG: eth0: transmit timed out.
then several tx descriptor messages
then a message that full duplex 100 mbps has been established.

Any ideas?

Thanks,
Robert

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] 8139too driver

[Zach Welch]

Robert Cole wrote:
 > Does someone here know what compiler options the 1.4 rc3 used for the
 >  8139too network driver by chance? I've tried everything I can think
 > of with the gentoo-sources and I can only get the driver to work when
 >  I boot the rc3 CD but not when I boot into the system after an
 > emerge system.
 >
 > Did they use a different version than whats in the 2.4.20 gentoo
 > sources?
 >
 > I keep getting a watchdog timeout error message. NETDEV WATCHDOG:
 > eth0: transmit timed out. then several tx descriptor messages then a
 > message that full duplex 100 mbps has been established.
 >
 > Any ideas?
 >

I fixed this problem on my hardware by using a kernel those does not
include the IO-APIC functionality.  This option was causing problems for
me on my SiS chipset mobo and resulted in the exact symptom you mention.

Cheers,

Zach Welch
Gentoo ARM Developer
Superlucidity Services


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] 8139too driver

[Brian Jackson]

You can test for this by adding "noapic" to your bootflags. That way you don't 
have to recompile just to test this theory out.

--Brian

On Saturday 08 March 2003 06:36 pm, Zach Welch wrote:
> Robert Cole wrote:
>  > Does someone here know what compiler options the 1.4 rc3 used for the
>  >  8139too network driver by chance? I've tried everything I can think
>  > of with the gentoo-sources and I can only get the driver to work when
>  >  I boot the rc3 CD but not when I boot into the system after an
>  > emerge system.
>  >
>  > Did they use a different version than whats in the 2.4.20 gentoo
>  > sources?
>  >
>  > I keep getting a watchdog timeout error message. NETDEV WATCHDOG:
>  > eth0: transmit timed out. then several tx descriptor messages then a
>  > message that full duplex 100 mbps has been established.
>  >
>  > Any ideas?
>
> I fixed this problem on my hardware by using a kernel those does not
> include the IO-APIC functionality.  This option was causing problems for
> me on my SiS chipset mobo and resulted in the exact symptom you mention.
>
> Cheers,
>
> Zach Welch
> Gentoo ARM Developer
> Superlucidity Services
>
>
> --
> gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] 8139too driver

[Zach Welch]

Brian Jackson wrote:
 > On Saturday 08 March 2003 06:36 pm, Zach Welch wrote:
 >> Robert Cole wrote:
 >>> Any ideas?
 >>
 >> I fixed this problem on my hardware by using a kernel those does
 >> not include the IO-APIC functionality.  This option was causing
 >> problems for me on my SiS chipset mobo and resulted in the exact
 >> symptom you mention.
 >>
 > You can test for this by adding "noapic" to your bootflags. That way
 > you don't have to recompile just to test this theory out.

I tested this option and, if I recall correctly, it did not fix the
problems.  The only solution I found was to recompile; however, this
suggestion is worth testing before going that far.

Cheers,

Zach


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] 8139too driver

[Robert Cole]

That was it! :) Thank you very much. 

Robert

On Saturday 08 March 2003 04:36 pm, Zach Welch wrote:
> Robert Cole wrote:
>  > Does someone here know what compiler options the 1.4 rc3 used for the
>  >  8139too network driver by chance? I've tried everything I can think
>  > of with the gentoo-sources and I can only get the driver to work when
>  >  I boot the rc3 CD but not when I boot into the system after an
>  > emerge system.
>  >
>  > Did they use a different version than whats in the 2.4.20 gentoo
>  > sources?
>  >
>  > I keep getting a watchdog timeout error message. NETDEV WATCHDOG:
>  > eth0: transmit timed out. then several tx descriptor messages then a
>  > message that full duplex 100 mbps has been established.
>  >
>  > Any ideas?
>
> I fixed this problem on my hardware by using a kernel those does not
> include the IO-APIC functionality.  This option was causing problems for
> me on my SiS chipset mobo and resulted in the exact symptom you mention.
>
> Cheers,
>
> Zach Welch
> Gentoo ARM Developer
> Superlucidity Services


--
gentoo-dev@gentoo.org mailing list