RE: booting from Promise tx2000

2003-02-24 Thread Len Conrad

I might be wrong here.. but I think you need some specific raid drivers for
the TX cards to work
the tx2000 is seen as an standard ATA interface. no driver needed

Len

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


Re: booting from Promise tx2000

2003-02-24 Thread Len Conrad

If your BIOS supports this, try setting the boot device in CMOS
configuration to SCSI Boot Device.
it does, and that's how we have it.

 The problem is that the offboard ATA
controller you are using has its own BIOS, thus the system BIOS will not
boot a disk attatched to it.
I don't think so, the system BIOS scans the i/o address space for 
executable segements and passes control to any that it finds, giving the 
disk controller card a chance to run its own code, hook interrupts, etc.

 Setting SCSI boot device will mostly make your
BIOS offer to hand booting over to what ever device offers to take it. Most
(modern) ATA controllers respond to the call for a SCSI boot device and
take controle, then booting the system from the hard drives they own.
agreed, but it's not happening.  We've played a lot with the System bios 
settings and with the tx2000 bios setup utility, which sees the drives 
correctly.

Len

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


booting from Promise tx2000: FIXED

2003-02-24 Thread Len Conrad
Since we only had one ATA133 disk on each TX2000 ATA channel, we skipped 
the TX2000 setup utility to define an array (we didn't want to run RAID 
or want any stinking arrays at all).

We were able to boot from mobo ATA CDROM and install fbsd through the TX2000.

( btw, we always install fbsd boot mgr, since without the boot mgr, we more 
often than not, cannot get any boot at all )

But, no boot from TX2000 fbsd disk. Nothing, no errors, from TX200, nothing 
from fbsd bootblock.

When we did define an array as span, but only had one disk per ATA 
channel in the span, we were finally able to get a boot but with a failure :

Mounting Root from ufs:/dev/ad4s1a
Root Mount Failed: 16
We figured the fbsd install pre-array/span wasn't accessible after we did 
defined array/span.

So with the array mode + span now on, we re-installed fbsd via the TX2000 
to the same disk.  And now, we can boot just fine.

 while waiting for Soeren Schmidt to get the Promise SX4000 driver done!

:))

Len 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


booting from Promise tx2000

2003-02-23 Thread Len Conrad
fbsd 4.7 release

no drives on motherboard ata channels

one ATA Master drive on each TX2000 IDE channel  (no Array is defined, we 
just want two independent disks for now)

fbsd cdrom boots, finds the disks and installs fbsd.

we choose boot manager because we typically have our system fail to boot 
without boot manager (fbsd 3 and 4 has has this pb) so we always install 
boot mgr and live with the additional timeout.

booting never gets to fbsd boot mgr menu.

we´ve disabled a bunch mobo i/o devics we don't need and can see no PCI IRQ 
conflicts.

any ideas?

Len

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


Re: booting from Promise tx2000

2003-02-23 Thread Willie Viljoen
On Monday 24 February 2003 2:52, someone, possibly Len Conrad, typed:
 fbsd 4.7 release

 no drives on motherboard ata channels

 one ATA Master drive on each TX2000 IDE channel  (no Array is defined, we
 just want two independent disks for now)

 fbsd cdrom boots, finds the disks and installs fbsd.

 we choose boot manager because we typically have our system fail to boot
 without boot manager (fbsd 3 and 4 has has this pb) so we always install
 boot mgr and live with the additional timeout.

 booting never gets to fbsd boot mgr menu.

 we´ve disabled a bunch mobo i/o devics we don't need and can see no PCI
 IRQ conflicts.

 any ideas?

If your BIOS supports this, try setting the boot device in CMOS 
configuration to SCSI Boot Device. The problem is that the offboard ATA 
controller you are using has its own BIOS, thus the system BIOS will not 
boot a disk attatched to it. Setting SCSI boot device will mostly make your 
BIOS offer to hand booting over to what ever device offers to take it. Most 
(modern) ATA controllers respond to the call for a SCSI boot device and 
take controle, then booting the system from the hard drives they own.

Will

-- 
Willie Viljoen
Freelance IT Consultant

214 Paul Kruger Avenue, Universitas
Bloemfontein
9321
South Africa

+27 51 522 15 60
+27 51 522 44 36 (after hours)
+27 82 404 03 27 (mobile)

[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message