[lkml]   [2002]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: misconfiguration of ne.o module in 2.2.19 damaged hardware. Is it normal?
Juhan Ernits <> said:


> I installed linux on this box (Debian 2.2r4, kernel version 2.2.19).
> Then when configuring the network the module ne.o was chosen.
> I was sure about the io address but not so sure about the irq. So I
> configured the module with only io address parameter.

This is enough, IRQ can be found from that datum. I assume this is an ISA
NIC? If PCI, no such parameters are needed. BTW, NE clones are (in)famous
for their bizarre assortment of bugs, you might have hit one that doesn't
work with Linux.

> At this point no problems occurred.
> Then I configured the network address but the device eth0 did not appear
> to be available (naturally, due to misconfiguration). Since it was part of
> automated install I decided to reboot after this.

What does lsmod(8) tell you? If you do an "modprobe ne io=..." what does it

If your guess at IO is wrong, nothing happens. If the NIC is _not_ an NE,
strange things could very well happen. It might be broken, not installed
correctly, jumpers set wrong, ...
Horst von Brand # 22616
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:18    [W:0.070 / U:0.192 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site