Wiki code for x86 : OpenSolaris 2009.06 Release Notes

Hide Line numbers
1: <h2>Release Notes for the x86: OpenSolaris 2009.06 Release</h2>
2: 
3:  This page lists the Release Notes for the **x86: OpenSolaris 2009.06** release. For additional information on the following issues, look up the bug number in <a href="http://defect.opensolaris.org/bz/">Bugzilla</a>.
4: 
5: Click <a href="http://hub.opensolaris.org/bin/view/Project+indiana/sparc">SPARC</a> for Release Notes for the SPARC: OpenSolaris 2009.06 release. For information about the new features in the OpenSolaris 2009.06 release, see <a href="http://www.opensolaris.com/learn/features/whats-new/200906">What’s New in OpenSolaris 2009.06</a>.
6: 
7: For <b>translations</b> of this document, refer to <a href="http://hub.opensolaris.org/bin/view/Project+indiana/relnotes">Release Notes translated into non-English Languages</a>
8: 
9: <table border="1">
10: <tr>
11: <td>
12: <h3>CONTENTS</h3>
13: <br>
14: <ol>
15: 
16: <li><a href="#general">
17: <h4>General Information</h4>
18: </a> </li>
19: 
20: <ul>
21: 
22: <li>
23: <p><a href="#upgradeUM">Upgrading OpenSolaris 2008.11 to OpenSolaris 2009.06 Using Update Manager.
24: </a></p>
25: </li>
26: 
27: <li>
28: <p><a href="#upgrade">Upgrading OpenSolaris 2008.05 to Later Versions of OpenSolaris.
29: </a></p>
30: </li>
31: 
32: <li>
33: <p>
34: <a href="#Low_Mem">Installing OpenSolaris on Systems With Low Memory.</a>
35: </p>
36: </li>
37: 
38: </ul>
39: 
40: 
41: <li><a href="#docissue">
42: <h4>Documentation Issues</h4>
43: </a> </li>
44: 
45: <ul>
46: <li>
47: <p><a href="#getstart">Getting Started With OpenSolaris 2009.06 Guide.</a> </p>
48: </li>
49: 
50: </ul>
51: 
52: 
53: <li><a href="#install">
54: <h4>Installation Bugs</h4>
55: </a> </li>
56: 
57: <ul>
58: <li>
59: <p><a href="#64">64 - Installer, but not Desktop, Allows Empty
60: Passwords.</a></p>
61: </li>
62: 
63: <li>
64: <p><a href="#1161">1161 - GUI Installer Shrinks the Solaris
65: Partition to be Created Even if Enough Available Space is Reported on
66: the Disk Screen.</a></p>
67: </li>
68: 
69: <li>
70: <p><a href="#1685">1685 - Renaming a Busy BE Might Fail.</a></p>
71: </li>
72: 
73: <li>
74: <p><a href="#3691">3691 - Using Fast Reboot When Specifying the
75: Name of a BE Fails.</a></p>
76: </li>
77: 
78: <li>
79: <p><a href="#3783">3783 - Installer Fails if the User Creates or
80: Imports the ZFS Pool <tt>rpool</tt>.</a></p>
81: </li>
82: 
83: <li><a href="#3947">3947 - Distribution Constructor Does Not
84: Recognize ZFS File System Mountpoints for Build Areas.</a></li>
85: 
86: <li>
87: <p><a href="#4061">4061 - Only the First GRUB <tt>menu.lst</tt>
88: Entry of the Source BE Is Created When Creating a New BE.</a></p>
89: </li>
90: 
91: <li><a href="#4589">4589 - Exception Message Generated by
92: Distribution Constructor Upon Successful Termination.</a></li>
93: 
94: <li>
95: <p><a href="#5003">5003 - Crash Dumps Are Not Saved to the File
96: System at Boot Time By Default.</a> </p>
97: </li>
98: 
99: 
100: <li><p><a href="#7218">7218 - Convert Existing <tt>installadm</tt> Services.</a> </p></li>
101: 
102: <li><p><a href="#8575">8575 - Automated Installation Fails if Slice 0 is Configured on the Client With Less Than 8 GB Disk Space.</a> </p></li>
103: 
104: <li>
105: <p><a href="#8661">8661 - Automated Installer Fails to Continue With Installation if Slices from the Previous Configuration Exist.</a> </p>
106: </li>
107: 
108: <li>
109: <p><a href="#8773">8773 - <tt>installadm create-service</tt>
110: Followed Quickly by <tt>installadm delete-service</tt> Causes <tt>installadm</tt> to Hang.</a> </p>
111: </li>
112: 
113: <li><p><a href="#8879">8879 - xVM hvm Guests Fail to PXE Boot While Installing From Build 111a Automated Installation Image.</a> </p></li>
114: 
115: <li><p><a href="#8961">8961 - Specifying pkg Version Strings in the Automated Installation Manifest List of Packages causes Automated Installation to Fail.</a> </p></li>
116: 
117: <li><p><a href="#9026">9026 - VTOC Partition Size Is Not Aligned to the Cylinder Boundary on Disks Larger Than 1.96 TB.</a> </p></li>
118: 
119: <!--<li><p><a href="#9214">9214 - <tt>installadm create-service</tt> Does Not Automatically Create <tt>/var/ai/image-server/logs</tt> Directory.</a> </p></li>
120: -->
121: 
122: 
123: <li>
124: <p><a href="#6670311">6670311 - Installer Might Fail if the Linux
125: Swap Primary Partition Precedes the Solaris Partition.</a> </p>
126: </li>
127: 
128: <li>
129: <p><a href="#6795293">6795293 - <tt>libdiskmgt</tt> Dumps Core on Systems With Fiber Channel Disks Attached.</a></p>
130: </li>
131: 
132: <li><p><a href="#6838658">6838658 - ZFS Hangs During Install if a Primary Linux Swap Partition Exists.</a> </p></li>
133: 
134: <li><p><a href="#6843138">6843138 - Cannot Boot a 2.2 TB Disk with a zfs Root.</a> </p></li>
135: 
136: <li><p><a href="#6845928">6845928 - Out-of-sync Boot Archive Message Displays an Incorrect Fix.</a> </p></li>
137: 
138: </ul>
139: <li><a href="#packaging">
140: <h4>Packaging Bugs</h4>
141: </a> </li>
142: 
143: <ul><li><p><a href="#7836">7836 - Warnings Are Displayed While Using <tt>pkg image-update</tt>.</a> </p></li>
144: 
145: <li><p><a href="#8246">8246 - Packagemanager Does Not Change Locale for Category Names.</a> </p></li>
146: 
147: </ul>
148: 
149: 
150: <li><a href="#desktop">
151: <h4>Desktop Bugs</h4>
152: </a> </li>
153: 
154: <ul>
155: <li><p><a href="#2656">2656 & 6366 - Enabling the printers:snmp Service Causes System to Revert to Maintenance State.</a></p></li>
156: 
157: <li>
158: <p><a href="#2900">2900 - Firefox Crashes in Build 95.</a></p>
159: </li>
160: 
161: <li>
162: <p><a href="#5543">5543 - Tracker Does Not Index the Home
163: Directory by Default.</a> </p>
164: </li>
165: 
166: <li>
167: <p><a href="#5544">5544 - Tracker Cannot Search Evolution Emails.</a>
168: </p>
169: </li>
170: 
171: 
172: <li><p><a href="#8748">8748 - Windows Are Maximized on All Screens in the Twinview or Xinerama Mode.</a> </p></li>
173: 
174: <li>
175: <p><a href="#6742850">6742850 - CJK Characters Do Not Display
176: Correctly in the Java Application Environment.</a> </p>
177: </li>
178: 
179: </ul>
180: 
181: 
182: <li><a href="#hardware">
183: <h4>Hardware-Related Bugs</h4>
184: </a> </li>
185: 
186: <ul><li><p><a href="#6658667">6658667 - MAC Address Is Reversed in Some mcp61-based Machines.</a> </p></li></ul>
187: 
188: 
189: <li><a href="#locale">
190: <h4>Localization Bugs<br>
191: </h4>
192: </a> </li>
193: 
194: <ul>
195: <li>
196: <p><a href="#5473">5473 - en_US/es_ES/fr_FR/de_DE UTF-8 Locales
197: Might Not be Installed by <tt>pkg image-update</tt>.</a> </p>
198: </li>
199: 
200: <li>
201: <p><a href="#8880">8880 - Input Method Preference Editor Help
202: Fails to Load.</a></p>
203: </li>
204: 
205: </ul>
206: 
207: 
208: <li><a href="#eos">
209: <h4>End-of-Software
210: Support
211: Statements</h4>
212: </a> </li>
213: 
214: <ul>
215: <li>
216: <p><a href="#xorg"><tt>xorgcfg</tt> and <tt>xorgconfig</tt>
217: Utilities.</a> </p>
218: </li>
219: 
220: </ul>
221: 
222: 
223: <li><a href="#troubleinfo">
224: <h4>Additional Installation Troubleshooting Information</h4>
225: </a> </li><br>
226: </ol>
227: 
228: </tr>
229: </table>
230: <br>
231: <br>
232: 
233: 
234: <a name="gentextid-1093"></a>
235: <h2><a name="general"></a>General Information</h2>
236: <p>This section provides general information such as upgrade issues and behavior changes in the OpenSolaris 2009.06 OS.</p>
237: 
238: 
239: <ul>
240: 
241: <li>
242: <a name="gentextid-1093"></a>
243: <h4><a name="upgradeUM"></a>Upgrading OpenSolaris 2008.11 to OpenSolaris 2009.06 Using Update Manager</h4>
244: <a name="gentextid-1095"></a>
245: 
246: <p>
247: The OpenSolaris Update Manager automatically detects when new packages are available for your system, including when the Update Manager itself needs to be updated. In this case, Update Manager will prompt you to open a terminal window and execute the following command:
248: <pre>$ pfexec pkg install SUNWipkg</pre>
249: <p>
250: After executing this command, you must close the Update Manager and then restart it via the System-> Administration menu to complete the update. 
251: </li>
252: 
253: 
254: <li>
255: <a name="gentextid-1093"></a>
256: <h4><a name="upgrade"></a>Upgrading OpenSolaris 2008.05 to Later Versions of OpenSolaris</h4>
257: <p>General instructions for updating from the OpenSolaris 2008.05 release to later versions of OpenSolaris are as follows:</p>
258: 
259: <ol>
260: <li>Before using the <i>image-update</i> subcommand, it is required that the latest available version of the IPS software and install libraries be installed for your current boot environment (BE) 
261: 
262: <pre>
263:     $ BUILD=`uname -v | sed -e "s/snv_//" -e "s/\[a-z\]//"`
264:     $ pfexec pkg refresh
265:     $ pfexec pkg install entire@0.5.11-0.${BUILD}
266:     $ pfexec pkg install SUNWipkg@0.5.11-0.${BUILD}
267:     $ pfexec pkg install SUNWinstall-libs 
268: </pre> </li>
269: 
270: <li>Use <i>image-update</i> directly as follows
271: 
272: <pre>
273:     $ pfexec pkg image-update
274: </pre>
275: 
276: <p>At this point, you can boot into the updated BE using <tt>reboot(1M)</tt>
277: or <tt>init(1M)</tt> as usual.</li>
278: 
279: </ol>
280: </li>
281: 
282: 
283: <li>
284: 
285: <h4><a name="Low_Mem">Installing OpenSolaris on Systems With Low Memory</a></h4>
286: 
287: <p>OpenSolaris supports installation through its Live CD on systems or virtual machines that contain 
288: 
289: at least 512 MB of RAM. The following limitations exist on systems with low memory.</p>
290: 
291: <p>While basic desktop functions and installation functions work well, attempting to use the Live CD 
292: 
293: as a full-blown user environment might cause issues. However, an installed system functions normally 
294: 
295: with 512 MB of RAM.</p>
296: 
297: <p>The Live CD supports booting the OpenSolaris kernel in either 32-bit mode or 64-bit mode depending 
298: 
299: on the capabilities of the underlying hardware. The OS will boot in the 64-bit mode only if the 
300: 
301: system has at least 1000 MB of RAM.  Systems
302: with less than this amount will boot in the 32-bit mode. This limitation does not apply to the 
303: 
304: installed system.</p>
305: 
306: <p>It is not possible to start the <b>’Read the Release Notes’</b> link from within the GUI Installer 
307: 
308: on systems with 512 MB of RAM.  Attempting to open this link causes the system to freeze while 
309: 
310: loading Firefox. Therefore users are recommended to read the Release Notes prior to launching the GUI 
311: 
312: Installer.</p>
313: 
314: <p>On systems with less than 700 MB of RAM the installer will create a dedicated swap slice instead 
315: 
316: of a ZFS volume to use for system swap.</p>
317: 
318: <p>For more information about the enhancements that were made to the OS from the OpenSolaris 2008.11 release onwards to 
319: 
320: support installation on systems with low memory, see <a 
321: 
322: href="http://defect.opensolaris.org/bz/show_bug.cgi?id=3597"># 3597</a><a name="3597"> Unable to 
323: 
324: install OpenSolaris with 512 MB Base Memory</a>.</p>
325: 
326: 
327: 
328: </li>
329: </ul>
330: 
331: 
332: <br>
333: <br>
334: <h2><a name="docissue"></a>Documentation Issues<br>
335: </h2>
336: <p>This section describes known issues that are related to the
337: OpenSolaris 2009.06 documentation.</p>
338: <ul>
339: <li>
340: <h4><a name="getstart"></a><a
341: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/gentextid-41.html">Getting
342: Started With OpenSolaris 2009.06 Guide</a></h4>
343: <p>Some links are incorrect in the
344: Getting Started With OpenSolaris
345: 2009.06 Guide.</p>
346: <ol>
347: <li>The following links are incorrect in the<a
348: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/links2.html">
349: Related Information</a> section of Chapter 2, Preparing to Install
350: OpenSolaris 2009.06:
351: <ul>
352: <li>http://frsun.downloads.edgesuite.net/sun/07C00892/media/demos/OpenSolarisDualBoot-Step1-Backup.html</li>
353: <li>http://frsun.downloads.edgesuite.net/sun/07C00892/media/demos/OpenSolarisDualBoot-Step2-Partition.html</li>
354: </ul>
355: <p>The following are the correct and updated links:</p>
356: <ul>
357: <li><a
358: href="http://webcast-west.sun.com/interactive/07C00892/media/demos/OpenSolarisDualBoot-Step1-Backup.html">http://webcast-west.sun.com/interactive/07C00892/media/demos/OpenSolarisDualBoot-Step1-Backup.html</a></li>
359: <li><a
360: href="http://webcast-west.sun.com/interactive/07C00892/media/demos/OpenSolarisDualBoot-Step2-Partition.html">http://webcast-west.sun.com/interactive/07C00892/media/demos/OpenSolarisDualBoot-Step2-Partition.html</a></li>
361: </ul>
362: </li><br>
363: <li>The following link is incorrect in the <a
364: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/links3.html">
365: Related Information</a> section of Chapter 3,  Installing the OpenSolaris 2009.06 Operating System:
366: <ul>
367: <li>http://www.opensolaris.org/os/project/indiana/resources/relnotes/200811/image-update/</li>
368: </ul>
369: <p>The following is the correct and updated link:</p>
370: <ul>
371: <li><a href="http://www.opensolaris.org/os/project/indiana/resources/relnotes/200805/image-update/">http://www.opensolaris.org/os/project/indiana/resources/relnotes/200805/image-update/</a>
372: </li>
373: </ul>
374: </ul>
375: 
376: <br>
377: <br>
378: 
379: <a name="gentextid-1093"></a>
380: <h2><a name="install"></a>Installation Bugs</h2>
381: <p>This section describes installation issues that apply to the
382: OpenSolaris 2009.06 OS.</p>
383: 
384: 
385: <ul>
386: 
387: <li>
388: <a name="gentextid-1093"></a>
389: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=64"># 64</a><a
390: name="64"> Installer, but not Desktop, Allows Empty Passwords</a></h4>
391: <a name="gentextid-1095"></a>
392: <h5>Description</h5>
393: <p>If, during installation, no root password is entered and no user
394: account is
395: created, you will not be able to log in to the installed
396: system.</p>
397: <a name="gentextid-1098"></a>
398: <h5>Workaround</h5>
399: <p>Choose one of the following workarounds:</p>
400: <ul>
401: <li>
402: <p>Enter a root password as follows:</p>
403: <ol>
404: <li>
405: <p>During boot, type “<tt>e</tt>” in the grub menu twice, in
406: order to edit the boot entry.</p>
407: </li>
408: <li>
409: <p>Add <tt>-s</tt> to the end of the boot entry, and boot with
410: this line.</p>
411: </li>
412: <li>
413: <p>Log in as root and use the <tt>passwd</tt> command to enter
414: a password.</p>
415: </li>
416: <li>
417: <p>Restart the system. Boot normally, and log in with the new
418: password.</p>
419: </li>
420: </ol>
421: </li>
422: <li>
423: <p>Set root so that it does not require a password as follows:</p>
424: <ol>
425: <li>
426: <p>During boot, type “<tt>e</tt>” in the grub menu twice, in
427: order to edit the boot entry.</p>
428: </li>
429: <li>
430: <p>Add <tt>-s</tt> to the end of the boot entry, and boot with
431: this line.</p>
432: </li>
433: <li>
434: <p>Log in to the system as root.</p>
435: </li>
436: <li>
437: <p>Edit the <tt>/etc/X11/gdm/custom.conf</tt> file so that the
438: value of PasswordRequired is false.</p>
439: </li>
440: </ol>
441: </li>
442: </ul>
443: </li>
444: 
445: 
446: 
447: <li>
448: <a name="gentextid-1235"></a>
449: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=1161">#
450: 1161</a><a name="1161"> GUI Installer Shrinks the Solaris Partition to
451: be Created Even if Enough Available Space is Reported on the Disk Screen</a></h4>
452: <a name="gentextid-1237"></a>
453: <h5>Description</h5>
454: <p>When creating a Solaris partition, the GUI installer only utilizes
455: the free space at the end of the disk after the last primary partition.
456: However, the sum of the total space available including gaps between
457: partitions is reported on the disk screen. If the user tries to create
458: a Solaris partition which is larger than the amount of free space
459: available at the end of the disk, the size of Solaris partition is
460: adjusted.</p>
461: <p>A warning message is displayed when the Next button is pressed on
462: the disk screen and the Solaris partition is shrunk. The title of the
463: warning message is as follows:</p>
464: <pre>Adjustments were made to the new partitions</pre>
465: <a name="gentextid-1242"></a>
466: <h5>Workaround</h5>
467: <p>Use the Solaris <tt>fdisk(1M)</tt> tool or the GParted tool to
468: create a Solaris2 partition. These tools enable the utilization of
469: unallocated space between already defined partitions. Select the newly
470: created Solaris2 partition as the target for the installation on the
471: installer disk screen.</p>
472: </li>
473: 
474: 
475: 
476: <li>
477: <a name="gentextid-1284"></a>
478: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=1685">#
479: 1685</a><a name="1685"> Renaming a Busy BE Might Fail</a></h4>
480: <a name="gentextid-1286"></a>
481: <h5>Description</h5>
482: <p>Renaming a boot environment (BE) might fail if the BE has a
483: dependent clone that is currently mounted or otherwise busy.</p>
484: <p>A typical example of this situation is when the live BE has
485: been successfully upgraded. If you then try to rename the
486: auto-generated and upgraded
487: BE, the renaming fails. The renaming fails because the upgraded BE has
488: been
489: activated and the live BE is now its clone.</p>
490: <a name="gentextid-1290"></a>
491: <h5>Workaround</h5>
492: <p>Use the following procedure:</p>
493: <ol>
494: <li>
495: <p>Activate the live BE.</p>
496: </li>
497: <li>
498: <p>Rename the upgraded BE.</p>
499: </li>
500: <li>
501: <p>Activate the upgraded BE.</p>
502: </li>
503: </ol>
504: <p>For example, if the live BE name is “opensolaris”, and the
505: auto-generated
506: BE name of the upgraded BE is “opensolaris-1,” use the following
507: commands:</p>
508: <pre># <tt>beadm activate <i>opensolaris</i></tt><br># <tt>beadm rename <i>opensolaris-1 new_name</i></tt><br># <tt>beadm activate <i>new_name</i></tt></pre>
509: </li>
510: 
511: 
512: 
513: <li>
514: <a name="gentextid-1235"></a>
515: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=3691">#
516: 3691</a><a name="3691"> Using Fast Reboot When Specifying the Name of a
517: BE Fails</a></h4>
518: <a name="gentextid-1237"></a>
519: <h5>Description</h5>
520: <p>The new fast reboot feature enables you to provide a <tt>’-e’</tt>
521: option to specify the name of the boot environment (BE) to which you
522: need to fast reboot. Attempting to do a fast reboot and specifying the
523: name of a BE fails in the OpenSolaris 2009.06 release. The following
524: error message is displayed:
525: </p>
526: <pre># reboot -f -e opensolaris-7<br>reboot: cannot mount BE opensolaris-7<br></pre>
527: <a name="gentextid-1242"></a>
528: <h5>Workaround</h5>
529: <p>Specify the full root dataset path to the BE to which you need to
530: fast reboot. For example: </p>
531: <pre># reboot -f rpool/ROOT/opensolaris-7 </pre>
532: </li>
533: 
534: 
535: 
536: <li>
537: <a name="gentextid-1235"></a>
538: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=3783">#
539: 3783</a><a name="3783"> Installer Fails if the User Creates or Imports
540: the ZFS Pool <tt>rpool</tt></a></h4>
541: <a name="gentextid-1237"></a>
542: <h5>Description</h5>
543: <p>If a ZFS pool named <tt>rpool</tt> is already present on the system
544: because it was manually imported or created by the user during the
545: current boot of the live CD, the install process fails. The last
546: message in the installation log file is as follows:</p>
547: <pre>Root pool rpool exists, we can’t proceed with the installation.</pre>
548: <p>This behavior is intentional and ensures that the installer does not
549: inadvertently corrupt the user’s data.</p>
550: <p>The installer recognises cases when <tt>rpool</tt> is created
551: by the installer but the installation process has failed or was
552: interrupted. In such cases, the installer destroys <tt>rpool</tt>
553: automatically after it is restarted.</p>
554: <a name="gentextid-1242"></a>
555: <h5>Workaround</h5>
556: <p>Choose one of the following workarounds:</p>
557: <ul>
558: <li>
559: <p>To preserve data in <tt>rpool</tt>, reboot the system and
560: do not import the pool. The pool remains invisible to the installer.
561: However, if the pool was created on the target disk then the pool
562: cannot be preserved. </p>
563: </li>
564: <li>
565: <p>If you do not want to preserve data in <tt>rpool</tt>,
566: destroy the pool before you start the installer by using the following
567: command:</p>
568: <pre>$ pfexec zpool destroy -f rpool </pre>
569: </li>
570: </ul>
571: </li>
572: 
573: 
574: 
575: <li>
576: <a name="gentextid-1235"></a>
577: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=3947">#
578: 3947</a><a name="3947"> Distribution Constructor Does Not Recognize ZFS
579: File System Mountpoints for Build Areas</a></h4>
580: <a name="gentextid-1237"></a>
581: <h5>Description</h5>
582: <p>If a system has a ZFS file system, the Distribution Constructor does
583: not recognise or treat a build area as a ZFS file system in the
584: following cases:</p>
585: <ul>
586: <li>
587: <p>A new sub-directory of the ZFS file system is specified as a
588: build area, but the mountpoint is specified instead of the <tt>zpool</tt>.</p>
589: </li>
590: <li>
591: <p>The build area already exists as a ZFS file system but the
592: mountpoint is specified instead of the <tt>zpool</tt></p>
593: </li>
594: </ul>
595: <p>For example, in the following <tt>zpool</tt>:</p>
596: <pre>$ zfs list | grep "disk2_pool/ib/pia"<br>disk2_pool/ib/pia 1.90G 355G 18K /export/home/ib/pia</pre>
597: <p>When you run the following command:</p>
598: <pre># distro_const build -p 1 slim_cd.xml</pre>
599: <p>Where the build area in <tt>slim_cd.xml</tt> is specified as <tt><i>build_area</i>/export/home/ib/pia<i>/build_area</i></tt>,
600: the following message error message is displayed:</p>
601: <pre>Checkpointing is not available<br>Rerun the build without -p<br></pre>
602: <a name="gentextid-1242"></a>
603: <h5>Workaround</h5>
604: <p>Specify the <tt>zpool</tt> in the manifest. For example, <tt><i>build_area</i>/disk2_pool/ib/pia<i>/build_area</i></tt>.</p>
605: </li>
606: 
607: 
608: 
609: <li>
610: <a name="gentextid-1235"></a>
611: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=4061">#
612: 4061</a><a name="4061"> Only the First GRUB <tt>menu.lst</tt> Entry of
613: the Source BE Is Created When Creating a New BE</a></h4>
614: <a name="gentextid-1237"></a>
615: <h5>Description</h5>
616: <p>When a new boot environment (BE) is created, the new BE will only
617: have one entry in the GRUB <tt>menu.lst</tt> file regardless of how
618: many entries the source BE has. The source BE’s first <tt>menu.lst</tt>
619: entry is used to create the entry for the new BE. All other entries are
620: ignored. This issue occurs when you create the new BE either through <tt>beadm</tt>
621: or <tt>pkg image-
622: update</tt>.</p>
623: <p>If the user needs the other entries for the new BE they are not
624: available.</p>
625: <a name="gentextid-1242"></a>
626: <h5>Workaround</h5>
627: <p>Edit the <tt>/rpool/boot/grub/menu.lst</tt> file and copy the
628: desired entries from the original BE. Replace the BE name in the source
629: entries with the BE name of the target.</p>
630: </li>
631: 
632: 
633: 
634: <li>
635: <a name="gentextid-1235"></a>
636: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=4589">#
637: 4589</a><a name="4589"> Exception Message Generated by Distribution
638: Constructor Upon Successful Termination</a></h4>
639: <a name="gentextid-1237"></a>
640: <h5>Description</h5>
641: <p>The Distribution Constructor might display the following error
642: message after successfully performing its function:</p>
643: <pre>Unhandled exception in thread started by<br>Error in sys.excepthook:<br><br>Original exception was:</pre>
644: <a name="gentextid-1242"></a>
645: <h5>Workaround</h5>
646: <p>This error message is displayed just before termination and can be
647: safely be ignored.</p>
648: </li>
649: 
650: 
651: 
652: <li>
653: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=5003">#
654: 5003</a><a name="5003"> Crash Dumps Are Not Saved to the File System at
655: Boot Time By Default</a></h4>
656: <a name="gentextid-1237"></a>
657: <h5To reduce reboot time, crash dumps are not saved to the file system at boot time by default.</p>
658: <a name="gentextid-1242"></a>
659: <h5>Workaround</h5>
660: <p>Use the <tt>dumpadm</tt>(1M) command to enable crash dumps at boot
661: time:</p>
662: <pre># dumpadm -y </pre>
663: <p>Alternatively, create a cron job that enables saving crash
664: dumps at any given later time.</p>
665: </li>
666: 
667: 
668: 
669: <li>
670: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=7218">#7218</a><a name="7218"> Convert Existing <tt>installadm</tt> Services</a></h4>
671: 
672: <a name="gentextid-1237"></a><h5>Description</h5>
673: 
674: <p>The latest version of SUNWinstalladm-tools from <a href="http:pkg.opensolaris.org/release">http:pkg.opensolaris.org/release</a> contains fixes for the following bug:</p>
675: <a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=7218">#7218 - <tt>installadm</tt> needs to move service data into SMF</a>
676: <p>If you update your automated install server with the versions of SUNWinstalladm-tools and SUNWinstall-libs packages that fix </a><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=7218">#7218</a>, then you will need to convert any services previously created with <tt>installadm create-service</tt>.</p>
677: 
678: <a name="gentextid-1242"></a><h5>Workaround</h5>
679: 
680: <p>Use the following procedure to convert the services created with <tt>installadm create-service</tt>.
681: <ol>
682: <li>Install the new SUNWinstalladm-tools and SUNWinstall-libs packages.</li>
683: <li>Reboot the automated install server.</li>
684: <li>Download and run the <tt>convert.sh</tt> script found at <a href="http://opensolaris.org/os/project/caiman/auto_install/convert.sh">http://opensolaris.org/os/project/caiman/auto_install/convert.sh</a>.</li>
685: <li>Enable the service:
686: <pre>svcadm enable svc:/system/install/server:default</pre></li>
687: </ol>
688: <p>For more information, see the <a href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/">OpenSolaris Automated Installer Guide</a>.
689: </p>
690: </li>
691: 
692: 
693: 
694: <li>
695: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8575">#8575</a><a name="8575"> Automated Installation Fails if Slice 0 is Configured on the Client With Less Than 8 GB Disk Space</a></h4>
696: 
697: <a name="gentextid-1237"></a><h5>Description</h5>
698: 
699: <p>Automated Installation fails when the Automated Installation manifest points to a target device and the slice 0 on target device is configured with less than 8 GB of disk space. The following error message is displayed:</p> 
700: <pre>Auto install failed</pre>
701: <p>The Automated Installation fails because it runs out of space in slice 0 of the target device.</p>
702: 
703: <a name="gentextid-1242"></a><h5>Workaround</h5>
704: <p>Choose one of the following workarounds:</p>
705: <ul>
706: <li>Create slice 0 of the target device with more than 8 GB space.</li>
707: <li>If there is another slice with more than 8 GB space, change the Automated Installation manifest to use that slice. For example, if you want to use Slice 4 of your target device c0t0d0, add the following lines to your Automated Installation manifest:
708: <pre>&lt;ai_target_device&gt;
709:    &lt;target_device_name&gt;c0t0d0&lt;/target_device_name&gt;
710:    &lt;target_device_install_slice_number&gt;4&lt;/target_device_install_slice_number&gt;
711: &lt;/ai_target_device&gt;
712: </pre></li>
713: </ul>
714: </li>
715: 
716: 
717: 
718: <li>
719: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8661">#8661</a><a name="8661"> Automated Installer Fails to Continue With Installation if Slices from the Previous Configuration Exist</a></h4>
720: 
721: <a name="gentextid-1237"></a><h5>Description</h5>
722: 
723: 
724: 
725: <p>When a custom Automated Installation manifest is used to install a system and there are customizations in the manifest to create slices other than the root slice if those slices already exist on the disk in your system, then the automated
726: installation fails. The following error message is seen in the install_log file:</p>
727: <pre>root@opensolaris:/tmp# tail -20 /tmp/install_log
728: 
729: <AI May  5 14:35:40> /tmp/ai_combined_manifest.xml is a valid manifest
730: <AI May  5 14:35:40> Auto reboot disabled
731: <AI May  5 14:53:32> Disk = c8t0d0 found on the system
732: <AI May  5 14:53:32> Disk name selected for installation is c8t0d0
733: <AI May  5 14:53:32> no manifest partition information found
734: <OM May  5 14:53:32> disk partition info not changed
735: <OM May  5 14:53:32> System reports enough physical memory for installation,
736: swap is optional
737: <OM_E May  5 14:53:32> creating slice which already exists
738: <AI May  5 14:53:32> failed to modify slice(s) specified in the manifest
739: <AI May  5 14:53:32> Auto install failed
740: </pre>
741: 
742: <a name="gentextid-1242"></a><h5>Workaround</h5>
743: 
744: <p>Use the <tt>format</tt>(1M) command to remove the existing slices from your disk. Rerun the automated installation by rebooting your system back into the automated install.</p>
745: </li>
746: 
747: 
748: 
749: <li>
750: <a name="gentextid-1235"></a>
751: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8773">#8773</a><a
752: name="8773"> <tt>installadm create-service</tt> Followed Quickly by <tt>installadm
753: delete-service</tt> Causes <tt>installadm</tt> to Hang</a></h4>
754: <a name="gentextid-1237"></a>
755: <h5>Description</h5>
756: <p>If you type <tt>installadm create-service</tt> followed immediately
757: by <tt>installadm delete-service,</tt> the <tt>installadm</tt>
758: command might hang. This command hangs because the <tt>installadm</tt> smf
759: service, <tt>svc:/system/install/server:default</tt>, is not online
760: when the <tt>installadm delete-service</tt> command is executed.</p>
761: <a name="gentextid-1242"></a>
762: <h5>Workaround</h5>
763: <p>Wait for the <tt>svc:/system/install/server:default</tt> service to
764: be online. To determine whether this service is online, type <tt>svcs
765: svc:/system/install/server:default</tt> and
766: check whether the STATE is listed as online.</p>
767: </li>
768: 
769: 
770: <li>
771: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8879">#8879</a>
772: <a name="8879"> xVM hvm Guests Fail to PXE Boot While Installing From Build 111a Automated Installation Image</a></h4>
773: 
774: <a name="gentextid-1237"></a><h5>Description</h5>
775: 
776: 
777: <p>PXE boot installation using Automated Installation fails for xVM hvm guests. On the guest console, after displaying the grub entry to boot, the system proceeds to download the kernel and boot archive from the automated install server.  The OS
778: banner appears. However, shortly afterwards, the guest cannot connect to the network to download the required installation files and proceed.
779: The installing guest drops to maintenance mode, and prompts for a
780: username and password.</p>
781: 
782: <a name="gentextid-1242"></a><h5>Workaround</h5>
783: <p>The guest client to be installed by using Automated Installation should be booted with additional
784: kernel options in the <tt>menu.lst</tt> file which is retrieved from the boot server.
785: 
786: Use any one of the following methods to set the correct <tt>menu.lst</tt> entries for the client on the
787: automated install server:</p>
788: <ul>
789: <li><p>For individual clients, type the <tt>installadm create-client</tt> command to specify
790:    the extra boot options needed for each installing client. The command syntax is as follows:</p>
791: <tt>installadm create-client -b network-interface=xnf0,xpv-hcp=dhcp
792:       -e <i>MAC address of the client</i> -t <i>target image</i> -n <i>install service name</i>
793: </tt>
794: <p>For example:</p>
795: <tt># installadm create-client -b network-interface=xnf0,xpv-hcp=dhcp
796:       -e 00:16:3e:7f:a9:6f -t /space/images/2009.06_111b -n osol_111b
797: </tt></li>
798: <li><p>For all clients of a given automated install service, manually edit the appropriate 
799:    <tt>menu.lst</tt> file in <tt>/tftpboot</tt> to add the <tt>network-interface</tt> and <tt>xpv-hcp</tt>
800:    boot options in the previous example.</p>
801: <p>The <tt>menu.lst</tt> file is named according to the following pattern:</p>
802: <tt>menu.lst.&lt;AI service name&gt;</tt>
803: <p>For example, for the automated install service <tt>osol</tt>, the <tt>menu.lst</tt> file is <tt>/tftpboot/menu.lst.osol</tt> and has the following structure:</p>
804: <tt>default=0<br>
805:    timeout=30<br>
806:    min_mem64=1536<br>
807:    title OpenSolaris 2009.06 snv_111b X86 <br>
808:            kernel$ /I86PC.OpenSolaris-10/platform/i86pc/kernel/$ISADIR/unix -B install_media=http://10.0.0.1:5555/space/images/osol,install_service=osol
809: ,install_svc_address=10.0.0.1:46502,livemode=text<br>
810:            module /I86PC.OpenSolaris-10/x86.microroot</tt>
811: 
812: <p>After adding the required boot options, the <tt>menu.lst</tt> file has the following structure:</p>
813: 
814:    <tt>default=0<br>
815:    timeout=30<br>
816:    min_mem64=1536<br>
817:    title OpenSolaris 2009.06 snv_111b X86 <br>
818:            kernel$ /I86PC.OpenSolaris-10/platform/i86pc/kernel/$ISADIR/unix -B install_media=http://10.0.0.1:5555/space/images/osol,install_service=osol
819: ,install_svc_address=10.0.0.1:46502,network-interface=xnf0,xpv-hcp=dhcp,livemode=text<br>
820:            module /I86PC.OpenSolaris-10/x86.microroot 
821: </tt>
822: <p>For more information, see the <a href="http://dlc.sun.com/osol/docs/content/dev/AIinstall/">OpenSolaris Automated Installer Guide</a>.</p>
823: </li>
824: </ul>
825: </li>
826: 
827: 
828: <li>
829: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8961">#8961</a>
830: <a name="8961"> Specifying pkg Version Strings in the Automated Installation Manifest List of Packages causes Automated Installation to Fail.</a></h4>
831: 
832: <a name="gentextid-1237"></a><h5>Description</h5>
833: 
834: <p>Automated Installation might fail if version strings for packages are specified in the Automated Installation manifest. 
835: The following error message might be found in the Automated Installation SMF log at <tt>/var/svc/log/application-auto-installer\:default.log</tt>.</p>
836: <pre>Unable to install SUNW in /a
837: om_perform_install failed with error 114
838: Auto install failed</pre>
839: 
840: 
841: <a name="gentextid-1242"></a><h5>Workaround</h5>
842: <p>List the entire package first and specify version strings for the entire package only. For example:</p>
843: <pre>&lt;ai_install_packages&gt;
844:     &lt;pkg name="entire@0.5.11,5.11-0.111"/&gt;
845:     &lt;pkg name="SUNWcsd"/&gt;
846:     &lt;pkg name="SUNWcs"/&gt;
847:     &lt;pkg name="SUNWj6rtx"/&gt;
848:     &lt;pkg name="SUNWgroff"/&gt;
849:     &lt;pkg name="SUNWgcc"/&gt;
850:     &lt;pkg name="babel_install"/&gt;
851:     &lt;pkg name="xvm"/&gt;
852: &lt;/ai_install_packages></pre&gt;
853: </li>
854: 
855: 
856: <li>
857: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=9026">#9026</a>
858: <a name="9026"> VTOC Partition Size Is Not Aligned to the Cylinder Boundary on Disks Larger Than 1.96 TB</a></h4>
859: 
860: <a name="gentextid-1237"></a><h5>Description</h5>
861: 
862: <p>On disks larger than 1.96 TB, the installer creates VTOC slices which are not aligned on the cylinder boundary. 
863: The installed OpenSolaris instance will boot successfully but the <tt>format</tt>(1M) tool cannot process the VTOC configuration.
864: The tool will report that the disk does not contain a valid label.</p>
865: 
866: 
867: <a name="gentextid-1242"></a><h5>Workaround</h5>
868: <p>Use the Solaris <tt>fdisk</tt>(1M) and <tt>format</tt>(1M) tools to create the required VTOC configuration outside the installer.
869: Then install into the existing slice using the Automated Installer.</p>
870: <p>For more information on how to configure and use the Automated Installer, see the <a href="http://dlc.sun.com/osol/docs/content/dev/AIinstall/index.html">OpenSolaris Automated Installer Guide</a>.</p>
871: 
872: </li>
873: 
874: 
875: <!--<li>
876: <a name="gentextid-1001"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=9214">#9214</a>
877: <a name="9214"><tt>installadm create-service</tt> Does Not Automatically Create <tt>/var/ai/image-server/logs</tt> Directory</a></h4>
878: 
879: <a name="gentextid-1002"></a><h5>Description</h5>
880: 
881: <p>As part of using the automated installer to install the OpenSolaris 2009.06 OS to multiple client systems, you run the <tt>installadm create-service</tt> command to create an install service.  This <tt>installadm create-service</tt> command does not automatically create the needed directory, <tt>/var/ai/image-server/logs</tt>, for the log files.</p>
882: 
883: 
884: <a name="gentextid-1003"></a><h5>Workaround</h5>
885: <p>You can manually create the <tt>/var/ai/image-server/logs</tt> directory by running the following command:</p>
886: 
887: <p><tt>pfexec mkdir -p /var/ai/image-server/logs</tt></p>
888: 
889: <p>For more information about installing to multiple client systems, see the <a href="http://dlc.sun.com/osol/docs/content/dev/AIinstall/index.html">OpenSolaris Automated Installer Guide</a>.</p>
890: 
891: </li>-->
892: 
893: 
894: <li>
895: <a name="gentextid-1385"></a>
896: <h4><a href="http://bugs.opensolaris.org/view_bug.do?bug_id=6670311">#
897: 6670311</a><a name="6670311"> Installer Might Fail if the Linux Swap
898: Primary Partition Precedes the Solaris Partition</a></h4>
899: <a name="gentextid-1387"></a>
900: <h5>Description</h5>
901: <p>The new Solaris installer installs the Solaris operating system into
902: the Solaris2 partition <tt>
903: (0xbf)</tt>. The installer does not support multiple Solaris partitions
904: on one disk. However, the installer recognizes the Linux swap partition
905: <tt>(0x82)</tt> correctly and installs successfully if the primary
906: partition is used as the Linux swap partition.</p>
907: <p>Solaris installation fails when the partition configuration is as
908: following:</p>
909: <ul>
910: <li>
911: <p>The Linux swap primary partition precedes the Solaris2 partition
912: </p>
913: </li>
914: <li>
915: <p>The Solaris2 partition is not active</p>
916: </li>
917: </ul>
918: <a name="gentextid-1098"></a>
919: <h5>Workaround</h5>
920: <p>Choose one of the following workarounds:</p>
921: <ul>
922: <li>
923: <p>Avoid defining a Linux swap partition as a primary partition on
924: the same disk where the Solaris2 primary partition will be created. For
925: example, create the Linux swap partition as logical volume within
926: extended partition.</p>
927: </li>
928: <li>
929: <p>Ensure that the Solaris2 partition precedes the Linux swap
930: partition.</p>
931: </li>
932: <li>
933: <p>Create the Solaris2 partition outside the installer and mark it
934: as active. Then install into that preexisting partition.</p>
935: </li>
936: <li>
937: <p>Before installation, change the Linux swap partition type to
938: another type, excluding <tt>
939: (0xbf)</tt> or <tt>(0x82)</tt>. After the installation is complete,
940: change the Linux swap partition type back to <tt>(0x82)</tt>.</p>
941: </li>
942: </ul>
943: 
944: <li><a name="gentextid-1000"></a><h4><a href="http://bugs.opensolaris.org/view_bug.do?bug_id=6795293">#
945: 6795293</a><a name="6795293"> <tt>libdiskmgt</tt> Dumps Core on Systems With Fiber Channel Disks Attached</h4>
946: 
947: <h5>Description</h5>
948: <p>If you try to install the OpenSolaris 2009.06 OS on a system that has Fiber Channel disks attached, <tt>/usr/bin/gui-install</tt> dumps the core.</p>
949: 
950: <h5>Workaround</h5>
951: <p>Disconnect the Fiber Channel disks and restart the installation.</p>
952: 
953: 
954: <li>
955: <a name="gentextid-1235"></a><h4><a href="http://bugs.opensolaris.org/view_bug.do?bug_id=6838658">#6838658</a><a name="6838658"> ZFS Hangs During Install if a Primary Linux Swap Partition Exists</a></h4>
956: 
957: <a name="gentextid-1237"></a><h5>Description</h5>
958: 
959: <p>bootadm causes ZFS to hang while installing OpenSolaris 2009.06. No error message is displayed. Install hangs at 99% completion.</p>
960: 
961: <a name="gentextid-1242"></a><h5>Workaround</h5>
962: <p>Ensure that the Linux swap partition is not a primary partition. Check if the Linux swap partition is a logical partition. To check if it’s a logical partition, delete the Linux swap and recreate it as a logical partition. Once this is done the installation is successful.</p>
963: <p>See also, <a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8693">#8693.
964: </li>
965: 
966: 
967: 
968: <li>
969: <a name="gentextid-1235"></a><h4><a href="http://bugs.opensolaris.org/view_bug.do?bug_id=6843138">#6843138</a>
970: <a name="6843138"> Cannot Boot a 2.2 TB Disk with a zfs Root</a></h4>
971: 
972: <a name="gentextid-1237"></a><h5>Description</h5>
973: 
974: 
975: <p>The OpenSolaris 2009.06 OS should not be booted from a disk whose capacity exceeds 2<sup>32</sup> sectors or 2 TB when the sector size is 512 bytes.
976: This is because of a limitation in the current implementation of GRUB which OpenSolaris uses as the boot loader.</p>
977: 
978: 
979: <a name="gentextid-1242"></a><h5>Workaround</h5>
980: <p>None.</p>
981: 
982: </li>
983: 
984: 
985: <li>
986: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=9187">#6845928</a>
987: <a name="6845928"> Out-of-sync Boot Archive Message Displays an Incorrect Fix</a></h4>
988: 
989: <a name="gentextid-1237"></a><h5>Description</h5>
990: 
991: 
992: <p>The message displayed when you boot an out-of-sync boot archive advises the user to boot from the GRUB menu "Solaris Failsafe" option . No such option is available on OpenSolaris.</p>
993: 
994: 
995: <a name="gentextid-1242"></a><h5>Workaround</h5>
996: <p>None.</p>
997: 
998: </li>
999: 
1000: 
1001: </ul>
1002: </li>
1003: 
1004: 
1005: 
1006: 
1007: <br>
1008: <br>
1009: <a name="gentextid-1093"></a>
1010: <h2><a name="packaging"></a>Packaging Bugs</h2>
1011: <p>This section describes IPS-related issues that apply to the
1012: OpenSolaris 2009.06 OS.</p><ul>
1013: 
1014: <li>
1015: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=7836">#7836</a><a name="7836"> Warnings Are Displayed  While Using <tt>pkg image-update</tt></a></h4>
1016: 
1017: <a name="gentextid-1237"></a><h5>Description</h5>
1018: 
1019: <p>While updating an image to build 111 or beyond, a warning message similar to the following might be displayed:</p>
1020: <pre>driver (emlxs) upgrade (removal of minor perm ’* 0600 root sys’’) failed with
1021: return code 252
1022: command run was: /usr/sbin/update_drv -b /mnt -d -m * 0600 root sys’ emlxs
1023: command output was:
1024: ------------------------------------------------------------
1025: No entry found for driver (emlxs) in file (/mnt/etc/minor_perm).
1026: ------------------------------------------------------------
1027: </pre>
1028: <p>This bug occurs only when the SUNWemlxs package is manually added to the OpenSolaris 2008.11 OS and the system is updated to the OpenSolaris 2009.06 release. This warning message is displayed for many drivers including emlxs, afe, audio810, audiohd, audioixp, bnx, isa, ixgbe, nge, nv_sata, and qlc.</p>
1029: 
1030: <a name="gentextid-1242"></a><h5>Workaround</h5>
1031: <p>The warning can be ignored.</p>
1032: 
1033: </li>
1034: 
1035: <li>
1036: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8246">#8246</a>
1037: <a name="8246"> Packagemanager Does Not Change Locale for Category Names</a></h4>
1038: 
1039: <a name="gentextid-1237"></a><h5>Description</h5>
1040: 
1041: <p>The left pane in Packagemanager is used to display category names. These names are localized in different locales. 
1042: However, the localization of the names is not changed if you switch the locale, even after restarting Packagemanager.</p>
1043: 
1044: <a name="gentextid-1242"></a><h5>Workaround</h5>
1045: <p>Click the reload button, which will reload the category names in the new locale.</p>
1046: </li>
1047: </ul>
1048: 
1049: 
1050: 
1051: <br>
1052: <br>
1053: <a name="gentextid-1093"></a>
1054: <h2><a name="desktop"></a>Desktop Bugs</h2>
1055: <p>This section describes desktop related issues that apply to the
1056: OpenSolaris 2009.06 OS.</p>
1057: <ul>
1058: 
1059: 
1060: <li>
1061: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=2656"> #2656</a> and <a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=6366">#6366</a> <a name="2656">Enabling the <tt>printers:snmp</tt> Service Causes System to Revert to Maintenance State</a></h4>
1062: 
1063: <h5>Description</h5>
1064: 
1065: <p>After installing the OpenSolaris 2009.06 release, the <tt>hald-addon-network-discovery</tt> agent cannot be enabled. This failure occurs regardless of which method you use to enable the service.</p>
1066: 
1067: 
1068: <p>An error message similar to the following is displayed in the service log:</p>
1069: <pre>\[ Jul 24 21:09:32 Executing start method<br>("/lib/svc/method/svc-network-discovery start snmp"). \]<br>/usr/bin/dbus-send \--\system \--\print-reply \--\dest=org.freedesktop.Hal<br>\--\type=method_call /org/freedesktop/Hal/devices/network_attached<br>org.freedesktop.Hal.Device.NetworkDiscovery.EnablePrinterScanningViaSNMP<br>int32:60 string:public string:0.0.0.0<br>Error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible<br>causes include: the remote application did not send a reply, the message bus<br>security policy blocked the reply, the reply timeout expired, or the network<br>connection was broken.<br>\[ Jul 24 21:09:40 Method "start" exited with status 1. \]</pre>
1070: 
1071: <h5>Workaround</h5>
1072: <p>Use the following procedure:</p>
1073: <ol>
1074: <li>
1075: <p> Add the SUNWSmmgr package. </p>
1076: <pre><tt># pkg install SUNWSmmgr</tt></pre>
1077: </li>
1078: <li>Edit the <tt>/etc/dbus-1/system.d/hal.conf</tt> file. Add the following line to the <tt>&lt;policy context="default"&gt;</tt> section:
1079: <pre><tt># allow send_interface="org.freedesktop.Hal.Device.NetworkDiscovery" send_destination="org.freedesktop.Hal"/&gt;</tt></pre>
1080: </li>
1081: <li>
1082: <p> Restart the HAL add-on module.</p>
1083: <p>- To restart the add-on module from the desktop, perform these steps:</p>
1084: <ol type="a">
1085: <li>
1086: <p>Open the Services settings application from the main menu.</p>
1087: <p>System-&gt; Administration-&gt; Services</p>
1088: <p>The Services settings window is displayed.</p>
1089: </li>
1090: <li>Select the Hardware Abstraction Layer network attached device discovery option <tt>(network/device-discovery/printers:snmp)</tt>.</li>
1091: <li>Click OK to save the changes.</li>
1092: </ol>
1093: <p>- To restart the add-on module from the command line, type:</p>
1094: <pre><tt># svcadm restart hal</tt></pre>
1095: </li>
1096: <li>Disable the snmp service.<pre># svcadm disable snmp</pre></li>
1097: <li>Re-enable the snmp service.<pre># svcadm enable snmp</pre></li>
1098: </ol>
1099: </li>
1100: 
1101: 
1102: <li>
1103: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=2900"> #
1104: 2900</a> <a name="2900">Firefox Crashes in Build 95</a></h4>
1105: <h5>Description</h5>
1106: <p>Firefox dumps core in NV build 95 due to Flash Player bug. Flash
1107: plug-in v9.0 r124 has a bug that causes Firefox to crash. <u>This issue
1108: has been fixed in the flash plug-in v 9.0 r125.</u></p>
1109: <p>Note - This affects <u>only</u> users of Flash Player v9.0 r124 and
1110: below. </p>
1111: <h5>Workaround</h5>
1112: <ol>
1113: <li>
1114: <p> Start Firefox. </p>
1115: </li>
1116: <li>
1117: <p> From the Menu bar, click on Tools -&gt; Add-ons -&gt; Plugins. </p>
1118: </li>
1119: <li>
1120: <p> Right click on Shockwave Flash and choose the Disable option to
1121: disable the plug-in.</p>
1122: </li>
1123: <li>
1124: <p>Manually install the updated version from the following URL: <a
1125: href="http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-%0A%0A4">http://www.adobe.com/products/flashplayer/productinfo/instructions/#section-4</a>
1126: </p>
1127: </li>
1128: </ol>
1129: </li>
1130: 
1131: 
1132: <li>
1133: <a name="gentextid-1235"></a>
1134: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=5543">#
1135: 5543</a><a name="5543"> Tracker Does Not Index the Home Directory by
1136: Default </a></h4>
1137: <a name="gentextid-1237"></a>
1138: <h5>Description</h5>
1139: <p>When you start Tracker, the home directory is not indexed by
1140: default. </p>
1141: <a name="gentextid-1242"></a>
1142: <h5>Workaround</h5>
1143: <p>Use the following procedure:</p>
1144: <ol>
1145: <li>
1146: <p>Go to System-&gt;Preferences.</p>
1147: </li>
1148: <li>Choose File Indexing to start tracker-preferences.</li>
1149: <li>
1150: <p>Check the Index and watch my home directory checkbox in the
1151: ’Files’ tab.</p>
1152: </li>
1153: <li>
1154: <p>Click OK.</p>
1155: </li>
1156: <li>
1157: <p>A dialog box appears prompting that data must be reindexed.</p>
1158: </li>
1159: <li><p>Click the Reindex button to reindex data.</p>
1160: </li>
1161: </ol>
1162: For more information, see the FAQs at the <a
1163: href="http://opensolaris.org/os/project/jds/tasks/MetaTracker/">Tracker
1164: community page</a>.
1165: </li>
1166: 
1167: 
1168: <li>
1169: <a name="gentextid-1235"></a>
1170: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=5544">#
1171: 5544</a><a name="5544"> Tracker Cannot Search Evolution Emails</a></h4>
1172: <a name="gentextid-1237"></a>
1173: <h5>Description</h5>
1174: <p>When you start Tracker, you cannot search for Evolution emails.</p>
1175: <a name="gentextid-1242"></a>
1176: <h5>Workaround</h5>
1177: <p>None.</p>
1178: <a name="gentextid-1385"></a>
1179: </li>
1180: 
1181: 
1182: <li>
1183: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8748">#8748</a>
1184: <a name="8748"> Windows Are Maximized on All Screens in the Twinview or Xinerama Mode</a></h4>
1185: 
1186: <a name="gentextid-1237"></a><h5>Description</h5>
1187: 
1188: 
1189: <p>When you maximize a window in the twinview or xinerama mode, the window fills all the screens instead of being maximized on the current screen only.</p>
1190: 
1191: 
1192: <a name="gentextid-1242"></a><h5>Workaround</h5>
1193: <p>None.</p>
1194: 
1195: </li>
1196: 
1197: 
1198: 
1199: <li>
1200: <h4><a
1201: href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6742850">#
1202: 6742850</a><a name="6742850"> CJK Characters Do Not Display Correctly
1203: in the Java Application Environment</a></h4>
1204: <a name="gentextid-1387"></a>
1205: <h5>Description</h5>
1206: <p>Chinese, Japanese, and Korean characters do not display correctly on
1207: Java technology-based applications.</p>
1208: <a name="gentextid-1391"></a>
1209: <h5>Workaround</h5>
1210: <p>Enable the antialiasing settings manually. Use one of the following
1211: commands:</p>
1212: <ul>
1213: <li>
1214: <pre><tt>java -Dawt.useSystemAAFontSettings=on</tt></pre>
1215: </li>
1216: <li>
1217: <pre><tt>env _JAVA_OPTIONS=-Dawt.useSystemAAFontSettings=on java</tt></pre>
1218: </li>
1219: </ul>
1220: <p>For more information about turning on the antialiasing settings,
1221: refer to <a
1222: href="http://java.sun.com/products/java-media/2D/reference/faqs/index.html#Q_How_can_I_specify_the_text_ant">
1223: Java 2D API FAQs.</a></p>
1224: </ul>
1225: 
1226: 
1227: 
1228: 
1229: <br>
1230: <br>
1231: <a name="gentextid-1093"></a>
1232: <h2><a name="hardware"></a>Hardware-Related Bugs</h2>
1233: <p>This section describes hardware-related issues that apply to the
1234: OpenSolaris 2009.06 OS.</p>
1235: <ul>
1236: 
1237: <li>
1238: <a name="gentextid-1235"></a><h4><a href="http://bugs.opensolaris.org/view_bug.do?bug_id=6658667">#6658667</a><a name="6658667"> MAC Address Is Reversed in Some mcp61-based Machines</a></h4>
1239: 
1240: <a name="gentextid-1237"></a><h5>Description</h5>
1241: 
1242: <p>The nge driver is obtaining the ethernet address with the bytes in the reverse order from the hardware.</p>
1243: 
1244: <a name="gentextid-1242"></a><h5>Workaround</h5>
1245: <p>Uncomment the last line of the nge.conf configuration file which is located in <tt>/kernel/drv/</tt>. Reboot the machine.</p>
1246: </li>
1247: 
1248: </ul>
1249: 
1250: <br>
1251: <br>
1252: <a name="gentextid-1093"></a>
1253: <h2><a name="locale"></a>Localization Bugs</h2>
1254: <p>This section describes localization issues that apply to the
1255: OpenSolaris 2009.06 OS.</p>
1256: </li>
1257: 
1258: <ul>
1259: 
1260: <li>
1261: <a name="gentextid-1235"></a>
1262: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=5473">#
1263: 5473</a><a name="5473"> en_US/es_ES/fr_FR/de_DE UTF-8 Locales Might Not
1264: be Installed by <tt>pkg image-update</tt></a></h4>
1265: <a name="gentextid-1237"></a>
1266: <h5>Description</h5>
1267: <p>The following locales will not be installed if your system is
1268: earlier than the OpenSolaris 2008.11 release and if the <tt>slim_install</tt>
1269: cluster is uninstalled before you upgrade your system to the
1270: OpenSolaris 2009.06 release using the <tt>pkg image-update</tt>
1271: command:
1272: </p>
1273: <ul>
1274: <li>
1275: <p>en_US.UTF-8</p>
1276: </li>
1277: <li>
1278: <p>es_ES.UTF-8</p>
1279: </li>
1280: <li>
1281: <p>fr_FR.UTF-8</p>
1282: </li>
1283: <li>
1284: <p>de_DE.UTF-8</p>
1285: </li>
1286: </ul>
1287: <a name="gentextid-1242"></a>
1288: <h5>Workaround</h5>
1289: <p>Install the missing locale packages. Execute the following commands:</p>
1290: <ol>
1291: <li>
1292: <p>If your current <i>LANG</i> variable is any one of the locales
1293: listed above:</p>
1294: <pre>$ export LANG=C</pre>
1295: </li>
1296: <li>
1297: <pre>$ pfexec pkg install SUNWlang-enUS SUNWlang-frFR SUNWlang-esES SUNWlang-deDE </pre>
1298: </li>
1299: </ol>
1300: </li>
1301: 
1302: 
1303: <li>
1304: <a name="gentextid-1235"></a>
1305: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8880">#
1306: 8880</a><a name="8880"> Input Method Preference Editor Help Fails to
1307: Load</a></h4>
1308: <a name="gentextid-1237"></a>
1309: <h5>Description</h5>
1310: <p><tt>iiim-properties</tt>(1) help fails to load with the XML parser error in some locales.</p>
1311: <a name="gentextid-1242"></a>
1312: <h5>Workaround</h5>
1313: <ol>
1314: <li>
1315: <p>Install <tt>SUNWgnome-xml</tt> from <tt>pkg.opensolaris.org</tt>.</p>
1316: <pre>$ pfexec pkg install SUNWgnome-xml</pre>
1317: </li>
1318: <li>
1319: <p>Manually execute the following script. </p>
1320: <pre>$ pfexec /usr/share/sgml/docbook/docbook-catalog-install.sh</pre>
1321: </li>
1322: </ol>
1323: </li>
1324: 
1325: </ul>
1326: 
1327: 
1328: <br>
1329: <br>
1330: <h2><a name="eos"></a>End-of-Software Support Statements<br>
1331: </h2>
1332: <p>The following features might not be supported in a future release of
1333: the OpenSolaris software.
1334: </p>
1335: 
1336: <ul><li>
1337: 
1338: <h4><a name="xorg"></a><tt>xorgcfg</tt> and <tt>xorgconfig</tt>
1339: Utilities</h4>
1340: The <tt>xorg</tt>(1) server does not require an <tt>xorg.conf</tt>(4) file in many cases,
1341: and will autoconfigure itself if one is not present. If the default
1342: configuration does not meet your needs, you may use one of these
1343: alternative methods to generate an <tt>xorg.conf</tt> file for customization:
1344: <ul>
1345: <li><tt>/usr/X11/bin/Xorg -configure</tt>, when the server is not already
1346: running will provide a sample configuration file for the currently
1347: detected hardware in the system. </li>
1348: <li>When Xorg is started without a configuration file, the <tt>xorg.conf</tt>
1349: data it generates automatically is logged in <tt>/var/log/Xorg.0.log</tt> and
1350: may be copied to an <tt>xorg.conf</tt> file for customization. </li>
1351: <li>Users of NVidia graphics devices may use the provided
1352: <tt>nvidia-settings</tt>(1) and <tt>nvidia-xconfig</tt>(1) utilities to generate or
1353: update device-specific configurations. </li>
1354: <li>Users of Sun graphics devices for the SPARC platform may use the
1355: <tt>fbconfig</tt>(1) utility to generate or update device-specific
1356: configurations.</li></li>
1357: </ul>
1358: 
1359: </ul>
1360: 
1361: 
1362: <br>
1363: <br>
1364: <h2><a name="troubleinfo"></a>Additional Installation Troubleshooting
1365: Information</h2>
1366: <p>This section provides troubleshooting resources for the OpenSolaris 2009.06 OS.
1367: </p>
1368: 
1369: 
1370: <ul>
1371: <li>For general troubleshooting information, see the <a
1372: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/troubleshooting.html">Getting
1373: Started Guide.</a></li>
1374: <li>For troubleshooting while installing the OpenSolaris release on
1375: your system, see <a
1376: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/tsboot.html">Tips
1377: on
1378: Troubleshooting an OpenSolaris Startup</a> and <a
1379: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/login.html">Troubleshooting
1380: Login and User Account
1381: Issues</a>.</li>
1382: <li>For troubleshooting while installing the OpenSolaris release on
1383: multiple client systems, see <a
1384: href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/trouble.html">Troubleshooting
1385: and FAQs for the Automated Installer.</a></li>
1386: <li>For troubleshooting while creating custom OpenSolaris images, see
1387: <a
1388: href="http://dlc.sun.com/osol/docs/content/2009.06/DistroConst/trouble.html">Troubleshooting
1389: for the Distribution
1390: Constructor.</a></li>
1391: </ul>
OpenSolaris

Top Menu

Wiki code for x86 : OpenSolaris 2009.06 Release Notes

Search

Collectives

Community Group

Project

User Group

Subsites

Project indiana Pages
