Could you attach lspci -vn output?  And this is devel and not fc1
test, correct?

Yes, this is devel

lspci from my (kinda) working install follows:

0000:00:00.0 Class 0600: 1106:3188 (rev 01)
        Subsystem: 1462:1300
        Flags: bus master, 66Mhz, medium devsel, latency 8
        Memory at f0000000 (32-bit, prefetchable)
        Capabilities: [80] AGP version 3.0
        Capabilities: [c0] #08 [0060]
        Capabilities: [68] Power Management version 2
        Capabilities: [58] #08 [8001]
 
0000:00:01.0 Class 0604: 1106:b188
        Flags: bus master, 66Mhz, medium devsel, latency 0
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 0000a000-0000afff
        Memory behind bridge: f8000000-f9ffffff
        Prefetchable memory behind bridge: d0000000-efffffff
        Expansion ROM at 0000a000 [disabled] [size=4K]
        Capabilities: [80] Power Management version 2
 
0000:00:05.0 Class 0100: 9005:0010
        Subsystem: 9005:a180
        Flags: bus master, medium devsel, latency 32, IRQ 16
        BIST result: 00
        I/O ports at b000
        Memory at fb014000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [dc] Power Management version 1
 
0000:00:06.0 Class 0401: 1102:0004 (rev 04)
        Subsystem: 1102:1007
        Flags: bus master, medium devsel, latency 32, IRQ 17
        I/O ports at b400
        Capabilities: [dc] Power Management version 2
 
0000:00:06.1 Class 0980: 1102:7003 (rev 04)
        Subsystem: 1102:0060
        Flags: bus master, medium devsel, latency 32
        I/O ports at b800
        Capabilities: [dc] Power Management version 2
 
0000:00:06.2 Class 0c00: 1102:4001 (rev 04) (prog-if 10)
        Subsystem: 1102:0010
        Flags: bus master, medium devsel, latency 32, IRQ 18
        Memory at fb015000 (32-bit, non-prefetchable)
        Memory at fb010000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [44] Power Management version 2
 
0000:00:0b.0 Class 0200: 14e4:1653 (rev 03)
        Subsystem: 1462:1300
        Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 16
        Memory at fb000000 (64-bit, non-prefetchable)
        Capabilities: [48] Power Management version 2
        Capabilities: [50] Vital Product Data
        Capabilities: [58] Message Signalled Interrupts: 64bit+
Queue=0/3 Enable-
 
0000:00:0f.0 Class 0104: 1106:3149 (rev 80)
        Subsystem: 1462:1300
        Flags: bus master, medium devsel, latency 32, IRQ 20
        I/O ports at bc00
        I/O ports at c000 [size=4]
        I/O ports at c400 [size=8]
        I/O ports at c800 [size=4]
        I/O ports at cc00 [size=16]
        I/O ports at d000 [size=256]
        Capabilities: [c0] Power Management version 2
 
0000:00:0f.1 Class 0101: 1106:0571 (rev 06) (prog-if 8a [Master SecP
PriP])
        Subsystem: 1462:1300
        Flags: bus master, medium devsel, latency 32, IRQ 20
        I/O ports at d400 [size=16]
        Capabilities: [c0] Power Management version 2
 
0000:00:10.0 Class 0c03: 1106:3038 (rev 81)
        Subsystem: 1462:1300
        Flags: bus master, medium devsel, latency 32, IRQ 21
        I/O ports at d800 [size=32]
        Capabilities: [80] Power Management version 2
 
0000:00:10.1 Class 0c03: 1106:3038 (rev 81)
        Subsystem: 1462:1300
        Flags: bus master, medium devsel, latency 32, IRQ 21
        I/O ports at dc00 [size=32]
        Capabilities: [80] Power Management version 2
 
0000:00:10.2 Class 0c03: 1106:3038 (rev 81)
        Subsystem: 1462:1300
        Flags: bus master, medium devsel, latency 32, IRQ 21
        I/O ports at e000 [size=32]
        Capabilities: [80] Power Management version 2
 
