On 19/06/14 04:09, John Andersen wrote:
On 06/18/2014 06:33 AM, Basil Chupin wrote:
On 18/06/14 19:05, Daniel Bauer wrote:
Am 18.06.2014 03:12, schrieb Basil Chupin:
On 17/06/14 23:52, Daniel Bauer wrote:
[pruned]
There is the wired desktop and max. 3 laptops/wifi-phones at the same time. The telefonica router does (did?) it's job good enough for me.
However, there's a friend moving house in a few days and then I can try if my problem persists using his router/cable... and then I look further...
I'll let the list know.
Meanwhile I'll train my social skills, just in case. Happy to have Chile-Spain tomorrow, because there's space in the street cafés and my usual male competitors sit in the restaurants in front of a screen forgetting even the nicest minifaldas close to them - my advantage...
:-)
Daniel You haven't answered my question whether your LAN is connected to the onboard chip in your computer or to a (PCI/PCIe) NIC in the computer. Either one could be playing up causing you your problem.
BC
Sorry Basil, it is connected to the onboard chip, which is a RTL 8111/8168 PCI Express Gigabit Ethernet controller by Realtek (thats what KDE Info-Center says...)
Daniel
Thanks Daniel.
As my earlier post states the chip on my mobo stopped working a couple of days after installation and I replaced it with a PCI (in my case a PCIe) NIC. The cost of such a card is less than a packet of cigarettes (if you smoke, and are living here in Australia!). Get yourself a gigabit NIC card which may solve your problem. If it does not solve the problem then at least you have gone some way to determine, at a VERY small price (a NIC is now peanuts to buy) that the problem is not in the onboard chip or the NIC and so we must look at the cable and, progressing up the line, at the modem/router. But first things first so start with installing a NIC. I won't mention any brand names as the same brand is sold under different names in different countries - but when buying make sure that it suits your motherboard: PCI or PCIe, and that your m/board has an available slot for it.
BC
While all very interesting, I don't see how this bears on Daniel's problem.
When a a nic fails to connect only upon rebooting, but otherwise works fine, and when rebooting the ROUTER fixes the problem, AND when this only came to pass with recent software updates, suggesting the he replace hardware seems a little off base.
This sounds more like a failure to negotiate (speed, duplex, etc) than anything else, and these are all software issues. I'd look into options for the Nic modules before I started replacing hardware.
Well, none of your suggestions have solved his problem so they, too, don't bear on his problem. With no specific reason for his problem having been offered so far any comment/suggest is to be considered because I, at least, have found that the most unlikely component or piece of equipment is capable of acting in the most unpredictable way. What one of the things I have found with a list such as this one is that people make a suggest/comment which then makes someone else suddenly remember of a (another) possible reason; and this exchange of ideas usually then leads to the right solution being produced. BC -- Using openSUSE 13.1, KDE 4.13.2 & kernel 3.15.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org