DragonFly bugs List (threaded) for 2008-12
DragonFly BSD
DragonFly bugs List (threaded) for 2008-12
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: [issue1158] Problems with a SATA DVD burner


From: Jeremy Chadwick <jdc@xxxxxxxxxxxx>
Date: Thu, 11 Dec 2008 07:15:53 -0800

On Thu, Dec 11, 2008 at 01:53:15PM +0000, Steve O'Hara-Smith wrote:
> On Thu, 11 Dec 2008 04:50:51 -0800
> Jeremy Chadwick <jdc@parodius.com> wrote:
> 
> > On Thu, Dec 11, 2008 at 12:24:08PM +0000, Steve O'Hara-Smith wrote:
> > > On Wed, 10 Dec 2008 23:38:08 -0000
> 
> > > 	I'm using an Asus A8V Deluxe motherboard - dmesg | grep ata
> > > 
> > > atapci0: <Promise PDC20378 SATA150 controller> port
> > > 0x8800-0x887f,0x9000-0x900f,0x9400-0x943f mem
> > > 0xfb700000-0xfb71ffff,0xfb800000-0xfb800fff irq 5 at device 8.0 on pci0
> > > ata2: <ATA channel 0> on atapci0 ad4: 239372MB <Maxtor 6Y250M0
> > > YAR51HW0> at ata2-master SATA150 ata3: <ATA channel 1> on atapci0 ata4:
> > > YAR51HW0> <ATA channel 2> on atapci0
> > > ad8: 117246MB <Maxtor 6Y120P0 YAR41BW0> at ata4-master UDMA133
> > > atapci1: <VIA 6420 SATA150 controller> port
> > > 0xa800-0xa8ff,0xb000-0xb00f,0xb400-0xb403,0xb800-0xb807,0xc000-0xc003,0xc400-0xc407
> > > irq 10 at device 15.0 on pci0 ata5: <ATA channel 0> on atapci1 ad10:
> > > 286168MB <Seagate ST3300622AS 3.AAE> at ata5-master SATA150 ata6: <ATA
> > > channel 1> on atapci1 atapci2: <VIA 8237 UDMA133 controller> port
> > > 0xfc00-0xfc0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on
> > > pci0 ata0: <ATA channel 0> on atapci2 ata1: <ATA channel 1> on atapci2
> > > cd0 at ata4 bus 0 target 0 lun 0
> > > cd1 at ata6 bus 0 target 0 lun 0
> > > 
> > > 	The reuse of ata4 seems odd - related or irrelevant ?
> > 
> > I'm trying very hard to stay out of this discussion because I'm in no
> > way familiar with DFBSD's changes to ATA and ATAPI.  I am, however,
> > quite familiar with ATA/SATA on FreeBSD.  One thing stands out here like
> > a sore thumb:
> > 
> > Your SATA CD/DVD drive is connected to a Promise RAID controller.  I
> 
> 	It's not actually connected to the Promise, it's connected to the
> VIA controller plugged in right next to the Seagate drive. The Promise
> controller has ad4 (SATA) and ad8 (PATA) connected to it, the VIA has ad10
> (SATA), cd0 (SATA) and cd1 (PATA) connected to it. I am deeply suspicious
> about the mention of ata4 for two different devices (ad8 and cd0) connected
> to two different controllers.

So, part of the complexity is that your Promise controller offers both
SATA **and** PATA.

Well, the breakdown is this:

atapci0 = Promise FastTrak RAID
	--> ata2 (SATA)
		--> ad4 = Maxtor 6Y250M0
	--> ata3 (SATA)
	--> ata4 (PATA)
		--> ad8 (master?) = Maxtor 6Y120P0
		--> cd0 (slave?)  = TSSTcorp CDDVDW SH-S223F SB00

atapci1 = VIA 6420 SATA
	--> ata5
		--> ad10 = Seagate ST3300622AS
	--> ata6
		--> cd1 = LITE-ON DVD SOHD-167T 9S19

atapci2 = VIA 8237 ATA133
	--> ata0
	--> ata1

cd0 showing up attached to ata4 (somehow) is indicative of a problem.

It might also help if you could provide "atacontrol list" output.  I
assume DFBSD has atacontrol.

> > have never seen this work, and vendors even go so far to state "DO NOT
> > HOOK UP CD/DVD DRIVES TO RAID CONTROLLERS".  The RAID controller is
> > probably freaking out because it doesn't know how to speak ATAPI
> > properly.
> 
> 	It doesn't even get recognised as being present if I connect it to
> the Promise RAID controller, I made that mistake when I first connected it.

Makes perfect sense.

-- 
| Jeremy Chadwick                                jdc at parodius.com |
| Parodius Networking                       http://www.parodius.com/ |
| UNIX Systems Administrator                  Mountain View, CA, USA |
| Making life hard for others since 1977.              PGP: 4BD6C0CB |




[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]