Wiki code for SPARC : OpenSolaris 2009.06 Release Notes

Hide Line numbers
1: <h2> Release Notes for the SPARC: OpenSolaris 2009.06 Release</h2>
2: 
3: 
4:  This page lists the Release Notes for the **SPARC: 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>.
5: 
6: Refer to the <a href="http://hub.opensolaris.org/bin/view/Project+indiana/x86-2">Release Notes for the x86: OpenSolaris 2009.06 release</a>. 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>.
7: 
8: 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>
9: 
10: <table border="1">
11: <tr>
12: <td>
13: <h3>CONTENTS</h3>
14: <ol>
15: 
16: <li><a href="#install">
17: <h4>Installation Bugs</h4>
18: </a> </li>
19: 
20: <ul>
21: 
22: <li><p><a href="#6616">6616 - <tt>platform/sun4u/dscp:default</tt> Service Failure Warnings Might be Displayed in sun4v Machines.</a> </p></li
23: 
24: <li><p><a href="#7218">7218 - Convert Existing <tt>installadm</tt> Services.</a> </p></li>
25: 
26: <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>
27: 
28: <li>
29: <p><a href="#8661">8661 - Automated Installer Fails to Continue With Installation if Slices from the Previous Configuration Exist.</a> </p>
30: </li>
31: 
32: <li>
33: <p><a href="#8773">8773 - <tt>installadm create-service</tt>
34: Followed Quickly by <tt>installadm delete-service</tt> Causes <tt>installadm</tt> to Hang.</a> </p>
35: </li>
36: 
37: <li>
38: <p><a href="#8884">8884 - Incorrect Backslash in Automated Installer Document Example.</a> </p>
39: </li>
40: 
41: <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>
42: 
43: <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>
44: 
45: <!--<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>-->
46: 
47: </ul>
48: 
49: 
50: <li><a href="#packaging">
51: <h4>Packaging Bugs</h4>
52: </a> </li>
53: 
54: <ul><li><p><a href="#7836">7836 - Warnings Are Displayed  While Using <tt>pkg image-update</tt>.</a> </p></li></ul>
55: 
56: 
57: 
58: <li><a href="#hardware">
59: <h4>Hardware-Related Bugs</h4>
60: </a> </li>
61: 
62: <ul><li><p><a href="#6831186">6831186 - Sun Ultra 45 Workstation With XVR-300 Graphics Adapter Crashes When starting X Server.</a> </p></li>
63: 
64: <li><p><a href="#6831559">6831559 - KFB and EFB Graphics Drivers have Initialization Issues with LCD Monitors.</a> </p></li>
65: 
66: <li><p><a href="#6835217">6835217 - EFB Driver Shows Graphic Artefacts Even Under Supported Resolutions.</a> </p></li>
67: 
68: <li><p><a href="#6836558">6836558 - Window Display Fails to Return After Display Power Management.</a> </p></li>
69: 
70: 
71: <li><p><a href="#6836612">6836612 - GNOME Monitor Resolution Applet Locks Out User.</a> </p></li>
72: 
73: <li><p><a href="#6837629">6837629 - Xorg Fails With Fatal Error.</a> </p></li>
74: 
75: <li><p><a href="#6838784">6838784 - EFB XVR-300 Ignores Resolution Set by <tt>fbconfig</tt> on Sun CRT Monitors.</a> </p></li>
76: 
77: <li><p><a href="#6838786">6838786 - Xorg Receives Hardware Cursor Error While Initializing With EFB.</a> </p></li>
78: 
79: <li><p><a href="#6840893">6840893 - Some Resolution Settings Produce an Incorrect Narrow Display Width on the LCD Monitor on EFB and NFB Drivers.</a> </p></li>
80: 
81: <li><p><a href="#6841967">6841967 - EFB with LCD Monitor Might Cause Powercycling of the System.</a> </p></li>
82: 
83: <li><p><a href="#6842468">6842468 - EFB Console Is All Black on the Sun Ultra 45 Workstation.</a> </p></li>
84: 
85: </ul>
86: 
87: <li><a href="#locale">
88: <h4>Localization Bugs<br>
89: </h4>
90: </a> </li>
91: 
92: <ul>
93: 
94: <li>
95: <p><a href="#8880">8880 - Input Method Preference Editor Help
96: Fails to Load.</a></p>
97: </li>
98: 
99: </ul>
100: 
101: 
102: <li><a href="#eos">
103: <h4>End-of-Software
104: Support
105: Statements</h4>
106: </a> </li>
107: 
108: <ul>
109: <li>
110: <p><a href="#xorg"><tt>xorgcfg</tt> and <tt>xorgconfig</tt>
111: Utilities.</a> </p>
112: </li>
113: 
114: </ul>
115: 
116: <li><a href="#troubleinfo">
117: <h4>Additional Installation Troubleshooting Information</h4>
118: </a> </li><br>
119: </ol>
120: 
121: </tr>
122: </table>
123: <br>
124: <br>
125: 
126: 
127: 
128: 
129: <a name="gentextid-1093"></a>
130: <h2><a name="install"></a>Installation Bugs</h2>
131: <p>This section describes installation issues that apply to the
132: OpenSolaris 2009.06 OS.</p>
133: 
134: 
135: <ul>
136: 
137: <li>
138: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=6616">#6616</a>
139: <a name="6616"> <tt>platform/sun4u/dscp:default</tt> Service Failure Warnings Might be Displayed in sun4v Machines</a></h4>
140: 
141: <a name="gentextid-1237"></a><h5>Description</h5>
142: 
143: <p>On some SPARC platforms, service failure warnings are generated during an Automated Install session. A warning similar to the following is displayed.</p>
144: <pre>Feb 19 16:07:43 svc.startd\[7\]: svc:/platform/sun4u/dscp:default: Method
145: "/lib/svc/method/svc-dscp start" failed with exit status 96.
146: Feb 19 16:07:43 svc.startd\[7\]: platform/sun4u/dscp:default misconfigured:
147: transitioned to maintenance (see ’svcs -xv’ for details)
148: </pre>
149: <p>This issue occurs because architecture specific services are not enabled correctly. These service failure warnings are benign and install succeeds.</p>
150: 
151: <a name="gentextid-1242"></a><h5>Workaround</h5>
152: <p>The warning messages can be ignored.</p>
153: 
154: </li>
155: 
156: <li>
157: <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>
158: 
159: <a name="gentextid-1237"></a><h5>Description</h5>
160: 
161: <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>
162: <a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=7218">#7218 - <tt>installadm</tt> needs to move service data into SMF</a>
163: <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>
164: 
165: <a name="gentextid-1242"></a><h5>Workaround</h5>
166: 
167: <p>Use the following procedure to convert the services created with <tt>installadm create-service</tt>.
168: <ol>
169: <li>Install the new SUNWinstalladm-tools and SUNWinstall-libs packages.</li>
170: <li>Reboot the automated install server.</li>
171: <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>
172: <li>Enable the service:
173: <pre>svcadm enable svc:/system/install/server:default</pre></li>
174: </ol>
175: <p>For more information, see the <a href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/">OpenSolaris Automated Installer Guide</a>.
176: </p>
177: </li>
178: 
179: 
180: 
181: <li>
182: <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 Lesser Than 8 GB Disk Space</a></h4>
183: 
184: <a name="gentextid-1237"></a><h5>Description</h5>
185: 
186: <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> 
187: <pre>Auto install failed</pre>
188: <p>The Automated Installation fails because it runs out of space in slice 0 of the target device.</p>
189: 
190: <a name="gentextid-1242"></a><h5>Workaround</h5>
191: <p>Choose one of the following workarounds:</p>
192: <ul>
193: <li>Create slice 0 of the target device with more than 8 GB space.</li>
194: <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:
195: <pre>&lt;ai_target_device&gt;
196:    &lt;target_device_name&gt;c0t0d0&lt;/target_device_name&gt;
197:    &lt;target_device_install_slice_number&gt;4&lt;/target_device_install_slice_number&gt;
198: &lt;/ai_target_device&gt;
199: </pre></li>
200: </ul>
201: </li>
202: 
203: 
204: 
205: <li>
206: <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>
207: 
208: <a name="gentextid-1237"></a><h5>Description</h5>
209: 
210: 
211: 
212: <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
213: installation fails. The following error message is seen in the install_log file:</p>
214: <pre>root@opensolaris:/tmp# tail -20 /tmp/install_log
215: 
216: <AI May  5 14:35:40> /tmp/ai_combined_manifest.xml is a valid manifest
217: <AI May  5 14:35:40> Auto reboot disabled
218: <AI May  5 14:53:32> Disk = c8t0d0 found on the system
219: <AI May  5 14:53:32> Disk name selected for installation is c8t0d0
220: <AI May  5 14:53:32> no manifest partition information found
221: <OM May  5 14:53:32> disk partition info not changed
222: <OM May  5 14:53:32> System reports enough physical memory for installation,
223: swap is optional
224: <OM_E May  5 14:53:32> creating slice which already exists
225: <AI May  5 14:53:32> failed to modify slice(s) specified in the manifest
226: <AI May  5 14:53:32> Auto install failed
227: </pre>
228: 
229: <a name="gentextid-1242"></a><h5>Workaround</h5>
230: 
231: <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 Installer.</p>
232: </li>
233: 
234: 
235: 
236: <li>
237: <a name="gentextid-1235"></a>
238: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8773">#8773</a><a
239: name="8773"> <tt>installadm create-service</tt> Followed Quickly by <tt>installadm
240: delete-service</tt> Causes <tt>installadm</tt> to Hang</a></h4>
241: <a name="gentextid-1237"></a>
242: <h5>Description</h5>
243: <p>If you type <tt>installadm create-service</tt> followed immediately
244: by <tt>installadm delete-service,</tt> the <tt>installadm</tt>
245: command might hang. This command hangs because the <tt>installadm</tt> smf
246: service, <tt>svc:/system/install/server:default</tt>, is not online
247: when the <tt>installadm delete-service</tt> command is executed.</p>
248: <a name="gentextid-1242"></a>
249: <h5>Workaround</h5>
250: <p>Wait for the <tt>svc:/system/install/server:default</tt> service to
251: be online. To determine whether this service is online, type <tt>svcs
252: svc:/system/install/server:default</tt> and
253: check whether the STATE is listed as online.</p>
254: </li>
255: 
256: 
257: 
258: <li>
259: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8884">#8884</a>
260: <a name="8884"> Incorrect Backslash in Automated Installer Document Example</a></h4>
261: 
262: <a name="gentextid-1237"></a><h5>Description</h5>
263: 
264: <p>The following SPARC example command in the OpenSolaris Automated Installer Guide section, <a href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/advancedsetup.html">How to Complete Server Setup (Advanced Instructions)</a>, contains an extra backslash:</p>
265: <tt># installadm create-service -n sparc1 \ -s /root/Desktop/osol-0906-111a-ai-sparc.iso /export/aiserver/osol-0906-ai-sparc </tt>
266: <p>If you type the command with the backslash, the following error message is displayed:</p>
267: <pre>The <tt>installadm</tt> SMF service (svc:/system/install/server:default) is no longer
268: online
269: because the last install service has been disabled or deleted.
270: 
271: </pre>
272: 
273: <a name="gentextid-1242"></a><h5>Workaround</h5>
274: <p>The backslash should not be used in the command. Rerun the command without the backslash.
275: 
276: </p>
277: 
278: </li>
279: 
280: <li>
281: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8961">#8961</a>
282: <a name="8961"> Specifying pkg Version Strings in the Automated Installation Manifest List of Packages causes Automated Installation to Fail</a></h4>
283: 
284: <a name="gentextid-1237"></a><h5>Description</h5>
285: 
286: <p>Automated Installation might fail if version strings for packages are specified in the Automated Installation manifest. 
287: 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>
288: <pre>Unable to install SUNW in /a
289: om_perform_install failed with error 114
290: Auto install failed</pre>
291: 
292: 
293: <a name="gentextid-1242"></a><h5>Workaround</h5>
294: <p>List the entire package first and specify version strings for the entire package only. For example:</p>
295: <pre>&lt;ai_install_packages&gt;
296:     &lt;pkg name="entire@0.5.11,5.11-0.111"/&gt;
297:     &lt;pkg name="SUNWcsd"/&gt;
298:     &lt;pkg name="SUNWcs"/&gt;
299:     &lt;pkg name="SUNWj6rtx"/&gt;
300:     &lt;pkg name="SUNWgroff"/&gt;
301:     &lt;pkg name="SUNWgcc"/&gt;
302:     &lt;pkg name="babel_install"/&gt;
303:     &lt;pkg name="xvm"/&gt;
304: &lt;/ai_install_packages></pre&gt;
305: </li>
306: 
307: 
308: <li>
309: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=9026">#9026</a>
310: <a name="9026"> VTOC Partition Size Is Not Aligned to the Cylinder Boundary on Disks Larger Than 1.96 TB</a></h4>
311: 
312: <a name="gentextid-1237"></a><h5>Description</h5>
313: 
314: <p>On disks larger than 1.96 TB, the installer creates VTOC slices which are not aligned on the cylinder boundary. 
315: The installed OpenSolaris instance will boot successfully but the <tt>format</tt>(1M) tool cannot process the VTOC configuration.
316: The tool will report that the disk does not contain a valid label.</p>
317: 
318: 
319: <a name="gentextid-1242"></a><h5>Workaround</h5>
320: <p>Use the Solaris <tt>format</tt>(1M) tools to create the required VTOC configuration outside the installer.
321: Then install into the existing slice using the Automated Installer.</p>
322: <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>
323: 
324: </li>
325: 
326: <!--<li>
327: <a name="gentextid-1001"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=9214">#9214</a>
328: <a name="9214"><tt>installadm create-service</tt> Does Not Automatically Create <tt>/var/ai/image-server/logs</tt> Directory</a></h4>
329: 
330: <a name="gentextid-1002"></a><h5>Description</h5>
331: 
332: <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>
333: 
334: 
335: <a name="gentextid-1003"></a><h5>Workaround</h5>
336: <p>You can manually create the <tt>/var/ai/image-server/logs</tt> directory by running the following command:</p>
337: 
338: <p><tt>pfexec mkdir -p /var/ai/image-server/logs</tt></p>
339: 
340: <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>
341: 
342: </li>-->
343: 
344: 
345: </ul>
346: </li>
347: 
348: 
349: 
350: 
351: <br>
352: <br>
353: <a name="gentextid-1093"></a>
354: <h2><a name="packaging"></a>Packaging Bugs</h2>
355: <p>This section describes IPS-related issues that apply to the
356: OpenSolaris 2009.06 OS.</p><ul>
357: 
358: <li>
359: <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>
360: 
361: <a name="gentextid-1237"></a><h5>Description</h5>
362: 
363: <p>While updating an image to build 111 or beyond, a warning message similar to the following might be displayed:</p>
364: <pre>driver (emlxs) upgrade (removal of minor perm ’* 0600 root sys’’) failed with
365: return code 252
366: command run was: /usr/sbin/update_drv -b /mnt -d -m * 0600 root sys’ emlxs
367: command output was:
368: ------------------------------------------------------------
369: No entry found for driver (emlxs) in file (/mnt/etc/minor_perm).
370: ------------------------------------------------------------
371: </pre>
372: <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>
373: 
374: <a name="gentextid-1242"></a><h5>Workaround</h5>
375: <p>The warning can be ignored.</p>
376: 
377: </li>
378: </ul>
379: 
380: 
381: 
382: 
383: <br>
384: <br>
385: <a name="gentextid-1093"></a>
386: <h2><a name="hardware"></a>Hardware-Related Bugs</h2>
387: <p>This section describes hardware-related issues that apply to the
388: OpenSolaris 2009.06 OS.</p>
389: <ul>
390: <li>
391: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8179">#6831186</a>
392: <a name="6831186"> Sun Ultra 45 Workstation With XVR-300 Graphics Adapter Crashes While starting X Server</a></h4>
393: 
394: <a name="gentextid-1237"></a><h5>Description</h5>
395: 
396: <p>Sun Ultra 45 Workstations with XVR-300 Graphics Adapter installed crash while starting the X Server. 
397: The system crashes just before the Gnome Display Manager (GDM) login page. JBUS-PCI error messages are displayed.</p>
398: 
399: <a name="gentextid-1242"></a><h5>Workaround</h5>
400: <p>None.</p>
401: </li>
402: 
403: <li>
404: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8239">#6831559</a>
405: <a name="6831559"> KFB and EFB Graphics Drivers have Initialization Issues with LCD Monitors</a></h4>
406: 
407: <a name="gentextid-1237"></a><h5>Description</h5>
408: 
409: <p>The KFB and EFB drivers have initialization issues because of the failure to retrieve EDID support data from the LCD monitor. This causes the
410: GNOME window system to hang or crash at GDM login or shortly after login. This issue is mainly seen with KFB drivers.</p>
411: 
412: <a name="gentextid-1242"></a><h5>Workaround</h5>
413: <p>Generate an <tt>/etc/X11/xorg.conf</tt> file. Perform the following steps:</p>
414: <ol>
415: <li>Disconnect the LCD monitor before you start.</li>
416: <li>On the virtual-console, type the following command:
417: <pre># fbconfig -dev efb0 -res VESA_STD_1280x1024x60 now nocheck</pre></li>
418: </ol>
419: <p>Note: For the XVR-2500 and KFB driver it is recommended that you use a SUN CRT type Monitor, Part numbers: 365-1399-01, 365-1418-01.
420: Currently LCD Monitors with KFB are facing issues, even when the resolution and <tt>xorg.conf</tt> file is pre-created with resolution set at <tt>1280x1024x60</tt>.</p>
421: 
422: <p>See also, CRs <a href="#6841967">6841967</a>, <a href="#6838784">6838784</a>, and <a href="#6831186">6831186</a>.</p>
423: 
424: </li>
425: 
426: <li>
427: <a name="gentextid-1235"></a><h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8973">#6835217</a>
428: <a name="6835217"> EFB Driver Shows Graphic Artefacts Even Under Supported Resolutions</a></h4>
429: 
430: <a name="gentextid-1237"></a><h5>Description</h5>
431: 
432: <p>The screen displays noise while moving windows and the windows have rough borders.</p>
433: 
434: <a name="gentextid-1242"></a><h5>Workaround</h5>
435: <p>None.</p>
436: 
437: </li>
438: 
439: 
440: <li>
441: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6836612">#6836612</a>
442: <a name="6836612"> GNOME Monitor Resolution Applet Locks Out User.</a></h4>
443: 
444: 
445: <a name="gentextid-1237"></a><h5>Description</h5>
446: 
447: <p>When the user clicks on System -> Preferences -> Screen Resolution, the user is locked out of the system.</p>
448: 
449: <a name="gentextid-1242"></a><h5>Workaround</h5>
450: <p>None.</p>
451: </li>
452: 
453: <li>
454: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6836558">#6836558</a>
455: <a name="6836558"> Window Display Fails to Return After Display Power Management</a></h4>
456: 
457: <a name="gentextid-1237"></a><h5>Description</h5>
458: 
459: <p>When the display power management reaches the OFF state, pressing the mouse button, or keyboard tab, or the control key does not display the window system.
460: </p>
461: <a name="gentextid-1242"></a><h5>Workaround</h5>
462: 
463: <p>Generate an <tt>/etc/X11/xorg.conf</tt> file. Perform the following procedure:</p>
464: <ol>
465: <li>Disconnect the LCD monitor before you start.</li>
466: <li>On the virtual-console, type the following command:
467: <pre># fbconfig -dev efb0 -res VESA_STD_1280x1024x60 now nocheck</pre></li>
468: <li>Reboot your system.</li>
469: </ol>
470: 
471: </li>
472: 
473: <li>
474: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6837629">#6837629</a>
475: <a name="6837629"> Xorg Fails With Fatal Error</a></h4>
476: 
477: <a name="gentextid-1237"></a><h5>Description</h5>
478: 
479: <p>Xorg Fails with a fatal error on XVR-2500 after the xhost is set. All applications and utilities close and the server crashes. 
480: This failure occurs when the XVR-2500 is connected to the SUN CRT Monitor. The following error message is seen:</p>
481: <pre>ddxDriverInit: Could not register as server</pre>
482: <p>This issue occurs when you type the following commands on the command-line:</p>
483: <pre># /usr/X11/bin/Xorg& 
484: # /usr/X11/bin/xhost + </pre>
485: <p>The error message is displayed and the driver crashes. GDM is functional when the X Server is restarted.</p>
486: 
487: <a name="gentextid-1242"></a><h5>Workaround</h5>
488: <p>None.</p>
489: 
490: </li>
491: 
492: 
493: <li>
494: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6838784">#6838784</a>
495: <a name="6838784"> EFB XVR-300 Ignores Resolution Set by <tt>fbconfig</tt> on Sun CRT Monitors</a></h4>
496: 
497: <a name="gentextid-1237"></a><h5>Description</h5>
498: 
499: <p>The resolution on Sun CRT monitors remains the same regardless of the resolution set using <tt>fbconfig</tt>.</p>
500: 
501: <a name="gentextid-1242"></a><h5>Workaround</h5>
502: <p>None.</p>
503: 
504: </li>
505: 
506: 
507: <li>
508: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6838786">#6838786</a>
509: <a name="6838786"> Xorg Receives Hardware Cursor Error While Initializing With EFB</a></h4>
510: 
511: <a name="gentextid-1237"></a><h5>Description</h5>
512: 
513: <p>The Xorg standard output displays a hardware cursor error during initialization. The following error message is displayed:
514: <pre>efb(0): Hardware cursor initialization failed</pre>
515: </p>
516: 
517: <a name="gentextid-1242"></a><h5>Workaround</h5>
518: <p>None. Xorg and GNOME are not noticeably affected by this error.</p>
519: 
520: </li>
521: 
522: 
523: <li>
524: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6840893">#6840893</a>
525: <a name="6840893"> Some Resolution Settings Produce an Incorrect Narrow Display Width on the LCD Monitor on EFB and NFB Drivers</a></h4>
526: 
527: <a name="gentextid-1237"></a><h5>Description</h5>
528: 
529: <p>The VESA_STD_800x600x75, VESA_STD_1280x1024x75, SUNW_DIG_1920x1080x60, and SUNW_DIG_1920x1200x60 resolutions cannot be set on LCD monitors. 
530: These resolutions produce an incorrect narrow width display.</p>
531: 
532: <a name="gentextid-1242"></a><h5>Workaround</h5>
533: <p>Use the <tt>1280x1024x60</tt> and <tt>1024x768x60</tt> resolution sizes.
534: </p>
535: 
536: </li>
537: 
538: 
539: 
540: <li>
541: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6841967">#6841967</a>
542: <a name="6841967"> EFB with LCD Monitor Might Cause Powercycling of the System</a></h4>
543: 
544: 
545: <a name="gentextid-1237"></a><h5>Description</h5>
546: 
547: <p>LCD Monitors that have higher than <tt>1280x1024x60</tt> preferred resolution settings might powercycle at GDM login.</p>
548: 
549: <a name="gentextid-1242"></a><h5>Workaround</h5>
550: <p>The recommended approach to the installation of a sun4v system is through the use of a service processor and virtual-console, or through ttya in the case of a sun4u system.
551: Perform the following procedure:</p>
552: <ol>
553: <li>Unplug the monitor before you begin. This enables the smooth initialization of the graphics card when the system is rebooted.</li>
554: <li>Install the system.</li>
555: <li>At the end of the installation setup procedure through the virtual-console or through ttya create an <tt>/etc/X11/xorg.conf</tt> by setting the resolution:
556: <pre># fbconfig -dev efb0 -res VESA_STD_1280x1024x60 now nocheck
557: New configuration file, /etc/X11/xorg.conf
558: Video mode has been set to "VESA_STD_1280x1024x60"</pre>
559: <li>Reconnect the monitor.</li>
560: <li>Type the following command on the virtual-console or ttya:
561: <pre># eeprom input-device=keyboard output-device=screen;</pre></li>
562: <li>Reboot the system.</li> 
563: </ol>
564: </li>  
565: 
566: 
567: <li>
568: <a name="gentextid-1235"></a><h4><a href="http://opensolaris.org/os/project/indiana/resources/relnotes/200906/sparc/#6842468">#6842468</a>
569: <a name="6842468"> EFB Console Is All Black on the Sun Ultra 45 Workstation</a></h4>
570: 
571: <a name="gentextid-1237"></a><h5>Description</h5>
572: 
573: <p>The screen is black on a Sun Ultra 45 workstation until the GDM login page is displayed.</p>
574: 
575: <a name="gentextid-1242"></a><h5>Workaround</h5>
576: <p>Telnet to ttya for installation and setup because you might be unable to install locally .</p>
577: 
578: </li>
579: 
580: 
581: </ul>
582: 
583: 
584: <br>
585: <br>
586: <a name="gentextid-1093"></a>
587: <h2><a name="locale"></a>Localization Bugs</h2>
588: <p>This section describes localization issues that apply to the
589: OpenSolaris 2009.06 OS.</p>
590: </li>
591: 
592: <ul>
593: <li>
594: <a name="gentextid-1235"></a>
595: <h4><a href="http://defect.opensolaris.org/bz/show_bug.cgi?id=8880">#
596: 8880</a><a name="8880"> Input Method Preference Editor Help Fails to
597: Load</a></h4>
598: <a name="gentextid-1237"></a>
599: <h5>Description</h5>
600: <p><tt>iiim-properties</tt>(1) help fails to load with the XML parser error in some locales.</p>
601: <a name="gentextid-1242"></a>
602: <h5>Workaround</h5>
603: <ol>
604: <li>
605: <p>Install <tt>SUNWgnome-xml</tt> from <tt>pkg.opensolaris.org</tt>.</p>
606: <pre>$ pfexec pkg install SUNWgnome-xml</pre>
607: </li>
608: <li>
609: <p>Manually execute the following script. </p>
610: <pre>$ pfexec /usr/share/sgml/docbook/docbook-catalog-install.sh</pre>
611: </li>
612: </ol>
613: </li>
614: 
615: </ul>
616: 
617: 
618: <br>
619: <br>
620: <h2><a name="eos"></a>End-of-Software Support Statements<br>
621: </h2>
622: <p>The following features might not be supported in a future release of
623: the OpenSolaris software.
624: </p>
625: 
626: <ul>
627: 
628: <li>
629: 
630: <h4><a name="xorg"></a><tt>xorgcfg</tt> and <tt>xorgconfig</tt>
631: Utilities</h4>
632: The <tt>xorg</tt>(1) server does not require an <tt>xorg.conf</tt>(4) file in many cases,
633: and will autoconfigure itself if one is not present. If the default
634: configuration does not meet your needs, you may use one of these
635: alternative methods to generate an <tt>xorg.conf</tt> file for customization:
636: <ul>
637: <li><tt>/usr/X11/bin/Xorg -configure</tt>, when the server is not already
638: running will provide a sample configuration file for the currently
639: detected hardware in the system. </li>
640: <li>When Xorg is started without a configuration file, the <tt>xorg.conf</tt>
641: data it generates automatically is logged in <tt>/var/log/Xorg.0.log</tt> and
642: may be copied to an <tt>xorg.conf</tt> file for customization. </li>
643: <li>Users of NVidia graphics devices may use the provided
644: <tt>nvidia-settings</tt>(1) and <tt>nvidia-xconfig</tt>(1) utilities to generate or
645: update device-specific configurations. </li>
646: <li>Users of Sun graphics devices for the SPARC platform may use the
647: <tt>fbconfig</tt>(1) utility to generate or update device-specific
648: configurations.</li></li>
649: </ul>
650: 
651: </ul>
652: 
653: 
654: 
655: 
656: <br>
657: <br>
658: <h2><a name="troubleinfo"></a>Additional Installation Troubleshooting
659: Information</h2>
660: <p>This section provides troubleshooting resources for the OpenSolaris 2009.06 OS.
661: </p>
662: 
663: 
664: <ul>
665: <li>For general troubleshooting information, see the <a
666: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/troubleshooting.html">Getting
667: Started Guide.</a></li>
668: <li>For troubleshooting while installing the OpenSolaris release on
669: your system, see <a
670: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/tsboot.html">Tips
671: on
672: Troubleshooting an OpenSolaris Startup</a> and <a
673: href="http://dlc.sun.com/osol/docs/content/2009.06/getstart/login.html">Troubleshooting
674: Login and User Account
675: Issues</a>.</li>
676: <li>For troubleshooting while installing the OpenSolaris release on
677: multiple client systems, see <a
678: href="http://dlc.sun.com/osol/docs/content/2009.06/AIinstall/trouble.html">Troubleshooting
679: and FAQs for the Automated Installer.</a></li>
680: <li>For troubleshooting while creating custom OpenSolaris images, see
681: <a
682: href="http://dlc.sun.com/osol/docs/content/2009.06/DistroConst/trouble.html">Troubleshooting
683: for the Distribution
684: Constructor.</a></li>
685: </ul>
OpenSolaris

Top Menu

Wiki code for SPARC : OpenSolaris 2009.06 Release Notes

Search

Collectives

Community Group

Project

User Group

Subsites

Project indiana Pages
