From owner-freebsd-questions Wed Sep 20 11:35:32 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mta01-svc.ntlworld.com (mta01-svc.ntlworld.com [62.253.162.41]) by hub.freebsd.org (Postfix) with ESMTP id B0FC537B424 for ; Wed, 20 Sep 2000 11:35:22 -0700 (PDT) Received: from parish ([62.253.84.231]) by mta01-svc.ntlworld.com (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000920183517.HAKH16640.mta01-svc.ntlworld.com@parish>; Wed, 20 Sep 2000 19:35:17 +0100 Received: (from mark@localhost) by parish (8.11.0/8.11.0) id e8KIZE402219; Wed, 20 Sep 2000 19:35:14 +0100 (BST) (envelope-from mark) Date: Wed, 20 Sep 2000 19:35:13 +0100 From: Mark Ovens To: Antoine Beaupre Cc: freebsd-questions@freebsd.org Subject: Re: PnP modem not recognized at boot, but by pnpinfo(8) Message-ID: <20000920193513.B1612@parish> References: <20000920191137.A1612@parish> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: ; from beaupran@IRO.UMontreal.CA on Wed, Sep 20, 2000 at 02:16:58PM -0400 Organization: Total lack of Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Sep 20, 2000 at 02:16:58PM -0400, Antoine Beaupre wrote: > This is a mess. I don't know exactly how I got it to work. I don't think > that the PnP OS has something to do with BSd problems but then again.. > > I have to run some test before commiting myself. > > However, I am now sure that it was not a kernel problem. (well, I did have > to add the modem's PnP ID to /sys/isa/sio.c and recompile the kernel). > > If I setup my com2 (sio1) in the BIOS correctly, (IRQ3, 2f8), Are those the settings on the ``device sio1 ....'' line in your kernel config file? FWIW, what I would do is to get it working under FreeBSD. Note the settings it is using (from the boot messages). Then boot Windows and check if it *really* isn't found or whether it is found, but doesn't appear because of a conflict. Use Control Panel->System, devices tab and, if your modem appears (probably with a yellow ``!'' or red warning icon) check the properties for conflicts, and resolve them (making sure your modem ends up with the same settings as in FreeBSD). Let me know how you get on. > the modem is > not recognized correctly. This is probably the main problem, but again, I > have to test all this stuff. > > Thanks again for you help and support > > A. > > On Wed, 20 Sep 2000, Mark Ovens wrote: > > > On Wed, Sep 20, 2000 at 12:36:46PM -0400, Antoine Beaupre wrote: > > > On Wed, 20 Sep 2000, Mark Ovens wrote: > > > > > > > On Tue, Sep 19, 2000 at 10:45:37AM -0400, Antoine Beaupre wrote: > > > > > > > > > > I have `resolved` my problem in some way. The modem is recognized at > > > > > boot. I cannot provide much details for now, since it`s not yet fully > > > > > functional. (see my other posting) > > > > > > > > > > I`ll just say for now that it was indeed a BIOS setting that solved the > > > > > problem. Curiously, this also busted windows support for the modem!!! So > > > > > now I can`t use my modem at all.. :( > > > > > > > > > > > > > Not really surprising. If I remember correctly, once W95 has allocated > > > > an IRQ and address for a device it forces the BIOS to update it's > > > > "resources table" so that on subsequent boots it always uses the same > > > > (Windows determined) IRQ. By changing the "PnP OS" setting to "no" the > > > > BIOS is assigning resources the way it wants to. Your Windows is > > > > expecting the modem to be on a particular IRQ and not finding it so it > > > > gives up. > > > > > > Grrr.. I hate-hate-hate-hate windows. I'll move PnP OS to NO. But now my > > > modem is working in windows. Re-install. For about the.. say.. 20th these > > > 2 weeks? > > > > > > But I still have the other problem with my modem in FBSD (see my other > > > post, I won't discuss it here.. :) > > > > > > > Whoa, whoa. when you said before, "I`ll just say for now that it was > > indeed a BIOS setting that solved the problem.", I took that to mean > > that changing "PnP OS" to "n" had fixed it. Is this not the case? > > > > Which setting works with Windows and which works with FreeBSD. > > Unfortunately I can't give you a definite setting as mine works with > > "PnP OS" set to either. > > > > > > Try completely removing your modem in Windows, doing the reboot, and > > > > hopefully Windows will re-find it (with "PnP OS" set to "no" in your > > > > BIOS should mean that Windows won't be able to f*!£ it up again. > > > > > > 'll try that thanks. > > > > > > > > > > > > > > > > > Just thought of something. Does your BIOS have a ``PnP OS'' option?. > > > > > > If so, what is it set to, and what happens if you change it from "yes" > > > > > > to "no" or vice versa. > > > > > > > > > > > > The last line of your pnpinfo(8) shows that the modem is not > > > > > > initialized: > > > > > > > > > > > > -- card select # 0x0001 > > > > > > > > > > > > CSN CIR2000 (0x0020320d), Serial Number 0xffffffff > > > > > > > > > > > > Logical device #0 > > > > > > IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 > > > > > > IRQ 0 0 > > > > > > DMA 4 4 > > > > > > IO range check 0x00 activate 0x00 > > > > > > > > > > > > Maybe you need to let the BIOS initialize the card (PnP OS == "n")? > > > > > > > > > > > > > Si l'image donne l'illusion de savoir > > > > > > > C'est que l'adage pretend que pour croire, > > > > > > > L'important ne serait que de voir > > > > > > > > > > > > If the image gives the illusion of knowledge(?) > > > > > > It is what the ???????? for thought(?) > > > > > > It is not important to know what is seen(?) > > > > > > > > > > > > -- > > > > > > 4.4 - The number of the Beastie > > > > > > ________________________________________________________________ > > > > > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > > > > > > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > > > > > > mailto:marko@freebsd.org http://www.radan.com > > > > > > > > > > > > > > > > Si l'image donne l'illusion de savoir > > > > > C'est que l'adage pretend que pour croire, > > > > > L'important ne serait que de voir > > > > > > > > > > Lofofora > > > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > -- > > > > 4.4 - The number of the Beastie > > > > ________________________________________________________________ > > > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > > > > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > > > > mailto:marko@freebsd.org http://www.radan.com > > > > > > > > > > Si l'image donne l'illusion de savoir > > > C'est que l'adage pretend que pour croire, > > > L'important ne serait que de voir > > > > > > Lofofora > > > > > > > -- > > 4.4 - The number of the Beastie > > ________________________________________________________________ > > 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org > > 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark > > mailto:marko@freebsd.org http://www.radan.com > > > > Si l'image donne l'illusion de savoir > C'est que l'adage pretend que pour croire, > L'important ne serait que de voir > > Lofofora > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- 4.4 - The number of the Beastie ________________________________________________________________ 51.44°N FreeBSD - The Power To Serve http://www.freebsd.org 2.057°W My Webpage http://ukug.uk.freebsd.org/~mark mailto:marko@freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message