Re: [OT] Re: LILO calling modprobe?
> > > 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 > > But why don't you use the bios keyword? From lilo.conf(5): I was only explaining. I foundout about the bios keyword after searching. But I didn't have time then to do the searching and didn't care. it worked for me. I don't boot scsi drives on any of my systems that also have ide. I prefer the systems to be either, but not both (test boxes excluded =) -- Lab tests show that use of micro$oft causes cancer in lab animals - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 doesn't. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 probing, another about the numbering. The bios keyword tells lilo about the numbering, and it works.) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 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 But why don't you use the bios keyword? From lilo.conf(5): For example, disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 would say that your SCSI disk is the first BIOS disk, and your (primary master) IDE disk is the second BIOS disk. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 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 The easy way to handle this is to md5 checksum the disks at boot. Read the first and last track of the first and last cylinder of every BIOS drive. Then match up the disks when partition tables get scanned. The hard way involves running the BIOS in virtual-8088 mode to trap IO accesses, then mapping to drivers by IO region later. Neither way is 100% reliable, but the current guess is worse. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
> > 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 annoying if it won't need to
> touch hda anyway.
>
> Is there a reason that it does this?
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 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
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[OT] Re: LILO calling modprobe?
> 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 annoying if it won't need to
touch hda anyway.
Is there a reason that it does this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[OT] Re: LILO calling modprobe?
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 annoying if it won't need to
touch hda anyway.
Is there a reason that it does this?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 annoying if it won't need to
touch hda anyway.
Is there a reason that it does this?
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 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
--
Lab tests show that use of micro$oft causes cancer in lab animals
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 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 The easy way to handle this is to md5 checksum the disks at boot. Read the first and last track of the first and last cylinder of every BIOS drive. Then match up the disks when partition tables get scanned. The hard way involves running the BIOS in virtual-8088 mode to trap IO accesses, then mapping to drivers by IO region later. Neither way is 100% reliable, but the current guess is worse. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 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 But why don't you use the bios keyword? From lilo.conf(5): For example, disk=/dev/sda bios=0x80 disk=/dev/hda bios=0x81 would say that your SCSI disk is the first BIOS disk, and your (primary master) IDE disk is the second BIOS disk. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 probing, another about the numbering. The bios keyword tells lilo about the numbering, and it works.) - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 doesn't. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [OT] Re: LILO calling modprobe?
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 But why don't you use the bios keyword? From lilo.conf(5): I was only explaining. I foundout about the bios keyword after searching. But I didn't have time then to do the searching and didn't care. it worked for me. I don't boot scsi drives on any of my systems that also have ide. I prefer the systems to be either, but not both (test boxes excluded =) -- Lab tests show that use of micro$oft causes cancer in lab animals - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
