RE: Kernel 2.4.0 vs 3Com NIC
out on a limb here but ... if you compiled 2.4.0 with support for your nic
selected would it not be normal for the module to fail ? Is your nic not
active in any way ? no ping, no tracert ? ifconfig ?
greetings,
J.L.
-----Original Message-----
From: Viktor Rosenfeld [mailto:rosenfel@informatik.hu-berlin.de]
Sent: Sunday, January 21, 2001 11:11 PM
To: debian-user@lists.debian.org
Subject: Kernel 2.4.0 vs 3Com NIC
Hi,
okay I have compiled and installed the new kernel on my woody system.
The compile went without problems and the kernel boots up with no error
messages (at least if I don't mount devfs, looks like devfsd is not
setting some symlinks properly like /dev/rtc ...)
The kernel won't recognize my network card though. I have a 3Com
Etherlink III card, which is supported by the 3c509 driver. I have it
compiled-in with kernel 2.2.18 and I've never had problems before. It
won't work with kernel 2.4.0 though, when I have it compiled-in. When I
compile it as a module and try to modprobe it, I get:
23:02 root@bart:/home/viktor # modprobe 3c509
/lib/modules/2.4.0/kernel/drivers/net/3c509.o: invalid parameter parm_io
/lib/modules/2.4.0/kernel/drivers/net/3c509.o: insmod
/lib/modules/2.4.0/kernel/drivers/net/3c509.o failed
/lib/modules/2.4.0/kernel/drivers/net/3c509.o: insmod 3c509 failed
23:02 root@bart:/home/viktor
#
I have up-to-date modutils (2.4.1) from woody and I can modprobe other
modules without problems.
23:02 root@bart:/home/viktor # lsmod
Module Size Used by
dummy 1168 0 (unused)
23:02 root@bart:/home/viktor
#
Any idea what I could be missing?
MfG Viktor
--
Viktor Rosenfeld
WWW: http://www.informatik.hu-berlin.de/~rosenfel/
Geek Code (3.1):
GCS/SS d-@ s+: a20 C++@ UL++$ P+ L+++ E--- W++ N++ o? K? !W O? M? V?
PS++@ PE+(-) Y+ P?(+++) t+ 5+ X- R? !tv b+ DI+ D- G e>+++ h-- r- !y+
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
Reply to: