eth0 problems with 8139

R2-D2 · Posted: Mon May 05, 2003 10:37 pm Post subject: eth0 problems with 8139

Hi there,
I have the same Problem discribed in this thread
https://forums.gentoo.org/viewtopic.php?t=51360&highlight=

but i can't solve that as easy as discribed there.

when I use "modprobe 8139too"
I get a message called:
"Couldn't find the Kernel version the module was compiled for"

I added 8139 Support in Kernel later after main Setup, und compiled it 2 or 3 times now. But i am not sure if he boots with the original Kernel or the new compiled one. What commands do I have to use, when compiling has finished?

be pleasant to me, im n00b with very little professional linux skills ^^

- R2-D2

duffolonious · n00b Joined: 04 Apr 2003 Posts: 34

well that depends on how you compile the kernel:

example: (starting over with fresh kernel)

duffolonious · n00b Joined: 04 Apr 2003 Posts: 34

Also a couple of other things,

Loading your 8139too modules (I have the same card).

Now then...
(make sure you compile the card as a module "<M>" , no "<*>")

Loading the module in gentoo:

R2-D2 · Posted: Tue May 06, 2003 6:18 am Post subject:

thx 4 reply...
i ll test this ones

freakallen · Posted: Thu May 08, 2003 5:47 pm Post subject:

You can also if compiling 8139too into the kernel (setting it as * instead of M, make things work by doing a "make install at the end of all the other make commands then runing "lilo". Anouther way to do the same thing instead of "make install" is to "cp /usr/src/linux/arch/i386/boot/bzImage /boot"

Make sure to mount your boot partition first before the above steps by "mount /dev/hdxy /boot"

X being your drive such as a,b,c,etc and Y being your partition being 1,2,3,etc.

Then afterwards run "lilo" like the last option.

Its much easier though the way mentioned already of compiling it as a module (using M and not *) then just adding the appropriate lines mentioned already into the modules.autoload file. Hope this information is usefull for you.

R2-D2 · Posted: Thu May 08, 2003 7:08 pm Post subject:

thanks 4 help guys.
This could have taken me a long time,
but I read your comment again carfully,
and noticed that the M at Kernel Settings
means Module, I didn't think about that ^^

... a poor silly n00b mistake ^^

but big thanks for help

- R2-D2

uzik · Apprentice Joined: 17 Apr 2003 Posts: 257

did you actually boot using your new kernel once you compiled it?

You must do something like

# make kernel

# mount your boot partition as /boot
mount /dev/hda1 /boot
# copy old kernel JUST IN CASE YOU MESS IT UP!
cp /boot/bzImage /boot/bzImage.old
# copy new kernel to your boot partition
cp /usr/src/linux/arch/i386/boor/bzImage /boot
# tell boot loader new kernel size etc.
# you'll have to do something different for grub
lilo

I made up another boot entry called 'backup' in my lilo.config
I pointed it to bzImage.old. So if my new kernel
locked up my computer I could boot the old one from
the menu lilo provides at bootup. Once you get the kernel
working you can take out the menu if you like.