From owner-freebsd-current@FreeBSD.ORG Sat Jun 2 09:42:55 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7B4CA16A468 for ; Sat, 2 Jun 2007 09:42:55 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout7.cac.washington.edu (mxout7.cac.washington.edu [140.142.32.178]) by mx1.freebsd.org (Postfix) with ESMTP id 5AC5A13C448 for ; Sat, 2 Jun 2007 09:42:55 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hymn04.u.washington.edu (hymn04.u.washington.edu [140.142.15.176]) by mxout7.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l529gs11015644 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sat, 2 Jun 2007 02:42:55 -0700 Received: from localhost (localhost [127.0.0.1]) by hymn04.u.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l529gsqI024680 for ; Sat, 2 Jun 2007 02:42:54 -0700 X-Auth-Received: from [67.166.149.71] by hymn04.u.washington.edu via HTTP; Sat, 02 Jun 2007 02:42:54 PDT Date: Sat, 2 Jun 2007 02:42:54 -0700 (PDT) From: youshi10@u.washington.edu To: freebsd-current@freebsd.org In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.2.22833 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='SUPERLONG_LINE 0.05, NO_REAL_NAME 0, __CT 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0' Subject: Re: Issues with kernel / userland drivers after recent install and upgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 02 Jun 2007 09:42:55 -0000 On Sat, 2 Jun 2007, illoai@gmail.com wrote: > On 01/06/07, youshi10@u.washington.edu wrote: >> Hello, >> >> I have the following issues with a clean install of 7-CURRENT; >> they may be related to the GCC upgrade or other things. > > Probably not related to gcc4.2 > >> Background: >> I started out with a virgin clean 6.2-RELEASE system, then went >> straight to 7-CURRENT (synced yesterday) wit out installing anything >> (to avoid having to reinstall packages, etc). >> >> pass: >> 1. I have pass compiled into the kernel statically, but /dev/pass* isn't >> created on boot (devfs is running properly I believe). >> > > What SCSI devices do you have? No real SCSI devices on my desktop; just the generic ones like cd, ses, etc. (In addition to those) just ahc on my server, but I don't think I'm going to go upgrading quite yet on my server because I don't want to kill one of my disk's functionality.. >> ohci/ukbd/ums: >> 1. These aren't operating properly. I can't see any keyboard output >> even though before when I didn't compile ukbd into the kernel the USB >> keyboard worked magically with slight lag preceding the first input. > > "device ukbd" is in GENERIC . . . > Assuming you commented it out, and you did not > disinclude the module via /etc/make.conf, the lag > was probably the module loading automagically. I do WITHOUT_MODULES=* just for speed and to reduce the amount of stuff that gets compiled with buildworld. I figure that everything important should be compiled statically into the kernel, but then again that's me, and since my server/desktop aren't production machines I can take them down whenever I need to modify the kernel. > I have the line > usbd_enable="YES" > in /etc/rc.conf, although I do not know > where the heck it comes from, since it > did not used to be needed under 6.1, > and it does not appear in /etc/defaults/rc.conf Yeah, got that too. >> 2. The mouse cursor doesn't move whatsoever. >> 3. OHCI isn't detected on boot, and I think that only UHCI is detected >> properly, even though my board is EHCI/OHCI capable (Asus P5B- >> Deluxe). >> > > % dmesg -a | grep hci > perhaps? I'll check on that again, but all I saw with an OHCI in it was the firewire stuff IIRC (something about Texas instruments, FWOHCI, etc). Thanks :), -Garrett