Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 29 Apr 2002 03:29:50 +0200 (MET DST)
From:      Lawrence Mayer dsg <Lawrence.Mayer@dsg.ki.se>
To:        freebsd-questions@FreeBSD.ORG
Subject:   Help! vnconfig won't work
Message-ID:  <Pine.GSO.4.44.0204290326050.3352-100000@mbox.ki.se>

next in thread | raw e-mail | index | archive | help
Hi,

I made my very first installation of FreeBSD 4.5 RELEASE this weekend. (I
haven't compiled a custom kernal yet: I've been using the generic kernel
so far.) I reinstalled several times to experiment with different
installation options. The first time I installed, vnconfig was working
fine.

Specifically, after my first installation, the command:
# vnconfig -e vn0c /dosd/pagefile.sys swap
returned no errors, and the command
# swapinfo
verified that /dosd/pagefile.sys was being used as swap

NOW, AFTER REINSTALLING FREEBSD, VNCONFIG WON'T WORK:

1. When I issue the same command as before (logged in as root)
# vnconfig -e vn0c /dosd/pagefile.sys swap
the following error is returned:
"vnconfig: cannot find or load "vn" kernal module"

2. I have troubleshooted as follows:
a. the file vn0c is indeed present in /dev
b. the file pagefile.sys is indeed present in /dosd, which is indeed
properly mounted
c. the file vn.ko is indeed present in /modules

3. Because of 2(c) above, I tried issuing the command (logged in as root):
# kldload vn.ko
but the following error is returned:
"kldload: can't load vn.ko: Operation not permitted"
The command:
# kldload /modules/vn.ko returns the same error, e.g.
"kldload: can't load vn.ko: Operation not permitted"

4. I've tried reinstalling the entire FreeBSD 4.5 RELEASE yet again, and I
get the same errors (1) and (3).

5. At no time did I enter "pseudo-device vn" (or anything else) into my
kernel configuration file. vnconfig was working earlier today (on my first
installation) without that entry, presumably loading the kernal module
vn.ko instead.

What's going on? Why can't the kernel load the module vn.ko when I've
verified that it's present in /modules?

As I said, vnconfig was working PERFECTLY on my first FreeBSD installation
earlier today. Why won't it work now?

I chose slightly different distribution sets on my first installation than
I have now. For example, I chose Linux binary compatibility on my first
installation but not now. Could my problem somehow depend on choosing
different distribution sets? If so, what do I need to install to get
vnconfig working again?

I would greatly appreciate help. This is driving me crazy!

Greetings,
Lawrence Mayer <lawmay@ki.se>
Ume=E5, Sweden


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.44.0204290326050.3352-100000>