No subject

<snip>
Real Time Clock Driver v1.09
RAM disk driver initialized:  16 RAM disks of 4096K size
PIIX: IDE controller on PCI bus 00 dev 38
PIIX: not 100% native mode: will probe irqs later
PIIX: neither IDE port enabled (BIOS)
PIIX: IDE controller on PCI bus 00 dev 39
PIIX: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hda: QUANTUM FIREBALL ST6.4A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: QUANTUM FIREBALL ST6.4A, 6149MB w/81kB Cache, CHS=784/255/63
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
md driver 0.90.0 MAX_MD_DEVS=256, MAX_REAL=12
raid5: measuring checksumming speed
   8regs     :   198.882 MB/sec
   32regs    :   136.779 MB/sec
using fastest function: 8regs (198.882 MB/sec)
scsi : 0 hosts.
scsi : detected total.
md.c: sizeof(mdp_super_t) = 4096
Partition check:
 hda: hda1 hda2 < hda5 hda6 >
RAMDISK: Compressed image found at block 0
autodetecting RAID arrays
autorun ...
... autorun DONE.
</snip>

(The entire dmesg output can be made available upon request.)

Has anyone seen this before?  I haven't got an extra motherboard or 
controller card to test the on-board controller.

I also seem to remember reading about a Linux utility that enables the 
user to change BIOS settings, but can't remember what it is.  Any 
suggestions?

Thanks in advance for your help.  I'd really appreciate it if I could 
get my backups going again.

Cheers,
BB

PS: I noted this post as OT because I'm convinced that it's a hardware 
issue, not a Linux issue.  The hardware just happens to run Linux.

Brian Barber
Ottawa, ON   CANADA
brian.barber at mysun.com