public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Victor Julien <v.p.p.julien@xs4all.nl>
To: Manuel McLure <manuel@mclure.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.3+ sound distortion
Date: Sun, 22 Apr 2001 20:37:38 +0200	[thread overview]
Message-ID: <20010422203738.A449@victor> (raw)
In-Reply-To: <20010422194713.A321@victor> <20010422110902.C1093@ulthar.internal.mclure.org>
In-Reply-To: <20010422110902.C1093@ulthar.internal.mclure.org>; from manuel@mclure.org on Sun, Apr 22, 2001 at 20:09:02 +0200

Wow! Now it not only boots right, the sound distortion problem also seems
to be fixed!!! Great work! However another problem is still here, i see
only one of the two ide-channels of the PDC20265.


> 
> On 2001.04.22 10:47 Victor Julien wrote:
> 
> > 2.4.4-pre6 did only compile when I aplied the '__builtin_expect'-patch.
> > It
> > crashed at boot however, when initializing my onboard raidcontroller
> > (PDC20265 on a MSI K7T Turbo-R). It seems to be the same problem as
> > reported by Manuel A. McLure. So no word yet about the sound
> > distortion-problem being fixed.
> 
> The PCD20265 crash is fixed in 2.4.3-ac12 and should be fixed in the next
> -pre.
> In the meantime you can apply the following patch from Alan Cox:
> 
> *** drivers/ide/ide-pci.c.orig	Sun Apr 22 11:07:51 2001
> --- drivers/ide/ide-pci.c	Sat Apr 21 20:07:09 2001
> ***************
> *** 596,602 ****
>   		if (IDE_PCI_DEVID_EQ(d->devid, DEVID_PDC20265))
>   		{
>   			printk(KERN_INFO "ide: Found promise 20265 in
> RAID mode.\n");
> ! 			if(dev->bus->self->vendor == PCI_VENDOR_ID_INTEL
> &&
>   				dev->bus->self->device == PCI_DEVICE_ID_INTEL_I960)
>   			{
>   				printk(KERN_INFO "ide: Skipping Promise
> PDC20265 attached to I2O RAID controller.\n");
> --- 596,602 ----
>   		if (IDE_PCI_DEVID_EQ(d->devid, DEVID_PDC20265))
>   		{
>   			printk(KERN_INFO "ide: Found promise 20265 in
> RAID mode.\n");
> ! 			if(dev->bus->self && dev->bus->self->vendor ==
> PCI_VENDOR_ID_INTEL &&
>   				dev->bus->self->device == PCI_DEVICE_ID_INTEL_I960)
>   			{
>   				printk(KERN_INFO "ide: Skipping Promise
> PDC20265 attached to I2O RAID controller.\n");
> 
> 
> 
> -- 
> Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
> <manuel@mclure.org>     | and significant law, no man may kill a cat.
> <http://www.mclure.org> |             -- H.P. Lovecraft
> 
> 
> 



  parent reply	other threads:[~2001-04-22 18:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-22 17:47 2.4.3+ sound distortion Victor Julien
     [not found] ` <20010422110902.C1093@ulthar.internal.mclure.org>
2001-04-22 18:37   ` Victor Julien [this message]
2001-04-22 18:55     ` Alan Cox
2001-04-22 18:53 ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06 16:43 Woller, Thomas
2002-03-06  5:08 David Ford
2001-04-23 15:01 Woller, Thomas
2001-04-21 16:04 Victor Julien
2001-04-21 19:05 ` Nigel Gamble
2001-04-21 19:40   ` Victor Julien
2001-04-21 20:52     ` Erik Mouw
2001-04-21 21:07       ` Victor Julien
2001-04-21 23:15 ` Alan Cox
2001-04-21 23:31   ` Victor Julien
2001-04-22  7:55   ` Marcel J.E. Mol
2001-04-22 12:17     ` Alan Cox
2001-04-22 13:46 ` Mike Castle
2001-04-23  3:08   ` David

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=20010422203738.A449@victor \
    --to=v.p.p.julien@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel@mclure.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