From owner-freebsd-hackers Fri Mar 28 08:40:58 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA19464 for hackers-outgoing; Fri, 28 Mar 1997 08:40:58 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA19441; Fri, 28 Mar 1997 08:40:48 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id JAA16977; Fri, 28 Mar 1997 09:40:36 -0700 (MST) Date: Fri, 28 Mar 1997 09:40:36 -0700 (MST) Message-Id: <199703281640.JAA16977@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Ian Kallen Cc: freebsd-mobile@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: (Dell Latitude) psm0/sc0 conflicts killing X? In-Reply-To: References: X-Mailer: VM 6.22 under 19.14 XEmacs Lucid Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I don't know what else changed when I went from 2.2-GAMMA w/o PAO (Used > the zp drivers from the 3c589) to 2.2.1-RELEASE... The queing patches were added to the console driver. And, it works fine on my 2.2 desktop box and on my laptop, both running Xig's package. The queing patches were necessary to avoid lockups on my desktop using Xig's server, hence the reason I pushed for them in the release. > I'm on a Dell XPi p100 > and Xinside's X server was doing fine w/ 800X600 @256 but since I ran the > upgrade and applied the PAO patches, I've had to explicitly re-enable psm0 > by booting w/ -c (other X won't start at all) but the keyboard is dead > once I'm in X. It works fine out of X? > I tried reinstalling Xinside but that made no > differnce. Any comments or suggestions (if a look @ my kernel config > is needed to comment on it, I'll send that along as well) appreciated! Hmm, can you send me your config file in private email, and I'll compare it to mine at work? Nate