From owner-freebsd-mobile Mon Oct 21 13:17:15 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31D0137B401 for ; Mon, 21 Oct 2002 13:17:14 -0700 (PDT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3818243E42 for ; Mon, 21 Oct 2002 13:17:13 -0700 (PDT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP id MUA74016; Mon, 21 Oct 2002 13:17:12 -0700 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Postfix) with ESMTP id EB2B75D03; Mon, 21 Oct 2002 13:17:11 -0700 (PDT) To: freebsd_mail@myrealbox.com Cc: dwalton@acm.org, mobile@freebsd.org Subject: Re: problems with upgrade In-reply-to: Your message of "Sat, 19 Oct 2002 22:16:31 PDT." <200210192216310092.503BB7CC@smtp.myrealbox.com> Date: Mon, 21 Oct 2002 13:17:11 -0700 From: "Kevin Oberman" Message-Id: <20021021201711.EB2B75D03@ptavv.es.net> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Date: Sat, 19 Oct 2002 22:16:31 -0700 > From: "Greg Smith" > > Kevin, > > I think the dmesg looks OK, IIRC. > > >> sio1: configured irq 3 not in bitmap of probed irqs 0 > > On my TP600 with 4.3-stable this is what I get without mwavedd > kldload'ed, but imodem definitely enabled on irq's 3 and 10 If you are loading mwavedd, you are loading an older version of mwavem. The current port creates 'mwave.ko'. > >> mwave0: on isa0 > >> Mwave Modem, UART settings IRQ 0x3 IO 0x2f8 > >> sio1 at port 0x2f8-0x2ff irq 3 on isa0 > >> sio1: type 16550A > > I think this is the result of kldload mwavedd [sadly I can't get mwave > to make on my 4.3-stable to verify my memory from 4.1]. Without the > mwavedd device driver there is no sio1. This is certainly true! Don't know how I missed it. It looks like everything loaded correctly if it not only sees sio1, but sees it as a 16550A. That means that the driver is actually communicating with the pseudo-device. The next question is whether the mwavem process is getting started. FWIW, I just tried this with 4.6-stable as of the day after 4.6.2 was released. I disabled loading mwave.ko at boot time and let the startup script do the job. I now see EXACTLY what Dave Walton saw, but my modem works fine. This is NOT assurance that it is the same, but it would be very close. At least I know my 600E is still working OK. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message