Keyboard not responding, Dell PE2650

[Russell P. Sutherland]

I have a fairly reproduceable problem with a new Dell PowerEdge 2650:

 After the machine has booted in a headless state (no keyboard
 or monitor) and then one inserts a keyboard into either the
 front or rear PS/2 plugs, there is no communication input from
 the keyboard to the server. The monitor/VGA port communication
 is fine.

 I believe the keyboard repsonse  is _normal_ if the keyboard
 is plugged in while the machine is powering up.

Has anyone else experienced this problem? And if so how was the issue
resolved?

Here is a copy of dmesg output from the machine:

Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.9-RELEASE #0: Wed Oct 29 13:19:21 EST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/ZEBRA
Timecounter i8254  frequency 1193182 Hz
Timecounter TSC  frequency 2784317344 Hz
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2784.32-MHz 686-class CPU)
  Origin = GenuineIntel  Id = 0xf29  Stepping = 9
  
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Hyperthreading: 2 logical CPUs
real memory  = 536805376 (524224K bytes)
avail memory = 518549504 (506396K bytes)
Preloaded elf kernel kernel at 0xc040f000.
Warning: Pentium 4 CPU: PSE disabled
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 9 entries at 0xc00fc430
npx0: math processor on motherboard
npx0: INT 16 interface
pcib0: Host to PCI bridge on motherboard
pci0: PCI bus on pcib0
pci0: unknown card (vendor=0x1028, dev=0x000c) at 4.0 irq 11
pci0: unknown card (vendor=0x1028, dev=0x0008) at 4.1 irq 10
pci0: unknown card (vendor=0x1028, dev=0x000d) at 4.2 irq 7
pci0: ATI Mach64-GR graphics accelerator at 14.0
atapci0: ServerWorks CSB5 ATA100 controller port 
0x8b0-0x8bf,0x8d8-0x8db,0x8d0-0x8d7,0x8c8-0x8cb,0x8c0-0x8c7 at device 15.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: OHCI USB controller at 15.2 irq 5
isab0: PCI to ISA bridge (vendor=1166 device=0225) at device 15.3 on pci0
isa0: ISA bus on isab0
pcib1: Host to PCI bridge on motherboard
pci1: PCI bus on pcib1
skc0: SysKonnect Gigabit Ethernet (V2.0) port 0xcc00-0xccff mem 
0xfcf0-0xfcf03fff irq 11 at device 6.0 on pci1
skc0: SK-9843 V2.0 Gigabit Ethernet 1000Base-SX Adapter
sk0: Marvell Semiconductor, Inc. Yukon on skc0
sk0: Ethernet address: 00:00:5a:9c:32:26
miibus0: MII bus on sk0
e1000phy0: Marvell Semiconductor 88E1000* gigabit PHY on miibus0
e1000phy0:  1000baseSX-FDX, auto
pcib8: PCI to PCI bridge (vendor=8086 device=b152) at device 8.0 on pci1
pci2: PCI bus on pcib8
fxp0: Intel 82558 Pro/100 Ethernet port 0xdce0-0xdcff mem 
0xfcd0-0xfcdf,0xfcaff000-0xfcaf irq 10 at device 4.0 on pci2
fxp0: Ethernet address 00:02:b3:da:62:5a
inphy0: i82555 10/100 media interface on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp1: Intel 82558 Pro/100 Ethernet port 0xdcc0-0xdcdf mem 
0xfcc0-0xfccf,0xfcafe000-0xfcafefff irq 7 at device 5.0 on pci2
fxp1: Ethernet address 00:02:b3:da:62:5b
inphy1: i82555 10/100 media interface on miibus2
inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pcib2: Host to PCI bridge on motherboard
pci3: PCI bus on pcib2
pcib3: Host to PCI bridge on motherboard
pci4: PCI bus on pcib3
bge0: Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfc91-0xfc91 
irq 11 at device 6.0 on pci4
bge0: Ethernet address: 00:0b:db:e6:e4:1c
miibus3: MII bus on bge0
brgphy0: BCM5703 10/100/1000baseTX PHY on miibus3
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, 
auto
bge1: Broadcom BCM5703 Gigabit Ethernet, ASIC rev. 0x1002 mem 0xfc90-0xfc90 
irq 10 at device 8.0 on pci4
bge1: Ethernet address: 00:0b:db:e6:e4:1d
miibus4: MII bus on bge1
brgphy1: BCM5703 10/100/1000baseTX PHY on miibus4
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, 
auto
pcib4: ServerWorks host to PCI bridge(unknown chipset) on motherboard
pci5: PCI bus on pcib4
pcib9: PCI to PCI bridge (vendor=8086 device=0309) at device 8.0 on pci5
pci6: PCI bus on pcib9
pci6: unknown card (vendor=0x9005, dev=0x00c5) at 6.0 irq 7
pci6: unknown card (vendor=0x9005, dev=0x00c5) at 6.1 irq 11
aac0: Dell PERC 3/Di mem 0xf000-0xf7ff irq 7 at device 8.1 on pci5
aac0: i960RX 100MHz, 118MB cache memory, optional battery present
aac0: Kernel 2.7-1, Build 3170, S/N c061d3
aac0: Supported Options=75cWCACHE,DATA64,HOSTTIME,WINDOW4GB,SOFTERR,NORECOND,SGMAP64
pcib5: ServerWorks host to PCI bridge(unknown chipset) on motherboard
pci7: PCI bus on pcib5
pcib6: ServerWorks host to PCI bridge(unknown chipset) on motherboard
pci8: PCI bus on pcib6
pcib7: ServerWorks host to PCI bridge(unknown chipset) on motherboard
pci9: PCI bus on pcib7
orm0: Option 

