From: Peter Kundrat <kundrat@kundrat.sk>
To: mtd@infradead.org
Subject: Re: lilo kernel params failure
Date: Tue, 27 Feb 2001 22:55:23 +0100 [thread overview]
Message-ID: <20010227225523.A743@napri.sk> (raw)
In-Reply-To: <3A9B09BD.C3D3CB68@tg-embedded.com>; from dant@tg-embedded.com on Mon, Feb 26, 2001 at 08:58:21PM -0500
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
On Mon, Feb 26, 2001 at 08:58:21PM -0500, dant@tg-embedded.com wrote:
> I have been strugling with this for some time now.
>
> It looks like a failure of lilo to pass kernel params ( append="...." )
> But we have been through the code and fail to find a reason.
> this happens with the lilo-mtd in the cvs /patches area and we have
> patched 21 with the same results.
> We are using DoC 2000 with kernel 2.4.2 though this has been happening
> for months really.
> Anyone have any ideas?
I sent a patch here few months ago for lilo-mtd, i havent checked if it
got applied. Attached again, just for case.
Another option is to use lilo available from m-sys (this one is a bit newer
version if i recall correctly).
pkx
--
Peter Kundrat
peter@kundrat.sk
peter-work@kundrat.sk (a copy goes to work)
[-- Attachment #2: lilo-ebda-pkx.patch --]
[-- Type: text/plain, Size: 1628 bytes --]
diff -ur lilo.orig/lilo.h lilo/lilo.h
--- lilo.orig/lilo.h Fri Dec 4 19:55:31 1998
+++ lilo/lilo.h Sun Aug 27 02:40:46 2000
@@ -149,10 +151,12 @@
FIRSTSEG = 0x9A00
STACKSEG = 0x9000
SECONDSEG = 0x9B00 ! second stage loader segment
+PARMLINE = 0x2A00 ! parameter line construction area off.
#else
FIRSTSEG = 0x8A00
STACKSEG = 0x8000
SECONDSEG = 0x8B00 ! second stage loader segment
+PARMLINE = 0xD000 ! parameter line construction area off. (0x98000)
#endif
INITSEG = DEF_INITSEG ! we move boot here - out of the way
@@ -164,7 +168,6 @@
DFLCMD = 0x2600 ! default command line
MAP = 0x2000 ! map load area offset
KEYTABLE = 0x2800 ! keyboard translation table offset
-PARMLINE = 0x2a00 ! parameter line construction area off.
SECOND = 0x1000 ! second stage loader load address
SECOND_SS = 0xB000 ! second as seen from SS:0000
SLA_SIZE = 0x9E00 ! setup load area size
diff -ur lilo.orig/second.S lilo/second.S
--- lilo.orig/second.S Sat Dec 5 00:20:07 1998
+++ lilo/second.S Sun Aug 27 02:43:56 2000
@@ -830,9 +830,15 @@
call load1
seg es
mov CL_MAGIC_ADDR,#CL_MAGIC ! set magic number
- seg es
- mov word ptr CL_OFFSET,#PARMLINE+SECOND_SS
- ! set parameter line offset
+#ifndef LCF_LARGE_EBDA
+ seg es
+ mov word ptr CL_OFFSET,#PARMLINE+SECOND_SS
+ ! set parameter line offset
+#else
+ seg es
+ mov word ptr CL_OFFSET,#PARMLINE+SECONDSEG*16-INITSEG*16
+ ! set parameter line offset
+#endif
pop si ! restore SI
lodsw ! get flags bit map
mov bx,ax
next prev parent reply other threads:[~2001-02-27 22:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 1:58 lilo kernel params failure dant
2001-02-27 21:55 ` Peter Kundrat [this message]
2001-02-28 9:29 ` Matteo Costa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010227225523.A743@napri.sk \
--to=kundrat@kundrat.sk \
--cc=mtd@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox