trouble with LILO

trouble with LILO

Post by Philippe Givele » Sat, 29 Mar 1997 04:00:00



I have a trouble with LILO

I have a P133 with 3 Disk (330M, 119M et 2,5G) and I want run  
3 possibility  Dos(and win3.11), Win95 and Linux
LINUX 2.0.0

When I Boot my conputer I have 3 possibility  
Dos, Win95 et Linux.
Dos and Linux run without problem

                 BUT NOT WIN95 (on /dev/hdc1)

I have on screen (in french): Erreur d'E/S  
        in english i think:     error in/out

and when i install again LILO, I see:

ide probable bad entry for /dev/hdc
        Warning BIOS drive 0X82 may not be accessible.

on this configuration The win 95's disk is secondary master,
if i plug it aloneas primary Master it boot and run win95
without any problem. so i think the trouble comes
from the MBR of this disk.

        how can i do to make this bootable partition(/dev/hdc1)
                        be reconized by  Lilo?
        I think fdisk /MBR but perhaps it will write on  /dev/hda1 !!!

I don't want to lose my win3.11 configuration(on /dev/hda1)
for the other, i have rinstalled them 3 time linux and win95 yet.
so one more or less it doesn't matter!!!

configuration:
Mainboard asustek, P133, 32M RAM, 512k cache

Device    Boot  Begin  Start  End  Blocks     ID      System
/dev/hda1    *      1      1  664  334624+     6      DOS 16-bit >=32M

/dev/hdb1           1      1  926  118056+     6      DOS 16-bit >=32M

/dev/hdc1    *      1      1  145  584508+     6      DOS 16-bit >=32M
/dev/hdc3         146    146  291  588672     83      Linux native
/dev/hdc5         292    292  405  459616+     6      DOS 16-bit >=32M
/dev/hdc6         406    406  514  439456+     6      DOS 16-bit >=32M
/dev/hdc7         515    515  623  439456+     6      DOS 16-bit >=32M

cdrom on /dev/hdd  

on /dev/hda1 et /dev/hdb1 dos 6.0 et win 3.11
on /dev/hdc1 win95
on /dev/hdc3 Linux

lilo.conf:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact        # faster, but won't work on all systems.
delay = 50
vga = normal    # force sane state
ramdisk = 0     # paranoia setting
# End LILO global section
# DOS bootable partition config begins
other = /dev/hda1
  label = dos
  table = /dev/hda
# DOS bootable partition config ends
# DOS bootable partition config begins
other = /dev/hdc1
  label = 95
  loader = /boot/any_d.b
  table = /dev/hdc
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /vmlinuz
  root = /dev/hdc3
  label = linux
  read-only # Non-UMSDOS filesystems should be mounted read-only for
checking
# Linux bootable partition config ends

 
 
 

1. That L010101010101 screenful of trouble with LILO

I saw some postings on this list about the L010101010 LILO problem.
I had the same problem but I solved it using another boot loader.
I use Snow 2.2. (Linux 1.1.58 + LILO-14)
I have been trying to track down why this happens, and I suspect
it's a obcsure BIOS problem in my Tulip DS 486-DX2-50 (TC-35 board)
I decided to junk LILO from my IDE 340 Mb drive and install Loadlin 1.5
from SunSite.unc.edu on C:\LOADLIN dir. My PAS 16 SCSI card has a ST1480N
425 MB drive loaded with SNOW 2.2 Linux and a CDROM on the same bus.

This program worked at the first attempt and is't a very good alternative
to LILO. I think it's even better to understand what's happening
and easier to configure _if_ you have a DOS system available on your box,
but doesn't everybody have DOS too on their box :-) Ah Well ...

If you use UMSDOS based Filesystem, it's probably the best option to choose
in my opinion.
Anyway, it was my attemt to work around that nasty L010101010 problem
when booting from my IDE drive.

Cheers,

--
Marcel Bernards, UNIX & Net sysadm Netherlands Energy Research Foundation ECN
(and SURFnet IC/ICP), Phone: (+31 /0)2246 4579 Fax: (+31 /0)2246 1864

SCREAMNet : AAAAAARGHH!HUH?? : Disclaimer: "The AntiChrist is the Computer !"

2. This is crazy! Cannot find stdio.h! (on RH Linux)

3. Trouble with LILO and OS/2 Boot Manager

4. Testing to determine if a command exists

5. Trouble with LILO

6. bincancel:28 large binaries:AR284:@@NCM

7. Trouble compiling lilo source code

8. csh filename completion / untaring to NFS directories

9. trouble with LILO

10. Trouble with LILO

11. Troubles compiling lilo v3

12. Trouble w/LILO (again)

13. Trouble with LILO (linux & msdos)