Results 1 to 2 of 2
I have 2 fresh installed Ubuntu 5.04 systems, on 2 different computers ("Duron" & "Sampron"). Duron has LT WinModem and it works fine. But, when I unplug modem from Duron, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-18-2005 #1
- Join Date
- Jul 2005
pppd with LT WinModem problem
I mean, it works, but connection can not be made. Modem dials a number, then comes noise tones, and after while, modem hangs up. On same machine, Sampron, under Windows, modem works fine.
I spent some time finding reason why it doesn't work on Sampron as it works on Duron (solution is still out of sight ), and after some digging through man pages, configs on both machines, I found next (I'm newbie in Linux world and this things are new to me, so this is maybe wrong path for finding solution):
- If I turn on 'debug' option in '/etc/ppp/options', some messages will be written in '/var/log/syslog' so I can see what's happening. And there was a difference between logs on Duron and Sampron.
I present log part from Sampron:
Jul 16 19:38:29 localhost udev: creating device node '/dev/ppp' Jul 16 19:38:29 localhost kernel: PPP generic driver version 2.4.2 Jul 16 19:38:29 localhost pppd: pppd 2.4.2 started by david, uid 1000 Jul 16 19:38:29 localhost pppd: using channel 1 Jul 16 19:38:29 localhost pppd: Using interface ppp0 Jul 16 19:38:29 localhost pppd: Connect: ppp0 <--> /dev/ttLTM0 Jul 16 19:38:29 localhost pppd: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xbe03344e> <pcomp> <accomp>] Jul 16 19:38:56 localhost last message repeated 9 times Jul 16 19:38:59 localhost pppd: LCP: timeout sending Config-Requests Jul 16 19:38:59 localhost pppd: Connection terminated. Jul 16 19:38:59 localhost pppd: Exit
I guess the problem is in pppd (as I understand those log lines), because it can't connect modem device (/dev/ttLTM0). At this point I found the problem goes beyond my scope (not for long, I hope), and I need help.
Note: wvdial says that pppd exits with code 10.
- 07-19-2005 #2
- Join Date
- Jul 2005
Problem solved by adding 'noapic' boot parametar for kernel (found tip somwhere on net). Don't know why, but it works.