From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, Martin Bene <martin.bene@icomedias.com>
Subject: Re: Network error with Intel E1000 Adapter on update 2.4.25 ==> 2.6.3
Date: Fri, 27 Feb 2004 18:54:12 +0100 [thread overview]
Message-ID: <1077904451.14545.3.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <200402271338.01853@WOLK>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On Fri, 2004-02-27 at 13:38, Marc-Christian Petersen wrote:
> On Friday 27 February 2004 13:22, Martin Bene wrote:
>
> Hi Martin,
>
> > When trying to update the kernel from 2.4.25 to 2.6.3 I run into a probelm:
> > While the driver for the onboard Intel E1000 network adapter loads OK, it
> > doesn't seem to find an interrupt for the interface - ifconfig shows:
> > eth0 Link encap:Ethernet HWaddr 00:0E:A6:2D:7A:64
> > BROADCAST 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:1000
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > Base address:0x9000 Memory:fc000000-fc020000
> > [ ... ripped the rest ... ]
> > Board is an Asus PC-DL, Intel 875P Chipset, one Xeon 2.8Ghz CPU, Onboard
> > e1000 Network interface. Any idea how I can get the onboard NIC to work?
>
> full output of /var/log/dmesg || dmesg after bootup might help.
e1000 is known to have problems in 2.6.3
Please try the latest 2.6.3-bk snapshot, it may work better, it has
helped at least one other reporter of e1000 problems in 2.6.3
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-27 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 12:22 Martin Bene
2004-02-27 12:38 ` Marc-Christian Petersen
2004-02-27 17:54 ` Martin Josefsson [this message]
2004-02-28 11:52 Martin Bene
2004-03-01 19:00 Feldman, Scott
2004-03-02 6:15 Martin Bene
2004-03-02 18:22 Feldman, Scott
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=1077904451.14545.3.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=martin.bene@icomedias.com \
/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
all inboxes | Powered by JetHome®