Sponsored Content
Full Discussion: Hardware Upgrades..
Top Forums UNIX for Dummies Questions & Answers Hardware Upgrades.. Post 4031 by htsubamoto on Tuesday 17th of July 2001 11:25:30 AM
Old 07-17-2001
That's depends on the kernel version you have. Some kernels below 2.2.7 (I think) had to be notified by lilo about the Memory size. here's an example:

# lilo.conf
boot=/dev/hda
map=/boot/map
install=/boot/boot.b
vga=791
default=linux
keytable=/boot/us-latin1.klt
lba32
prompt
timeout=50
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label=linux
root=/dev/hda2
append=" mem=64M)"
read-only
other=/dev/fd0
label=floppy
unsafe

Note the append= line.
If linux don't recognize your entire memory, insert the append line, but the size must be exactly the size of your available physical memory, if you put less memory, you will not use all memory, if you put more, you will experience a kernel panic.

In your case put, after image=<kernel image>:
append="mem=128M)"
but only if linux refuses to recognize your memory size correctly

Regards
HTT
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

RedHat remote upgrades

Is there an easy (and safe) way to upgrade RedHat versions remotely? I know the difference between 7.2 and 7.3 is just a bunch of newer .rpm file versions. Or is there more? Do I have to boot the CD and choose upgrade? What if I'm 100 miles from the server and would like to avoid traveling there?... (1 Reply)
Discussion started by: ArkiMage
1 Replies

2. SuSE

Linux(Suse) Upgrades

Hello, Anyone out there deal with updating OS on linux servers remotely? We use Suse but like to hear what someone else does with any linux version. We have network connectivity to our remote locations but it's just a DSL connection, so some will be fast and some will be slow. Thanks for... (1 Reply)
Discussion started by: benefactr
1 Replies

3. News, Links, Events and Announcements

Solaris 10 and live upgrades

two articles related to live upgrades that i found useful and noteworthy. Solaris 10 5/08 Live Upgrade Gotcha :: Col’s Tech Stuff Solaris Live Upgrade and Patches :: Col’s Tech Stuff (0 Replies)
Discussion started by: pupp
0 Replies

4. AIX

HMC upgrades

Hey!!! Has anyone done HMC patch installation remotely? I would love to know if that would be possible. I have been doing through CD/DVD but hate to do the additional work of finding someone in the DC and sending him the CD's. I have seen the option to supply remote site. can that be helpful?... (5 Replies)
Discussion started by: balaji_prk
5 Replies

5. AIX

How can I manage redundant HMC upgrades with firmware upgrades?

Lets says I have 2 HMC's A and B, connected to a p570 managed system. Right now the firmware level of the p570 is EM320_076 and that needs to be upgraded to EM340_095. Now the HMC's are at V7R3.3 and as per the code matrix the HMC's needs to be upgraded to V7R3.4 Servicepack 2. Now my... (5 Replies)
Discussion started by: balaji_prk
5 Replies

6. AIX

Need to confirm something regarding TL upgrades

Hi everyone, My current AIX OS level is "7100-01-06-1241" and I am planning to upgrade it to " 7100-02-03 ". Can i directly upgrade it to "7100-02-03" from 7100-01-06" ? or first i need to upgrade the "7100-01-06" LPAR to TL 02 and then reboot and then upgrade it to TL 02 SP03 ? ... (4 Replies)
Discussion started by: System Admin 77
4 Replies

7. What is on Your Mind?

Update on UNIX.COM Site Upgrades (Desktop)

This post is about the "Desktop" view, not "Mobile' ... First of all, I want to thank everyone for all the great comments, error checking and feature suggestions as we modernize the site, step-by-step. Also, thank you for your patience with me when as we make the site better. So far, we... (1 Reply)
Discussion started by: Neo
1 Replies

8. What is on Your Mind?

Discussion (Thread) Tagging Upgrades

Dear All, I have made significant progress coding new discussion thread tagging features. As always, we want all users to tag thread and moderators to tag threads with relevant keywords. Moving forward, in addition to the #1 important "human tagging", we will also auto tag threads with one... (4 Replies)
Discussion started by: Neo
4 Replies
MKRESCUE(8)						      System Manager's Manual						       MKRESCUE(8)

