HighPoint 372 on AbitBD7RAID and RH7.2/7.3
 

Was trying to install 7.3/7.2 on BD7RAID with raid enabled. I was installing using guidance from HighPoint.
After installation and reboot I'm getting this one:

Booting 'Red Hat Linux(2.4.7-10)'
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /vmlinuz-2.4.7-10 ro root = /dev/sda8 hda=ide-scsi
Error 15: File not found
Press any key to continue...

The part "hda=ide-scsi" looks supicious... but what it should be?That was the option offered by RedHat.

In case anyone has an experience or desire to help then help please.
Thnx

Last Step
 

Did you perform the last step where you replace the kernel?

I have ABIT KT7 RAID and installed RH7.2 with no problem at all following Highpoints instructions. But I just posted that I can't get it to work with 7.3. After running postinstall I get a message "unary operator expected". Then when I try to boot I get a similar message to yours.

Well.. I believe that we are in the same boat

Got a link to the Highpoint instruction page? I'm not running RH, but I've got this controller on a Slack 8.1 box so I might be able to fiddle with a workaround.

Cheers,

Finegan

The instructions are included in the driver download its a pdf file called Install_RedHat_HPT37x2.

I would put it on my server with a link to it, but I CAN"T GET MY SERVER BACK UP!!

http://www.highpoint-tech.com/370drivers_down.htm

Alright, I have to check which HPT BIOS I'm running when I get home. Its not available in "dmesg" or "lspci", so according to Highpoint, I've got to get it to at least v2.1, and since its a motherboard controller, that means snarfling the driver from Abit if I need it.

I downloaded and followed the readme in the source tarball, except that I didn't remove support for the hpt370 from the kernel as I don't have that as a module, its built into my slackware scsi.i kernel. I could recompile the kernel, re-run lilo, change the default, and reboot the machine from here at work... but I'de rather just try this later at home. Now according to my dmesg, the module I created from the source tarball, with nothing more than a simple "make", bound to the card. The readme.txt explains that this is probably no good as I already have the hpt366/370 registering the thing as an IDE device. So, from what I can tell... ditch the stinky RPMs, compile it from source, make sure you have scsi emulation already in your kernel (like mine), or insmod it, and follow the source tarball's readme.

For VotTak, you can just compile this from source without having to worry about a conflict with the kernel driver as there isn't a kernel driver for the 372 in 2.4.18 or 2.4.7 (depending on which RedHat you have on there.)

Cheers guys,

Finegan

I'm now booting from the harddisk after struggling with the file not found problem while booting with grub from the harddisk.
The problem is that in the /grub/grub.conf the vmlinuz was linked to /boot/vmlinuz.2.4.18-3
and you must remember that during bootup /boot is an apart file system.

follow the sequence I've cut and pasted from the terminal

[root@localhost boot]# pwd
/boot
[root@localhost boot]# cat grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Red Hat Linux (2.4.18-3)
root (hd0,0)
# changed this entry to a file instead of a link
# because during booting /boot is /
kernel /vmlinuz.hpt37x2 ro root=/dev/sda2
#kernel /vmlinuz-2.4.18-3 ro root=/dev/sda2
initrd /initrd-2.4.18-3.img
[root@localhost boot]# ls -l
total 5966
-rw-r--r-- 1 root root 5824 Jun 25 2001 boot.b
-rwxr-xr-x 1 root root 203 Aug 7 23:47 boot.msg
-rw-r--r-- 1 root root 612 Jun 25 2001 chain.b
-rw-r--r-- 1 root root 39809 Apr 18 13:53 config-2.4.18-3
drwxr-xr-x 2 root root 1024 Aug 8 22:24 grub
-rw-r--r-- 1 root root 224850 Aug 7 22:14 initrd-2.4.18-3.img
-rwxr-xr-x 1 root root 239077 Aug 7 23:47 initrd.img
-rw-r--r-- 1 root root 479 Aug 7 21:15 kernel.h
-r-xr-xr-x 1 root root 6192 Aug 7 23:48 ldlinux.sys
drwx------ 2 root root 12288 Aug 7 22:03 lost+found
-rw-r--r-- 1 root root 23108 Jun 25 2001 message
lrwxrwxrwx 1 root root 20 Aug 7 22:07 module-info -> module-info-2.4.18-3
-rw-r--r-- 1 root root 14431 Apr 18 13:53 module-info-2.4.18-3
-rw-r--r-- 1 root root 640 Jun 25 2001 os2_d.b
lrwxrwxrwx 1 root root 19 Aug 7 22:07 System.map -> System.map-2.4.18-3
-rw-r--r-- 1 root root 478261 Apr 18 13:53 System.map-2.4.18-3
-rwxr-xr-x 1 root root 2917643 Apr 18 13:53 vmlinux-2.4.18-3
lrwxrwxrwx 1 root root 16 Aug 7 22:07 vmlinuz -> vmlinuz-2.4.18-3
lrwxrwxrwx 1 root root 21 Aug 7 22:39 vmlinuz-2.4.18-3 -> /boot/vmlinuz.hpt37x2
-rw-r--r-- 1 root root 1052336 Apr 18 13:53 vmlinuz-2.4.18-3.old
-rwxr-xr-x 1 root root 1052188 Aug 7 22:37 vmlinuz.hpt37x2
[root@localhost boot]#

-----------------------
I hope that for you people out there that this can be an eyeopener

Regards Hans van Hal

Thank you j.hal for your post.

Could you perhaps explain in simpler terms your instructions a little for me?

I'm new to linux, and am encountering the same problem/error as VoTak. I'm trying to install RH7.3 on my Abit KR7A-133R motherboard with integrated HPT372 controller. Thank you.

Hello Mudd

Oke I will try to tell you what is happenning.

When you installed redhat according to the instructions found in the HPT installation notes you have to make some floppy's with drivers and kernels.
This kernel has disabled the normal access to the ide disk interface and we need that kernel to get to the raid interface.
The copy instuctions, the ones that do the mounting of the floppy,
are copying that kernel to the proper place, this is on the /boot partition.

Most likely there is also installed a boot manager (named grub).
This boot manager is able to give us a choice in what kind of kernel or operating system we boot. During installation you were offered a choice of either grub or lilo (another boot manager).

When the computer starts up it mount the boot partition and grub (or) lilo start working to load the kernel that we need to load
i.e. vmlinuz.hpt.37x2

Grub reads it instructions from a file called /boot/grub/grub.conf
if you look in this grub.conf you will see that it wants to load a file by the name of vmlinuz or something like vmlinuz.2.4.18-3.
Now we look in /boot with the command ls -l /boot and we see several entries of which the first letter is an l .

This l means that it is a link to another name and if you look closer
that linkname is pointing to another name and that one has a /boot to start with

Now we must remember that at the time of booting there is no such partition as boot because it is mounted as /

Therefore the system cannot find the kernel image it needs in order to boot from, hence you see the message that it cannot find the file.

Now I renamed the entry in /boot/grub/grub.conf to vmlinuz.hpt37x2 and the boot loader (grub) was able to find it
and did normally boot up

By the way, if you cannot come to your harddisk, you can boot from the floppy that was created,(in the normal redhat installation) but that must als contain the vmlinuz.hpt37x2 kernel
So copy that kernel over the kernel that is originally on the floppy

I hope that it is clear now and that over time you come to love linux

regards Hans van Hal

RedHat 7.3 + HighPoint HPT 370 RAID 0 : kernel issue
 

I got a follow-up question.
The board: Soyo SY-6BA+100 board with on-board HighPoint HPT 370 .

What I did:
1. Got a beta BIOS upgrade from Soyo tech support - version 1.2.0612.
2. Followed instructions from HighPoint site (referenced earlier in this thread) and installed RedHat 7.3 on RAID 0 with not a glitch.
3. Tweaked the grub (as suggested earlier in the thread) - replaced vmlinuz-2.4.18-3 with vmlinuz.hpt37x2 in /boot/grub/grub.conf.

Result:
Everything boots wonderfully.

What I did further:
Updated the kernel to 2.4.18-10 - using RedHat up2date utility to access their "RedHat Network".

Result:
New kernel does not want to boot (the old one still boots with no problemo).

Question: Que pasa?

RedHat 7.3 + HighPoint HPT 370 RAID 0 : kernel issue
 

I got a follow-up question.
The board: Soyo SY-6BA+100 board with on-board HighPoint HPT 370 .

What I did:
1. Got a beta BIOS from Soyo tech support - version 1.2.0612.
2. Followed instructions from HighPoint site (referenced earlier in this thread) and installed RedHat 7.3 on RAID 0 with not a glitch.
3. Tweaked the grub (as suggested earlier in the thread) - replaced vmlinuz-2.4.18-3 with vmlinuz.hpt37x2 in /boot/grub/grub.conf.

Result:
Everything boots wonderfully.

What I did further:
Updated the kernel to 2.4.18-10 - using RedHat up2date utility to access their "RedHat Network".

Result:
New kernel does not want to boot (the old one still boots with no problemo).

Question: Que pasa?

The kernel you installed, vmlinuz.hpt37x2 had support for your RAID card, the updated kernel from RedHat does not. Most likely there won't be support for the HPT372 in a default RedHat kernel until they release 8.0. RedHat, when releasing these updates, keeps sending out a new compile of the exact same kernel, so if there wasn't support in 2.4.18 stock, they're not going to add it with a new compile.

Cheers,

Finegan

And the solution to this problem is...??

Stick with the old kernel, or compile your own updated kernel, replacing the source for that little part of the kernel source with the one from Highpoint (there's instructions on the HPT page). Until the patched driver for the HPT372+4 makes it into the stock kernel, RedHat isn't going to produce an RPM for you that supports it.

The solution is that the problem is, "how do I upgrade my kernel through RPM and keep support for my board?" Simply, you can't.

Cheers,

Finegan

Kernel Panic
 

OK, I'm back to try installing this on my machine, now that I see Highpoint has put out a new driver version.

But I am still getting the boot problem

I get a Kernel panic.

I tried changing the kernel to vmlinuz.hpt37x2 on the grub loader, but it still won't boot.

Kernel panic, init not found - something to that effect.

The only thing I might be see as a problem is that I don't have the most up to date BIOS. I believe I have 2.31 and the HP zip has 2.32.

Is that the problem?

You have an Abit KT7 RAID?, VIA KT133 chipset? I Just checked the closet for my manual instead of cracking my case but I've got the same board...

Unless they got funky with the cheese whiz right at the end of the series, that thing has a HPT 370, not a 372. If so, support for that card has been in the kernel since... 2.4.10 I think, and everyone compiles support in by default. I could send you a .config that would boot for that machine. The BIOS was an issue if you ever wanted to get it to work in hardware RAID, in which case yeah update to yesterday's, but to just get the ATA100 to work should just be a matter of changing fstab, swapping the drives up, and rebooting.

If your kernel panic failed at init, it either couldn't find the drives, or really couldn't find the drive it was pointed to by LILO or Grub. Hmm...

Cheers,

Finegan

Ok I'm trying to install using 2 RAID 0 drives

Here is my GRUB loader :

root (hd0,0)
kernel /vmlinuz-2.4.18-3 ro root=sda2 hda=ide-scsi
initrd /initrd-2.4.18-3.img

When I change the kernel to vmlinuz.hpt37x2 I get this error

kernel panic: No init found. Try passing init= option to kernel.

Any ideas?

This same setup work without RAID, with Red Hat install from CD's

HPT and Raid 1
 

I have been trying to figure out whether or not I can use the HPT RAID controller with a RAID 1 under linux. As far as I can tell, I can only find support for RAID 0. (I'm running debian.)

Thanks,
greenkiwi

1) about the highpoint 372 and redhat 8 or mandrake 9

I prepared these:

http://www.terra.es/personal2/capullator/


____________________


2) about the hpt37x2.o ... if you modify hpt37x2lib.o with an hex editor changin the strings:

"gcc2_compiled" -> "gcc3_compiled"
"CC: (GNU) 2.96" -> "GCC: (GNU) 3.2 " (note the space)

you can use the precompiled highpoint "opensource" (note the quotes) with a gcc3 compilied kernel!!!

Sharky, your links seem to be dead. I'm guessing they are links to boot kernels with instructions?

