As I previousy wrote, I switched from SATA to IDE mode in BIOS (after which everything started working), so the system no longer recognizes ahcisata. Here's the output for my HD and CD:
wd0 at atabus0 drive 0 wd0: <ST9500325AS> wd0: drive supports 16-sector PIO transfers, LBA48 addressing wd0: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168 sectors wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) atapibus0 at atabus1: 2 targets cd0 at atapibus0 drive 0: <MATSHITADVD-RAM UJ890AS, UH44 215630, 1.00> cdrom removable cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) 2016-09-11 12:33 GMT+03:00 Michael van Elst <[email protected]>: > [email protected] ("Andrei M.") writes: > >>No, this happened when the installation CD was loading. I've had >>exactly the same problem in the installation process last year, see >>attachment. > > The screenshot shows > > two SATA devices that couldn't be recognized. > one USB umass device. > > The information about the CD has either scrolled off, or it's > one of the SATA devices, probably the latter (with only 1.5Gb/s on > the second port). > > Can you identify your ahcisata controller? E.g.: > > ahcisata0 at pci0 dev 31 function 2: vendor 0x8086 product 0x8c02 (rev. 0x04) > ahcisata0: interrupting at ioapic0 pin 19 > ahcisata0: 64-bit DMA > ahcisata0: AHCI revision 1.30, 6 ports, 32 slots, CAP > 0xc730ff45<EMS,PSC,SSC,PMD,ISS=0x3=Gen3,SCLO,SAL,SALP,SNCQ,S64A> > > -- > -- > Michael van Elst > Internet: [email protected] > "A potential Snark may lurk in every tree."
