LKML Archive on
help / color / mirror / Atom feed
From: Manfred Spraul <>
Cc:, XFree86@XFree86.Org,,
Subject: Re: forcedeth breaks X in Debian-testing 2.4.25 on MSI K7N2 Delta-L mobo
Date: Sat, 15 May 2004 20:56:15 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <> wrote:

>So do you (or anyone) have any suggestions for what to do?  This is a
>reasonably new motherboard (I don't think it has any new firmware
>versions out yet) and this leaves me dead in the water---all I can do
>at this point is to just try the nVidia drivers and hope they work
>better than forcedeth.
I would propose that as the first step: If this fails, then you can try 
to get support from NVidia.

 From you description it doesn't look like a bug directly in the 
forcedeth driver: Perhaps a problem with a shared interrupt, or the vesa 
bios uses an area for I/O and the ethernet registers are remapped on top 
of the vesa registers.

Could you post lspci -vxx from both before and after loading forcedeth. 
Or try bios settings that sound like Plug-N-Play aware OS. Or try ACPI 
instead of APM (I've seen a boot log that contains both acpi and apm - 
which one do you use? Try to boot with "acpi=off", "pci=noacpi", etc.)


      reply	other threads:[~2004-05-15 18:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2004-05-10 19:08 ` Carl-Daniel Hailfinger
2004-05-13  6:19   ` foner+x-forcedeth
2004-05-15 18:56     ` Manfred Spraul [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \
    --cc=XFree86@XFree86.Org \ \ \ \ \
    --subject='Re: forcedeth breaks X in Debian-testing 2.4.25 on MSI K7N2 Delta-L mobo' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).