One more comment: Although I don't use kernel 2.6, when I use kernel 2.4, ext3.o and jdb.o go in the initrd file. To see if you have them there, copy /boot/initrd-2.6.11.2k5.img into, say, initrd.gz. Then do "gunzip initrd.gz; mkdir tmp; mount -o loop initrd tmp; ls tmp/lib". You should see files ext3.o and jbd.o. If they're not there, get them there somehow or compile the kernel with them in it. Steven Yellin On Thu, 2 Jun 2005, Steven J. Yellin wrote: > You show the complaint "mount: error 19 mounting ext3". The > "RETURN CODES" shown in "man mount" say, since 19=1+2+16, that the > errors were > 1 incorrect invocation or permissions > 2 system error (out of memory, cannot fork, no more loop > devices) > 16 problems writing or locking /etc/mtab > I would expect errors 1 and 2 for / to cause 16. Maybe you could > change /etc/fstab to mount / as ext2 and/or maybe your new kernel > doesn't know about ext3. Verify that you have > /lib/modules/2.6.11.2k5/kernel/fs/ext3/ext3.o > and /lib/modules/2.6.11.2k5/kernel/fs/jbd/jbd.o > > Steven Yellin > > On Thu, 2 Jun 2005 Raja.Saleru@xxxxxxxxxxxxxxx wrote: > > > Thanks for the reply. > > > > I downloaded the latest kernel 2.6.11.11 and I followed the same step > > with > > make modules > > and > > make modules_install > > then I did > > > > mkinitrd /boot/initrd-2.6.11.2k5.img 2.6.11.2k5 > > the lilo.conf file is > > > > ---------------------------------------------------------- > > prompt > > timeout=50 > > default=DOS > > boot=/dev/hda > > map=/boot/map > > install=/boot/boot.b > > message=/boot/message > > lba32 > > > > image=/boot/vmlinuz-2.6.11.2k5 > > label=2.6.11.2k5 > > initrd=/boot/initrd-2.6.11.2k5.img > > read-only > > append="root=LABEL=/" > > > > image=/boot/vmlinuz-2.4.20-8 > > label=linux > > initrd=/boot/initrd-2.4.20-8.img > > read-only > > append="root=LABEL=/" > > > > other=/dev/hda1 > > optional > > label=DOS > > ----------------------------------------------------------- > > > > now I did > > lilo -v > > > > after rebooting, I am getting the following error > > > > mount: error 19 mounting ext3 > > pivotroot: pivot_root (/sysroot, /initrd) failed: 2 > > umount /initrd /proc failed :2 > > kernel panic - not syncing : no init found, try passing "init = option" to > > kernel > > > > what would be the error in this ? > > > > - Raja S > > > > > > > > > > > > > > "Steven J. Yellin" <yellin@xxxxxxxxxxxxxxxxx> > > Sent by: shrike-list-bounces@xxxxxxxxxx > > 06/01/2005 11:00 PM > > Please respond to "Discussion of Red Hat Linux 9 (Shrike)" > > > > > > To: "Discussion of Red Hat Linux 9 (Shrike)" <shrike-list@xxxxxxxxxx> > > cc: > > Subject: Re: help on frame buffer > > > > > > Maybe you need to do > > make modules > > make modules_install > > It looks like you don't have an initrd=... line in lilo.conf for your > > previous kernel, but if you do, you should make one for this kernel. > > > > Steven Yellin > > > > On Wed, 1 Jun 2005 Raja.Saleru@xxxxxxxxxxxxxxx wrote: > > > > > Hi, > > > > > > I am using redhat linux 9, I want to enable frame buffer support. > > > I followed the following steps.. > > > > > > > > > 1. Make sure that you have the Linux kernel source code in > > /usr/src/linux/. > > > 2. Log in as root and cd /usr/src/linux > > > 3. Configure the kernel: > > > Run: > > > make menuconfig > > > > > > Select "Code maturity level options" and set "Prompt for development > > > and/or incomplete code/drivers". > > > Then select "Console drivers" set "Support for frame buffer devices" to > > > built-in (even if it says EXPERIMENTAL). Then configure the driver. Most > > > modern graphics cards can use the "VESA VGA graphics console"; use that > > or > > > a driver that specifically matches your video card. Finally enable > > > "Advanced low level driver options" and make sure that 16 and 32 bpp > > > packed pixel support are enabled. > > > When you are finished, chose exit and save. > > > 4. Compile the kernel > > > First do: > > > make dep > > > > > > then: > > > make bzImage > > > > > > The new kernel should now be in arch/i386/boot/bzImage > > > 5. Copy the kernel to the boot directory: > > > cp arch/i386/boot/bzImage /boot/linux.vesafb > > > > > > 6. Edit /etc/lilo.conf > > > IMPORTANT: Keep a backup of /etc/lilo.conf, and have a rescue disk > > > available. If you make a mistake at this stage, the machine may not > > boot. > > > The file /etc/lilo.conf specifies how the system boots. The precise > > > contents of the file varies from system to system, this is one example: > > > boot = /dev/hda3 > > > delay = 30 > > > image = /boot/vmlinuz > > > root = /dev/hda3 > > > label = Linux > > > read-only # Non-UMSDOS filesystems should be mounted read-only for > > > checking > > > other=/dev/hda1 > > > label=nt > > > table=/dev/hda > > > > > > IMPORTANT: Keep a backup of /etc/lilo.conf, and have a rescue disk > > > available. If you make a mistake here, the machine may not boot. > > > Make a new "image" section that is a copy of the first one, but with > > image > > > = /boot/linux.vesafb and label = Linux-vesafb. Place it just above the > > > first image section. > > > Add a line before the image section saying 'vga = 791'. (Meaning > > 1024x768, > > > 16 bpp.) > > > With the above example, lilo.conf would now be: > > > boot = /dev/hda3 > > > delay = 30 > > > vga = 791 > > > image = /boot/linux.vesafb > > > root = /dev/hda3 > > > label = Linux-vesafb > > > read-only # Non-UMSDOS filesystems should be mounted read-only for > > > checking > > > image = /boot/vmlinuz > > > root = /dev/hda3 > > > label = Linux > > > read-only # Non-UMSDOS filesystems should be mounted read-only for > > > checking > > > other=/dev/hda1 > > > label=nt > > > table=/dev/hda > > > > > > Do not change any lines in the file; just add new ones. > > > 7. Run lilo > > > To make the new changes take effect, run the lilo program: > > > lilo > > > > > > 8. Reboot the system > > > > > > -------------------------------------------------------------- > > > > > > after rebooting, the kernel is not booting... > > > it says kernel version mismatch and kernel panic, mention the correct > > > root. > > > > > > can anybody help in this ? > > > > > > > > > Raja Saleru > > > LARSEN & TOUBRO INFOTECH LIMITED > > > Communications & Embedded Systems > > > No.4, Service Road, > > > Domlur Layout, > > > Bangalore - 560 071 > > > INDIA > > > Tel : +91-80-25350510/512 Extn : 106 > > > Mobile : +91- > > > Fax : +91-80-25350495 > > > > > > > > > ______________________________________________________________________ > > > > -- > > Shrike-list mailing list > > Shrike-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/shrike-list > > > > ______________________________________________________________________ > > > > > > > > > > ______________________________________________________________________ > > -- > Shrike-list mailing list > Shrike-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/shrike-list > -- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
