From owner-freebsd-current Tue Jul 3 8: 7: 4 2001 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id ADDB537B407; Tue, 3 Jul 2001 08:06:56 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id RAA25967; Tue, 3 Jul 2001 17:06:55 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: current@freebsd.org Subject: Still weird psm behaviour in -CURRENT From: Dag-Erling Smorgrav Date: 03 Jul 2001 17:06:54 +0200 Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I hit the famed "psm probed twice" problem on my laptop last week (trackpoint didn't work at all), and tried to remove the psm and atkbd hints as advised. This resulted in a laptop with no trackpoint and no keyboard ("dumb, dumb fun" sez Juliana Hatfield), but interestingly, when I then rebooted with the previous kernel, the trackpoint worked. Both kernels were identical except for the hints, which I compile statically. No fiddling with the BIOS or anything. I'm now using the exact same kernel that didn't work before, with the exact same hints, on the exact same hardware, and I get the exact same PnP "can't assign resources" messages as before, but the trackpoint works. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message