> > > Is there a reason that it does this?
> >
> > I believe there is. It wants to find what drive is bios drive 80h.
>
> Yes.
>
> > I had a machine at work with both ide and scsi. ide hdd was hdc and ide
> > cdrom was hda just to keep lilo from thinking hdc is the first bios drive
> > which
On Fri, Jul 06, 2001 at 01:08:55AM +0200, Guest section DW wrote:
> (But you must distinguish people. One complains about the probing,
> another about the numbering. The bios keyword tells lilo about
> the numbering, and it works.)
Well, shouldn't lilo avoid probing if you pass bios=? Currently
On Thu, Jul 05, 2001 at 04:03:32PM -0700, Aaron Lehmann wrote:
> On Fri, Jul 06, 2001 at 01:01:07AM +0200, Guest section DW wrote:
> > But why don't you use the bios keyword? From lilo.conf(5):
>
> It doesn't help.
Of course it does.
(But you must distinguish people. One complains about the
On Fri, Jul 06, 2001 at 01:01:07AM +0200, Guest section DW wrote:
> But why don't you use the bios keyword? From lilo.conf(5):
It doesn't help.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, Jul 05, 2001 at 06:03:31PM -0400, Wakko Warner wrote:
> > > Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
> > > There is no problem, certainly no kernel problem.
> >
> > Sure it isn't a problem, but it's really annoying if it won't need to
> > touch hda anyway.
>
Wakko Warner writes:
> I believe there is. It wants to find what drive is bios drive 80h. Really
> annoying since there's no way (correct me if I'm wrong) to read bios from
> linux. If there is, lilo should do that. But since it's an old copy, this
> probably was fixed.
>
> I had a machine
> > cache_add("/dev/hda",0x300);
> > for (i = 1; i <= 8; i++) {
> > sprintf(tmp,"/dev/hda%d",i);
> > cache_add(tmp,0x300+i);
> >
> > Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
> > There is no problem, certainly no kernel problem.
>
> Sure it
> cache_add("/dev/hda",0x300);
> for (i = 1; i <= 8; i++) {
> sprintf(tmp,"/dev/hda%d",i);
> cache_add(tmp,0x300+i);
>
> Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
> There is no problem, certainly no kernel problem.
Sure it isn't a problem, but
cache_add(/dev/hda,0x300);
for (i = 1; i = 8; i++) {
sprintf(tmp,/dev/hda%d,i);
cache_add(tmp,0x300+i);
Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
There is no problem, certainly no kernel problem.
Sure it isn't a problem, but it's really
cache_add(/dev/hda,0x300);
for (i = 1; i = 8; i++) {
sprintf(tmp,/dev/hda%d,i);
cache_add(tmp,0x300+i);
Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
There is no problem, certainly no kernel problem.
Sure it isn't a problem, but
Wakko Warner writes:
I believe there is. It wants to find what drive is bios drive 80h. Really
annoying since there's no way (correct me if I'm wrong) to read bios from
linux. If there is, lilo should do that. But since it's an old copy, this
probably was fixed.
I had a machine at work
On Fri, Jul 06, 2001 at 01:01:07AM +0200, Guest section DW wrote:
But why don't you use the bios keyword? From lilo.conf(5):
It doesn't help.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Thu, Jul 05, 2001 at 06:03:31PM -0400, Wakko Warner wrote:
Before doing anything LILO v21 collects the hda, hdb, sda, sdb info.
There is no problem, certainly no kernel problem.
Sure it isn't a problem, but it's really annoying if it won't need to
touch hda anyway.
Is there
On Thu, Jul 05, 2001 at 04:03:32PM -0700, Aaron Lehmann wrote:
On Fri, Jul 06, 2001 at 01:01:07AM +0200, Guest section DW wrote:
But why don't you use the bios keyword? From lilo.conf(5):
It doesn't help.
Of course it does.
(But you must distinguish people. One complains about the
On Fri, Jul 06, 2001 at 01:08:55AM +0200, Guest section DW wrote:
(But you must distinguish people. One complains about the probing,
another about the numbering. The bios keyword tells lilo about
the numbering, and it works.)
Well, shouldn't lilo avoid probing if you pass bios=? Currently it
Is there a reason that it does this?
I believe there is. It wants to find what drive is bios drive 80h.
Yes.
I had a machine at work with both ide and scsi. ide hdd was hdc and ide
cdrom was hda just to keep lilo from thinking hdc is the first bios drive
which infact sda was
16 matches
Mail list logo
