From owner-freebsd-amd64@FreeBSD.ORG Tue Nov 9 01:39:01 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2714616A4CE for ; Tue, 9 Nov 2004 01:39:01 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id B35E043D53 for ; Tue, 9 Nov 2004 01:39:00 +0000 (GMT) (envelope-from astrodog@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so381779rnf for ; Mon, 08 Nov 2004 17:38:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=RsIlHJknWxPGAwmTKLIbQCcf1S8qph5zJ1zlrBWOG2zIc6Mhqog/OxTcLxNIQfIwE1UdLRqv/OlOyya2uPWQr33u18b+cpV9p3dzp7VfUJk/mE8dIe78GHJYYuU/HDd6CJ1Nt2HyJHuOt0p+gM0ukYWxeW6PJHSUJHGSQzHkh84= Received: by 10.38.75.70 with SMTP id x70mr154764rna; Mon, 08 Nov 2004 17:38:51 -0800 (PST) Received: by 10.38.164.65 with HTTP; Mon, 8 Nov 2004 17:38:50 -0800 (PST) Message-ID: <2fd864e04110817381ca993fa@mail.gmail.com> Date: Mon, 8 Nov 2004 17:38:50 -0800 From: Astrodog To: freebsd-amd64@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Compaq 3000Z Laptops (And some misc. others) X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Astrodog List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Nov 2004 01:39:01 -0000 After browsing the lists for awhile for information on this problem, I figured I'd share my... findings, as it were, with interested parties. The showstopping glitch that appears to occur on the Compaq 3000Z Series of laptops relates to the keyboard test interrupt. As best as I can tell, Nvidia for the mobile version of their chipset, or Compaq, has remapped the keyboard test, to instead perform a system reboot. This behavior exists under any boot options, and the only known workaround I am aware of is to apply a patch to the kernel sources. As a result, for the past month or so, I've been tracking FreeBSD -CURRENT with the patch applied, and producing ISO Images of the modified setup. If there is a way to test for a specific chipset, and to use the patched code if it is detected, merging that on to the main tree would be most appreiated. The other major glitch appears to be in APIC support. I haven't tested this much though, as the above error is, in my opinion, a much larger issue. If, for whatever reason, there is no way to merge the patch, I can start making the -CURRENT snapshots we use internally avalibile, and anyone who is interested in getting a copy is more than welcome to e-mail me. Please let me know if there is anything else I can do to assist in troubleshooting these two problems. --- Harrison Grundy