Re: Communicating with USB Modem

On Sun, 10 Oct 2010 02:05:08 +, Phil Requirements wrote: > On 2010-10-09 20:22:41 +, Camaleón wrote: >> When it comes to modems and linux, the only way to hit the right device >> is by using a RS-232 modem. No drivers needed and straight-forward >> setup for all kind of services (dial-up

Re: Communicating with USB Modem

On 2010-10-09 23:17:40 -0400, Hal Vaughan wrote: > On Oct 9, 2010, at 10:17 PM, Phil Requirements wrote: > > > The one I used was US Robotics, but I can't lay my hand on it right > > this minute to say the product number. > > I saw some USR USB modems, but considering how I'll be buying a > numbe

If you want it to be an appliance... (was Re: Communicating with USB Modem)

On 10/09/2010 04:28 PM, Hal Vaughan wrote: [snip] but, in short, I want what's in their offices to be as simple as possible and to be a black box. I do not want them hooking up a keyboard or monitor to it ever. I don't even want them to think of it as a computer, EVER! So I'm looking not at low

Re: Communicating with USB Modem

On Oct 9, 2010, at 10:17 PM, Phil Requirements wrote: > On 2010-10-09 19:26:42 -0400, Hal Vaughan wrote: >> On Oct 9, 2010, at 6:49 PM, Camaleón wrote: > [big snip] >>> O.k. I also think geting an USB modem to work should just be plug and >>> play and no needing to mess with drivers at all. But

Re: Communicating with USB Modem

On 2010-10-09 19:26:42 -0400, Hal Vaughan wrote: > On Oct 9, 2010, at 6:49 PM, Camaleón wrote: [big snip] > > O.k. I also think geting an USB modem to work should just be plug and > > play and no needing to mess with drivers at all. But it could worst: > > there are some embedded modems (those yo

Re: Communicating with USB Modem

On 2010-10-09 20:22:41 +, Camaleón wrote: > On Sat, 09 Oct 2010 15:29:40 -0400, Hal Vaughan wrote: > > On Oct 9, 2010, at 12:44 PM, Camaleón wrote: > [big snip] > > When it comes to modems and linux, the only way to hit the right device > is by using a RS-232 modem. No drivers needed and str

Re: Communicating with USB Modem

On Oct 9, 2010, at 6:49 PM, Camaleón wrote: > On Sat, 09 Oct 2010 17:28:31 -0400, Hal Vaughan wrote: > >> On Oct 9, 2010, at 4:22 PM, Camaleón wrote: > >>> ... >> >> I see that, the one thing that is discouraging me is that, while I know >> they are talking about the chip, the pictures are of

Re: Communicating with USB Modem

On Sat, 09 Oct 2010 17:28:31 -0400, Hal Vaughan wrote: > On Oct 9, 2010, at 4:22 PM, Camaleón wrote: >> I can give you at least one reference (the manufacture's tech. specs): >> >> *** >> http://www.agere.com/docs/PCS_Catalog_052606.pdf >> >> (page 5) >> >> – SV92U2: USB 2.0 device controller,

Re: Communicating with USB Modem

On Oct 9, 2010, at 4:22 PM, Camaleón wrote: > On Sat, 09 Oct 2010 15:29:40 -0400, Hal Vaughan wrote: > >> On Oct 9, 2010, at 12:44 PM, Camaleón wrote: > > (...) > >>> Bufff... as per this doc¹ you could try "sl-modem" package from >>> non-free repo (it seems that your device -SV92U2- uses the

Re: Communicating with USB Modem

On Sat, 09 Oct 2010 15:29:40 -0400, Hal Vaughan wrote: > On Oct 9, 2010, at 12:44 PM, Camaleón wrote: (...) >> Bufff... as per this doc¹ you could try "sl-modem" package from >> non-free repo (it seems that your device -SV92U2- uses the "Scorpio" >> chipset) but prepare for the worst ;-( >> >>

Re: Communicating with USB Modem

On Sat, 9 Oct 2010 15:29:40 -0400 Hal Vaughan wrote: Hello Hal, > I can't remember where (so it could have been the manufacturer's > site), but there was one place I read that if it's USB, it had to use > the Hayes command set and would work on anything, but Brad's link to > TLDP shows that wron

Re: Communicating with USB Modem

On Oct 9, 2010, at 12:44 PM, Camaleón wrote: > On Sat, 09 Oct 2010 11:39:49 -0400, Hal Vaughan wrote: > >> On Oct 9, 2010, at 7:24 AM, Camaleón wrote: > >>> Don't go nuts with this. Just plug the modem, open a console, type >>> "dmesg | grep -i usb" and put the result here (for very long logs, >

Re: Communicating with USB Modem

On Sat, 09 Oct 2010 11:39:49 -0400, Hal Vaughan wrote: > On Oct 9, 2010, at 7:24 AM, Camaleón wrote: >> Don't go nuts with this. Just plug the modem, open a console, type >> "dmesg | grep -i usb" and put the result here (for very long logs, >> upload the result to "www.pastebin.com" or any servic

Re: Communicating with USB Modem

On Oct 9, 2010, at 7:24 AM, Camaleón wrote: > On Sat, 09 Oct 2010 03:21:36 -0400, Hal Vaughan wrote: > >> I have a Debian Lenny system and I've plugged in a USB 56K modem. (I >> know that's as outdated as a Model T, but I need it for business.) When >> I type "cat /proc/bus/usb/devices" I get

Re: Communicating with USB Modem

On Sat, 09 Oct 2010 03:21:36 -0400, Hal Vaughan wrote: > I have a Debian Lenny system and I've plugged in a USB 56K modem. (I > know that's as outdated as a Model T, but I need it for business.) When > I type "cat /proc/bus/usb/devices" I get this: (...) As Ron suggested, better look at dmesg

Re: Communicating with USB Modem

On Sat, 9 Oct 2010 03:21:36 -0400 Hal Vaughan wrote: Hello Hal, > I have a Debian Lenny system and I've plugged in a USB 56K modem. From (the Linux Documentation Project) comes this; 2.9 USB Modems USB = Universal Serial Bus. Most USB modems are wi

Re: Communicating with USB Modem

On 10/09/2010 02:21 AM, Hal Vaughan wrote: I have a Debian Lenny system and I've plugged in a USB 56K modem. (I know that's as outdated as a Model T, but I need it for business.) When I type "cat /proc/bus/usb/devices" I get this: T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxC