Hello,
After trying different methods to compile a Puppy Linux kernel without IDE and SATA modules I had no success. It seems that totorials that I followed are above my knowledges...maybe I need a simple tutorial.
I need kernel 2.6.33.2 pet without IDE and SATA modules. I want to use it in Woof for building a distribution which don't touch the hard-drives.
Maybe there are other people who needs this task too.
If someone can post a simple tutorial for doing this it will be great too.
I appreciate any help!
Thank you.
need kernel 2.6.33.2 .pet - no IDE and SATA
-
laurentius77
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
need kernel 2.6.33.2 .pet - no IDE and SATA
Last edited by laurentius77 on Wed 20 Apr 2011, 06:59, edited 1 time in total.
-
laurentius77
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
Thank you Scsijon for your post. I can deactivate IDE or SATA from Bios but I need them because there are other operating systems that I use them regularly from hard-drives.
Until now I tried following methods:
Method 1
- downloaded patched kernel source from
http://bkhome.org/sources/kernel-2.6.33.2/
- Compiling the kernel
# make clean
# make mrproper
<<<copy in the .config file
# make menuconfig
Removed SATA and IDE modules from menuconfig
# make bzImage
# make modules
# make modules_install
bzImage is in arch/x86/boot/, renamed to 'vmlinuz'
The problem is that when I run make modules_install command I got some errors. Even in case of success I don't know how to make the .pet: should I make the .pet using command dir2pet linux-2.6.33.2 ? Because this folder is pretty huge (370 MB)
Maybe this is not the proper method to compile the kernel
Method 2
- followed Iguleders method from
http://brainwavedesigncentral.net/dima/ ... -howto.txt
- downloaded linux kernel 2.6.33.2 source
- followed instructions successfully until command
make INSTALL_MOD_PATH=linux_kernel-2.6.33.2-bfs install
- here I got this error
sh /root/linux_kernel-2.6.33.2-bfs/linux-2.6.33.2/arch/x86/boot/instal.sh 2.6.33.2 arch/x86/boot/bzImage \
System.map "boot"
/root/linux_kernel-2.6.33.2-bfs/linux-2.6.33.2/arch/x86/boot/install.sh: line 49
: /boot/vmlinuz: No such file or directory
cp: cannot create regular file '/boot/System.map': No such file or directory
Cannot find LILO.
I think there are some other commands before running make INSTALL_MOD_PATH=linux_kernel-2.6.33.2-bfs install
I tried to create folder structure before launching the command. Anyway in this tutorial the folder structure is created after the command.
Maybe the tutorial has some minor lacks which doesn't create problems for experienced users but for me they are embarrassing.
I think the problem is that there is not a line by line tutorial for inexperienced users for compiling kernel...or this task should be accomplished just by the experienced ones.
I don't know how to solve the problem so I need your help.
I will try to PM 01micko if I can't finally solve the problem.
Thanks.
Until now I tried following methods:
Method 1
- downloaded patched kernel source from
http://bkhome.org/sources/kernel-2.6.33.2/
- Compiling the kernel
# make clean
# make mrproper
<<<copy in the .config file
# make menuconfig
Removed SATA and IDE modules from menuconfig
# make bzImage
# make modules
# make modules_install
bzImage is in arch/x86/boot/, renamed to 'vmlinuz'
The problem is that when I run make modules_install command I got some errors. Even in case of success I don't know how to make the .pet: should I make the .pet using command dir2pet linux-2.6.33.2 ? Because this folder is pretty huge (370 MB)
Maybe this is not the proper method to compile the kernel
Method 2
- followed Iguleders method from
http://brainwavedesigncentral.net/dima/ ... -howto.txt
- downloaded linux kernel 2.6.33.2 source
- followed instructions successfully until command
make INSTALL_MOD_PATH=linux_kernel-2.6.33.2-bfs install
- here I got this error
sh /root/linux_kernel-2.6.33.2-bfs/linux-2.6.33.2/arch/x86/boot/instal.sh 2.6.33.2 arch/x86/boot/bzImage \
System.map "boot"
/root/linux_kernel-2.6.33.2-bfs/linux-2.6.33.2/arch/x86/boot/install.sh: line 49
: /boot/vmlinuz: No such file or directory
cp: cannot create regular file '/boot/System.map': No such file or directory
Cannot find LILO.
I think there are some other commands before running make INSTALL_MOD_PATH=linux_kernel-2.6.33.2-bfs install
I tried to create folder structure before launching the command. Anyway in this tutorial the folder structure is created after the command.
Maybe the tutorial has some minor lacks which doesn't create problems for experienced users but for me they are embarrassing.
I think the problem is that there is not a line by line tutorial for inexperienced users for compiling kernel...or this task should be accomplished just by the experienced ones.
I don't know how to solve the problem so I need your help.
I will try to PM 01micko if I can't finally solve the problem.
Thanks.
-
laurentius77
- Posts: 82
- Joined: Wed 30 Mar 2011, 07:02
Tried another tutorial for upgrade Puppy kernel, found on http://pateo.wordpress.com/. Thanks to the author for the tutorial.
This one is pretty well explained but I have troubles again...
boot puppy
I have a Puppy 5.2 distribution with 2.6.33.2 kernel
reboot create save file
add dev sfs to boot
reboot
untar source to any existing <HD> (preferably linux FS – may work with NTFS)
Refer to the kernel version notes provided by Barry at http://puppylinux.com/sources (id=puppy pw=linux) and patch source per instructions
Perform any other personal patches as required
I downloaded and untared patched kernel source 2.6.33.5 from www.puppylinux.com/sources
I didn’t apply any supplementary patches because I don’t need any this time. Is this a correct approach or should I download original source and apply patches?
In <HD> partition where source extracted, mkdir remasterinit remasteriso remastersfs folders
Mount the base puppy iso by clicking on it then copy all files to remasteriso
Mount the sfs by clicking on it then copy all files to remastersfsShould mount is lupu_520.sfs or new kernel source patched sfs from www.puppylinux.com/sources ?
cd remasterinit
zcat remasteriso/initrd.gz | cpio -i -d
rm -r remastersfs/lib/firmware
mkdir remastersfs/lib/firmware
mv /lib/modules /lib/modules.old
mv /lib/firmware /lib/firmware.old
Are these two lines target /lib/modules and /lib/firmware from my Puppy 520 /root or the right commands should target remastersfs folder and to be:
mv /remastersfs/lib/modules /remastersfs/lib/modules.old
mv /remastersfs/lib/firmware /remastersfs/lib/firmware.old
What is the reason for giving this command?
cd /lib
Is this command target /lib from Puppy 520 /root or the right command should be
cd /remastersfs/lib
ln -s remastersfs/lib/modules/ modules
ln -s remastersfs/lib/firmware/ firmware
cd <HD> source
make clean
make mrproper
copy DOTConfig file provided by Barry at Puppylinux.com to source folder and rename to .config
make menuconfig (kernel hacking – timers stats, usb sleep, sound generic ac97)
make bzImage
make modules
make modules_install
cp -r -p <source>/arch/x86/boot/bzImage /remasteriso/vmlinuz
copy remastersfs/lib/modules/<new kernel> remasterinit/lib/modules/<new kernel>
Here I have two misunderstandings:
- from this tutorial I can’t see how <new kernel> folder can appear in remastersfs/lib/modules. Because after following this tutorial /remastersfs/lib/modules/<2.6.33.5> is not suppose to be found in this place.
- copy is not a command in Linux, should I use cp –r or cp –r –p ?
===================================
[for puppy]
rm remastersfs/lib/modules/<new kernel>/modules.*
cp -r -p remasterinit/lib/modules/<old kernel>/modules.* remasterinit/lib/modules/<new kernel>/ [overwrite existing files]
Same problem with <new kernel> folder
edit remasterinit/lib/modules/modules.dep and replace old kernel path with new kernel path
Here I suppose that I shoul change 2.6.33.2 with 2.6.33.5, is it correct?
===================================
cd remasterinit/lib/modules/<new kernel>
replicate folders/files per <old kernel> and gzip .ko files
Here I suppose I should create similar folder structure. Which is the right command for gzip .ko files? Should I zip them one by one?
rm -r remasterinit/lib/modules/<old kernel>
cd remasterinit
find . | cpio -o -H newc | gzip -9 > <HD>/initrd.gz
cp -r -p <HD>/initrd.gz remasteriso/
cd remastersfs
rm -r remastersfs/lib/modules/<old kernel>
mksquashfs . hd/<new sfs name>.sfs
cp <HD>/<new sfs name>.sfs /remasteriso
cd /remasteriso
mkisofs -D -R -o <HD>/<yourpuppyname.iso> -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table
This one is pretty well explained but I have troubles again...
boot puppy
I have a Puppy 5.2 distribution with 2.6.33.2 kernel
reboot create save file
add dev sfs to boot
reboot
untar source to any existing <HD> (preferably linux FS – may work with NTFS)
Refer to the kernel version notes provided by Barry at http://puppylinux.com/sources (id=puppy pw=linux) and patch source per instructions
Perform any other personal patches as required
I downloaded and untared patched kernel source 2.6.33.5 from www.puppylinux.com/sources
I didn’t apply any supplementary patches because I don’t need any this time. Is this a correct approach or should I download original source and apply patches?
In <HD> partition where source extracted, mkdir remasterinit remasteriso remastersfs folders
Mount the base puppy iso by clicking on it then copy all files to remasteriso
Mount the sfs by clicking on it then copy all files to remastersfsShould mount is lupu_520.sfs or new kernel source patched sfs from www.puppylinux.com/sources ?
cd remasterinit
zcat remasteriso/initrd.gz | cpio -i -d
rm -r remastersfs/lib/firmware
mkdir remastersfs/lib/firmware
mv /lib/modules /lib/modules.old
mv /lib/firmware /lib/firmware.old
Are these two lines target /lib/modules and /lib/firmware from my Puppy 520 /root or the right commands should target remastersfs folder and to be:
mv /remastersfs/lib/modules /remastersfs/lib/modules.old
mv /remastersfs/lib/firmware /remastersfs/lib/firmware.old
What is the reason for giving this command?
cd /lib
Is this command target /lib from Puppy 520 /root or the right command should be
cd /remastersfs/lib
ln -s remastersfs/lib/modules/ modules
ln -s remastersfs/lib/firmware/ firmware
cd <HD> source
make clean
make mrproper
copy DOTConfig file provided by Barry at Puppylinux.com to source folder and rename to .config
make menuconfig (kernel hacking – timers stats, usb sleep, sound generic ac97)
make bzImage
make modules
make modules_install
cp -r -p <source>/arch/x86/boot/bzImage /remasteriso/vmlinuz
copy remastersfs/lib/modules/<new kernel> remasterinit/lib/modules/<new kernel>
Here I have two misunderstandings:
- from this tutorial I can’t see how <new kernel> folder can appear in remastersfs/lib/modules. Because after following this tutorial /remastersfs/lib/modules/<2.6.33.5> is not suppose to be found in this place.
- copy is not a command in Linux, should I use cp –r or cp –r –p ?
===================================
[for puppy]
rm remastersfs/lib/modules/<new kernel>/modules.*
cp -r -p remasterinit/lib/modules/<old kernel>/modules.* remasterinit/lib/modules/<new kernel>/ [overwrite existing files]
Same problem with <new kernel> folder
edit remasterinit/lib/modules/modules.dep and replace old kernel path with new kernel path
Here I suppose that I shoul change 2.6.33.2 with 2.6.33.5, is it correct?
===================================
cd remasterinit/lib/modules/<new kernel>
replicate folders/files per <old kernel> and gzip .ko files
Here I suppose I should create similar folder structure. Which is the right command for gzip .ko files? Should I zip them one by one?
rm -r remasterinit/lib/modules/<old kernel>
cd remasterinit
find . | cpio -o -H newc | gzip -9 > <HD>/initrd.gz
cp -r -p <HD>/initrd.gz remasteriso/
cd remastersfs
rm -r remastersfs/lib/modules/<old kernel>
mksquashfs . hd/<new sfs name>.sfs
cp <HD>/<new sfs name>.sfs /remasteriso
cd /remasteriso
mkisofs -D -R -o <HD>/<yourpuppyname.iso> -b isolinux.bin -c boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table