[NBLUG/talk] A couple of questions

[ME]

> I just booted up windows - modem is on Com4, IRQ 5, 02E8-02EF

Excellent. We can start from here. RedHat probably has some sort of
"Dialup Connection manager and Utility" (dont know what it is called.)

Try running this tool from Linux, and when it asks you where your modem
can be found, see if it can auto-detect. If it can't try specifying:
/dev/ttyS3
When it asks you for what serial port your modem is using. If it asks for
IRQ, then specify IRQ 5.

If for some reason, it is unable to detect your modem (even when
explicitly stated) then the next step is to see if the kernel even knows
abolut it.

Another tool to try is something called setserial, but we can get to that
later.

**** ONLY TRY BELOW THIS POINT IF THE ABOVE DOES NOT WORK ****

(A command-line is not so bad. Think of it as a program that gives you
access to work on the engine of the OS.)

A "command line" is or should be available when you run a program called
"Terminal" or "Xterm" or something like that. You get a box with text an
will likely have a prompt waiting for you to type. Your prompt will likely
start with a "$" but may have other stuff before it.

So, you can start up a terminal to give you a command line. The following
commands won't do anything harmful to your system, The following will only
read data and display it to your terminal:
$ grep " 5:" /proc/interupts
(You should see any devices recognized by your kernel as using IRQ 5)
(If you see nothing, then your kernel prob does not reconize the card.)

Also, you can try:
$ grep "02e8" /proc/ioports
(If your card is recognized, then you will likely see something output.)
(If you see nothing, then it is likely that your modem is not recognized.)

lspci is useful, since if it says "winmodem" then we know where to go
next. If it does not, the information it gives may help us to make a
decision.

>> A useful tool for this is a command line tool called "lspci"
>
>
> Ah, haven't gotten that far yet - getting to the command line!
> I am starting to fade here, so I will try this in the morning, thanks for
> responding so quickly.