Laptops :: How to install CPU Freq Driver
The comment about CONFIG_BLK_DEV_RAM caught my attention so I went back and checked the .config file before and after "make mrproper"/"make oldconfig" and discovered that (somehow) it was getting completely mangled - since "make oldconfig" was only showing the cpufreq options, I had presumed everything else was left as-is.
I had also noticed that kernelsource.dsl does not contain any kernel sources (sic) and I could not find them on Knoppix 3.4 so I prepared the sources as follows:
unpack 2.4.26 kernel sources (kernel.org) into /usr/src/linux-2.4.26
delete /usr/src/linux-2.4.26/include and replace with /include from Knoppix 3.4
copy knoppix kernel patch & .config from Knoppix 3.4
apply knoppix patch
apply cpufreq patch
Then, after pulling up a copy of the Knoppix 3.4 .config, I did "make mrproper"/"make config" using the exact same responses as in the Knoppix 3.4 .config (except for the cpufreq options) - an extremely tedious process, I will have to look at "make menuconfig"/"make xconfig".
Next I did "make dep", "make clean", "make bzImage", "make modules", "make modules_install", "make" & "make install" (not sure if the last two are neccessary) which gave a bzImage kernel file (as opposed to a vmlinuz file last time).
When I boot from the bzImage file, I get further than last time, but the last few messages are:
RAMDISK: Compressed image found at block 0
Freeing initrd memory 784k freed
VFS: Mounted root (ext2 filesystem) readonly
Freeing uneeded kernel memory 140k freed
Scanning for USB devices...Done
Accessing DSL image as /dev/sda1.../linuxrc cannot create /etc/ld.so.cache: read-only filesystem
and then things drop back into the extremely limited kernel
Since a successful boot with linux24 gives the message "VFS: Mounted root (ext2 filesystem)" without the "readonly", I presume the problem is this.
Edit: I made a test by recompiling the kernel without making any changes and using .config from Knoppix 3.4 - I get the same result, i.e. the root filesystem is mounted read-only and then /linuxrc cannot create...
No idea why it's only getting mounted ro...
but what I'd suggest (which was based on what i did in my previous post) is to
1. unpack kernel.org's 2.4.26 to some place
2. From kernelsource.dsl - extract only the knoppix kernel patch and .config
3. apply the knoppix kernel patch to #1
4. Copy the .config over to #1
5. Do your cpufreq stuff
6. make mrproper
7. Configure your kernel by make menuconfig - but first load the .config you copied in #4
8. do the rest of the 'make' stuff, etc. To just recompile the kernel you could do make dep; make clean; make bzImage
These steps are just made up so that you don't have to bother with the rest of the kernelsource.dsl or the stuff in knoppix 3.4 cd to minimize problems. Loading gcc1-with-libs, then gcc-2.95 should be good enough to do this and maybe gnu-utils for a safe measure.
Note: make install (after make bzImage) should install the kernel stuff to /boot so you don't need to worry about which file you're getting. Also, I think the bzImage IS vmlinuz - but not too sure about that. (make sure you don't use the vmlinux file though)
Hope this helps...
Thanks - I did exactly as you suggested (gnu-utils did not seem to be required) without bothering with the cpufreq patch, but no joy. The last few messages from booting with bzImage (from linux-2.4.26/arch/i386/boot) or vmlinuz-2.4.26 (from /boot) are:
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 784k freed
VFS: Mounted root (ext2 filesystem) readonly
Freeing uneeded kernel memory: 140k freed
Welcome to DSL boot splash
Scanning for USB devices...Done
Accessing DSL image at /dev/sda1.../linuxrc cannot create /etc/ld.so.cache: read-only filesystem
DSL boot splash repeats
mount: device or resource busy
mount: device or resource busy
Cannot find KNOPPIX filesystem, sorry
Dropping you to a (very limited) shell
Whereas in a successful boot using the original linux24, the last few massages are:
RAMDISK: Compressed image found at block 0
Freeing initrd memory: 784k freed
EXT2-fs warning checktime reached, running e2fsck recommended
VFS: Mounted root (ext2 filesystem)
Welcome to DSL boot splash
Scanning for USB devices...Done
Accessing DSL image at /dev/sda1...
Hm, having that as ro really is a show-stopper.
I'm not sure what you did differently as I wrote out those steps based on what I did.
The one thing I think may be the problem is loading the .config from kernelsource.dsl (using make oldconfig at this point should not prompt you for anything i think, but if you use make menuconfig you have to load it via the menu). Also note that I did not install the kernelsource.dsl ...
I've tried with .config from both kernelsource.dsl (without loading it) and from Knoppix 3.4 - I loaded .config via "make menuconfig", didn't change anything and then saved it.
Using "script", I saved the screen output from the various make commands - searching on "error" did not turn up anything, the only two things that caught my eye were:
1. Excerpt from output following "make bzImage", this kind of warning came up a few times:
quote
gcc -E -D -I/ramdisk/temp/linux-2.4.26/include -D -traditional -DSVGA_MODE=NORMAL_VGA bootsect.S -o bbootsect.s
as -o bbootsect.o bbootsect.s
bbootsect.s: Assembler messages:
bbootsect.s:258: Warning: indirect lcall without `*'
Unquote
2. Excerpt from output following "make install", I've noticed that this kind of BusyBox message appears after a command (or maybe command option) is passed that BusyBox doesn't know about - for example, if the "find" command is called, this type of message appears if gnu-utils is not loaded:
quote
tools/build -b bbootsect bsetup compressed/bvmlinux.out CURRENT > bzImage
Root device is (1, 0)
Boot sector 512 bytes.
Setup is 4868 bytes.
System is 966 kB
warning: kernel is too big for standalone boot from floppy
sh -x ./install.sh 2.4.26 bzImage /ramdisk/temp/linux-2.4.26/System.map ""
+ '[' -x /home/dsl/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 2.4.26 bzImage /ramdisk/temp/linux-2.4.26/System.map ''
BusyBox v1.00 (2006.01.04-23:00+0000) multi-call binary
Usage: readlink
Displays the value of a symbolic link.
unquote
All this apart, the only other thing I can think of that was done differently was a USB stick install as opposed to a HD install.
Next Page...
original here.