Need sungem to use eth0, no luck

Message

kingLatency · Post by **kingLatency** » Wed Jul 14, 2004 4:21 am

When booted from the liveCD 'modprobe sungem' got eth0 up and running. Now, however, booted up from my 2.4.26-r3 system, I can't. I've tried compiling sungem builtin and as a module. When it's builtin I get an error on startup as the system puts up the network. When it's a module, I can't load it because 'modprobe sungem' gives me, "couldn't find the kernel version the module was compiled for.'

I imagine the problem lies in some config files not being updated or some symlinks that should exist but don't. However, I don't know what the actual problem is. How can I get sungem working or get eth0 working by some other method? Thanks in advance.

P.S. It might be useful to know that I get this same error attempting to modprobe any kernel modules that are available.

silian87 · Post by **silian87** » Wed Jul 14, 2004 7:00 am

go to /usr/src/linux and do:

Code: Select all

make dep && make clean vmlinux modules modules_install

Perhaps a clean can solve your problem.

kingLatency · Post by **kingLatency** » Wed Jul 14, 2004 2:04 pm

Thanks. I was actually going to read up on what each of those arguments to make does--perhaps I would have discovered that one on my own. I'll try that.

kingLatency · Post by **kingLatency** » Wed Jul 14, 2004 3:04 pm

I tried making again with the command you recommended. Unfortunately, I still get the same error when trying to use modprobe. Now I'll try with sungem compiled in.

What else could it be? Something about module dependencies (sungem seems to depend on sungem_phy)?

kingLatency · Post by **kingLatency** » Wed Jul 14, 2004 4:00 pm

I just booted with sungem compiled in. I was getting this message before, and it might be useful, but I don't know what it means. When we get to the "* Bringing eth0 up..."

Code: Select all

SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface: No such device
SIOCSIFNETMASK: No such device

stimuli · Post by **stimuli** » Wed Jul 14, 2004 8:08 pm

Before getting newer kernel sources, try that with eth1

billbrasky · Post by **billbrasky** » Wed Jul 14, 2004 8:41 pm

I just switched my box from 2.6 to 2.4 (emerge'd ppc-sources), rebuilt and I'm getting the same error. I wonder if there's a wrong version number in the kernel source somewhere. I'll do some more digging tonight.

kingLatency · Post by **kingLatency** » Thu Jul 15, 2004 12:42 am

I may just try a newer kernel version if that'll help me get my network going. Were you also attempting to use sungem? Might I ask which package containing a 2.6 kernel it was you were using? I know there are several options-- gentoo-sources, benh, dev ppc sources, etc.

eth1 didn't work either.

billbrasky · Post by **billbrasky** » Thu Jul 15, 2004 2:12 am

No, I have two pcnet32 cards in my box. I'm compiling them directly in right now just so I can get some network access. I still have some other modules I'll need to load.

I was using gentoo-dev-sources (2.6.7) before, but there were problems with some of my ISA bus hardware, that's why I'm going back to 2.4.X. Your mileage will vary.

(Yes, strangely enough, old RS/6000s have ISA busses on PPC boxen).

billbrasky · Post by **billbrasky** » Thu Jul 15, 2004 2:41 am

Aha, someone opened a bug on this:

http://bugs.gentoo.org/show_bug.cgi?id=53371

I'm gonna try compiling a stock kernel from kernel.org and see what happens.

billbrasky · Post by **billbrasky** » Thu Jul 15, 2004 2:47 am

Actually, I should read closer. It says to use gcc 3.3.2, not 3.3.3.

kingLatency · Post by **kingLatency** » Thu Jul 15, 2004 12:43 pm

I've got 3.3.3, so I guess that bug is what's affecting me. I'm going to try gentoo-dev-sources.

billbrasky · Post by **billbrasky** » Thu Jul 15, 2004 9:21 pm

Good luck. Downgrading GCC worked for me, so if you have problems, just emerge /usr/portage/sys-devel/gcc/gcc-3.3.2-r7.ebuild, make clean in your 2.4 kernel and rebuild it.