This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Wired network connection question [SOLVED]

Tags: None
(comma "," separated)
User avatar
NickElliott
Registered Member
Posts
258
Karma
3
OS
If I switch on my router after I've booted into KDE I'd expect the network connection to be enabled automatically, but it isn't.

Both ifconfig and Network Settings don't even see the wired interface (it is greyed out in Network Settings).

I've tried many things including restarting the network service but the only solution seems to be to reboot.

On a similar note if the network is disconnected during a session, and then reconnected, the connection does not restore - though it might do after a very long delay but I'm not sure what the trigger is.

My netbook has no such problems. Does anyone know of any settings I can adjust which will prevent this?

Last edited by NickElliott on Mon Aug 29, 2011 10:03 am, edited 1 time in total.


NickElliott, proud to be a member of KDE forums since 2008-Oct.
User avatar
bcooksley
Administrator
Posts
19765
Karma
87
OS
Have a look at output of "ifconfig -a" to see if the interface is being detected correctly. This looks like a issue in NetworkManager itself.


KDE Sysadmin
[img]content/bcooksley_sig.png[/img]
User avatar
NickElliott
Registered Member
Posts
258
Karma
3
OS

Re: Wired network connection question

Fri Aug 26, 2011 11:52 am
If I run "ifconfig -a" after booting with the router powered OFF the interface "eth0" is not detected, just loopback.

Subsequently powering on the router makes no difference, only a reboot will cause "eth0" to be listed using "ifconfig -a".

I added a wired connection in Network Connections and repeated the test but this did not make any difference.


NickElliott, proud to be a member of KDE forums since 2008-Oct.
lamarque
Registered Member
Posts
152
Karma
2
OS
This looks like a driver problem or something blocking the network interface. Which ethernet card (lspci) and distribution do you use?


Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer
User avatar
NickElliott
Registered Member
Posts
258
Karma
3
OS

Re: Wired network connection question

Sat Aug 27, 2011 11:43 pm
It's a Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller on Kubuntu.


NickElliott, proud to be a member of KDE forums since 2008-Oct.
lamarque
Registered Member
Posts
152
Karma
2
OS
does dmesg shown any message reggarding eth0 interface? Which kernel version do you use?


Software engineer at Petrobrás http://www.petrobras.com.br/en/about-us/
KDE's Network Management maintainer
User avatar
NickElliott
Registered Member
Posts
258
Karma
3
OS
Hello lamarque,

Thank you for your help working through this.

Kernel is 2.6.38-11-generic

If I boot the machine without a live network connection dmesg shows no message regarding eth0, in fact the network interface driver is not loaded at all - effectively the interface is invisible.

Compare this to when I boot with a live network connection - I see these references in dmesg:

r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:04:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
r8169 0000:04:00.0: setting latency timer to 64
r8169 0000:04:00.0: irq 44 for MSI/MSI-X
r8169 0000:04:00.0: eth0: RTL8168c/8111c at 0xffffc90000c74000, 00:1f:d0:23:31:f5, XID 1c4000c0 IRQ 44

Plus some later messages when it brings up the eth0 link.


NickElliott, proud to be a member of KDE forums since 2008-Oct.
User avatar
NickElliott
Registered Member
Posts
258
Karma
3
OS

Re: Wired network connection question

Mon Aug 29, 2011 10:02 am
Ok I have now resolved this issue, thanks (especially to lamarque) for help in troubleshooting.

There is a 'Green LAN' setting in my PCs BIOS which will automatically disable the controller when a LAN cable is not detected, this was enabled, I have now disabled this setting - simple as that!

Thanks again.


NickElliott, proud to be a member of KDE forums since 2008-Oct.


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]