Date: Wed, 13 Nov 1996 10:30:43 -0700 (MST) From: Nate Williams <nate@mt.sri.com> To: sos@freebsd.org Cc: nate@mt.sri.com (Nate Williams), jkh@time.cdrom.com, wangel@wgrobez1.remote.louisville.edu, freebsd-current@freebsd.org Subject: Re: your mail Message-ID: <199611131730.KAA00439@rocky.mt.sri.com> In-Reply-To: <199611131655.RAA16645@ravenock.cybercity.dk> References: <199611131509.IAA00027@rocky.mt.sri.com> <199611131655.RAA16645@ravenock.cybercity.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > > Has anyone been looking into why the Keyboard spastically locks up? We > > > > know there is the 'band-aid'(echo "set ipending=2"|gdb -k -w /kernel > > > > /dev/mem)by telnetting into the 'locked' machine by another machine. Not > > > > a problem, and it works, but what if people don't have another machine? > > > > > > That's been fixed in -current with Soren's latest syscons changes. > > > > The fix also broke PS/2 mouse support. :( :( > > I know :(, but so long as we occasionally looses an interrupt, there > is not much else to do. Or merge syscons and the ps/2 mousedriver. > (which I have on my TODO list) Are we losing interrupts, or is there something else going on? Also, I just spoke with someone (the recent psm.c author) who is willing to do the work to integrate the two, so hopefully you two can resolve this. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611131730.KAA00439>