[SOLVED] Damn small linux not connecting to net after krnl rcmpl

smeezekitty · 12-23-2009, 12:21 AM

Damn small linux is not connecting to the internet (Host name not found) after i recompiled the kernel (BTW: i did not touch any net device settings).
----edit----
BTW: Its connect to a "CAT5" cord.

smeezekitty · 12-24-2009, 03:23 AM

reallyreallyreallybigBUMP
really need help here.

linuxlover.chaitanya · 12-24-2009, 03:30 AM

Host name not found could be due to the DNS error. You may need to check the DNS settings.

AwesomeMachine · 12-24-2009, 04:36 AM

Check if the old kernel works for networking. Try to ping yahoo.com. Do lspci -vvv | less, and check what ethernet adapter chip you have. Google the chip, and see which module that chip uses. Do lsmod, and see if that module is loaded. If the module isn't loaded, try: modprobe <module_name>. Restart networking, /etc/init.d/networking restart, and see if Internet works.

The other thing you can try is, from the kernel source root, /usr/src/linux, is running depmod.

smeezekitty · 12-24-2009, 12:59 PM

Code:

root@tty1[/]#ping yahoo.com
ping: unknown host yahoo.com
root@tty1[/]#lspci | grep ethernet
00:08.0 Advanced micro devices 79c970 
root@ttyl[/]#lsmod 
Module                Size  Used by
root@tty1[/]#/etc/init.d/networking restart
Reconfiguring network interfaces... done.
root@tty1[/]#ping yahoo.com
ping: unknown host yahoo.com
root@tty1[/]#

If i know linux good enough to understand that, that is not good.

evo2 · 12-24-2009, 02:22 PM

As previously suggested, it could be a DNS issue. Can you ping an IP: 75.126.162.205?
Is your /etc/resolv.conf sane?

Evo2.

smeezekitty · 12-24-2009, 04:24 PM

Code:

root@tty1[/]#ping 72.126.162.205
ping: no response from 72.126.162.205
root@tty1[/]#cat /etc/resolv.conf
search Belkin
nameserver 192.168.2.1
root@tty1[/]#

evo2 · 12-24-2009, 04:28 PM

Have you done a diff of the old and new kernel config files?

Evo2.

smeezekitty · 12-24-2009, 05:13 PM

I fixed it. When i was playing with the kernel, i accdentally removed /var/*.sock (* means i forgot the exact name).
I just type touch /var/(whatever the filenam is).sock and its working again.
I am posting this from Ubuntu running in VBox on DSL.