RE: Kernel Panic was: System is too Big; son of make menuconfig
further no progress
1. Just restarting and pressing shift just when Lilo starts to load gives me
an option box to load linux or linux old. Selecting either and putting in
... root=/dev/hda7 in both cases just brings me back to the first kernel
panic situation.
2. If I start out with the instalation CD and use rescue root=/dev/hda7 it
gets to starting runlevel 2 and then pauses for a very long time, but
eventually gives me a login...but only userme can login...no root! Then I
can su to root.
The problem is...I don't know what I need to modify from there, if it is
possible, to get back to the old setup or to get the new kernel loading
properly. Also, the x-windows system does not seem to have been loaded at
this point.
Best Wishes!
Mike Olds www.buddhadust.org
-----Original Message-----
From: Michael Olds [mailto:MikeOlds@pacbell.net]
Sent: Saturday, October 12, 2002 10:44 AM
To: Michael Olds; Torsten Wolny; Debian-User@Lists. Debian. Org
Subject: RE: Kernel Panic was: System is too Big; son of make menuconfig
update not very much:
I did find out how to reboot, by pressing the reset button on the box. Then
I tried using the boot floppy, which ended up in the same place (using, as
the book says: ctrl or shift did not bring me to an option where I could
insert root=/dev/hda7). I also tried a previous boot floppy which it could
not even start to read because of an invalid compression format???How can
this be it came from the previous setup? And I used the installation cd
which did allow me to pass the root=, but ended up giving me a million
errors on the way to stalling out at "beginning run level 2 and ending at
starting syslogd."
I really don't mind if I have hosed the system, I had a fair up time this go
round, but if I can get back to the old system or correctly get to the new
kernel, I would like to know how.
Best Wishes!
Mike Olds www.buddhadust.org
-----Original Message-----
From: Michael Olds [mailto:MikeOlds@pacbell.net]
Sent: Saturday, October 12, 2002 10:06 AM
To: Torsten Wolny; Debian-User@Lists. Debian. Org
Subject: Kernel Panic was: System is too Big; son of make menuconfig
OK, now I've done it!
I followed the instructions below and everything seemed to go without
problems. I installed the new kernel package also without problems (it did
seem to go very fast?) and then made a floppy disk and then rebooted to end
up on a frozen screen ending with this message:
...root fs not mounted
VFS: Cannot open root device "307" or 03:07
Please append a correct "Root=" boot option
Kernel panic: VFS: unable to mount root FS on 03:07
To what do I append the correct "Root="? (I believe this should be
Root=/dev/hda7 (the root partition?), and how? ctrl+alt+del does not start
reboot
Best Wishes!
Mike Olds www.buddhadust.org
-----Original Message-----
From: Torsten Wolny [mailto:torwo@torsten-wolny.de]
Sent: Saturday, October 12, 2002 1:37 AM
To: Michael Olds; Debian-User@Lists. Debian. Org
Subject: Re: System is too Big; son of make menuconfig
Hello,
Am Samstag, 12. Oktober 2002 04:39 schrieb Michael Olds:
> Ok, first time rebuilding the kernel so I'm not too upset it's
> going all wrong...but
> my books tell me what to do when I run make zImage and the system
> is too big: run make bzImage. But they don't tell me what to do
> when that too is too big. And how could it be too big? I use the
> M option as my yes key and I didn't select anything that I didn't
> recognize and I have a pretty stripp't down system. I get the
> message: Boot Sector 512 bytes
> System is 601 bytes after make bzImage
>
> What else can I do? Am I correct in assuming that this does not
> have anything to do with my boot partition size? Which just
> happens to be about 512MB. But I've looked, it's hardly being
> used.
>
It seems you are using the normal way to build the kernel (make
clean, make dep, make bzImage)
Try to use the debian-tools. A short description:
Install packeages bin86, libc-dev, debian-utils, make, bzip2 and
kernel-package
Then copy the config-file to your kernel-sources and run make
menuconfig. Edit the options in your way.
Then run "make-kpkg clean" in /usr/src/linux and then "make-kpkg
-revision=<SOMETHING> kernel_image". If this works without errors
you can find a new kernel... .deb in /usr/src. Install this with
"dpkg -i kernel... .deb" This should work.
> Also, I took a chance and just exited the terminal after this
> message. Am I correct in assuming nothing on my system was
> changed? I rebooted and nothing seems changed.
>
> Since my current configuration seems to be acceptable in size, is
> there a way of just using it as the basis for making changes? The
> book suggests that this be done on subsequent rebuilds, but
> doesn't say anything about using the current configuration for
> the first rebuild.
In /boot is file called config-<kernel-version>. This contains the
configuration of the installed kernel. Copy this file to
/usr/src/linux/.config and you can use it base-configuration
> Best Wishes!
> Mike Olds www.buddhadust.org
Cheers,
Torsten
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: