Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Sep 2000 13:47:35 -0400 (EDT)
From:      Antoine Beaupre <beaupran@IRO.UMontreal.CA>
To:        Mark Ovens <marko@freebsd.org>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: PnP modem not recognized at boot, but by pnpinfo(8)
Message-ID:  <Pine.LNX.4.21.0009221335340.5624-100000@bld42.IRO.UMontreal.CA>
In-Reply-To: <20000921232540.A257@parish>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Sep 2000, Mark Ovens wrote:

> On Wed, Sep 20, 2000 at 10:19:49PM -0400, Antoine Beaupre wrote:
> > Here we go again.
> > 
> > Yep. Award 4.51PG BIOS. 
> 
> Close enough, mines a 4.51PGM ('M' for modem maybe :))

Is it onboard?
 
> > Anyways, I have some odd results regarding this. I tried to recompile with
> > sio1 on irq 9, obviouslyy not a good idea since my SCSI adapter is on irq
> > 9... So I tried to move it back to irq5, but surprise! after a whole new
> > "config SHALL && cd ../../compile/SHALL && make depend && make && make
> > install" cycle with the sio1's irq tweaked to 5, at boot, it still gets
> > listed ('ls' in userconfig (-c)) as irq 9!!!
> 
> I'd recommend using ``config -r'' when you've changed things. It removes
> the compile directory and re-creates it which guarantees that everything is
> correct (some files are created by the build process containing specific
> data from the config file - these don't get updated just because something
> is changed or deleted from the config, only if something is added).

I often do a make clean before starting a build... But it takes a looong
time to compile then. I'll try config -r next time.

> [snip]
> 
> > > Aha! a classic case of IRQ conflicts. 
> > 
> > Or so I've been told. But with what? The sio1? It seems so. But then, the
> > kernel should switch the modem to another irq! I can't move it away from
> > irq3, whatever I try! (get ready for the classical "Windoze can do
> > it!?") On windos, it's on irq 10 and port 0x3e8 - 0x3fe. Shouldn't the
> > fbsd kernel be able to do the same acrobatics?
> 
> I must have missed that in an earlier post, I'd been assuming that Win was
> using IRQ3.

Nope. Even when I disabled my COM2 (sio1) in the BIOS, it (windows) still
did not used the IRQ3 for the modem.
 
> OK, maybe this won't directly solve your problem but it may give you some
> ideas to try, I reboot my PC into all 3 OS's and looked for the modem
> settings:
> 
> 	FreeBSD - IRQ5  0x3e8 sio2 (COM3 in DOS)
> 	Win 95  - IRQ5  0x3e8 COM3
> 	Win NT4 - IRQ5  0x2e8 COM4
> 
> (note the different address in NT)

This remembers me the good ol' times when my modem was working. :) 

But notice here that irq5 is not available on my side, because of the
network card (NIC).
 
> My BIOS is setup thus:
> 
> PnP OS: N
> Resources controlled by: Manual
> Reset configuration Data: Disabled
> 
> IRQ-3  Legacy ISA
> IRQ-4  Legacy ISA
> IRQ-5  PCI/ISA PnP
> IRQ-7  Legacy ISA
> IRQ-9  PCI/ISA PnP
> IRQ-10 PCI/ISA PnP
> IRQ-11 PCI/ISA PnP
> IRQ-12 Legacy ISA
> IRQ-14 PCI/ISA PnP
> IRQ-15 PCI/ISA PnP

Humm.. How did you decide to put this or that IRQ on ISA on PCI/PnP? I
guess that 3 & 4 are for the 2 COM ports, and then leave irq5 to the
PnP modem. One major hassle here is that I have a NIC on irq 5! Yay. In
windows, it is used in EISA mode which _doesn't use and irq_, which I find
hard to believe... :)
 
> OK, I've done some tests on my system. Normally this is what I get:
> 
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1 at port 0x2f8-0x2ff irq 3 on isa0
> sio1: type 16550A
> ....
> sio2: <Pace 56 Voice Internal Plug & Play Modem> at port 0x3e8-0x3ef irq 5 on isa0
> sio2: type 16550A

Nice & clean. :)
 
> I disabled sio1 (COM2) in the BIOS and got:
> 
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> sio1: configured irq 3 not in bitmap of probed irqs 0
> .....
> sio2: <Pace 56 Voice Internal Plug & Play Modem> at port 0x2f8-0x2ff irq 3 on isa0
> sio2: type 16550A

So this kinda confirms the meaning of the message "configured irq...". It
is the opposite that the intuitive one. :) That is:

configured irq X not in bitmaps of probed irqs Y

means that the the irq _configured in the kernel_ to X, is not found
there.
 
> I got the same error about sio1 that you did but notice that my modem,
> although it is still found at sio2, now has the IRQ and address that sio1
> usually has (IRQ3 0x2f8).

Hum.. Interesting. The port/irq settings switch quite easily. But not on
my side... I would like to see my modem on irq 5 in the first place but
it's not available. There's irq 10 available, but maybe FBSD's sio driver
isn't designed for that?
 
> Next, I did ``boot -c'' and disabled sio1, this time I got:
> 
> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> sio0: type 16550A
> ....
> sio2: <Pace 56 Voice Internal Plug & Play Modem> at port 0x2f8-0x2ff irq 3 on isa0
> sio2: type 16550A
> 
> No warning about sio1, the modem still found as sio2, and still with IRQ3
> 0x2f8 (sio1's usual settings).

And the modem is working, of course. :)
 
> So, why don't you try, disabling sio1 (COM2) in the BIOS, doing ``boot
> -c'', disabling sio1, and see what happens to your modem.

I think I did that already, but I'll try again, with the exact settings
you sent me.

I will probably be able to post the results tonight or tomorrow.

A.

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0009221335340.5624-100000>