From owner-freebsd-stable Sun Mar 19 0:49:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 0ACC737BC52 for ; Sun, 19 Mar 2000 00:49:46 -0800 (PST) (envelope-from jim@nasby.net) Received: from nasby.net (sysnasby@2.nasby.dsl.enteract.com [216.80.51.18]) by mail.enteract.com (8.9.3/8.9.3) with ESMTP id CAA84328 for ; Sun, 19 Mar 2000 02:49:41 -0600 (CST) (envelope-from jim@nasby.net) Message-ID: <38D494A5.FE9796CD@nasby.net> Date: Sun, 19 Mar 2000 02:49:41 -0600 From: "Jim C. Nasby" Organization: distributed.net X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en-US,en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 3.4-4.0 and vinum References: <38D48D3D.1DBA8F5D@nasby.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I got vinum to start by doing a 'cd /usr/src/sys/modules/vinum && make install' (after booting back to a 3.4 GENERIC kernel). I can now get vinum to load, but it won't mount anything... the error it gives is 'Cannot get device list: cannot allocate memory'... I'm guessing that some library needs to be installed as well. I'm way to tired to try trouble-shooting this anymore tonight (last thing I want to do is destroy my volumes :) ), but if anyone has any ideas I'd love to hear them. FWIW, I'd followed all the steps in /usr/src/UPDATING up to and including ''... the only variations were that for building/installing the kernel, I used make buildkernel from /usr/src (as well as make installkernel), and I just did a MAKEDEV all (I don't have any IDE drives on this box; though dmesg is now saying something about an IDE device... guess I still have one of the controllers enabled in the BIOS). Also, sorry for cross-posting my previous message to -questions as well as -stable, but I wanted to warn anyone who might be running vinum about this... would be a major pain if this happened on a production box. Thanks, Jim "Jim C. Nasby" wrote: > > For those of you who are running vinum, make damn sure you keep an old > kernel around while upgrading... it seems that you can't load vinum > after booting with the new kernel... I'm hoping that a make install in > the vinum directory will remedy this situation... I'll post an update > once I know what's going on, but in the meantime, this is a heads-up for > everyone running vinum. > -- > Jim C. Nasby (aka Decibel!) /^\ > jim@nasby.net /___\ > Freelance lighting designer and database developer / | \ > Member: Triangle Fraternity, Sports Car Club of America /___|___\ > > Give your computer some brain candy! www.distributed.net Team #1828 > Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Jim C. Nasby (aka Decibel!) /^\ jim@nasby.net /___\ Freelance lighting designer and database developer / | \ Member: Triangle Fraternity, Sports Car Club of America /___|___\ Give your computer some brain candy! www.distributed.net Team #1828 Get paid to surf!! http://www.enteract.com/~nasby/alladvantage.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message