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