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 kernel running and the order of the controllers reversed. If you find a patch that fixes this, send it to the maintainer. > 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 happened to result in the CMD646 controller being probed before the Apple Heathrow controller, because the drivers are called cmd64x and pmac-ide, respectively. In 2.6, we tried to build as many drivers as possible as modules. The pmac-ide driver, however, has to be built into the kernel and is therefore always probed first. > (except, of course, that fstab is broken). Well, that should be easy to fix now, so you're almost there. Regards, Jens. -- J'qbpbe, le m'en fquz pe j'qbpbe! Le veux aimeb et mqubib panz je pézqbpbe je djuz tqtaj!
