-*- indented-text -*- T H E K E Y B O A R D B L A C K L I S T F O R F L O Y D Unfortunately, there are some floyd-incompatible keyboard, or keyboard+motherboard(or chipset ?) combination. The BLACKLIST hereunder is collected by the authour, and I am hoping some other guys make it grow (actually I don't want this list won't grow long, though). To test your keyboard is floyd-compatibility, use howmanymoretimes.c which may be included in the floyd distribution. However, this test program may not detect all the disorders described below. PRODUCT NAME: MICROSOFT `Natural' Elite PRODUCT ID: 71305-584-92277791-18308 SYMPTOM: Slow IOCTL() in combination with a certain motherboard. The Encountered combination was MICROSOFT `Natural' + GIGABYTE 6BA (SLOT1 AT Board). `Natural' is connected to GIGABYTE 6BA's AT keyboard interface via PS/2->AT conversion cable. On 6BA, Celeron 300A SEPP (no overclock) + 128Mb DIMM are equipped. The chipset is 440BX. MAJOUR APPARENT DISORDER: 1) While any LED is blinked by floyd, it generates spurious characters as if it is chattering. 2) Floyd's %CPU goes up high up to 30-40% even if the load average is just in 0.00-0.02 range. If floyd is watching eth0 $ uptime 11:26am up 6 min, 1 user, load average: 0.00, 0.13, 0.08 $ psgrep floyd USER PID %CPU %MEM SIZE RSS TTY STAT START TIME COMMAND root 198 4.2 0.2 824 300 ? S 11:21 0:13 /usr/local/bin/floyd -v -C root 199 0.0 0.2 824 288 ? S 11:21 0:00 /usr/local/bin/floyd -v -ES root 200 0.0 0.2 824 284 ? S 11:21 0:00 /usr/local/bin/floyd -v -pi ul0 -N STRUGGLE: Tried to use XKB (normal setting in my environment is `XkbDisable') for X, but it took no effect. XFree86 supports this keyboard: there is a file /var/X11R6/lib/xkb/geometry/microsoft, and I thought XKB might help (in vain). Disabling/Enabling CMOS setup on `typematic' did not take any effect. Nor `Delayed Transaction' in CMOS setup was solution. SOLUTION: Throw away the mother or keyboard. The `Natural' worked with no problem on my other old motherboards. PRODUCT NAME: FKD46AK110P (FCC ID maybe) PRODUCT NAME: BTC 5100 (FCC ID: E5X5R5BTC-5100) SYMPTOM: When the NumLock led is blinked by floyd, spurious NumLock shift occurs. These two are small 84key `space saver' keyboard, in which NumLock key is used to map 10key part on the right half of the alphabet part: the use of NumLock key is different from that in normal pc101/102/109 full keyboards. SOLUTION: Do not use floyd on NumLock LED. PRODUCT NAME: PC101/102/109 full keyboards Most of the ordinary full keyboards the authour encountered were floyd compatible. If there is no spurious character input, nor spurious mode shift, and the floyd's %CPU displayed via `top' or `ps' command is not so high (at most 3-5% range in -p mode), maybe the keyboard is floyd-compatible. Even in those floyd-compatible keyboards, when LED is blinking too fast (ie. floyd -E -S [1-5] : watching eth0 with 1 to 5msec sleep, and eth0 traffic is high), your console may raise warning "Keyboard timeout [2]". This warning is not so serious, but in such case, `sleep' value may have be increased to 50-90msec order (floyd -ES50 to -Es90). In the packet load mode, default `sleep' is automatically set to 10msec (50msec is the default of the load average mode) unless -s is not explicitly specified. You can select sleep longer than 100msec, but LED may not look like ethernet traffic LED.