On Tue, 02 Dec 2003 22:39:16 +0100 John Smith <[EMAIL PROTECTED]> wrote:
On Tue, 2003-12-02 at 20:51, Watwe, Abhay wrote:I have a Dell Dimension 8300 PC with master HD of 120 GB with
Windows XP on it. I installed Debian ´potato¡ on a slave HD (6GB). Kerner version is 2.2.19. I did NOT build my own kernel, I used the
one which came on the CD. My network card is an Intel Pro 100 M PCI
NIC card. I downloaded the Intel Pro 100 M adapter driver source
from Intel and compiled it. However, when I go and try to
Modprobe e100.0
<snip>
You might try 'lspci' or 'lspci -v' to check wether your e100 is visible. Mine shows up as
00:09.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 09) Subsystem: Intel Corp.: Unknown device 2204 Flags: bus master, medium devsel, latency 66, IRQ 11 Memory at 41280000 (32-bit, non-prefetchable) [size=4K] I/O ports at 3440 [size=64] Memory at 41200000 (32-bit, non-prefetchable) [size=128K] Expansion ROM at <unassigned> [disabled] [size=1M] Capabilities: [dc] Power Management version 2
kernel 2.4.18 I load eepro100 (check with lsmod) and it works perfectly.
And since you mention you're using kernel 2.2.19, it's an easy "apt-get install kernel-image-2.4.18" to upgrade to the 2.4.18 kernel with a newer ee100 driver.
(Note: You may need to do an "apt-get update" first to grab the latest list of packages from debian, if you haven't done that since the install.)
Er, except to download the kernel via the network, his network card needs to work. Doh!
Still, I concur with Jacob; a newer kernel might solve your problem. You might use the Windows side (or Knoppix), to get the newer kernel.
Also, I believe you want to "modprobe e100" instead of "modprobe e100.O"; I'm not sure it matters, but I sortta kindda in a way think it does.
-- Kent
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
