8KNXP 1.x Hard drive config

Bob,

Just found what may be the right files on the INtel site

Contains the four files you mentioned, all dated July 3rd 2003 - do they
sound right to you?

Cheers

--
Neil Atwood
Sydney, Australia


"Bob Davis" wrote in message
news:ZyZue.51064$iU.6992@lakeread05...

"NeilA" wrote in message
u...
"Bob Davis" wrote in message
news:65Kue.50925$iU.17037@lakeread05...

"NeilA" wrote in message
u...

Hey Bob,

Just tried your instructions...

On-Chip SATA: Manual
SATA Port0 Configure as: SATA Port0
SATA Port1 Configure as: SATA Port1
SATA RAID function: Enabled

And saw a confiuration screen flash by, then the XP splash screen,
then... a BSOD! ;-)

An unexpected, revolting development. What did the BSOD say? It must
be reacting adversely to the new hardware that has no driver, but in my
case it booted into XP without a hitch and asked for drivers. Keep in
mind that I still had XP on a PATA drive at the time, with nothing
connected to the SATA controller. It may be that you'll need to boot up
with a PATA like I did, then do the above.

Come to think of it, you are enabling the 82801ER with a drive attached
to it before it has drivers, so that is probably the problem. Thus
you're asking it to run the drive without drivers. Attach the PATA you
ghosted as C: (also change the boot order), then boot into XP with
nothing attached to the SATA controller with settings as above. At that
point XP should see the new hardware, install the drivers, and you can
then shut it down and swap the drives. That would be the procedure I
used that worked.

Also, what bios version are you running? When I did this I was fairly
up-to-date on the bios at the time, on either f10 or f11, now on f13a.



Yeah - but it's but I was concerned would happen because my boot drive is
a SATA drive... ;-)

So I will image to a PATA drive and do as you suggest...
BIOS is due to be updated to F13a - I have the file, just need to do it.
Any known problems with the F13a code?

Thanks again, and will keep you posted...

I'm confident Plan B will work as it did for me.

I've had f13a on this system since January without any issues and haven't
heard anything negative about it. I had f10 before that and wasn't having
trouble with it either, but the description of f13a mentioned a problem
with f12 and installing XP using RAID, which sounded like it might apply
to me even though I was running f10. I figured after two months that if
there were problems with it Gigabyte would've pulled it, and it's still
there today as a "beta." I think you could say that it has been tested
enough to pull the "beta" label.

Hey Bob,

Third message, and counting!

Just ran into another strange problem with this board... (Did I mention this
was a replacement board for one that died under warranty?)

Went to flash the BIOS with F13, and checked the current version. It says
it's 'FB' - which I can find no reference to anywhere on the Gigabyte web
site.
An attempt to flash it anyway with F13 gives me a 'BIOS ID check error' and
aborts the flash.
Tried two other earlier BIOS versions - same error.

Ever come across that?

Cheers

--
Neil Atwood
Sydney, Australia


"Bob Davis" wrote in message
news:ZyZue.51064$iU.6992@lakeread05...

"NeilA" wrote in message
u...
"Bob Davis" wrote in message
news:65Kue.50925$iU.17037@lakeread05...

"NeilA" wrote in message
u...

Hey Bob,

Just tried your instructions...

On-Chip SATA: Manual
SATA Port0 Configure as: SATA Port0
SATA Port1 Configure as: SATA Port1
SATA RAID function: Enabled

And saw a confiuration screen flash by, then the XP splash screen,
then... a BSOD! ;-)

An unexpected, revolting development. What did the BSOD say? It must
be reacting adversely to the new hardware that has no driver, but in my
case it booted into XP without a hitch and asked for drivers. Keep in
mind that I still had XP on a PATA drive at the time, with nothing
connected to the SATA controller. It may be that you'll need to boot up
with a PATA like I did, then do the above.

Come to think of it, you are enabling the 82801ER with a drive attached
to it before it has drivers, so that is probably the problem. Thus
you're asking it to run the drive without drivers. Attach the PATA you
ghosted as C: (also change the boot order), then boot into XP with
nothing attached to the SATA controller with settings as above. At that
point XP should see the new hardware, install the drivers, and you can
then shut it down and swap the drives. That would be the procedure I
used that worked.

Also, what bios version are you running? When I did this I was fairly
up-to-date on the bios at the time, on either f10 or f11, now on f13a.



Yeah - but it's but I was concerned would happen because my boot drive is
a SATA drive... ;-)

So I will image to a PATA drive and do as you suggest...
BIOS is due to be updated to F13a - I have the file, just need to do it.
Any known problems with the F13a code?

Thanks again, and will keep you posted...

I'm confident Plan B will work as it did for me.

