public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Evgeniev" <nick@octet.spb.ru>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: linnux 2.4.19-rc1 i845e ide not detected. dma doesn't work
Date: Mon, 1 Jul 2002 15:49:43 +0400	[thread overview]
Message-ID: <000801c220f5$8176fb50$15cf69c2@nick> (raw)
In-Reply-To: E17O821-0007we-00@the-village.bc.nu

Hi,

    Why are you so assure? It's "msi 845e Max" with LAN on-board mb with
_latest_ BIOS installed....
Just FYI 2.4.18 was even unable to run eepro100 driver on it while intels
e100 driver was working perfectly.

----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "Nick Evgeniev" <nick@octet.spb.ru>
Cc: <linux-kernel@vger.kernel.org>
Sent: Saturday, June 29, 2002 6:32 AM
Subject: Re: linnux 2.4.19-rc1 i845e ide not detected. dma doesn't work


> Complain to your BIOS vendor
>
> A workaround for this BIOS flaw will be in the -ac tree in a week or so
>
>


  parent reply	other threads:[~2002-07-01 11:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-29  1:54 linnux 2.4.19-rc1 i845e ide not detected. dma doesn't work Nick Evgeniev
2002-06-29  2:32 ` Alan Cox
2002-06-29 17:45   ` linux 2.4.19-rc1 i845e workaround udma fix Gunther Mayer
2002-06-29 19:59     ` Andre Hedrick
2002-07-01 11:49   ` Nick Evgeniev [this message]
2002-07-03 15:28     ` linnux 2.4.19-rc1 i845e ide not detected. dma doesn't work Dave Jones
2002-07-03 19:17       ` Andre Hedrick
2002-07-04 13:14         ` Nick Evgeniev
2002-07-06  0:25           ` Andre Hedrick
2002-07-06 12:41             ` Nick Evgeniev
  -- strict thread matches above, loose matches on Subject: below --
2002-07-06  2:33 Anthony Spinillo

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='000801c220f5$8176fb50$15cf69c2@nick' \
    --to=nick@octet.spb.ru \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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