public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Terry Hardie <terryh@orcas.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Asus P4C800-E Deluxe and Intel Pro/1000
Date: Sat, 01 Jan 2005 15:31:01 -0500	[thread overview]
Message-ID: <41D70885.3080208@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0412311715190.3717@orcas.net>

Terry Hardie wrote:
> On Fri, 31 Dec 2004, Bill Davidsen wrote:
> 
> 
>>Terry Hardie wrote:
>>
>>>Well, this has been plauging me for months, and finally figured it out.
>>>
>>>Any 2.6 kernel on my board, would boot, then give errors (paraphrased,
>>>sorry) when I tried to bring up the ethernet:
>>>
>>>NETDEV WATCHDOG: eth0: transmit timed out
>>>IRQ #18: Nobody cared!
>>>
>>>And no ethernet conectivity.
>>>
>>>The Fix: Update bios from asus' website. I guess their ACPI was screwed
>>>up. This is the second time I've had to update this MB to fix
>>>incompatibilities with Linux. So, watch out with Asus boards on Linux.
>>>
>>>BTW - Linux 2.4's driver worked fine with the old bios. Only 2.6 didn't
>>>work.
>>
>>Some additional info, I've been investigating this for a few hours, and
>>it appears that (a) IRQ 18 on my system is shared by ide0 and ide1, and
>>that the IRQ storm seems to start the first time I use ide1 (DVD only).
>>
>>I will be posting a bunch of dmesg results when/if the system reboots,
>>but acpi={off,ht} doesn't help, pollirq doesn't help, and system
>>shutdown leaves the system unbootable without a full (pull the power
>>cord) hardware power cycle.
>>
>>Questions:
>>1 - do you have trouble rebooting after a failure?
> 
> 
> Since I flashed my bios, no more problems, so I've had no more failures

I hesitate to try that, since the web page says you must use "real DOS" 
and gives instructions for creating the FD using that. Since I lack both 
DOS and a floppy, that does present problems...

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  reply	other threads:[~2005-01-01 20:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-08 15:49 USB-Serial fails with USB 2.0 Hub Robin Getz
2004-11-11 19:03 ` USB-1.1 fails with USB 2.0 Hub [was: Re: USB-Serial fails with USB 2.0 Hub] Gregor Jasny
2004-11-11 19:30   ` Gregor Jasny
2004-11-12 10:44   ` USB-1.1 fails with USB 2.0 Hub Juergen Stuber
2004-12-27  5:32   ` Asus P4C800-E Deluxe and Intel Pro/1000 Terry Hardie
2004-12-30  2:01     ` Bill Davidsen
2004-12-31 21:27     ` Bill Davidsen
2005-01-01  1:21       ` Terry Hardie
2005-01-01 20:31         ` Bill Davidsen [this message]
2005-01-01 21:26           ` Terry Hardie
2005-01-01 22:51             ` Lee Revell
2005-01-02  2:12             ` Bill Davidsen
2005-01-02 15:11               ` Klaus Kurzmann
2005-01-03  0:45                 ` Bill Davidsen
2004-11-13  0:54 ` USB-Serial fails with USB 2.0 Hub Greg KH

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=41D70885.3080208@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=terryh@orcas.net \
    /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