lilo.conf error
 

Hi all, i just compiled the 2.6.13.1 kernel and i got to the part about adding it to the lilo.conf but ive made mistakes and dont have my old lilo.conf anymore, stupid of me i know :( When i use "/sbin/lilo" i get:

Added Linux
Added test-2.6.13.1 *
Syntax error at or above line 27 in file '/etc/lilo.conf'

Here is my broken lilo.conf:

Hopefully someone who isnt a complete newbie can see what i've done wrong :(

Any help very appreciated

OK i used liloconfig to make a new one and added the new kernel properly this time. Have a few other problems now though :(

1. When slackware is booting up it says How do i turn this on?

2. Also it says What is this, how do i remove it?

3. Lastly also it says
Again, any help at all appreciated

Hello dave,
would like to ask.......which "config" file you used while compiling the kernel. ??
have you upgraded your kernel from 2.4.x......or was it 2.6.x ??

regards

Upgraded from the 2.4 kernel, the one that comes with Slackware 10.1. I compiled that 1 too to change a few things.

The config file, i think it was generated by me using xconfigjust before starting to compile the 2.6 kernel? Not too sure :/

hi,
well not very sure......but i think slackware 10.1 too is 2.4.x kernel
if you are upgrading it to 2.6.x then you are not supposed to use the "config" of 2.4.x.
Get your slackware 10.1 second cd.
search for "testing" directory ( folder ) in it.....do a littly more search inside it......there you will get a "config 2.6.x"
use this as the base.

may it help you in solving your problem

lol me too facing some problem while upgrading my slackware 10.0 to 2.6.x ( my X window is giving error, but thats a different story )

regards

Does'nt me going through and choosing options then saving them in xconfig make a config file?

wait !
are not you loading any "config" file before selecting/unselecting among the various option during "make xconfig".
if you are not loading then you are doing mistake.
suppose u compile the way you are doing....fine.
now next time when you will be compiling the kernel.....will you start in the same way ????
it will be started from the scratch again.
at that time you will have to "load" the "config" file of last compiled kernel ( which will be keeping all the changes with it ), otherwise if you wont load it.......you will be starting from scratch i.e you won't find any of the changes you made during the last compilation.
i hope you are getting my point

now since you are compiling for the first time, use the "config" which i told you.
this config has the settings of the options of the kernel which you are using currently.

and ya you are very much right that after saving ( after make xconfig ) a "config" file will be created. backup this config file in some other directory b'coz you will be using it next time during compilation.

other directory b'coz.....during the "make mrproper" it deletes your "config" from /boot or where ever you had it......so have a backup in some other directory too

regards

ahhh i think i know what you mean now, i think i have a problem, i did "make mrproper" without backing up my old config first :(

Any suggestions? Should i just get a test config off the slackware cd 2 and try again?

I still have my old kernel on the system, and listed in lilo.conf so i can still choose it. Will this help at all?

ya, since you are going to upgrade your kernel from 2.4.x to 2.6.x so you should use "config" of 2.6.x and not of 2.4.x........which you will find in second cd somewhere inside testing folder.

regards

Before i try the test config on slackware cd 2 thought it might help to mention this, I've been told i should have done "make oldconfig" to use the settings that worked on the 2.4.29 kernel. Seeing as i think i deleted my old config im not sure this is an option.

In /usr/src/linux-2.4.29/arch/i386 there are config.in and defconfig files, can i use these somehow?

read this
from this tutorial i learnt kernel compilation.
frankly speaking........me too new to kernel compilation.....don't know much, have compiled my 2.4.x kernel 8-10 times only.
what ever i knew, i've already explained

and i never used " make oldconfig".....instead of that i prefer to load the old config file manually.
and if you are going to follow the steps of the above stated tut........then please take care of not tempering with the original files ( as i have already stated )

regards

make oldconfig works but you cannot use it interchangeably in different kernel series.i.e. you cannot make oldconfig 2.4.x series config file for compiling 2.6.x series kernel. I suggest you use the kernel Pat provides in slackware-current. Go to slackware-current ---> testing ---> packages. You'll see a folder for linux-2.6.13...the latest kernel. Download the necessary tarballs kernel-generic, kernel-modules and kernel-source. **Be careful** of kernel-headers and read the warning posted there.

Install this kernel and see how it fares. You can then take the config file from this kernel and try compiling your own kernel. This way you would have a 2.6 series working kernel and you can continue to tweak the config file till it works. Once a config file is ready...everything else is a breeze. That config file is also going to serve you for future kernels unless you upgrade your system or want to use a special functionality in future kernels.

Hope this helps
Tux,

hi
1) you can enable DMA adding a line like
/usr/sbin/hdparm -d1 /dev/hdx
in your /etc/rc.d/rc.local.
hdx is where your linux partitions are (may be hda,b,oc....)
This unfortunately cannot help you if you experience speed problems while fscking the partitions at boot, as /etc/rc.d/c.rc.local is at the very end of the boot sequence.
I'd suggest you recompile the kernel enabling DMA in the kernel.

2) Not very clear to me with just these infos. It seems a USB-controller module failed creating a node while loading...
Not sure

3) Don't get scaried by the "FATAL" message.
this simply means the listed modules has not been loaded, but it doesn't necessarely means your system is affected by that.
For instance if you choosed to "build in" the kernel those drivers your get that message although your system has full functionality. If this is the case just comment out their occourrencies in your /etc/rc.d/rc.modules.
What makes things a little complicate is snd_pcm_oss and snd_mixer_oss are loaded by /etc/rc.d/rc.alsa.
Editing that script requires a bit of experience.....

Hope this helps
Ciao