PCI IDE Controller & Linux kernel
 

I'm thinking about buying this controller
*/HighPoint Rocket133SB

I would like to use it to boot linux form.

Any known problems with this(or a like) Dev?

TIA

Sort of, the chipset is important, also make certain this isn't a PCI 2.2 compliant only card as only the past 8 months or so of mobos are compliant with that standard. The kernel can handle the HPT372 and 374 chipsets, but its a hack to get them as the boot device. Support for em is in 2.5.x, but its a good six or seven months before 2.6.x is out and a distro bases a release of of them.

Check the chipset at Highpoint's page and you can find the method in order to get the chipset to boot right, its RH tailored (of course), but it can work with Slack.

Cheers,

Finegan

Thanks,

The Dev uses a HPT371 chipset.

I took this from the 2.5.59 kernel
*
*HPT366 is an Ultra DMA chipset for ATA-66.
*HPT368 is an Ultra DMA chipset for ATA-66 RAID Based.
*HPT370 is an Ultra DMA chipset for ATA-100.
*HPT372 is an Ultra DMA chipset for ATA-100.
*HPT374 is an Ultra DMA chipset for ATA-100.
*
*This driver adds up to 4 more EIDE devices sharing a single
*interrupt.
*
I assume the HPT371 is like the HPT372 with a single interrupt.
HTP371 is a singel chanel version of the HPT372

I think it will work.

(if it won't work, then I will have someting to do for a while :P )

If you or anybody else had any luck/unluck getting it to work,
please write here... I'm just now trying to make it work on
my 2.4.10-SMP installation, but I *am* struggling a bit...

J.O.

The problem is now somewhat mundane... I cannot manage
to get the HighPoint-driver to compile!

How does one compile a kernel module not native to the kernel-
package?

I don't get rid of a lot of warnings like this:

/usr/include/linux/version.h:2: #error "======================================================="
/usr/include/linux/version.h:3: #error "You should not include /usr/include/{linux,asm}/ header"
/usr/include/linux/version.h:4: #error "files directly for the compilation of kernel modules."
/usr/include/linux/version.h:5: #error ""
/usr/include/linux/version.h:6: #error "glibc now uses kernel header files from a well-defined"
/usr/include/linux/version.h:7: #error "working kernel version (as recommended by Linus Torvalds)"
/usr/include/linux/version.h:8: #error "These files are glibc internal and may not match the"
/usr/include/linux/version.h:9: #error "currently running kernel. They should only be"
/usr/include/linux/version.h:10: #error "included via other system header files - user space"
/usr/include/linux/version.h:11: #error "programs should not directly include <linux/*.h> or"
/usr/include/linux/version.h:12: #error "<asm/*.h> as well."
/usr/include

whatever I try... The hints in the error msg are not helpful at
all, since my
/lib/modules/`... is not a link to some source directory,
but rather a directory containing the compiled modules
themselves...

*sigh*.

Ahh... Sweet music... I just commented out the #ifdef _KERNEL_
in /usr/include/linux.h, and voila, it worked... insmod hpt371
immediately recognized the new Maxtor 200 GB disk also...
Now, let's just hope this little "hack" doesn't screw up everything
later on... :-)

I think you will find it works nicely now :)

But if you still have troubles with the dev, you might want to try the 2.5.x kernel.
Or just wait for 2.6.

Good luck,

Yes, thanks, it seems to work fine. (After about 24 hours of
relatively heavy load...) Someone told me that in 2.4.21-pre-
something (I'm running 2.4.10) there are open source
drivers. (These are probably the ones you have in mind
wrt. 2.5.x) I will perhaps upgrade when I can verify that all my
other essential software will work with other kernels...