 |
|
| Linux Forum Index » Linux - Slackware Forum » Help: Network Card Oddity... |
|
Page 1 of 1 |
|
| Author |
Message |
| sam... |
 Posted: Thu Nov 05, 2009 5:51 pm |
|
|
|
Guest
|
I have a Linux 10.2 box on a cable modem and router (Linksys/Cicso)
that I use for my web server. Yesterday, my router stopped working
for my telephone and internet *only* when I had the linux server
connected via cable (from box to router). When I unplugged it, and
plugged it back in, it worked for about an hour, then the phone
and internet went out again. If I leave the web server disconnected,
everything works fine.
Any thoughts?
Thanks,
s |
|
|
| Back to top |
|
|
|
| Lew Pitcher... |
| Posted: Thu Nov 05, 2009 5:51 pm |
|
|
|
Guest
|
On Nov 5, 5:51 pm, sam <nos... at (no spam) nospam.spam> wrote:
Quote: I have a Linux 10.2 box on a cable modem and router (Linksys/Cicso)
that I use for my web server. Yesterday, my router stopped working
for my telephone and internet *only* when I had the linux server
connected via cable (from box to router). When I unplugged it, and
plugged it back in, it worked for about an hour, then the phone
and internet went out again. If I leave the web server disconnected,
everything works fine.
Any thoughts?
Yah. Either your router or the ethernet card on your Linux system or
the cable between them is snafu.
The cheapest and easiest thing to fix is the ethernet UTP between the
Linux system and the router. Check this first. Reseat each end. If
that doesn't fix the problem, swap it out with a different cable.
The next cheapest/easiest thing to fix is the ethernet card in your
Linux system. Check to see that you are using the correct Linux
driver. Load the proper driver, if you need to. Take a look at /var/
log/syslog, /var/log/messages, and /var/log/debug to see what sort of
errors Linux is complaining about. Also look at your dmesg to see if
there are any kernel messages that might explain the problem. Swap out
your ethernet card with a new one (shouldn't cost more than $15 for a
good PCI ethernet card), load the proper driver, and check if that
fixes the problem.
Finally, the most costly thing to fix is the router. If it is
malfunctioning, you /might/ find a firmware update to fix it.
Otherwise, toss the thing out and replace it with a new router.
Other than those generic steps, there's nothing we can really tell
you.
HTH |
|
|
| Back to top |
|
|
|
| Auric__... |
| Posted: Thu Nov 05, 2009 6:26 pm |
|
|
|
Guest
|
On Thu, 05 Nov 2009 22:51:26 GMT, sam wrote:
Quote: I have a Linux 10.2 box on a cable modem and router (Linksys/Cicso)
that I use for my web server. Yesterday, my router stopped working
for my telephone and internet *only* when I had the linux server
connected via cable (from box to router). When I unplugged it, and
plugged it back in, it worked for about an hour, then the phone
and internet went out again. If I leave the web server disconnected,
everything works fine.
Any thoughts?
Either you're from the future, or else you mean Slackware 10.2. ;-)
--
Sometimes I lie awake at night and ask, "Why me?" Then a voice answers,
"Nothing personal, your name just happened to come up." |
|
|
| Back to top |
|
|
|
| Dan C... |
| Posted: Fri Nov 06, 2009 11:15 pm |
|
|
|
Guest
|
On Fri, 06 Nov 2009 20:40:54 +0100, Henrik Carlqvist wrote:
Quote: Dan C <youmustbejoking at (no spam) lan.invalid> wrote:
The power supply in a router doesn't power anything but the router.
Adding more connections to it does not affect the P/S at all.
You seem really sure that the number of connections and the activity on
those connections does not affect the power usage at all?
I have seen a few router which have leds indicating which network ports
are in use and if there is any activity on the ports. Knowing that leds
draw a little current when lit I feel rather sure that more connections
does affect the current the PS will have to supply. I would be rather
surprised if the router only needed current for the leds, my guess is
that the logic circuits in the router also needs current and I would
also guess that this current depends upon the load on the router.
The additional LED's make a negligible difference, and the "logic
circuits" are already powered up regardless of load.
So, yes, I'm sure that my original statement is correct.
--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he garotted another passing Liberal.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/ |
|
|
| Back to top |
|
|
|
| Grant... |
| Posted: Fri Nov 06, 2009 11:39 pm |
|
|
|
Guest
|
On 07 Nov 2009 04:15:19 GMT, Dan C <youmustbejoking at (no spam) lan.invalid> wrote:
Quote: On Fri, 06 Nov 2009 20:40:54 +0100, Henrik Carlqvist wrote:
Dan C <youmustbejoking at (no spam) lan.invalid> wrote:
The power supply in a router doesn't power anything but the router.
Adding more connections to it does not affect the P/S at all.
You seem really sure that the number of connections and the activity on
those connections does not affect the power usage at all?
I have seen a few router which have leds indicating which network ports
are in use and if there is any activity on the ports. Knowing that leds
draw a little current when lit I feel rather sure that more connections
does affect the current the PS will have to supply. I would be rather
surprised if the router only needed current for the leds, my guess is
that the logic circuits in the router also needs current and I would
also guess that this current depends upon the load on the router.
The additional LED's make a negligible difference, and the "logic
circuits" are already powered up regardless of load.
Except for a certain netgear router with weak power supply that
did struggle when too many LEDs lit, active channels  Forget
the model, it was Gigabit 8 channel.
Grant.
--
http://bugsplatter.id.au |
|
|
| Back to top |
|
|
|
| Sylvain Robitaille... |
| Posted: Fri Nov 13, 2009 7:12 am |
|
|
|
Guest
|
I'm coming in late on this, but there are a couple of points that I feel
I can contribute to, at little risk of continuing to beat the already
dead horse ...
On 06 Nov 2009 17:22:13 GMT, goarilla wrote:
Quote: ... i had a crappy router that resetted when i torrented and had more
than 200 connections ...
Perhaps, but this is not a power-supply issue, which is what had been
suggested to this point.
Quote: then there's power over lan ...
In a switch, not in a router.
Well, except that I'm not sufficiently familiar with the
"consumer-electronics" versions of these to know whether PoE
(power over Ethernet) has been built into any of the all-in-one
router/switch/wireless-access-point/broadband-gateway things ...
In "real" equipment, though, Power over Ethernet is provided from the
switch or from a separate device inline between the switch and the
powered device.
--
----------------------------------------------------------------------
Sylvain Robitaille syl at (no spam) encs.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
---------------------------------------------------------------------- |
|
|
| Back to top |
|
|
|
| Sylvain Robitaille... |
| Posted: Fri Nov 13, 2009 7:16 am |
|
|
|
Guest
|
On Fri, 6 Nov 2009 11:59:17 -0600, sam wrote:
Quote: I took the box to the garage and blew out the dust with my
air compressor. Then I did a fresh install of Slackware 13.
It's been a whole day and no problems so far.
I've seen similar situations. If it acts up again, remove socketed
items (whether they be PCI cards, memory modules, CPUs and other chips),
and blow air into the sockets as well. Reassemble carefully, and the
system should be fine. Cleaning out dust is one of the first things I
do to computers (or other electronic items) that are acting up. It can
often be the only required remedy.
--
----------------------------------------------------------------------
Sylvain Robitaille syl at (no spam) encs.concordia.ca
Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
---------------------------------------------------------------------- |
|
|
| Back to top |
|
|
|
| Grant... |
| Posted: Fri Nov 13, 2009 6:43 pm |
|
|
|
Guest
|
On Fri, 13 Nov 2009 17:16:29 +0000 (UTC), Sylvain Robitaille <syl at (no spam) alcor.concordia.ca> wrote:
Quote: On Fri, 6 Nov 2009 11:59:17 -0600, sam wrote:
I took the box to the garage and blew out the dust with my
air compressor. Then I did a fresh install of Slackware 13.
It's been a whole day and no problems so far.
I've seen similar situations. If it acts up again, remove socketed
items (whether they be PCI cards, memory modules, CPUs and other chips),
and blow air into the sockets as well. Reassemble carefully, and the
system should be fine. Cleaning out dust is one of the first things I
do to computers (or other electronic items) that are acting up. It can
often be the only required remedy.
And, check for bulging or leaking capacitors around the CPU socket and
graphics card, these should be replaced. Symptom of cap. fault is that
the mobo is reluctant to startup, but once started seems to work okay.
If left alone eventually the CPU and/or other chips blow up due to
power supply spiking.
I've seen bulging caps in the PSU too, it's worth opening up the PSU
to blow dust out and check the fan bearings oiled, as well as for bad
caps.
Grant.
--
http://bugsplatter.id.au |
|
|
| Back to top |
|
|
|
| sam... |
| Posted: Fri Nov 13, 2009 6:52 pm |
|
|
|
Guest
|
In article <qirrf5pf9jbdvl00dr5tao3abgeejah3pi at (no spam) 4ax.com>,
g_r_a_n_t_ at (no spam) bugsplatter.id.au says...
Quote:
On Fri, 13 Nov 2009 17:16:29 +0000 (UTC), Sylvain Robitaille <syl at (no spam) alcor.concordia.ca> wrote:
On Fri, 6 Nov 2009 11:59:17 -0600, sam wrote:
I took the box to the garage and blew out the dust with my
air compressor. Then I did a fresh install of Slackware 13.
It's been a whole day and no problems so far.
I've seen similar situations. If it acts up again, remove socketed
items (whether they be PCI cards, memory modules, CPUs and other chips),
and blow air into the sockets as well. Reassemble carefully, and the
system should be fine. Cleaning out dust is one of the first things I
do to computers (or other electronic items) that are acting up. It can
often be the only required remedy.
And, check for bulging or leaking capacitors around the CPU socket and
graphics card, these should be replaced. Symptom of cap. fault is that
the mobo is reluctant to startup, but once started seems to work okay.
If left alone eventually the CPU and/or other chips blow up due to
power supply spiking.
I've seen bulging caps in the PSU too, it's worth opening up the PSU
to blow dust out and check the fan bearings oiled, as well as for bad
caps.
Grant.
It's been a week and it's still going. It might be fine for
a while, but I'm still scoping around on Craiglist for a cheap
backup, just in case.
s |
|
|
| Back to top |
|
|
|
|
|
All times are GMT - 5 Hours
The time now is Sun Mar 21, 2010 9:05 pm
|
|