nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   General Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=27)
-   -   network trouble after upgrading kernel (http://www.nvnews.net/vbulletin/showthread.php?t=9949)

mvp 04-10-03 07:50 AM

network trouble after upgrading kernel
 
hello people.

I am running debian, woody and i just upgraded my kernel from 2.2.20 to 2.4.20. now my network dosen't work, when i try to browse to an url i get a msg saying "unknown host"
when i try reconfiguring my network with "ifup --force eth0" it says:
SIOCSIFADDR: No such device
Eth0: Error while getting interface flags: No such device
SIOCSIFNETMASK: No such device
SIOCSIFBRDADDR: No such device
Eth0: Error while getting interface flags: No such device
Eth0: Error while getting interface flags: No such device

ive tried recompiling the kernel a few times with different network settings, but no luck. any help would be appreciatet

suexec 04-10-03 12:41 PM

Check your interfaces at /etc/network/interfaces

Also, do you have the proper modules compiled for your NIC?

mvp 04-10-03 12:56 PM

i have the correct settings in /etc/network/interfaces

about the module i'm not sure, im new to linux and not sure what NIC is.

its just weird, it worked fine with the old kernel, and i did use all the realtek drivers, when i compiled my new kernel

revolution_of_1 04-10-03 02:17 PM

I had the same problem as you before. Being new to gnu/linux I thought I had selected all the right options when compiling my kernel but I hadn't. What I finally did was use my old config file that had all the options from the stock kernel. Perhaps that will help you also. Issue make oldconfig instead of make xconfig when compiling your kernel and see if that helps you. No promises but it worked for me. Also, NIC is just an abbreviation for network interface card.
revolution_of_one

mvp 04-10-03 03:32 PM

it didn't work unfortunetly, but thanks it was worth a try :)

suexec 04-10-03 05:09 PM

Can you post the output of:
lsmod

And also the network card related part of:
lspci -v

mvp 04-10-03 07:33 PM

lsmod with my old kernel (2.2.20-idepci)

Module Size Used by
af_packet 6136 0 (unused)

and lspci -v

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Subsystem: Realtek Semiconductor Co., Ltd. RT8029(AS)
Flags: medium devsel, IRQ 11
I/O ports at 9400


lsmod with new kernel (2.4.20)

Module Size Used by Not tainted

and lspci -v

00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
Subsystem: Realtek Semiconductor Co., Ltd. RT8029(AS)
Flags: medium devsel, IRQ 11
I/O ports at 9400 [size=32]

suexec 04-10-03 10:36 PM

From your lsmod, it appears that you are compiling drivers into the kernel.

I think the Realtek 8029 uses the ne2k-pci driver. Do you have this enabled?

What is the output of:
ifconfig

Have you tried to bind the interface manually with an
ifconfig eth0 some_ip netmask some_netmask
then manually setup your default gateway with
route add default gw gateway_IP

mvp 04-11-03 04:25 AM

With the new kernel

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:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4020 (3.9 KiB) TX bytes:4020 (3.9 KiB)

and with my old kernel

eth0 Link encap:Ethernet HWaddr 00:00:B4:BB:BB:3B
inet addr:195.249.88.162 Bcast:195.249.91.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:945 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:100482 (98.1 KiB) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x9400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:63 errors:0 dropped:0 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4280 (4.1 KiB) TX bytes:4280 (4.1 KiB)


you could be on to something with the ne2k-pci driver .. it uses them during boot up with my old kernel, just before it shows my realtek 8029 card. but it dosent whow it with my new kernel.

i tried bind the interface manualy, but i get simar errors as mentioned in my first post

mvp 04-11-03 07:41 PM

w00t it works! :)

answer was simple to put "alias ne2k-pci eth0" into /etc/modules.conf

thanks for helping people

suexec 04-11-03 10:19 PM

Glad you got the 2.4 kernel working. Now you can enjoy the benefits of iptables and ext3/xfs/jfs/reiserFS filesystems :)


All times are GMT -5. The time now is 08:17 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.