I just downloaded the 2.1.115 kerenl source today (my first
development kernel) and compiled it. Everything seemed to compile ok
and when I rebooted eveyrthing appeard to be working normally. However
my eepro100 ethernet card was not functioning properly (error messages
below) and I was thus unable to access the internet (note: I have to
ethernet cards, one compiled into the kernel one as a module, the
eepro100 is a module). Ifconfig listed the card and in /proc/interrupts
it was listed also, isnmod seemed to work also. The other card seemingly
works fine in 2.1.115. The eepro100 works fine in 2.0.35 and I havent
really experienced any problems.
When I was upgrading from 2.0.33 to 2.0.34 (maybe 2.0.32 to 2.0.33)
I noticed similar problems with the driver for the card. When I first
installed Linux, the driver wasn't included with the kernel src and I
had to fetch it off the web (2.0.27?), so everytime I would recompile
the kernel I recompiled the module. However, 2.0.34 (.33?) included the
driver and my old one seemed to stop working (similar error messages(.
When I recompiled the new driver (included with kenrel src) and used it,
everything worked fine. The eepro100 driver included with 2.1.x seems to
be older than the one included with 2.0.35, I found this out by the date
they listed when you inserted them, the 2.0.35 is dated 4/98 while the
2.1.115 is dated somewhere in 10/97. I'm guessing the driver hasn't been
updated for 2.1.x yet, but figured best to confirm. When I attempted to
compile (under 2.1.115) the eepro100.c included in 2.0.35 src using the
compile command given in eepro100.c, it failed. Any help or information
concerning this issue would be greatly appreciated.
On a slightly unrelated note, I am also experiecing reboot problems.
I am currently running redhat 5.0 with most of the stuff in errata
patched. Whenever I reboot in 2.0.xx, It _always_ freezes on umounting
the local drives (first thought it might be a nfs thing, but turned out
not to be). It is a real pain in the a** becuase besdies slowly messing
up my fs, it also takes forever to reboot because <sarcasm> fsck is
soooo fast </sarcasm>. I've tired quite a few things to no avail.
Surprisingly, I don't experience this problem under 2.1.xxx, it seems to
reboot without a problem. Any suggestions or ideas on possibilie
solutions would be really nice. Thanks for your time.
Sincerely,
Nadeem Riaz
Here are some kernel (2.1.115) error messages:
eth1: Transmit timed out: status 0090 command 0000.
eth1: Tx timeout fill index 23 scavenge index 8.
Tx queue 000c0000 00000000 000c0000 000c0000 00000000 000c0000
00000000 0000a000 00000000 00000000 000c0000 000c0000 000c0000 00000000
000c0000 000c0000.
Rx ring 00000001 00000001 00000001 00000001 00000001 00000001
00000001 00000001 00000001 00000001 00000001 00000001 00000001 00000001
00000001 c0000002.
eth1: Transmit timed out: status 0090 command 0000.
eth1: Tx timeout fill index 23 scavenge index 8.
Tx queue 000c0000 00000000 000c0000 000c0000 00000000 000c0000
00000000 0000a000 00000000 00000000 000c0000 000c0000 000c0000 00000000
000c0000 000c0000.
Rx ring 00000001 00000001 00000001 00000001 00000001 00000001
00000001 00000001 00000001 00000001 00000001 00000001 00000001 00000001
00000001 c0000002.
eth1: Transmit timed out: status 0090 command 0000.
eth1: Tx timeout fill index 23 scavenge index 8.
Tx queue 000c0000 00000000 000c0000 000c0000 00000000 000c0000
00000000 0000a000 00000000 00000000 000c0000 000c0000 000c0000 00000000
000c0000 000c0000.
Rx ring 00000001 00000001 00000001 00000001 00000001 00000001
00000001 00000001 00000001 00000001 00000001 00000001 00000001 00000001
00000001 c0000002.
eth1: Transmit timed out: status 0090 command 0000.
eth1: Tx timeout fill index 23 scavenge index 8.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html