Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!psgrain!percy!agora!rgrimes From: rgrimes@agora.rain.com (Rodney Grimes) Subject: Re: HELP! 386BSD kbd problem on notebook : -( Message-ID: <C4sH0r.FG6@agora.rain.com> Organization: Open Communications Forum References: <9309019.27177@mulga.cs.mu.OZ.AU> <summer.733616213@mullian.ee.Mu.OZ.AU> Date: Thu, 1 Apr 1993 05:10:03 GMT Lines: 34 summer@ee.mu.OZ.AU (Mark Summerfield) writes: >I wrote: >>I have just tried to boot the pk-0.2 dist.fs disk on a new 486 notebook >>(of a fairly generic nature). >>Everything goes OK until the shell prompt "#", when I find I can't type >>anything (well, I can, but it doesn't recognise the keyboard :-( ) >>Perhaps I need a different console driver? If so, is there a site somewhere >>with a suitable dist.fs/fixit.fs image? Or is the problem something else? >I've kind of solved my own problem -- if I use the *unpatched* dist.fs then >everything's OK, so my new question is: >When I install 386bsd, and apply the 0.2.2 patchkit, WHICH PATCH IS GOING >TO KILL MY KEYBOARD?! If I get a new console driver up and running first, >will this avoid the problem? If so, which console driver? The patch that was killing your keyboard is the OLD version of patch00083 that apperead in patchkit 0.2.1. The patch00083 in patchkit 0.2.2 is a more or less complete rewrite of pccons.c's probe routines. It should work on ALL systems. We have not had a keyboard failure reported with this patch yet. So I would not worry about pathckit 0.2.2 breaking your keyboard. If I am wrong about patch00083 form patchkit 0.2.2 breaking someones keyboard, please let me KNOW ASAP. -- Rod Grimes rgrimes@agora.rain.com Accurate Automation Company All opinions belong to me and my company! Get your free copy of 386bsd from agate.berkeley.edu:/pub/386BSD via ftp! An out of work contractor... You need unix work done.... Send me your project!