0000:00:10.4 Class 0c03: 1106:3104 (rev 86) (prog-if 20)
        Subsystem: 1462:1300
        Flags: bus master, medium devsel, latency 32, IRQ 21
        Memory at fb016000 (32-bit, non-prefetchable)
        Capabilities: [80] Power Management version 2
 
0000:00:11.0 Class 0601: 1106:3227
        Subsystem: 1462:1300
        Flags: bus master, stepping, medium devsel, latency 0
        Capabilities: [c0] Power Management version 2
 
0000:00:18.0 Class 0600: 1022:1100
        Flags: fast devsel
        Capabilities: [80] #08 [2101]
        Capabilities: [a0] #08 [2101]
        Capabilities: [c0] #08 [2101]
 
0000:00:18.1 Class 0600: 1022:1101
        Flags: fast devsel
 
0000:00:18.2 Class 0600: 1022:1102
        Flags: fast devsel
 
0000:00:18.3 Class 0600: 1022:1103
        Flags: fast devsel
 
0000:01:00.0 Class 0300: 1002:4152
        Subsystem: 1043:c002
        Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 16
        Memory at d0000000 (32-bit, prefetchable)
        I/O ports at a000 [size=256]
        Memory at f9000000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [58] AGP version 3.0
        Capabilities: [50] Power Management version 2
 
0000:01:00.1 Class 0380: 1002:4172
        Subsystem: 1043:c003
        Flags: 66Mhz, medium devsel
        Memory at e0000000 (32-bit, prefetchable) [disabled]
        Memory at f9010000 (32-bit, non-prefetchable) [disabled]
[size=64K]
        Capabilities: [50] Power Management version 2


If it makes a difference I can try and run it from the installer later
tonight.

Not sure if this matters, but I'm having to boot using acpi=off else I
get weird timeouts on the sata drive.

And, just because : )  I noticed tonight, that I can't install using a
usb keyboard, once the installer begins, my keyboard stops working. 
(I was using a ps/2 adapter before).

Isn't this a general hwdata issue, the libata drivers don't seem to be
listed at all. Or am I missing something? :-)

It's in modules.pcimap, so it should work. Is it in module-info?

I think this is explained by modules.pcitable being empty lately
(snapshot from 03-06) I checked yesterdays snapshot and it looks sane
now, so this bug might even be fixed. Will check later tonight.

I saw this same problem on a x86 (promise sata), an additional problem
to autoloading not working was that manual installation didn't work
either, the only option given was a driver disk. In test1 the module
could be loaded manually just fine.

Yes, this should be fixed by current rawhide since modules.pcimap now
gets generated correctly.

Works for me now, hopefully for the original reporter as well.

Close, but now while it loads the sata_via module, it doesn't create
the /dev/hde* devices   .. I just tested this using the boot.iso image
dated today (the 11th) and using ftp install from the duke mirror. 
Just in case it's relevent, I also have an adaptec scsi controller
installed, and it did pick that up and created the /dev/sd* devices.

Err... Unless something is completely different with sata_via, the
drive should be showing up as a SCSI one (i.e. /dev/sd* ). Check the
boot logs from virtual console 3 :-)

No, it comes up as /dev/hde and /dev/hdf (if I had a 2nd drive).. I
can go to the console and mknod /dev/hde and fdisk -l it to see my
existing partitions.  sata_via has been coming up as /dev/hde for a
bit over a month now.. can't remember exactly when it changed....
maybe it was with the 2.6 kernel?  I thought it was something they'd
changed for all the sata controllers, but maybe not, and I only have
one I can test : )

I guess I was supposed to change the status on this... I had retested,
and it was still broken (modules loads automatically now, but the
devices don't get created).

I think this is due to the legacy VIA IDE driver not masking SATA
ports to be used by the SATA driver instead.

Just tested with the FC2T3 install iso's and it works correctly..
Thanks to whoever fixed this : )  Let me know if you have any
questions, but I'd say this bug can be marked as resolved now. (Guess
I'll do that.)