Hi All,
I seem to be having a similar issue to the one described here: NetworkManager: wireless disabled by default - FedoraForum.org but with opensuse 11.3.
Anyone have any idea how to get Network Manager to start with wireless enabled?
Once I click ‘enable wireless’ it connects just fine.
Thanks in advance.
kev.
I’m having the same thing on Linux Mint with my netbook. Would it happen to be Broadcom?
On which desktop? KDE, Gnome?
What works on KDE, is changing from Networkmanager-kde4 to plasmoid-networkmanagement (which IMHO is much better ). If you select the latter for install it will cause the uninstall of the first. You may have to edit the properties of the systray to make it show…
Another possible cause of this problem would be that You don’t have the drivers installed. Could You post the results of this command here ?
lspci -nnk
Best regards,
Greg
Yep. It’s broadcom.
Thanks I’m giving this a go now.
You’re right the plasmoid-networkmanagement is nicer than than Networkmanager-kde4. Unfortunately, it’s doing the same thing. When the machine boots up wi-fi is disabled.
Here’s what I get:
00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] RS780 Host Bridge Alternate [1022:9601]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
00:01.0 PCI bridge [0604]: Acer Incorporated [ALI] Device [1025:9602]
00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 0) [1022:9604]
Kernel driver in use: pcieport
00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge (PCIE port 1) [1022:9605]
Kernel driver in use: pcieport
00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: ahci
00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: ohci_hcd
00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: ehci_hcd
00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: ohci_hcd
00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: ehci_hcd
00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 41)
00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] (rev 40)
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: pata_atiixp
00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40)
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: HDA Intel
00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40)
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40)
00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration [1022:1200]
00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Address Map [1022:1201]
00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller [1022:1202]
00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control [1022:1203]
Kernel driver in use: k10temp
00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Link Control [1022:1204]
01:05.0 VGA compatible controller [0300]: ATI Technologies Inc M880G [Mobility Radeon HD 4200] [1002:9712]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: radeon
01:05.1 Audio device [0403]: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] [1002:970f]
Subsystem: Acer Incorporated [ALI] Device [1025:037b]
Kernel driver in use: HDA Intel
03:00.0 Ethernet controller [0200]: Broadcom Corporation NetLink BCM57780 Gigabit Ethernet PCIe [14e4:1692] (rev 01)
Subsystem: Acer Incorporated [ALI] Aspire 7740G [1025:033d]
Kernel driver in use: tg3
06:00.0 Network controller [0280]: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) [168c:002a] (rev 01)
Subsystem: Device [1a32:0306]
Kernel driver in use: ath9k
The relevant bit is at the bottom 
On 12/30/2010 07:06 PM, yu210148 wrote:
>
> Knurpht;2271910 Wrote:
>> What works on KDE, is changing from Networkmanager-kde4 to
>> plasmoid-networkmanagement (which IMHO is much better ). If you select
>> the latter for install it will cause the uninstall of the first. You may
>> have to edit the properties of the systray to make it show…
>
> You’re right the plasmoid-networkmanagement is nicer than than
> Networkmanager-kde4. Unfortunately, it’s doing the same thing. When
> the machine boots up wi-fi is disabled.
If the wireless network were disabled because the rfkill switch were in the
disable position, then the “Enable wireless” button would be grayed out. My
suspicion is that you have run with ifup at one time and have a configuration
file that is enabling the wired connection “onboot” rather than “ifplugd”.
To test this, look at the listing of the directory /etc/sysconfig/network. Is
file ifcfg-eth0 found there? If so, edit it (as root) and make sure that it has
a line like
STARTMODE='ifplugd'
A second thing to check is that your wireless connection in the Connection
Manager has “Connect automatically” checked.
Yes, when I first got the machine I set it to us ifup in yast’s network settings with the hardwired connection available to me at the time. I then switched it over to use network manager.
I changed the STARTMODE line in /etc/sysconfig/network/ifcfg-eth0 from:
STARTMODE='auto'
to
STARTMODE='ifplugd'
I’m not sure if it’s relevant but the same line in ifcfg-wlan0 is also set to:
STARTMODE='auto'
I’ve left that one as is and will now reboot and see where I stand.
Hummmm, still not coming up enabled. I’ll try changing the STARTMODE in ifcfg-wlan0 to ‘ifplugd’ as well and see if that has an effect.
No dice on that.
I did just double check that ‘connect automatically’ was checked off on the wireless connection that I’m using.
On 12/31/2010 09:06 AM, yu210148 wrote:
>
> Hummmm, still not coming up enabled. I’ll try changing the STARTMODE in
> ifcfg-wlan0 to ‘ifplugd’ as well and see if that has an effect.
That one should be “auto”.
I have no idea why your wireless is not coming up automatically.
Have you looked at /var/log/NetworkManager for any clues?
I’m looking through the log and found this from the last boot:
Dec 31 14:54:59 linux-ioxs NetworkManager: <info> (wlan0): bringing up device.
Dec 31 14:54:59 linux-ioxs NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Dec 31 14:54:59 linux-ioxs NetworkManager: <info> modem-manager is now available
Dec 31 14:54:59 linux-ioxs NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
Dec 31 14:54:59 linux-ioxs NetworkManager: <info> Trying to start the supplicant...
Dec 31 14:54:59 linux-ioxs NetworkManager: <info> (wlan0): supplicant manager state: down -> idle
Dec 31 14:54:59 linux-ioxs nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/netcontrol_services' exited with error status 127.
There’s no bluetooth adapter in the machine so the line about the bluez error makes sense. I’m less sure about the deactivating device (reason: 2) and the last line about netcontrol_services.
On 12/31/2010 02:06 PM, yu210148 wrote:
>
> There’s no bluetooth adapter in the machine so the line about the bluez
> error makes sense. I’m less sure about the deactivating device (reason:
> 2) and the last line about netcontrol_services.
I sent a copy of the log extract to the NM mailing list. If/when I get a
response, I’ll post here.
On 12/31/2010 03:01 PM, Larry Finger wrote:
> On 12/31/2010 02:06 PM, yu210148 wrote:
>>
>> There’s no bluetooth adapter in the machine so the line about the bluez
>> error makes sense. I’m less sure about the deactivating device (reason:
>> 2) and the last line about netcontrol_services.
>
> I sent a copy of the log extract to the NM mailing list. If/when I get a
> response, I’ll post here.
I got a response from Jirka Klimes, which is shown below between the lines of ===:
=============================================================
The line
Dec 31 14:54:59 linux-ioxs NetworkManager: <info> (wlan0): deactivating
device (reason: 2).
is not an error. That just says the device is now deactivated and the reason
code 2 - means “Device is now managed”.
You can check device states and reason codes in
http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/include/NetworkManager.h
> >
> > What should we be checking? AFAICT, everything in the Connection Manager is
> > correct.
> >
In the logs you should see entry like this:
NetworkManager[1287]: <info> WiFi enabled by radio killswitch; enabled by
state file
Verify rfkill state with:
rfkill list
Check NM states with:
nmcli nm
What are the versions of NetworkManager daemon and the applet?
=================================================================
Do you see the “Wifi enabled …” line in /var/log/NetworkManager? I did not in
mine, and my system works perfectly. That may not be in openSUSE’s version.
You can get the NetworkManager component versions from YaST => Software
Management. Search for “network”, then highlight “NetworkManager” and look at
the “Versions” tab. My system has version 0.8-8.2.1-x86_64. Then find the
version information for the “plasmoid-networkmanagement”, which you indicated
earlier that you had installed.
I thought we had established earlier that you did not have an rfkill problem,
but I couldn’t find the posting. When you have the network active, please run
the command
sudo zypper in rfkill
Then when your system is freshly booted, but wireless is not active, run the command
/usr/sbin/rfkill list
As for the “nmcli” command, I do not have that one in 11.3, but it is present in
11.4M5.
One additional step: Please post the output of the command “nm-tool” while at
the just booted but wireless not enabled state.
Cool, thanks see below.
Do you see the “Wifi enabled …” line in /var/log/NetworkManager? I did not in
mine, and my system works perfectly. That may not be in openSUSE’s version.
I didn’t see anything about wifi enabled but I did find this:
Jan 4 19:44:53 linux-ioxs NetworkManager: <info> WiFi disabled by radio killswitch; enabled by state file
Jan 4 19:44:53 linux-ioxs NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k')
You can get the NetworkManager component versions from YaST => Software
Management. Search for “network”, then highlight “NetworkManager” and look at
the “Versions” tab. My system has version 0.8-8.2.1-x86_64. Then find the
version information for the “plasmoid-networkmanagement”, which you indicated
earlier that you had installed.
The version of NetworkManager that’s installed is: 0.8-8.2.1-x86_64 and the plasmoid-networkmanagement version is 0.9.svn1057339-4.1-x86_64.
I thought we had established earlier that you did not have an rfkill problem,
but I couldn’t find the posting. When you have the network active, please run
the command
sudo zypper in rfkill
Done.
Then when your system is freshly booted, but wireless is not active, run the command
/usr/sbin/rfkill list
Okay give me a sec…
As for the “nmcli” command, I do not have that one in 11.3, but it is present in
11.4M5.[/QUOTE]