Skip to contentSkip to conversation

SATA/ATAPI

DISCUSSION Tais M. Hansen 4 participants 10 messages Apr 21, 2005 – Apr 27, 2005 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

Hi,

I know there has been some talking about SATA/ATAPI being experimental and might not work at all under kernel-2.6.x.

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

Is there anything I can do to help the development of SATA/ATAPI devices?

libata version 1.10 loaded.
sata_promise version 1.01
ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 18 (level, low) -> IRQ 18
ata1: SATA max UDMA/133 cmd 0xF8804200 ctl 0xF8804238 bmdma 0x0 irq 18
ata2: SATA max UDMA/133 cmd 0xF8804280 ctl 0xF88042B8 bmdma 0x0 irq 18
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:407f
ata1: dev 0 ATA, max UDMA/133, 240121728 sectors:
ata1: dev 0 configured for UDMA/133
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
scsi1 : sata_promise
Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
sata_via version 1.1
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 20 sata_via(0000:00:0f.0): routed to hard irq line 4
ata3: SATA max UDMA/133 cmd 0xE800 ctl 0xE402 bmdma 0xD400 irq 20
ata4: SATA max UDMA/133 cmd 0xE000 ctl 0xD802 bmdma 0xD408 irq 20
ata3: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_via
ata4: no device found (phy stat 00000000)
scsi3 : sata_via
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB) SCSI device sda: drive cache: write back
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB) SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)
#1 lore raw

Just to check, you do have scsi cdrom support enabled right?

Quoted 57 lines · Tais M. Hansen

Hi,

I know there has been some talking about SATA/ATAPI being experimental and might not work at all under kernel-2.6.x.

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

Is there anything I can do to help the development of SATA/ATAPI devices?

libata version 1.10 loaded.
sata_promise version 1.01
ACPI: PCI interrupt 0000:00:08.0[A] -> GSI 18 (level, low) -> IRQ 18
ata1: SATA max UDMA/133 cmd 0xF8804200 ctl 0xF8804238 bmdma 0x0 irq 18
ata2: SATA max UDMA/133 cmd 0xF8804280 ctl 0xF88042B8 bmdma 0x0 irq 18
ata1: dev 0 cfg 49:2f00 82:7c6b 83:7b09 84:4003 85:7c69 86:3a01 87:4003 88:407f
ata1: dev 0 ATA, max UDMA/133, 240121728 sectors:
ata1: dev 0 configured for UDMA/133
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
scsi1 : sata_promise
Vendor: ATA Model: Maxtor 6Y120M0 Rev: YAR5
Type: Direct-Access ANSI SCSI revision: 05
sata_via version 1.1
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 20 sata_via(0000:00:0f.0): routed to hard irq line 4
ata3: SATA max UDMA/133 cmd 0xE800 ctl 0xE402 bmdma 0xD400 irq 20
ata4: SATA max UDMA/133 cmd 0xE000 ctl 0xD802 bmdma 0xD408 irq 20
ata3: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_via
ata4: no device found (phy stat 00000000)
scsi3 : sata_via
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB) SCSI device sda: drive cache: write back
SCSI device sda: 240121728 512-byte hdwr sectors (122942 MB) SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0

--
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's ideas were invented and had taken out patents, the industry would be at a complete standstill today." -Bill Gates (1991)

#2 lore raw
Quoted 5 lines · Brian Jackson
Quoted 4 lines

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

Just to check, you do have scsi cdrom support enabled right?

Yes. cdrom and sr_mod are both loaded as modules. I'm assuming having compiled them as modules doesn't change anything. I'm probably going to try messing with the SCSI cdrom driver, just to see if I can figure out what's going on.

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)
#3 lore raw
In reply to Tais M. Hansen
Quoted 9 lines · Tais M. Hansen

I know there has been some talking about SATA/ATAPI being experimental and might not work at all under kernel-2.6.x.

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

Is there anything I can do to help the development of SATA/ATAPI devices?

I thought all SCSI cdroms were using /dev/scdx or /dev/srx. Atleast all mine are (I use ide-scsi for ide disks)

Signature · 1 line
 Lab tests show that use of micro$oft causes cancer in lab animals
#4 lore raw
Quoted 6 lines · Wakko Warner
Quoted 4 lines

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

I thought all SCSI cdroms were using /dev/scdx or /dev/srx. Atleast all mine are (I use ide-scsi for ide disks)

You thought right. The "/dev/sdx" was just a typo on my side.

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)
#5 lore raw
In reply to Tais M. Hansen
Quoted 4 lines · Tais M. Hansen

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

I've been digging through sr, scsi, sata_via, libata-scsi and libata-core, littering the code with printk's.

My lack of knowledge on how the kernel handles devices, is really showing now.

I've been unable to figure out what is supposed to tie sr to the devices probed by sata_via. Also, littering sr with printk's gave me the idea that sr is not even looking for cdrom devices. It loads, does the basic module __init stuff and then silence. Should sr find devices itself or is the kernel supposed to inform sr via some callback hook? I could really be barking up the wrong tree here, and not even see it.

