hi all,

I've recompiled my kernel (2.4.20-8) in REDHAT 9.0, but i don't want x to start with this specific kernel, but i want it to start with the original kernel..


also with the new kernel i get the message that something is wrong with the ip-table during startup, it [FAILED]

and this also happens with the usb-uhci....

the only thing i did with the new kernel is changed the cpu type and supported NTFS read only...

this i did with the make xconfig command, for the rest i kept everything the same...


i'm pretty new to unix/linux and this is the first time i ever compiled a kernel....



any hints would be greatly appreciated...


ps, i've been searching google for over 2 hours now, but i haven't found anything usefull yet...
only info on how to compile the kernel and configure it, but not about these specific things!

You mean you want to boot to your new kernel but then change back to your old kernel when X starts?! That's not possible.

Make sure you're building uhci and full IP tables support - I think building them as modules is default in Redhat. But for NTFS you could just install the RPM from http://linux-ntfs.sourceforge.net and use the default Redhat kernel.

As for X not starting - either you have missed some critical support in the kernel configuration - agpgart or DRI for your chipset perhaps? Or you use a binary driver (ATI or Nvidia user?) which relies on a specific kernel version. If so, download the tar.gz package of the driver and build it against your own kernel.


Håkan

I think he means that when he chooses his old kernel from LILO/GRUB, he wants X to automatically startup, but if he chooses the new kernel, he doesn't want X to automatically startup.

I'm not really sure why you would want to do this, but I don't think it's possible.

that's exactly what i mean, let me explain:

on the default kernel i've installed the latest nvidiadriver to play ut2004, but when i launch my new kernel, it automatically starts x, but fails doing so, since XF86Config isn't correct... when i install the nvdia driver again with the new kernel the problem is solved,
but when i launch my default kernel again, it has the same problem as the custom kernel before installing the driver...

so that's why i want the custom kernel not to start x, so i can test the custom kernel and play with it, without having to install the driver over and over again if i want to play a game...

and somehow when i play ut2004, it runs better with the default kernel, where i suppose to have a PII cpu, then with the custom kernel, although i've said here it is a PIV....

i think this is really strange....


the only thing i can think of to solve the above problem, is to create another partition and make my system triple boot... one windows xp, one redhat 9 default kernel, and one red hat9 custom kernel...
i just hope this isn't necessary...