Re: [Cooker] FATAL: kernel too old

2000-12-13 Thread Guillaume Cottenceau

Udo Weber [EMAIL PROTECTED] writes:


[...]

 Please make the cooker compatible with the old 2.2.*-kernel,
 I think there are lot more issues to do this.

Latest glibc from Chmouel was kernel-2.4 only AFAIK. He should fix that
soon.


-- 
Guillaume Cottenceau - http://us.mandrakesoft.com/~gc/




[Cooker] FATAL: kernel too old

2000-12-12 Thread Udo Weber

Hi folks,

I know there was a big move to kernel 2.4 I also have installed
it with success and it works most time very well,

BUT I have some modules (e.g. for the IBM Etherjet-PCMCIA-card)
which are ONLY working withe kernel 2.2*.
src can't compiled with 2.4-kernels and the developer wants wait until
2.4 is offical released.
In the past I could run both kernels on cooker - why not now ?
Always since the last updates I get during the boot-process now

...
Freeing unused kernel memory: 124k freed
FATAL: kernel too old

and the system stops.

Please make the cooker compatible with the old 2.2.*-kernel,
I think there are lot more issues to do this.

Thanks,
Udo





Re: [Cooker] FATAL: kernel too old

2000-12-12 Thread Jean Meloche

On Tuesday 12 December 2000 17:49, you wrote:
 Hi folks,

 I know there was a big move to kernel 2.4 I also have installed
 it with success and it works most time very well,

 BUT I have some modules (e.g. for the IBM Etherjet-PCMCIA-card)
 which are ONLY working withe kernel 2.2*.
 src can't compiled with 2.4-kernels and the developer wants wait until
 2.4 is offical released.
 In the past I could run both kernels on cooker - why not now ?
 Always since the last updates I get during the boot-process now

 ...
 Freeing unused kernel memory: 124k freed
 FATAL: kernel too old

 and the system stops.

 Please make the cooker compatible with the old 2.2.*-kernel,
 I think there are lot more issues to do this.

 Thanks,
 Udo

How about

# touch /vmlinuz

Kidding... I had the same thing after trying a rpm -Uvh on the recent glibc.
I had to reboot: all exec failed. I rebooted a 2.4.0 kernel and the problem
disappeared.

-- 
Jean Meloche
[EMAIL PROTECTED]
e-gold # 133947