From owner-freebsd-current@FreeBSD.ORG Fri Jul 18 06:43:49 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9342637B401 for ; Fri, 18 Jul 2003 06:43:49 -0700 (PDT) Received: from secure-info.ca (jeamland.ca [66.11.170.102]) by mx1.FreeBSD.org (Postfix) with SMTP id 71B0443F3F for ; Fri, 18 Jul 2003 06:43:48 -0700 (PDT) (envelope-from stark@jeamland.ca) Received: (qmail 88321 invoked by uid 1029); 18 Jul 2003 13:45:08 -0000 Message-ID: <20030718134508.88320.qmail@secure-info.ca> From: "stark" In-Reply-To: <20030718105347.GA9225@speedy.unibe.ch> To: Tobias Roth Date: Fri, 18 Jul 2003 09:45:08 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: current@freebsd.org cc: "M. Warner Losh" Subject: Re: Problems with fxp0 on T30 with 5.1-RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 13:43:49 -0000 > On Thu, Jul 17, 2003 at 09:58:00AM -0600, M. Warner Losh wrote: > kevin oberman suggested the use of the ps2 utility for thinkpads. i > did not have the chance to try it out myself. I also didn't have the time to look at it the last day and a half, but I have time this weekend so I'll definitely investigate. The part that I'm confused about is "what's the 'ps2' utility?" There's no mention of it in /usr/ports and the only things I can find with google are a DOS program by that name. Is that what you're referring to? If so, where do I get it? > the only odd thing is that 5.0 did not have this bug, while 5.1 has > it. if it needs fixing is up to you, i am now happy with the current > solution. but then, the default bios settings are so stupid that it may > not be feasable to do anything about it. This is the part that confuses me as well, but from 5.0 to 5.1 the fxp driver was completely re-written to use a different API so tracking down the specific problem is going to suck :( I also have XP on the laptop (for work stuff, honest! :) and it's working fine as well, so it's definitely a bug in 5.1. I'll also try getting -CURRENT /usr/src off another system and recompiling from scratch to see if that fixes the issue (not having net sucks! :) Dana Lacoste Ottawa, Canada PS: Someone had said that although they might be able to find the bug they'd need the affected hardware. Well, if you're between Toronto and Quebec City I could arrange a field trip for the weekend, but I'm not shipping my laptop to Europe :)