SEO

Hello, I just installed Slackware 9.0 on a Toshiba 320CDT with 32 mb RAM,4gb
hd. Everything works fine but I must boot from a floppy.

I get the following message when I run lilo from the command prompt:

"Warning: LINEAR is deprecated in favor of LBA32: LINEAR specifies 24-bit
disk addresses below the 1024 cylinder limit; LBA32 specifies 32-bit disk
addresses not subject to cylinder limits on systems with EDD extensions;
use LINEAR only if you are aware of its limitations.
Fatal: open /boot/message: No such file or directory "

My /etc/lilo.conf look like this:

boot= "/dev/hda1"
prompt
timeout="1200"
message=/boot/message
root=/dev/hda1
linear <<<<<<-----maybe something to do
with this parameter?
vga="771"

image="/boot/vmlinuz"
label=Linux
root="/dev/hda1"
read-only


Any clue what to do to get it boot directly from the hd?

Thanks

Conny Enström wrote:
> Hello, I just installed Slackware 9.0 on a Toshiba 320CDT with 32 mb RAM,4gb
> hd. Everything works fine but I must boot from a floppy.
>
> I get the following message when I run lilo from the command prompt:
>
> "Warning: LINEAR is deprecated in favor of LBA32: LINEAR specifies 24-bit
> disk addresses below the 1024 cylinder limit; LBA32 specifies 32-bit disk
> addresses not subject to cylinder limits on systems with EDD extensions;
> use LINEAR only if you are aware of its limitations.
> Fatal: open /boot/message: No such file or directory "
>
> My /etc/lilo.conf look like this:
>
> boot= "/dev/hda1"

this should be /dev/hda, if you want to install lilo to the MBR. right now,
lilo is installed to the superblock of /dev/hda1. that's not impossible,
but you'll need another boot loader in the MBR. better to install lilo in
the MBR, so change it to /dev/hda.

> prompt
> timeout="1200"
> message=/boot/message
> root=/dev/hda1
> linear <<<<<<-----maybe something to do with this parameter?

this is what the warning talks about, but it is not the reason why lilo
isn't installed. a warning is only a warning, and is not fatal to program
execution. (unlike an error.)

however, as this line indicates:

> Fatal: open /boot/message: No such file or directory "

your problem is that you don't have a file /boot/message. the line
'message=/boot/message' in your lilo.conf tells lilo to use this file as a
boot message. but the file isn't there, so lilo refuses to work.

in slack, the boot message is normally /boot/message.txt. check if you have
that file, and modify lilo.conf to match.

HTH

--
Joost Kremers
since when is vi an editor? a discussion on vi belongs in
comp.tools.unusable or something...

"Joost Kremers" <joostkremers@yahoo.com> skrev i meddelandet
news:slrnbl7cmg.e7r.joostkremers@j.kremers4.news.a rnhem.chello.nl...
> Conny Enström wrote:
> > Hello, I just installed Slackware 9.0 on a Toshiba 320CDT with 32 mb
RAM,4gb
> > hd. Everything works fine but I must boot from a floppy.
> >
> > I get the following message when I run lilo from the command prompt:
> >
> > "Warning: LINEAR is deprecated in favor of LBA32: LINEAR specifies
24-bit
> > disk addresses below the 1024 cylinder limit; LBA32 specifies 32-bit
disk
> > addresses not subject to cylinder limits on systems with EDD extensions;
> > use LINEAR only if you are aware of its limitations.
> > Fatal: open /boot/message: No such file or directory "
> >
> > My /etc/lilo.conf look like this:
> >
> > boot= "/dev/hda1"
>
> this should be /dev/hda, if you want to install lilo to the MBR. right
now,
> lilo is installed to the superblock of /dev/hda1. that's not impossible,
> but you'll need another boot loader in the MBR. better to install lilo in
> the MBR, so change it to /dev/hda.
>
> > prompt
> > timeout="1200"
> > message=/boot/message
> > root=/dev/hda1
> > linear <<<<<<-----maybe something to do with this
parameter?
>
> this is what the warning talks about, but it is not the reason why lilo
> isn't installed. a warning is only a warning, and is not fatal to program
> execution. (unlike an error.)
>
> however, as this line indicates:
>
> > Fatal: open /boot/message: No such file or directory "
>
> your problem is that you don't have a file /boot/message. the line
> 'message=/boot/message' in your lilo.conf tells lilo to use this file as a
> boot message. but the file isn't there, so lilo refuses to work.
>
> in slack, the boot message is normally /boot/message.txt. check if you
have
> that file, and modify lilo.conf to match.
>

It worked! Thanks, I got a red looking boot menu and lilo was booting
allright :-)

Conny

In article <slrnbl7cmg.e7r.joostkremers@j.kremers4.news.arnhe m.chello.nl>, Joost Kremers wrote:
> Conny Enström wrote:
>> Hello, I just installed Slackware 9.0 on a Toshiba 320CDT with 32 mb RAM,4gb
>> hd. Everything works fine but I must boot from a floppy.
>>
>> I get the following message when I run lilo from the command prompt:
>>
>> "Warning: LINEAR is deprecated in favor of LBA32: LINEAR specifies 24-bit
>> disk addresses below the 1024 cylinder limit; LBA32 specifies 32-bit disk
>> addresses not subject to cylinder limits on systems with EDD extensions;
>> use LINEAR only if you are aware of its limitations.
>> Fatal: open /boot/message: No such file or directory "
>>
>> My /etc/lilo.conf look like this:
>>
>> boot= "/dev/hda1"
>
> this should be /dev/hda, if you want to install lilo to the MBR. right now,
> lilo is installed to the superblock of /dev/hda1. that's not impossible,
> but you'll need another boot loader in the MBR. better to install lilo in
> the MBR, so change it to /dev/hda.

Not true. If you mark had1 as "bootable" (using fdisk, for example)
then (notwithstanding BIOS bugs) that should work fine. (It does for
me.) I started doing this after I read some article advocating this
approach. I don't remember the full rationale or the author, but I
actually like the idea of not messing with the first block of the
drive.

Cheers.

Jim

Jim Diamond wrote:
>> this should be /dev/hda, if you want to install lilo to the MBR. right now,
>> lilo is installed to the superblock of /dev/hda1. that's not impossible,
>> but you'll need another boot loader in the MBR. better to install lilo in
>> the MBR, so change it to /dev/hda.
>
> Not true. If you mark had1 as "bootable" (using fdisk, for example)
> then (notwithstanding BIOS bugs) that should work fine.

mmm, that actually makes sense. didn't know that.

--
Joost Kremers
since when is vi an editor? a discussion on vi belongs in
comp.tools.unusable or something...

Jim Diamond <jdiamond@removethis.istar.ca> wrote:
> Not true. If you mark had1 as "bootable" (using fdisk, for example)
> then (notwithstanding BIOS bugs) that should work fine. (It does for
> me.) I started doing this after I read some article advocating this

Yes, but Windows-9x will not boot anymore after this change, even through
lilo, as they NEED to have THEIR boot partition to be marked as bootable
(it is the way they determine what partition to call the C: drive).

Newer Windows versions are smarter than that so will work ok, as far
as I know.
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TWA **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

"Eef Hartman" <E.J.M.Hartman@math.tudelft.nl> skrev i meddelandet
news:bj4s69$uo$1@news.tudelft.nl...
> Jim Diamond <jdiamond@removethis.istar.ca> wrote:
> > Not true. If you mark had1 as "bootable" (using fdisk, for example)
> > then (notwithstanding BIOS bugs) that should work fine. (It does for
> > me.) I started doing this after I read some article advocating this
>
> Yes, but Windows-9x will not boot anymore after this change, even through
> lilo, as they NEED to have THEIR boot partition to be marked as bootable
> (it is the way they determine what partition to call the C: drive).
>
> Newer Windows versions are smarter than that so will work ok, as far
> as I know.
> --
>

Slackware is the only os installed so no problem for me, it works fine :-)

On 2003-09-03, Eef Hartman <E.J.M.Hartman@math.tudelft.nl> wrote:
> Jim Diamond <jdiamond@removethis.istar.ca> wrote:
>> Not true. If you mark had1 as "bootable" (using fdisk, for example)
>> then (notwithstanding BIOS bugs) that should work fine. (It does for
>> me.) I started doing this after I read some article advocating this
>
> Yes, but Windows-9x will not boot anymore after this change, even through
> lilo, as they NEED to have THEIR boot partition to be marked as bootable
> (it is the way they determine what partition to call the C: drive).

So, that would be a Good Thing, wouldn't it? :-)

Jim

In article <bj4s69$uo$1@news.tudelft.nl>, Eef Hartman wrote:
> Yes, but Windows-9x will not boot anymore after this change, even through
> lilo, as they NEED to have THEIR boot partition to be marked as bootable
> (it is the way they determine what partition to call the C: drive).

Hmmm, I am not sure about that. I think "C:" is the first DOS-known
primary partition on the BIOS 0x80 device. I don't believe the
active / bootable flag matters.

Anyway, if you are using Win9x, you might find that DOS and loadlin are
a pretty good boot manager for Linux. I think it's just as fast as LILO
(faster, depending upon how you set the delays.)
--
/dev/rob0 - preferred_email=i$((28*28+28))@softhome.net
or put "not-spam" or "/dev/rob0" in Subject header to reply