mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: NillyNux <selfdest@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: 2.6 Kernel and Ami IDE Raid Controller
Date: Mon, 12 Jan 2004 11:41:25 -0500	[thread overview]
Message-ID: <pan.2004.01.12.16.41.25.332063@comcast.net> (raw)


I have been trying to get 2.6 working on my redhat box for while now.  I
have been through various versions of 2.6 but they all seem to end at the
same spot.  I just tried 2.6.1 over the weekend, and well, I guess it's
time to ask for some help. My motherboard is a Iwill DVD266-r with dual
PIII's, and on this mobo there is an AMI megaraid ide controller which
works great under kernel 2.4.20 and a few versions prior that I have tried.  

lspci reports this controller as:

00:0f.0 RAID bus controller: CMD Technology Inc PCI0649 (rev 02)

and messages log shows:

Jan 10 10:53:04 pcp476248pcs kernel: CMD649: IDE controller at PCI slot 00:0f.0
Jan 10 10:53:04 pcp476248pcs kernel: CMD649: chipset revision 2
Jan 10 10:53:04 pcp476248pcs kernel: CMD649: not 100%% native mode: will probe
 irqs later

That's how it shows in 2.4.x kernels and it works great, but in 2.6.x it
kernel panics shortly after this module is loaded.  I see the module load
and it goes to detecting the drive on the controller, but in the process
of doing this, it says "IRQ to HDA1 has been lost",  it will say that
about 4 times over the course of a couple of minutes and then I get the
kernel panic.

The only difference that I have noticed with module is that during the
boot process the version of CMD649 with 2.4.20 says it's Beta3, but the
one that 2.6.x reports is Alpha, would this driver version have regressed?

Other than that, anyone got any ideas?



                 reply	other threads:[~2004-01-12 16:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=pan.2004.01.12.16.41.25.332063@comcast.net \
    --to=selfdest@comcast.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

all inboxes | Powered by JetHome®