Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Oct 1998 10:44:56 -0400
From:      "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
To:        "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG>, "i98" <jkibler@dycon.com>
Subject:   Re: /dev/sio1  arhgg!
Message-ID:  <199810241446.KAA06116@laker.net>

next in thread | raw e-mail | index | archive | help
On Sat, 24 Oct 1998 00:32:43 -0400, i98 wrote:

>Hi there. Justin Kibler here.  Hrmph, i have been having so much fun with
>trying to get my darn modem setup. Well,  i would like to ask a few
>questions before i dedicate alot of time to doing nothing that will work.
>My kernel booting, (dmesg info) won't detect /dev/sio1, which is where my
>modem is.  I have the irq and everything correct, its exctly how it says it
>in my computer's manual.  But i have had no luck getting it to detect. I
>have tried MAKEDEV an all.  I am thinking the GENERIC kernel could be the
>problem.  But I wanted to make sure of this before I go downloading all the
>source to find out it wont work.  I have all the info I  need to configure
>my own modem, i just need the source. If this is my problem, please tell me
>so.  If not, could you give me some possibities of fixing my problem. Oh! By
>the way, I have FreeBSD 2.2.7.  Thanks alot!

Hey dude, nowhere do you mention what brand modem you have.  If it's a
"WinModem", it's NEVER going to work.  That's because to cut costs, the
manufacturer took some of the code that would normally be in a ROM or
Flash ROM on the board and put it in software that gets loaded by
Windows.  They DIDN'T create that software for other platforms.

If that's the case, that you have a WinmModem, you'll simply have to
get another one.  And the GENERIC kernel will detect sio0 and sio1, but
not sio2 or sio3.  The i/o address is determines which sio port it is.

sio0	0x3f8
sio1	0x2f8
sio2	0x3e8
sio3	0x2e8

sio0 (what DOS people call COM1) usually uses interrupt 4 (by
convention, not definition) but could use any int not reserved.
sio1 (what DOS people call COM2) usually uses interrupt 3 (again, by
convention, not definition) but could use any int not reserved.

Most people that have hardware troubles with their system caused by
adding a card, is due to them not taking inventory of their irqs.  You
need to create a chart containing the dedicated interrupts and add the
interrupts for your daughter cards.

Here's a table showing the dedicated IRQs:
IRQ	Description	Notes
0	System Timer	Dedicated
1	Keyboard		Dedicated
2	8259A Cascade	Dedicated, this is where IRQs 8-15 come
in
3	COM2 (sio1)	Convention
4	COM1 (sio0)	Convention
5	Soundblaster	Convention, also may be LPT2 instead
6	Floppy Controller	Dedicated, unless you ditch the
floppy
7	LPT1		Convention
8	RTC		Dedicated, Real-time clock for process
scheduler
9	Video		Convention, see video notes
10	Network		Convention
11	
12
13	Math CoProc	Dedicated
14	IDE0		Dedicated, unless you ditch IDE0
15	IDE1		Dedicated, unless you ditch IDE1 (or
don't have one)

Video notes:
originally int9 was used by VGA boards to remain compatible with CGA,
but now many video cards use int9 if the have an accelerator.

So if your modem is NOT a WinModem, check to see if it's jumpered as
COM3 or COM4. Also, you need to know if there are COM ports on your
motherboard.  Most modern motherboards have COM1, COM2, LPT1, IDE0,
IDE1, and floppy controllers built-in but can be disabled in the BIOS
setup.


Unix systems measure "uptime" in years, Winblows measures it in minutes.



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?199810241446.KAA06116>