Network

lacktchou · 2015-08-30 22:36:31

I have installed Voyager xfce 14.04.4 HD
I use a Netgear router and i cannot have a wifi connection, only a wired connection
My laptop is a lenovo g560
On another partition KDE, the same router connect ok in wifi
On another partition Cinnamon, the router connect ok in wifi
But not on the partition with voyager 14.04.4 HD.
In the menu of the network it is on but the is an X in the icon.
Do you have a solution for me, please?
Thanks
smile

Jerry3904 · 2015-08-31 00:05:37

I don't know anything about Voyager, though I see from a quick glance that it is a derivative of Xubuntu. And I have trouble believing that your problem has anything to do with Xfce.

But could you run this command as root and paste the result back here:

ifconfig

And also these two:

lspci

lsusb

Finally, which network manager are you using?

lacktchou · 2015-08-31 00:53:32

Jerry3904 wrote:

I don't know anything about Voyager, though I see from a quick glance that it is a derivative of Xubuntu. And I have trouble believing that your problem has anything to do with Xfce.
But could you run this command as root and paste the result back here:
ifconfig
And also these two:
lspci
lsusb
Finally, which network manager are you using?

lacktchou@Lenovo:~ > sudo ifconfig [sudo] password for lacktchou:  eth0      Link encap:Ethernet  HWaddr b8:70:f4:0e:1f:52             UP BROADCAST MULTICAST  MTU:1500  Metric:1           Packets reçus:0 erreurs:0 :0 overruns:0 frame:0           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 lg file transmission:1000            Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)  lo        Link encap:Boucle locale             inet adr:127.0.0.1  Masque:255.0.0.0           adr inet6: ::1/128 Scope:Hôte           UP LOOPBACK RUNNING  MTU:65536  Metric:1           Packets reçus:36578 erreurs:0 :0 overruns:0 frame:0           TX packets:36578 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 lg file transmission:0            Octets reçus:16214448 (16.2 MB) Octets transmis:16214448 (16.2 MB)  wlan0     Link encap:Ethernet  HWaddr ac:81:12:5d:d3:12             inet adr:192.168.1.5  Bcast:192.168.1.255  Masque:255.255.255.0           adr inet6: fe80::ae81:12ff:fe5d:d312/64 Scope:Lien           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           Packets reçus:41144 erreurs:0 :0 overruns:0 frame:0           TX packets:37233 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 lg file transmission:1000            Octets reçus:29253039 (29.2 MB) Octets transmis:7182879 (7.1 MB)  lacktchou@Lenovo:~ >

 sudo lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 05)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05)
00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)                                                                                    
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
05:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
lacktchou@Lenovo:~ >

 sudo lsusb
Bus 002 Device 007: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)
Bus 002 Device 005: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 002 Device 004: ID 04f2:b273 Chicony Electronics Co., Ltd 
Bus 002 Device 003: ID 0480:a006 Toshiba America Info. Systems, Inc. 
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

How to find network manager?

Jerry3904 · 2015-08-31 01:38:28

Here's the likely culprit:

05:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01)

That chip needs special love in Linux, and you will see a lot of hits if you do a web search on "linux bcm4313." It requires a kernel module (brcm80211) to be loaded that is often blacklisted in the file /etc/modprobe.d/broadcom-sta-dkms.conf

I know nothing about your OS, so can't say what is happening in your particular case. But here is the always reliable Arch Wiki to get you started on the general topic:

https://wiki.archlinux.org/index.php/Broadcom_wireless

Bottom line: Xfce is a desktop environment and has AFAIK no impact on kernelspace where all the problems are located in this situation. If Voyager OS resources are not sufficient, I imagine you would want to turn to the Xubuntu or Ubuntu forums from which I gather it derives. Good luck.

Last edited by Jerry3904 (2015-08-31 11:41:33)

MountainDewManiac · 2015-08-31 17:28:06

I second that response, lol. It's been a while (two or three years), but I had version one (zero?) of one of those Broadcom things. I'd had to follow special procedures to get it working. Then a new version of the distro I was using came out and I was told "Broadcom support is in the kernel now, no special song & dance required." Only that didn't work with the first version of the hardware, so not only was I still forced to jump through hoops, I had to blacklist what was already there.

The good news is that the Broadcom stuff was popular hardware (Microsoft compatibility, I assume), so there's lots of information about it on the Internet. One thing I'd suggest is to find out exactly what version (revision?) of the hardware you have, because the steps to a solution might be different. I'm sorry, but due to the time since I've had to deal with it and the fact that I have a different laptop now, I no longer have any relevant links in my web browser or information.

Regards,
MDM

Jerry3904 · 2015-08-31 17:38:49

Forgot to say: a link you may need to know about:

http://linuxwireless.org/

InsideJob · 2015-09-03 02:17:21

The Raspberry Pi Foundation uses Broadcom so support has improved but you still need non-free firmware in most cases. You'll also need the wireless-tools package which has iwlist and iwconfig. those are usually the first two commands... iwlist wlan0 scan and then something like iwconfig wlan0 essid "mywifi" before you ifconfig the interface up.

Be careful about two different network managers handling the interfaces...t hat's usually the sounce of my problems. I tell Wicd not to touch eth0 and just handle wlan0 for example. That way my /etc/network/interfaces setting aren't ignored/overridden

Xfce Forum

Sub domains

#1 2015-08-30 22:36:31

Network

#2 2015-08-31 00:05:37

Re: Network

#3 2015-08-31 00:53:32

Re: Network

#4 2015-08-31 01:38:28

Re: Network

#5 2015-08-31 17:28:06

Re: Network

#6 2015-08-31 17:38:49

Re: Network

#7 2015-09-03 02:17:21

Re: Network

Board footer