Re: [Cooker] Kernel 4.3.17mdk panics

Actually, he said he upgraded the kernel in that message. That is why I thought he might be having similar problems. --- Chmouel Boudjnah [EMAIL PROTECTED] wrote: SI Reasoning [EMAIL PROTECTED] writes: This might be related to the lack of initrd being created. I have had this problem on

Re: [Cooker] Kernel 4.3.17mdk panics

I just upgraded to 17 and had the same problem as always. Since I have been doing it manually (using make install in /usr/src/linux) I have had some bizarre behavior after I first upgrade. Only vmlinuz and system.map are properly linked to 17. Config was still linked to 16 and initrd was linked

Re: [Cooker] Kernel 4.3.17mdk panics

On Friday 13 April 2001 12:21 am, you wrote: I just upgraded to 17 and had the same problem as always. Since I have been doing it manually (using make install in /usr/src/linux) I have had some bizarre behavior after I first upgrade. Only vmlinuz and system.map are properly linked to 17.

Re: [Cooker] Kernel 4.3.17mdk panics

SI Reasoning wrote: Actually, he said he upgraded the kernel in that message. That is why I thought he might be having similar problems. - Yup, I upgraded it using ... RPMDRAKE! I wanted to see if it would handle it okay. shrugs

Re: [Cooker] Kernel 4.3.17mdk panics

I always check my /boot record and manually run lilo before I ever reboot after a kernel upgrade. I bet you can guess why now! --- Giles Hamlin [EMAIL PROTECTED] wrote: SI Reasoning wrote: Actually, he said he upgraded the kernel in that message. That is why I thought he might be

Re: [Cooker] Kernel 4.3.17mdk panics

SI Reasoning wrote: I always check my /boot record and manually run lilo before I ever reboot after a kernel upgrade. I bet you can guess why now! heh yeah - the question is though (and this is where my stupidity becomes overwhelming), is it possible to fix this without a boot disk? I

Re: [Cooker] Kernel 4.3.17mdk panics

As long as /usr/src/linux links to the 2.4 src directory... I would think yes. Otherwise go directly to the 2.4 source directory and do a make install. --- Giles Hamlin [EMAIL PROTECTED] wrote: SI Reasoning wrote: I always check my /boot record and manually run lilo before I ever

[Cooker] Kernel 4.3.17mdk panics

Just tried to upgrade to the new kernel, and it refuses to boot giving a kernel panic with the message "unable to mount vfs" any suggestions?

Re: [Cooker] Kernel 4.3.17mdk panics

Giles Hamlin [EMAIL PROTECTED] writes: Just tried to upgrade to the new kernel, and it refuses to boot giving a kernel panic with the message "unable to mount vfs" bad upgrade ? boot on a rescue cd and check your lilo.conf to point to the right partitions. -- MandrakeSoft Inc

Re: [Cooker] Kernel 4.3.17mdk panics

SI Reasoning [EMAIL PROTECTED] writes: This might be related to the lack of initrd being created. I have had this problem on both of my last 2 kernel upgrades. As root goto /usr/src/linux and type "make install" (without quotes). When this is complete type "lilo". This will allow you to