Has anyone been able to boot a SATA drive using FILO on a 690/600 platform? I keep getting IDE timeouts on detection. I originally thought that it might be the SATA flash that I am using, but it does the same thing with a standard HDD. Both devices are SATA 1.5g drives, so maybe my last patch to fall down to 1.5g is incomplete or broken? I don't have any SATA 2.0 drives around.
I have compared PCI configs between the prop BIOS and CB. From what I can see all of the settings that need to be the same are.
If someone else could give this a shot it would be appreciated. Any good ideas where to start trying to debug this would be appreciated also. I have already turned on debug messages, but the FILO prompt currently wipes them out before I can grab them so I can't post a log yet.
I have another question dealing with PCI numbering if someone has the time to answer it. 690/600 SATA is Bus 0: Dev 18: Func 0 in the docs. How/Why/Where did it get 0:12:0 ? in the OS and in some places in CB(dts)? Am I mixing two different things up? I would like to know what I am missing.
Thanks, Dan Lykowski
I have another question dealing with PCI numbering if someone has the time to answer it. 690/600 SATA is Bus 0: Dev 18: Func 0 in the docs. How/Why/Where did it get 0:12:0 ? in the OS and in some places in CB(dts)? Am I mixing two different things up? I would like to know what I am missing.
It looks like the docs are using decimal. CB uses hex for device numbers.
Sorry to only answer the easy one :)
Myles
On 16.01.2009 20:41, Dan Lykowski wrote:
Has anyone been able to boot a SATA drive using FILO on a 690/600 platform?
Yes, I'm booting from SATA using FILO on an Asus M2A-VM. However, my two SATA disks are SATA 2.0 they are connected the two ports of the first channel (Primary Master + Slave or whatever they are called now).
I keep getting IDE timeouts on detection. I originally thought that it might be the SATA flash that I am using, but it does the same thing with a standard HDD. Both devices are SATA 1.5g drives, so maybe my last patch to fall down to 1.5g is incomplete or broken? I don't have any SATA 2.0 drives around.
Could be. I remember getting IDE timeouts back when the code only supported one SATA drive.
I have compared PCI configs between the prop BIOS and CB. From what I can see all of the settings that need to be the same are.
If someone else could give this a shot it would be appreciated. Any good ideas where to start trying to debug this would be appreciated also. I have already turned on debug messages, but the FILO prompt currently wipes them out before I can grab them so I can't post a log yet.
Can you attach a serial console (minicom etc.) and log the boot messages there? That should work fine.
Just in case you're being hit by an old bug which was seemingly fixed, please check whether the behaviour differs between cold boot and warm reset (with the reset button). Oh, and you want to test this with only 1 GB of RAM. That may or may not help, but the DSDT is a bit peculiar.
Regards, Carl-Daniel
Dan Lykowski wrote:
Has anyone been able to boot a SATA drive using FILO on a 690/600 platform? I keep getting IDE timeouts on detection.
I would be interested in debug output from filo-0.5, e.g. r52, with http://stuge.se/filo.r52.ide_ext2_pio4_debug6.patch applied and both DEBUG_PCI = 1 and DEBUG_IDE = 1 in Config. Please also set USE_GRUB = 0 to make the interface easier to work with.
//Peter
-
Carl-Daniel Hailfinger -
Dan Lykowski -
Myles Watson -
Peter Stuge