From owner-freebsd-hackers@FreeBSD.ORG Sun Dec 7 09:13:25 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D5B716A4CE for ; Sun, 7 Dec 2003 09:13:25 -0800 (PST) Received: from out-2.mail.amis.net (out-2.mail.amis.net [212.18.32.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8EE543F93 for ; Sun, 7 Dec 2003 09:13:23 -0800 (PST) (envelope-from blaz@si.FreeBSD.org) Received: from localhost (in-3.mail.amis.net [212.18.32.22]) by out-2.mail.amis.net (Postfix) with ESMTP id BC3AE7CE8 for ; Sun, 7 Dec 2003 18:13:22 +0100 (CET) Received: from in-3.mail.amis.net ([127.0.0.1]) by localhost (in-3.mail.amis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 68098-01 for ; Sun, 7 Dec 2003 18:13:21 +0100 (CET) Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5]) by in-3.mail.amis.net (Postfix) with ESMTP id AD671585889; Sun, 7 Dec 2003 18:13:21 +0100 (CET) Date: Sun, 7 Dec 2003 18:13:21 +0100 (CET) From: Blaz Zupan X-X-Sender: blaz@titanic.medinet.si To: freebsd-hackers@freebsd.org Message-ID: <20031207180022.B63497@titanic.medinet.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at amis.net Subject: Reward for fixing keyboard support in FreeBSD, apply within X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2003 17:13:25 -0000 In the last couple of days I've been fighting with a evaluation IBM BladeCenter. For those that don't know, it's a 7U rackmount box with 14 slots that can take one PC each. http://www.ibm.com/servers/eserver/blades/ All the PC's share a single CD, floppy and the builtin KVM. CD, floppy and the KVM are USB connected. There are two problems with FreeBSD on this box: 1. No FreeBSD version boots from CD on this box. Tried with 4.x and 5.x. Both complain that they can't find their own boot device and don't know how to load the kernel. There are some signs that booting from any USB connected CDROM on any hardware is broken. 2. The more troubling problem is that upon bootup the keyboard does not work. The problem is that there are actually two USB keyboards. The first one is apparently some dummy device connected to the KVM while the second is the working keyboard. Logging in through the network and running "kbdcontrol -k /dev/kbd2" activates the keyboard. The problem is that only a single keyboard can be active at any time in FreeBSD and on boot the first detected keyboard becomes active. As the first USB keyboard on the Bladecenter is not actually connected anywhere, the keyboard is basically dead as soon as the FreeBSD kernel takes over. The box does not have any serial ports, so a serial console is out of the question. Needless to say, both Windows and Linux work just fine on the Bladecenter. The main reason for working keyboard support is, that both under Windows and Linux, *all* keyboards are active at the same time. On FreeBSD only a single keyboard can be active at any time. My company would really like to deploy the Bladecenter as it is otherwise a very solid solution for our problem. But 99.9% of our servers are FreeBSD and the above problems are a real showstopper. That's why I'm offering a reward to anybody who produces working patches that are polished enough to be included both in -stable and -current. I will do my best to provide all the neccesary information as well as an account on the box. I don't have much time left, as I will have to return the evaluation box soon, so if you think you are able to solve the problems, send me an email *now*.