public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: David Grant <davidgrant79@hotmail.com>
Cc: Greg Ward <gward@python.net>,
	bugs@linux-ide.org, linux-kernel@vger.kernel.org
Subject: Re: "hde: timeout waiting for DMA": message gone, same behaviour
Date: Mon, 24 Sep 2001 10:35:44 +0200	[thread overview]
Message-ID: <20010924103544.A1572@suse.cz> (raw)
In-Reply-To: <20010921134402.A975@gerg.ca> <20010921205356.A1104@suse.cz> <20010921150806.A2453@gerg.ca> <20010921154903.A621@gerg.ca> <20010921215622.A1282@suse.cz> <20010921164304.A545@gerg.ca> <20010922100451.A2229@suse.cz> <OE3183UV8wAddX47sFo00001649@hotmail.com> <20010922110945.B678@gerg.ca> <OE48GTjkifTNRMOKS310000192c@hotmail.com>
In-Reply-To: <OE48GTjkifTNRMOKS310000192c@hotmail.com>; from davidgrant79@hotmail.com on Sat, Sep 22, 2001 at 01:07:39PM -0700

On Sat, Sep 22, 2001 at 01:07:39PM -0700, David Grant wrote:
> >
> > BTW, you wouldn't happen to know which kernel version was in the Linux
> > distros you attempted to install, would you?  Not that it
> > matters... 2.4.9 doesn't work for me, and I haven't heard anyone telling
> > me to upgrade to the latest bleeding edge 2.4.10.preXX or 2.4.9acYY.
> 
> Redhat 7.1 uses 2.4.2-2 (redhat version).  Debian uses 2.2.19-pre17?
> something weird like that.  Mandrake uses 2.4.8 (which I now believe had no
> changes to VIA and/or Promise code).  I'm still wondering when Alan Cox's
> fixes went into the Linus code.  And I'm still trying to figure out why
> Alan's code is called via82cxxx, while Vojtech's is called vt82cxxx.  So
> either someone renamed Alan's version back to vt82cxxx to integrate into the
> main kernel tree, or it never got included???  But I know Vojtech's recent
> fixes are still in the latest pre (2.4.10-pre1 I think).

It's only via82cxxx, and is in quite recent versions in both the latest
Alan's and Linus's kernels ... 

> So from what you are saying and what I'm saying, 2.4.8 and 2.4.9 don't work.
> 2.4.9 should have included Alan's fixes since he originally patched them to
> 2.4.6-ac5.  So his fixes don't seem to fix OUR problem.  The only hope left
> might be Vojtech's changes, which are in 2.4.10-pre1.  But I doubt that
> these are major changes, or else, like you say, someone would have told us
> to upgrade to that kernel.

No, they only affected 686b's and newer chips.

> I actually just had an idea which just came to me.  I have added a little
> bit of hardware since I first started playing with Linux.  I added a network
> card.  This could have been around the time that I started having trouble
> installed Linux period.  And I also remember my BIOS warning me as I started
> my computer, "The PCI device you just added will be sharing an IRQ with
> 'Promise IDE Controller'.  You must alter the BIOS settings manually if
> these devices don't support IRQ sharing."  So, I could see how that could
> cause my Promise to not work properly, but the VIA too?  I'm haven't done
> any looking into the IRQ for the Southbridge any whether there is any
> sharing.  I also added a USB webcam, but I don't think that will do
> anything.
> 
> Also, if someone could explain to me personally over e-mail how Linux
> handle's IRQs and stuff, that would be nice.  Specifically, I'm wondering
> about something I read in the Mandrake installer guide.  It said that I
> should change the BIOS setting: "Plug & Play Computer" to "No".  I currently
> have had it set to "Yes," and this is what I used when I tried to install
> Redhat and it used to work.  I'm just confused as to what exactly this BIOS
> setting does.

The PnP stuff is for ISA PnP cards. If you don't have those, it's
irrelevant. When "PnP OS Installed" is set to "No", the BIOS does the
ISAPnP initialization. If it is set to "Yes", it skips that step. Linux
prefers to have the ISAPnP cards pre-initialized, though it can do it
all by itself.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2001-09-24  8:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-21 17:44 "hde: timeout waiting for DMA": message gone, same behaviour Greg Ward
2001-09-21 18:53 ` Vojtech Pavlik
2001-09-21 19:08   ` Greg Ward
2001-09-21 19:49     ` Greg Ward
2001-09-21 19:56       ` Vojtech Pavlik
2001-09-21 20:43         ` Greg Ward
2001-09-22  8:04           ` Vojtech Pavlik
2001-09-22 10:53             ` David Grant
2001-09-22 13:40               ` Eyal Lebedinsky
2001-09-22 15:09               ` Greg Ward
2001-09-22 15:58                 ` Alan Cox
2001-09-25 20:23                   ` Maxwell Spangler
2001-09-26  2:02                     ` David Grant
2001-09-26  2:18                       ` Maxwell Spangler
2001-09-22 20:07                 ` David Grant
2001-09-24  8:35                   ` Vojtech Pavlik [this message]
2001-09-24 18:37                     ` Eric W. Biederman
2001-09-24 22:44                       ` Vojtech Pavlik
2001-09-25  0:15                         ` Kevin P. Fleming
2001-10-01 14:03 ` Greg Ward

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=20010924103544.A1572@suse.cz \
    --to=vojtech@suse.cz \
    --cc=bugs@linux-ide.org \
    --cc=davidgrant79@hotmail.com \
    --cc=gward@python.net \
    --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