Hi, Chief, sorry for sounding fragmented, let me put the steps together sequentially.
Many linux commands are similar to Dos/win, like dir, cp, cd but GNU/Linux has much more.
The directories are referenced from /
if you cd to boot/grub/ (without the /), it will look from where you are, for boot/grub.
Which may not exist.
But if you cd /boot/grub it will look from / to find the dir.
for example...
Code:
door@MusicBox:~$ cd boot/grub (03-07 11:18)
cd: no such file or directory: boot/grub
door@MusicBox:~$ pwd (03-07 11:18)
/home/door
door@MusicBox:~$ cd /boot/grub (03-07 11:18)
door@MusicBox:/boot/grub$
Firstly, when you up-zipped/tarred the kernel to the old folder
Quote:
|
I copied my new kernel (linux-2.6.30.tar.bz2) to folder (/usr/src/linux-source-2.6.28).
|
That was the wrong thing to do, but I can understand why you might want to do that.
This is where the link to /usr/src/linux comes in, you can have many sources available, but only need to change the link to compile or build any of them (within reason)
So go back, you can delete that "/usr/src/linux-source-2.6.28" directory later if you need the space.
Start here....
move to the directory where the kernel .tar is, then (we need root (admin) access to write to /usr/src/folders, if the your shell terminal is already logged in as root, leave out the preceeding "sudo")
sudo tar cjf linux-2.6.30.tar.bz2 /usr/src/linux-2.6.30
change to the root (/) directory, type
cd / (enter) Or cd.. enter until you get there.
remove any old link...
sudo rm -rf /usr/src/linux
create a new link to the new kernel sources...
sudo ln -s /usr/src/linux-2.6.30 /usr/src/linux
now you should be ready to configure the kernel.
cd to it to make sure it's there and ls (list the files)
ls /usr/src/linux (it should be the same as /usr/src/linux-2.6.30)
save a backup copy of /boot/config to /boot/config-old
cp /boot/config /boot/config-old, (if you have done it, skip it. ;-))
Before you apply the patches, configure the kernel based on the old one (it works, right?)
cd /usr/src/linux
make oldconfig (this will apply the old /boot/.config file to the new Makefile)
You may get questions about any new stuff in the kernel, it's generally best to follow the defaults, unless you recognise something.
You may require the dev packages to do this, but unless you want to customise it further, you can probably skip the config part. (make xconfig, or menuconfig)
make all && make modules_install && make install.
If all goes well you should be able to boot into the new kernel just by rebooting.
If you see errors, and make stops, post those here for us to check. Don't reboot if you get errors, it may break your system!
Generally there are warnings, but rarely do they compromise the system, they are just messages.
see how you go, regards Glenn