can't access internet!

asif2k · 03-18-2006, 04:17 PM

When I boot up my linux machine. On the boot screen I see 2 version of kernels. One is old and the other newer. When I boot from the older version I able to access the internet. I cannot access the internet from the newer version. When I boot from the newer version. I can see the NIC from network settings. It says it is active. But when I open up my browser and go to a specific site. I cannot access it. I dont know what is going on?

any help is appreciated!

thanks in advance

Dark() · 03-18-2006, 04:23 PM

The problem is probably in your default gateway.Do you use dhcp for your NIC?

vmlinuz.gz · 03-18-2006, 04:29 PM

I'm having the exact same problem. See my thread (debian netinst: upgraded kernel; cannot access internet) on this board and look through the replies. See if they help.

Quote:

Originally Posted by Dark()

The problem is probably in your default gateway.Do you use dhcp for your NIC?

How do I determine whether or not I use dhcp?

theNbomr · 03-18-2006, 04:39 PM

run ifconfig (both working & non-working conditions). Post the results here.

--- rod.

vmlinuz.gz · 03-18-2006, 04:48 PM

My ifconfig results:

Code:

#ifconfig
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:8 errors:0 dropped:0 overruns:0 frame:0
      TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

asif2k · 03-18-2006, 06:17 PM

Quote:

Originally Posted by Dark()

The problem is probably in your default gateway.Do you use dhcp for your NIC?

The dhcp settings for the NIC is automatically set.

asif2k · 03-18-2006, 06:18 PM

I tried /sbin/ifconfig eth0 up - did not work
I tried /etc/init.d/network start - did not work

Also, yesterday I ran the command yum install yumex. and the yum thing did not go all the way. It only went up to 272/349. It crashed on me. I may be missing some configuration files.

asif2k · 03-18-2006, 11:43 PM

when I do /sbin/ifconfig under the new kernel. This is what I see:

Code:

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:2875 errors:0 dropped:0 overruns:0 frame:0
TX packets:2875 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 
txqueuelen:0 RX bytes:3062242 (2.9 Mb)
 TX bytes:3062242 (2.9 Mb)

asif2k · 03-18-2006, 11:50 PM

Quote:

Originally Posted by vmlinuz.gz

My ifconfig results:

Code:

#ifconfig
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:8 errors:0 dropped:0 overruns:0 frame:0
      TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

maybe, drivers are not loaded

theNbomr · 03-19-2006, 12:03 AM

Okay, now we know your ethernet interface is not configured. There is apparently a functional set of startup scripts for networking in your system, since one kernel works. What kernel modules are loaded in the working version (lsmod). How does this compare with the modules that are loaded in the non-working version? Can any missing module(s) be manully loaded (with modprobe)? Try these things, and post the results here.

--- rod.

vmlinuz.gz · 03-19-2006, 01:29 AM

I looked at the lsmod for the two kernels. Here are the ones that were available in the older kernel but not in the newer one:

Code:

usb-uhci     19504   0 (unused)
...
ide-sesi      8272   0
...
via-rhine    10960   0
...
crc32         2848   0
...
ide-cd       27072   0
...
ide-disk     12448   0
ide-core     91832   0

via-rhine is of particular interest because I believe that is my ethernet controller. So, how do I add it? modprobe via-rhine didn't seem to work, but I haven't restarted linux yet since. I'll try restarting and see what happens.

Edit: Still not working. Debian better start cooperating soon if it hopes to have it's partition on my computer for much longer! And if it hopes to not be replaced by Slackware. Or something.

asif2k · 03-19-2006, 02:22 AM

Quote:

Originally Posted by theNbomr

What kernel modules are loaded in the working version (lsmod).
--- rod.

I ran the lsmod command on both kernels. The older kernel has this module, but the newer kernel does not have this module:

Code:

 binfmt_misc    7176  1

I am using U.S. Robotics NIC.

Edit: these are the modules from the older kernel:

Code:

Module                  Size  Used by
parport_pc             19392  1
lp                      8236  0
parport                29640  2 parport_pc,lp
autofs4                10624  0
sunrpc                101064  1
8139too                17792  0
mii                     3584  1 8139too
ipt_REJECT              4736  1
ipt_state               1536  6
ip_conntrack           24968  1 ipt_state
iptable_filter          2048  1
ip_tables              13440  3 ipt_REJECT,ipt_state,iptable_filter
floppy                 47440  0
sg                     27552  0
scsi_mod               91344  1 sg
microcode               4768  0
binfmt_misc             7176  1
dm_mod                 33184  0
ipv6                  184288  14
ext3                  102376  2
jbd                    40216  1 ext3

thanks for replying

theNbomr · 03-19-2006, 11:03 AM

When you ran lsmod on each version of the kernel, were you able to identify any driver that applied to your ethernet card? Can you see any driver module for you USR NIC?

It is often useful to post complete listings in these cases. Gives everyone more context to view, with possible solutions or more appropriate diagnostics.

--- rod.

asif2k · 03-19-2006, 12:53 PM

sorry, about that. No! I was not able to identify drivers that applied to my ethernet card. please, look at my previous post. I have edited it. thank you

theNbomr · 03-19-2006, 04:09 PM

Okay, I see the driver for a Realtech 8139 ethernet chip, 8139too. If that module is not loaded in the non-working version, try loading it:

modprobe 8139too

What happens? Is there an entry in modprobe.conf (or maybe modules.conf) that contains configuration parameters for the driver? If not, perhaps the default configuration in the new kernel module has changed and must be specified. You may be able to get the paramters from dmesg on the working version. You will have to do a bit of digging to find out exactly how the parameters are passed to the driver; ie. syntax.

If it *is* loaded, try reloading it.

rmmod 8139too
modprobe 8139too

Then see if you can

ifup eth0

Also, if it already loaded, what other modules have linked to it (under the 'used by' column)?

Is this a plug-in NIC? If yes, does it show up in when you run 'lspci'?

--- rod.