From: dth@lin-gen.com (Danny ter Haar)
To: linux-kernel@vger.kernel.org
Subject: Re: Drivers under 2.4
Date: Thu, 11 Jan 2001 16:33:14 +0000 (UTC) [thread overview]
Message-ID: <93kn8a$itt$1@voyager.cistron.net> (raw)
In-Reply-To: <20010110223836.A7321@gruyere.muc.suse.de> <93k75v$r1u$1@voyager.cistron.net> <93ke9q$jnj$1@voyager.cistron.net> <3A5DC411.794486B0@mandrakesoft.com>
Jeff Garzik <jgarzik@mandrakesoft.com> 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 0x22625003.
eth0: PCnet/FAST III 79C973 at 0xfce0, 00 00 e2 24 41 1d<6>pcnet32: pcnet32_priv
ate lp=c3fb8d40 lp_dma_addr=0x3bf1000
assigned IRQ 9.
pcnet32.c:v1.25smp Nov 11, 2000 tsbogend@alpha.franken.de
eth0: pcnet32_open() irq 9 tx/rx rings 0x3bf1200/0x3bf1000 init 0x3bf1300.
eth0: pcnet32 open after 5 ticks, init block 0x3bf1300 csr0 01f3.
eth0: pcnet32_start_xmit() called, csr0 01f3.
multimedia:~# ping -c5 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
--- 192.168.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
multimedia:~# arp -an
? (192.168.1.2) at <incomplete> on eth0
? (192.168.1.1) at <incomplete> on eth0
multimedia:~# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:00:E2:24:41:1D
inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:9 Base address:0xfce0
Danny
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 16:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 9:12 Failure building 2.4 while running 2.4. Success in building 2.4 while running 2.2 Silviu Marin-Caea
2001-01-09 10:17 ` Alessandro Suardi
2001-01-09 10:33 ` Failure building 2.4 while running 2.4. Success in building 2.4 Alan Cox
2001-01-09 18:20 ` Failure building 2.4 while running 2.4. There is no such thing Silviu Marin-Caea
2001-01-09 18:43 ` Alan Cox
2001-01-09 19:57 ` Drivers under 2.4 Dennis
2001-01-09 20:13 ` suser checks in 2.2.x Bosko Radivojevic
2001-01-09 18:39 ` Arnaldo Carvalho de Melo
2001-01-10 18:22 ` Drivers under 2.4 Dennis
2001-01-10 20:01 ` Hans Grobler
2001-01-10 21:37 ` Dennis
2001-01-10 21:38 ` Andi Kleen
2001-01-10 22:08 ` Hans Grobler
2001-01-11 10:24 ` Danny ter Haar
2001-01-11 10:31 ` Andi Kleen
2001-01-11 10:58 ` Danny ter Haar
2001-01-11 11:36 ` Andrew Morton
2001-01-11 11:58 ` Danny ter Haar
2001-01-11 14:00 ` Danny ter Haar
2001-01-11 14:32 ` Jeff Garzik
2001-01-11 16:33 ` Danny ter Haar [this message]
2001-01-11 16:44 ` Hans Grobler
2001-01-12 11:50 ` PRoblem with pcnet32 under 2.4.0 , was :Drivers " Danny ter Haar
2001-01-12 12:01 ` Hans Grobler
2001-01-12 12:16 ` Danny ter Haar
2001-01-12 22:33 ` Thomas Bogendoerfer
2001-01-15 16:29 ` Danny ter Haar
2001-01-11 12:56 ` Drivers " Alan Cox
2001-01-09 10:28 ` Failure building 2.4 while running 2.4. Success in building 2.4 while running 2.2 Alan Cox
2001-01-09 16:10 ` [rlug] " Eugen
2001-01-09 19:01 ` J Sloan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='93kn8a$itt$1@voyager.cistron.net' \
--to=dth@lin-gen.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox