-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[crosspostet because of increasing frustation]

There are days i just hate...

Looked like a quick'n easy- set up old P1-133 with slackware9.1, cli only.
Usually a thing of mere minutes (not counting installation process itself)
if nothing goes wrong. Yes, if.

Problem:

System is installed, runs fine as far as i can tell after 5 days without
doing actual work with it.
But- Lilo doesn't seem to work, or the bios doesn't seem to work as has to
be expecetd, or what the fuck ever.

I installed lilo as i do it always in the mbr of the first (and in this case
only) harddisk. No error reportings, all looks clear. But after POST i only
get "Insert bootable media in the aprobiate drive" That's it, nothing more.
Re-installed lilo some times with the same result (and yes, i double-
triple- and whatever checked the lilo.conf *g*).
Used the superblock for my next tries, same result. One small difference- i
get the same "Insert bootable media in the aprobiate drive", but after 2 or
3 retries i get "Li 99 99 99 99l" Somewhere far far in the back of my head
i think to remember that a message like "Li 01 01 01 01 lo" sometimes
occured when one switched the kernel images without re-installing lilo
after. But sure as hell i didn't change the kernel, and nobody said
anything about this happening after some failed retries.
Only way i get that box to boot is by floppy, and that isn't exactly what i
had in mind.

System Specs :

Dell Dimension XPS P133S (P1 133MHz)
32MB RAM
hda -> WD Caviar 850MB
hdc -> IDE CD-ROM
BIOS -> A10
(Sidenote on the BIOS- at first that sucker didn't even boot from CD.
Original BIOS was Version A00, updated to A10 (most recent) to get (with
some other shit) ElTorrito support)

Slackware 9.1, Lilo 22.5.7.2

****************

Any ideas what's wrong here, and how i can get it to boot from hd?

- --
- -=SilliCone=-

"as appealing as it might seem, it is impossible to patch or upgrade users"
<Security Warrior>


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFBbV0nZa9iGSXQ4MIRAq9jAJ4iynj0UTg42IYqkzOIu0 fMbdnGjQCfWbaC
XicMjUbOcoGKpWUsOo6wnGA=
=/gNi
-----END PGP SIGNATURE-----

SilliCone <noone@nowhere.net> writes:

> [crosspostet because of increasing frustation]

No, crossposted to increase created frustration.

--
Måns Rullgård
mru@mru.ath.cx

(NOTE: I'm following up to alt.os.linux.slackware only; This seems the
most appropriate group for this message)

SilliCone wrote:

> [crosspostet because of increasing frustation]

One thing that you'll find helps a lot when working with computers is to
not let yourself get frustrated. It's just a machine. You've clearly
done what you're trying to do before, and you seem to have a pretty good
handle on it. Now we only need to figure out why the machine isn't
behaving as you expect ...

> Any ideas what's wrong here, and how i can get it to boot from hd?

Not yet. Can you post the output of "lilo -v 2" (and perhaps even the
contents of lilo.conf), so we can see what is happening when you install
the boot loader?

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

SilliCone wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> [crosspostet because of increasing frustation]
>
> There are days i just hate...
>
> Looked like a quick'n easy- set up old P1-133 with slackware9.1, cli only.
> Usually a thing of mere minutes (not counting installation process itself)
> if nothing goes wrong. Yes, if.
>
> Problem:
>
> System is installed, runs fine as far as i can tell after 5 days without
> doing actual work with it.
> But- Lilo doesn't seem to work, or the bios doesn't seem to work as has to
> be expecetd, or what the fuck ever.
>
> I installed lilo as i do it always in the mbr of the first (and in this
> case only) harddisk. No error reportings, all looks clear. But after POST
> i only get "Insert bootable media in the aprobiate drive" That's it,
> nothing more. Re-installed lilo some times with the same result (and yes,
> i double- triple- and whatever checked the lilo.conf *g*).
> Used the superblock for my next tries, same result. One small difference-
> i get the same "Insert bootable media in the aprobiate drive", but after 2
> or 3 retries i get "Li 99 99 99 99l" Somewhere far far in the back of my
> head i think to remember that a message like "Li 01 01 01 01 lo" sometimes
> occured when one switched the kernel images without re-installing lilo
> after. But sure as hell i didn't change the kernel, and nobody said
> anything about this happening after some failed retries.
> Only way i get that box to boot is by floppy, and that isn't exactly what
> i had in mind.
>
> System Specs :
>
> Dell Dimension XPS P133S (P1 133MHz)
> 32MB RAM
> hda -> WD Caviar 850MB
> hdc -> IDE CD-ROM
> BIOS -> A10
> (Sidenote on the BIOS- at first that sucker didn't even boot from CD.
> Original BIOS was Version A00, updated to A10 (most recent) to get (with
> some other shit) ElTorrito support)
>
> Slackware 9.1, Lilo 22.5.7.2
>
> ****************
>
> Any ideas what's wrong here, and how i can get it to boot from hd?


Check if the partition is marked "Bootable", other than that there are old
BIOS versions which can't cope with certain harddisks.

Jenni

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sylvain Robitaille wrote:

> (NOTE: I'm following up to alt.os.linux.slackware only; This seems the
> most appropriate group for this message)

It doesn't seem to be a slackware-specific problem imo, but when i post to
multiple groups i look in all of them for replies :-)

> SilliCone wrote:
>
>> [crosspostet because of increasing frustation]
>
> One thing that you'll find helps a lot when working with computers is to
> not let yourself get frustrated. It's just a machine. You've clearly
> done what you're trying to do before, and you seem to have a pretty good
> handle on it. Now we only need to figure out why the machine isn't
> behaving as you expect ...

:-)
_That_ is easy: it doesn't like me ;-))

>> Any ideas what's wrong here, and how i can get it to boot from hd?
>
> Not yet. Can you post the output of "lilo -v 2" (and perhaps even the
> contents of lilo.conf), so we can see what is happening when you install
> the boot loader?

O'course.

#################################################

LILO version 22.5.7.2
##Copyright notice et al...

Warning: LBA32 addressing assumed
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/fd0
Warning: boot record relocation beyond BPB is necessary: /dev/fd0
pf_hard_disk_scan: ndevs=1
0300 3DB012B3 /dev/hda
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (bios assigned) = 0
device codes (canonical) = 1
Warning: unable to determine video adapter in use in the present system
Using MENU secondary loader
Calling map_insert_data
Secondary loader: 17 sectors (0x3200 dataend).
Warning: The boot sector and map file are on different disks
bios_boot = 0x00 bios_map = 0x80 map==boot = 0 map S/N: 3DB012B3
BIOS data check will include auto-suppress check

Boot image: /boot/vmlinuz
Setup lenght is 10 sectors.
Mapped 2398 sectors.
Added linux *

BIOS VolumeID Device
80 3DB012B3 0300
Writing boot sector
/boot/boot.200 exists - no boot sector backup copy made.
Map file size: 25088 bytes.
RAID device mask 0x0000
Boot sector relocation performed

******************************************
The lilo.conf
(skipping all the comments)

boot = /dev/fd0
#if i try to boot from floppy

boot = /dev/hda
#boot from hd

prompt
timeout = 50
vga = normal
image = /boot/vmlinuz
root = /dev/hda1
label = linux
read-only


ThanX !


- --
- -=SilliCone=-

"as appealing as it might seem, it is impossible to patch or upgrade users"
<Security Warrior>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQFBbXwiZa9iGSXQ4MIRApZkAJ9SYOhIHXy13sQAwm+zrq W0FKQYHwCfZUbu
/bPrmFmbTH6ezdaDySbpgXg=
=SfG7
-----END PGP SIGNATURE-----

["Followup-To:" header set to comp.os.linux.hardware.]
On Wed, 13 Oct 2004 18:51:51 +0200, SilliCone
<noone@nowhere.net> wrote:
>
> [crosspostet because of increasing frustation]
>
> There are days i just hate...
>
> Looked like a quick'n easy- set up old P1-133 with slackware9.1, cli only.
> Usually a thing of mere minutes (not counting installation process itself)
> if nothing goes wrong. Yes, if.
>
> Problem:
>
> System is installed, runs fine as far as i can tell after 5 days without
> doing actual work with it.
> But- Lilo doesn't seem to work, or the bios doesn't seem to work as has to
> be expecetd, or what the fuck ever.
>
> I installed lilo as i do it always in the mbr of the first (and in this case
> only) harddisk. No error reportings, all looks clear. But after POST i only
> get "Insert bootable media in the aprobiate drive" That's it, nothing more.

That looks like a BIOS error message. Some BIOSes have "virus
protection" which prevents writing to the MBR. You should turn that off
when installing an operating system.

> Re-installed lilo some times with the same result (and yes, i double-
> triple- and whatever checked the lilo.conf *g*).
> Used the superblock for my next tries, same result. One small difference- i
> get the same "Insert bootable media in the aprobiate drive", but after 2 or
> 3 retries i get "Li 99 99 99 99l" Somewhere far far in the back of my head
> i think to remember that a message like "Li 01 01 01 01 lo" sometimes
> occured when one switched the kernel images without re-installing lilo
> after. But sure as hell i didn't change the kernel, and nobody said
> anything about this happening after some failed retries.
> Only way i get that box to boot is by floppy, and that isn't exactly what i
> had in mind.
>
> System Specs :
>
> Dell Dimension XPS P133S (P1 133MHz)
> 32MB RAM
> hda -> WD Caviar 850MB
> hdc -> IDE CD-ROM
> BIOS -> A10
> (Sidenote on the BIOS- at first that sucker didn't even boot from CD.
> Original BIOS was Version A00, updated to A10 (most recent) to get (with
> some other shit) ElTorrito support)
>
How recent is the "most recent" BIOS for a 133 MHz machine? The BIOS
might not support hard drives larger than 540 MB, in which case you need
a boot partition or a boot floppy disk. The kernel doesn't have to be
on the boot floppy. You could make a lilo.conf with
boot=/dev/fd0
root=/dev/hda1
image=/vmlinuz (or whatever your kernel is called)


--
System Events
=-=-=-=-=-=-=
Sep 16 03:31:11 don kernel: lp0 on fire

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Måns Rullgård wrote:
| SilliCone <noone@nowhere.net> writes:
|
|
|>[crosspostet because of increasing frustation]
|
|
| No, crossposted to increase created frustration.

Ah, you must be from alt.2600.hackerz then.

Any more helpful advice to give?

- --
Leo Fellmann
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBcJ7JwjjtrLvNMRARAmcnAKCN+RlfLg3dI3AXooqCkS sfOo6xRQCdHuum
nr5kl52NgejV7+s3WFAOruw=
=a4XH
-----END PGP SIGNATURE-----

SilliCone wrote:

> It doesn't seem to be a slackware-specific problem imo, ...

True, but this felt like the best match for your problem anyway.

> but when i post to multiple groups i look in all of them for replies :-)

It's appreciated ...

> LILO version 22.5.7.2
> ...
> Reading boot sector from /dev/fd0

Notice that it's reading the old boot sector from /dev/fd0 ....

>...
> Writing boot sector
> /boot/boot.200 exists - no boot sector backup copy made.

and writing to /dev/fd0; (/boot/boot.200 is a backup of the original
boot sector found on that drive; the number in that filename is from
the device major and minor numbers, so it's easy to know where the boot
sector copy originally came from).

If it had tried to write to /dev/hda, it would be looking for (and
perhaps creating) /boot/boot.0300.

> The lilo.conf
> ...
>
> boot = /dev/fd0
> #if i try to boot from floppy
>
> boot = /dev/hda
> #boot from hd

Do you have both of these in the file, or are you just showing what you
have in each case? I suspect that if you have both, Lilo may be just
using the first one. If you're trying to permit yourself to easily
boot from either, why not run lilo twice, specifying the different boot
devices on the command line? (see the "-b" option in the Lilo manual
page for details)

I hope I've helped ...

--
----------------------------------------------------------------------
Sylvain Robitaille syl@alcor.concordia.ca

Systems analyst Concordia University
Instructional & Information Technology Montreal, Quebec, Canada
----------------------------------------------------------------------

On 10/13/04 22:21, SilliCone wrote:
> System Specs :
>
> Dell Dimension XPS P133S (P1 133MHz)
> 32MB RAM
> hda -> WD Caviar 850MB
> hdc -> IDE CD-ROM
> BIOS -> A10
> (Sidenote on the BIOS- at first that sucker didn't even boot from CD.
> Original BIOS was Version A00, updated to A10 (most recent) to get (with
> some other shit) ElTorrito support)

For my DELL Inspiron 4150/P4(M)/2.4GHz/256MB the latest avaiable BIOS
version at Dell's support site is A06 only; and you have installed A10.
Is that version correct and, or applicable for your dated machine?

--
Dr Balwinder Singh Dheeman Registered Linux User: #229709
CLLO (Chief Linux Learning Officer) Machines: #168573, 170593, 259192
Anu's Linux@HOME Distros: Knoppix, Fedora, FreeBSD
More: http://anu.homelinux.net/~bsd/ Visit: http://counter.li.org/

"SilliCone" <noone@nowhere.net> wrote in message
news:ckjmfa$18j$1@newsreader2.netcologne.de...

Stupid thing to point out, but you got the correct boot order/included the
hdd in the bios boot.

[folloups set to alt.hacker]