Re: Still getting kernel panic when compiling my own kernel
That is what I did all the time. This thread was about how to do it a
different way.
Anyhow it seems to work now. Still I've some problems, but need to dig
into that. At least I am able to boot now and I am not sure what I did
wrong before. I ***guess*** is was something about dpkg -i and my
assumption that it does run lilo, because I now ran lilo by hand (to use
the manual approach described by Klaus.
So, I'll investigate further and come back to the list if it is still
not working.
Thanks to everyone for supporting me.
Mariano
On Sat, 2002-09-28 at 16:05, Hanasaki JiJi wrote:
> apt-get kernel-package
> read the readme in /usr/share/docs/kernel-package
> follow the instructions
>
> Mariano Kamp wrote:
> > If the below describe assumption was true then it didn't work out. I
> > have the same problem.
> >
> > Mariano
> >
> > On Sat, 2002-09-28 at 16:33, Mariano Kamp wrote:
> >
> >>Which one is "kernelimage"? I found one called bzImage, size ~500K.
> >>should I copy it to /boot/vmlinuz-2.4.18? on my system /vmlinuz points
> >>to /boot/vmlinuz-2.4.18 and /vmlinuz is configured in lilo.conf.
> >>
> >>Mariano
> >>
> >>On Sat, 2002-09-28 at 16:24, Mariano Kamp wrote:
> >>
> >>>On Sat, 2002-09-28 at 14:00, Klaus Imgrund wrote:
> >>>
> >>>>On 28 Sep 2002 15:43:48 +0200
> >>>
> >>>>Did you ever try the old fashioned way?
> >>>>
> >>>>cd /usr/src/linux-x.x.x
> >>>>make menuconfig
> >>>>make dep && make clean bzImage modules modules_install
> >>>>mv /boot/kernelimage /boot/kernelimage.orig
> >>>>cp /usr/src/linux-x.x.x/arch/i386/boot/bzImage /boot
> >>>>
> >>>>Prost,
> >>>
> >>>I'll try that and feed back.
> >>>
> >>>Mariano
> >>>
> >>>
> >>>--
> >>>To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> >>>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >>>
> >>
> >>
> >>
> >>--
> >>To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> >>with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> >>
> >
> >
> >
> >
>
Reply to: