back for modem advice

Mike Reinehr cmr
Tue Jun 6 11:05:51 PDT 2006


On Friday 02 June 2006 04:45 pm, Bob Hemus wrote:
> ----- Original Message -----
> From: "Net Llama!" <netllama at linux-sxs.org>
> To: "Linux tips and tricks" <linux-users at linux-sxs.org>
> Sent: Thursday, June 01, 2006 6:53 PM
> Subject: Re: back for modem advice
>
> > On 06/01/2006 06:41 PM, Bob Hemus wrote:
> >
> > Bob, whatever happened to getting lspci output to determine what this
>
> OK, here are the lspci's from SuSE 10.0, LibraNet 2.8.1, and Fdora Core 5.
> All of the distros see it, but are the differences in the modem description
> indicative of something?  Can I download Linux drivers for these?  I'm
> Googleing then right after I send this.
> Thanks,
> Bob
>
<snip>
>
> 03:03.0 Communication controller: Agere Systems Venus Modem (V90, 56KFlex)
>
<snip>

Bob,

Ok, this is step 1. We know that the modem is "alive". At least, it's being 
recognized by the PCI system.

Step 2: From the thread "Re: modem education" I think we can be sure that this 
is a fully equipped modem that should work well under Linux.

The next step is to determine what device node that the modem is using. (This 
is one reason, of several, that I prefer external modems that connect to a 
serial port.) Is the correct device node setup, or being setup for you by 
udev? The output from dmesg might help, here. If not, here's a link with 
information that might help in this regard:  
http://www.tldp.org/HOWTO/Modem-HOWTO-6.html#ss6.3

Once you're assured that you have a working device node (& driver) we can move 
on to kppp.

Cheers!

cmr

-- 
Debian 'Sarge': Registered Linux User #241964

"More laws, less justice." -- Marcus Tullius Ciceroca, 42 BC


More information about the Linux-users mailing list