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
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
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
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
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
Hi Danny,
If you're willing, would you please follow "REPORTING-BUGS" and send some
more info. Also cat /proc/interrupts. This one's intriging...
-- Hans
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ
Jeff Garzik <[EMAIL PROTECTED]> wrote:
>Does this patch help at all?
Nope, unfortunatly it didn't
> filename="pcnet32.patch"
pcnet32_probe_pci: found device 0x001022.0x002000
ioaddr=0x00fce0 resource_flags=0x000101
PCI: Found IRQ 9 for device 00:0f.0
PCnet chip version is 0x22
Danny ter Haar wrote:
>
> >Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3.
> >Jan 11 12:46:01 multimedia last message repeated 12 times
>
> hot from the ethernet wire: more info just arrived:
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: transmit timed o
>Jan 11 12:45:49 multimedia kernel: eth0: pcnet32_start_xmit() called, csr0 07f3.
>Jan 11 12:46:01 multimedia last message repeated 12 times
hot from the ethernet wire: more info just arrived:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: transmit timed out, status 07f3, resetting.
Ring data
> cyrix processor, chipset and amd/lance ethernet chipset onboard.
> It' working fine with 2.2.x but not with 2.4.x kernels with
> the same driver version of the pcnet32 networkdriver.
What problems do you see
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Andrew Morton <[EMAIL PROTECTED]> wrote:
>There's a "reporting problems" section at the end
>of Documentation/networking/vortex.txt. Should help.
okidoki, have read it, thanks
>Probably the most important thing is inserting the driver
>module with `debug=7', opening the device, sending some
>t
Danny ter Haar wrote:
>
> According to Andi Kleen:
> > "Doesn't work" isn't a very useful bug report. What happens exactly?
> > Do the RX/TX/error counters increase when you try to send packets?
>
> no, the counters you see with ifconfig eth0 are set to zero
> for rx and to 1 for tx.
>
> So it'
According to Andi Kleen:
> "Doesn't work" isn't a very useful bug report. What happens exactly?
> Do the RX/TX/error counters increase when you try to send packets?
no, the counters you see with ifconfig eth0 are set to zero
for rx and to 1 for tx.
So it's trying to send out data but somehow
On Thu, Jan 11, 2001 at 10:24:01AM +, Danny ter Haar wrote:
> Version number of the driver is the same but it doesn't work.
>
> Any thoughts anyone ?
"Doesn't work" isn't a very useful bug report. What happens exactly?
Do the RX/TX/error counters increase when you try to send packets?
-An
Hans Grobler <[EMAIL PROTECTED]> wrote:
>The softnet changes are most likely the primary source of breakage (for
>network drivers).
I happen to have a multimedia box from siemens/fujitsu with a
cyrix processor, chipset and amd/lance ethernet chipset onboard.
It' working fine with 2.2.x but not
On Wed, 10 Jan 2001, Andi Kleen wrote:
> On Wed, Jan 10, 2001 at 04:37:06PM -0500, Dennis wrote:
> >
> > Aren't you supposed to design the spec BEFORE you implement it?
>
> Try http://www.firstfloor.org/~andi/softnet (minor details outdated)
The softnet changes are most likely the primary source
On Wed, Jan 10, 2001 at 04:37:06PM -0500, Dennis wrote:
> At 03:01 PM 01/10/2001, Hans Grobler wrote:
> >On Wed, 10 Jan 2001, Dennis wrote:
> > > At 02:57 PM 01/09/2001, Dennis wrote:
> > > >Where might one find the definitive document on porting device drivers to
> > > >2.4 kernels?
> > >
> > > s
At 03:01 PM 01/10/2001, Hans Grobler wrote:
>On Wed, 10 Jan 2001, Dennis wrote:
> > At 02:57 PM 01/09/2001, Dennis wrote:
> > >Where might one find the definitive document on porting device drivers to
> > >2.4 kernels?
> >
> > should I assume that there are none?
>
>I don't think anyone has had th
On Wed, 10 Jan 2001, Dennis wrote:
> At 02:57 PM 01/09/2001, Dennis wrote:
> >Where might one find the definitive document on porting device drivers to
> >2.4 kernels?
>
> should I assume that there are none?
I don't think anyone has had the time yet. I'm sure someone will get
around to this soon
At 02:57 PM 01/09/2001, Dennis wrote:
>Where might one find the definitive document on porting device drivers to
>2.4 kernels?
>
>DB
should I assume that there are none?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Pleas
Where might one find the definitive document on porting device drivers to
2.4 kernels?
DB
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
21 matches
Mail list logo
