Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!vic.news.telstra.net!act.news.telstra.net!psgrain!newsfeed.internetmci.com!news.cftnet.com!ns2.mainstreet.net!sloth.swcp.com!news.swcp.com!russo
From: russo@bogoflux.losalamos.nm.us (Thomas Russo)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Help me catch this mouse...
Date: 18 Jun 1996 05:57:00 GMT
Organization: First "Bob"tist Church and Loan of Los Alamos, Inc. --- Eternal
Salvation, Easy Monthly Payments
Lines: 112
Message-ID: <RUSSO.96Jun17235700@bogoflux.losalamos.nm.us>
NNTP-Posting-Host: bogoflux.losalamos.nm.us
...input, that is.
I just upgraded my dinosaur PC from a 40MHz 386 with 8MB and an ET4000
VGA card, on which I've been running FreeBSD (386BSD with patchkits,
FreeBSD 1.1, 1.1.5, and now 2.1.0-R) for ages (it took ages to run,
too). Tonight I installed an Amptron 7700 PCI motherboard with 16MB
and a Cyrix 6x86/120+ processor, and replaced the old VGA with a
Diamond Stealth 64 S3-Trio64. I'm thrilled to bits how fast it is by
comparison. Every thing works Just Fine, except my mouse, so I can't
run X (the server starts up Just Fine, but the cursor doesn't go
anywhere when I move the mouse) and use all the pretty colors that the
Diamond promises unless I use Microsloth Windoze (gag).
Here's the deal: Running FreeBSD 2.1.0-RELEASE. (output of initial
probe below). I've got an IMSI mouse (switch selectable
MouseSystems/Microsoft) which served me quite well with the old
motherboard and an ISA "multi-io" card (using the latter is not an
option as all 4 of my new ISA slots are taken). Now, when I run
MS-DROSS/Windoze on the newly upgraded system, with the mouse plugged
into the on-board "COM1" port, DOG/Windoze programs recognise it and
function with no problem. But I can't get FreeBSD to talk to it at
all. I've tried disabling the FIFO of the 16550A on sio0. I've tried
fiddling with baud rates and assorted sttyisms (I started with the
stuff that's in rc.serial and fiddled from there). I've looked at the
output of cat < /dev/ttyd0 for signs that the mouse is actually
putting characters on that device. Nada. If I pick a baud rate like
9600 for ttyd0, I get hundreds of nulls with the odd random character
when the mouse is just sitting there, and it looks like I can make
some random characters by clicking the mouse button now and then. If
I pick 1200 I might get a burst of 10 or 12 nulls, but other than that
I get nothing.
Has anyone else had this sort of problem with a PCI motherboard with
on-board serial ports? I wish there were jumpers or such so that I could
be sure that the IRQs are right; the IO addresses are, and all of
the DOS stuff says the IRQs are right, but the BIOS setup only lets me
choose whether it's "COM1, COM2, COM3, or COM4", not whether it's "IO
0x3f8-0x3ff and IRQ 4".
Anyhow, I realize this probably doesn't help pin down my problem.
Please excuse my rambling. I'm tired.
If anyone has a hint or two for me that might get me on track, I would
really appreciate it. I've been tinkering for hours and am no closer
to having a working mouse than I was when I started.
Here's what my system prints out on start-up. I don't see from this
that there's anything conflicting. Oh, and why, oh, why, does the
6x86 probe as a "i486DX (486-class CPU)" when it should be more like a
Pentium (or so I am told)? Microsoft Flight Simulator setup probes it
the same way.
FreeBSD 2.1.0-RELEASE #0: Fri Jun 14 00:56:33 MDT 1996
root@bogoflux:/usr/src/sys/compile/BOGOFLUX
CPU: i486DX (486-class CPU)
real memory = 16777216 (16384K bytes)
avail memory = 14831616 (14484K bytes)
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 flags 0x82 on isa
sio0: type 16550A fifo disabled <---- because the mouse is here
sio1 not found at 0x2f8 (there is one on the MB, but I
turned it off in SETUP)
sio2 at 0x3e8-0x3ef irq 5 on isa
sio2: type 16550A
sio3 not found at 0x2e8
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
lpt1 not found at 0xffffffff
lpt2 not found at 0xffffffff
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.2MB 5.25in
fd1: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <Maxtor 7850 AV>
wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <MATSHITA CR-581/1.05>, removable, accel, iordis
wcd0: 689Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray
wcd0: no disc inside, unlocked
aha0 at 0x334-0x337 irq 9 drq 6 on isa
aha0 waiting for scsi devices to settle
(aha0:2:0): "WangDAT Model 3100 02.2" type 1 removable SCSI 2
st0(aha0:2:0): Sequential-Access density code 0x13, drive empty
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 12 on isa
ep0: aui/bnc/utp[*UTP*] address 00:20:af:26:af:4e irq 12
npx0 on motherboard
npx0: INT 16 interface
pas0 not probed due to drq conflict with aha0 at 6
sb0 at 0x220 irq 10 drq 1 on isa
sb0: <SoundBlaster 16 4.13>
sbxvi0 at 0x0 drq 5 on isa
sbxvo0: <SoundBlaster 16 4.13>
sbmidi0 at 0x330 on isa
<SoundBlaster MPU-401>
opl0 at 0x388 on isa
opl0: <Yamaha OPL-3 FM>
mpu0 not probed due to I/O address conflict with sbmidi0 at 0x330
uart0 not probed due to I/O address conflict with sbmidi0 at 0x330
Probing for devices on the PCI bus:
chip0 <Intel 82437 (Triton)> rev 2 on pci0:0
chip1 <Intel 82371 (Triton)> rev 2 on pci0:7
vga0 <VGA-compatible display device> rev 0 int a irq 11 on pci0:20
--
Tom Russo WWW: http://www.swcp.com/~russo/
Never put off until tomorrow what you can do today, because if you like it
today you can do it again tomorrow.