[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

bf2.4 3.0.22-2002-04-03 RAID on IDE controller HighPoint 372 hpt37x2



Hi.


I tried to install woody using the bf2.4-images 3.0.22-2002-04-03
on this machine:
athlon xp, 512MByte on a Shuttle AK35GTR (BIOS AK35H00F, includes
latest HighPoint-BIOS) with an UDMA133-controller HighPoint372
(it's AFAIK not the 372A); this EIDE-controller is also used on the
Shuttle AK35GTR2, the Abit KR7A-RAID and the Abit KX7-333R. the
HighPoint chip is often referred to as hpt372 or hpt37x2 or simply
hpt.
on each hpt-channel I put a WesternDigital600AB configured as RAID0
via the hpt-BIOS. one DVD-drive is attached to the VIA-controller. I
know, that it's probably preferable not to use this pseudo-RAID-
option and that there are better software solutions (and of course
much better hardware solutions) out there but let me give it a try.

FreeBSD4.5 got the first 16GBytes of the RAID; therefore I used the
precompiled driver from
  http://www.highpoint-tech.com/372drivers_down.htm
and it works fine, though the driver using SCSI-emulation is surly
far from optimum.

bootstrapping from the floppies the following messages appear:

boot:
Loading linux.bin..................... ready
Linux version 2.4.18-bf2.4 (root@zombie) (gcc version 2.95.4 20011002 (Debian
prerelease)) #1 Sam Mär 30 00:56:06 CET 2002
.
.
.
Kernel command line: vga=normal noinitrd load_ramdisk=1 prompt_ramdisk=1
ramdisk_size=16384 root=/dev/fd0 disksize=1.44 flavor=bf2.4 BOOT_IMAGE=linux.bin
.
.
.
Checking 'hlt' instruction... OK.
Checking for popad bug... OK.
POSIX conformance testing by UNIFIX
mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au)
mtrr: detected mtrr type: Intel
PCI: PCI BIOS revision 2.10 entry at 0xfb450, last bus=1
PCI: Using configuration type 1
PCI: Probing PCI hardware
Unknown bridge resource 0: aussuming transparent
PCI: Using IRQ router default [1106/3099] at 00:00.0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
VFS: Diskquotas version dquot_6.4.0 initialized
Journalled Block Device driver loaded
vga16fb: mapped to 0xc00a0000
Console: switching to colour frame buffer device 80x30
fb0: VGA16 VGA frame buffer device
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
Real Time Clock Driver v1.10e
block: 128 slots per queue, batch=32
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
?jfà?uC??S?fà?u:ïF,?=??: IDE controller on PCI bus 00 dev 78
?jfà?uC??S?fà?u:ïF,?=??: chipset revision 5
?jfà?uC??S?fà?u:ïF,?=??: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0xd400-0xd407, BIOS settings: hde:DMA, hdf:pio
    ide3: BM-DMA at 0xd408-0xd40f, BIOS settings: hdg:DMA, hdh:pio
VP_IDE: IDE controller on PCI bus 00 dev 89
PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using pci=biosirq.
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt8233 (rev 00) IDE UDMA100 controller on pci00:11.1
    ide0: BM-DMA at 0xdc00-0xdc07, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdg:pio, hdh:pio
hda: TOSHIBA DVD-ROM SD-M1612, ATAPI CD/DVD-ROM drive
hde: WDC WD600AB-60CBA0, ATA DISK drive
hdg: WDC WD600AB-00BVA0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide2 at 0xc400-0xc407,0xc802 on irq 5
ide3 at 0xcc00-0xcc07,0xd002 on irq 5
hde: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63, UDMA(100)
hdg: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63, UDMA(100)
hda: ATAPI 48x DVD-ROM drive, 512kB Cache
Uniform CD-ROM driver Revision: 3.12
ide-floppy driver 0.97.sv
Partition check:
 hde: [PTBL] [7297/255/63] hde1
 hdg: unknown partition table
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
Loading I2O Core - (c) Copyright 1999 Red Hat Software
I2O configuration manager v 0.04.
  (C) Copyright 1999 Red Hat Software
loop: loaded (max 8 devices)
Compaq CISS Driver (v 2.4.5)
HDLC support module revision 1.02 for Linux 2.4
Cronyx Ltd, Synchronious PPP and CISCO HDLC (c) 1994
Linux port (c) 1998 Building Number Three Ltd & Jan "Yenya" Kasprzak.
ide-floppy driver 0.97.sv
 ataraid/d0: ataraid/d0p1
Highpoint HPT370 Softwareraid driver for linux version 0.01
Drive 0 is 57241 Mb
Drive 1 is 57241 Mb
Raid array consists of 2 drives.
SCSI subsystem driver Revision: 1.00
Read Hat/Adaptec aacraid driver, Mar 30 2002
DC390: 0 adapters found
3ware Storage Controller device driver for Linux v1.02.00.016.
3w-xxxx: No cards with valid units found.
request_module[scsi_hostadapter]: Root fs not mounted
request_module[scsi_hostadapter]: Root fs not mounted
i2c_scsi.c: Version 0.0.1
  chain_pool: 0 bytes @ c1857440
  (512 byte buffers X 4 can_queue X 0 i2o controllers)
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP, IGMP
IP: routing cache hash table of 4096 buckets, 32Kbytes
TCP: Hash tables configured (established 32768 bind 32768)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Insert root floppy disk to be loaded into RAM disk and press ENTER
VFS: Disk change detected on device fd(2,0)
RAMDISK: compressed image found at block 0
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 260 k freed
usb.c: registered new driver usbdevfs
.
.
.
cdrom: open failed.
VFS: Disk change detected on device ide0(3,0)

and then the installation system starts.
this surprised me a little bit, because many people reported kernel-
panics when attempting to get the hpt372 working with the hpt370-
linux-driver. anyway, these messages don't look comfortable.

I googled for hpt372-linux-support and this is what I found:

HighPoint offers GPL'd drivers which use AFAIK SCSI-emulation
:-(  :
  http://www.highpoint-tech.com/372drivers_down.htm
I don't want to use them.
Jack Kolesar manually patched ide-pci.c and mentions the AlanCox-
kernel:
  http://www.amdpower.com/sections.php4?op=viewarticle&artid=71
this file should do the same:
  http://www.timj.co.uk/linux/kernel-hpt372.patch
Andy Jeffries asking Alan Cox for help in getting the patch into
the official kernel:
  http://www.uwsg.iu.edu/hypermail/linux/kernel/0203.0/0649.html
ok, these infos should give us hpt372-support. the latest chip by
HighPoint is AFAIK the hpt374; I think that implementing support
for this one wouldn't be a big effort, so I suggest to add it, too.

now, making the RAID work:
Arjan van de Ven from Redhat and others work on really good
drivers:
  http://people.redhat.com/arjanv/pdcraid/
these dmesg-lines indicate the use of Ven's sources, at least I
think so:
...
ide-floppy driver 0.97.sv
 ataraid/d0: ataraid/d0p1
Highpoint HPT370 Softwareraid driver for linux version 0.01
Drive 0 is 57241 Mb
Drive 1 is 57241 Mb
Raid array consists of 2 drives.
...
I don't know if displaying 'HPT370' should make me worry. but hey,
/dev/ataraid/d0 is available!
I prefer Ven's driver over the use of /dev/md0, etc. as described
on
  http://www.tldp.org/HOWTO/Software-RAID-HOWTO.html  .

on debianhelp.org someone described how he made his RAID work, but
it's not the way I would like to do it:
  http://www.debianhelp.org/modules.php?op=modload&name=News&file=article&sid=808

so my question: could you please add support for the hpt372 to the
floppy-images? or could you tell me where to get info about
building my own floppy-images or at least patching bf2.4?
TIA.

OT: BTW; what does this mean?
PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using pci=biosirq.


ciao
   hog
--
Managers occasionally wore ties, but productivity went down on the
days they did.
           -- The Cuckoo's Egg, Cliff Stoll, 1990
-


--
To UNSUBSCRIBE, email to debian-boot-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: