Hi all, This will be the first time i'm compiling a kernel, on this box, scsi troubles me: PIII 800 mb asus p3c intel 820 chipset 258 MB Rimm memory 800Mhz scsi card 2940 U2W ( aic7*** i suppose ) sda = 18 GB disk 10000rpm full windows sdb = 18 GB disk 10000rpm full suse 7 ( stable ) ext2 sdc = 18 GB disk 10000rpm full RH7 sdd = 36 GB disk 10000rpm full SuSE 7 ( test ) rsfs sound = sb PCI 128 cdrom = plextor scsi 40x cdwriter = plextor 12/4/32 video = Geforce DDR scanner = snapscan 1212 U USB mouse = Intellieye KB = logitech ( french kb ) Being off computer world since university (+/- 25 years ), i've been working very hard to catch up my delay in the linux world ( one year (in my spare time)), having only used Win (word&excell) before. I test a lot of things on sdd and i have a SuSE for working on sdb The "last" thing to do now : compiling a kernel ( downloaded 2.4.0 + suse 24 patch.gz ). This is what I'm going to do : 1. upgrading to modutil 2.4.0 2. make cloneconfig of actual kernel ( 2.2.16 ) and print it out 3. cd /usr/src and rm linux 4. tar zxpvf linux-2.4.0.SuSE-14.tgz Question : can I apply the patch file from here; if yes how ? 5. mv linux linux-2.4.0.SuSE-14; ln -s linux-2.4.0.SuSE-14 linux 6. make xconfig, looking around and matching the previous cloneconfig file Question : including reiserfs in the kernel ?? I suppose so. 7. make dep make clean make bzImage make modules make modules_install 8. cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.0-SuSE-14 cp /usr/src/linux/Sy test a lot of things on sdd and i have a SuSE for working on sdb The last thing to do now : compiling a kernel ( downloaded 2.4.0 + suse 2.4.0-15.gz ). test a lot of things on sdd and i have a SuSE for working on sdb The last thing to do now : compiling a kernel ( downloaded 2.4.0 + suse 2.4.0-15.gz ).stem.map /boot/System.map-2.4.0-SuSE-14 9. yast ---> check if aic7xxx+usbcore is in INITRD_MODULES 10. mk_initrd-2.4.0-SuSE-14 ( is this correct ???? and will this put initrd..... in /boot/ ?????? 11. edit lilo.conf and adding the lines : image = /boot/vmlinuz-2.4.0-SuSE-14 root = /dev/sdd2 label = lin-2.4.0-SuSE-14 initrd = /boot/initrd-2.4.0-SuSE-14 12 /sbin/lilo Any suggestions are really welcome, specially for the patch file, reiserfs and mk_initrd. Meanwhile, I'll read some more howtos. TIA Filip.
filip wrote:
This will be the first time i'm compiling a kernel, on this box, scsi troubles me:
I test a lot of things on sdd and i have a SuSE for working on sdb The "last" thing to do now : compiling a kernel ( downloaded 2.4.0 + suse 24 patch.gz ).
This is what I'm going to do : 1. upgrading to modutil 2.4.0 2. make cloneconfig of actual kernel ( 2.2.16 ) and print it out
This is only really useful as a reference. So much has changed between the 2.2.x and the 2.4.0 kernels that it is better to just go through the config selecting options as appropriate, rather using an old config and trying to 'fix' it to get it to compile.
3. cd /usr/src and rm linux 4. tar zxpvf linux-2.4.0.SuSE-14.tgz Question : can I apply the patch file from here; if yes how ? 5. mv linux linux-2.4.0.SuSE-14; ln -s linux-2.4.0.SuSE-14 linux
Now install the patch file: cd /usr/src; patch -p0 < /path/to/patch/file
6. make xconfig, looking around and matching the previous cloneconfig file Question : including reiserfs in the kernel ?? I suppose so.
I would include it in the kernel. I had problems when it wasn't. Don't take the old config 'word for word' as I mentioned earlier.
7. make dep make clean make bzImage make modules make modules_install 8. cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.0-SuSE-14 cp /usr/src/linux/System.map /boot/System.map-2.4.0-SuSE-14 9. yast ---> check if aic7xxx+usbcore is in INITRD_MODULES 10. mk_initrd-2.4.0-SuSE-14 ( is this correct ???? and will this put initrd..... in /boot/ ??????
If you want to keep your previous initrd file (probably a wise idea), then you'll need to make a copy of it, as the mk_initrd command stores the image as /boot/initrd. You can then rename this to initrd-2.4.0-SuSE-14 afterwards (and copy your original initrd file back if you need to).
11. edit lilo.conf and adding the lines : image = /boot/vmlinuz-2.4.0-SuSE-14 root = /dev/sdd2 label = lin-2.4.0-SuSE-14 initrd = /boot/initrd-2.4.0-SuSE-14
If you don't already have it, I'd also put a separate entry for your current kernel so that if, in the future, you install a kernel to /boot/vmlinuz, you'll still have a working kernel image.
12 /sbin/lilo
Any suggestions are really welcome, specially for the patch file, reiserfs and mk_initrd. Meanwhile, I'll read some more howtos.
Bye, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\
participants (2)
-
Chris Reeves -
filip