So to see if I could get my 3c509.o module to load (see if previous
emails to the list) I loaded it by hand with insmod, and lo and behold,
here is message it gave:
eth0: 3c509 at 0x300 tag1, 10baseT port, address 00 a0 24 03 9f ec IRQ 10
3c509.c: 1.16 (2.2) 2/3/98 becker@cesdis.gsfc.nasa.gov
Yes, I instantly recognized this as the tell-tale sign that it loaded
correctly, and that those were indeed the correct values for the 3c509
which i have in /etc/conf.modules .
So after this I ran /etc/sysconfig/network-scripts/ifup to get the
networking initialized, but unfortunately bootp got no response. So I
went into the ifcfg-eth0 and changed it to dhcp, (mainly because I figured
hardly anyone has ever gotten this to work and I figured I could eliminate
a possibility quickly and move on to hard-coding it), so i did a ifup
again, and to my amazement, dhcp actually *worked* and got my ip...I
was absolutely shocked. I didn't expect it to work, as noone else I know
has got it to consistently work, and especially with all the problems I've
been having. That's just really odd. Anyways, I'm excited, but that's
still not the end of the road yet...first of all, I noticed after awhile
that dhcp clobbered my /etc/resolv.conf after awhile (at first it was
there in the beginning, later it was just reduced to no searching at all,
etc.) I mean I used to be able to do a ssh mars ; and now it's just
annoying to do a ssh mars.its.yale.edu . Is this a feature of some kind
of dhcp? It's really annoying me, and I wish I could turn it off or
something so I could keep my own. Luckily I have my old resolv.conf saved
away. Shawn or someone else familiar with the protocol could probably
answer this one...
And on another note, this manually loading of the 3c509 module is only a
temporary fix, and I'm searching for a way to fix this so it works upon
bootup. It still does the same thing upon bootup right now.
insmod: ...3c509.o: invalid parameter io:
and a bunch of other module errors like this:
/lib/modules/2.2.5/net/<insertnetmodulehere>.o: unresolved symbol(s)
for a bunch of modules, note that this particular error never occurs for
the 3c509, just a bunch of other modules I don't really need. While I
suppose I could just recompile and exclude these other things, I'm
thinking that perhaps these errors and the 3c509 error are all connected
somehow. I'm not sure. I'm hoping to isolate this problem, correct it,
and then recompile a more optimized version of the kernel, *without*
breaking networking or sound (which I also have working as a module right
now) I must admit I still haven't tried doing a mv on my 2.2.5 modules
before doing another recompilation, so perhaps i will try that. Does
anyone have any other suggestions?
BTW, I know I could've fixed this long ago (reinstall, etc.), but my goal
all along has been to learn from this experience and become a better
SysAdmin for it, and believe me, even if this is far as I get...I have
learned a great deal, and am very appreciative.
Thanks,
dave