NAME
mkrescue - make rescue floppy or CD SYNOPSIS
/sbin/mkrescue makes a bootable rescue floppy or CD using the default kernel specified in lilo.conf. DESCRIPTION
mkrescue takes its specifation for the kernel from the default image specified in /etc/lilo.conf. If the actual default is an other= spec- ification, then use the first image= specification. Any associated initial ramdisk (initrd=), and append= options will also be used. The root directory will be taken to be the current root. A bootable floppy or CD-image will be created using LILO version 22.5.5 or later. mkrescue normally requires no options, unless a CD-image is desired (--iso). OPTIONS
--append <string> Override any append= options taken from the default image. If there is any doubt about whether the lilo.conf options are correct, then specify no kernel parameters by providing the null string (--append ""). --debug Provide verbose output of the operation of mkrescue, pausing to allow the setting of internal operating parameters to be viewed. <CR> must be hit to proceed from these pauses. --device <device> Make the floppy on a device other than /dev/fd0. The floppy disk will always be made to boot on BIOS device code 0x00 (A: drive), without regard to the drive on which it is created. --fast Use a faster method of creating the boot floppy. This involves first creating a file of --size 1k blocks (default is 1440) mounted using a loopback device, creating the bootable floppy, then copying the entire file to the disk. --fs [ ext2 | msdos | minix ] Specify the type of filesystem to create on the drive. ext2 is the default, but msdos and minix allow slightly more disk sectors for really big kernels. --help Print a short usage synopsis, including a list of command options. --image <label> Specifies the label or alias of the particular image from which the append, initial ramdisk, root, keytable, and kernel information is to be taken. --initrd <filepath> and --kernel <filepath> These options, which must be used together, allow specification of an arbitrary kernel file and initial ramdisk file to be used on the created boot floppy. Be sure you know what you are doing before you use these options. If no inital ramdisk is needed with a particular kernel, then you MUST specify --initrd "", meaning a null pathname. --install [ text | menu ] Allows overriding the default human interface used with the rescue bootloader (configuration file "install=" option). text is the default on 1.2MB and 1.44MB floppy disks, and menu is the default on 2.88MB floppies and HD emulation on CD-R media. --iso Create an ISO-9660 bootable CD image (El Torito Format) suitable for burning to a CD-R or CD-RW. The --device specification defaults to the filename rescue.iso, and the --size defaults to 2880. A utility such as "wodim" may be used to burn the ISO file to a recordable CD medium. With this ISO option, the --size HD option is allowed. --nocompact For faster kernel loading from a floppy, LILO map compaction is normally enabled. This option will disable map compaction by omit- ting the lilo -c switch. --noformat Suppresses creation of a new filesystem on the boot floppy. This option may be used ONLY when you know that the floppy you will be writing upon is formatted with the same filesystem as specified by --fs XXX (default is ext2). --root <device> Specify the root filesystem for the kernel on the boot floppy. The currently mounted root is taken as the default specification. --size [ 1440 | 1200 | 2880 | HD ] The default floppy disk size is 1440, meaning a 1.44MB floppy. When --iso is specified, the default size is 2880. Allowed specifi- cations are 1200, 1440, or 2880, meaning a 1.2MB, 1.44MB or 2.88MB floppy, respectively. No other floppy disk sizes are supported. The HD specification, meaning "hard disk", may only be used with the --iso option, to indicate a 16MB hard disk is to be generated for emulation. This allows for very large kernel/initial ramdisk combinations on CD-R. The hard disk image is created using loop- back devices /dev/loop0 and /dev/loop1, which must be free to utilize this size option. --version Print the version number of mkrescue, then terminate. SEE ALSO
cdrecord(1), dd(1), wodim(1), lilo.conf(5), lilo(8), mkfs(8), mkinitrd(8), mkisofs(8), mount(8) 6 Mar 2011 MKRESCUE(8)
All times are GMT -4. The time now is 07:30 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy