LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)
-   -   notwork card do not work after updating kernel (https://www.linuxquestions.org/questions/linux-hardware-18/notwork-card-do-not-work-after-updating-kernel-192345/)

crowl 06-11-2004 10:37 AM

notwork card do not work after updating kernel
 
I have installed debian woody (kernel 2.2-20) and all work fine.

In order to get iptables work, I have update my kernel to 2.4.18-bf2.4.

Now, my networkkart do not work :-(

with kernel 2.2-20 ifconfig shows:

eth0 Link encap:Ethernet HWaddr 00:50:BF:9C:E7:4B
inet addr:172.19.2.1 Bcast:172.19.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4156 errors:0 dropped:0 overruns:0 frame:0
TX packets:3545 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:5638476 (5.3 MiB) TX bytes:275636 (269.1 KiB)
Interrupt:11 Base address:0xb800

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

With the new kernel eth0 is missing. Is this a driver issue? How can I get this to work?

Please bear with me, I am not familiar with kernel an compiling. But I hope I can learn from you. Thanks for your assistance.

crowl 06-13-2004 06:10 AM

Nobody can help me?

I'm using debian, and I assume this is a basic linux question. Hope that someone can assistance me.

Thanks in advance.

eccles23 06-13-2004 07:23 AM

My suggestion is this...

if you still have your old kernel set up as "Linux.old" which is the default when you have compiled a new kernel...
do:

grep eth0 /etc/modules.conf.old

this *should* give you a line like:

alias eth0 <module name>

so you should get to see the name of the module the old kernel was loading for the network card (which it called eth0).

once you know that you can do:

grep <module name> /usr/src/<old kernel source dir>/drivers/net/Makefile

and the *easiest* way in the world for you to fix this up is to simply copy that line into the Makefile in your new kernel source. (but make sure that the line does exist and is just one single line first)

ie:

grep <module name> /usr/src/<old kernel source dir>/drivers/net/Makefile >> /usr/src/<new kernel source dir>/drivers/net/Makefile

NOTE THAT THE REDIRECTION IS ">>" AND NOT ">". the first one tells it to APPEND to the file, the second tells it to clobber (overwrite) it!!!

alternatively, just do a 'make menuconfig' and pick the module under network cards (10/100)

so there you go, you should be ok with that I think, unless the module isn't aliased in your modules.conf or whatever.
in that case just use dmesg, or else boot into the old kernel and try 'lsmod' to see a module listing.

good luck :D

(and P.S. please don't flame me for telling someone to mess with their kernel source files like that - if he/she does it properly it should be fine.)

crowl 06-14-2004 06:30 AM

eccles23,

thank for your assistance.

No case work for me. But I figured out that it seems that is not only a network problem. So, I assume it is not depended on hardware, therefore I will ask for help in a new thread.


All times are GMT -5. The time now is 04:36 PM.