On Aug 24, 2007, at 10:30 AM, Ken Irving wrote:
On Fri, Aug 24, 2007 at 08:48:42AM -0800, Ken Irving wrote:
On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote:
As an alternative to minicom, 'screen' also makes a useful serial
terminal
program. At least on OS X, I often do someth
On Fri, Aug 24, 2007 at 08:48:42AM -0800, Ken Irving wrote:
> On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote:
> > As an alternative to minicom, 'screen' also makes a useful serial terminal
> > program. At least on OS X, I often do something like this to talk to
> > routers and th
On Aug 24, 2007, at 9:48 AM, Ken Irving wrote:
On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote:
As an alternative to minicom, 'screen' also makes a useful serial
terminal
program. At least on OS X, I often do something like this to talk to
routers and the like:
screen /dev/tt
On Fri, Aug 24, 2007 at 09:14:21AM -0700, David Brodbeck wrote:
> As an alternative to minicom, 'screen' also makes a useful serial terminal
> program. At least on OS X, I often do something like this to talk to
> routers and the like:
> screen /dev/tty.usbserial 9600
>
> "Ctrl-A Shift-K" will e
As an alternative to minicom, 'screen' also makes a useful serial
terminal program. At least on OS X, I often do something like this
to talk to routers and the like:
screen /dev/tty.usbserial 9600
"Ctrl-A Shift-K" will exit. "Ctrl-A i" will give you a nice little
display of what the seria
After some testing it turned out that the cable is indeed not properly
wired :S
I ordered a better one and I'm hoping that it will do the job flawlessly.
Thanks for replying!
Regards,
Fili
Btw. the cat/echo is a proposed test by Linux-Ha.org which should work.
--
To UNSUBSCRIBE, email to [
On Thu, Aug 23, 2007 at 11:17:11AM -0800, Ken Irving wrote:
> On Thu, Aug 23, 2007 at 03:06:45PM +, Douglas A. Tutty wrote:
> > I have yet to find a ready-made null-modem cable that is actually wired
> > correctly for use by UNIX. How it should be wired can be found in
> > several places acces
On Thu, Aug 23, 2007 at 03:06:45PM +, Douglas A. Tutty wrote:
> On Thu, Aug 23, 2007 at 03:37:00PM +0200, Fili Wiese wrote:
> > I'm having trouble setting up a serial connection between two servers
> > using a null modem cable.
> > ...
> >
> > Maybe the (brand-new) null-modem cable is not wire
On Thu, Aug 23, 2007 at 03:37:00PM +0200, Fili Wiese wrote:
> I'm having trouble setting up a serial connection between two servers
> using a null modem cable.
> This link is needed as a redundant connection for Heartbeat.
> Both machines are indentical (both hardware and software).
>
> In my hu
Fili Wiese wrote:
Hello,
I'm having trouble setting up a serial connection between two servers using a
null modem cable. This link is needed as a redundant connection for
Heartbeat. Both machines are indentical (both hardware and software).
[cut]
I'm really at a loss :S Does anybody have a c
On 08/23/2007 08:37 AM, Fili Wiese wrote:
Hello,
I'm having trouble setting up a serial connection between two servers
using a null modem cable.
This link is needed as a redundant connection for Heartbeat.
Both machines are indentical (both hardware and software).
Some info:
--
Hello,
I'm having trouble setting up a serial connection between two servers
using a null modem cable.
This link is needed as a redundant connection for Heartbeat.
Both machines are indentical (both hardware and software).
Some info:
-
Thanks for the advice, it helped me figure out how to get the I/O from lspci
-v. I've got the modem *sort of* working now: It seems to only work on IRQ
0 (shared with the timer), and at speeds no higher than 9600 baud. Examples:
# lspci -v
:02:0b.0 Serial controller: 5610 56K FaxModem 56K
Thanks for the advice, it helped me figure out how to get the I/O from lspci
-v. I've got the modem *sort of* working now: It seems to only work on IRQ
0 (shared with the timer), and at speeds no higher than 9600 baud. Examples:
# lspci -v
:02:0b.0 Serial controller: 5610 56K FaxModem 56K
Levi Waldron wrote:
>
> I just went out and bought a brand new, fully hardware PCI modem (for
> $68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
> to get assigned a ttyS* port during the boot process. The Modem HOWTO
> gives some tips for finding out the essential infor
Levi Waldron wrote:
I just went out and bought a brand new, fully hardware PCI modem (for
$68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
to get assigned a ttyS* port during the boot process. The Modem HOWTO
gives some tips for finding out the essential information, then
Levi Waldron wrote:
I just went out and bought a brand new, fully hardware PCI modem (for
$68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
to get assigned a ttyS* port during the boot process. The Modem HOWTO
gives some tips for finding out the essential information, then
I just went out and bought a brand new, fully hardware PCI modem (for
$68!), USR 56K V.90 w/ Voice (2976/3298). Unfortunately, it does not seem
to get assigned a ttyS* port during the boot process. The Modem HOWTO
gives some tips for finding out the essential information, then says
without givin
Gudmundur writes:
> I now have to put my old modem back in, but was thinking that maybe it
> would be safe to have them both, since one is PCI and the other ISA.
That will work fine.
--
John Hasler
[EMAIL PROTECTED]
Dancing Horse Hill
Elmwood, Wisconsin
On Fri, Apr 14, 2000 at 09:41:26PM +0200, Guðmundur Erlingsson wrote:
> Hi there,
>
> Thanks for the responses to my original question. I have now found out
> about what is wrong. It is a PCI modem and modems of that kind don't
> work with linux yet, although there is work going on in that field.
Hi there,
Thanks for the responses to my original question. I have now found out
about what is wrong. It is a PCI modem and modems of that kind don't
work with linux yet, although there is work going on in that field.
Maybe for 2.4. It may well by a winmodem too, although it showed up on
at least
Guðmundur Erlingsson wrote:
>
> Hi there,
>
> I'm having a bit of a problem getting my modem working under Debian
> Slink 2.1, and really I'm beginning to think that I will have to do
> something drastic as playing with jumpers.
>
> It's a SupraSST 56i PRO DF card (Diamond Multimedia), and it se
On Wed, Apr 12, 2000 at 01:37:05PM +0200, Gu?mundur Erlingsson wrote:
> Yeah, it's supposed to be a normal modem. I inspected the box and the
> manual carefully before buying to avoid the winmodem-curse. And their
> homepage (Diamond multimedia) doesn't indicate anything in that
> direction,
It se
Hi,
Yeah, it's supposed to be a normal modem. I inspected the box and the
manual carefully before buying to avoid the winmodem-curse. And their
homepage (Diamond multimedia) doesn't indicate anything in that
direction, I even found a blurb where they stated that they work closely
with the Linux co
[EMAIL PROTECTED] wrote:
> I'm having a bit of a problem getting my modem working under Debian
> Slink 2.1, and really I'm beginning to think that I will have to do
> something drastic as playing with jumpers.
>
> It's a SupraSST 56i PRO DF card (Diamond Multimedia)
Is that a normal, full-functi
Hi there,
I'm having a bit of a problem getting my modem working under Debian
Slink 2.1, and really I'm beginning to think that I will have to do
something drastic as playing with jumpers.
It's a SupraSST 56i PRO DF card (Diamond Multimedia), and it seems to
use something called Modem Enumerator
Hi Debian users,
First, I didn't know very well yet manipulate ioports and interrupts. I
bought a 56.6Kbs Motorola V.90 (SM56) modem and tried the package wvdial to
detect my modem and it didn't detected. My mouse is at /dev/ttyS0 and the output
of the wvdialconf program is:
phanta
Evan Van Dyke wrote:
>
> Are you logged in as root? pon/poff do require that, i seem to remember.
>
> --Evan
>
With the correct file permissions, pon/poff *can* be run by a normal,
non-root, user.
--
Ed C.
It seems that I am to be the doomsayer of Diamond modems. Folks, if you
plan on using Linux, don't buy one! You weren't very specific about your
modem. Some of the older Diamond Supra modems are actually accessible to
Linux, but it's not easy to set them up. The newer PCI modems are
memory-mapp
Are you logged in as root? pon/poff do require that, i seem to remember.
--Evan
I am a new Linux User. I need Help!
I am having Problems Setting up My Supra 56k PNP PCI modem with Debian. I
can install the Base System from Floppy Fine. When I Tryed to connect to my
ISP it told me that /usr/bin/pon: /usr/sbin/pppd: Permission denied. So I
read the install manual and it told me
31 matches
Mail list logo
