[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [Fwd: KI-2.6.8-2-686 Upgrage And Modem Issuse]



------------------------------------------------------------------------
------------------------------------------------------------------------
On 03/13/2005 02:20 PM, Leonard Chatagnier wrote:

   Please someone respond to this. I've done my homework and am
   stymied. Even
   just a clue would help. Thanks for reconsidering.
   Leonard Chatagnier

   ------------------------------------------------------------------------

Subject:
KI-2.6.8-2-686 Upgrage And Modem Issuse
From:
Leonard Chatagnier <lenc@ruralcomm.com>
Date:
Fri, 11 Mar 2005 01:48:52 +0000
To:
debian-user@lists.debian.org


To:
debian-user@lists.debian.org


   Message-ID:
   <4230F904.6050501@ruralcomm.com
   <http://lists.debian.org/debian-user/2005/03/msg01361.html>>
   User-Agent:
   Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20050105
   Debian/1.7.5-1
   X-Accept-Language:
   en
   MIME-Version:
   1.0
   Content-Type:
   text/plain; charset=ISO-8859-1; format=flowed
   Content-Transfer-Encoding:
   7bit


   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.
   Am I dealing with a bug or is there an easy fix as there was for my
   X-window
   problem. The modem works fine when I bootup with my 2.4.18-bf2.4
   kernel using the same configuration files on wvdial, pon,
   pap-secrets, chap-secrets, etc.
   I'll appreciate any advice or suggested reading offered to solve
   this problem. It's the only issue I know to have to get a fully
   functioning system with the sarge kernel.
   Thanks so much,
Leonard Chatagnier

On 03/13/2005 02:20 PM,Ralph Katz  wrote:
Hello again Leonard,

I'll take a few non-expert swings at this... :)

1) Confirm your connectivity with ping and traceroute to a numerical IP address like 194.109.137.218 or 66.35.250.151.

2) Your errors resolving urls sound like a "no dns" problem. Try $ host www.debian.org , or $ dig www.kernel.org to see if you're getting anything back from your dns servers.

Of course you've read the /usr/share/doc/... for the packages you've upgraded and checked the bug reports for them?

Good luck!

Ralph

Ralph, plz excuse this email. Had to read it off www as I'm not subscribed and
forgot to mention it.

I had come to the same conclusion after running scanModem but don't know what to do about it as I'm dumb regarding networking. The ping, traceroute and host commands all indicated hosts not found or server not available which I believe verifies a dns problem. A snippit from scanModem indicates I'v got a live comm port that I need to disable for dns to work. I don't know how to turn it off, maybe you can help or point to a man. The snippit follows:

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

I'd like to turn 's10' and 'tun10' off first to see if that fixes my problem/ if I just new how. I couldn't find an init.d reference to stop amd dont know what else to do.

As far as reading manuals, that all I've done beside googling since the first post. Problem is, I have a problem zeroing in on the real issue. The only upgrade was to the 2.6.8-2-686 kernel including the kernel modules so I could reinstall my hcfpcimodem modules again. If Debian changed something as they tend to do, then I could have easily made some mistake. All I did besides installing the kernel and modules is run the hcfpcimodem.deb file.

I had great success this time installing the new sarge, it booted successfully. the first time I attempted sarge, I ended up doing a total woody reinstall to get it working again. well, I'm ramblilng.

I very much appreciate your reply and tell me how to stop the comm mode refered to in scanModem if you will.

Leonard




Reply to: