% ncftpget ftp://ftp.jp.kernel.org/pub/linux/kernel/v2.2/linux-2.2.14.tar.gz % su # rm /usr/src/linux # gtar zxvf linux-2.2.14.tar.gz -C /usr/src # mv /usr/src/linux /usr/src/linux-2.2.14 # ln -s /usr/src/linux-2.2.14 /usr/src/linux # cd /usr/src/linux # setenv DISPLAY abyss:0.0 # make xconfig |& tee MAKE_XCONFIG_LOG //# make dep |& tee MAKE_DEP_LOG # make-kpkg clean # make-kpkg --revision vaio505rx-0 --zimage kernel_image |& tee MAKE_KPKG_LOG or # make-kpkg --revision pws266i-2000.MMDD.NN --bzimage kernel_image |& tee MAKE_KPKG_LOG_MMDDNN # cd .. # dpkg -i kernel-image-2.2.14_pws266i_2000.0308.01_i386.deb |& tee DPKG_INST_LOG_030901 or # dpkg -i kernel-image-2.2.14_vaio505rx-0_i386.deb 未選択パッケージ kernel-image-2.2.14 を選択しています。 (データベースを読み込んでいます... 現在 64581 個のファイルとディレクトリがインストールされています。) (kernel-image-2.2.14_vaio505rx-0_i386.deb から) kernel-image-2.2.14 を展開しています... kernel-image-2.2.14 (vaio505rx-0)を設定しています ... A new kernel image has been installed, and usually that means that some action has to be taken to make sure that the new kernel image is used next time the machine boots. Usually, this entails running a ``bootloader'' like grub, SILO, loadlin, LILO, QUIK, or booting from a floppy. A new kernel image has been installed. LILO sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy. WARNING If you are keeping another operating system or another version of Linux on a separate disk partition, you should not have LILO install a boot block now. Wait until you read the LILO documentation. That is because installing a boot block now might make the other system un-bootable. If you only want to run this version of Linux, go ahead and install the boot block here. If it does not work, you can still boot this system from a floppy. Would you like to create a boot floppy now? [No] You already have a LILO configuration in /etc/lilo.conf Install a boot block using the existing /etc/lilo.conf? [Yes] Testing lilo.conf ... The boot sector and the map file have *NOT* been altered. Testing successful. Installing the partition boot sector... Installation successful. #
% ncftpget ftp://ftp.jp.kernel.org/pub/linux/kernel/v2.2/linux-2.2.10.tar.gz % su # rm /usr/src/linux # gtar zxvf linux-2.2.10.tar.gz -C /usr/src # mv /usr/src/linux /usr/src/linux-2.2.10 # ln -s /usr/src/linux-2.2.10 /usr/src/linux # cd /usr/src/linux # setenv DISPLAY abyss:0.0 # make xconfig rm -f include/asm ( cd include ; ln -sf asm-i386 asm) make -C scripts kconfig.tk make[1]: Entering directory `/usr/src/linux-2.2.10/scripts' gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkparse.o tkparse.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkcond.o tkcond.c gcc -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -c -o tkgen.o tkgen.c gcc -o tkparse tkparse.o tkcond.o tkgen.o cat header.tk >> ./kconfig.tk ./tkparse < ../arch/i386/config.in >> kconfig.tk echo "set defaults \"arch/i386/defconfig\"" >> kconfig.tk echo "set ARCH \"i386\"" >> kconfig.tk cat tail.tk >> kconfig.tk chmod 755 kconfig.tk make[1]: Leaving directory `/usr/src/linux-2.2.10/scripts' wish -f scripts/kconfig.tkTune as you like:
# make dep # make-kpkg --revision vaio505rx-0 kernel_image -zimage | & tee MAKE_KPKG_LOG # cd .. # dpkg -i kernel-image-2.2.10_vaio505rx-0_i386.deb Selecting previously deselected package kernel-image-2.2.10. (Reading database ... 56857 files and directories currently installed.) Unpacking kernel-image-2.2.10 (from kernel-image-2.2.10_vaio505rx-0_i386.deb) .. . Setting up kernel-image-2.2.10 (vaio505rx-0) ... A new kernel image has been installed, and usually that means that some action has to be taken to make sure that the new kernel image is used next time the machine boots. Usually, this entails running a ``bootloader'' like grub, SILO, loadlin, LILO, QUIK, or booting from a floppy. A new kernel image has been installed. LILO sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy. WARNING If you are keeping another operating system or another version of Linux on a separate disk partition, you should not have LILO install a boot block now. Wait until you read the LILO documentation. That is because installing a boot block now might make the other system un-bootable. If you only want to run this version of Linux, go ahead and install the boot block here. If it does not work, you can still boot this system from a floppy. Would you like to create a boot floppy now? [No] no You already have a LILO configuration in /etc/lilo.conf Install a boot block using the existing /etc/lilo.conf? [Yes] yes Testing lilo.conf ... The boot sector and the map file have *NOT* been altered. Testing successful. Installing the partition boot sector... Installation successful. #
% cd /usr/local/src/sys/ % ncftpget ftp://ftp.jp.kernel.org/pub/linux/kernel/v2.2/linux-2.2.4.tar.gz % su # cd /usr/src/ # gtar zxvf /usr/local/src/sys/linux-2.2.4.tar.gz # mv linux linux-2.2.4 # ln -s linux-2.2.4 linux # cd linux # setenv DISPLAY abyss:0.0 # make xconfigWhere's the config file? Let's see... It looks like /usr/src/linux/.config. It seems okay. Let's move on.
# make-kpkg --revision vaio505rx.0 kernel_image -zimage # cd .. # dpkg -i kernel-image-2.2.4_vaio505rx.0_i386.deb Selecting previously deselected package kernel-image-2.2.4. (Reading database ... 53056 files and directories currently installed.) Unpacking kernel-image-2.2.4 (from kernel-image-2.2.4_vaio505rx.0_i386.deb) ... Setting up kernel-image-2.2.4 (vaio505rx.0) ... A new kernel image has been installed, and usually that means that some action has to be taken to make sure that the new kernel image is used next time the machine boots. Usually, this entails running a ``bootloader'' like grub, SILO, loadlin, LILO, QUIK, or booting from a floppy. A new kernel image has been installed. LILO sets up your system to boot Linux directly from your hard disk, without the need for a boot floppy. WARNING If you are keeping another operating system or another version of Linux on a separate disk partition, you should not have LILO install a boot block now. Wait until you read the LILO documentation. That is because installing a boot block now might make the other system un-bootable. If you only want to run this version of Linux, go ahead and install the boot block here. If it does not work, you can still boot this system from a floppy. Would you like to create a boot floppy now? [No] no You already have a LILO configuration in /etc/lilo.conf Install a boot block using the existing /etc/lilo.conf? [Yes] yes Testing lilo.conf ... The boot sector and the map file have *NOT* been altered. Testing successful. Installing the partition boot sector... Installation successful. #At first, I enabled most features by answering "Yes" (put them statically in kernel), but it ended up with too big kernel and the kernel configuration utility advised me to make it as bzImage. Unfortunately, I couldn't succeed to boot a bzImage kernel on VAIO. So, I have to stick to zImage. I reconfigured kernel by answering "Module" (enable them as dynamically loadable module) which consequently makes the kernel size smaller and it worked.
# vi /etc/lilo.conf # /sbin/liloBooting up with a fresh kernel. It stopped rebooting in midst of extracting boot image now!
I checked APM BIOS is properly recognized. apm, xpm, xbatt are working correctly. suspend/resume just works well. network card is coming back after resume.
abyss:/home/dxy[9:17] apm APM BIOS 1.2 (kernel driver 1.9) AC on-line, battery charging: 100% (3:00)