eSATA - esp. M2N-SLI Deluxe
Rajah!
Got an M2N-SLI Deluxe, running WinXPP SP3, 32 bit. Bought a Kingwin
EZD-2535 external HD dock, with USB and eSATA cable connection
options. USB works fine, nothing with eSATA.
Does anyone with an M2N-SLI Deluxe mobo have an eSATA based HD dock?
If so, what brand & model?
Both ASUS and Kingwin replaced their hardware trying to resolve the
problem. Both were extremely reasonable on the exchanges. I'm pretty
sure that this specific HD dock just will not work with this
particular mobo through the eSATA port - so I'm looking for one that
will.
Note - drives work fine when connected internally via internal SATA
port & power supply.
Paul
Did you install the JMB363 driver ? Do you see some kind of entry
in Device Manager, to show you the driver is installed ? Check the
INF file in the JMB363 driver folder, and read what entries
it is trying to create, and verify they exist in Device
Manager.
Have you unplugged the USB connector to the EZD-2535 ? You cannot
leave both the USB and ESATA connected at the same time. Enclosures
with multiple connectors, only support one connector at a time.
Connect only one cable. Turn off the enclosure power and then back
on again, so the enclosure detects which cable is in use.
As an experiment, have you inserted the "Force150" jumper on
the back of the hard drive ? Some hard drives have a 1x4 set of
pins, and two of those pins are the "Force150" function,
for slowing down the cable communications rate. If there was a problem
with the cable (pinched, bent, cut), maybe the cable might work
a bit better at 150MB/sec.
(As an example of jumper info, look for "Force 150" in this document.)
(Not all brands of drives have jumpers. For example, Hitachi does not.
On Hitachi, you use the Drive Feature Tool, to set the cable speed
electronically. See page 22. Naturally, you need a SATA2 motherboard,
to use this tool. Which is not nearly as convenient as using a jumper.)
http://www.hitachigst.com/hdd/support/downloads/FTool_User_Guide_215.pdf
Paul
Rajah!
>
> (Not all brands of drives have jumpers. For example, Hitachi does not.
> On Hitachi, you use the Drive Feature Tool, to set the cable speed
> electronically. See page 22. Naturally, you need a SATA2 motherboard,
> to use this tool. Which is not nearly as convenient as using a jumper.)
>
> http://www.hitachigst.com/hdd/support/downloads/FTool_User_Guide_215.pdf
>
> Paul
I downloaded (from ASUS) as well as tried to install the driver from
the ASUS Setup CD, but the program would not install it. I get the
message:
Error
No JMicron JMB36X SCSI adapter found! Setup program will terminate!
F:\My Documents\Downloads\JMicronJMB363_RAID_V117150_makedisk_xpvista
\RAID\Driver\amd64
There is the setting in BIOS - My BIOS is up to date [1701], and shows
the JMicron RAID Controller, which setting (the folks at ASUS say
should be on IDE) is now AHCI has no different results.
Paul
>
> I downloaded (from ASUS) as well as tried to install the driver from
> the ASUS Setup CD, but the program would not install it. I get the
> message:
>
> Error
> No JMicron JMB36X SCSI adapter found! Setup program will terminate!
>
> F:\My Documents\Downloads\JMicronJMB363_RAID_V117150_makedisk_xpvista
> \RAID\Driver\amd64
>
> There is the setting in BIOS - My BIOS is up to date [1701], and shows
> the JMicron RAID Controller, which setting (the folks at ASUS say
> should be on IDE) is now AHCI has no different results.
Asus has their download. This would be similar in design to what you've got.
http://dlcdnet.asus.com/pub/ASUS/mb/socketAM2/M2N-SLI%20Deluxe/RAID_V11610.zip
The Jmicron download is very similar in structure.
ftp://driver.jmicron.com.tw/jmb36x/XP_Vista_Win7/JMB36X_WinDrv_R1.17.53_WHQL_eSATA.zip
In either of those, I look in the "jraid_i.inf" file, for matching plug and play info.
%PCI\VEN_197B&DEV_2363
If you download Everest, run it, and check "Devices : PCI Devices", you should
look for evidence the Jmicron chip is present. The "Device ID" field, to match
the example I extracted from the "jraid_i.inf" file, should be "197B-2363".
That is how I'd check the hardware was active. This old version of Everest,
may not be able to name the Jmicron chip, but you can still use the
Device ID field for info.
"EVEREST Free Edition 2.20 "
http://majorgeeks.com/download4181.html
The BIOS setting should be set to "AHCI", as that may assist with supporting
hot-plug for ESATA. Usually, it is the same driver that gets installed
for either AHCI or RAID, but AHCI should be sufficient to do the job.
Sometimes on a motherboard, changing settings like this, changes how the
device reports itself in Windows.
JMicron SATAII Controller [AHCI]
If you've already tried all that, I don't know what else to do. Check
Device Manager, for signs of a problem, an error code or the like,
and maybe that info can be used to figure out what the problem is.
You can also look for "setupapi.log" on your C: partition. At the end
of the file, you may see log entries for the attempts to install the
latest hardware.
Paul
andy
<rjtm...@gmail.com> wrote:
>Hi
>
>Got an M2N-SLI Deluxe, running WinXPP SP3, 32 bit. Bought a Kingwin
>EZD-2535 external HD dock, with USB and eSATA cable connection
>options. USB works fine, nothing with eSATA.
I have an EZD-2535W connected to a JMB363 eSATA controller on a
Gigabyte EP45-UD3R motherboard.
>
>Does anyone with an M2N-SLI Deluxe mobo have an eSATA based HD dock?
>If so, what brand & model?
>
>Both ASUS and Kingwin replaced their hardware trying to resolve the
>problem. Both were extremely reasonable on the exchanges. I'm pretty
>sure that this specific HD dock just will not work with this
>particular mobo through the eSATA port - so I'm looking for one that
>will.
>
>Note - drives work fine when connected internally via internal SATA
>port & power supply.
Is this with the SATA_RAID1 connector? Otherwise, you would be on the
nVidia SATA controller, which is independent of the JMicron
controller.
In the Bios, set the JMicron SATAII Controller to AHCI, and under
Windows XP, execute Setup.exe in folder
JMicronJMB363_RAID_V11764.zip\Raid\Jmb363.
Rajah!
> On Tue, 26 Jan 2010 15:04:02 -0800 (PST), "Rajah!"
>
> >Hi
>
> >Got an M2N-SLI Deluxe, running WinXPP SP3, 32 bit. Bought a Kingwin
> >EZD-2535 external HD dock, with USB and eSATA cable connection
> >options. USB works fine, nothing with eSATA.
>
> I have an EZD-2535W connected to a JMB363 eSATA controller on a
> Gigabyte EP45-UD3R motherboard.
Glad to hear of an EZD working thru eSATA. I think the M2N-SLI Deluxe
is incompatible with my EZD. So, I'm searching for a dock that does
work thru eSATA on an M2N-SLI Deluxe.
>
>
>
> >Does anyone with an M2N-SLI Deluxe mobo have an eSATA based HD dock?
> >If so, what brand & model?
>
> >Both ASUS and Kingwin replaced their hardware trying to resolve the
> >problem. Both were extremely reasonable on the exchanges. I'm pretty
> >sure that this specific HD dock just will not work with this
> >particular mobo through the eSATA port - so I'm looking for one that
> >will.
>
> >Note - drives work fine when connected internally via internal SATA
> >port & power supply.
>
> Is this with the SATA_RAID1 connector? Otherwise, you would be on the
> nVidia SATA controller, which is independent of the JMicron
> controller.
No, thru one of the standard SATA connectors (there are a group of
them SATA0, SATA1, ...).
>
> In the Bios, set the JMicron SATAII Controller to AHCI, and under
> Windows XP, execute Setup.exe in folder
> JMicronJMB363_RAID_V11764.zip\Raid\Jmb363.
I've tried changing that setting to AHCI, IDE but it made no
difference - even shutting the PC down, powering up the dock first,
and then booting to WinXPP.
Also, I've run that setup - but it fails (I mentioned it somewhere
above):
Error!
andy
You should be able to install the JMicron SATA driver without having
anything connected to the JMicron JMB363 SATA connectors, so the
problem you're experiencing right now has nothing to do with the
docking device.
Rob
"Rajah!" <rjtm...@gmail.com> wrote in message
news:710e33aa-4cf8-4f29...@r19g2000yqb.googlegroups.com...
Double-check that the JMicron controller is enabled in the BIOS,
then go to Device Manager and check it is visible there (with no
drivers, it should be flagged with a red 'X'. If it isn't visible there,
I would suspect a hardware failure on the motherboard.
If it is visible, try using 'Update Drivers' and choose the option which
says 'Have disk', then browse to the folder where you have previously
extracted the relevant drivers to.
HTH,
--
Rob
Rajah!
ports that connect to SATA ports on the motherboard. My EZ Dock is
now connected via the eSATA port.
Still don't know where to look for the JMicron controller in Device
Manager. The setting for JMicron RAID Controller is in the BIOS and
set to AHCI. But trying to load the drivers fails, with the following
error:
andy
The reason you're getting this error is because the JMicron SATA
interface isn't showing up in device manager. Does the Asus bios show
a list of PCI devices during Post, and if so, is the JMicron
controller listed?
Paul
As I suggested in my previous post, download Everest (the utility that
lists hardware). Look in the Devices:PCI Devices section, for an
entry %PCI\VEN_197B&DEV_2363. The free version of Everest, being
rather old now, may not be able to name the device in its displayed
information. But you should see some unnamed device, with 197B and
2363 as its Vendor and Device Numbers. In Everest, you would
look for "197B-2363" in the right hand pane, while looking at the
list of PCI devices and clicking them one by one for details.
If 197B-2363 doesn't show up, then that hardware device is dead or
disabled. If it is showing some other set of numbers (i.e. you have
an unidentified device, and you check its numbers), then it could be
defective. Also, it is possible Jmicron could change the part number,
as a function of the mode the device operates in. Some other hardware
works that way. I don't think the JMB363 has to do that, so don't
think that is a possibility. In any case, look for 197B-???? and
see if there are any Jmicron devices of unknown nature in the list.
You can also look in the setupapi.log file on your C: partition
(where the OS lives), and examine it for instances of VEN_197B&DEV_2363,
to see if it ever worked or was properly installed at some previous date.
Paul
Rajah!
> > No JMicron JMB36X SCSI adapter found! Setup program will terminate!
> As I suggested in my previous post, download Everest (the utility that
> lists hardware). Look in the Devices:PCI Devices section, for an
> entry %PCI\VEN_197B&DEV_2363. The free version of Everest, being
> rather old now, may not be able to name the device in its displayed
> information. But you should see some unnamed device, with 197B and
> 2363 as its Vendor and Device Numbers. In Everest, you would
> look for "197B-2363" in the right hand pane, while looking at the
> list of PCI devices and clicking them one by one for details.
>
> If 197B-2363 doesn't show up, then that hardware device is dead or
> disabled. If it is showing some other set of numbers (i.e. you have
> an unidentified device, and you check its numbers), then it could be
> defective. Also, it is possible Jmicron could change the part number,
> as a function of the mode the device operates in. Some other hardware
> works that way. I don't think the JMB363 has to do that, so don't
> think that is a possibility. In any case, look for 197B-???? and
> see if there are any Jmicron devices of unknown nature in the list.
>
> You can also look in the setupapi.log file on your C: partition
> (where the OS lives), and examine it for instances of VEN_197B&DEV_2363,
> to see if it ever worked or was properly installed at some previous date.
>
> Paul
Hi
I checked the setupapi.log file - no mention of JMicron or the string
you mentioned above.
Everest Ultimate has a free 30 day trial. There was no mention of
JMicron or the device you listed. Nor of 197B, either - I created a
text report from Everest and searched it.
This morning the eSATA-connected drive did not show up. But I checked
my cables, and one was loose. When I fully seated it, the drive
showed up immediately.
Paul
Is this your motherboard ?
http://images17.newegg.com/is/image/newegg/13-131-013-S03?$S640W$
The JMB363 is just below the rightmost PCI Express x1 slot on the
motherboard. It should be showing up on the bus, and should be
visible in Everest. At least, as long as it is enabled in the BIOS.
If the ESATA drive is showing up immediately, something has to interface to
it. From the picture, my guess is, the six red SATA connectors are connected
to the Nvidia chip. The black SATA next to the JMB363 is connected
to the JMB363. And the ESATA on the I/O plate area on the back
of the computer, is also connected to the JMB363.
So it should be there, or at least the VEN and DEV should be showing
up for that device. You can also check in Device Manager for the
chip if you want.
There has to be an explanation hiding in there somewhere :-)
Paul
Rajah!
Hi Paul,
Yes, that's the beast. Nice little AM2 board with dual Gigabit LAN
ports - though I haven't come up with a good purpose for the unused
one yet. Yes, I am familiar with the SATA RAID port which I kinda
figured is controlled by the JMicron hardware/software.
I need to ask - specifically - where/what section in Device Manager
should the chip show itself? I've looked, even under System Devices,
but nothing that mentions RAID, eSATA, or JMicron to be found.
I'd be happy to email you the Everest report - perhaps you could find
something there?
R.
Paul
>
> Hi Paul,
>
> Yes, that's the beast. Nice little AM2 board with dual Gigabit LAN
> ports - though I haven't come up with a good purpose for the unused
> one yet. Yes, I am familiar with the SATA RAID port which I kinda
> figured is controlled by the JMicron hardware/software.
>
> I need to ask - specifically - where/what section in Device Manager
> should the chip show itself? I've looked, even under System Devices,
> but nothing that mentions RAID, eSATA, or JMicron to be found.
>
> I'd be happy to email you the Everest report - perhaps you could find
> something there?
>
> R.
>
Have you looked in the various storage sections of Device Manager ?
In this example, look under "IDE ATA/ATAPI controllers" to see if
something like "pciide.sys" got installed to control the Jmicron.
Look under SCSI and RAID controllers, because I suspect that is where
the Jmicron would go, if the driver was installed properly. And
in the example here, something called "Mass Storage Controller" showed
up. Since no driver is installed for "Mass Storage Controller", it remains
unnamed. The claim is, this picture is from an M2N-SLI Deluxe system.
http://attachments.techguy.org/attachments/149562d1239984098/device_mngr.jpg
In WinXP Device Manager, if you do "Properties" on an entry, then
use the "Details" tab, then look for "Device Instance" or "Hardware Ids"
in the list, you may get VEN and DEV numbers for a device that way.
Try looking for the Jmicron numbers, on one of your existing storage
device entries. There are a number of places to hide storage devices,
which is why you'll have to look carefully through the list.
If your ESATA did not work, there was no Jmicron or "unknown" entry in
Device Manager, the Jmicron was enabled in the BIOS, you might conclude
the chip was broken. Since you claim to have a working ESATA drive, that
means the Jmicron must be in Device Manager somewhere, with some driver
installed. If a proper Jmicron driver is not installed, then perhaps
some other "generic" driver, like pciide.sys or the like, is installed
instead.
I had hoped the "setupapi.log" file on your C: drive would have helped.
If Jmicron hardware is enabled in the BIOS, there should be at least
one line in the setupapi.log corresponding to it. Look for 197B and 2363
in there.
You say the ESATA drive works ? And that it is plugged into the ESATA
connector in the I/O plate area ? You aren't, perhaps, using a SATA to
ESATA cable with PCI slot plate, to connect to a Southbridge SATA port
instead ? Maybe that would account for why the drive is working.
Paul
Rajah!
> Rajah! wrote:
>
> > Hi Paul,
>
> > Yes, that's the beast. Nice little AM2 board with dual Gigabit LAN
> > ports - though I haven't come up with a good purpose for the unused
> > one yet. Yes, I am familiar with the SATA RAID port which I kinda
> > figured is controlled by the JMicron hardware/software.
>
> > I need to ask - specifically - where/what section in Device Manager
> > should the chip show itself? I've looked, even under System Devices,
> > but nothing that mentions RAID, eSATA, or JMicron to be found.
>
> > I'd be happy to email you the Everest report - perhaps you could find
> > something there?
>
> > R.
>
> Have you looked in the various storage sections of Device Manager ?
> In this example, look under "IDE ATA/ATAPI controllers" to see if
> something like "pciide.sys" got installed to control the Jmicron.
> Look under SCSI and RAID controllers, because I suspect that is where
> the Jmicron would go, if the driver was installed properly. And
> in the example here, something called "Mass Storage Controller" showed
> up. Since no driver is installed for "Mass Storage Controller", it remains
> unnamed. The claim is, this picture is from an M2N-SLI Deluxe system.
>
>
> In WinXP Device Manager, if you do "Properties" on an entry, then
> use the "Details" tab, then look for "Device Instance" or "Hardware Ids"
> in the list, you may get VEN and DEV numbers for a device that way.
> Try looking for the Jmicron numbers, on one of your existing storage
> device entries. There are a number of places to hide storage devices,
> which is why you'll have to look carefully through the list.
>
> If your ESATA did not work, there was no Jmicron or "unknown" entry in
> Device Manager, the Jmicron was enabled in the BIOS, you might conclude
> the chip was broken. Since you claim to have a working ESATA drive, that
> means the Jmicron must be in Device Manager somewhere, with some driver
> installed. If a proper Jmicron driver is not installed, then perhaps
> some other "generic" driver, like pciide.sys or the like, is installed
> instead.
>
> I had hoped the "setupapi.log" file on your C: drive would have helped.
> If Jmicron hardware is enabled in the BIOS, there should be at least
> one line in the setupapi.log corresponding to it. Look for 197B and 2363
> in there.
>
> You say the ESATA drive works ? And that it is plugged into the ESATA
> connector in the I/O plate area ? You aren't, perhaps, using a SATA to
> ESATA cable with PCI slot plate, to connect to a Southbridge SATA port
> instead ? Maybe that would account for why the drive is working.
>
> Paul
Sorry, I might not have made it clear: Rolled a $9 dice bet and
bought a expansion slot card with two eSATA
ports that connect to SATA ports on the motherboard. My EZ Dock is
now connected via the (dock's) eSATA port. I am *not* using the
eSATA port that is hardwired to the motherboard.
Neither 197B nor 2363 is in setupapi.log.
According to ASUS, they tested the onboard eSATA port the two
replacement motherboards before shipping them to me.
Still can't find any mention of JMicron in Everest log or Device
Manager.
R.