Re: 1-way modem
- From: "Calab" <myspam@xxxxxx>
- Date: Fri, 29 Feb 2008 02:46:12 GMT
"Time Waster" <bfc@xxxxxxxxxxx> wrote in message
news:KRIxj.4659$A93.2571@xxxxxxxxxxx
Just upgrade from 2.6.9 to 2.6.18 (RHEL4.6 to RHEL 5), and my dialup
is malfunctioning. I can turn ppp debug on, and see that LCP config
requests are being sent, I can snoop the other side and see that
it's sending the LCP ACK's back, but there's no sign of them back
on the original side.
I also tried a manual test of using minicom to dialing another box,
manually
ATAing from minicom, the connect happens, but only when I type on host-A
does it show up on destination host-B. Not the reverse. So it's like
a 1-way port or something. Anyone have any debug ideas for this sort
of problem? Anyone seen it before?
Looking at a working case, I see that stty -a < /dev/ttyS0 (the modem
port) looks the same, and setserial -a /dev/ttyS0 is basically the same
(I tried setting it to auto_irq with no diff). Looking at
/proc/tty/driver/serial during the PPP negotiation seem to only show
transmissions, not receptions.
I'm past doing the dumber things like trying to run a console at the
same time on the same port.
Thanks for any ideas! (Ideally, someone's hit the same thing and
solved it.)
Had the same issue when a modem and COM port shared an IRQ. I only found out
what the problem was because I had a mouse in the COM port... I'd only
recieve data from the modem if I moved the mouse around.
.
- Follow-Ups:
- Re: 1-way modem
- From: Time Waster
- Re: 1-way modem
- References:
- 1-way modem
- From: Time Waster
- 1-way modem
- Prev by Date: Re: 1-way modem
- Next by Date: Re: Streaming different audio on multiple sound cards simultaneously
- Previous by thread: Re: 1-way modem
- Next by thread: Re: 1-way modem
- Index(es):
Relevant Pages
|
|