* AHCI and VT8251
@ 2005-11-10 3:14 Andrew Joyce
2005-11-10 23:47 ` Jeff Garzik
0 siblings, 1 reply; 3+ messages in thread
From: Andrew Joyce @ 2005-11-10 3:14 UTC (permalink / raw)
To: linux-ide
I am trying to get a system using a VIA VT8251 chipset up and running.
The chip claims to comply to the AHCI standard so, much like a previous
poster, I added the PCI ID of the controller into the AHCI driver,
compiled the 2.6.14 kernel and crossed my fingers. I met with the same
problems as were found earlier. I am fairly certain this is an issue
with the kernel driver and the new VT8251 chipset. As far as I can tell
this is the first board the chip is shipping in and the board has only
been on the market for about a month at this stage.
I am presently unsure how to proceed in order to diagnose or address
this problem. My experience with kernel hacking is pretty limited but I
would be willing to help out by testing whatever I can and I am happy to
do some legwork and research to get this going. Would anyone be
interested in helping me address this problem?
I have attached the relevant portions of kernel messages below.
Thanks,
Andrew
=========================================================================
SCSI subsystem initialized
libata version 1.12 loaded.
ahci version 1.01
ACPI: PCI Interrupt 0000:00:0f.0[B] -> GSI 21 (level, low) -> IRQ 19
PCI: Via IRQ fixup for 0000:00:0f.0, from 10 to 3
ahci(0000:00:0f.0) AHCI 0001.0000 32 slots 4 ports 3 Gbps 0xf impl SATA
mode
ahci(0000:00:0f.0) flags: 64bit ncq pm led clo pmp pio slum part
ata1: SATA max UDMA/133 cmd 0xFFFFC20000006D00 ctl 0x0 bmdma 0x0 irq 19
ata2: SATA max UDMA/133 cmd 0xFFFFC20000006D80 ctl 0x0 bmdma 0x0 irq 19
ata3: SATA max UDMA/133 cmd 0xFFFFC20000006E00 ctl 0x0 bmdma 0x0 irq 19
ata4: SATA max UDMA/133 cmd 0xFFFFC20000006E80 ctl 0x0 bmdma 0x0 irq 19
ata1 is slow to respond, please be patient
ata1 failed to respond (30 secs)
scsi0 : ahci
ata2: no device found (phy stat 00000000)
scsi1 : ahci
ata3: no device found (phy stat 00000000)
scsi2 : ahci
ata4: no device found (phy stat 00000000)
scsi3 : ahci
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: AHCI and VT8251
2005-11-10 3:14 AHCI and VT8251 Andrew Joyce
@ 2005-11-10 23:47 ` Jeff Garzik
0 siblings, 0 replies; 3+ messages in thread
From: Jeff Garzik @ 2005-11-10 23:47 UTC (permalink / raw)
To: Andrew Joyce; +Cc: linux-ide
Andrew Joyce wrote:
> I am trying to get a system using a VIA VT8251 chipset up and running.
> The chip claims to comply to the AHCI standard so, much like a previous
> poster, I added the PCI ID of the controller into the AHCI driver,
> compiled the 2.6.14 kernel and crossed my fingers. I met with the same
> problems as were found earlier. I am fairly certain this is an issue
> with the kernel driver and the new VT8251 chipset. As far as I can tell
> this is the first board the chip is shipping in and the board has only
> been on the market for about a month at this stage.
>
> I am presently unsure how to proceed in order to diagnose or address
> this problem. My experience with kernel hacking is pretty limited but I
> would be willing to help out by testing whatever I can and I am happy to
> do some legwork and research to get this going. Would anyone be
> interested in helping me address this problem?
>
> I have attached the relevant portions of kernel messages below.
Does disabling PCI MSI fix things?
Jeff
^ permalink raw reply [flat|nested] 3+ messages in thread
* AHCI and VT8251
@ 2005-11-11 20:33 Don Carroll
0 siblings, 0 replies; 3+ messages in thread
From: Don Carroll @ 2005-11-11 20:33 UTC (permalink / raw)
To: linux-ide
Jeff, disabling PCI MSI does not help
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-11-11 20:34 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-11-10 3:14 AHCI and VT8251 Andrew Joyce
2005-11-10 23:47 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2005-11-11 20:33 Don Carroll
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).