<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: PC-BSD 9.0 Users Handbook</title>
	<atom:link href="http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/</link>
	<description>Discover the Desktop</description>
	<lastBuildDate>Mon, 20 May 2013 21:14:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: dru</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-2527</link>
		<dc:creator>dru</dc:creator>
		<pubDate>Mon, 28 May 2012 11:31:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-2527</guid>
		<description><![CDATA[Is this still occurring for you?]]></description>
		<content:encoded><![CDATA[<p>Is this still occurring for you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Billy J Nunez</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-2526</link>
		<dc:creator>Billy J Nunez</dc:creator>
		<pubDate>Mon, 28 May 2012 03:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-2526</guid>
		<description><![CDATA[Unable to load page

Problem occurred while loading the URL ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.pdf

Links are down?!]]></description>
		<content:encoded><![CDATA[<p>Unable to load page</p>
<p>Problem occurred while loading the URL <a href="ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.pdf" rel="nofollow">ftp://ftp.pcbsd.org/pub/handbook/9.0/handbook_en_ver9.0.pdf</a></p>
<p>Links are down?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dru</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-2157</link>
		<dc:creator>dru</dc:creator>
		<pubDate>Mon, 26 Mar 2012 13:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-2157</guid>
		<description><![CDATA[Thanks for posting the link!]]></description>
		<content:encoded><![CDATA[<p>Thanks for posting the link!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-2149</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Fri, 23 Mar 2012 21:00:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-2149</guid>
		<description><![CDATA[Hey! I know this is an old post, but the other day I browsed around, still looking for a more &quot;professional&quot; solution to my ACPI problem, and I came across this website, where the probable cause of the problem is described: http://osdir.com/ml/freebsd-bugs/2011-09/msg00170.html. According to this site, &quot;The problem should occur on any system with a battery using the cmbat 
interface, which dispatches a large number of calls via AcpiOsExecute during 
initialization. This fills up the task queue, which results in the call to 
acpi_cmbat_init_battery getting dropped due to the queue being full, which 
results in the bif information not being properly initialized. Because the 
cmbat driver only reads this information at initalization, the driver will 
incorrectly report the battery as not being present.

Similar issues with other ACPI features may have a similar root cause.
&gt;Fix:
Setting debug.acpi.max_tasks to a high value (I used 128) is a stable 
workaround, and will restore functionality.&quot;]]></description>
		<content:encoded><![CDATA[<p>Hey! I know this is an old post, but the other day I browsed around, still looking for a more &#8220;professional&#8221; solution to my ACPI problem, and I came across this website, where the probable cause of the problem is described: <a href="http://osdir.com/ml/freebsd-bugs/2011-09/msg00170.html" rel="nofollow">http://osdir.com/ml/freebsd-bugs/2011-09/msg00170.html</a>. According to this site, &#8220;The problem should occur on any system with a battery using the cmbat<br />
interface, which dispatches a large number of calls via AcpiOsExecute during<br />
initialization. This fills up the task queue, which results in the call to<br />
acpi_cmbat_init_battery getting dropped due to the queue being full, which<br />
results in the bif information not being properly initialized. Because the<br />
cmbat driver only reads this information at initalization, the driver will<br />
incorrectly report the battery as not being present.</p>
<p>Similar issues with other ACPI features may have a similar root cause.<br />
&gt;Fix:<br />
Setting debug.acpi.max_tasks to a high value (I used 128) is a stable<br />
workaround, and will restore functionality.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dru</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-1922</link>
		<dc:creator>dru</dc:creator>
		<pubDate>Thu, 02 Feb 2012 17:18:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-1922</guid>
		<description><![CDATA[You&#039;re welcome. Let us know if it renders well in the Kobo.]]></description>
		<content:encoded><![CDATA[<p>You&#8217;re welcome. Let us know if it renders well in the Kobo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Zplay</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-1921</link>
		<dc:creator>Zplay</dc:creator>
		<pubDate>Thu, 02 Feb 2012 16:46:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-1921</guid>
		<description><![CDATA[Many thanks for publishing this handbook with an epub format ! So I can read the handbook on my Kobo ebook reader !]]></description>
		<content:encoded><![CDATA[<p>Many thanks for publishing this handbook with an epub format ! So I can read the handbook on my Kobo ebook reader !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dru</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-1909</link>
		<dc:creator>dru</dc:creator>
		<pubDate>Mon, 30 Jan 2012 13:56:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-1909</guid>
		<description><![CDATA[No, the correct location includes the pub directory.]]></description>
		<content:encoded><![CDATA[<p>No, the correct location includes the pub directory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mich</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-1898</link>
		<dc:creator>Mich</dc:creator>
		<pubDate>Sat, 28 Jan 2012 07:19:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-1898</guid>
		<description><![CDATA[There&#039;s an error in the link to the handbook page at the ftp server should be :
ftp://ftp.pcbsd.org/handbook/9.0/ 
instead of
ftp://ftp.pcbsd.org/pub/handbook/9.0/]]></description>
		<content:encoded><![CDATA[<p>There&#8217;s an error in the link to the handbook page at the ftp server should be :<br />
<a href="ftp://ftp.pcbsd.org/handbook/9.0/" rel="nofollow">ftp://ftp.pcbsd.org/handbook/9.0/</a><br />
instead of<br />
<a href="ftp://ftp.pcbsd.org/pub/handbook/9.0/" rel="nofollow">ftp://ftp.pcbsd.org/pub/handbook/9.0/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-1869</link>
		<dc:creator>Anders</dc:creator>
		<pubDate>Tue, 24 Jan 2012 17:03:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-1869</guid>
		<description><![CDATA[Yesterday, I opened up a forum post on the FreeBSD forums and described my problem there. A tip another user sent me was to add the following to /boot/loader.conf: &quot;debug.acpi.max_tasks=&quot;128&quot;. It worked to some extent; when I boot up PC-BSD on battery source, the system behaves the way it should, it displays the time until empty, XX% remaining, etc. However, if I connect a power source, the system does not necessarily notice it, so the battery icon, as well as acpiconf -i 0 says &quot;discharging&quot; (with the &quot;Remaining capacity&quot; increasing). If I happen to connect my Mac to a power source and then boot PC-BSD, the battery indicator (on GNOME, KDE, XFCE, etc) and acpiconf -i 0 say charging, as they are supposed to. But if I then disconnect the Mac from the power source, the battery indicator on GNOME, KDE, and so on says &quot;Laptop is fully charged&quot;, while acpiconf -i 0 says:
&quot;
Design capacity:	65000 mWh
Last full capacity:	65700 mWh
Technology:		secondary (rechargeable)
Design voltage:		10950 mV
Capacity (warn):	250 mWh
Capacity (low):		100 mWh
Low/warn granularity:	10 mWh
Warn/full granularity:	10 mWh
Model number:		bq20z451077VCDEF0123456789ABCDE
Serial number:		
Type:			LIONz451077VCDEF0123456789ABCDE
OEM info:		SMPNz451077VCDEF0123456789ABCDE
State:			high 
Remaining capacity:	95%
Remaining time:		unknown
Present rate:		24127 mW
Present voltage:	12161 mV
&quot;
which is a whole lot better than it would be without the 
debug.acpi.max_tasks=&quot;XXXX&quot; in /boot/loader.conf.

My sysctl now reads (with results affected by the debug.acpi.max_tasks=&quot;128&quot;):
hw.acpi.supported_sleep_state: S3 S4 S5
hw.acpi.power_button_state: S5
hw.acpi.sleep_button_state: S3
hw.acpi.lid_switch_state: NONE
hw.acpi.standby_state: NONE
hw.acpi.suspend_state: S3
hw.acpi.sleep_delay: 1
hw.acpi.s4bios: 0
hw.acpi.verbose: 0
hw.acpi.disable_on_reboot: 0
hw.acpi.handle_reboot: 1
hw.acpi.reset_video: 0
hw.acpi.cpu.cx_lowest: C1
hw.acpi.acline: 1
hw.acpi.battery.life: 93
hw.acpi.battery.time: -1
hw.acpi.battery.state: 0
hw.acpi.battery.units: 1
hw.acpi.battery.info_expire: 5

So, to make a long story short, all I&#039;ve really done is to add
bebug.acpi.max_tasks=&quot;128&quot; to /boot/loader.conf. (I&#039;ve tried to increase that number to 2048 without much visible effect).]]></description>
		<content:encoded><![CDATA[<p>Yesterday, I opened up a forum post on the FreeBSD forums and described my problem there. A tip another user sent me was to add the following to /boot/loader.conf: &#8220;debug.acpi.max_tasks=&#8221;128&#8243;. It worked to some extent; when I boot up PC-BSD on battery source, the system behaves the way it should, it displays the time until empty, XX% remaining, etc. However, if I connect a power source, the system does not necessarily notice it, so the battery icon, as well as acpiconf -i 0 says &#8220;discharging&#8221; (with the &#8220;Remaining capacity&#8221; increasing). If I happen to connect my Mac to a power source and then boot PC-BSD, the battery indicator (on GNOME, KDE, XFCE, etc) and acpiconf -i 0 say charging, as they are supposed to. But if I then disconnect the Mac from the power source, the battery indicator on GNOME, KDE, and so on says &#8220;Laptop is fully charged&#8221;, while acpiconf -i 0 says:<br />
&#8221;<br />
Design capacity:	65000 mWh<br />
Last full capacity:	65700 mWh<br />
Technology:		secondary (rechargeable)<br />
Design voltage:		10950 mV<br />
Capacity (warn):	250 mWh<br />
Capacity (low):		100 mWh<br />
Low/warn granularity:	10 mWh<br />
Warn/full granularity:	10 mWh<br />
Model number:		bq20z451077VCDEF0123456789ABCDE<br />
Serial number:<br />
Type:			LIONz451077VCDEF0123456789ABCDE<br />
OEM info:		SMPNz451077VCDEF0123456789ABCDE<br />
State:			high<br />
Remaining capacity:	95%<br />
Remaining time:		unknown<br />
Present rate:		24127 mW<br />
Present voltage:	12161 mV<br />
&#8221;<br />
which is a whole lot better than it would be without the<br />
debug.acpi.max_tasks=&#8221;XXXX&#8221; in /boot/loader.conf.</p>
<p>My sysctl now reads (with results affected by the debug.acpi.max_tasks=&#8221;128&#8243;):<br />
hw.acpi.supported_sleep_state: S3 S4 S5<br />
hw.acpi.power_button_state: S5<br />
hw.acpi.sleep_button_state: S3<br />
hw.acpi.lid_switch_state: NONE<br />
hw.acpi.standby_state: NONE<br />
hw.acpi.suspend_state: S3<br />
hw.acpi.sleep_delay: 1<br />
hw.acpi.s4bios: 0<br />
hw.acpi.verbose: 0<br />
hw.acpi.disable_on_reboot: 0<br />
hw.acpi.handle_reboot: 1<br />
hw.acpi.reset_video: 0<br />
hw.acpi.cpu.cx_lowest: C1<br />
hw.acpi.acline: 1<br />
hw.acpi.battery.life: 93<br />
hw.acpi.battery.time: -1<br />
hw.acpi.battery.state: 0<br />
hw.acpi.battery.units: 1<br />
hw.acpi.battery.info_expire: 5</p>
<p>So, to make a long story short, all I&#8217;ve really done is to add<br />
bebug.acpi.max_tasks=&#8221;128&#8243; to /boot/loader.conf. (I&#8217;ve tried to increase that number to 2048 without much visible effect).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dru</title>
		<link>http://blog.pcbsd.org/2012/01/pc-bsd-9-0-users-handbook/#comment-1867</link>
		<dc:creator>dru</dc:creator>
		<pubDate>Tue, 24 Jan 2012 15:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.pcbsd.org/?p=795#comment-1867</guid>
		<description><![CDATA[Replying here as a bit more room. Let us know if you have a chance to experiment with ACPI sysctl settings and which ones improved the situation. Info to get you started is at the beginning of this page: http://wiki.pcbsd.org/index.php/Laptops.]]></description>
		<content:encoded><![CDATA[<p>Replying here as a bit more room. Let us know if you have a chance to experiment with ACPI sysctl settings and which ones improved the situation. Info to get you started is at the beginning of this page: <a href="http://wiki.pcbsd.org/index.php/Laptops" rel="nofollow">http://wiki.pcbsd.org/index.php/Laptops</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
