Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4

2001-01-15 Thread Danny ter Haar
I experimented some further today. using some printk i found out is was setting Fullduplex, hardcoded that to half-duplex (mine is connected to a hub and not a switch) , and it's configuration was 100Mbit as it was supposed to. Then i started looking at the start_xmit code and got lost :-))) Ho

Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4

2001-01-12 Thread Thomas Bogendoerfer
On Fri, Jan 12, 2001 at 12:50:10PM +0100, Danny ter Haar wrote: > eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d > pcnet32: pcnet32_private lp=c3c42000 lp_dma_addr=0x3c42000 assigned IRQ 9. > pcnet32.c:v1.25kf 26.9.1999 [EMAIL PROTECTED] same chip works for me von my P5 SMP box. > ir

Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4

2001-01-12 Thread Danny ter Haar
Hans Grobler <[EMAIL PROTECTED]> wrote: >> lspci -vx output: >What about the other devices? ok, here's the full listing : 00:00.0 Host bridge: Cyrix Corporation PCI Master Flags: bus master, medium devsel, latency 0 00: 78 10 0

Re: PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4

2001-01-12 Thread Hans Grobler
On Fri, 12 Jan 2001, Danny ter Haar wrote: > According to Hans Grobler: > > If you're willing, would you please follow "REPORTING-BUGS" and send some > > more info. Also cat /proc/interrupts. This one's intriging... Thanks for the report (still studying it). > lspci -vx output: > > 00:0f.0 Ether

PRoblem with pcnet32 under 2.4.0 , was :Drivers under 2.4

2001-01-12 Thread Danny ter Haar
According to Hans Grobler: > If you're willing, would you please follow "REPORTING-BUGS" and send some > more info. Also cat /proc/interrupts. This one's intriging... In short: Cyrix Multimedia box Everything onboard, including ethernet. Works as supposed to under 2.2.x (including 2.2.19pre7) i