Hi Doug;
I would suggest that you do through the debian-user and debian-devel
message archive lists (ie: on debian.org).
You have probably "been hit" by the "perl problem".
An "apt-get upgrade" may or may not (at this point) bring things to
a "sane" point.
Those of us that are using "potato"
On Sat, Jul 17, 1999 at 10:48:53PM -0700, Doug Thistlethwaite wrote:
>
> The error messages during the configureation of setserial said that my
> modules needed to be updated and to run
> "update-module force" and run configure again. Well, I did this and the
These days the Debian way is to crea
hello, i am new to this list, and love debian.
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org
On Sun, 18 Jul 1999, Doug Thistlethwaite wrote:
> Thanks for all of the help!
>
> I ended up removing the ne module and replaceing it with the io=0x300 irq=3
> specified in
Thanks for all of the help!
I ended up removing the ne module and replaceing it with the io=0x300 irq=3
specified in
the options.
I can now telnet to my system, so I think its fixed! I will check it out the
rest of
the way in the morning,
Doug
THANK YOU!
Doug
Jim wrote:
> The easiest way
On 07/17/99 11:59 PM, Doug Thistlethwaite wrote:
> Ok,
>
> I went into modconf and select "net" and "ne".
>
> It said that this module was currently installed on my system. It gave me
> two choices,
>
> Exit or Remove the module from the kernel.
> Where do I specify the io-0x300? I do not see
Ok,
I went into modconf and select "net" and "ne".
It said that this module was currently installed on my system. It gave me two
choices,
Exit or Remove the module from the kernel.
Where do I specify the io-0x300? I do not see anywhere in the modconf that
allows me to
edit anything.
Doug
J
The easiest way for us to fix this would be by running modconf. Hopefully
nothing else is broken (which we'll find out soon).
As root, run:
modconf
Then go to "net" and then "ne" and enable the module for your card. The
reason you aren't detecting the card? modprobe will generally only detect
Thanks for the reply.
I am not sure if I was using module or kernel for the network card. I have had
this system for awhile (potato is the third debian distrubution I have used, and
the network settings were setup at the very beginning. How would I tell? The
current kernel version seems to be 2
On 07/17/99 10:48 PM, Doug Thistlethwaite wrote:
> Hello, I hope someone can help me with this. It seems like it should
> not to hard to fix, but without any knowledge of how or where the
> network services are started / initialized, I don't think I will figure
> it out without help.
>
Hmm. I;m
Thanks for the reply Jim!
I have a standard NE2000 card (cheap one I got for about $20).
Everything was working fine until my last moves that I described below. My
network was
working after the potato upgrade until I "fixed" the last two problems taht
dselect
caused. I rebooted, and the netwo
Hello, I hope someone can help me with this. It seems like it should
not to hard to fix, but without any knowledge of how or where the
network services are started / initialized, I don't think I will figure
it out without help.
I upgraded my slink system to potato using dselect about a week ago.
11 matches
Mail list logo
