Re: WLAN
2012/5/29 Daniel Ackwonu > Hello! > > My name is Daniel and I am using Ubuntu on a new HP notebook. I have got > the problem that my Realtek Wlan card(RTL8111) is not recognized by my > operating system. I have tried a few things but it is still not working. If > one of you could help that would be great. > Thank you. > >> iwconfig >> lono wireless extensions. >> >> eth0 no wireless extensions. >> >> vboxnet0 no wireless extensions. >> > > Hello Daniel, Have you posted this on the Ubuntu Forum? http://ubuntuforum.org You may also try to use the command below to find out which hardware you have, and whether their drivers are correctly loaded. sudo lshw -C network ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN
On 05/31/2012 05:31 AM, Daniel Ackwonu wrote: Thank you for answering! The Output of lspci -nn is: daniel@linzuntu:~$ lspci -nn 00:00.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1705] 00:01.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:9647] 00:01.1 Audio device [0403]: ATI Technologies Inc Device [1002:1714] 00:02.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1707] 00:04.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:1709] 00:05.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:170a] 00:06.0 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:170b] 00:10.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7812] (rev 03) 00:10.1 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7812] (rev 03) 00:11.0 SATA controller [0106]: Advanced Micro Devices [AMD] Device [1022:7804] 00:12.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7807] (rev 11) 00:12.2 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7808] (rev 11) 00:13.0 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7807] (rev 11) 00:13.2 USB Controller [0c03]: Advanced Micro Devices [AMD] Device [1022:7808] (rev 11) 00:14.0 SMBus [0c05]: Advanced Micro Devices [AMD] Device [1022:780b] (rev 13) 00:14.1 IDE interface [0101]: Advanced Micro Devices [AMD] Device [1022:780c] (rev 40) 00:14.2 Audio device [0403]: Advanced Micro Devices [AMD] Device [1022:780d] (rev 01) 00:14.3 ISA bridge [0601]: Advanced Micro Devices [AMD] Device [1022:780e] (rev 11) 00:14.4 PCI bridge [0604]: Advanced Micro Devices [AMD] Device [1022:780f] (rev 40) 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1700] (rev 43) 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1701] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1702] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1703] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1704] 00:18.5 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1718] 00:18.6 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1716] 00:18.7 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1719] 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Device [1002:6741] 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) 03:00.0 Network controller [0280]: RaLink Device [1814:5390] 04:00.0 Class [ff00]: Realtek Semiconductor Co., Ltd. Device [10ec:5209] (rev 01) 04:00.1 SD Host controller [0805]: Realtek Semiconductor Co., Ltd. Device [10ec:5209] (rev 01) Two points of mailing list etiquette: (1) ALWAYS use the "Reply All" button - NEVER drop any list or individual. If your mailer does not have that feature, get a new mailer. People like me do what we can to help, but only if our exchange of information is in the public record. If you want private consulting, you need to pay for it. (2) Do not top post. By placing your reply at the bottom, everyone can read in natural order. With your reply at the top, one has to scroll down an up. Your wireless device is the one described by: > 03:00.0 Network controller [0280]: RaLink Device [1814:5390] The appropriate driver for newer kernels is rt2800pci. As you did not provide any information regarding kernel or distro information, I have no idea if that driver is included in the configuration, or if your kernel is too old to have support for the 5390. I suggest that you contact the mailing list for your distro and find out what it takes to support this device on their system. The latest versions of compat-wireless should work, but I have no idea if a precompiled version is available for your distro. Larry ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN
On 05/29/2012 04:18 AM, Daniel Ackwonu wrote: Hello! My name is Daniel and I am using Ubuntu on a new HP notebook. I have got the problem that my Realtek Wlan card(RTL8111) is not recognized by my operating system. I have tried a few things but it is still not working. If one of you could help that would be great. Thank you. iwconfig lo no wireless extensions. eth0 no wireless extensions. vboxnet0 no wireless extensions. The Realtek RTL8111 is a wired interface, not wireless. The output of the dmesg command should give you some indication of why the wireless device is not created. You are probably missing firmware. If the above does not provide any clues, please post the output of 'lspci -nn'. Larry ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On Mon, Mar 7, 2011 at 8:02 PM, Ozan Çağlayan wrote: > On 07.03.2011 19:01, Dan Williams wrote: > >> That message can only come from a user applet property set request from >> D-Bus. > > Actually this came to my mind right after posting the e-mail. It is the > new KDE4 applet. Should I blame it for this problem? > I confirm this issue under KDE NM applet; opened bug report: https://bugs.kde.org/show_bug.cgi?id=267967 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On Mon, 2011-03-07 at 19:02 +0200, Ozan Çağlayan wrote: > On 07.03.2011 19:01, Dan Williams wrote: > > > That message can only come from a user applet property set request from > > D-Bus. > > Actually this came to my mind right after posting the e-mail. It is the > new KDE4 applet. Should I blame it for this problem? Possibly. Here's what *might* be going on... usually GUI tools will hook a UI element like a checkbox up to a property so that the checkbox automatically updates when that property changes. In the case of the WiFi Enabled property, that's clearly the right thing to do as other tools besides the applet could toggle that property without the applet's knowledge, but the applet must still reflect the current state as provided by NetworkManager. But the applet must also respond to *user* initiated changes to that checkbox as well. Usually that happens when the applet attaches to the signal/slot that indicates the checkbox has been toggled, and upon receipt of that signal it tells NM to enable/disable wifi. But if the code also toggles the checkbox as a result of NM sending a property-changed signal, that could result in the NM change signal toggling the checkbox, which the applet interprets as the user clicking on the checkbox, which the applet then handles by telling NM to explicitly enable/disable wireless. Basically, the applet should never update NM's user wifi state based on signals from NM, or from NM's wifi hardware enabled state. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On 07.03.2011 19:01, Dan Williams wrote: > That message can only come from a user applet property set request from > D-Bus. Actually this came to my mind right after posting the e-mail. It is the new KDE4 applet. Should I blame it for this problem? Ozan Caglayan -- Pardus Linux http://www.pardus.org.tr/eng ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On Sun, 2011-03-06 at 18:03 +0200, Ozan Çağlayan wrote: > On 05.03.2011 17:31, Dan Williams wrote: > > > Need a bit more debug here; the --log-level=debug logs would be useful > > for starters. > > > > Dan > > Ok, the logs are attached. (This is the new NM 0.8.3.997) Is this also with nm-applet or some other GUI applet? The logs indicate that something external to NM is setting wireless as disabled by the user: NetworkManager[15750]: [1299426968.665704] [nm-manager.c:4456] manager_radio_user_toggled(): (WiFi): setting radio disabled by user That message can only come from a user applet property set request from D-Bus. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On 05.03.2011 17:31, Dan Williams wrote: > Need a bit more debug here; the --log-level=debug logs would be useful > for starters. > > Dan Ok, the logs are attached. (This is the new NM 0.8.3.997) Thanks, -- Pardus Linux http://www.pardus.org.tr/eng After pressing the rfkill button on laptop: --- NetworkManager[15750]: [1299426967.981710] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 4 flags 0x1002 NetworkManager[15750]: [1299426967.984006] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 4 flags 0x1043 NetworkManager[15750]: [1299426967.984789] [nm-udev-manager.c:477] handle_uevent(): UDEV event: action 'change' subsys 'rfkill' device 'rfkill2' NetworkManager[15750]: [1299426967.984948] [nm-udev-manager.c:204] recheck_killswitches(): WiFi rfkill state now 'soft-blocked' NetworkManager[15750]: [1299426967.984983] [nm-manager.c:1854] manager_rfkill_update_one_type(): WiFi hw-enabled 1 sw-enabled 0 NetworkManager[15750]: WiFi now disabled by radio killswitch NetworkManager[15750]: [1299426967.985045] [nm-manager.c:1690] manager_update_radio_enabled(): (wlan0): setting radio disabled NetworkManager[15750]: [1299426967.985064] [nm-device-wifi.c:3757] real_set_enabled(): (wlan0): device now disabled NetworkManager[15750]: (wlan0): device state change: 8 -> 2 (reason 0) NetworkManager[15750]: (wlan0): deactivating device (reason: 0). dhcpcd[15754]: received SIGTERM, stopping dhcpcd[15754]: wlan0: removing interface NetworkManager[15750]: (wlan0): canceled DHCP transaction, DHCP client pid 15754 NetworkManager[15750]: [1299426968.185839] [nm-device-wifi.c:1165] _set_hw_addr(): (wlan0): no MAC address change needed NetworkManager[15750]: [1299426968.185900] [nm-system.c:1362] flush_routes(): (wlan0): flushing routes ifindex 4 family INET (2) NetworkManager[15750]: [1299426968.186049] [nm-system.c:1277] dump_route(): route idx 1 family INET (2) addr 127.0.0.0/8 NetworkManager[15750]: [1299426968.186076] [nm-system.c:1277] dump_route(): route idx 1 family INET (2) addr 127.255.255.255/32 NetworkManager[15750]: [1299426968.186103] [nm-system.c:1277] dump_route(): route idx 1 family INET (2) addr 127.0.0.0/32 NetworkManager[15750]: [1299426968.186136] [nm-system.c:1277] dump_route(): route idx 1 family INET (2) addr 127.0.0.1/32 NetworkManager[15750]: [1299426968.186166] [nm-system.c:1277] dump_route(): route idx 1 family INET (2) addr 127.0.0.0/8 NetworkManager[15750]: [1299426968.186203] [nm-system.c:1277] dump_route(): route idx 1 family INET6 (10) addr 0:0:6100::903b:6502/0 NetworkManager[15750]: [1299426968.186236] [nm-system.c:1277] dump_route(): route idx 1 family INET6 (10) addr ::1/128 NetworkManager[15750]: [1299426968.186270] [nm-system.c:1277] dump_route(): route idx 1 family INET6 (10) addr 0:0:9100::5812:2306/0 NetworkManager[15750]: [1299426968.186399] [nm-system.c:222] sync_addresses(): (wlan0): syncing addresses (family 2) NetworkManager[15750]: [1299426968.639413] [nm-device-wifi.c:1331] real_is_available(): (wlan0): not available because not enabled NetworkManager[15750]: [1299426968.639463] [nm-device.c:3792] nm_device_state_changed(): (wlan0): device not yet available for transition to DISCONNECTED NetworkManager[15750]: (pid 15754) unhandled DHCP event for interface wlan0 NetworkManager[15750]: [1299426968.647490] [nm-netlink-monitor.c:117] link_msg_handler(): netlink link message: iface idx 4 flags 0x1002 NetworkManager[15750]: [1299426968.665704] [nm-manager.c:4456] manager_radio_user_toggled(): (WiFi): setting radio disabled by user Now the WirelessEnabled key turned to false in /var/lib/NetworkManager.state file. Pressing the rfkill button again doesn't set WirelessEnabled to true again: NetworkManager[15750]: [1299427091.367610] [nm-udev-manager.c:477] handle_uevent(): UDEV event: action 'change' subsys 'rfkill' device 'rfkill2' NetworkManager[15750]: [1299427091.367902] [nm-udev-manager.c:204] recheck_killswitches(): WiFi rfkill state now 'unblocked' NetworkManager[15750]: [1299427091.367988] [nm-manager.c:1854] manager_rfkill_update_one_type(): WiFi hw-enabled 1 sw-enabled 1 NetworkManager[15750]: WiFi now enabled by radio killswitch ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On Sat, 2011-03-05 at 15:07 +0200, Ozan Çağlayan wrote: > On 09.02.2011 19:50, Ozan Çağlayan wrote: > > > I think there are multiple issues in here. The one that I've mentioned > > in the original thread and you've commented about may be triggered by > > the bug that I've replied. > > > > So with NM 0.8.2 on my Toshiba Portege R700 (iwlagn, exposing only a > > soft rfkill which is correctly turning on/off on keypress), when I > > sw-kill the radio, this is correctly detected by NM. The "Enable > > Wireless" gets unchecked and WirelessEnabled=false is written to the > > state file. If WirelessEnabled=false gets written as a result of the rfkill, that's wrong and is a bug. Can you post some logs from this happening? Better yet, stop NM, run it with "--no-daemon --log-level=debug" and lets get some verbose output here if we can. Basically, WirelessEnabled should be the *user* preference, and should be independent of whatever happens with rfkill. But having either or both of rfkill or WirelessEnabled off causes wireless to be off. > > But when I unblock, NM detects this to some point (looking at the > > debugged outputs and the code) but doesn't update the state file and > > doesn't enable the wireless networking. So one should explicitly check > > the "enable wireless" every time after unblocking the rfkill. > > > > I think this should be fixed. I'd like to debug more but I'm really > > getting lost in the glib/gobject mechanisms and NM code which contains a > > lot of abstraction/callback stuff really hard to follow :( > > > > > > Ping? Any idea before 0.8.4 gets released? Need a bit more debug here; the --log-level=debug logs would be useful for starters. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On 09.02.2011 19:50, Ozan Çağlayan wrote: > I think there are multiple issues in here. The one that I've mentioned > in the original thread and you've commented about may be triggered by > the bug that I've replied. > > So with NM 0.8.2 on my Toshiba Portege R700 (iwlagn, exposing only a > soft rfkill which is correctly turning on/off on keypress), when I > sw-kill the radio, this is correctly detected by NM. The "Enable > Wireless" gets unchecked and WirelessEnabled=false is written to the > state file. > > But when I unblock, NM detects this to some point (looking at the > debugged outputs and the code) but doesn't update the state file and > doesn't enable the wireless networking. So one should explicitly check > the "enable wireless" every time after unblocking the rfkill. > > I think this should be fixed. I'd like to debug more but I'm really > getting lost in the glib/gobject mechanisms and NM code which contains a > lot of abstraction/callback stuff really hard to follow :( > > Ping? Any idea before 0.8.4 gets released? -- Pardus Linux http://www.pardus.org.tr/eng ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On 09.02.2011 18:40, Dan Williams wrote: In current NM 0.8.x git, if you uncheck "Enable Wireless" from the menu, NM writes that to the state file. That will then be in-force until you re-check "Enable Wireless", even across reboots. This takes precedence over rfkill because it was an explicit user choice to disable wifi. This fix was included in NM 0.8.2. I don't think we should be relying on rfkill here, because then it's simply magic what happens on reboot. Some laptops expose multiple rfkill "switches" in the kernel, others expose one, some chain them together, etc. It's a big mess really, and trying to rely on the kernel behavior here isn't going to help much. Instead, I think it's a lot clearer that "If you turn off wifi it stays disabled til you turn it back on". Or? I think there are multiple issues in here. The one that I've mentioned in the original thread and you've commented about may be triggered by the bug that I've replied. So with NM 0.8.2 on my Toshiba Portege R700 (iwlagn, exposing only a soft rfkill which is correctly turning on/off on keypress), when I sw-kill the radio, this is correctly detected by NM. The "Enable Wireless" gets unchecked and WirelessEnabled=false is written to the state file. But when I unblock, NM detects this to some point (looking at the debugged outputs and the code) but doesn't update the state file and doesn't enable the wireless networking. So one should explicitly check the "enable wireless" every time after unblocking the rfkill. I think this should be fixed. I'd like to debug more but I'm really getting lost in the glib/gobject mechanisms and NM code which contains a lot of abstraction/callback stuff really hard to follow :( -- Pardus Linux http://www.pardus.org.tr/eng ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On Thu, 2011-02-03 at 13:00 +0200, Ozan Çağlayan wrote: > Hi, > > I have bug reports about some inconsistencies caused by the state file and > rfkill > interactions like when the user kills the radio and then re-enables it, the > WLAN can't be enabled > unless the state file is edited manually as root, etc. > > I think that when the system is booted, NM should ignore the state values in > the state file and > should rely only on the rfkill status. When the user disables the WLAN > through nm-applet or another > GUI, NM can internally remember this without needing that state file. > > Can someone explain how the logic currently works? In current NM 0.8.x git, if you uncheck "Enable Wireless" from the menu, NM writes that to the state file. That will then be in-force until you re-check "Enable Wireless", even across reboots. This takes precedence over rfkill because it was an explicit user choice to disable wifi. This fix was included in NM 0.8.2. I don't think we should be relying on rfkill here, because then it's simply magic what happens on reboot. Some laptops expose multiple rfkill "switches" in the kernel, others expose one, some chain them together, etc. It's a big mess really, and trying to rely on the kernel behavior here isn't going to help much. Instead, I think it's a lot clearer that "If you turn off wifi it stays disabled til you turn it back on". Or? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
2011/2/7 Ozan Çağlayan > On 03.02.2011 13:00, Ozan Çağlayan wrote: > >> Hi, >> > > And there's also another bug that I can reproduce: > > 1. Connect using WiFi > 2. Soft block WiFi (result: sw_enabled=0, hw_enabled=1) > 3. state file is updated to WirelessEnabled=false > 4. Unblock wifi (result: sw_enabled=1, hw_enabled=1) > 5. state file is not updated and stays the same > 6. WiFi doesn't come up automatically unless the "Enable wireless > networking" is clicked in the UI. > I confirm that this happens here, too. NM 0.8.1+git.20101009t040337.01fa170-0ubuntu1~nmt1~lucid1 Kubuntu 10.04, NM from ppa/Launchpad. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: WLAN disabled by state file
On 03.02.2011 13:00, Ozan Çağlayan wrote: Hi, And there's also another bug that I can reproduce: 1. Connect using WiFi 2. Soft block WiFi (result: sw_enabled=0, hw_enabled=1) 3. state file is updated to WirelessEnabled=false 4. Unblock wifi (result: sw_enabled=1, hw_enabled=1) 5. state file is not updated and stays the same 6. WiFi doesn't come up automatically unless the "Enable wireless networking" is clicked in the UI. -- Pardus Linux http://www.pardus.org.tr/eng ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
