Re: [Fwd: KI-2.6.8-2-686 Upgrage And Modem Issuse]
------------------------------------------------------------------------
Leonard Chatagnier wrote:
Subject:
KI-2.6.8-2-686 Upgrage And Modem Issuse
After upgrading to kernel-image 2.6.8-2-686 and reinstalling my
hcfpci winmodem deb file, I can activate the modem, dial my ISP,
conduct PAP negotiations and get my local IP address and DNS servers
assigned with a
real connection in process using wvdial as indicated by the online
time posted when I kill the process with cntrl C. However, no
transmissions take
place.
If I use apt-get update, upgrade or anything requiring data transfer
I get an error: to the effect-tempory error resolving URL. If I use my
mozilla browser I get URL cannot be found, check the name and try
again. It's
obvious to me that the connection is there, but there is no
communication between hosts.
*
*
*
Kent West Wrote:
It sounds to me like you're not getting your /etc/resolv.conf file
populated with your DNS servers.
Once you're dialed up, what's the ouput of "ifconfig"?
Can you ping another computer by address (not by name, but by address)?
If so, the problem is in your /etc/resolv.conf file; if not, the problem
is elsewhere.
Can you ping yourself (ping localhost)?
Is your winmodem .deb designed for a 2.6 kernel? If not, that's probably
the problem (and a good reason for manufacturers of winmodems who don't
release specs to be avoided).
*
*--*
Kent
My /etc/resolv.conf file contains both ISP supplied DNS servers. The modem works
under woody bf2.4 when booted.
I can't ping under sarge(host not found or server not available depending on ping,
traceroute or host usage) but can under woody. _*I can ping localhost under sarge-no
packets lost*_! I've pinged debian, mylocal ISP and others under woody but not sarge.
Wayne Topa asked if I could ping my DNS servers by number. No, not even via woody
-get no response. Under sarge, I get 100% packet loss when I ping my ISP by number.
I have a "Communication controller: Conexant HCF 56k Data/Fax Modem (rev 08)" which is
supported and was told when I paid for the full speed version that it would work on any
kernel, but I'll check further. ScanModem test gave this info:(important I think)
*Resident PPP support modules are properly uncompressed .
----active COMM services are ------------
sl0 Link encap:Serial Line IP
tunl0 Link encap:IPIP Tunnel HWaddr
_*This COMM mode should be closed before using the modem,* or DNS services may fail._
Be sure to read the section about ppp related modules and aliases in Modem/General.txt
DEVPPP=crw-rw---- 1 root dip 108, 0 Mar 4 21:58 /dev/ppp*
The tun10 and s10 entries shows up doing ipconfig but didn't before installing sarge.
Would like to stop or kill it to see if it fixes modem but don't know how to stop it.
My ifconfig output under woody is:
ChatagnierL-Home:/home/lchata# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:206 errors:0 dropped:0 overruns:0 frame:0
TX packets:206 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:45978 (44.9 KiB) TX bytes:45978 (44.9 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:209.34.98.124 P-t-P:209.34.96.250 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:320 errors:0 dropped:0 overruns:0 frame:0
TX packets:361 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:291391 (284.5 KiB) TX bytes:39198 (38.2 KiB)
tunl0 Link encap:IPIP Tunnel HWaddr
inet addr:192.168.1.1 Mask:255.255.255.0
UP RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:51 dropped:0 overruns:0 carrier:0
collisions:51 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ifconfig output under sarge is:
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:149 errors:0 dropped:0 overruns:0 frame:0
TX packets:149 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19563 (19.1 KiB) TX bytes:19563 (19.1 KiB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:209.34.98.22 P-t-P:209.34.96.250 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:230 (230.0 b) TX bytes:87 (87.0 b)
sl0 Link encap:Serial Line IP
inet addr:192.168.0.1 P-t-P:192.168.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:0 (0.0 b) TX bytes:248 (248.0 b)
tunl0 Link encap:IPIP Tunnel HWaddr
inet addr:192.168.1.1 Mask:255.255.255.0
UP RUNNING NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:43 dropped:0 overruns:0 carrier:0
collisions:43 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Hope this helps you and Wayne. It's greek to me. Let me know how to stop the
comm mode mentioned under scanModem and I'll get back real quick if it solves
anything. Forgot to mention-not subscribed-in initial post. Please copy my email
address-much easier to reply that way. And most of all-thanks to you, Wayne and
others that responded to my post.
Leonard Chatagnier
Reply to: