Project

General

Profile

Actions

Bug #1386

closed

kernel modules installed in wrong place?

Added by wa1ter almost 15 years ago. Updated almost 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

I just pulled from the git mirror at theshell.com and built world,
and also kernel -- but using the old-style method of running 'config'
from /usr/src/sys/config and then compiling in the sys/compile directory.

The building went fine, but the 'install' target put the kernel modules
in / instead of /boot/modules. (The old modules did, however, go in the
/boot/modules.old directory.)

Is the old method still supported, BTW? It's been working well for me
until today's update.

Actions #1

Updated by qhwt+dfly almost 15 years ago

On Sat, May 23, 2009 at 11:47:36AM -0700, walt wrote:

I just pulled from the git mirror at theshell.com and built world,
and also kernel -- but using the old-style method of running 'config'
from /usr/src/sys/config and then compiling in the sys/compile directory.

The building went fine, but the 'install' target put the kernel modules
in / instead of /boot/modules. (The old modules did, however, go in the
/boot/modules.old directory.)

I guess you haven't updated the system (other than the source tree and the
kernel) since February, or you're doing it on DragonFly 2.0.x-RELEASE .
If one of them is the case, either installing those files first (which is
usually done by installworld), or explicitly specifying the location of
these files in the source tree on the command line should help.

make -m /usr/src/share/mk install
or to install just modules
make -m /usr/src/share/mk modules-install

The commits 663216ba and 3b25fbd4 have moved some variables which affect
installing kernel modules into /sys/conf, so you need to have newer *.mk
files installed under /usr/share/mk, or explicitly tell make command to
use /usr/src/share/mk.

Is the old method still supported, BTW? It's been working well for me
until today's update.

Yes, but sometimes you need to take care of a few special things,
usually done by the installkernel target.

Cheers.

Actions #2

Updated by wa1ter almost 15 years ago

YONETANI Tomokazu wrote:

On Sat, May 23, 2009 at 11:47:36AM -0700, walt wrote:

The building went fine, but the 'install' target put the kernel modules
in / instead of /boot/modules. (The old modules did, however, go in the
/boot/modules.old directory.)

I guess you haven't updated the system (other than the source tree and the
kernel) since February...

Yes, I installed the kernel before installing world. The problem fixed
itself after that, thanks.

Actions

Also available in: Atom PDF