I can't find any of this in any log file, so I typed the last few lines in manually. The first error I see is when mount returns error 6. From these errors, it looks like it has trouble mounting root with ext3. Ext3 is in the config as a module (I attached .config). Ext2 is in the config as part of the kernel. ... Freeing initrd memory. 107k freed VFS: Mounted root (ext2 filesystem). Red Hat nash version 3.3.10 starting Loading ext3 module Mounting /proc filesystem Creating root device Mounting root filesystem mount: error 6 mounting ext3 pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 Freeing unused kernel memory. 124k freed Kernel panic: No init found. Try passing init= option to kernel. ----- Original Message ----- From: "David Hawkins" <dwh@ovro.caltech.edu> To: "Mark Hamblin" <MarkHamblin@cox.net>; "Bernd Petrovitsch" <bernd@gams.at>; <kernelnewbies@nl.linux.org> Sent: Wednesday, November 13, 2002 12:44 PM Subject: RE: Trying to build 2.5.46 > > The messages may have been logged in /var/log/messages. > > The normal kernel build process I use is something > like: > > cd /usr/src/linux-<version> > > make xconfig > edit Makefile to add new extension to kernel name > make clean > make dep > make bzImage > make modules > > cp arch/i386/boot/bzImage /boot/vmlinuz-<version> > cp System.map /boot/System.map-<version> > > make modules_install > > mkinitrd /boot/initrd-<version>.img <version> > > edit /boot/grub/grub.conf > > I'm not a kernel building guru myself, but maybe > the order here is required. > > Dave > > > > > -----Original Message----- > > From: Mark Hamblin [mailto:MarkHamblin@cox.net] > > Sent: Wednesday, November 13, 2002 11:12 AM > > To: David Hawkins; Bernd Petrovitsch; kernelnewbies@nl.linux.org > > Subject: Re: Trying to build 2.5.46 > > > > > > I did the mkinitrd to create a new image (mkinitrd /boot/initrd-2.5.46.img > > 2.5.46). I then edited the initrd accordingly in grub.conf. As for my > > setup, I know my primary controller is indeed a Promise SCSI/IDE > > controller. > > And lines 13-16 do represent my original working configuration. When I > > rebooted, I got the same error as before. There is some > > information leading > > up to this that may also be useful. Are these messages logged somewhere? > > If so, I can post that and that might help. Also, I was playing > > with a lot > > of configuration options without really knowing what I was doing, so is it > > possible I screwed up something there? > > > > > > ----- Original Message ----- > > From: "Bernd Petrovitsch" <bernd@gams.at> > > To: <kernelnewbies@nl.linux.org> > > Sent: Wednesday, November 13, 2002 10:53 AM > > Subject: Re: Trying to build 2.5.46 > > > > > > > [ fixed TOFU quoting ] > > > > > > "Usman S. Ansari" <uansari@yahoo.com> wrote: > > > >--- Bernd Petrovitsch <bernd@gams.at> wrote: > > > >> "Mark Hamblin" <MarkHamblin@cox.net> wrote: > > > >> >13 title Red Hat Linux (2.4.18-3) > > > >> >14 root (hd0,0) > > > >> >15 kernel /vmlinuz-2.4.18-3 ro root=/dev/hde2 > > > >> >16 initrd /initrd-2.4.18-3.img > > > >> >17 title Red Hat Linux (2.5.46) > > > >> >18 root (hd0,0) > > > >> >19 kernel /bzImage-2.5.46 ro root=/dev/hde2 > > > >> >20 initrd /initrd-2.4.18-3.img > > > >> > > > > >> >I added lines 17-20. Note that I use bzImage instead of > > vmlinuz. I'm > > not > > > >> >sure about that. I also don't know if I should modify the initrd > > line. > > > >> > > > >> Line 20 as of above is definitely wrong. Either you create an initrd > > > >> for your kernel version or (which is probably the simpler thing) is > > > >> compile all drivers statically into kernel which are necessary to > > > >> mount / (the root filesystem), i.e. usually the IDE or SCSI driver > > > >> and the filesystem driver (ext2, ext3, or whatever) and delete line > > > >> 20 from above. > > > > > > >On line 15 and 19, are you sure it is /dev/hde, which means > > that (correct > > me i > > > >f wrong), your > > > > > > I assumed line 13-16 is the original working boot configuration. > > > > > > >harddisk is 5th ide device on your system. Usually > > motherboards only have > > supp > > > >ort for 4 ide device. > > > > > > Actually I have here a motherboard (Asus A7V) which a primary VIA IDE > > > controller and a secondary/external/"SCSI" Promise IDE controller. > > > So yes, having hda-hdh is actually quite possible. > > > > > > Bernd > > > > > > -- > > > Bernd Petrovitsch Email : bernd@gams.at > > > g.a.m.s gmbh Fax : +43 1 205255-900 > > > Prinz-Eugen-Straße 8 A-1040 Vienna/Austria/Europe > > > LUGA : http://www.luga.at > > > > > > > > > -- > > > Kernelnewbies: Help each other learn about the Linux kernel. > > > Archive: http://mail.nl.linux.org/kernelnewbies/ > > > FAQ: http://kernelnewbies.org/faq/ > > > > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ >
Attachment:
.config
Description: Binary data