I've had f13a on this system since January without any issues and haven't
heard anything negative about it. I had f10 before that and wasn't having
trouble with it either, but the description of f13a mentioned a problem
with f12 and installing XP using RAID, which sounded like it might apply
to me even though I was running f10. I figured after two months that if
there were problems with it Gigabyte would've pulled it, and it's still
there today as a "beta." I think you could say that it has been tested
enough to pull the "beta" label.

Worked out the BIOS issue..

The board identifies itself as a Rev 1.x board, whereas in reality, it's a
Rev 2.

So I now have the latest BIOS version flashed... onto the SATA driver
issues... ;-)

--
Neil Atwood
Sydney, Australia


"NeilA" wrote in message
u...
Hey Bob,

Third message, and counting!

Just ran into another strange problem with this board... (Did I mention
this was a replacement board for one that died under warranty?)

Went to flash the BIOS with F13, and checked the current version. It says
it's 'FB' - which I can find no reference to anywhere on the Gigabyte web
site.
An attempt to flash it anyway with F13 gives me a 'BIOS ID check error'
and aborts the flash.
Tried two other earlier BIOS versions - same error.

Ever come across that?

Cheers

--
Neil Atwood
Sydney, Australia


"Bob Davis" wrote in message
news:ZyZue.51064$iU.6992@lakeread05...

"NeilA" wrote in message
u...
"Bob Davis" wrote in message
news:65Kue.50925$iU.17037@lakeread05...

"NeilA" wrote in message
u...

Hey Bob,

Just tried your instructions...

On-Chip SATA: Manual
SATA Port0 Configure as: SATA Port0
SATA Port1 Configure as: SATA Port1
SATA RAID function: Enabled

And saw a confiuration screen flash by, then the XP splash screen,
then... a BSOD! ;-)

An unexpected, revolting development. What did the BSOD say? It must
be reacting adversely to the new hardware that has no driver, but in my
case it booted into XP without a hitch and asked for drivers. Keep in
mind that I still had XP on a PATA drive at the time, with nothing
connected to the SATA controller. It may be that you'll need to boot
up with a PATA like I did, then do the above.

Come to think of it, you are enabling the 82801ER with a drive attached
to it before it has drivers, so that is probably the problem. Thus
you're asking it to run the drive without drivers. Attach the PATA you
ghosted as C: (also change the boot order), then boot into XP with
nothing attached to the SATA controller with settings as above. At
that point XP should see the new hardware, install the drivers, and you
can then shut it down and swap the drives. That would be the procedure
I used that worked.

Also, what bios version are you running? When I did this I was fairly
up-to-date on the bios at the time, on either f10 or f11, now on f13a.



Yeah - but it's but I was concerned would happen because my boot drive
is a SATA drive... ;-)

So I will image to a PATA drive and do as you suggest...
BIOS is due to be updated to F13a - I have the file, just need to do it.
Any known problems with the F13a code?

Thanks again, and will keep you posted...

I'm confident Plan B will work as it did for me.

I've had f13a on this system since January without any issues and haven't
heard anything negative about it. I had f10 before that and wasn't
having trouble with it either, but the description of f13a mentioned a
problem with f12 and installing XP using RAID, which sounded like it
might apply to me even though I was running f10. I figured after two
months that if there were problems with it Gigabyte would've pulled it,
and it's still there today as a "beta." I think you could say that it
has been tested enough to pull the "beta" label.

Ok Bob, - all solved and done.

For any others, here's a summary of what I did:

Original situation:

Drives:

On on-board SATA (82801ER Controller)
1 x 80GB SATA (boot)
1 x 160Gb SATA

2 x Optical drives (on secondary IDE channel)
1 x PATA HDD (on primary IDE channel)

Problem: SATA drives were being remapped to the primary IDE channel, locking
out the use of the PATA drive.


Solution:

Ghost (well, True Image, actually) Boot drive to spare PATA disk
Set SATA drives to SATA-0 and SATA-1 RAID enabled
Change boot order to PATA cloned disk
Boot system
Install 82801 drivers for RAID controller when Windows asks
Ghost PATA boot drive back to SATA-0 (original boot disk)
Change boot order in BIOS to SATA-0
Boot from SATA-0 disk

All done!

Speed on SATA drives is well up now, using the proper SATA drivers, and I
have access to the extra PATA drive on the IDE channel.

Thanks heaps Bob for your good advise...

Cheers

--
Neil Atwood
Sydney, Australia


"Bob Davis" wrote in message
news:0Bhue.50819$iU.16050@lakeread05...

"NeilA" wrote in message
...

I have an 8KNXP Rev 1 board, and am having trouble setting up my desired
combination of drives.
I don't use RAID.

I have:
1 x 80Gb SATA drive (boot drive)
1 x 40Gb PATA drive (used for data backup)
2 x optical drives (CD-RW & DVD-RW)

And I've just added:
1 x 160Gb SATA drive (data)

I have the two SATA drive plugged into the first of the two SATA
controllers, which remaps the two SATA drives as Primary PATA master and
slave.
But doing this locks out the 40Gb PATA drive, which is plugged into the
primary IDE channel.
The two optical drives are on the secondary PATA channel.

Is there a way to have both SATA drives AND the PATA 40Gb drive
available?

The whole SATA/RAID config in the BIOS is very confusing!


Follow these steps, and hopefully I haven't forgotten anything. You'll
need
to enable and install the 82801ER (ICH5R) SATA RAID controller.

1. Back up everything as a precaution.

2. Go to the Gigabyte or Intel site and download the IAA (82801ER)
drivers.
Put the four driver files (IASTOR.SYS, IASTOR.INF, IASTOR.CAT,
TXSETUP.OEM)
on a floppy disk.

3. Reboot, enter bios and change the following items:
On-Chip SATA: Manual
SATA Port0 Configure as: SATA Port0
SATA Port1 Configure as: SATA Port1
SATA RAID function: Enabled

Keep in mind that the "On-board SATA" is the Sil3112 controller, which
isn't what you're trying to enable.

4. XP will find the new hardware (82801ER SATA RAID controller) and will
prompt for drivers. Point to the floppy and let them install.

5. Reboot, enter bios and make sure your Hard Disk Boot Priority is set
properly (mine reads "Intel RAID_Volume1" with a RAID0 array), then let it
boot into XP. You should then be in business.

Caveat: I used this procedure on the same mobo and it worked perfectly,
but
I started with my OS on a PATA drive, and enabled the SATA RAID controller
before installing a SATA drive. I installed the SATA drive after Step 4,
and between Step 4 and 5 I cloned the PATA to SATA with Norton Ghost.
Later
on (months later) I moved to RAID0 and that transition was also a piece of
cake.

This procedure should work as well, but please make sure you're backed up!

I believe the drives will stay mapped to the IDE controller until Step 5,
at
which time the 82801ER will be installed and the drives will be picked up
on
that controller, freeing the IDE controllers for IDE drives.

Please let us know if you run into any glitches.

"NeilA" wrote in message
u...
Ok Bob, - all solved and done.

For any others, here's a summary of what I did:

Original situation:

Drives:

On on-board SATA (82801ER Controller)
1 x 80GB SATA (boot)
1 x 160Gb SATA

2 x Optical drives (on secondary IDE channel)
1 x PATA HDD (on primary IDE channel)

Problem: SATA drives were being remapped to the primary IDE channel,
locking out the use of the PATA drive.


Solution:

Ghost (well, True Image, actually) Boot drive to spare PATA disk
Set SATA drives to SATA-0 and SATA-1 RAID enabled
Change boot order to PATA cloned disk
Boot system
Install 82801 drivers for RAID controller when Windows asks
Ghost PATA boot drive back to SATA-0 (original boot disk)
Change boot order in BIOS to SATA-0
Boot from SATA-0 disk

All done!

Speed on SATA drives is well up now, using the proper SATA drivers, and I
have access to the extra PATA drive on the IDE channel.

Thanks heaps Bob for your good advise...

Great! Sorry for being out of pocket when you needed help in the last day
or so. Yes, you apparently have a rev. 2 board, which I think has a label
or stencil on the corner of the board nearest PCI5. That won't matter for
all this HD rigmarole, though, since the only difference between the two
boards is the sound controller, and the bios, of course.

I've been running SATA RAID0 (36gb x 2 Raptors) on the ICH5R for almost 10
months now without a burp, and 25 months now on this rev. 1 board (knock on
wood) with very stable results. Can't brag on it enough, and hope it stays
this way.

"Bob Davis" wrote in message
news:HFoxe.52792$iU.42648@lakeread05...

That won't matter for
all this HD rigmarole, though, since the only difference between the two
boards is the sound controller, and the bios, of course.

Can you give details on this difference?

"Craig Sutton" wrote in message
...

"Bob Davis" wrote in message
news:HFoxe.52792$iU.42648@lakeread05...

That won't matter for
all this HD rigmarole, though, since the only difference between the two
boards is the sound controller, and the bios, of course.

Can you give details on this difference?

Had to Google for this one, as I was aware only of the sound change:

1. The Realtek audio codec in a rev. 2 board is an ALC658. Original board
used a ALC655 II.

2. The SYS_FAN header for revision 2 was moved from the bottom of the board
to
the front near SATA0_SB.

3. The board revision number location has moved from near the middle by the
GA-8KNXP logo to the bottom near the IR_CIR header.