My problem has been solved by the great ANTONIO OLIVARES.............. Thank you to all who helped me............ On 16/10/2009, Sreehari. T. <sreeharigvr@xxxxxxxxx> wrote: > THANK YOU ANTONIO................... > YOU ARE GREAT..................... > MY SUFFERING COMES TO AN END............... > I HAVE NOW FULL FLEDGED INTERNET.................... > YOU HAVE HELPED ME FROM THE FIRST............. > AND NOW YOU HAVE AT LAST SOLVED MY PROBLEM............. > I AM WRITING THIS FROM SLAX................... > THANK YOU.......... > THANK YOU.......... > THANK YOU.......... > THANK YOU.......... > THANK YOU.......... > > > On 16/10/2009, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: >> Sreehari & Jacques, >> >> Sorry to jump in on the thread, the advice given is excellent, but >> since Sreehari is using slax, wvdial by itself does not setup the DNS >> (Domain Name Servers on the spot) so he can do the following once he >> sees the lines >> >> Oct 10 16:43:46 (none) pppd[9811]: local IP address 61.2.192.101 >> Oct 10 16:43:46 (none) pppd[9811]: remote IP address 61.1.254.12 >> Oct 10 16:43:46 (none) pppd[9811]: primary DNS address 218.248.240.23 >> Oct 10 16:43:46 (none) pppd[9811]: secondary DNS address 218.248.240.135 >> >> # cp /etc/pppd/resolv.conf /etc/resolv.conf >> >> and it should work otherwise open /etc/resolv.conf with kwrite or >> other editor and paste the lines: >> >> nameserver 218.248.240.23 >> nameserver 218.248.240.135 >> >> and save it. Hopefully with that you can safely browse and cross your >> fingers so that the machine does not "freeze". >> >> Sorry for not responding to the messages as before, but I have a >> nonworking phone line at home and I cannot browse the internet :( >> >> Regards, >> >> Antonio >> >> On 10/15/09, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: >>> Sreehari >>> >>> >>> I know that this is going to cost you a freeze and a reset, but we must >>> find what goes wrong. >>> >>> So please: >>> >>> >>> 1-open a new command line window/terminal as root or prefix commands >>> with sudo if using Ubuntu Linux. Expand >>> >>> it vertically as much as your screen allows because you will not been >>> able to scroll up the window after the freeze if a lot is written on it >>> during this experiment . >>> >>> 2-type command as shown: >>> >>> tail -f /var/log/messages >>> >>> This will print 10 irrelevant lines on the screen. >>> >>> 3-return to the window where you are ready to retry wvdial and start it. >>> Make sure that this window does not overlap the "tail" window. Windows >>> can be made smaller, see their upper task bars. >>> >>> 4-when the machine freezes, sorry for this burden but please copy with a >>> pen on a piece of paper what has appeared on the "tail" window from the >>> instant you started wvdial . No need for the 10 lines shown before >>> you start wvdial. >>> >>> >>> And of course send us what you have written. >>> >>> >>> A tip, if you did not try it: before pushing reset when a machine >>> freezes, it is a good practice to try to simultaneously press the CTRL >>> , ALT and BACKSPACE keys. This restarts the display if it is the display >>> (mouse and keyboard included) which has frozen. >>> >>> There is another wonderful tip, but it needs to have an other computer >>> and to have them connected (Ethernet or WiFi): logon from the one which >>> is not frozen etc... >>> >>> Sreehari. T. wrote: >>> >>>> Hello jacques, >>>> >>>> When displaying this there is no network activity............ >>>> Oct 10 16:43:46 (none) pppd[9811]: local IP address 61.2.192.101 >>>> Oct 10 16:43:46 (none) pppd[9811]: remote IP address 61.1.254.12 >>>> Oct 10 16:43:46 (none) pppd[9811]: primary DNS address 218.248.240.23 >>>> Oct 10 16:43:46 (none) pppd[9811]: secondary DNS address >>>> 218.248.240.135 >>>> >>>> Wvdial displays the above but browser says no network >>>> connection.............. >>>> No network applications works........ >>>> >>>> Computer hanged means even mouse pointer was not moving.......... >>>> I was forced to press the reset button......... >>>> >>>> On 14/10/2009, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: >>>> >>>>> What do you mean by "the computer hanged". >>>>> >>>>> Do you mean that the window running wvdial became inactive, or that >>>>> you >>>>> could not do anything with the computer >>>>> except switch it off and reboot? >>>>> >>>>> I think that you panicked because you saw no activity in the wvdial >>>>> window. >>>>> I say this because wvdial worked perfectly and established a >>>>> connection, as shown by >>>>> >>>>> Oct 10 16:43:46 (none) pppd[9811]: local IP address 61.2.192.101 >>>>> Oct 10 16:43:46 (none) pppd[9811]: remote IP address 61.1.254.12 >>>>> Oct 10 16:43:46 (none) pppd[9811]: primary DNS address >>>>> 218.248.240.23 >>>>> Oct 10 16:43:46 (none) pppd[9811]: secondary DNS address >>>>> 218.248.240.135 >>>>> >>>>> When the connection is established, wvdial shows nothing until you >>>>> stop >>>>> wvdial by >>>>> typing control-C in the wvdial window. You must leave wvdial running >>>>> like >>>>> that as long as you want to use the connection. >>>>> So do it again, and start your browser for example, or any other >>>>> network >>>>> application >>>>> in an other window, not in the wvdial window. >>>>> >>>>> This is explained in the instructions for wvdial. >>>>> >>>>> Jacques >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>> >>> >> >
