[OpenIndiana-discuss] JMB363 Chipset support in OI_148

[Robin Axelsson]

On 2011-05-08 22:50, Albert Lee wrote:
> On Sun, May 8, 2011 at 5:33 AM, Sean O'Brien<upinthecloudz at gmail.com>  wrote:
>> I have a pci-express card based on JMB363 chipset, because it is listed in
>> HCL. The card is recognized by the ahci driver.
>>
>> model:  'SATA AHCI 1.0 Interface'
>>                 power-consumption:  00000001.00000001
>>                 devsel-speed:  00000000
>>                 interrupts:  00000001
>>                 subsystem-vendor-id:  0000197b
>>                 subsystem-id:  00002363
>>                 unit-address:  '0'
>>                 class-code:  00010601
>>                 revision-id:  00000002
>>                 vendor-id:  0000197b
>>                 device-id:  00002363
>>                 name:  'pci197b,2363'
>>
>> The device is seen by cfgadm as well, but an attempt to connect a drive or
>> to reset the controller results in the following in /var/adm/messages:
>>
>> May  8 01:54:36 fileserv ahci: [ID 860969 kern.warning] WARNING: ahci1:
>> ahci_port_reset port 0 the device hardware has been initialized and the
>> power-up diagnostics failed
>> May  8 01:54:59 fileserv ahci: [ID 860969 kern.warning] WARNING: ahci1:
>> ahci_port_reset port 1 the device hardware has been initialized and the
>> power-up diagnostics failed
>>
>>
>> There are some patches posted for an old version of OpenSolaris to resolve
>> issues with the ahci driver and this card.
>> http://web.archiveorange.com/archive/v/1sSOwqLUl8mdFzhkydYU
>>
>> Would it be possible to apply these patches to the kernel source for oi_148?
>> Any assistance or guidance on compiling this would be much appreciated.
> Hi Sean,
>
> Thanks for the pointer, unfortunately both of those bugs were fixed in 2008 as:
> 6645543 relax AHCI checks violated by JMicron JMB363 controller
> 6648246 AHCI driver looks for its registers wrongly, blocking support
> for JMicron JMB363
>
> This is not the first time problems have been mentioned for JMB363
> controllers recently, though.
>
> If you're interested in looking into this problem, you should sign up
> on the illumos developer mailing list.
> http://www.illumos.org/projects/site/wiki/Mailing_Lists
> Also, the build instructions are here:
> http://www.illumos.org/projects/illumos-gate/wiki/How_To_Build_Illumos
>
> -Albert
>
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

A question is if anyone has managed to get the JMB363 to work properly 
at all on any operating system. I haven't. On windows there are no error 
messages, but hard drives on that controller disappear mysteriously and 
become irresponsive from time to time, sometimes during startup not even 
BIOS can identify hard drives connected to it and diagnostics software 
(such as Samsung ESTOOL) almost always identifies errors on any hard 
drive connected to it. I have tested this on several different 
motherboards and came to the same conclusion. I personally think it is a 
broken controller.