RE: [Netstation-general] lpp

[Miles R. <mr...@we...>]

if you don't want supermount support its pretty easy, if you want super
mount support then there is about 30ish patches you need to apply in a
certain order to a base 2.4.18 kernel.

you should be able to do this without to many hassles as long as you know
how to compile a kernel.  I can send you the required patches if you want, +
a script which will apply them, but I've since worked out that I think it
will either work or it won't, mandrake creates the boot method at
installation time, I don't think it autodetects for the vesa type when
booting, but at install (needs to be vesa 2),  some modern computers we have
don't even work with the lpp patch.  so I don't really recommend it.

-----Original Message-----
From: Jim Van Eeckhoutte [mailto:ji...@va...]
Sent: Wednesday, 10 July 2002 06:31
To: net...@li...; Miles Roper
Subject: RE: [Netstation-general] lpp


You wouldnt happen to have a mini howto for this?
---------- Original Message ----------------------------------
From: "Miles Roper" <mr...@we...>
Date:  Thu, 4 Jul 2002 13:44:51 +1200

>Hi All,
>
>Well I got lpp working with a kernel image (including supermount).
However,
>doesn't seem to work on many machines, gives a error message about
>unsupported display or something.  I know mandrake Linux has a nice way of
>either using a image overlay if it can, otherwise you see the text.  I
might
>do some investigation about this, as I'm using the mandrake kernel anyhow
>for supermount support.  If you have any further ideas about this let me
>know :o)
>
>Ideally, what I would like is lpp to work if it could, if it doesn't, then
>just boot as normal.  Ideas?
>
>Cheers
>
>Miles
>
>-----Original Message-----
>From: Paul Whittaker [mailto:pa...@hy...]
>Sent: Tuesday, 2 July 2002 07:04 p.m.
>To: Miles Roper
>Cc: net...@li...
>Subject: Re: [Netstation-general] lpp
>
>
>> Just looking at lpp, how can we do this.  I'm fine with applying the
>patches
>> etc... But in the install instructions it says to edit the lilo config
>file
>> and add in:
>> 
>>  vga=0x301
>>  append="console=/dev/tty2 CONSOLE=/dev/tty2"
>> 
>> We obviously aren't using lilo, I'm using mknbi (for the nbi image as
>that's
>> what I'm using).  The append line is fine, you can do this with mknbi,
>> however the vga line is a problem.
>> 
>> Anyone have an idea how to do this?
>
>Despite what the doco says, LILO really has nothing to do with it - it's
>a Linux kernel parameter.  There are several ways you can set this:
>
>1) You can add the vga=0x301 to your mknbi --append string also (might
>need to use vga=769 instead, there's a lot of unresolved FUD about
>whether or not hexidecimal is accepted (I suspect it has been for
>years)).
>
>2) You can use vidmode (or rdev -v) to tag the bzImage file with the
>appropriate value (prior to running mknbi), ie. "rdev -v bzImage 769".
>
>3) You can use the DHCP 129 option to pass kernel arguments (including
>vga=0x301) to the Etherboot ROM in the DHCP response, provided that
>option 128 is also set to the binary string e4:45:74:68:00:00
>(hexidecimal).  DHCP options 128 (byte array or string) and 129 (string)
>are non-standard and must be user-defined; the way you define these
>depends upon which DHCP implementation you are using.
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>No, I will not fix your computer.
>http://thinkgeek.com/sf
>_______________________________________________
>Netstation-general mailing list
>Net...@li...
>https://lists.sourceforge.net/lists/listinfo/netstation-general
>