Hi everybody! I'm a SuSE 7.0 user, I've just donwloaded new drivers for my HPT370 RAID controller intended for SuSE 7.1; these are provided only in precompiled modules for kernels 2.2.18 and 2.4.0-4GB. So I need to download the 2.4.0-4GB kernel but I can't find it on SuSE ftp site (lx_sus24.rpm in 7.1 directory provides kernel 2.4.2). Please, help me! -- Emilio Federici emilio.federici@libero.it ICQ:27013758
On Fri, 24 Aug 2001, Emilio wrote:
Hi everybody! I'm a SuSE 7.0 user, I've just donwloaded new drivers for my HPT370 RAID controller intended for SuSE 7.1; these are provided only in precompiled modules for kernels 2.2.18 and 2.4.0-4GB. So I need to download the 2.4.0-4GB kernel but I can't find it on SuSE ftp site (lx_sus24.rpm in 7.1 directory provides kernel 2.4.2).
*sigh* binary modules are a huge pain in the ass for all involved. Especially when they're built against known buggy kernels. Complain to Highpoint, and ask for a newer set of modules. regards, Dave. -- | Dave Jones. http://www.suse.de/~davej | SuSE Labs
Dave Jones wrote:
*sigh* binary modules are a huge pain in the ass for all involved. Especially when they're built against known buggy kernels. Complain to Highpoint, and ask for a newer set of modules.
regards,
Dave.
I wrote to them two times, but I haven't received a single word as answer :-(. New drivers? It took them one year and a half to develop a driver supporting RAID (this one) I'm not very confident in their capabilities! Bye! Emilio -- Emilio Federici emilio.federici@libero.it ICQ:27013758
On Fri, 24 Aug 2001, Emilio wrote:
*sigh* binary modules are a huge pain in the ass for all involved. Especially when they're built against known buggy kernels. Complain to Highpoint, and ask for a newer set of modules.
*shrug*. Vendors have to get their heads around the fact that binary modules are a *bad* idea. Since 2.4.0, there have been _dozens_ of fixes to various filesystems, the block layer, the IDE & SCSI layers, many of which were made as it was possible to cause data corruption. Given Highpoints lack of clue over this fact alone, I wouldn't trust my data to a company who blatantly disregards these issues. Thankfully Andre Hedrick has stood his ground and not allowed us to get into a position where we need binary drivers just to get the drives to talk. I own a highpoint controller myself, and use software RAID0 on it. It performs very well, giving me between 40-50MB/s transfer rates. I doubt tbh that the binary drivers would improve on this. Leaving just two things for Highpoint to have over the open driver. Support for RAID sets created with the BIOS. (Not that big a deal unless your RAID set contains a FAT volume that you dual boot into Windows with). (And theres a reverse engineered solution to this in Alan Cox's tree). (Not sure if Hubert has merged this with the SuSE kernel yet) And the other feature they have is a graphical setup tool. To which I answer: vim /etc/raidtab It really isn't difficult to set up at all. regards, Dave. -- | Dave Jones. http://www.suse.de/~davej | SuSE Labs
Having a Abit BE6-II,rev 2.0 and also having tried many versions of their drivers in Winblows, and then try endless combinations of Andre Hedriks patch to get the silly thing working in Linux I can also say that I'm not that confident that Highpoint will upgrade the Linux very soon. One never know and we might get a pleasant surprise (though I'm not holding my breath). Then again the guys at Highpoint seem pretty clueless at times - at least where Linux is concerned. *Shrugs and sighs* Curtis On Thursday 23 August 2001 07:33 pm, Dave Jones wrote:
On Fri, 24 Aug 2001, Emilio wrote:
*sigh* binary modules are a huge pain in the ass for all involved. Especially when they're built against known buggy kernels. Complain to Highpoint, and ask for a newer set of modules.
*shrug*. Vendors have to get their heads around the fact that binary modules are a *bad* idea. Since 2.4.0, there have been _dozens_ of fixes to various filesystems, the block layer, the IDE & SCSI layers, many of which were made as it was possible to cause data corruption.
Given Highpoints lack of clue over this fact alone, I wouldn't trust my data to a company who blatantly disregards these issues.
Thankfully Andre Hedrick has stood his ground and not allowed us to get into a position where we need binary drivers just to get the drives to talk.
I own a highpoint controller myself, and use software RAID0 on it. It performs very well, giving me between 40-50MB/s transfer rates. I doubt tbh that the binary drivers would improve on this.
Leaving just two things for Highpoint to have over the open driver. Support for RAID sets created with the BIOS. (Not that big a deal unless your RAID set contains a FAT volume that you dual boot into Windows with). (And theres a reverse engineered solution to this in Alan Cox's tree). (Not sure if Hubert has merged this with the SuSE kernel yet)
And the other feature they have is a graphical setup tool. To which I answer: vim /etc/raidtab It really isn't difficult to set up at all.
regards,
Dave.
One option, that usually works (but may not. Excercize caution) is to use insmod -f This will work (hopefully) if you have a module built for 2.4.0 and want to load it in a 2.4.2 kernel. regards Anders On Friday 24 August 2001 02:00, Emilio wrote:
Hi everybody! I'm a SuSE 7.0 user, I've just donwloaded new drivers for my HPT370 RAID controller intended for SuSE 7.1; these are provided only in precompiled modules for kernels 2.2.18 and 2.4.0-4GB. So I need to download the 2.4.0-4GB kernel but I can't find it on SuSE ftp site (lx_sus24.rpm in 7.1 directory provides kernel 2.4.2).
Please, help me!
On Fri, 24 Aug 2001, Anders Johansson wrote:
One option, that usually works (but may not. Excercize caution) is to use insmod -f
This will work (hopefully) if you have a module built for 2.4.0 and want to load it in a 2.4.2 kernel.
And pray to $DEITY that no big changes were made to any structure/code in the IDE/Block layer during this gap. Russian roulette with disk data doesn't sound like my idea of fun :) regards, Dave. -- | Dave Jones. http://www.suse.de/~davej | SuSE Labs
Very true, which was why I mentioned the caution bit. Anyway, you should never use a new thing directly on a production machine, and any changes that can cause corruption (a seg fault straight away is more likely, in my experience), will show up in the test phase. regards Anders On Friday 24 August 2001 02:36, Dave Jones wrote:
On Fri, 24 Aug 2001, Anders Johansson wrote:
One option, that usually works (but may not. Excercize caution) is to use insmod -f
This will work (hopefully) if you have a module built for 2.4.0 and want to load it in a 2.4.2 kernel.
And pray to $DEITY that no big changes were made to any structure/code in the IDE/Block layer during this gap.
Russian roulette with disk data doesn't sound like my idea of fun :)
regards,
Dave.
Hi I went that road yesturday, and now in boot I get: "could not mount root file system 08:03" or similar... Actually there is few lines up a message: "unable to excecute /sbin/modprobe char-major-8" or similar... Ofcourse it cant excecute modprobe (or was it insmod), because sda3 is not yet mounted.. And in order to mount it, it need to load the module that is in sda3... Does anyone have a solution to that?.. I think I need to start playing around with initrd, perhaps do my own that includes the module? Jaska. Viestissä Perjantai 24. Elokuuta 2001 03:00, Emilio kirjoitti:
Hi everybody! I'm a SuSE 7.0 user, I've just donwloaded new drivers for my HPT370 RAID controller intended for SuSE 7.1; these are provided only in precompiled modules for kernels 2.2.18 and 2.4.0-4GB. So I need to download the 2.4.0-4GB kernel but I can't find it on SuSE ftp site (lx_sus24.rpm in 7.1 directory provides kernel 2.4.2).
Please, help me!
Anders Johansson wrote:
Hi
I went that road yesturday, and now in boot I get:
NOW YOU BOOT?! I'd love to get that far!!! What kernel are you using? About all the others things said on this mailing about my post, I'd like to add that: 1) insmod -f failed 2) Software RAID has been my solution for quite a long time but I'd like to use RAID with Windows too! 3) No one answered my question: "Where in the world can I find kernel 2.4.0-4GB?" Thanks for yor help! -- Emilio Federici emilio.federici@libero.it ICQ:27013758
Anders Johansson wrote:
Hi
I went that road yesturday, and now in boot I get:
NOW YOU BOOT?! I'd love to get that far!!! What kernel are you using?
About all the others things said on this mailing about my post, I'd like to add that:
1) insmod -f failed 2) Software RAID has been my solution for quite a long time but I'd like to use RAID with Windows too! 3) No one answered my question: "Where in the world can I find kernel 2.4.0-4GB?"
Thanks for yor help!
Hi Well, I did download my kernel from ftp.funet.fi, but You can search ftp.kernel.org for a mirror close to you. but I'm not able to compile it !!.. some weird error.. Okay, a short description of the procudre... What I did, is that I downloaded 2.2.18 kernel, and untarred it to /usr/src/linux in /dev/hda3 (normal IDE disk). Then I started the RAID installation with the boot disk that comes from highpoint-tech. When the boot-disk asks for SuSE 7.1 CD1, is calmly put 7.2 there, and it works. I then installed the whole system, so that it came to login-prompt. Now I had new kernel installed, that needed to be replaced... so no booting now! Logged in, and then comes to custom part. I went to /usr/src/, copied the 2.2.18 kernel sources from /dev/hda3. Made a link "/usr/src/linux" to "/usr/src/linux-2.2.18". Then I compiled the kernel 2.2.18, and installed it (just to get all references correctly). I did select all possible modules, because the kernel shall be the one from boot-disk, and not the one I was making, so I don't know what modules it will actually need... Then I copied the kernel from the Highpiont-tech bootdisk to /boot/vmlinux.raid. Then I copied the hpt370.o module for 2.2.18 kernel from the modules disk to /lib/modules/2.2.18/scsi. Then I went to zast-sysadmin-change configuration file, and said "INITRD_MODULES = hpt370". Then quit zast, and in prompt said "mk_initrd". This then builds the /boot/initrd, that is loaded during boot as ramdisk. It will search the module from /lib/modules/<kernel-version>, so that is why it had to be copied there. Then I renamed the new /boot/initrd to /boot/initrd.raid Now I had /boot/vmlinuz.raid from original boot disk and /boot/initrd.raid, that included the hpt370 driver. Then some editing for lilo.conf like this: default = linux boot = /dev/sda disk = /dev/sda bios = 0x80 #vga = extended read-only prompt timeout = 50 image = /boot/vmlinuz.raid initrd = /boot/initrd.raid label = linux root = /dev/sda3 image = /boot/memtest.bin label = memtest86 Then I ran lilo, and it installed nicely. And voila, now I'm running abit-K7 RAID with SuSE 7.2, but with 2.2.18 kernel.. it does not support my nice USB mice.... but one can't always have it all... .( I need to know how to get 2.4.0 compiled, so that I could use that kernel.. it should support my micro-size mitsumi-USB mice... And also I seem to have some problem with my sound too.... Jaska
On Friday 24 August 2001 12:17, Emilio wrote:
Anders Johansson wrote:
No, I didn't! Please be more careful when quoting!
Hi
I went that road yesturday, and now in boot I get:
NOW YOU BOOT?! I'd love to get that far!!! What kernel are you using?
About all the others things said on this mailing about my post, I'd like to add that:
1) insmod -f failed 2) Software RAID has been my solution for quite a long time but I'd like to use RAID with Windows too! 3) No one answered my question: "Where in the world can I find kernel 2.4.0-4GB?"
Thanks for yor help!
Anders
On Friday 24 August 2001 7:41 am, Jaakko Tamminen wrote:
I went that road yesturday, and now in boot I get:
"could not mount root file system 08:03" or similar...
Actually there is few lines up a message: "unable to excecute /sbin/modprobe char-major-8" or similar...
Ofcourse it cant excecute modprobe (or was it insmod), because sda3 is not yet mounted.. And in order to mount it, it need to load the module that is in sda3...
Does anyone have a solution to that?.. I think I need to start playing around with initrd, perhaps do my own that includes the module?
Jaska.
Viestissä Perjantai 24. Elokuuta 2001 03:00, Emilio kirjoitti:
Hi everybody! I'm a SuSE 7.0 user, I've just donwloaded new drivers for my HPT370 RAID controller intended for SuSE 7.1; these are provided only in precompiled modules for kernels 2.2.18 and 2.4.0-4GB. So I need to download the 2.4.0-4GB kernel but I can't find it on SuSE ftp site (lx_sus24.rpm in 7.1 directory provides kernel 2.4.2).
Please, help me!
Are the 2.4.0 sources you require on the original 7.1 CDs? M
Hi Nope.. In 7.1 there is 2.4.2 kernel... I did download 2.4.0 kernel from kernel.org, but I'm not able to make it. In the end when I do make bzImage it fails. Compiling is okay, but the few last lines when it whould actually put the image together it fails... there was something like "bbootsector" involved in that error. I've tried now the whole day to compile it, but I'm not able to.. So, I'm stuck with kernel 2.2.18, that works except my nice USB-mouse is not working :-( And actually to make the Abit-KT7 raid to work, You need to build the initrd-image too! That is not hard to do.. Jaska. Viestissä Perjantai 24. Elokuuta 2001 15:14, kirjoitit:
On Friday 24 August 2001 7:41 am, Jaakko Tamminen wrote:
I went that road yesturday, and now in boot I get:
"could not mount root file system 08:03" or similar...
Actually there is few lines up a message: "unable to excecute /sbin/modprobe char-major-8" or similar...
Ofcourse it cant excecute modprobe (or was it insmod), because sda3 is not yet mounted.. And in order to mount it, it need to load the module that is in sda3...
Does anyone have a solution to that?.. I think I need to start playing around with initrd, perhaps do my own that includes the module?
Jaska.
Viestissä Perjantai 24. Elokuuta 2001 03:00, Emilio kirjoitti:
Hi everybody! I'm a SuSE 7.0 user, I've just donwloaded new drivers for my HPT370 RAID controller intended for SuSE 7.1; these are provided only in precompiled modules for kernels 2.2.18 and 2.4.0-4GB. So I need to download the 2.4.0-4GB kernel but I can't find it on SuSE ftp site (lx_sus24.rpm in 7.1 directory provides kernel 2.4.2).
Please, help me!
Are the 2.4.0 sources you require on the original 7.1 CDs?
M
participants (6)
-
Anders Johansson -
Curtis Rey -
Dave Jones -
Emilio -
Jaakko Tamminen -
Martin Webster