From: Daniel Schmitt <pnambic@unu.nu>
To: ktech@wanadoo.es
Cc: manfred@colorfullife.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org, jgarzik@pobox.com
Subject: Re: 2.6.7-rc1 breaks forcedeth
Date: Sun, 6 Jun 2004 15:31:45 +0200 [thread overview]
Message-ID: <200406061531.45891.pnambic@unu.nu> (raw)
In-Reply-To: <E1BWxTh-0002dx-KR@mb06.in.mad.eresmas.com>
Hi,
> Daniel, how do you fix or suggest to fix that? Any way I can get my network
> card on, in your opinion?
if what I suspect about MY problem is in fact true, then for your problem I'd
try the following:
- switch on APIC and IO-APIC support on uniprocessors in your kernel config
- if there is such a setting, switch on APIC mode in your BIOS
- see if this suffices (your dmesg output seems more sane than mine)
If the problem doesn't go away, try the patch at the top of my mail. If it
still doesn't work, well, I might be completely wrong, or you might also be
suffering from BIOS and/or DSDT problems, but I'm even more out of my depth
there than with the issue I saw...
Good luck,
Daniel.
next parent reply other threads:[~2004-06-06 13:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BWxTh-0002dx-KR@mb06.in.mad.eresmas.com>
2004-06-06 13:31 ` Daniel Schmitt [this message]
2004-06-16 18:40 David Mansfield
-- strict thread matches above, loose matches on Subject: below --
2004-06-06 13:49 jjluza
2004-06-06 12:10 ktech
2004-06-06 12:53 ` Vincent van de Camp
2004-06-06 13:40 ` Manfred Spraul
2004-06-06 14:17 ` Manfred Spraul
2004-06-06 1:59 ktech
2004-06-06 3:14 ` Linus Torvalds
2004-06-06 8:36 ` Manfred Spraul
2004-06-06 17:04 ` Linus Torvalds
2004-06-06 18:13 ` Jeff Garzik
2004-06-06 18:21 ` Jeff Garzik
2004-06-06 18:32 ` Linus Torvalds
2004-06-05 23:41 Luis Miguel García Mancebo
2004-06-05 23:50 ` Linus Torvalds
2004-05-31 0:29 jjluza
2004-05-30 17:54 Luis Miguel García Mancebo
2004-05-30 20:47 ` Jeff Garzik
2004-05-30 15:57 Lee Howard
2004-05-30 17:20 ` Jeff Garzik
2004-05-30 22:59 ` Lee Howard
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=200406061531.45891.pnambic@unu.nu \
--to=pnambic@unu.nu \
--cc=jgarzik@pobox.com \
--cc=ktech@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®