From owner-freebsd-questions Mon Jul 31 6:45:35 2000 Delivered-To: freebsd-questions@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 7110B37BB57 for ; Mon, 31 Jul 2000 06:45:30 -0700 (PDT) (envelope-from dgason@mindspring.com) Received: from smui1.atl.mindspring.net (smui1.atl.mindspring.net [207.69.200.121]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id JAA00969; Mon, 31 Jul 2000 09:45:28 -0400 (EDT) From: dgason@mindspring.com Received: by smui1.atl.mindspring.net id JAA0000020425; Mon, 31 Jul 2000 09:45:28 -0400 (EDT) Date: Mon, 31 Jul 2000 09:45:28 -0400 To: freebsd-questions@freebsd.org Subject: 4.0 -> 4.1 upgrade; now moused doesn't start??? Message-ID: X-Originating-IP: 12.20.58.68 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I recently upgraded from 4.0-RELEASE to 4.1-STABLE using CVSup and "make world". After this upgrade, I have found two problems and I would like to know if there is a simple solution, or if these are bugs that need to be reported. The first problem is that the moused daemon no longer starts. I can start it manually either with /stand/sysinstall or by running #/usr/sbin/moused -d /dev/psm0 However, it used to start automatically with 4.0-RELEASE and the code to start the mouse still seems to be in /etc/rc.conf and /etc/rc.i386 "dmesg" reveals that the kernel is finding the mouse on boot, and I see no error messages in "dmesg" either. Should I be looking in some other place for the error message? While I can always use the /usr/sbin/moused command to start the mouse daemon, this is something of a hack, and I would like to identify the root cause of the problem. ===> My question is - what must I do to get the mouse working??? In addition, I notice that when I run /stand/sysinstall, I am now getting an error reading the primary partition table afd0 or fsbn0. However, I am unaware of any such device: this is not my hard disk, floppy, or cd-rom. ===> Any ideas here? Thank you very much in advance for any advice or solutions, Dave FYI, here's some more detail on my upgrade from 4.0-RELEASE to 4.1-STABLE (given the problems above, I am starting to regret my decision to upgrade, things worked just fine before) I was running 4.0-RELEASE. I used CVSup and a stable-supfile to download the source for 4.1 STABLE. After this, I backed up /etc I then did a make world as follows: #script /var/tmp/mw.out #make world I then did a "diff" on the files in /etc and /usr/src/etc and tried to merge any changes. (The changes were few and appeared to be minor). I then rebuilt the kernel. I did this by coping GENERIC to EMERALD (my machine name) and added the following for my DSL connection: optoins NETGRAPH options NETGRAPH_PPPOE options NETGRAPH_SOCKET I then did: #config EMERALD #cd ../..compile/EMERALD #make depend #make #make install To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message