No network connection or virtualbox guest additions after upgrade

I followed the instructions carefully, from the homepage, when carrying out the latest upgrade. Unfortunately, virtualbox guest additions is no longer working and nor can I get a network connection. To clarify, arch is running inside a virtual machine.
I'm not sure where to start looking to be honest and would appreciate some pointers about to get me on the way towards solving this problem.
EDIT: The virtualbox problem is related to error in the package
Thanks
Last edited by n_t (2013-06-11 19:01:52)

for the guest additions, it's a bug in the package, look here: https://bbs.archlinux.org/viewtopic.php?id=164924
For the network, you'll have to tell us how you were setting up the network before that isn't working now.

Similar Messages

[solved] Virtualbox guest additions stopped working

Hi,
I got some trouble after an upgrade of kernel yesterday. Virtualbox guest additions doesn't work any longer, and I have tried both downgrading virtualbox-guest-additions and the new linux that got pushed yesterday, but it's still not working.
Is there some know issue related to this?
Do anyone have information on how to trace errors with Virtualbox, or any guide on how to fix this.
I have also tried a reinstall of the modules without success.
Thanks.
Last edited by grrrm (2014-10-08 15:45:45)

Suddenly it worked

Error installing VirtualBox Guest Additions

Hello. ¿Cuál es el motivo por el cual a la hora de instalar VirtualBox Guest Additions me sale lo siguiente?
(1) 0 - ENTER: DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vboxguest.inf_amd64_neutral_08c563e3b006bb64\vboxguest.inf" on the Machine.
(1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\Windows\System32\DriverStore\FileRepository\vboxguest.inf_amd64_neutral_08c563e3b006bb64\vboxguest.inf'.
(1) 0 - RETURN: DriverPackageInstallW (0xE000020B)
How I can solve this installation error?

2898527 wrote:
I was installing VirtualBox Guest Additions, and install gives me the following installation error:
(1) 0 - ENTER: DriverPackageInstallW
(1) 0 - Installing INF file 'C:\Program Files\Oracle\VirtualBox Guest Additions\VBoxGuest.inf' (Plug and Play).
(1) 0 - Looking for Model Section [VBoxGuest.NTamd64]...
(1) 0 - No matching devices found in INF "C:\Windows\System32\DriverStore\FileRepository\vboxguest.inf_amd64_neutral_08c563e3b006bb64\vboxguest.inf" on the Machine.
(1) 0 - No drivers installed. No devices found that match driver(s) contained in 'C:\Windows\System32\DriverStore\FileRepository\vboxguest.inf_amd64_neutral_08c563e3b006bb64\vboxguest.inf'.
(1) 0 - RETURN: DriverPackageInstallW (0xE000020B)
How is it possible that mistake, and how could I fix it?
Regards,
--Alejandro
You just repeated your original post with no additional information.
SPECIFICALLY, how were installing Guest Additions? What SPECIFIC steps did you take? Where, SPECIFICALLY, did you find the messages you posted?

Failed to install VirtualBox Guest Addition on Oracle Linux 6.1

I can successfully install Oracle Linux 6.1 on VirtualBox 4.1. But failed to install VirtualBox Guest Additions with the following message: Building the main Guest Additions module [FAILED]. All other modules installed ok.

Actually you don't have do install the developer version. According to the documentation http://www.virtualbox.org/manual/ch04.html you will need to install gcc and kernel-devel packages. In case Oracle Enterprise Linux does not find the required packages, you either have to install them from a different source (e.g. DVD) or use Oracle's public Yum server located at http://public-yum.oracle.com.

How can i install virtualbox-guest-additions?

pacman -S virtualbox-guest-additions
edit rc.conf
MODULES=(vboxguest vboxsf vboxvideo)
under gnome
glxgears 60.975fps
but under centos 5.6 gnome 559.203fps
how would i do to so fast?
Last edited by oddhornedant (2011-04-25 10:03:56)

This is the only entry I have in MODULES=(vboxdrv)
I use Vbox from AUR as they work for me.
I use win7/winxp fedora debian etc as guests with full access to usb/ shared drives etc.and full screen where possible as some distros do not do full screen in vbox without a lot of fiddling
are you in the correct groups with out the correct permissions they do not work usbmux:x:140:username
vboxusers:x:108:username

HT1551 my apple tv intermittently stops playing music while playing Songza. network connection is strong. i have upgraded to the latest appletv s/w

My apple tv intermittently stops playing music while playing Songza. network connection is strong. i have upgraded to the latest appletv s/w
what can i do to fix this?

Strangely enough, I exchanged the ATV2 and ATV3 and now both work fine. I suspect it may have something to do with the fact that (previously) the ATV3 (1080p) was behind an ethernet hub. Somehow the ATV2 (720p) does not mind being behind the hub. Either that or iTunes suddenly became smarter since the exchange . Anyway, it works now so I'm not touching it. Thanks for the suggestion.

Errors installing virtualbox guest additions from AUR

After failing to get ose guest additions working in an Arch guest on Ubuntu host by (a) mounting the ISO and (b) installing from pacman, I thought that it would be an idea to use builds from AUR as these would likely to be more customised for Arch guests.
Installing ose-guest-additions-modules (the dependency for ose-guest-additions) worked flawlessly, but whenever I try and makepkg -s for ose-guest-additions I get the following error:
install: cannot stat 'vboxadd-timesync' : no such file or directory
install: cannot stat 'VBoxClient' : no such file or directory
install: cannot stat 'mountvboxsf' : no such file or directory
These directories do exist at /usr/share/virtualbox/additions/ so I am at a loss as to what is causing this to fail.
(It is worth pointing out that I am new to Arch -and relatively new to Linux- & while I am having a lot of fun trying to figure this stuff out, I am aware that I am probably missing something quite obvious...)

bump
Last edited by Mufasaa (2015-06-12 13:04:45)

Virtualbox guest addition install issue on oel 64bit guest

Hi,
my configuration is
windows 7 home 64 bit -
virtualbox 4.1.8
I installed oel 64 bit guest
and now I am trying to install the guest addition . but while installing it failed
Building the main guest additon module FAILED
it says of a missing package kernel-devel-2.6.32-100.26.2.el5
so I did
yum install kernel-devel-2.6.32-100.26.2.el5
but now it complains
ULN support will be disabled
No package kernel-devel-2.6.32-100.26.2.el5 available
appreciate any suggestion
thanks
Kart
sharing 2 wonderful links
https://blogs.oracle.com/fatbloke/entry/virtualbox_and_the_unbreakable_enterprise
http://www.oracle.com/technetwork/articles/servers-storage-admin/vmlove-1368887.html
Edited by: user12046749 on Feb 21, 2012 6:27 AM

Thanks Avi..:) seems like i am progressing..
[root@localhost yum.repos.d]# cat /etc/oracle-release
Oracle Linux Server release 5.6
so now I enabled all the enabled in the repos file . after that I was able to
[root@localhost yum.repos.d]# yum install kernel-uek-devel-2.6.32-100.26.2.el5
Loaded plugins: rhnplugin, security
This system is not registered with ULN.
ULN support will be disabled.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package kernel-uek-devel.x86_64 0:2.6.32-100.26.2.el5 set to be updated
--> Finished Dependency Resolution
Dependencies Resolved
===============================================================================================================
Package Arch Version Repository Size
===============================================================================================================
Installing:
kernel-uek-devel x86_64 2.6.32-100.26.2.el5 ol5_u6_base 6.6 M
Transaction Summary
===============================================================================================================
Install 1 Package(s)
Upgrade 0 Package(s)
Total download size: 6.6 M
Is this ok [y/N]: y
Downloading Packages:
kernel-uek-devel-2.6.32-100.26.2.el5.x86_64.rpm | 6.6 MB 00:21
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : kernel-uek-devel 1/1
Installed:
kernel-uek-devel.x86_64 0:2.6.32-100.26.2.el5
Complete!
[root@localhost yum.repos.d]#
after that when i try to run guest addition it complains of gcc utility not found. Is there some other rpms that I need to install for guestaddition to run succesfully.
Please let me know... thank you for the wonderful tips
Kart.

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.

