Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:3728 comp.os.386bsd.bugs:1095 Path: sserve!newshost.anu.edu.au!munnari.oz.au!network.ucsd.edu!swrinde!cs.utexas.edu!uunet!mcsun!sun4nl!philapd!apdnews!spoetnix.idca.tds.philips.nl!wilko From: wilko@idca.tds.philips.nl (Wilko Bulte) Newsgroups: comp.os.386bsd.questions,comp.os.386bsd.bugs Subject: Re: /dev/sio01: Device not configured --- Solution. Keywords: sio com shitty-modem Message-ID: <wilko.742466103@spoetnix.idca.tds.philips.nl> Date: 12 Jul 93 08:35:03 GMT References: <jl.742239288@argon> Sender: news@idca.tds.philips.nl Lines: 38 jl@argon.gas.uug.arizona.edu (Joshua Lackey) writes: >Greetings! >Thanks to all who replied to my posts. I also want to thank everyone >involved with the latest patch kit and sio!!! >I correctly configured my kernel and re-compiled. >device sio00 at isa? port "IO_COM1" tty irq 4 vector siointr >device sio01 at isa? port "IO_COM2" tty irq 3 vector siointr >device sio02 at isa? port "IO_COM3" tty irq 5 vector comintr >#device sio03 at isa? port "IO_COM4" tty irq 9 vector siointr >Yet at boot time, the probe would fail to recognize /dev/sio01. >... >sio0 <16450> at 0x3f8 irq 4 on isa >sio2 <16550A> at 0x3e8 irq 5 on isa >fd0 drives... >Where is sio1??? >When I try to use /dev/sio01, I get a device not configured error. If it is of any consolation: same problem for me. It looks as if it is dependend on a 'hard' or 'soft' boot (ctl-alt-del type reset). Maybe the probe stuff has some timing/speed quirks? Every now and then the sio1 is correctly recognized. Wilko -- | / o / / _ Wilko Bulte mail: wilko@idca.tds.philips.nl |/|/ / / /( (_) |d|i|g|i|t|a|l| Equipment Corporation voice: +3155-432062 fax: +3155-432103 DTN: 829 2062 PO Box 245 - 7300 AE Apeldoorn - The Netherlands