I have a client that has several dell machines, when he boots without a keyboard he gets: atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 but no: atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 This used to work, then was broken by someone trying to "do the right thing". We need the keyboards to be hot swappable. I recommend that the next dork that breaks this should have to reenact the lye scene from Fight Club. No other OS has this problem. Also, breaking this in -stable is super lame, c'mon can't we do better? -- - Alfred Perlstein - Research Engineering Development Inc. - email: bright@mu.org cell: 408-480-4684
On Fri, 2 Apr 2004 07:05, Alfred Perlstein wrote:> I have a client that has several dell machines, when he boots without > a keyboard he gets: > > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > > but no: > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > > This used to work, then was broken by someone trying to "do the right > thing".I have some motherboards like that too, they've always been broken. I deal with it by rolling a release with the flags set to force PS/2 keyboard detection. I'd like it fixed but I don't have the clue to do so. The bit *I* see as broken is keybaord detection. Dunno if its the same for you.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5
Alfred Perlstein wrote:> I have a client that has several dell machines, when he boots without > a keyboard he gets: > > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > > but no: > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > > This used to work, then was broken by someone trying to "do the right > thing".jhb, three years ago, sys/i386/conf/GENERIC 1.255> We need the keyboards to be hot swappable.Use USB keyboards... The commit message of 1.255 suggests that you broke hotplugging for those again, have you checked this? -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 260 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20040402/cd18a539/attachment.bin
On Thu, Apr 01, 2004 at 01:35:59PM -0800, Alfred Perlstein wrote:> I have a client that has several dell machines, when he boots without > a keyboard he gets: > > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > > but no: > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0Did you read atkbd(4) man page carefully? Did you try to use 'flags 0x0'? Eugene
Alfred Perlstein <alfred@freebsd.org> writes:> I have a client that has several dell machines, when he boots without > a keyboard he gets: > > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > > but no: > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > > This used to work, then was broken by someone trying to "do the right > thing". > > We need the keyboards to be hot swappable. I recommend that the next > dork that breaks this should have to reenact the lye scene from Fight > Club. > > No other OS has this problem. Also, breaking this in -stable is > super lame, c'mon can't we do better?In this context, detection of Fujitsu-Siemens-Computers KBPC S2 keyboards (looks like normal PS/2 stuff) has also been broken on -CURRENT somewhen after 5.1. If some of such breakage has propagated into -STABLE (via MFC), then the person who did the original change ought to sit down and clear things up. However, I have been unable to identify a "suspicious" commit. If however you need to boot without keyboard and plug one in later, then you cannot go with the default flags of 0x1 for this will disable the _driver_ when no keyboard is found at boot time. Change it to 0x0, 0x2 or 0x3, whichever works well for you. I wonder what this whole mess with the keyboard detection/nondetection and flags=0x1 is about. 0x0 should be the default, if someone knows he won't ever need the driver (headless), he can remove it from the kernel. -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95