Network connection slow to become active after waking from sleep.

Using MBP (2007) with OS 10.8.2 I put my machine to sleep each night after work. Each morning when I wake it, the network connection takes over 90 seconds to become active. This is on a WIRED network. Didn't have this problem before Mountain Lion upgrade. Before ML the connection was nearly instant. Any clues?

I am seeing the same issue. I believe it started after upgrading to 10.8.2. (I did not notice such long network reconnections after wake with either 10.8.0 or 10.8.1.) I am also on a wired network. Same result using DHCP and fixed IP.
The network reconnection after wake used to be nearly instantaneous.

Installing virtualbox guest additions - No X-11

OK, so I took the plunge (again) and [re]started with Arch.
I have it right now as a virtualbox guest, but the screen is the size of a key hole.
I followed the steps on the wiki here and I encountered a curve ball when it came to setting the values in ~/.xinitrc.
The file is now there. I had to manually create it as I do not have (or want) any non-terminal applications on this VM.
However, when I run " ps ax | grep -i vbox ", the services VBoxClient --display | seamless | draganddrop are not running until I manually start VBoxClient-all. VBoxService -f is running, seemingly without any issues.
How can I fix this so that /usr/bin/VBoxClient-all (the same line now in the .xinitrc) would run at boot?
TIA