This headache with the HPT 37x controllers is probably going to be knocked out by 2.4.20 and the distros released on that, but for the time inbetween this would be really helpful.

Cheers,

Finegan

Yep, ... terra my ISP delete my personal files!!! (wtf)

Whell the files are up again, ...



About the 2.4.20 , ... its posible but, ... I coud't install redhat 8 using the kernel 2.4.19-ac4 drivers because the redhat 8 installer dont try the /dev/ataraid/* devices :(. Thats why the boot floppies made to install rh8 use the shit hpt drivers)

(sorry by my poor english)

Yep, ... They hava:
- a detailed readme
- the modified files to "compile the kernel yourself" :P
- the rh8 tgz contain the "hpt37x2lib.o" tricked to be used with a "gcc3 compiled kernel"
- a raw image to the boot floopies
- a precompiled kernel (and initrd with the driver inside) for athlon ready to use once the install finish.

I downloaded and read through the Mandy install version. I wouldn't worry so much about your english, they were very good directions.

Want a US mirror?

Cheers,

Finegan

You can make a mirror or modify my files without any problem :)

If you do these thx. (I will add the links a.s.a.p.)

Aight, here they are on http, I'm cagey about opening up an anonymous ftp.

http://www.clockwatching.net/~fin/ra...at8_hpt372.tgz
http://www.clockwatching.net/~fin/ra...ke9_hpt372.tgz

Cheers,

Finegan

Hello Sharky and Finigan

Today I tried to update a Redhat 7.3 system with the modified bootdisk
but it failed completely.

I downloaded your install_redhat8_hpt372.tgz and unpacked it
and made the bootfloppy from the instructions as:
dd if=install_bootdisk.img of=/dev/fd0

when loading the /bin/insmod /modules/hpt37x2.o driver, this system
comes back with a warning message:
Warning: loading /modules/hpt37x2.o will taint the kernel: no license

When I came in the graphical interface to the choice of either installing
or upgrading I clicked on the upgrading (because I have a running 7.3 system)
The system comes back with the message:
You don't have any Linux Partitions. You can't upgrade this system.

I then went back and choose : Install on system | Desktop

... automatically partition and the system comes back with
an Error has occurred - No Valid devices wher found on which to create
new filesystems. Please check your hardware for the cause of this problem.

when I push the OK button the system reboots.

Do you know what has been going wrong?

Anyway It is clear that the installation kernel has not yet any support for the hpt37x2 conroller.

Regards

Hans van Hal

thats normal.

Do de insmod before the instaler enters the graphical mode.
Run this as soon as you can enter the 2nd virtual terminal.

(Or modify the initrd renaming the linuxrc to linuxrc_ and create an script that to de insmod and then call the linuxrc_).

The problem is that the rh installer detects de hardisk configuration as soon as it enter the gralphical mode.

Probably when the 2.4.20 kernel the new disitributions will have full hpt372 support.

RedHat 7.3 + HighPoint HPT 370 RAID 0 : kernel issue
 

What about putting in 8.0 since it's just become available? Anyone has a HPT370 and a successful install of RAID 0 or 1 on RH 8.0?

Re: RedHat 7.3 + HighPoint HPT 370 RAID 0 : kernel issue
 

The hpt370 and hpt372 can use the same driver probided by highpoint, ... just have a try with my .tgz ;)

Sharky and all,

If you go to term 2 before you say no to the driver question, the raid is recognized by the graphical installer.

Great job!!!!!


Thanks


Ray Dias

RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue
 

OK, so im my situation - I already have a working RedHat 7.3 istalled successfully on HPT370 RAID 0 and with vmlinuz.hpy37x2 in /boot/grub/grub.conf - I can't really boot from the boot disk provided on your link, can I? I would like to keep current kernel - at least for now - until I know I can boot from the new RedHat 8.0.

Also, mine is an Intel box, so recompiling kernel is "not optional". How do I do that with an existing 7.3? And how am I going to make use of the driver provided by you during compiling the kernel?
Regards.

Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue
 

Humm you have never compiled or upgreded the kernel since the 7.3 install?

I think that it sould boot correctly with your configuration. Did you tried it?


I have never upgrade redhat. When i install a new S.O. i whant it clean.
By this reason y have a separate /home partition :)

So, ... I don't know how RedHat upgrade works (probably upgrading the old kernels will be deleted, ... ... ... or not)

A posible solution is save the /modules/* and /boot/* in a CDR

Realy you can compile that kernel yourself but you need gcc3 to make it 100% compatible with the old one overwriting only 1 or 2 files.


To make the kernel to the rh8 install the rpm of this kernel and the kernel-source of this version.

copy the /boot/config-THEKERNELVERSIONYOUNEED to the kernel's source directory.

Modify the makefile and change the version ;P (or insmod will not work)

Edit the drivers/ide/ide-pci.c and drop these lines:

{DEVID_HPT34X, "HPT34X", FIXUP_HPT34X, PCI_HPT34X, NULL, INIT_HPT34X, NULL, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, NEVER_BOARD, 16 },
{DEVID_HPT366, "HPT366", FIXUP_HPT366, PCI_HPT366, ATA66_HPT366, INIT_HPT366, DMA_HPT366, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 240 },
{DEVID_HPT372, "HPT372A", NULL, PCI_HPT366, ATA66_HPT366, INIT_HPT366, DMA_HPT366, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 0 },
{DEVID_HPT302, "HPT302", NULL, PCI_HPT366, ATA66_HPT366, INIT_HPT366, DMA_HPT366, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 0 },
{DEVID_HPT371, "HPT371", NULL, PCI_HPT366, ATA66_HPT366, INIT_HPT366, DMA_HPT366, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 0 },
{DEVID_HPT374, "HPT374", FIXUP_HPT374, PCI_HPT366, ATA66_HPT366, INIT_HPT366, DMA_HPT366, {{0x00,0x00,0x00}, {0x00,0x00,0x00}}, OFF_BOARD, 0 },


(in some kernels only the 2 lines if the begining)

go to the kenel source dir. and do a "make xconfig" (or similar ;) ) and disable (under "ATA/IDE/MFM/RLL" -> "IDE,ATA and ATAPI Block devices"):

"Highpoint 370 software RAID" (CONFIG_BLK_DEV_ATARAID_HPT)
"HPT34X chipset support" (CONFIG_BLK_DEV_HPT34X)
"HPT34X AUTODMA support (WIP)" (CONFIG_HPT34X_AUTODMA)
"HPT366 chipset support" (CONFIG_BLK_DEV_HPT366)

Save the changes, ... do a "make dep" and a "make" ... if you wanna test that ... "make modules , "make install"

Remember you need to recompile the hpt37x2 module before do a "make install" in the tgz of rh8 i included an hpt37x2lib.o with some modifications to allow use the resulting hpt37x2.o module with a gcc3 compiled kernel.

So, ... untar the oficial hpt "openshit" (really not opensource) driver overwrite the hpt37x2lib.o with the modified one and do a "make KERNELDIR=/usr/src/YOURKERNELSOUERCE"

Now you need to modify the initrd of the new kernel to do some insmods in the initrd...

mount it and edit "linuxrc" after the last insmod add these 3 insmods:

insmod /lib/scsi_mod.o
insmod /lib/sd_mod.o
insmod /lib/hpt37x2.o

and copy theselibraries from your recently compiled kernel/driver to the initrd's /lib

unmount the initrd run lilo and ... try this.

and, ... other posibility is:

download the oficial kernel and the -ac4 patch

... (patch the kernel)

compile it with the config file of the previous post :) ( in the redhat cd the kernel package)
install it, ...


1 consideration: you will NOT boot from /dev/sda ... you will boot from /dev/ataraid/d0 or /dev/ataraid/disc0/disc

you probably will need to make the nodes in the initrd and in yor "/" doing this:

cd /dev
mkdir ataraid
mkdir disc0
cd disc0
mknod disc b 114 0
mknod part1 b 114 1
mknod part2 b 114 2
mknod part3 b 114 3
mknod part4 b 114 4
mknod part5 b 114 5
mknod part6 b 114 6

or


cd /dev
mkdir ataraid
mknod d0 b 114 0
mknod d0p1 b 114 1
mknod d0p2 b 114 2
mknod d0p3 b 114 3
mknod d0p4 b 114 4
mknod d0p5 b 114 5
mknod d0p6 b 114 6

Thats all, ...

I am trying to install rh on an exsisting raid 0 array with 3 partitions. One contains windows xp. On my abit-kr7a 133r MB. When I use highpoints boot and driver disk i get an error

Ib: stdin :i/o error or -2147483630 reading error no such file or directory.

Can anyone interpret this error, and reccommend a solution?

I just tried it again, and hit ctl+alt+ f3 and f4 and I notice it says a bunch of i/o errors for the Floppy disk. Ive tried two different drives and two different cables. all the same thing

Try with a better floppy. Bad media?

Wich redhat are you installing?

sorry shoulda said prior to.. I am installing RH 7.3
I have tried several different disks.
It will actually start to load the driver then, i get that message in the background and it continues the install. But still does not find the array

Highpoint suggest to upgrade the bios to make it work under linux, ... did you do this?

did you do the CD-ROM media test?

I just reflashed my MB bios. so it is the newest.

When I use the boot disk provided by Highpoint it doesnt ask me to do a media check. I downloaded your bootdisk, when yours does a media check it says there is a checksum error.. The disks I have are the retail disks bought in the store. It lets me continue regardless of the checksum error, but then it says the second part of the install doesnt match the bootdisk or something like that. Then it reboots..

Hmm

Any ideas?

My boot disks works with redhat 8 / mandrake 9 only

If you are using the highpoint redhat 7.3 disks write mediacheck in the boot time (you can obtain more info pressing the function keys)

I am a newbie.. I dont know what "write mediacheck in boot time means"

Insert the boot disk, ...
Turn off your computer, ...
Turn on your computer, ...

Your floopy led will blink 1 time and some text information will be displayed on your screen, ...

At this moment you must write "linux mediacheck" (without quotes) and press enter, ...

The installer will ask you about the 3 CDs to check if they are ok.

Ok, tell ya what.. I feel kinda stupid.. But I was finally able to get a driver disk to work.. What I was doing was quick formatting the disks, but when I did a full format on the disk and install the drivers It finally worked. This is the first time Ive been able to see my raid array in linux.
Right now, i am making room on a partition of my HD. then I will go to work, and install it tommorow after school.

I appreciate the help.. And sorry for being so stupid..

Pandimus..

Wants its up and running, i am sure I can come up with more questions regarding hardware and various other stuff.

Re: Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue
 

I think I'll hold off with compiling the RH 8.0 with this driver for now. The more I read it, the more complicated it sounds, and I am not a kernel compilation guru. My RH 7.3 works perfectly with RAID 0 on HP370, so, I guess I'll just wait for RH8.1 or something - hopefully they'll build in support for HP370 by then.

Re: Re: Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue
 

As i said in this thread you don't need to recompile the kernel, ... you can use the precompiled one included in my gziped tar file, ... just read the readme file included inside,... i think that this can be realy easy,...

I posted a reply recently about the new kernel 2.4.20, ...
I mailed alan cox to ask him about the update of the hpt driver inside the kernel, ... he said that the kernel will not be updated until 2.4.21 :(

The native support of our raid using the oficial kernel will be far :(

Re: Re: Re: Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue
 

Sorry, I was away busy with other things for about a month, so I lost track of what's where. I can't find the link to the gzipped tar file. And I remember you mentioned that all this would only work for an AMD machine and I have an Intel on this box. So I would still need to compile, don't I?
Anyway, so basically my action plan should be (please confirm):
1. Unzip/untar the kenel file.
2. Move teh resulting file to /???/???
3. Run make?
4. At what point the HP driver comes into the picture?
5. At what point the compilation process is over?
Regards.

Re: Re: Re: Re: Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue + Rex2 :P
 

http://www.terra.es/personal2/capullator/
http://www.clockwatching.net/~fin/ra...at8_hpt372.tgz
(mirror provided by finegan :P)

1) Extract the files inside: install_redhat8_hpt372.tgz you will get a boot disk to install redhat. Check the readme file for further info,...
2) In your case you will need to change ALL the "post install" procedure :P, ... you must compile your own kernel instead of overwriting the original one,...
3) edit your /usr/src/linux/drivers/ide-pci.c and drop the lines:
copy the /boot/config-... to .config inside the kernel source dir.

make menuconfig -> disable de hpt support (inside ata)

compile and install the kernel,...
compile the highpoint driver with the gcc3 cheat,...
mount your initial ramdisk partition and copy your hpt37x2.o inside at /lib
add an "insmod" inside the linuxrc from the initial ramdisk,...
unmount your initial ramdisk,...

Re: Re: Re: Re: Re: Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue + Rex2 :
 

1. Boot from the boot disk you created. Do I really need to boot from it - I already have a RedHat 7.3 running on HighPoint 370 RAID 0 - can't I just boot from it and compile a new kernel with the new driver support, what do you think?
2. Say No to the prompt "Do you have a driver disk"
3. Open another terminal (Alt+F2)
4. Run /bin/insmod /modules/hpt37x2.o. I understand I should build my own driver - make KERNELDIR=/usr/src/linux-2.4.18-14 or can I use yours? Mine is an Intel machine.
5. Get back to the original terminal window?
6. Is this where I should supposedly start compiling the RH 8.0 kernel? It sounds like I should already have a compiled kernel at this point. The HighPoint readme says I should "install" (compile?) my new kernel first, then remove the necessary lines from /usr/src/drivers/ide/ide-pci.c, and then "rebuild" (recompile?) the kernel. Now this part is a bit confusing.
7. Also ,compiling the kernel involves the following:
- cd /mnt/cdrom/RedHat/RPMS
- rpm -i kernel-source-2.4.18-14.i386.rpm. Do I need any other files?
- cd /usr/src/linux
- make xconfig
- insmod - this is where I should take care of this driver?
- make dep
- make clean
What and at which point do I copy to the /boot?

Re: Re: Re: Re: Re: Re: Re: RedHat 8.0 + HighPoint HPT 370 RAID 0 : kernel issue + Re
 

Yep you can,...
The instaler kernel works in an i586, ... no problem here :)
Not needed, ... While you are doing the "/bin/insmod /modules/hpt37x2.o" the installer is detecting your monitor, hd drives, ... (so go as fast as you can), .... and then, ... the graphical mode will popup automatically.
You must compile / change the kernel at the last part of the installation, ... (when it ask for reboot)
(Yep, ... but you can do this inside the installer)
(Remember to modify ide-pci.c here)
No, ... copy your /boot/config-2.4.18-14?????' to /usr/src/linux/.config
- make menuconfig
(disable the hpt* support inside IDE and save the changes)
modify the Makefile (drop "custom" in the kernel version)
No, ... forget the insmod
- make

Here you have an "/usr/src/linux/arch/i386/boot/bzImage"
NOW Copy /usr/src/linux/arch/i386/boot/bzImage to /boot/vmlinuz-2.4?????????

NOW compile the driver and copy htp37x2.o to /lib/modules/2.4????/kernel/drivers/scsi and run (depmod -a)

run
/sbin/mkinitrd -f --preload scsi_mod --preload sd_mod --preload ext3 --preload hpt37x2 --with=hptraid /boot/initrd-2.4????????.img 2.4????????

(note that ???? is not ???? exactly :P)

run lilo if you use lilo and reboot,...

some more hpt37x2 stuff
 

hello,

I read the whole thread and I used some tricks you wrote.
now my RedHat 7.1 runs and allows me to mount my HDD's which are attached to the hpt-controller.

the only problem is that I have to connect my linux-HDD to the mainboards primary (or secondary) ide-interface to boot linux.

I used the manual given by RedHat to compile a new kernel (it's now about 900k)...I hope I did it right (it showed no erros during the compilation) but it didn't work.

my linux partition is the second one on the HDD, the first one is a windows-partition with about 18gig...so Linux gets the last 2.1gig of the HDD.
that's why I have to use Loadlin to boot up Linux or I use a boot-disc.
but I prefer to boot with Loadlin.

so my question is: can I load the needed hpt-module with Loadlin so that Linux boots from the proper recognized HDD attached to the hpt-controller ?

hope anyone can help me out...cause I hate it to plug and unplug the HDD everytime I want to use Linux.

Thanks,
Mercenary