Skip to contentSkip to conversation

can't see drive on promise 20375 ATA card

DISCUSSION sean 3 participants 6 messages May 8, 2004 – May 10, 2004

lore
Share & tools
lore

sean

author
#0 lore raw

got a maxtor sata/i50 combo card today. It uses the promise 20375 chip with 2 SATA ports and one ATA port.

Using 2.6.6-rc3-bk8.

grep SATA .config
CONFIG_SCSI_SATA=y
# CONFIG_SCSI_SATA_SVW is not set
CONFIG_SCSI_SATA_PROMISE=y

Also:

# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set

should they be?

dmesg has:

libata version 1.02 loaded.
sata_promise version 0.92
ata1: SATA max UDMA/133 cmd 0xE1863200 ctl 0xE1863238 bmdma 0x0 irq 19
ata2: SATA max UDMA/133 cmd 0xE1863280 ctl 0xE18632B8 bmdma 0x0 irq 19
ata1: no device found (phy stat 00000000)
ata1: thread exiting
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
ata2: thread exiting
scsi1 : sata_promise

So it can see the SATA ports.

How do I get the kernel to see the ATA port on the card?

thanks

sean

author
#1 lore raw

Also, on boot, the SATA card bios is loaded and sees the PATA drive.

sean

author
#2 lore raw

Looking at the source - usually foolhardy at least for me, I find this at lines 1806-1808 of sata_promise.c:

              case board_2037x:
       		probe_ent->n_ports = 2;
		break;

Is the solution here as simple as changing two to three? Does this break somethng else?

Has anyone else got this board to work? It's been out over a year.

sean

#3 lore raw
In reply to sean
Quoted 12 lines · sean

libata version 1.02 loaded.
sata_promise version 0.92
ata1: SATA max UDMA/133 cmd 0xE1863200 ctl 0xE1863238 bmdma 0x0 irq 19
ata2: SATA max UDMA/133 cmd 0xE1863280 ctl 0xE18632B8 bmdma 0x0 irq 19
ata1: no device found (phy stat 00000000)
ata1: thread exiting
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
ata2: thread exiting
scsi1 : sata_promise

Quoted 3 lines

So it can see the SATA ports.

How do I get the kernel to see the ATA port on the card?

The driver does not support the PATA ports.

Jeff

#4 lore raw
Quoted 13 lines · Jeff Garzik
Quoted 12 lines · sean

libata version 1.02 loaded.
sata_promise version 0.92
ata1: SATA max UDMA/133 cmd 0xE1863200 ctl 0xE1863238 bmdma 0x0 irq 19
ata2: SATA max UDMA/133 cmd 0xE1863280 ctl 0xE18632B8 bmdma 0x0 irq 19
ata1: no device found (phy stat 00000000)
ata1: thread exiting
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
ata2: thread exiting
scsi1 : sata_promise

Quoted 6 lines
Quoted 3 lines

So it can see the SATA ports.

How do I get the kernel to see the ATA port on the card?

The driver does not support the PATA ports.

Do you think it is reasonable to include support for PATA ports in your code?

#5 lore raw
Quoted 18 lines · Marc Singer
Quoted 16 lines · Jeff Garzik
Quoted 14 lines · sean

libata version 1.02 loaded.
sata_promise version 0.92
ata1: SATA max UDMA/133 cmd 0xE1863200 ctl 0xE1863238 bmdma 0x0 irq 19
ata2: SATA max UDMA/133 cmd 0xE1863280 ctl 0xE18632B8 bmdma 0x0 irq 19
ata1: no device found (phy stat 00000000)
ata1: thread exiting
scsi0 : sata_promise
ata2: no device found (phy stat 00000000)
ata2: thread exiting
scsi1 : sata_promise

So it can see the SATA ports.

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

How do I get the kernel to see the ATA port on the card?

The driver does not support the PATA ports.

Do you think it is reasonable to include support for PATA ports in your code?

It is very reasonable :) I just haven't had the time to do it yet.

Jeff