[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [3.2] Can't open /dev/wsmouse (lame rodent)

To: misc_(_at_)_openbsd_(_dot_)_org
Subject: Re: [3.2] Can't open /dev/wsmouse (lame rodent)
From: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>
Date: Thu, 1 May 2003 19:39:42 -0400
Mail-followup-to: Chuck Yerkes <chuck+obsd_(_at_)_2003_(_dot_)_snew_(_dot_)_com>, misc_(_at_)_openbsd_(_dot_)_org
Reply-to: misc_(_at_)_openbsd_(_dot_)_org

Quoting Harry Putnam (hgp_(_at_)_sbcglobal_(_dot_)_net):
> Harry Writes concerning non-working mouse:
> > What do I need to do here?
> 
> A private poster suggested I include dmesg output.
> 
> >From dmesg following a reboot
> 
> [...]
> wsmouse0 at pms0 mux 0
> [...]

This is LIKE a dmesg, but oddly isn't a dmesg.  It's part of a dmesg.
Which usually doesn't help as much as you think.

References:
- [3.2] Can't open /dev/wsmouse (lame rodent)
  - From: Harry Putnam
- Re: [3.2] Can't open /dev/wsmouse (lame rodent)
  - From: Harry Putnam

Prev by Date: Re: IBM eServer x305 Multi-disk Boot Problem (3.3-release)
Next by Date: RAIDFRAME 120GB disks
Previous by thread: Re: [3.2] Can't open /dev/wsmouse (lame rodent)
Next by thread: yet another darpa news/olds story (zdnet)
Index(es):
- Date
- Thread

Visit your host, monkey.org