Hi biil !
Well i guess you got me all wrong... :)
there is NO hda on my system (or there wasn't , at least till las
night at 4 am...) :)
i could not config that damm hd to be master on the primary
channel...so i installed Linux
on it as slave.
The problem started from the 1st time i booted linux after the
installation.
Last night (or should i say this morning) i had it (!) and i tried
once more to config that disk as primary.
This time it worked :) but linux (as expected) gave me a kernel panic
on bootup and gave up on me.
I had to re-install mdk all over again...and i did...
after doing so , i booted-up , and guess what ?? same thing all over
again !!! :(
the disk is now configured as hda and everything is suppose to be
normal, but i am still getting :
li 04 04 04 04 04 04 04 04 04 04
04 04 04 04 04 04 04 04 04 04 04
04 04 04 04 04 04 04 04 04 04 04
04 04 04 04 04 04 04 04 04 04 04
all over the screen (when trying to boot normally)
when booting from fd0 everything is ok...
i really donno this time..think my boot sector is damaged ?
This is a 4 months old hard drive !!!
any suggestion's ?
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 6/17/00, 6:03:08 AM, "Bill Shirley" <[EMAIL PROTECTED]> wrote regarding
RE: [expert] lilo:
> When you run lilo and is says:
> Warning: /dev/hdb is not on the first disk
> it is telling you "I will write the boot program to /dev/hdb but your
BIOS
> will probably never look for the boot loader on hard drive B!" You
are
> probably booting the lilo on /dev/hda which now points to a kernel
that is
> no longer in the correct place on the disk.
> I did this too. I had to boot my old Slackware system from a floppy
for a
> very long time. I finally figured it out.
> I you have one of the newer BIOS's, you may be able to set it up to
boot
> from IDE-1 if that is really what you want.
> What I THINK you want is the boot loader (LILO) on /dev/hda
(boot=/dev/hda)
> and change lilo.conf to use root=/dev/hdb1 (or /dev/hdb? whatever
number ?
> is). Such as:
> elmo:/etc/named# less /etc/lilo.conf
> # LILO configuration file
> # generated by 'liloconfig'
> #
> # Start LILO global section
> boot = /dev/hda
> default = Slack96
> #compact # faster, but won't work on all systems.
> delay = 100
> vga = normal # force sane state
> ramdisk = 0 # paranoia setting
> # End LILO global section
> # Linux bootable partition config begins
> image = /vmlinuz
> root = /dev/hdb1
> label = Slack96
> read-only # Non-UMSDOS filesystems should be mounted read-only for
> checking
> append = "max_scsi_luns=5"
> # Linux bootable partition config ends
> Hope this helps,
> Bill
> > -----Original Message-----
> > From: LinuxMan [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, June 16, 2000 3:53 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: [expert] lilo
> >
> >
> >
> > Hi!
> >
> > i did not change any settings in my bios since i installed mandrake...
> > in fact , this happened from the first boot after installation... :(
> >
> > when running lilo i get :
> >
> >
> >
> > [root@webug /root]# lilo
> > Warning: /dev/hdb is not on the first disk
> > Added linux *
> > Added failsafe
> > Added floppy
> > [root@webug /root]
> >
> > my primary disk (as you can see) is not hda but hdd... i had some
> > problems installing
> > it as primary, so it's configured as secondary slave..
> > think that could be the reason ??
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > >>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
> >
> > On 6/16/00, 12:26:23 PM, "Juan A. Magallon"
> > <[EMAIL PROTECTED]>
> > wrote regarding Re: [expert] lilo:
> >
> >
> > > At 02:35 +0000 2000/06/16, tal amir wrote:
> > > >Hey you guy's ! :-)
> > > >
> > > >when booting lilo (mdk 7.1) i am getting :
> > > >
> > > >li 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04
> > > >04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04
> > > >04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04
> > > >04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04
> > > >04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04
> > > >04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04
> > > >
> >
> > > Suffered from that sometimes: two possible causes:
> > > - You booted with some different BIOS setting for your hard
> > drive when
> > > running lilo and when trying to boot with the kernel lilo
> > intalled
> > > (say you booted with disk in LBA mode, and then rebooted in
> > LARGE
> > > or NORMAL)
> > > - You changed kenel (usuallly /vmlinuz or /boot/vmlinuz) without
> > re-running
> > > lilo. Or you ran lilo and it didn't found the default
> > kernel you
> > > specified in lilo.conf
> >
> > > Take a look to the error messages when running lilo....
> >
> > > Good Luck.
> >
> > > --
> > > Juan Antonio Magallon Lacarta
> > mailto:[EMAIL PROTECTED]
> > > Grupo de Informatica Grafica Avanzada
> > http://giga.cps.unizar.es
> > > Tlf: 34-976-762354,1916 - Fax: 34-976-761914
> >
> >
> >
> >
