All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Manfred Spraul <manfred@colorfullife.com>
Subject: Re: forcedeth as a module only?
Date: Sat, 18 Jun 2005 00:22:10 +0200	[thread overview]
Message-ID: <42B34D12.70008@g-house.de> (raw)
In-Reply-To: <42B336FC.9000400@colorfullife.com>

Manfred Spraul schrieb:
> Very interesting.  The message itself is not fatal: It merely means that
> there was no link during ifup. This typically happens when the hardware
> initialization was not yet finished during ifup. Theoretically, an
> interrupt should happen when the hardware initialization is completed
> and that interrupt then sets up the link.
> Somehow it doesn't work for you.

could be the hardware's fault too? it's an onboard NIC on an nforce
chipset and the lspci i attached in the last mail looks rather strange
(compared to the r8169 (eth1) entry).

> Could you try the attached patch? It polls for link changes instead of
> relying on the irq. Additionally, I have enabled some debug output.

off to reboot in a second...


thanks,
Christian.

PS: on a side note, did you get my "other" mail concerning your mail address?
-- 
BOFH excuse #122:

because Bill Gates is a Jehovah's witness and so nothing can work on St.
Swithin's day.

  reply	other threads:[~2005-06-17 22:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200506171804.j5HI4qoh027680@dbl.q-ag.de>
     [not found] ` <42B31749.90208@g-house.de>
2005-06-17 20:47   ` forcedeth as a module only? Manfred Spraul
2005-06-17 22:22     ` Christian Kujau [this message]
2005-06-17 22:36       ` Christian Kujau
2005-06-18 10:44     ` marvin24
2005-06-18 12:53       ` Manfred Spraul
2005-06-17 17:41 Christian Kujau

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=42B34D12.70008@g-house.de \
    --to=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.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 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.