All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mads Martin Jørgensen" <mmj@suse.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.4-ac8 now with added correct EXTRAVERSION
Date: Fri, 11 May 2001 14:15:21 -0700	[thread overview]
Message-ID: <20010511141521.A632@suse.com> (raw)
In-Reply-To: <E14yJEw-0001dW-00@the-village.bc.nu>
In-Reply-To: <E14yJEw-0001dW-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Fri, May 11, 2001 at 09:10:17PM +0100

* Alan Cox <alan@lxorguk.ukuu.org.uk> [May 11. 2001 13:18]:
> 2.4.4-ac8
> o	Tulip driver updates				(Jeff Garzik)

Networking stopped working with this kernel. I have the following
NIC:

02:0b.0 Ethernet controller: Lite-On Communications Inc LNE100TX (rev
20)
        Subsystem: Netgear FA310TX
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
        Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32
        Interrupt: pin A routed to IRQ 3
        Region 0: I/O ports at b800 [size=256]
        Region 1: Memory at df800000 (32-bit, non-prefetchable)
[size=256]
        Expansion ROM at <unassigned> [disabled] [size=256K]

-- 
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic and
totally illogic, with just a little bit more effort."
                                -- A. P. J.

  reply	other threads:[~2001-05-11 21:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 20:10 Linux 2.4.4-ac8 now with added correct EXTRAVERSION Alan Cox
2001-05-11 21:15 ` Mads Martin Jørgensen [this message]
2001-05-11 22:14   ` Jeff Garzik
2001-05-12  0:13 ` andersg
2001-05-12  0:22   ` Alan Cox
2001-05-12  0:38     ` andersg
  -- strict thread matches above, loose matches on Subject: below --
2001-05-11 21:26 Wayne.Brown

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=20010511141521.A632@suse.com \
    --to=mmj@suse.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.