On 12/03/2009 08:51, Alexander Motin wrote: > Have you tried to enable verbose boot messages? It may give some > additional info. Yep, tried it, but the dmesg buffer filled up with stuff like this: > ata2: siiprb_issue_cmd time=0ms status=00050000 > ata2: siiprb_issue_cmd time=0ms status=00010000 > ata2: siiprb_issue_cmd time=0ms status=00010000 > ata2: p0: connect status=00000000 > ata2: siiprb_issue_cmd time=0ms status=00010000 > ata2: siiprb_issue_cmd time=0ms status=00010000 > ata2: siiprb_issue_cmd time=27ms status=00010000 > ata2: p1: SIGNATURE=00000101 > ata2: siiprb_issue_cmd time=0ms status=00010000 and so on - probably about 50-100k of this sort of thing. So I have no idea what happened at the start of the card initialisation process. > Can you try to use AHCI controller present in your system instead of > SiI? It may allow to differentiate SiI controller related problems from > PM related ones. I don't have a sata->esata cable handy. However, I replaced the SiI3531 with a JMB366 card, and have attached the results of a verbose boot. > I am expecting to receive some PM hardware in a week or so, so I will be > able to test it's support, at least with AHCI. Oh cool. Would you like remote access to my box, btw? I might also be able to dig out an rs232 card somewhere for debugging. Nick
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:43 UTC