i'm facing aggravation that passing parameter's to debian's given
kernel 2.4.18 eepro and eepro100 modules (with modprobe) already built
is not working for me (dpkg'ed from woody)..(not too sure if i'm doing
this right -> modprobe -t net eepro100.o 11,0x300 correct?)..modprobe
says it fails and argues about possible faulty parameters for both
eepro and eepro100 and these are the correctly available modules for
my niccard...i've tried module -t net * with my two loadable kernels
i've dpkeg from woody...with no success as well...the biggest hassle
now is that i don't even have a bootable 2.4.18 bloody kernel since my
.config always seems to get screwed up with options i consider very
carefully...my question is (or maybe i should look into rdev?), is
there someway to use the given /boot/config-2.4.18bf2-4 or
/boot/conf**-686-smp configuration file for a new build...without
'make' failing on me when i try their copied .config from boot to then
use for what to compile against the 2.4.18 tree?(i tried doing this
without success...but please readon...)?...i've also been exhausted
with the attempt of getting e100.o (successfully built 2.4.18 and
e100.o for 2.4.18...but 2.4.18 doesn't boot with my system...yet! and
can't seem to find a fix for it, rdev?) to load properly.
so long as my e100.o is compiled for 2.4.18 and can't seem to not even
get it working for neither of my two other kernels by using modprobe
-f -t net "e100.o" (intel's e100.o built against 2.4.18 module
copied)...what more is there to do?...is there somethings i should
look into?...my lspci lists an intel ethernet controller so i know its
possible to get it working one way or another...i just can't wait to
get off this dam windoze and go blazing on my cable with debian...any
help would be greatly appreciated..thx..
jagg