SEO

On 11 Feb 2007, in the Usenet newsgroup alt.os.linux.dial-up, in article
<1171242122.791112.40810@s48g2000cws.googlegroups. com>, jamiil wrote:

[NOTE: Followup-To: set to alt.os.linux.debian]

> (Moe Trin) wrote:

>> Look at the 'lspci -vv' or 'cat /proc/pci' output

>I tried your suggestion and the results were as follow:
>lspci -b [ I clould not find the w option ]

-vv for Very Verbose but that's ok

>0000:01:0b.0 Serial Controler: 5610 56K FaxModem 56K FaxModem Model
>5610 (rev 01)

That's a good one! I've used several of those modems without any problem
at all (except initially when we were still using the 4.13 driver - and
even then it only took the setserial command to fix things). You can
ignore all statements about winmodems - you have a Gen-U-Wine Real
Hardware Modem (tm) that needs nothing special to run.

>cat proc/pci
>~~~~~~~~~
>IRQ 9 I/O 0xecb8 [0xecbf] Bus 1 device 12 function 0

Looks reasonable

>Armed with this information I wanted to use 'setserial' but the
>command was not found (!?)

That has been a separate package - all of the distributions I've used
install it by default. I don't know why it's not on your system. Perhaps
one of the Debian experts can tell why, or how to install it.

>pppconfig is not of much use in this case, since it has not room for
>IRQ/Port setting.

Correct - that's a kernel function, not an application.

>On the other hand, finding that Linux does recognize the modem is a
>step forward and an inspiration to continue with the process of
>setting up the modem under linux to 'Dial Up"

What shows up in the /var/log/messages - do you see the kernel serial
driver finding the card as noted up-thread?

>Now, could you please advice me what to do with the information I have
>collected.

I would expect that the kernel driver should have found the card, only
it may have put it someplace we didn't expect. The '/bin/setserial'
route was what we were using when the kernel driver got confused, or
didn't see it. In this case, the syntax would merely be

/bin/setserial /dev/ttyS3 irq 9 port 0xecb8

if the kernel driver hasn't found it.

Old guy