Hi,
Sven Luther writes:
> Why not use discover in the initrd ?
This has gotten hold of you and won't let you go, eh?
> Would this be too place consuming ?
Yes. Also, discover is meant to detect all the hardware no matter
where you run it. If you want this, you should build as many drivers
a
On Sun, May 23, 2004 at 04:13:49PM +0200, Michael Schmitz wrote:
> > > Why do the drives get numbered in a different order?
> >
> > In 2.4, the drivers for both your controllers were built into the
> > kernel. They probably got probed in alphabetical order, which
>
> Nope, they get probed in the
> > Why do the drives get numbered in a different order?
>
> In 2.4, the drivers for both your controllers were built into the
> kernel. They probably got probed in alphabetical order, which
Nope, they get probed in the precise order that is defined in the IDE
driver (there's a lengthy struct pop
Jens Schmalzing wrote:
Beats me. The mkinitrd script contains fairly involved detection
heuristics for the root filesystem drivers. They use the /proc
filesystem repeatedly, so the problem may be due to your first initrd
being built with a 2.4 kernel running and the order of the controllers
rev
Hi,
Tim Otten writes:
> Why doesn't it find the CMD646 automatically?
Beats me. The mkinitrd script contains fairly involved detection
heuristics for the root filesystem drivers. They use the /proc
filesystem repeatedly, so the problem may be due to your first initrd
being built with a 2.4 ker
I'm trying to boot kernel-image-2.6.6-powerpc, version 2.6.6-2, on a
Blue&White G3. It crashes during the initrd, with pivot_root complaining,
"No such file or directory," and subsequent complaints about failing to
open /dev/console and a failure of init.
Looking at the hardware detection, I got:
6 matches
Mail list logo