bump
Last edited by Mufasaa (2015-06-12 13:04:45)

VirtualBox Guest Addition install failed

Hello,
I just build a linux-guest virtual box and I am trying to install the guest addition and the first step is to run "/etc/init.d/vboxadd setup". I got the following error:
+"The heaers for the current running kernel were not found. If the following module compilation fails then this could be the reason. The missing package can be probably installed with+
+yum install kernel-devel-2.6.18-194.e15+
+You system does not seem to be set up to build kernel modules. Look at /var/log/vboxadd-install.log to find out what went wrong. Once you have corrected it, you can run /etc/init.d/vboxadd setup to build them."+
And the log file reads:
+"*** Error: unable to find the sources of your current linux kernel. Specify KERN_DIR=<directory> and run Make again.. Stop"+
I then tried "yum install dkms". This time no error but it says +"No package dkms available . Nothing to do".+ Also, my /usr/src/kernels directory is empty. I dont know if this is part of the reason.
Thanks for the help.
Harry

user11957149 wrote:
It says no package kernel-devel-2.6.18-194.e15 available. How can i install this package?I think that the 1 should be an 'l' - ie: kernel-devel-2.6.18-194.el5. Also, you should double-check your running kernel to make sure that corresponds to the version you are running.
Edited by: JaredGreenwald on May 4, 2011 10:26 PM

Network can't see my Mac after upgrading to Mountain Lion 10.8.2

After upgrading to ML 10.8.2 (coming from Lion), the network (another mac and an iPad) can't see my Macbook-pro.
Using a network scanner (Fing on iPad), my Macbook is not there, and in the same way all the other services from Macbook-pro (such as Internet sharing, Filemaker sharing, ...) don't work.
My Macbook-pro is regularly connected to the right network and has a proper IP address (192.168.1.32 with 192.168.1.1 being the router, ...33 the other mac and so on). Also, my Macbook-pro perfectly reaches both other LAN devices and the internet.
I've tried disabling Firewall but nothing changed. I havn't got any antivirus nor security programs running.
Anyone experiencing the same issue?

Please read this whole message before doing anything. This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it. The purpose of this test is to determine whether your problem is caused by third-party system modifications that load automatically at startup or login. Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
When you see the gray Apple logo, release the shift key.
If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
*Note: If FileVault is enabled under OS X 10.7 or later, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode. Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs. The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Can't connect to 10.6 Server after upgrade

I have a Mac Mini server running 10.6.8 using kerberos as the only authentication for AFP.
After upgrade my Macbook to Lion I can't connect to the server Sharing Points anymore. If I try to connect from Go to Server, it asks me for a password. I think I am not being authenticated via kerberos. Before Lion everything was working fine. Another computer running 10.6 client are connecting fine, so I am thinking the problem is with 10.7
I used Login Options > Network Account Services to bind to the Server. Green Light!
I tryed klist from terminal but no credential was found, so I used kinit username. Now it shows a credential but I still can't connect.

I solved use to finder menu connect server to and use complete name server with domain example:
afp://nameserver.domain.com and connected with kerberos

"network connection timed out"-can't update upgrade on ipod

Last year an ipod touch 8GB was given to me and I am just now updating everything. When I plug my ipod into my computer and open itunes, it prompts me to download and install 3.1.3 upgrade. So I hit "download and install" and right after it gets done downloading (takes 7 min), an error message pops up and says "network connection timed out"- could not install the upgrade, try again later. I have paid the 5 bucks for the upgrade and tried it about 10 times now with the same results everytime.
I have tried turning off my router and restarting that and also reset my network connections on the actual ipod itself with re-typing in my network name and password for the wifi. My wireless connection is strong and never goes out on me, as well as my ipod always recognizes it and connects automatically so I'm not sure why I keep getting this error message!
HELP!!! thx

I ran into the issue this week. said yes to upgrade, ipod was backed up, and then upgrade died. ipod touch itself indicated it was no longer aware. power down did not help, itunes could not restore to previous. Looking on apple site, I was getting a code 14 error. solution was to update itunes to 9.03, restart system and then retry the download. it worked after that, and the backup did restore all my info including kindle books etc.

No network connection or virtualbox guest additions after upgrade

Similar Messages

Maybe you are looking for