Eide channel on ASUS P5E3 Deluxe not working.

[Robin Bignall]

I've now got my SATA-based system working and thought I'd add a couple
more EIDE HDDs. In addition to SATA on the m/b, there is also one
EIDE channel to take up to two devices, as usual. This m/b also has
an additional Jmicron controller connected to two SATA ports on the
back panel, to support RAID or external devices for large data
volumes. If you boot showing the memory checks and other boot items
you see that this extra controller activates after the main boot, and,
correctly, reports "no devices detected" because I haven't any. All of
these SATA channels are set to IDE because I do not use RAID.

Right, so I add a couple of HDDs on the eide channel. It makes no
difference if they're correctly connected master and slave, or CS.
With the Jmicron disabled they are not detected by BIOS. "My Computer"
sometimes shows one or the other of them, but they're marked as not
accessible. If I enable the Jmicron, one or the other is shown when
it boots, again inaccessible to XP. (I have the latest BIOS installed
and working.)

This is really weird. Why doesn't the main BIOS detect devices on the
eide channel, and why should a SATA controller with no devices
connected seem to see them? Anybody got any ideas?

 

[housetrained]

"All of these SATA channels are set to IDE because I do not use RAID."
This I do not quite understand.

 

[Paul]

I've now got my SATA-based system working and thought I'd add a couple
more EIDE HDDs. In addition to SATA on the m/b, there is also one
EIDE channel to take up to two devices, as usual. This m/b also has
an additional Jmicron controller connected to two SATA ports on the
back panel, to support RAID or external devices for large data
volumes. If you boot showing the memory checks and other boot items
you see that this extra controller activates after the main boot, and,
correctly, reports "no devices detected" because I haven't any. All of
these SATA channels are set to IDE because I do not use RAID.

Right, so I add a couple of HDDs on the eide channel. It makes no
difference if they're correctly connected master and slave, or CS.
With the Jmicron disabled they are not detected by BIOS. "My Computer"
sometimes shows one or the other of them, but they're marked as not
accessible. If I enable the Jmicron, one or the other is shown when
it boots, again inaccessible to XP. (I have the latest BIOS installed
and working.)

This is really weird. Why doesn't the main BIOS detect devices on the
eide channel, and why should a SATA controller with no devices
connected seem to see them? Anybody got any ideas?

ICH9R 6 SATA

JMB363 1 UltraDMA 133/100 for up to 2 PATA devices
2 External SATA

The main BIOS code module handles the Southbridge (ICH9R). The main
screen will show the status of the 6 SATA ports.

When separate chips are added to a motherboard, such as the hybrid Jmicron
part, a separate code module is added to the BIOS for that. It is not
as tightly integrated into the BIOS.

Enabling or disabling the JMB363, will affect all the resources on the chip.
The JMB363 controls both EIDE and SATA devices.

What the separate code module should do for JMB363 -

1) Support pressing Ctrl-J, for accessing the Jmicron SATA ports and
RAID functions. The separate code module will sllow writing metadata
on two SATA hard drives, marking them as RAID0 or RAID1. Control-J
only works, if the chip is set to RAID mode.

2) During POST, the add-in code module will show a few lines "Detecting..."
and indicate what storage devices were found on the various Jmicron ports.

3) In all modes, the code will register extended INT 0x13 support for booting.
Booting from Jmicron RAID or booting from an EIDE, would be supported by
that, and the boot menu should be showing things connected to the Jmicron.
They show up, because they've been registered via INT 0x13.

*Note - check the BIOS, and enable "Interrupt 19 Capture" ! That is how
add-in code modules get loaded, for hardware outside the chipset. Decimal 19
equals hexidecimal 0x13.

4) The SATA ports can be set to IDE, AHCI, or RAID. AHCI or RAID, would require
a separate driver to be installed. (AHCI supports hot plugging, amongst other
things.) A SATA port in IDE mode, could end up mapped into the "PCI space",
where a Microsoft PCI driver could find it.

5) The EIDE port might also end up PCI mapped, where a Microsoft PCI space driver
can find it. The Microsoft PCI driver became available in WinXP SP1 as
far as I know. The older, I/O space driver, is what was used previously,
and that is also still available (Microsoft has two default driver options).

I would think you could install WinXP on an EIDE drive connected to the Jmicron.
As long as the WinXP disk has SP1 or has it slipstreamed.

Different brands of drives use different modes for their jumpering.
Such as Master, Master only, Master with Slave and so on. If mixing
different brands, check the jumper settings shown on the drive label.
The disk manufacturer web site, sometimes shows more jumper options
on a web page, than were shown on the label (such as the position and
usage of the "clip" jumper, to limit an IDE drive to 32GB size).

Best guess (i.e. not likely to find documentation),
Paul

 

[Robin Bignall]

Thanks for this very helpful post, Paul.

ICH9R 6 SATA

JMB363 1 UltraDMA 133/100 for up to 2 PATA devices
2 External SATA

The main BIOS code module handles the Southbridge (ICH9R). The main
screen will show the status of the 6 SATA ports.

When separate chips are added to a motherboard, such as the hybrid Jmicron
part, a separate code module is added to the BIOS for that. It is not
as tightly integrated into the BIOS.

Enabling or disabling the JMB363, will affect all the resources on the chip.
The JMB363 controls both EIDE and SATA devices.

What the separate code module should do for JMB363 -

