From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: problems with libata and ICH5 chipset.
Date: Sat, 19 Jun 2004 19:05:21 +0100 [thread overview]
Message-ID: <40D48061.1070300@superbug.demon.co.uk> (raw)
In-Reply-To: <40D4792C.5030702@superbug.demon.co.uk>
I have managed to fix this myself, but I don't think it is very user
friendly.
I have to compile into the kernel the option:
ATA/ATAPI/MFM/RLL support -> Include IDE/ATA-2 DISK support
I can leave the kernel CD drivers as modules.
This works, even though I don't have any PATA hard discs.
So, I now have:
hda - PATA DVD-Writer
hdb - PATA DVD-ROM
sda - SATA HD
sdb - SATA HD.
See new dmesg extract:
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
hda: OPTORITEDVD RW DD0203, ATAPI CD/DVD-ROM drive
hdb: ATAPI DVD-ROM 16XMax, ATAPI CD/DVD-ROM drive
ide1: I/O resource 0x170-0x177 not free.
ide1: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
libata version 1.02 loaded.
ata_piix version 1.02
ata_piix: combined mode detected
ata: 0x1f0 IDE port busy
PCI: Setting latency timer of device 0000:00:1f.2 to 64
ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
88:207f
ata1: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
ata1: dev 1 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
88:207f
ata1: dev 1 ATA, max UDMA/133, 312581808 sectors: lba48
ata1: dev 0 configured for UDMA/133
ata1: dev 1 configured for UDMA/133
scsi0 : ata_piix
Vendor: ATA Model: ST3160023AS Rev: 3.18
Type: Direct-Access ANSI SCSI revision: 05
Vendor: ATA Model: ST3160023AS Rev: 3.18
Type: Direct-Access ANSI SCSI revision: 05
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sda: drive cache: write back
/dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
SCSI device sdb: drive cache: write back
/dev/scsi/host0/bus0/target1/lun0: p1 p2 < p5 p6 >
Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0
James Courtier-Dutton wrote:
> I am using kernel 2.6.7.
> I enclose an extract from dmesg below.
> I have 2 PATA devices, one DVD-ROM, one DVD-writer on ata1. (or hda and
> hdb)
> I also have 2 SATA devices, both Hard Discs.
> When I boot without libata enabled, and just use:-
> ATA/ATAPI/MFM/RLL support -> Intel PIIXn chipsets support
> I get access to: -
> hda - PATA DVD-Writer
> hdb - PATA DVD-ROM
> hdc - SATA HD
> hdd - SATA HD.
>
> If I then enable:
> SCSI device support -> SCSI low-level drivers -> Serial ATA (SATA)
> support -> Intel PIIX/ICH SATA support
>
> No PATA devices are accessible. I get:
> sda - SATA HD
> sdb - SATA HD
>
> Is there any way that I can fix this using kernel options.
> It seems that below, the PATA devices are being recognised, but then are
> unable to be accessed.
>
> Cheers
> James
>
>
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> libata version 1.02 loaded.
> ata_piix version 1.02
> ata_piix: combined mode detected
> PCI: Setting latency timer of device 0000:00:1f.2 to 64
> ata1: PATA max UDMA/33 cmd 0x1F0 ctl 0x3F6 bmdma 0xF000 irq 14
> ata1: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000
> 88:0407
> ata1: dev 0 ATAPI, max UDMA/33
> ata1: dev 1 cfg 49:0b00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000
> 88:0407
> ata1: dev 1 ATAPI, max UDMA/33
> ata1: dev 0 configured for UDMA/33
> ata1: dev 1 configured for UDMA/33
> scsi0 : ata_piix
> ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
> ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
> 88:207f
> ata2: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
> ata2: dev 1 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
> 88:207f
> ata2: dev 1 ATA, max UDMA/133, 312581808 sectors: lba48
> ata2: dev 0 configured for UDMA/133
> ata2: dev 1 configured for UDMA/133
> scsi1 : ata_piix
> Vendor: ATA Model: ST3160023AS Rev: 3.18
> Type: Direct-Access ANSI SCSI revision: 05
> Vendor: ATA Model: ST3160023AS Rev: 3.18
> Type: Direct-Access ANSI SCSI revision: 05
> SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
> SCSI device sda: drive cache: write back
> /dev/scsi/host1/bus0/target0/lun0: p1 p2 < p5 >
> Attached scsi disk sda at scsi1, channel 0, id 0, lun 0
> SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
> SCSI device sdb: drive cache: write back
> /dev/scsi/host1/bus0/target1/lun0: p1 p2 < p5 p6 >
> Attached scsi disk sdb at scsi1, channel 0, id 1, lun 0
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2004-06-19 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 17:34 problems with libata and ICH5 chipset James Courtier-Dutton
2004-06-19 17:50 ` Jeff Garzik
2004-06-19 18:05 ` James Courtier-Dutton [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=40D48061.1070300@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).