01-12-2013
I did switch to a generic kernel, and the OS is booted fine (I had to add an initrd, besides). But lilo's menu screen shows garbage. Everything in the screen looks well save for a letter U printed within the red box. At this time, lilo is waiting keyboard input, I mean lilo has the control (of course lilo calls some BIOS routines). So, what has the kernel to do with all this? How can the fact of having changed the kernel produce this effect? Something is wrong in the code in the MBR and the other sectors that contain lilo's bootloader. Is there a way to check this code? Or check the BIOS?
---------- Post updated at 03:06 AM ---------- Previous update was at 02:18 AM ----------
I think the letter U has been printed by lilo as an indicator, but I do not know what it means. The red box menu has two entries, 'slack14' and 'xp'. The 'U' is beside 'slack14'. Does anybody know it's meaning?
10 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
Information on current kernel development status & Compatibality Status. (0 Replies)
Discussion started by: killerserv
0 Replies
2. SCO
I tried to add ppp on a serial line tty1b and I relink the kernel. Now, I would like to boot from the previous kernel because I lost the connexion for the others terminal (serial lines) too.
I would appreciate any help. (3 Replies)
Discussion started by: pacctono
3 Replies
3. Programming
Hello All,
Background
========
I am creating a virtual appliance console for a software stack on VMware ESXi. I am using Centos 5.x as the Linux distro (Guest OS). I have created a ncurses based application that does the user authentication and present him with some basic controls to do basic... (2 Replies)
Discussion started by: ku@ntum
2 Replies
4. BSD
Salamo Alikom after recompilation my kernel does not boot and display msg said : enter full path to bash : /bin/sh i try fsck -r ,fsck -y but the problem is steel . my make.conf : PERL_VER=5.8.8 OVERRIDE_LINUX_BASE_PORT=f8 PERL_VERSION=5.8.8 MODULES_OVERRIDE = linux acpi accf_http pccard msdosfs... (1 Reply)
Discussion started by: SIFE
1 Replies
5. UNIX for Advanced & Expert Users
Hi all,
I have four (4) different UNIX flavours and I want to know whether the following commands are correct with respect to wanting to check on what are my current kernel parameter settings.
I just want to clear the doubts hanging over my head whether the commands below are the right ones... (2 Replies)
Discussion started by: newbie_01
2 Replies
6. Solaris
Is there any link/tutorial on loading Solaris kernel modules at boot time?? (0 Replies)
Discussion started by: unisolin
0 Replies
7. UNIX for Advanced & Expert Users
how to display pid and other parameters of current process in linux platform ?
i know it can be done through a linux commmand ps -F
but i want it done through kernel program
thanks in advance (1 Reply)
Discussion started by: vaibhavkorde
1 Replies
8. UNIX for Dummies Questions & Answers
I compiled new kernel in linux 10.04 called linux-2.6.26.8-xenomai, it runs alongside the other kernel, but when I want to boot it I get an error message saying:
Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/sda5 does not exist.
After making the modules and headers
I made the... (4 Replies)
Discussion started by: mdop
4 Replies
9. Ubuntu
Hello Everyone,
First of all, I highly appreciate all Linux forum members and whole Linux community. http://forums.linuxmint.com/images/smilies/icon_wink.gif. I wish you the best for all of you !
I will try to be short and concise: I am using Linux Mint 10 for 2 months on 2 ws, and all went... (3 Replies)
Discussion started by: cdt
3 Replies
10. Linux
Hi everyone,
I am trying to prevent the ehci_hcd kernel module to load at boot time.
Here's what I've tried so far:
1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here):
2) Blacklisted the module by adding the following string to
3) Tried to blacklist the module... (0 Replies)
Discussion started by: gacanepa
0 Replies
LEARN ABOUT REDHAT
lvmcreate_initrd
LVMCREATE_INITRD(8) System Manager's Manual LVMCREATE_INITRD(8)
NAME
lvmcreate_initrd - create an initial ramdisk to boot with root on a logical volume
SYNOPSIS
lvcmreate_initrd [-i|--iop IOP] [-D|--devfs] [-v|--verbose] [-V|--version] [KernelVersion]
DESCRIPTION
lvmcreate_initrd creates a new compressed initial ramdisk /boot/initrd-lvm-KernelVersion.gz. The initial ramdisk contains all necessary
binaries, shared libraries and a linuxrc file to switch to a logical volume based root filesystem. To build an initial ramdisk for a ker-
nel other than the one currently running add the KernelVersion parameter (e.g. lvmcreate_initrd 2.3.25) on the command line.
OPTIONS
-h, --help
Print a usage message on standard output and exit.
-i, --iop IOP
Specify the LVM kernel IOP version if you are using wrapper scripts in /sbin. This is only necessary if you are building an initrd
for a kernel other than the current one, and you have tools for multiple IOP versions installed.
-D, --devfs
Force the use of devfs when building the initrd. lvmcreate_initrd by default probes for devfs by checking for /dev/.devfsd, which
is created by devfsd when it is running. This option will force lvmcreate_initrd to do this, when devfsd is not currently running.
-v, --verbose
Gives verbose runtime information about the creation of the ram disk image.
-V, --version
Print version number and exit successfully.
The necessary actions to change your system into a "root on logical volume" one are:
Create a small (~20MB) partition which is BIOS reachable to hold the /boot filesystem (if you already have a small partition based root
filesystem this can be used instead). If you want to boot standalone from this partition in an emergency, copy all the necessary binaries
and libraries to that filesystem as well and create a corresponding /etc/lilo.conf entry. In order to be able to edit lilo.conf when booted
standalone, you should move /etc/lilo.conf to /boot/lilo.conf and create a symbolic link to it in /etc. This is not needed if you have a
boot/root floppy which contains the LVM binaries and the library.
Create all logical volumes you need (for root, usr, opt etc.), create filesystems in them, mount them and transfer all files from the par-
tition based filesystems into the logical volume based ones.
Set up your /etc/lilo.conf with a boot configuration like:
image = /boot/vmlinuz
initrd = /boot/initrd-lvm-KernelVersion.gz
root = /dev/YourVG/YourRootLV
label = rootonlv
append = 'ramdisk_size=8192'
Replace YourVG and YourRootLV by your actual volume group and root logical volume names. You also need to change the ramdisk size to be at
least as large as that reported while lvmcreate_initrd is run. If you have enough memory, it is OK if the ramdisk size in /etc/lilo.conf
is larger than what lvmcreate_initrd reports (the memory is freed after booting). Also, your /etc/fstab in the root logical volume should
contain entries for the root LV, and the boot partition, along with any other LVs you have configured:
/dev/YourVG/YourRootLV / ext2 defaults 0 1
/dev/YourBootPartition /boot ext2 defaults 0 2
/dev/YourVG/YourUsrLV /usr ext2 defaults 0 3
/dev/YourVG/YourOptLV /opt ext2 defaults 0 4
etc.
You can use other supported filesystem types as well (e.g. reiserfs) if you have support for those in your kernel. Run lilo, reboot and
try...
The partitions containing the former /usr, /opt etc. filesystems can now be used as physical volumes. Use pvcreate(8) to turn them into
PVs and then use vgextend(8) to add them to e.g. YourVG.
DIAGNOSTICS
lvcmcreate_initrd returns 0 for success. 1 is returned in all other cases.
SEE ALSO
lilo(8), lilo.conf(5), fstab(5), lvm(8), pvcreate(8), vgextend(8), lvcreate(8), vgcreate(8)
AUTHOR
Heinz Mauelshagen <Linux-LVM@Sistina.com>
Heinz Mauelshagen LVM TOOLS LVMCREATE_INITRD(8)