Thanks James,
I have seen that this comes from the vboxnet interface, where dhcpd and
nwam has issues with. VirtualBox 2.2.2, which has been released recently
fixed this.
Detlef
On 04/28/09 20:05, James Carlson wrote:
Detlef drew...@sun.com writes:
3. Also: After the boot I see dhcpagent/1
I am still seeing issues with VirtualBox 2.2.2 and nwam.
I reverted to doing the following:
1) add e1000g0 static x.x.x.x/24 to /etc/nwam/llp
2) add x.x.x.1 to /etc/defaultrouter
3) cp /etc/nsswitch.dns /etc/nsswitch.conf
4) add name server ip tpo /etc/resolv.conf
pfexec restart nwam
pfexec
Paul Griffith writes:
I am still seeing issues with VirtualBox 2.2.2 and nwam.
If you're seeing the 'dhcpagent' process spinning and consuming CPU
time, then it's very likely to be the same CR that I cited. The fix
for that problem was just integrated yesterday.
Running OS 2008.11, waiting
Detlef drew...@sun.com writes:
3. Also: After the boot I see dhcpagent/1 consuming 50 % CPU (looks like
1 core) and the nwam applet will not show up in the gnome panel. I first
have to kill -9 the dhcpagent, then the nwam applet comes up and the
cpu consuming goes away.
This part sounds
Hi,
with b111a now I can boot again my Toshiba M9.
1.I discoverred that Power Management seems no longer to work.
(The fan is blowing like hell and kstat -m cpu_info shows in
currentClock_Hz 200100
but
supported_frequencies_Hz
8:12:16:20:200100
New Bug
Detlef drew...@sun.com wrote:
Hi,
with b111a now I can boot again my Toshiba M9.
1.I discoverred that Power Management seems no longer to work.
(The fan is blowing like hell and kstat -m cpu_info shows in
currentClock_Hz 200100
but
supported_frequencies_Hz
1.I discoverred that Power Management seems no longer to work.
(The fan is blowing like hell and kstat -m cpu_info shows in
currentClock_Hz 200100
but
supported_frequencies_Hz
8:12:16:20:200100
New Bug with b111a ?
Try to use powertop to check if