1) Support pressing Ctrl-J, for accessing the Jmicron SATA ports and
RAID functions. The separate code module will sllow writing metadata
on two SATA hard drives, marking them as RAID0 or RAID1. Control-J
only works, if the chip is set to RAID mode.

2) During POST, the add-in code module will show a few lines "Detecting..."
and indicate what storage devices were found on the various Jmicron ports.

3) In all modes, the code will register extended INT 0x13 support for booting.
Booting from Jmicron RAID or booting from an EIDE, would be supported by
that, and the boot menu should be showing things connected to the Jmicron.
They show up, because they've been registered via INT 0x13.

*Note - check the BIOS, and enable "Interrupt 19 Capture" ! That is how
add-in code modules get loaded, for hardware outside the chipset. Decimal 19
equals hexidecimal 0x13.

I'm with you up to here, but even with the Jmicron enabled the BIOS
does not show an "interrupt 19 capture" line on the Boot settings
screen, even though it's mentioned in the manual.

4) The SATA ports can be set to IDE, AHCI, or RAID. AHCI or RAID, would require
a separate driver to be installed. (AHCI supports hot plugging, amongst other
things.) A SATA port in IDE mode, could end up mapped into the "PCI space",
where a Microsoft PCI driver could find it.

5) The EIDE port might also end up PCI mapped, where a Microsoft PCI space driver
can find it. The Microsoft PCI driver became available in WinXP SP1 as
far as I know. The older, I/O space driver, is what was used previously,
and that is also still available (Microsoft has two default driver options).

I would think you could install WinXP on an EIDE drive connected to the Jmicron.
As long as the WinXP disk has SP1 or has it slipstreamed.

Different brands of drives use different modes for their jumpering.
Such as Master, Master only, Master with Slave and so on. If mixing
different brands, check the jumper settings shown on the drive label.
The disk manufacturer web site, sometimes shows more jumper options
on a web page, than were shown on the label (such as the position and
usage of the "clip" jumper, to limit an IDE drive to 32GB size).

Best guess (i.e. not likely to find documentation),

I've got XP SP3 installed on SATA1, with all critical updates. The
eide disks worked well under SP3 on my previous (ASUS) board. I'll
check the jumpers again, and see what happens. But before, the
Jmicron did "see" the disk on the master position and "My Computer"
could also "see" it, but XP wouldn't even format it. I can't remember
the exact message: something like "Disk not accessible" or words to
that effect.

 

[Paul]

I'm with you up to here, but even with the Jmicron enabled the BIOS
does not show an "interrupt 19 capture" line on the Boot settings
screen, even though it's mentioned in the manual.

I've got XP SP3 installed on SATA1, with all critical updates. The
eide disks worked well under SP3 on my previous (ASUS) board. I'll
check the jumpers again, and see what happens. But before, the
Jmicron did "see" the disk on the master position and "My Computer"
could also "see" it, but XP wouldn't even format it. I can't remember
the exact message: something like "Disk not accessible" or words to
that effect.

I'd need to find someone else's Device Manager display for the
JMB363, to see if there is anything special about it. I thought
the idea was, that for the EIDE, you could at least boot from a
bootable CD, while connected to it. Otherwise, it would be
pretty useless.

When you update the motherboard main BIOS, you also get whatever
version of JMB363 add-on module they choose to include inside the
image. So it is remotely possible, that a different version of
main BIOS, will change the symptoms. (I tried to use my copy
of MMTOOL on the P5E3 Deluxe BIOS, but it crashed. MMTOOL can be
used to take apart a BIOS, and expand the add-in modules.)

The guys here had some trouble with JMB36x family and their burners.
But this thread is from 2006.

http://club.cdfreaks.com/f61/jmicron-jmb363-189057/

I have a quick look on vip.asus.com, but don't see issues with
JMB363 listed for your board.

I don't know what the deal is with the "Interrupt 19 capture". If
the manual shows it, you'd think it would be there somewhere. It
always surprises me, to see the default for it listed as disabled,
in the manuals I see it in.

Paul

 

[Robin Bignall]

I'd need to find someone else's Device Manager display for the
JMB363, to see if there is anything special about it. I thought
the idea was, that for the EIDE, you could at least boot from a
bootable CD, while connected to it. Otherwise, it would be
pretty useless.

When you update the motherboard main BIOS, you also get whatever
version of JMB363 add-on module they choose to include inside the
image. So it is remotely possible, that a different version of
main BIOS, will change the symptoms. (I tried to use my copy
of MMTOOL on the P5E3 Deluxe BIOS, but it crashed. MMTOOL can be
used to take apart a BIOS, and expand the add-in modules.)

The guys here had some trouble with JMB36x family and their burners.
But this thread is from 2006.

http://club.cdfreaks.com/f61/jmicron-jmb363-189057/

I have a quick look on vip.asus.com, but don't see issues with
JMB363 listed for your board.

I don't know what the deal is with the "Interrupt 19 capture". If
the manual shows it, you'd think it would be there somewhere. It
always surprises me, to see the default for it listed as disabled,
in the manuals I see it in.

It's shown as defaulting to disabled in the manual. I've downloaded
and installed the latest BIOS and Jmb drivers, and I've got the Jmb
enabled and set to ide, but still no actual int 19 line in the bios.

To tell you the truth, I'm not too worried about the eide disks not
working at this stage. Everything else is, and I've got plenty of HDD
space. Physically working on the system is hard for me (I'm disabled)
now it's on the floor rather than a workbench, so I'll have another
try with eide when a friend can help.

Thanks again for your assistance.