JMicron JMB363 add-on-card shows up as RAID-class - EON 0.60 b130

[nnc tlb]

hello,

after having performance issues with a SIL3132 based controller I switched to a JMB363 based controller but start with the SIL3132:

dmesg is showing me a notice concerning IRQ sharing with my SIL3132, normally this shouldn´t be a problem, but it seems in my case it is.

so my idea was buying a JMB363, which uses ahci as driver in opensolaris (http://blog.zorinaq.com/?e=10), and hoping the ahci driver has no problem with irq-sharing, I tested opensolaris on my workstation with a jmb363 chip onboard, it worked.

so I bought a add-on card PCIe 1x based on JMB363 chip, unfortunataly the card is recognized as “raid-controller” (class-code 10400 not 10601 which is SATA AHCI 1.0) so the ahci driver is not attached.
so I went to the add-on-cards BIOS, hdds are configured as “non-raid” and found no option the select legacy IDE, AHCI or RAID like in the BIOS of the workstation-mainboard with the onboard 363.
flashed newer option-rom/bios for the add-on-card, but still no option and no AHCI.

windows xp and 7 also recognize the jmb363 based add-on-card as raid-class-controller.

but linux (partition magic 5.10) as two devices:
- IDE (nothing connected)
- AHCI (my 2 hdds and ahci-driver attached)

which would be nice for me if I wanna use linux (but I don’t) – but bad for people who actually use the card as raid (native by the chip and not via softraid under linux) if there is no switch to avoid this.

so how to achieve this under opensolaris ?
linux seems reading/writing pci(e)-register in “early stages” in linux/drivers/pci/quirks.c (http://lxr.linux.no/#linux v2.6.38/drivers/pci/quirks.c#L1478)

coreboot (a generic BIOS replacement) does similiar things (r/w pci-regs) with an SIL3114
http://tracker.coreboot.org/trac/coreboot/changeset/5560

[Andre Lue]

Hi nnc,

If it loads a functional driver(s) in opensolaris or live cd, you could identify and add the needed drivers to EON and it should work.

[nnc tlb]

@dre2kse

even openindiana 148 and opensol 134 are unable to use the jmb363 in raid-class-mode.
I nearly believe there is no jmb363-raid-driver for the non-MS-Windows-world.
linux quirks the controller to sata-ahci1.0-class-mode and uses the ahci-driver.

on my workstation with a jmb363-chip onboard I believe the mainboard-BIOS does the same things like linux (read/write pci(e)-regs/config-block) depending an selection in the mainboard-BIOS-settings and the onboard 363 is working with the ahci driver from EON 130 and openindiana 148.

solution for using the add-on card should be:
a) a hacked BIOS for my fileserver-mainboard ?
b) a quirks-kernel-module ?
c) hack the jmb363-bios, so the jmb363-addon-card starts in ahci-mode per default ?

b) would be the coolest and cleanest but I´m no kernel hacker.