Re: Keyboard not responding, Dell PE2650

[Charles Swiger]

On Nov 11, 2003, at 9:14 AM, Russell P. Sutherland wrote:
I have a fairly reproduceable problem with a new Dell PowerEdge 2650:

 After the machine has booted in a headless state (no keyboard
 or monitor) and then one inserts a keyboard into either the
 front or rear PS/2 plugs, there is no communication input from
 the keyboard to the server. The monitor/VGA port communication
 is fine.
 I believe the keyboard repsonse  is _normal_ if the keyboard
 is plugged in while the machine is powering up.
Has anyone else experienced this problem? And if so how was the issue
resolved?
See man atkb:

   Driver Flags
 The atkbd driver accepts the following driver flags.  They can be 
set
 either in the kernel configuration file (see config(8)), or else 
in the
 User Configuration Menu at boot time (see boot(8)).

 bit 0 (FAIL_IF_NO_KBD)
   By default the atkbd driver will install even if a keyboard 
is not
   actually connected to the system.  This option prevents the 
driver
   from being installed in this situation.

You can also change this line in /usr/src/sys/i386/conf/GENERIC:

device  atkbd0  at atkbdc? irq 1 flags 0x1

...or your own kernel config file, removing the flags 0x1, and 
rebuilding your kernel.  That will let you plug in a keyboard later and 
have it be recognized.

--
-Chuck
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Keyboard not responding, Dell PE2650

[Olaf Hoyer]

On Tue, 11 Nov 2003, Russell P. Sutherland wrote:

 I have a fairly reproduceable problem with a new Dell PowerEdge 2650:

  After the machine has booted in a headless state (no keyboard
  or monitor) and then one inserts a keyboard into either the
  front or rear PS/2 plugs, there is no communication input from
  the keyboard to the server. The monitor/VGA port communication
  is fine.

  I believe the keyboard repsonse  is _normal_ if the keyboard
  is plugged in while the machine is powering up.

 Has anyone else experienced this problem? And if so how was the issue
 resolved?

Hi!

Well, I just had a bunch of 2650's (german version) on the desk, that
were deployed under Redhat advanced server.

during tests, the machine was rebooted, and keyboard was plugged in
later. No hassle.

I had a short time slot to play with it under FreeBSD, but did not run
in such an issue. does not mean much, I had short time...

I ran into a similar thing on a HP/Compaq Proliant 380 G3, with a
-current from yesterday.

Build a custom kernel, and after the bootloader kicked it, the keyboard
was dead. Build of new kernel (basically a GENERIC with SMP support
activated) worked then...

Which is the OS type in BIOS?
(I remember that there is sometimes the option, at least Compaq has it)

Also, you have the opportunity of a serial console redirection to com1
via BIOS hardware, works like a charm.

HTH
Olaf


-- 
Olaf Hoyer[EMAIL PROTECTED]
Fuerchterliche Erlebniss geben zu raten,
ob der, welcher sie erlebt, nicht etwas Fuerchterliches ist.
(Nietzsche, Jenseits von Gut und Boese)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]