Re: /etc/lilo.conf and system.map mismatches -- my syntax ?
> An unidentified someone repsonded to the original question:
> > Try putting the map=... Line in the specific to kernel section.
Theodore Knab wrote:
[snip]
I think what the response at the top refers to is removing this line:
> map=/boot/map
and placing separate map= lines in *EACH* of the image= sections
below: (Making sure the kernel versions match in each section. )
> #2nd build try
> #smp himem xfs
> image=/boot/vmlinuz-2.4.19-xfs2
> label=Linux
> read-only
--> map=/boot/map-{kernel-version}
> #first build try
> #smp himem xfs
> image=/boot/vmlinuz-2.4.19
> label=Linux_older
> read-only
--> map=/boot/map-{kernel-version}
> #smp himem xfs
> #high mem with io stuff
> image=/boot/vmlinuz-2.4.22
> label=Linux_22_notest
> read-only
--> map=/boot/map-{kernel-version}
> image=/vmlinuz.old
> label=LinuxOLD
> read-only
> optional
--> map=/boot/map-{kernel-version}
However, a recent woody install I did with the 2.2 kernel, and later
installed 2.4, only seems to have the one map= line- and IIRC both
kernels boot cleanly. It is NOT an SMP machine however.
HTH,
-kgd
--
"Sendmail administration is not black magic. There are legitimate
technical reasons why it requires the sacrificing of a live chicken."
- Unknown
Re: /etc/lilo.conf and system.map mismatches -- my syntax ?
> An unidentified someone repsonded to the original question:
> > Try putting the map=... Line in the specific to kernel section.
Theodore Knab wrote:
[snip]
I think what the response at the top refers to is removing this line:
> map=/boot/map
and placing separate map= lines in *EACH* of the image= sections
below: (Making sure the kernel versions match in each section. )
> #2nd build try
> #smp himem xfs
> image=/boot/vmlinuz-2.4.19-xfs2
> label=Linux
> read-only
--> map=/boot/map-{kernel-version}
> #first build try
> #smp himem xfs
> image=/boot/vmlinuz-2.4.19
> label=Linux_older
> read-only
--> map=/boot/map-{kernel-version}
> #smp himem xfs
> #high mem with io stuff
> image=/boot/vmlinuz-2.4.22
> label=Linux_22_notest
> read-only
--> map=/boot/map-{kernel-version}
> image=/vmlinuz.old
> label=LinuxOLD
> read-only
> optional
--> map=/boot/map-{kernel-version}
However, a recent woody install I did with the 2.2 kernel, and later
installed 2.4, only seems to have the one map= line- and IIRC both
kernels boot cleanly. It is NOT an SMP machine however.
HTH,
-kgd
--
"Sendmail administration is not black magic. There are legitimate
technical reasons why it requires the sacrificing of a live chicken."
- Unknown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: /etc/lilo.conf and system.map mismatches -- my syntax ?
I have a 'map=' parameter, but when I use 2 kernels of the same stock as in the full lilo.conf below the wrong system.map file is being loaded. For example, it seems that the xfs kernel loads the system-2.4.10 system map file rather than the one I want it to load, which is the '/boot/system-2.4.19-xfs2' file. Is my syntax wrong ? /boot/system-2.4.19 /boot/system-2.4.19-xfs2 System.map-2.2.19 System.map-2.4.19-xfs2 System.map-2.4.22 > Try putting the map=... Line in the specific to kernel section. > > " map=/boot/map " > Is this the way it looks in your lilo.conf file? > Here is a copy of my lilo.conf without the the comments. lba32 boot=/dev/sda1 root=/dev/sda5 install=/boot/boot.b map=/boot/map timeout=100 delay=100 prompt vga=normal default=Linux #2nd build try #smp himem xfs image=/boot/vmlinuz-2.4.19-xfs2 label=Linux read-only #first build try #smp himem xfs image=/boot/vmlinuz-2.4.19 label=Linux_older read-only #smp himem xfs #high mem with io stuff image=/boot/vmlinuz-2.4.22 label=Linux_22_notest read-only image=/vmlinuz.old label=LinuxOLD read-only optional -- -- Ted Knab Chester, MD 21619 -- 940216d6021602a41607166696c656c202778696368602d65616e637 02940226c696e646c69702c6f667560256675627478696e67602a416 0716e6563756e2a0
Re: /etc/lilo.conf and system.map mismatches -- my syntax ?
I have a 'map=' parameter, but when I use 2 kernels of the same stock as in the full lilo.conf below the wrong system.map file is being loaded. For example, it seems that the xfs kernel loads the system-2.4.10 system map file rather than the one I want it to load, which is the '/boot/system-2.4.19-xfs2' file. Is my syntax wrong ? /boot/system-2.4.19 /boot/system-2.4.19-xfs2 System.map-2.2.19 System.map-2.4.19-xfs2 System.map-2.4.22 > Try putting the map=... Line in the specific to kernel section. > > " map=/boot/map " > Is this the way it looks in your lilo.conf file? > Here is a copy of my lilo.conf without the the comments. lba32 boot=/dev/sda1 root=/dev/sda5 install=/boot/boot.b map=/boot/map timeout=100 delay=100 prompt vga=normal default=Linux #2nd build try #smp himem xfs image=/boot/vmlinuz-2.4.19-xfs2 label=Linux read-only #first build try #smp himem xfs image=/boot/vmlinuz-2.4.19 label=Linux_older read-only #smp himem xfs #high mem with io stuff image=/boot/vmlinuz-2.4.22 label=Linux_22_notest read-only image=/vmlinuz.old label=LinuxOLD read-only optional -- -- Ted Knab Chester, MD 21619 -- 940216d6021602a41607166696c656c202778696368602d65616e637 02940226c696e646c69702c6f667560256675627478696e67602a416 0716e6563756e2a0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RE: /etc/lilo.conf and system.map mismatches
Try putting the map=... Line in the specific to kernel section. " map=/boot/map " Is this the way it looks in your lilo.conf file? Hope this does the trick. Eddy Petrisor
RE: /etc/lilo.conf and system.map mismatches
Try putting the map=... Line in the specific to kernel section. " map=/boot/map " Is this the way it looks in your lilo.conf file? Hope this does the trick. Eddy Petrisor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
/etc/lilo.conf and system.map mismatches
I was wondering if someone knew how to avoid system.map mismatch errors when building 2 or more kernels from the same version. Could someone look at my inserted the lilo.conf and file names and tell me if I have some type of formatting error ? The kernel documention recommends that SMP users compile 2 kernels. The documentation recommends that one contains SMP support while the other should be in-case SMP does not work with the hardware. Reference from $my-kernel/Documentation/smp.txt: If you are using LILO, it is handy to have both SMP and non-SMP kernel images on hand. Edit /etc/lilo.conf to create an entry for another kernel image called "linux-smp" or something. Like the SMP recommendation, when I compile new stuff in I build a kernel without the extra modules, just in-case. For example, I have an xfs-kernel and a non xfs kernel. The last time I built 2 kernels of the same version I got system map mismatch errors after running system commands like ps. Is there something wrong with the file format I am using for my kernel ? My /etc/lilo.conf looks like this: lba32 boot=/dev/sda1 root=/dev/sda5 install=/boot/boot.b map=/boot/map timeout=100 delay=100 prompt vga=normal default=Linux image=/boot/vmlinuz-2.4.19-xfs2 label=Linux read-only image=/boot/vmlinuz-2.4.19 label=failsafe read-only My files boot partition looks for this 2.4.19 kernel looks like this: /boot/vmlinux-2.4.19 /boot/System.map-2.4.19 /boot/vmlinuz-2.4.19-xfs /boot/System.map-2.4.19-xfs -- -- Ted Knab Chester, MD 21619 -- 940216d6021602a41607166696c656c202778696368602d65616e637 02940226c696e646c69702c6f667560256675627478696e67602a416 0716e6563756e2a0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
/etc/lilo.conf and system.map mismatches
I was wondering if someone knew how to avoid system.map mismatch errors when building 2 or more kernels from the same version. Could someone look at my inserted the lilo.conf and file names and tell me if I have some type of formatting error ? The kernel documention recommends that SMP users compile 2 kernels. The documentation recommends that one contains SMP support while the other should be in-case SMP does not work with the hardware. Reference from $my-kernel/Documentation/smp.txt: If you are using LILO, it is handy to have both SMP and non-SMP kernel images on hand. Edit /etc/lilo.conf to create an entry for another kernel image called "linux-smp" or something. Like the SMP recommendation, when I compile new stuff in I build a kernel without the extra modules, just in-case. For example, I have an xfs-kernel and a non xfs kernel. The last time I built 2 kernels of the same version I got system map mismatch errors after running system commands like ps. Is there something wrong with the file format I am using for my kernel ? My /etc/lilo.conf looks like this: lba32 boot=/dev/sda1 root=/dev/sda5 install=/boot/boot.b map=/boot/map timeout=100 delay=100 prompt vga=normal default=Linux image=/boot/vmlinuz-2.4.19-xfs2 label=Linux read-only image=/boot/vmlinuz-2.4.19 label=failsafe read-only My files boot partition looks for this 2.4.19 kernel looks like this: /boot/vmlinux-2.4.19 /boot/System.map-2.4.19 /boot/vmlinuz-2.4.19-xfs /boot/System.map-2.4.19-xfs -- -- Ted Knab Chester, MD 21619 -- 940216d6021602a41607166696c656c202778696368602d65616e637 02940226c696e646c69702c6f667560256675627478696e67602a416 0716e6563756e2a0