Enabling SCSI logging and kernel debug didn't really give me anything useful.

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)
#6 lore raw
Quoted 8 lines · Tais M. Hansen
Quoted 4 lines · Tais M. Hansen

One of my linux boxes has a Plextor DVD-RW drive with a SATA interface. The kernel sees this drive (ata3) but apparently doesn't tie it to a sdx device. The box also have a SATA harddisk, which is working just fine. The relevant dmesg output is pasted below.

Quoted 7 lines

I've been digging through sr, scsi, sata_via, libata-scsi and libata-core, littering the code with printk's.

My lack of knowledge on how the kernel handles devices, is really showing now.

I've been unable to figure out what is supposed to tie sr to the devices probed by sata_via. Also, littering sr with printk's gave me the idea that sr is not even looking for cdrom devices. It loads, does the basic module __init stuff and then silence. Should sr find devices itself or is the kernel supposed to inform sr via some callback hook? I could really be barking up the wrong tree here, and not even see it.

Enabling SCSI logging and kernel debug didn't really give me anything useful.

Did you turn on ATA_ENABLE_ATAPI in include/linux/libata.h?

Jeff

#7 lore raw
Quoted 12 lines · Jeff Garzik
Quoted 4 lines

I've been digging through sr, scsi, sata_via, libata-scsi and libata-core, littering the code with printk's.
My lack of knowledge on how the kernel handles devices, is really showing now.

Quoted 8 lines

I've been unable to figure out what is supposed to tie sr to the devices probed by sata_via. Also, littering sr with printk's gave me the idea that sr is not even looking for cdrom devices. It loads, does the basic module __init stuff and then silence. Should sr find devices itself or is the kernel supposed to inform sr via some callback hook? I could really be barking up the wrong tree here, and not even see it. Enabling SCSI logging and kernel debug didn't really give me anything useful.

Quoted 1 line

Did you turn on ATA_ENABLE_ATAPI in include/linux/libata.h?

Tried with it both defined and undefined. When it's defined an extra line is added (the last one below) when loading the sata_via module:

sata_via version 1.1
ACPI: PCI interrupt 0000:00:0f.0[B] -> GSI 20 (level, low) -> IRQ 20 sata_via(0000:00:0f.0): routed to hard irq line 4
ata3: SATA max UDMA/133 cmd 0xE800 ctl 0xE402 bmdma 0xD400 irq 20
ata4: SATA max UDMA/133 cmd 0xE000 ctl 0xD802 bmdma 0xD408 irq 20
ata3: dev 0 cfg 49:0f00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000 88:0007
ata3: dev 0 ATAPI, max UDMA/33
ata3: dev 0 configured for UDMA/33
scsi2 : sata_via
ata4: no device found (phy stat 00000000)
scsi3 : sata_via
ata3: command 0xa0 timeout, stat 0xd0 host_stat 0x1

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)
#8 lore raw
In reply to Jeff Garzik
Quoted 7 lines · Jeff Garzik
Quoted 6 lines

I've been unable to figure out what is supposed to tie sr to the devices probed by sata_via. Also, littering sr with printk's gave me the idea that sr is not even looking for cdrom devices. It loads, does the basic module __init stuff and then silence. Should sr find devices itself or is the kernel supposed to inform sr via some callback hook? I could really be barking up the wrong tree here, and not even see it.

Did you turn on ATA_ENABLE_ATAPI in include/linux/libata.h?

Seems like there's another guy reporting pretty much the same problem. Also sata_via and the Plextor 712SA SATA DVD drive. Different motherboard though.

http://lkml.org/lkml/2005/3/25/259

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)

A message that is not in the archive (sent off-list or not yet received): [email protected]

#10 lore raw
Quoted 4 lines · Andy Stewart

I have a patch that partially solves this situation. My patch allows the SATA ATAPI device to be seen, mounted, umounted, and read without problem. Writes to the device fail miserably, and I haven't debugged that yet. Also, the use of the 'dd' command with my patch works unless

Quoted 8 lines

'dd' is allowed to read off the end of the CD, in which case there is a kernel oops (easily reproduced, and I've not yet debugged that failure, but I have a theory).
Since my patch isn't a complete solution, I haven't told anybody about it until now. However, if you are interested in my patch despite its limitations, please let me know, and I'll be happy to share it with you.
My work was done with the 2.6.11.5 kernel and is limited to one or two
files, if I recall correctly.

I'd very much like to see what you came up with. I'm currently playing with 2.6.11.7 but I doubt there's much difference in this area from .5.

Signature · 8 lines
Regards,
Tais M. Hansen
OSD

___________________________________________________________
"If people had understood how patents would be granted when most of today's 
ideas were invented and had taken out patents, the industry would be at a 
complete standstill today." -Bill Gates (1991)