On Tue, 2005-06-21 at 21:47 +0400, Yuri Kirsanov wrote: > Roger, dmesg (sata_promise doesn't load at boot time for some reason, > so i start it by 'modprobe sata_promise'):
Hmm, then I guess it would be very interesting to know WHY it doesn't load at boot time! What are the symptoms? > sata_promise version 1.01 > PCI: Found IRQ 5 for device 0000:01:09.0 > ata1: PATA max UDMA/133 cmd 0xCCB4A200 ctl 0xCCB4A238 bmdma 0x0 irq 5 > ata2: PATA max UDMA/133 cmd 0xCCB4A280 ctl 0xCCB4A2B8 bmdma 0x0 irq 5 > ata3: PATA max UDMA/133 cmd 0xCCB4A300 ctl 0xCCB4A338 bmdma 0x0 irq 5 > ata4: PATA max UDMA/133 cmd 0xCCB4A380 ctl 0xCCB4A3B8 bmdma 0x0 irq 5 > ata1: no device found (phy stat 00000000) > scsi0 : sata_promise > ata2: no device found (phy stat 00000000) > scsi1 : sata_promise > ata3: no device found (phy stat 00000000) > scsi2 : sata_promise > ata4: no device found (phy stat 00000000) > scsi3 : sata_promise It seems to strange to me that sata reports PATA devices... What kind of harddisks do you connected (brand, type, pata/sata?)
signature.asc
Description: This is a digitally signed message part
