From: Auke Kok <sofar@foo-projects.org>
To: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18
Date: Tue, 09 Jan 2007 13:39:15 -0800 [thread overview]
Message-ID: <45A40B83.2060009@foo-projects.org> (raw)
In-Reply-To: <45A4003A.3080403@wolfmountaingroup.com>
Jeff V. Merkey wrote:
> Jeff V. Merkey wrote:
>
> root=/dev/hda2 is what was passed to the kernel from grub.
>
> Jeff
>
>>
>> I just finished pulling out a melted IDE flash drive out of a Shuttle
>> motherboard with the intel 945 chipset which claims to support
>> SATA and IDE drives concurrently under Linux 2.6.18.
>>
>> The chip worked for about 30 seconds before liquifying in the
>> chassis. I note that the 945 chipset in the shuttle PC had some serious
>> issues recognizing 2 x SATA devices and a IDE device concurrently.
>> Are there known problems with the Linux drivers
>> with these newer chipsets.
>>
>> One other disturbing issue was the IDE flash drive was configured (and
>> recognized) as /dev/hda during bootup, but when
>> it got to the root mountint, even with root=/dev/hda set, it still
>> kept thinking the drive was at scsi (ATA) device (08,13)
>> and kept crashing with VFS cannot find root FS errors.
it sounds like someone switched the BIOS IDE setting from ide-compatible/legacy to AHCI
or similar, a not uncommon option in the sata controllers on those boards.
None of that would explain the melting of anything of course.
Cheers,
Auke
next prev parent reply other threads:[~2007-01-09 21:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 20:46 SATA/IDE Dual Mode w/Intel 945 Chipset or HOW TO LIQUIFY a flash IDE chip under 2.6.18 Jeff V. Merkey
2007-01-09 20:51 ` Jeff V. Merkey
2007-01-09 21:39 ` Auke Kok [this message]
2007-01-09 22:11 ` Jeff V. Merkey
2007-01-09 22:59 ` Lennart Sorensen
2007-01-09 23:35 ` Jeff V. Merkey
2007-01-09 23:21 ` Jeff Garzik
2007-01-09 23:34 ` Jeff V. Merkey
2007-01-10 0:25 ` Jeff Garzik
2007-01-10 0:13 ` Jeff V. Merkey
2007-01-10 14:39 ` Lennart Sorensen
2007-01-10 14:58 ` Jeff Garzik
2007-01-10 15:15 ` Lennart Sorensen
2007-01-10 17:29 ` Prakash Punnoor
2007-01-10 17:47 ` Lennart Sorensen
2007-01-10 17:25 ` Jeff V. Merkey
2007-01-10 17:58 ` Lennart Sorensen
2007-01-10 18:17 ` Jeff Garzik
2007-01-10 17:56 ` Prakash Punnoor
2007-01-10 18:00 ` Lennart Sorensen
2007-01-10 18:19 ` Jeff Garzik
2007-01-10 18:33 ` Prakash Punnoor
[not found] <fa.w2Xz1pEig0R6ShqpHFJyconmPBo@ifi.uio.no>
[not found] ` <fa.Dlil7VK33821i8DmcFWlIN2XaQU@ifi.uio.no>
[not found] ` <fa.tj/VxhLXoYhj9fN5JWFl+JK12nU@ifi.uio.no>
[not found] ` <fa.j4A1taZJ5T85q4EnugrwsVjbq80@ifi.uio.no>
[not found] ` <fa.F7iasR6Lz0YMnhzBecxJ2HmeL/Y@ifi.uio.no>
[not found] ` <fa.knaXdjvwhsPCFpF5idaEG5sHhcM@ifi.uio.no>
2007-01-10 22:50 ` Robert Hancock
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=45A40B83.2060009@foo-projects.org \
--to=sofar@foo-projects.org \
--cc=jmerkey@wolfmountaingroup.com \
--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.