On Fri, Sep 27, 2002 at 08:15:47AM +0530, J.S.Sahambi wrote:
> One thing more. Following is the dir list of /boot:
>
> *************
> jsahambi@ws97:/boot$ ll
> total 6788
> -rw-r--r-- 1 root root 547232 Jul 10 14:55
> System.map-2.4.18-bf2.4
> -rw-r--r-- 1 root root 423760 Aug 11 08:30
> System.map-2.4.19-686
> -rw-r--r-- 1 root root 423760 Sep 26 13:45
> System.map-2.4.19-patched
> -rw-r--r-- 1 root root 512 Jul 10 15:01 boot.0300
> -rw-r--r-- 1 root root 17370 Jul 10 14:55 config-2.4.18-bf2.4
> -rw-r--r-- 1 root root 38237 Aug 8 16:58 config-2.4.19-686
> -rw-r--r-- 1 root root 38237 Sep 26 13:11
> config-2.4.19-patched
> -rw-r--r-- 1 root root 2752512 Sep 11 08:36
> initrd.img-2.4.19-686
> -rw------- 1 root root 102400 Sep 26 20:03 map
> -rw-r--r-- 1 root root 1256707 Jul 10 14:55 vmlinuz-2.4.18-bf2.4
> -rw-r--r-- 1 root root 647416 Aug 11 08:30 vmlinuz-2.4.19-686
> -rw-r--r-- 1 root root 647157 Sep 26 13:45
> vmlinuz-2.4.19-patched
>
>
> ***************
>
> Now here I only have the initrd.img-2.4.19-686 file for 2.4.19-686 which
> is working, but not for the patched kernel. Do I need a saparate
> initrd... files for patched kernel? I fyes, where would the file be?
>
> The command I gave to build the package is :
> fakeroot make-kpkg --append-to-version -patched kernel_image
>
> This only generated the .deb file and not the initrd file
>
>
> What I am doing wrong????
>
> Thanks
> J S Sahambi
>
>
I took the kernel configuration help advice and avoided initrd.
There fore I can only guess about it. However like you, not having an
initrd file for the new kernel looks suspicious.
I believe that the initrd file is created separately from the creation
of a kernel deb package. Maybe with the initrd-tools package?
>
>
>
>
>
>
> [EMAIL PROTECTED] wrote:
> >On Thu, Sep 26, 2002 at 03:06:11PM +0530, J.S.Sahambi wrote:
> >
> >>I patched some files and then made the kernel "2.4.19-patched" with the
> >>following commands:
> >>
> >>fakeroot make-kpkg --append-to-version -patched kernel_image
> >>
> >>
> >>and then installed the kernel with :
> >>dpkg -i kernel-image-2.4.19-patched_10.00.Custom_i386.deb
> >>
> >>
> >>
> >>Then I modified the /etc/lilo/conf
> >>
> >>When i boot from this kernel i get the following errors and the kernel
> >>panics
> >>
> >>
> >>******************
> >>.
> >>.
> >>.
> >>modprobe: cant find dependency file
> >>/lib/modules/2.4.19-patched/modules.dep
> >>modprobe: cant find dependency file
> >>/lib/modules/2.4.19-patched/modules.dep
> >>modprobe: cant find dependency file
> >>/lib/modules/2.4.19-patched/modules.dep
> >>
> >>mount you must specify a file system
> >>kernel panic - Attempted tokill init
> >>
> >>********************************
> >>But i have seen that modules.dep exits
> >>ll /lib/modules/2.4.19-patched/modules.dep
> >>-rw-r--r-- 1 root root 112310 Sep 26 13:50
> >>/lib/modules/2.4.19-patched/modules.dep
> >>
> >>
> >>
> >>
> >>Can any body help me out.
> >>Thanks
> >>J S Sahambi
> >>
> >
> >
> >
> >You haven't mentioned running lilo after modifying /etc/lilo.conf.
> >Is it too obvious that you forgot to mention it?
> >
>
>
>
> --
> Dr. J. S. Sahambi
> Assistant Professor
> Dept. of Electronics & Communication Engg.
> Indian Institute of Technology,
> Guwahati 781039, Assam, INDIA
> Phone(o) : +91-361-690321 Ext. 2055,
> (R) : +91-361-690940
> Fax : +91-361-690762,
> Email : [EMAIL PROTECTED]
> : [EMAIL PROTECTED]
>
--
Shaul Karl, [EMAIL PROTECTED] e t
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
