From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Date: Mon, 17 Dec 2007 13:28:09 +0000 From: Bob Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <9d2fdca3-705f-4f28-a98d-432019d157bb@d27g2000prf.googlegroups.com> Subject: [9fans] Intel Sata Topicbox-Message-UUID: 1b3ae0c0-ead3-11e9-9d60-3106f5b1d025 On Dec 17, 7:56 am, quans...@quanstro.net (erik quanstrom) wrote: > > I modified sdata.c. Added the device id, which was 27c1. I can provide > > the whole pci output from Solaris. Its rather long. Then the kernel > > seemed to recognize it once i added the id. I'll look at the other > > file. > > is this a sata or pata disk? > > if this is a sata disk, i believe this chipset is already supported in ahci mode. > we have machines around here with the same south bridge. > > to enable ahci mode in bios, generally one needs to change the sata mode > to enhanced and, for this particular chipset, i believe it's necessary to enable > ahci mode. for the esb chipsets enabling ahci mode is not necessary. > when you enable ahci, you should have a second device show up that starts > 0x27cx. > > - erik Well 9load seemed to recognize it from the get go. The kernel however did not. I added the device ID, which after many hours turned out to be 27C0 not 27C1, and it recognized the hard drive, i think. The kernel prints a message detailing the sata port. 9load says its #S/ sdE0, but when I try to tell the kernel the root fs is local!#/sdE0! fossil the kernel panics because it can't connect to the given server. Any ideas? Bob