On Fri, May 21, 1999 at 06:02:17PM +0200, Nick Hibma wrote: > > < # atkbdc0 controlls both the keyboard and the PS/2 mouse > > < controller atkbdc0 at isa? port IO_KBD > > < device atkbd0 at isa? irq 1 > > < device psm0 at isa? irq 12 > > --- > > > # atkbdc0 controls both the keyboard and the PS/2 mouse > > > controller atkbdc0 at isa? port IO_KBD > > > device atkbd0 at atkbdc? irq 1 > > > device psm0 at atkbdc? irq 12 > > Looks ok. > > > < device npx0 at isa? port IO_NPX irq 13 > > --- > > > device npx0 at nexus? port IO_NPX irq 13 > > Mistake (see the dmesg)
Yep - I'll fix that one. > 140c118,119 > < device sc0 at isa? > --- > > device sc0 at isa? > > > > Why does this one show up? It shouldn't. You might want to retype it to > make sure there is no bogus char in there somewhere. There's a space after the "?". I got rid of it, but I can't see how THAT would break anything. > > > #controller umass0 > > > #device ums0 > > > #device ukbd0 > > > #device ulpt0 > > > #device uhid0 > > > #device ugen0 > > FYI, this GENERIC is not the one from yesterday evening (sorting of the > elements above has changed). > > I can't see anything obviously wrong. > > Nick I don't see anything obviously wrong either. It DOES reset the keyboard during the boot (the LEDs flash), so the probe definitely does see the device (not to mention that I can use it in the loader, which is how I found out about this - I booted the new kernel manually in single-user - part of my standard "be careful" stuff - and then found it locked when it asked me for the root shell!) I don't see anything in the commit logs from my early-morning CVSUP that would indicate anything significant happening in the last 24 hours, but I'll give it another build and see what happens. -- -- Karl Denninger (k...@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-hackers" in the body of the message
