From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: libata driver update posted
Date: 19 Jul 2003 22:27:00 -0400 [thread overview]
Message-ID: <m3ispyx79n.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <3F19A651.2080503@pobox.com>
I gave this (pulled into linus' bk current) a try on my laptop.
It has this pata chip:
00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 04)
00:1f.1 IDE interface: Intel Corp. 82801BAM IDE U100 (rev 03)
aka
00:00.0 Class 0600: 8086:1130 (rev 04)
Flags: bus master, fast devsel, latency 0
Memory at e8000000 (32-bit, prefetchable) [size=64M]
00:1f.1 Class 0101: 8086:244a (rev 03)
Subsystem: 8086:4541
Flags: bus master, medium devsel, latency 0
I/O ports at bfa0 [size=16]
I left out the regualt ide support and added:
CONFIG_SCSI_ATA=y
CONFIG_SCSI_ATA_PATA=y
CONFIG_SCSI_ATA_ATAPI=y
CONFIG_SCSI_ATA_PIIX=y
The laptop has its fixed drive at hda, its fixed cd/dvd at hdb and
its media bay drive (whatever may be installed) at hdc.
root=/dev/sda3 failed to find the root fs.
I don't have anything here to plug into the serial port, so I cannot
record the boot messages.
Is my controller among the supported PIIX/ICH PATA chipsets?
-JimC
next prev parent reply other threads:[~2003-07-20 2:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 21:14 libata driver update posted Jeff Garzik
2003-07-18 6:24 ` Catalin BOIE
2003-07-18 13:13 ` Jeff Garzik
2003-07-18 15:39 ` Martin Schlemmer
2003-07-18 15:43 ` Jeff Garzik
2003-07-19 0:30 ` Martin Schlemmer
2003-07-19 0:38 ` Alan Cox
2003-07-19 0:52 ` Martin Schlemmer
2003-07-19 0:45 ` Andre Tomt
2003-07-19 20:08 ` Martin Schlemmer
2003-07-19 20:13 ` Jeff Garzik
2003-07-19 21:18 ` Martin Schlemmer
2003-07-20 2:27 ` James H. Cloos Jr. [this message]
2003-07-20 2:51 ` Jeff Garzik
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=m3ispyx79n.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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