On Dec 17, 7:56 am, [EMAIL PROTECTED] (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

Reply via email to