Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.mel.connect.com.au!news.syd.connect.com.au!phaedrus.kralizec.net.au!not-for-mail From: bde@zeta.org.au (Bruce Evans) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problem with serial port Date: 18 Sep 1996 14:06:40 +1000 Organization: Kralizec Dialup Unix Lines: 33 Message-ID: <51nsgg$i5j@godzilla.zeta.org.au> References: <51ngh0$ahg@pelican.cs.ucla.edu> NNTP-Posting-Host: godzilla.zeta.org.au In article <51ngh0$ahg@pelican.cs.ucla.edu>, Andreas Terzis <terzis@pelican.cs.ucla.edu> wrote: >... >I recently upgraded my machine from 2.1.0R to 2.1.5R and I have the following >problem: My modem is not detected !!! >I have an internal modem in COM4 (sio3) which worked in 2.10R and works in >Win95. I don't have a COM2 serial port so there mustn' be any problem with >IRQ 3. The only relevant change between 2.1.0R and 2.1.5R was the removal of the initialization of unconfigured ports, so maybe you have a COM2 that you don't know about :-). >MYKERNEL >device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr >device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr >#device sio2 at isa? port "IO_COM3" tty irq 4 vector siointr >device sio3 at isa? port "IO_COM4" tty irq 3 vector siointr This should work even if you don't have a COM2. The main difference in 2.1.0R is that it does a partial initialization of COM3, which should make no difference to COM2 or COM4, but might mess up a non-sio device at the same address. Anyway, try enabling sio2 (unless you have a non-sio device at the same address), and leaving out the irqs for the devices that you don't want or have, and turning on the flag for verbose probe messages: device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr flags 0x80 device sio1 at isa? port "IO_COM2" tty vector siointr device sio2 at isa? port "IO_COM3" tty vector siointr device sio3 at isa? port "IO_COM4" tty irq 3 vector siointr flags 0x80 -- Bruce Evans bde@zeta.org.au