Network Manager cannot be configured
Hi,
I'm having some trouble with the Network Manager. I installed networkmanager, networkmanager-vpnc and kdeplasma-applets-networkmanagement from the non-testing repoa and after a restart networking worked fine and I added the applet to the tray with no error.
But then I wanted to configure the Network Manager. First of all the second page at the Network Manager settings (it's called "Sonstiges" in german) shows me this error message (translated to english):
Library /usr/lib/kde4/kcm_networkmanagement_tray.so cannot be loaded: (/usr/lib/kde4/kcm_networkmanagement_tray.so: undefined symbol: _ZN27KNetworkManagerServicePrefs4selfEv)
However, the file /usr/lib/kde4/kcm_networkmanagement_tray.so exists in the filesystem.
When I try to add a VPNC connection it doesn't show all VPNC settings like it did on my fresh installed Kubuntu but the generic IPv4/IPv6 tabs. After that I clicked "OK" and got an error windows with the message "service-type" in it.
Did someone has a similar problem? Thanks in advance!
pacman -Q kdeplasma-applets-networkmanagement networkmanager
be sure you are fully up to date, inclusive glibc,gcc-libs
Last edited by wonder (2011-11-05 16:55:40)
Similar Messages
-
[SOLVED] Network Manager cannot connect to wifi after suspend
Hi,
There appears to be similar threads recently, but they relate to no wifi at all. I did some updates today, and now if I suspend or hibernate, network manager cannot reconnect to my wifi. It will (after a while) ask me to authenticate, but still fails. Nothing works except a reboot where it connects without issue.
It was fine yesterday, has only started today. Here is my pacman log for today's updates:
[2012-04-11 17:13] upgraded libpciaccess (0.13-1 -> 0.13.1-1)
[2012-04-11 17:13] upgraded lib32-libpciaccess (0.13-1 -> 0.13.1-1)
[2012-04-11 17:13] upgraded mpd (0.16.7-3 -> 0.16.8-2)
[2012-04-11 17:13] upgraded xorg-server-common (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server-devel (1.12.0.901-1 -> 1.12.0.902-1)
[2012-04-11 17:13] upgraded xorg-server-xephyr (1.12.0.901-1 -> 1.12.0.902-1)
Here is my messages log:
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Auto-activating connection 'Padfoot'.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) starting connection 'Padfoot'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0/wireless): connection 'Padfoot' has security, and secrets exist. No new secrets needed.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'ssid' value 'Padfoot'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'scan_ssid' value '1'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: added 'psk' value '<omitted>'
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> Config: set interface ap_scan to 1
Apr 11 18:38:28 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 11 18:38:29 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): association took too long.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0/wireless): asking for new secrets
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Couldn't disconnect supplicant interface: This interface is not connected.
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> No agents were available for this request.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed for access point (Padfoot)
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> Marking connection 'Padfoot' invalid.
Apr 11 18:38:53 localhost NetworkManager[1475]: <warn> Activation (wlan0) failed.
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 11 18:38:53 localhost NetworkManager[1475]: <info> (wlan0): deactivating device (reason 'none') [0]
Last edited by Padfoot (2012-04-13 23:47:55)heiko wrote:linux-3.3.2 is released on www.kernel.org and reverts the patch that introduced this problem.
For those using the arch repo kernel the next release will solve this issue. So I suggest waiting for this (no more than a few days) and use the LTS kernel in the meantime (or using a fixed ath9k module if already built).
Thanks for that heiko. I thought that would be the case, hence I just waited.
Will mark this as solved.
Cheers. -
[SOLVED]Network Manager dispatcher unexpected unmounting davfs folders
I have used Network Manager dispatcher to configure automatic mount of cloud storage using webdav. i have used davfs2 to perform mounting and wrote a script for NM dispatcher.
If i run /etc/NetworkManager/dispatcher.d/10-YandexDisk.sh manualy all works perfect.
If this script will be executed by NM-dispatcher all will fine(YandexDisk mounts successfully, sycronization - successfully), but after ~10 seconds mount.davfs gets signal 15.
sudo systemctl status NetworkManager-dispatcher
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
Active: inactive (dead) since Wed 2013-07-31 23:12:55 EEST; 11s ago
Process: 12132 ExecStart=/usr/lib/networkmanager/nm-dispatcher.action (code=exited, status=0/SUCCESS)
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: --- yandex.ru ping statistics ---
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: rtt min/avg/max/mdev = 36.570/37.776/38.983/1.222 ms
Jul 31 23:12:44 DellLaptop mount.davfs[12138]: davfs2 1.4.7
Jul 31 23:12:44 DellLaptop mount.davfs[12138]: mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=users,_netdev,rw,uid=lexa https://webdav.yandex.ru/ /home/lexa/.../YandexDisk
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >mounted https://webdav.yandex.ru/ to /home/lexa/Data/YandexDisk
Jul 31 23:12:44 DellLaptop nm-dispatcher.action[12132]: >exiting!!
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: pid 12140, got signal 15
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting /home/lexa/Data/YandexDisk
Jul 31 23:12:55 DellLaptop mount.davfs[12140]: unmounting failed
Why does this happen? Who send this signal ?
/etc/NetworkManager/dispatcher.d/10-YandexDisk.sh
#!/bin/bash
#this script will mount WebDav folder
# by pirat9600q
#given arguments are
#$1 is interface name
#$2 is state "up" or "down"
eth="enp7s0" #ethernet interface
wlan="wlp8s0" #wireless interface
ignore_connections="Pirat9600q" #WiFi SSIDs that must be ignored
mount_dir="/home/lexa/Data/YandexDisk" #mount point directory
remote_server="https://webdav.yandex.ru/" #server address
#local acces options
local_user="lexa" #files owner user
local_group="users" #files owner group
echo "<<<started with '$1' and '$2' arguments>>>"
echo "> our mount dir is '$mount_dir'"
echo "> and remote server is '$remote_server'"
case "$2" in
up)
#first of all we need to check internet connection
if (ping -c 2 -q yandex.ru); then
#we are online
if [ "$1" = "$wlan" ]; then
#Does this network is ignored ?
SSID=$(iwgetid -r)
for x in $ignore_connections; do
if [ "$x" = "$SSID" ]; then
echo "> WiFi SSID '$SSID' is in ignore list, exiting"
exit
fi
done
fi
if [ ! -d "$mount_dir" ]; then
fusermount -u "$mount_dir"
fi
if(mount.davfs -o auto,nodev,dir_mode=755,exec,file_mode=755,gid=$local_group,_netdev,rw,uid=$local_user "$remote_server" "$mount_dir"); then
echo ">mounted $remote_server to $mount_dir"
echo ">invoking syncronization script"
/home/lexa/.scripts/SyncYandexDisk.sh
else
echo ">error mounting $remote_server to $mount_dir !!!"
fi
else
echo ">network down";
exit
fi;;
down)
echo ">unmounting '$mount_dir'"
fusermount -u "$mount_dir"
echo ">removing $mount_dir"
rmdir $mount_dir
echo ">finished";;
esac
echo ">exiting!!"
exit
/home/lexa/.scripts/SyncYandexDisk.sh
#!/bin/bash
#this script will synchronize local storage
#with mounted Yandex Disk folder
# by pirat9600q
source_dir="/home/lexa/Data/YandexDisk/" #mount point directory
dest_dir="/home/lexa/Data/ARC/CloudSync/" #local storage location
echo "<<<started with:"
echo " source folder '$source_dir'"
echo " and destination folder '$dest_dir'"
if [ ! -L ${source_dir}Foto ]; then #if not link
echo ">invoking syncronization from '$source_dir' to '$dest_dir'"
echo ">syncronizing 'Foto' folder"
if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Foto/ ${dest_dir}Foto/); then
echo ">>error"
else
echo ">>success"
fi
echo ">syncronizing 'Documents' folder"
if !(rsync --quiet --recursive --update --executability --owner --group --delete-before ${source_dir}Documents/ ${dest_dir}Documents/); then
echo ">>error"
else
echo ">>success"
fi
else
echo ">syncronization will not be made, because source is fake"
fi
echo ">exiting"
exit 0
P.S. sorry for my English
Last edited by pirat9600q (2013-08-02 08:14:44)I solved the problem. Here is a little explanation.
After NetworkManager establishes network connection, NetworkManager-dispatcher service is started( for ~10 seconds). This service execute /usr/lib/networkmanager/nm-dispatcher.action, which execute scripts in /etc/NetworkManager/dispatcher.d. After exiting nm-dispatcher.action mount.davfs process appears in NetworkManager-dispatcher`s CGroup. By default all processes in CGroup must be killed when service stops. To change this behavior I have added KillMode=process to [Service] section of NetworkManager-dispatcher.service file.
sudo nano /usr/lib/systemd/system/NetworkManager-dispatcher.service
Here is it`s code now.
[Unit]
Description=Network Manager Script Dispatcher Service
[Service]
Type=dbus
BusName=org.freedesktop.nm_dispatcher
ExecStart=/usr/lib/networkmanager/nm-dispatcher.action
KillMode=process
[Install]
WantedBy=multi-user.target
Alias=dbus-org.freedesktop.nm-dispatcher.service -
I'm having trouble connecting to a VPN through network manager on KDE. I think my biggest problem is understanding the structure of Network Manager, can anyone help me out.
I have Network Manager running and configuring my wireless client perfectly through networkmanager-plasmoid.
I would like to setup a vpn through pptp. I tried to set this up through the plasmiod but it doesn't really do anything. I understand this is still alpha, so it may just not work.
I have installed networkmanager-pptp through aur. But what is this doing? It seems like in gnome this has a gui. Is this purely a gui or a backend as well.
Should I be manually setting up a vpn with pptp? It seems like the point of networkmanager is to configure this for me (or is network manager only going to start this and tell me when it is running).
Thanks for any help.Currently, the plasmoid is in heavy development, so I recommend to remove it with pacman -R, and use the gnome networkmanager frontend. Use the connection editor, enter the gateway, username, password, domain, use the special button to choose the authentication method (pap, chap, mschap, mschapv2, choose only one, if the login fails, try another). On the ipv4 tab, use the routing button, and enter the routing info, e.g. 192.168.1.0, 255.255.255.0, and disable automatic routing.
Hope that helps. -
How to connect old aiport express to my new Airport Extreme?
I have a PC running with Win7 and just replaced my Jensen With a brand New Airport Extreme.
I have set up the Airport Extreme to the internet, Iphones and Ipads and it work as it should.
I have downloaded latest Version of Airport tool on my PC. In addition i have downloaded the airport tool for Ipad.
I have reset one of my airport Express and it now shows up both on the Ipad and on the PC airport tool.
My Ipad says "base station e5713b cannot be configured."
I have wired the airport Express to my Ethernet to be able to "see it" on my Airport tool.
My AirPort tool on the PC will not permit me to add the airport Express to my new Airport Extreme network (no network names on the drop-down list to choose from). I wished for an easy set-up, but nothing seems to be plug and play as the Commercial says.. can you please help me?
SigveHi
Thanks for Swift reply.
Yep - I in fact have two A1088 and one A1264
I actually bought the new router because the Jensen
router always lost connection to the Airport Express after some hours or days. I
always needed to restart my Jensen to play music and that was driving my wife
mad. The hope was that the Extreme should fix this. Both A1088 have been set up
to only stream music to two of my stereo amplifiers from my PC’s Itunes library.
Are the A1088 now useless?
The A1264 has been set up to feed internet into a Denon Reciever that needed Ethernet cable.
Please advise
Regards
Sigve -
Network Manager Applet Cannot Edit Options/Connections As Normal User
Today I installed Network Manager, and Network Manager Applet in XFCE as a normal user. I followed the instructions on the Arch Network Manager Wiki to the best of my knowlage. The NM-Applet connects to my ethernet, and everything is fine. Untill that is, when I right click the NM Applet.
Once right clicked as a normal user, 'Enable Networking', and 'Enable Wireless' are greyed out and unselectable. Also, when I right click the applet and select 'Edit Connections' 90% of the clickable options are greyed out, including the options to 'Edit' or 'Delete' connections. The only clickable option not greyed out is 'Add' button.
Clicking Add brings up the 'Add New Connection Window', but again everything is greyed out. 'Available To All Users' is checked, but is greyed out also. But, starting XFCE as root, allows me to use the NM Applet with no restrictions, AKA none of the greyed out options. Everything works fine.This is my second day using Arch, so I am not sure where to go now.
It also may be of help ito say I haven't gotten a display manager, such as lightdm or gdm.
My guess is that root is listed under a group the 'jesse' isn't. Or maybe it has something to do with PolicyKit. I'm not sure. If someone could give me a set of clear instructions on how to fix this annoyance, it would be greatly appreciated. Thank You.
My Current Normal User Groups wrote: disk lp wheel uucp games network video audio optical storage scanner power users
My /etc/hosts file wrote:
# /etc/hosts: static lookup table for host names
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost jesse
::1 localhost.localdomain localhost jesse
# End of file
My /etc/rc.conf wrote:
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(alsa dbus syslog-ng crond ifplugd networkmanager bluetooth avahi-daemon acahi-dnsconfd avahi-dnsconfd fa$
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=eth0
# address=
# netmask=
# gateway=
My /etc/polkit-1/localauthority/50-local.d/org.freedesktop.NetworkManager.pkla wrote:Identity=unix-group:network
Action=org.freedesktop.NetworkManager.*
ResultAny=yes
ResultInactive=no
ResultActive=yes
Last edited by TriforceLZG (2012-09-02 13:43:23)I found the solution, I had to install a Display Manager. Now everything is fine.
-
"Configuration Manager cannot connect to the site" after site update from SP1 to R2
Our dev SCCM environment only has a single primary site with a remote SQL database. Initially, the dev primary site had SP1 Beta (5.00.7782.1000) installed but as everyone is aware there is no upgrade path available to SP1 or R2 from Beta; so, we uninstalled
the site and removed the database, re-installed SP1 non-Beta (5.00.7804.1000), then proceeded to update all devices with the latest client agent. Afterwards, we attempted to upgrade the site from SP1 non-Beta (5.00.7804.1000) to R2 (5.00.7958.1000).
All seemed well until we attempt to open the Configuration Manager console and we get the following error message:
Configuration Manager cannot connect to the site (Site Name)
The Configuration Manager Administrator console could not connect to the Configuration Manager site database. Verify the version of the console is compatible with the version of the site server you are connecting to and then try to connect again.
So we tried reinstalling the console directly from here...
"C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\AdminConsole.msi"
still the same error message persisted, so we tried installing it from here...
"C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\ConsoleSetup.exe"
still the same error message persisted, so then we tried installing it directly from the R2 (5.00.7958.1000) installation media, and afterwards the same error message persisted....
All along, we were checking the AdminConsole log from here:
"C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\AdminUILog\SmsAdminUI.log"
Here are the contents:
[4, PID:4836][04/22/2014 15:21:10] :Property: 'Features'\r\nSystem.Management.ManagementException\r\nNot found \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.PropertyData.RefreshPropertyInfo()
at System.Management.PropertyDataCollection.get_Item(String propertyName)
at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObjectBase.get_Item(String name)\r\nManagementException details:
[4, PID:4836][04/22/2014 15:21:10] :ReadExtraProperties: Failed to initialize extra properties
[4, PID:4836][04/22/2014 15:21:11] :Transport error; failed to connect, message: 'The Configuration Manager Administrator console could not connect to the Configuration Manager site database. Verify the version of the console is compatible with the version
of the site server you are connecting to and then try to connect again.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.SmsConnectionWithDetailException\r\nThe Configuration Manager Administrator console could not connect to the Configuration Manager
site database. Verify the version of the console is compatible with the version of the site server you are connecting to and then try to connect again.\r\n at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.ValidateConnectionParameters(ConnectionManagerBase
connection)
at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nNo details are available for this error.\r\n
Once again, we validated we could connect to the SQL database from this box, and that the console was at the same version as the site. Any help or guidance with getting our access to the console restored after the SP1 to R2 upgrade would be greatly
appreciated.From the Primary Site Server, I tried uninstalling the Admin Console and re-installing using:
consolesetup.exe /q TargetDir="%ProgramFiles%\Microsoft Configuration Manager" EnableSQM=0 DefaultSiteServerName=<SiteServerName>
Of course replacing <SiteServerName> with the FQDN of my Primary Site Server. Console installed successfully however the same error message persists.
Also tried installing the console on a clean Windows Server 2008 R2 installation. I tried it from the R2 (5.00.7958.1000) installation media, from the "C:\Program Files\Microsoft Configuration Manager\tools\ConsoleSetup\" both without any luck, the
same error message persists. I verified I could ping the FQDN of the site server also, and that the firewall between the two permits communication over the ports listed here: http://technet.microsoft.com/en-us/library/hh427328.aspx
Any help would be greatly appreciated. -
SQL Server Configuration Manager – Cannot connect to WMI provider – Invalid class [0x80041010]
look at this post am getting the same
http://social.msdn.microsoft.com/Forums/en-US/sqlkjmanageability/thread/4c8ca86c-105f-4f0a-ac18-6e33dda2bc46
but when I tried the solution given there , It is not working
the error I am getting is mofcomp is not recognized as internal or external command
I tried in C:\program files\Microsoft sql server\90\shared and in Windows\system32
I am getting the same errorHi sql393,
Cannot connect to WMI provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager. Invalid class [0x80041010].
The solution is to go to a command prompt and then run mofcomp.
C:\Program Files\Microsoft SQL Server\90\Shared>mofcomp "C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof"
For more information, please refer to
http://blogs.msdn.com/b/echarran/archive/2006/01/03/509061.aspx
http://msmvps.com/blogs/martinpoon/archive/2009/11/27/sql-server-configuration-manager-cannot-connect-to-wmi-provider-invalid-class-0x80041010.aspx.
Thanks,
Maggie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. This can be beneficial to other community members reading the thread. -
ISync Palm Conduit cannot be configured with the HotSync Manager UPDATE
First, I apologize for the SPAM-like posting of the material below in the existing threads regarding this issue. It is—unfortunately—the most effective way to garner the attention of earlier posters and gather this information.
Apple continues to investigate the issue, and needs this information to isolate and identify the problem. It is characterized by the apparently successful installation of the bundled iSync Palm Conduit using the Enable Palm OS Syncing… option in iSync 2.4 with either Mac OS X 10.4.9 or 10.4.10, but with the result that this conduit—normally visible in and configurable with the HotSync Manager—cannot be seen and therefore not configured.
In order to help Apple software engineers isolate and identify this issue—if you are affected by this specific issue—can you please provide the precise build number for the operating system on the machine that exhibit this problem?
To do so, select About This Mac from the Apple menu, and—beneath the Mac OS X label—press the Version 10.4.9 or Version 10.4.10 label. That value will change to something like 8P1xxx. Please respond to this message with that build number, the version of Mac OS X 10.4.x you have installed, and the last three digits of your machine serial number.
Thank you in advance for providing this information.First, I apologize for the SPAM-like posting of the material below in the existing threads regarding this issue. It is—unfortunately—the most effective way to garner the attention of earlier posters and gather this information.
Apple continues to investigate the issue, and needs this information to isolate and identify the problem. It is characterized by the apparently successful installation of the bundled iSync Palm Conduit using the Enable Palm OS Syncing… option in iSync 2.4 with either Mac OS X 10.4.9 or 10.4.10, but with the result that this conduit—normally visible in and configurable with the HotSync Manager—cannot be seen and therefore not configured.
In order to help Apple software engineers isolate and identify this issue—if you are affected by this specific issue—can you please provide the precise build number for the operating system on the machine that exhibit this problem?
To do so, select About This Mac from the Apple menu, and—beneath the Mac OS X label—press the Version 10.4.9 or Version 10.4.10 label. That value will change to something like 8P1xxx. Please respond to this message with that build number, the version of Mac OS X 10.4.x you have installed, and the last three digits of your machine serial number.
Thank you in advance for providing this information. -
How Can I configure network manager correctly?
Well, in debian, when I started the gnome session, immediately I was asked for a password to connect my default wireless connection. It is the correct way I want.
In arch, the process is: First, the network manager connects to localhost (I don't know why...), and I have to select manually my wireless net to connect to it, and put my password.
Is there anyway to make this process as it was in debian? So, when I start gnome session, be asked for password and connect immediately.
My rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="es_ES.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Europe/Madrid"
KEYMAP="es"
CONSOLEFONT="lat1-16"
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
MODULES=(ipw3945 8139too mii cpufreq_powersave cpufreq_userspace
freq_table acpi_cpufreq asus_acpi sn9c102)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
HOSTNAME="samantha"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="dhcp"
eth2="dhcp"
INTERFACES=(lo !eth0 !eth2)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.1.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles
#NET_PROFILES=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng crond hal hwd cpudyn @alsa xinetd vmware ipw3945d
laptop-mode dhcdbd networkmanager !network netfs gdm)
# End of file
GreetingsIf i'm not misstaken, this is a bug in the latest version of NetworkManager (0.64).
-
I cannot connect to internet im getting the error message: no network adapter installed or configure
i cannot connect to internet im getting the error message: no network adapter installed or configured. what can i do?
Sherya, welcome to the forum.
When requesting help, you should always include the make/model of the computer and/or monitor. This information is necessary for us to review the specifications of them.
I believe that this is a problem for your ISP. Their Customer Service should be able to help you. There may be some settings that can be changed to solve the problem. They would know what the settings should be. I don't believe that it is a hardware problem.
Please click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee. -
Network Manager - IP Configure Commit (stage 5) hangs
I am having the following issue when using network manager: sometimes it works, but sometimes the notification icon sits there spinning as if it's still attempting to connect to the wireless network.
/var/log/message.log says the following
Oct 19 22:47:39 localhost NetworkManager[693]: <warn> the dhcpcd backend does not support IPv6.
Oct 19 22:47:39 localhost dhcpcd[2700]: wlan0: acknowledged 192.168.1.117 from 192.168.1.1
Oct 19 22:47:39 localhost dhcpcd[2700]: wlan0: checking for 192.168.1.117
Oct 19 22:47:44 localhost dhcpcd[2700]: wlan0: leased 192.168.1.117 for 86400 seconds
Oct 19 22:47:44 localhost NetworkManager[693]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Oct 19 22:47:44 localhost NetworkManager[693]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Oct 19 22:47:44 localhost NetworkManager[693]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Oct 19 22:47:44 localhost NetworkManager[693]: <info> address 192.168.1.117
Oct 19 22:47:44 localhost NetworkManager[693]: <info> prefix 24 (255.255.255.0)
Oct 19 22:47:44 localhost NetworkManager[693]: <info> gateway 192.168.1.1
Oct 19 22:47:44 localhost NetworkManager[693]: <info> nameserver '68.87.64.150'
Oct 19 22:47:44 localhost NetworkManager[693]: <info> nameserver '68.87.75.198'
Oct 19 22:47:44 localhost NetworkManager[693]: <info> nameserver '192.168.1.1'
Oct 19 22:47:44 localhost NetworkManager[693]: <info> domain name 'hsd1.de.comcast.net.'
Oct 19 22:47:44 localhost NetworkManager[693]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
TOct 19 22:54:34 localhost -- MARK --
However, sometimes it works flawlessly. I am on an Asus EEEPC using the ath9k driver. Here is the lspcpi output for the wireless card.
02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
Subsystem: AzureWave Device 1089
Kernel driver in use: ath9k
Kernel modules: ath9k
Is there another log file I can look at to get more info? Has anyone seen this happening with the ath9k driver?It seems Gnome 3 is in a slightly random state at the moment. While I don't have issues with my wi-fi, other things seem to work and then fail at random boots and other times.
One thing you might try with nm-applet to get wi-fi to connect automatically is change the following lines in /etc/rc.conf:
Change:
eth0="dhcp"
INTERFACES=(eth0)
to:
wlan0="dhcp"
INTERFACES=(wlan0)
Cheers. -
Network-manager-applet cannot run!!!!!!!!!!
Installed networkmanager and network-manager-applet, but I found it could not startup at boot time.....
When I run nm-applet in terminal as normal user, it print:
[yin@q ~]$ nm-applet
** (nm-applet:2168): WARNING **: <WARN> request_name(): Could not acquire the NetworkManagerUserSettings service.
Error: (9) Connection ":1.39" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file
When I run "sudo nm-applet", noting was wrong ,and the icon appeared in the panel right top.
Another question:
What's the difference between daemons in rc.conf and startup applications in gnome ?
I add "networknamager" in daemons line in rc.conf ,but I found there is a network manager entry in startup applications in gnome with the command : nm-applet --sm-disable. Does they conflict ??
Last edited by iamybj (2010-03-27 12:52:56)iamybj wrote:
ngoonee wrote:You did not search the forums. Please do so before asking a question.
I think if the question was resolved, it should be updated to the wiki....
I find the wiki updating is very slow right now.
You misunderstand how this community works.
Users update the wiki, voluntarily. If you find a solution and feel its a common enough problem to post on the wiki, please do so.
Also, if you can't even bother to do a forum search or google search before asking questions, this may not be the right distro for you. Please read http://wiki.archlinux.org/index.php/FAQ … se_Arch.3F, especially the 'do-it-yourself' part. -
No interfaces shown in network manager [SOLVED]
Hi All,
I have just done a fresh install of Arch on my new Sony Vaio VGN-FW53GF, all goes well, except for Network Manager.
I can use my wired connection ok as eth0 shows up as active when I hover over the kde applet in the task bar. However when I go to "Manage Connections"
I do not see any Wireless networks or even my "working" wired connection in any list.
Wireless seems to be working as iwconfig shows an interface.
wlan0 IEEE 802.11abgn ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
But a scan gives this:
iwlist wlan0 scan
wlan0 Interface doesn't support scanning : Network is down
This machine is using the Intel driver "iwlagn" supplied by the kernel (2.6.31).
My /etc/rc.conf is:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Pacific/Auckland"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="Laptop2"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng !network hal networkmanager netfs crond)
Can anyone offer some suggestion on how to get network manager going, I would like to use it. In the past
I have used Wicd, but it has some limitations.
Cheers,
Bernie
Last edited by bmentink (2009-12-24 04:19:49)bmentink wrote:
Ok, I found the issue. I was missing the firmware for the card. I downloaded firmware from the intel site as per the wiki on wireless and
my interface comes up (shown with ifconfig) and I can see all the networks.
However, I cannot seem to connect to my network with WPA. When I go to connect I get network manager thinking the access point is WEP and asking for pass phrase.
If I select WPA(personal) and fill in a password, nothing happens .... just says unavailable.
Can anyone give some idea's here. I have not used network manager before for WPA.
Cheers,
Bernie
I use WPA2 with network manager without a problem. It should "just work", im not sure why you have issues, can you switch your router to a different security protocol to test? -
Network Manager fails to connect with Huawei E3276 modem after upgrade
Hi,
I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
Error: failed to connect modem: Only IPv4 is supported by this modem.
I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
I would be grateful for any advice.
After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
Before upgrade (KDE 4.14)
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
Linux Mint 17.1 KDE (works the same like Arch before update)
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
Last edited by Shocker (2015-05-07 19:18:43)This week, after update, modem works again.
However, there's a new bug in the kernel, which was not there before:
kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
but the modem works and connects to the network.
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.
Maybe you are looking for
-
How do I get past the password prompt with a locked iPhone?
I updated to iOS7, and everything seemed fine. But then when the phone locked after a few minutes, it asked me for a password to unlock. I never used a password before. So the phone is asking me for something I didn't have to do before. Now the phon
-
I've been eyeballing iTunes 12 and not enjoying it. I didn't much like the original upgrade to iTunes 11, but at least I kept my beloved Internet radio station playlists. After upgrading iTunes to the latest version, not only is the interface once ag
-
No ringtone with FaceTime and no alert sound??
I have not been able to get a ringtone with FaceTime nor can I get an alert signal. Mute is off and volume control works.HELP
-
What exactly is going on with the creative products, it is like an epidemic Admins come and l
Ok, I got a vision m for christmas and everything worked fine. I stopped using it for?a couple of months and then my mom got a v plus. I wasn't getting the connection error with the MTP device stuff. Now I plug in my vision m and I am getting the sam
-
Need Help - Installation failing at: Phase 25 Intsall instance basics
Hello everyone, We are trying to install solution manager 4 on linux readhat E4 (oracle db). Currently, we are stuck at phase 25 "install instance basics. I can see at the bottom of the screen, the message says the phase is "Creating instance dire