All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Walrond <andrew@walrond.org>
To: linux-kernel@vger.kernel.org
Subject: Re: IDE Problems with 2.5.39
Date: Mon, 30 Sep 2002 16:47:57 +0100	[thread overview]
Message-ID: <3D98722D.5050503@walrond.org> (raw)
In-Reply-To: 1033337141.9053.6.camel@I401.resi.insa-lyon.fr

Nope; This is the latest Asus PR-DLS dual Xeon motherboard with

ServerWorks^® Grand Champion LE North Bridge (CMIC-LE)
ServerWorks^® Champion South Bridge (CSB5)
ServerWorks^® 64-bit PCI-X Bridge (CIOB-X2)

And the Serverworks IDE driver doesn't see my drive.
Works Fine with 2.4.20-pre8

Who should I be talking to?

JF wrote:

>On Sun, 2002-09-29 at 23:50, Andrew Walrond wrote:
>  
>
>>Hi,
>>
>>I can't boot with 2.5.39 because the built-in  ide driver (ServerWorks 
>>CSB5) can't see hda, and VFS says "Cannot open root device "hda3" or 
>>03:03" which results in a kernel panic
>>
>>Works fine with 2.4.20-pre? with identical kernel setup and kernel 
>>parameter root=/dev/hda3
>>
>>Is this a known problem? Any way around it or patches?
>>    
>>
>
>I used to have this problem with 2.5 too
>It went from the IDE controller chipset.
>
>Are you sure that you have only 1 IDE controller chipset ?
>
>I have both PIIX4 and HPT366. Root FS is on HPT366 controller. Enabling
>only PIIX4 used to work with 2.4 but doesn't with 2.5 anymore (got
>exactly your problem). I had to enable specific support for both.
>
>I suppose your root FS is on a specific IDE controller for which the
>support is not enabled (check the different type in the IDE/ATA kernel
>config section)
>
>Regards.
>
>  
>



      reply	other threads:[~2002-09-30 15:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 21:50 IDE Problems with 2.5.39 Andrew Walrond
2002-09-29 22:05 ` JF
2002-09-30 15:47   ` Andrew Walrond [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:
  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=3D98722D.5050503@walrond.org \
    --to=andrew@walrond.org \
    --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 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.