Who makes cdm640?  This is an Intel motherboard, with (of course)
an Intel chipset (if that makes any difference).

But as I stated in an earlier post, this thing had been running
happily for a year or so, and just decided to be a problem a couple
of days ago.  If it was an interface-related problem, what are the
chances it would have waited that long to show up?

And I know POST isn't much of a test, but right now that's about
all I can muster.

-jdr-

[EMAIL PROTECTED] wrote:
> 
> Scratch together $5 or so and treat that puppy to a new IDE cable.
> That is my best bet.
> 
> There is one hardware booby-trap to do with IDE drives:  the cdm640 IDE
> interface chip.  If you let it have its way it will make hd's appear to
> be utterly broken; in fact you can fix them with format (as practiced by
> msdose install (you can abort the install once it has done the format);
> AFAIK there is no linux equivalent, except for one I cobbled together
> with kernel patches).  If the IDE driver was compiled with
> CONFIG_BLK_DEV_CMD640, it can detect the PCI version of the chip and
> prevent it from doing any damage.  If you have a VLB version, you must
> use the boot parameter ide0=cmd640_vlb or it will eat you alive.
> 
> Any distro that would ship a stock kernel or ide module without this
> option is brain dead.  The slackware kernels have it; I trust the others
> do too.
> 
> On Fri, 4 Aug 2000, Jim Reimer wrote:
> 
> > The computer has a new drive, and I've swapped the memory (was 16meg,
> > now 32meg).  Condition of memory is unknown - came out of an old
> > machine - but it passes the POST ok.
> >
> The POST memory check is a bit sketchy.  gcc is a much better memory
> tester.
> 
> > RH6.2 installed ok, and I left it sitting at the login prompt.  A while
> > later, I had the "drive not ready for command" messages scrolling up
> the
> > screen again.  Computer would not respond to CTRL-ALT-DEL.  Pressed
> reset,
> > and the computer wouldn't boot (just like with the old drive).  Cycled
> > power, it started booting, but now I have a corrupted file system
> again.
> 
> Oh oh.  I have a junk-pentium 66 with the cmd640;  when the HD is
> unhappy the BIOS hangs and won't reset.
> >
> > It's been turned off all night, just turned it on, and it won't boot at
> > all from the hard drive.  Boots ok from floppy.
> >
> > Booting from the floppy (with the install disk) goes ok until it starts
> > checking for drives, then I get "hda: lost interrupt" over and over
> > and over.......
> >
> > P90, Award BIOS v4.50G, on-board IDE & floppy controllers.
> > Everything related to APM in the BIOS is either 'off' or 'disabled'.
> >
> > Where do I go now?
> >
> > -jdr-
> >
> > -
> Lawson
> 
> | We apologize if this message has reached you in error.
> | Save the Planet, Save the Trees! Advertise via E mail.
>

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs

Reply via email to