From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 23 12:17:08 2011 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE653106566C for ; Wed, 23 Mar 2011 12:17:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id B78528FC13 for ; Wed, 23 Mar 2011 12:17:08 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 6608346B99; Wed, 23 Mar 2011 08:17:08 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D1FB68A01B; Wed, 23 Mar 2011 08:17:07 -0400 (EDT) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Wed, 23 Mar 2011 08:17:07 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.4-CBSD-20110107; KDE/4.4.5; amd64; ; ) References: <3052ba363957ef179b4531ed0362d494.squirrel@www2.ertyu.org> <201103221100.30082.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201103230817.07347.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6 (bigwig.baldwin.cx); Wed, 23 Mar 2011 08:17:08 -0400 (EDT) Cc: Steven Nikkel Subject: Re: 8.x and Modems X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2011 12:17:09 -0000 On Wednesday, March 23, 2011 1:34:54 am Steven Nikkel wrote: > On Tue, 22 Mar 2011, John Baldwin wrote: > >>> On Monday, March 21, 2011 5:17:19 pm steven_nikkel@ertyu.org wrote: > >>>> I recently upgraded my trusty old 4.x system to 8.1 and the one little > > bit > >>>> I can't get working is the internal ISA modem in the system. On 4.x it > > was > >>>> detected automatically by the sio driver: > >>>> > >>>> /kernel: sio4: <U.S. Robotics Sportster 33600 FAX/Voice Int> at > > port > >>>> 0x3e8-0x3ef irq 5 on isa0 > >>>> /kernel: sio4: type 16550A > >>> > >>> Can you get a verbose dmesg and post it somewhere? > >>> > >> > >> I think I got it into verbose mode, but it doesn't look any different, so > >> I'm not sure I did that right, but here it is: > >> http://pastebin.com/BbFevvt6 > > > > Hmm, you need to use 'boot -v' at the loader prompt. If you can't get to the > > loader prompt easily you can try using 'nextboot -o "-v" -k kernel' before > > rebooting. > > > > -- > > John Baldwin > > Ok, here's the proper verbose dump: http://pastebin.com/DJ1z0k4D > I've set it back to PnP mode and taken out all the specific hints. Hmm, no helpful bootverbose messages in the pnp.c code it seems. Can you take a hand at adding printfs to sys/isa/pnp.c? Specifically, something like this: Index: pnp.c =================================================================== --- pnp.c (revision 219740) +++ pnp.c (working copy) @@ -743,10 +743,10 @@ pnp_isolation_protocol(device_t parent) printf("A Normal-ISA-PnP card (%s).\n", pnp_eisaformat(id.vendor_id)); } +#endif if (bootverbose) printf("Reading PnP configuration for %s.\n", pnp_eisaformat(id.vendor_id)); -#endif error = pnp_read_resources(&resources, &space, &len); if (error) break; That should at least list each card it finds in a verbose boot. If you get a message showing your card, then the next step is probably to see if pnp_read_resources() is failing. If it is you'd want to narrow down where it fails. If not then you'd want to trace pnp_create_devices() to see if it fails. Oh, and a 'devinfo -v' to make sure your device doesn't already exist might be a good sanity check as well. -- John Baldwin