Date: Tue, 21 May 1996 11:35:14 +0930 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: brian@MediaCity.com Cc: sparkles@leland.Stanford.EDU, freebsd-questions@FreeBSD.org Subject: Re: My mouse and xfree86 don't get along Message-ID: <199605210205.LAA24044@genesis.atrad.adelaide.edu.au> In-Reply-To: <199605190518.WAA12686@MediaCity.com> from "Brian Litzinger" at May 18, 96 10:18:15 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Litzinger stands accused of saying: > > > > We're trying to bring up a freeBSD box. The biggest problem so far > > is that we bring up the X server/client system (xfree86), and it just > > hangs. I think it's something to do with the mouse, because we've just > > specified /dev/mouse for the mouse driver. We have a bus mouse, and we've > > set all the params properly in xf86config, but we haven't filled in any of > > the make/model text strings (those don't seem to get used at all). So when Ok. A few questions : what sort of busmouse are you using? Microsoft, Logitech, Mouse Systems? Note that you really want a 3-button mouse for X. Also, are you certain it's a bus mouse and not a PS/2 mouse? Which version of FreeBSD, installed from where (CD or FTP?) You're correct about the make/model fields, they're just there so that it's possible to automagically build a database of cards, monitors and modes by processing the file. I don't think anyone actually _does_ this. > > we bring up X, we get the cursor and the standard backdrop stipple on the > > screen, but the mouse cursor won't move at all. We've tried switching to You're not starting X correctly if that's all you get 8) The 'best' way to start X is with xdm, either by running it out of /etc/rc.local, or in /etc/ttys. Both methods are discussed in the XFree86 installation notes. (/usr/X11R6/lib/X11/doc/* - not an intuitive location I admit) > > /dev/mse0, and that seems to cause the entire system to reboot in the > > middle of starting up X. We don't even get to the stipple screen, nor do This sounds like you may have a really obscure hardware problem, or you may have found a bug in the busmouse driver. /dev/mse0 is correct for the Microsoft Bus Mouse driver. I don't (believe I) have access to a working MS busmouse at this point in time, but if your problem persists I may be able to locate one. Alternatively, I would strongly advocate purchasing a low-cost 3-button serial mouse if you want a minimum-pain solution! > > we get a cursor. Maybe you know what our problem is or can recommend how > > we might be able to find out more information. We haven't found a phone > > number for dev support at FreeBSD, maybe there isn't one. We've tried > > emailing their tech support group, but we haven't heard a response for > > several days, so we can only assume they don't tackle questions on a case > > by case basis. No phone numbers, but I don't recall seing your question go past before, and I watch this list pretty closely 8) Yes, we do our best to tackle problems on a case-by-case basis; support and solving user problems are a major point of pride for us. > > Robert James Williamson #include <ASCI_Pic.h> -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605210205.LAA24044>