speeding up devb-eide device scanning

I’m using devb-eide & in my script for my boot image. the problem i’m
having is that it takes 30-45 seconds to find 1 device (the only
device on the system). is there a way of telling devb-eide that there
is only 1 device present its located “here”, and not to bother with
the rest? i’m my case the device is on the secondary master so i’m
sure it searching primary master,primary slave, then secondary
master,secondary slave.
its not really a problem but i would like a little snappier boot
response…

vince

Modify your boot image to pass ‘eide nopci,slave’ to eide driver, it
will help a lot.

vince wrote:

I’m using devb-eide & in my script for my boot image. the problem i’m
having is that it takes 30-45 seconds to find 1 device (the only
device on the system). is there a way of telling devb-eide that there
is only 1 device present its located “here”, and not to bother with
the rest? i’m my case the device is on the secondary master so i’m
sure it searching primary master,primary slave, then secondary
master,secondary slave.
its not really a problem but i would like a little snappier boot
response…

vince

vince wrote:

I’m using devb-eide & in my script for my boot image. the problem i’m
having is that it takes 30-45 seconds to find 1 device (the only
device on the system). is there a way of telling devb-eide that there
is only 1 device present its located “here”, and not to bother with
the rest? i’m my case the device is on the secondary master so i’m
sure it searching primary master,primary slave, then secondary
master,secondary slave.

Pass options to the eide module of the devb-eide driver. In your
specific case it would appear you want:
“devb-eide eide ioport=0x170,irq=15,slave &”

I had a thought for an App / Script

cp .boot to .altboot
build enum-ed and rc.local changes (or curr running sys)
to a .build file w/o enum, mkifs → .boot

John Garvey <jpg@cisco.com> wrote in message
news:3A329AD2.D9A77F7F@cisco.com

vince wrote:
I’m using devb-eide & in my script for my boot image. the problem i’m
having is that it takes 30-45 seconds to find 1 device (the only
device on the system). is there a way of telling devb-eide that there
is only 1 device present its located “here”, and not to bother with
the rest? i’m my case the device is on the secondary master so i’m
sure it searching primary master,primary slave, then secondary
master,secondary slave.

Pass options to the eide module of the devb-eide driver. In your
specific case it would appear you want:
“devb-eide eide ioport=0x170,irq=15,slave &”

Works like a charm… boot up in photon in under 15s … very impressive
thanks…

vince


On Sat, 09 Dec 2000 15:49:22 -0500, John Garvey <jpg@cisco.com> wrote:

vince wrote:
I’m using devb-eide & in my script for my boot image. the problem i’m
having is that it takes 30-45 seconds to find 1 device (the only
device on the system). is there a way of telling devb-eide that there
is only 1 device present its located “here”, and not to bother with
the rest? i’m my case the device is on the secondary master so i’m
sure it searching primary master,primary slave, then secondary
master,secondary slave.

Pass options to the eide module of the devb-eide driver. In your
specific case it would appear you want:
“devb-eide eide ioport=0x170,irq=15,slave &”