kab...@lich.phys.spbu.ru (Dima Veselov) writes:
>That was what I had looking for. But now there is new problem - root
>detection. After finding correct wedges it want to boot from wd0b.
BIOS boots from a specific drive (not a logical volume) and that's
passed to the kernel.
The kernel tries to locate the bootsector, but since it detects the
components first, this is used.
>If I understand properly - I can't supply root option via boot.cfg,
>so I am trying to compile new kernel with:
While the bootloader could pass a literal boot device, this is only
done by multiboot (e.g. grub), not by the regular /boot.
>include "arch/amd64/conf/GENERIC"
>no config netbsd root
>config netbsd root on dk1 type ?
Instead of specifying dk1, you can use a quoted string like
"wedge:name-of-my-root-wedge"
>But it also won't build with
>/usr/src/sys/arch/amd64/conf/Alba:5: syntax error
>/usr/src/sys/arch/amd64/conf/Alba:6: netbsd: device `dk' does not exist
>nbconfig: /usr/src/sys/arch/amd64/conf/Alba has no configurations!
>I suggest it happens because dk is not set as a device in kernel config.
Yes. config cannot identify a device named dk1. You could specify it
as a major/minor combination like:
config netbsd root on major 168 minor 1 type ?
or use a string with a device name
config netbsd root on "dk1" type ?
or use a string with a wedge name like above.
--
--
Michael van Elst
Internet: mlel...@serpens.de
"A potential Snark may lurk in every tree."
