Date: Thu, 21 May 1998 08:20:44 -0500 From: Dave Bender <bendede@startribune.com> To: "'djv@bedford.net'" <djv@bedford.net>, "'freebsd-questions@FreeBSD.ORG'" <freebsd-questions@FreeBSD.ORG> Subject: RE: The unending conflict: modems and mice Message-ID: <01BD8491.6FA153D0@MANNY>
next in thread | raw e-mail | index | archive | help
As suggested, here's the output from dmesg to troubleshoot my suspected modem/mouse conflict. A free AOL diskette to anyone who can point out what's goofy (aside from that silly offer):
freebee# dmesg
Copyright (c) 1992-1998 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
FreeBSD 2.2.6-RELEASE #0: Wed Mar 25 02:28:49 GMT 1998
jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC
CPU: Cyrix 6x86 (486-class CPU)
Origin = "CyrixInstead" Id = 0x520 DIR=0x2231 Stepping=2 Revision=2
real memory = 33554432 (32768K bytes)
avail memory = 30445568 (29732K bytes)
Probing for devices on PCI bus 0:
chip0 <generic PCI bridge (vendor=1106 device=0585 subclass=0)> rev 35 on pci0:0:0
chip1 <generic PCI bridge (vendor=1106 device=0586 subclass=1)> rev 37 on pci0:7:0
pci0:7:1: VIA Technologies, device=0x0571, class=storage (ide) [no driver assigned]
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 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
lpt1 at 0x378-0x37f on isa
lpt1 not probed due to I/O address conflict with lpt0 at 0x378
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: FIFO enabled, 8 bytes threshold
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <WDC AC34000L>
wd0: 3815MB (7814016 sectors), 7752 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (atapi): <BCD 24XM CD-ROM/VER 2.1>, removable, accel, dma, iordy
wcd0: 4125Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tray
wcd0: 120mm data disc loaded, unlocked
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: utp/bnc[*UTP*] address 00:10:4b:74:55:f9
npx0 flags 0x1 on motherboard
npx0: INT 16 interface
freebee#
Many thanks.
----------
From: CyberPeasant
Sent: Wednesday, May 20, 1998 10:37 PM
To: Dave Bender
Cc: freebsd-questions@FreeBSD.ORG
Subject: Re: The unending conflict: modems and mice
Dave Bender wrote after reformatting:
> I've run into what seems to be a perrenial
> problem for me on a PC: a mouse/modem conflict. I've dealt with
> this in DOS, then in Windows, and in WindowsNT (which I dumped in
> favor of FreeBSD).
>
> Now it appears to have reared its ugly head in FreeBSD.
>
> But this time I'm stumped as to where to turn. I'm new to Unix (at
> least sysAdmin stuff) and I'm not sure what to do.
>
> Here are symptoms I've seen:
>
> + When I enter the tip command, and type "AT" the machine freezes.
> I have to reboot.
>
> + In another iteration, tip froze, but if I moved the mouse I got
> all sorts of frenetic, weird output on the screen. I also had to
> reboot.
Post the output of dmesg after a boot. This sounds like an IRQ problem.
> The modem is a brand spanking new US Robotics jumperless Plug and
> Play 56K modem (motherboard /bios is also PnP -- does that matter?)
That's spelled "Plug and Pray" or "Plug and Prey". :)
> so I don't know how to tell what port/irq it selected. How can I
> find that out from the OS?
(Dmesg)
> The mouse IO/card is an old generic thing that's been with me for
> many moons. (It worked OK when NT was on this particular machine.)
> The mouse is self is a $5 computer show special.
It ain't the mouse, probably.
> I unplugged the mouse and rebooted, but got the same behavior with
> the freezing at the AT Specifically I entered:
>
> $tip cuaa0b connected <freeeeze>
Sure that's the right device name? The usuals are /dev/cuaa0 ...1 ...2,
..3 corresponding to COM1,...4.
> If I don't use the modem (don't enter a tip command) the mouse
> works fine. It shows up and a test in Xwindows says it's functional.
Then it is. IO or IRQ conflict, no doubt.
Dave
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?01BD8491.6FA153D0>