From owner-freebsd-questions@FreeBSD.ORG Sun May 15 08:36:49 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2215106566B for ; Sun, 15 May 2011 08:36:49 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de (mx01.qsc.de [213.148.129.14]) by mx1.freebsd.org (Postfix) with ESMTP id A48398FC12 for ; Sun, 15 May 2011 08:36:49 +0000 (UTC) Received: from r55.edvax.de (port-92-195-63-204.dynamic.qsc.de [92.195.63.204]) by mx01.qsc.de (Postfix) with ESMTP id EFD353C9C1; Sun, 15 May 2011 10:36:46 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id p4F8akh8001518; Sun, 15 May 2011 10:36:46 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Sun, 15 May 2011 10:36:46 +0200 From: Polytropon To: Rob Clark Message-Id: <20110515103646.7558ddb2.freebsd@edvax.de> In-Reply-To: <117637.44743.qm@web111903.mail.gq1.yahoo.com> References: <117637.44743.qm@web111903.mail.gq1.yahoo.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-questions@freebsd.org Subject: Re: No keyboard after ports update, 2x moused_enable="YES" culprit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 May 2011 08:36:50 -0000 Please allow me a technical sidenote: On Sat, 14 May 2011 20:53:27 -0700 (PDT), Rob Clark wro= te: > Trying the obvious first, I unplugged the keyboard and plugged it > back in the ps2 port, and keyboard worked immediately -- this > was repeatable.=A0=20 Do _NOT_ hotplug the PS/2 port! It's not capable of that! I've seen myself in the past that trying so caused a mainboard to fly into the garbage can - as hotplugging the keyboard seemed to have damaged the PS/2 port (it didn't work anymore, with no keyboard). However, you actually CAN do this with USB. And I've done hotplugging with an old AT ("big" 5 pin keyboard connector) and HIL connect/disconnect at the keyboard (!) without any problem (IBM model M, the famous one). > Some digging around revealed that I had the following > line in /etc/rc.conf twice: > moused_enable=3D"YES" This doesn't matter: /etc/rc.conf is a shell script included in system scripts that does just contain variables that are set. Compare the following: x =3D 3; x =3D 3; What does happen? Or even this: x =3D 3; x =3D 4; You can have the same line 100 times in this file, with the result that the _last_ setting will be used. See "man rc.conf" for details. > I removed one of these (which I guess was the culprit) and left > one as it should have been, then all was well.=A0 So _that_ is very strange, if one has the functionality of /etc/rc, rc.conf, and the rc.d/ scripts in mind... having a line twice in the config file does _not_ imply a service is started twice. > I have no idea why I had=A0 moused_enable=3D"YES"=A0 in there twice, > whether it was from an old or recent rc.conf edit, but it > clearly seems to have been causing the issue. Coincidence, covariation, correlation...? :-) > Other (maybe valuable) info: > I am running hald in /etc/rc.conf as follows: > dbus_enable=3D"YES" > hald_enable=3D"YES" > ...and these were there prior to the ports update. >=20 > I figured this "issue" may be of some value since I did not > do any src updates. While moused is part of the base system (updated per source or freebsd-update), dbus and hal are ports (job for portmaster). --=20 Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...