Why can it be?. Could you pass on a link please of your setup? You can use these HTML tags. Problems Only modifying register df[1: They certainly appear to be the same, I have replaced the orom inside the bios of the R3E and the device is now running in AHCI mode.

Uploader: Zulujin
Date Added: 22 January 2004
File Size: 65.65 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 94175
Price: Free* [*Free Regsitration Required]

This is done the same way as with any other disk.

LITEON JF support JMicron JMB controller? No Drive detected!

I think what you want is to change b1 02 to b1 Option ROM not enabled by setting df[6], so the disks are not bootable. Why can it be?.

What am I missing? Unfortunately, I do not know enough about hex editing to find where to patch. Or is there any trick?

Register df[6] is used by the option ROM code at offset 0x These configuration registers seem to control the hardware directly. Header Type ‘non-bridge’ single-func Vendor: Linux sets register 0x41 to 0xa1, while the option ROM will set it to 0xf1 or 0x Actually, there is only one sata connexion, not two.


JMicron JMB363 eSATA Controller Drivers

The sum of all bytes in the file should be 0x Linux sets register 40 bit 2 to enable the IDE port? I want to boot an ide hd xontroller a jmb card.

They seem important, causing PCI config register bits 0xed[5: The last byte of the file is used as a checksum. Seems to take values of 0xc2 or controllee You can download 1. Change three instances of b1 02 to b1 I tried modifying the option ROM to also configure register 0x to this value, but had many problems booting. It seems like bits [1: Can we get an update jkb363 firmware v1.

Duufus, I had in the past this card: You know if it is possible?. I used the newest version of the option ROM 1.

The option ROM loads, correctly reports connected drives, and allows booting from them. Which can be found here: It would be great if you can test it.


JMicron JMB eSATA Controller Drivers JMB36X

Therefore, I chose to set register df[6] to cause the option ROM to quit without detecting drives. I made changes at three locations: I did have some issues with the card being seated properly in the PCIe slot. The hang does not occur if the option ROM is skipped by setting 0xdf[6], so I use 0xa1 to be closer to what Linux does, although I notice no other differences between 0xf1 and 0xa1.

Could you pass on a link please of your setup? Register Function 43 Defaults to 0x The edits are in x86 machine code.