>
> I'm trying to install 4.0-RELEASE on a COMPAQ Proliant 1850R
> with the root disk on a SMART-2SL raid controller. The install
> works perfectly, but boot/loader fails to load the kernel.
>
> Booting "kernel" fails with 'Don't know how to load module
> "/kernel"', and boot kernel.GENERIC
Mike Smith once wrote:
>> After doing a cvsup yesterday evening i can't seem to boot on
>my
>> raid cotroller using the same kernel config.
>>
>> Is -current probing hardware i a different way now or ??
>
>This is a consequence of a defect in the way that the ida driver
>works,
>and new code w
>
> For now, you could remove the IDE devices from the config file,
> until this gets fixed. Ideally, the boot blocks/loader should be
> taught to boot from something other than wd() or da().
The loader groks this already; there's some missing glue in the kernel
that Poul has already worked ou
> After doing a cvsup yesterday evening i can't seem to boot on my
> raid cotroller using the same kernel config.
>
> Is -current probing hardware i a different way now or ??
This is a consequence of a defect in the way that the ida driver works,
and new code which resorts the disk drivers (so
Jonathan Lemon wrote:
>
> For now, you could remove the IDE devices from the config file,
> until this gets fixed. Ideally, the boot blocks/loader should be
> taught to boot from something other than wd() or da().
Alas, the loader uses BIOS to read the disk. Anything the BIOS can
read, so can t
In message <[EMAIL PROTECTED]>, Warner Losh writes:
>phk's fla driver mount / correctly when it is the boot device.
>However, the boot loader does have some interesting limitations in
>this area last time I checked. Likely it was due to using the -stable
>version for most of my testing.
I actua
In message <[EMAIL PROTECTED]> Jonathan Lemon writes:
: Yes. The IDA driver will be happy with it's own device nodes
: (/dev/ida), but last time I checked, the boot/loader would
: only understand root devices of wd() or da(). I understand that
: Soren's ad() driver has the same problem.
T
On Sep 09, 1999 at 01:26:35PM -0600, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Jonathan Lemon writes:
> : It appears so. The IDA driver needs to stomp on the WD driver's
> : vectors in order to boot off of the RAID controller. It seems that
> : something changed so that wd is getting p
In message <[EMAIL PROTECTED]> Jonathan Lemon writes:
: It appears so. The IDA driver needs to stomp on the WD driver's
: vectors in order to boot off of the RAID controller. It seems that
: something changed so that wd is getting probed after the ida driver
: now, and removing the vectors.
Is
In article [EMAIL PROTECTED]> you
write:
>After doing a cvsup yesterday evening i can't seem to boot on my
>raid cotroller using the same kernel config.
>
>Is -current probing hardware i a different way now or ??
It appears so. The IDA driver needs to stomp on the WD driver's
vectors in order t
I don't know who is maintaining the id driver, but it looks to
me like it isn't able to co-exist with the wd driver (because
it "steals" the wd drivers cdevsw entry)
Poul-Henning
In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] w
rites:
>After doing a cvsup yesterday evening i can't seem to bo
After doing a cvsup yesterday evening i can't seem to boot on my
raid cotroller using the same kernel config.
Is -current probing hardware i a different way now or ??
Is there anyone with an answer to this ??
Kernel Config:
#Compaq SMART Array 2-SL Controller
controller ida0
device
12 matches
Mail list logo
