Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave
Hello!
I've finally solved it!
- The error messages by commenting some entries in the network script,
- The card problem by changing the BIOS! Yeah, I can't believe it myself,
but I simply had not remembered that a non-pnp card was using IRQ9 and I had
not told that to the bios which also gave
On Wed, Oct 27, 1999 at 02:23:16PM +0200, Stephan Hachinger wrote:
Hello!
I've finally solved it!
Great, now you should have a look at your MUA and MTA,
because you posted the same mail 5 times!
JY
--
Jean-Yves F. Barbier [EMAIL PROTECTED]
It is easier to change the specification to fit
I had this problem and it turned out the card was trying to use an IRQ of 0.
Fixed it by cd-ing into the modules directory and loading each module in
turn 'til I found one that worked.
config problems - please help
Hello!
I've got problems setting up my network card (Etherlink III 509b) on my
slink box, running a self-compiled 2.2.12 kernel.
The network tools in netbase are recompiled potato ones.
When booting, I get the messages (from which program???):
SIOCADDART
-BEGIN PGP SIGNED MESSAGE-
On Sun, 24 Oct 1999, Harlan Crystal wrote:
I believe this results from when you upgrade your
kernel from the older series to the 2.2.x series.
The older kernels had a Route command which is used
in various startup scripts, but the newer series
is
looks like the driver for the card isnt loaded.
nate
[mailto:[EMAIL PROTECTED] ]--
Linux System Administrator http://www.firetrail.com/
Firetrail Internet Services Limited http://www.aphroland.org/
Everett, WA 425-348-7336
Hello!
I've got problems setting up my network card (Etherlink III 509b) on my
slink box, running a self-compiled 2.2.12 kernel.
The network tools in netbase are recompiled potato ones.
When booting, I get the messages (from which program???):
SIOCADDART: Invalid argument
SIOCSIFADDR: Operation
11 matches
Mail list logo