Solaris Express 12/05 Issues

The following issues apply to the Solaris Express 12/05 release.

x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card

If your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps:

1. Log in to a command-line session.

   • If you are using the GNOME Display Manager, follow these steps:

     1. Log in to a session as superuser.

     2. At the prompt, type svcadm disable application/gdm2-login.

     3. Log in again as superuser.

   • If you are using dtlogin, follow these steps:

     1. In the dtlogin window, click Options and select Command Line Login.

     2. Log in as superuser.

2. Create a new xorg.conf file.

   # /usr/X11/bin/Xorg -configure

   The command creates the file xorg.conf.new in the root (/) directory.

3. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

   # cp /xorg.conf.new /etc/X11/xorg.conf

4. Modify the configurations in the file by using the following sample configurations:

   • Add a new monitor section.

     Section "Monitor" Identifier "monitor_dummy" ModelName "dummy" HorizSync 10-200 VertRefresh 20-90 EndSection

   • Add a new device section.

     Section "Device" BoardName "dummy" Driver "dummy" Identifier "device_dummy" VendorName "dummy" videoram 10000 EndSection

     ---

     Note –

     You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8

     ---

   • Add a new screen section.

     Section "Screen" DefaultDepth 24 SubSection "Display" Depth 24 Modes "1280x1024" EndSubSection Device "device_dummy" Identifier "screen_dummy" Monitor "monitor_dummy" EndSection

     You might need to adjust the resolution value for your particular system setup.

5. Look for the following line under the ServerLayout section:

   Screen 0 "Screen0" 0 0

6. Insert the following line below the line in the previous step:

   Screen 1 "screen_dummy" RightOf "Screen0"

   This new line defines Screen1, a second dummy screen that is notionally to the right of Screen0, the physical and primary screen.

7. Save the changes.

8. Reboot the system from the appropriate command-line session:

   • If you are using GDM, perform the following:

     1. Type svcadm enable application/gdm2-login.

     2. Reboot the system.

   • If you are using dtlogin, reboot the system and log in.

9. Start the Gnopernicus screen reader.

10. Change the Startup Mode to Magnifier.

11. Click Preferences, then select Magnifier.

12. Click Add/Modify.

13. Assign the following values for Magnifier preferences:

    • For Source: 0.1

    • For Zoomer Placement:

      • Left and Top: 0

      • Bottom and Right: maximum

14. Click Apply.

    Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.

x86: Problems Configuring USB Mouse Device as Extension Device for Use With GNOME On-Screen Keyboard

You cannot set up a USB mouse device as an extension device with the GNOME On-Screen Keyboard (GOK). The configuration fails when you are setting up the USB mouse device while using a PS2 mouse device as the core pointer. To properly set up the USB mouse, follow these steps.

1. Log in as superuser.

2. While the USB mouse device is unplugged, type the following in a terminal window:

   # ls -l /dev/usb/hid*

3. Connect the USB mouse and type the previous command again.

4. Record the path of the USB mouse that is displayed on the screen.

5. Log in to a command-line session.

   • If you are using the GNOME Display Manager, follow these steps:

     1. Log in to a session as superuser.

     2. At the prompt, type svcadm disable application/gdm2-login.

     3. Log in again as superuser.

   • If you are using dtlogin, follow these steps:

     1. In the dtlogin window, click Options and select Command Line Login.

     2. Log in as superuser.

6. Create a new xorg.conf file.

   # /usr/X11/bin/Xorg -configure

   The command creates the file xorg.conf.new in the root (/) directory.

7. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

   # cp /xorg.conf.new /etc/X11/xorg.conf

8. Modify the configurations in the file:

   • In the ServerLayout section, add an input device for Mouse1 after the line InputDevice "Mouse0" "CorePointer". See the following example:

     InputDevice "Mouse0" "CorePointer" InputDevice "Mouse1"

   • In the InputDevice section that contains the line Identifier "Mouse0", apply the following changes:

     • Change Option "Device" "/dev/mouse" to Option "Device" "/dev/kdmouse"

     • Change Option "Protocol" "auto" to Option "Protocol" "VUID"

     • Add the following new Option:

       Option "StreamsModule" "vuid3ps2"

     After you have applied the changes, the section should appear similar to the following example:

     Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "VUID" Option "Device" "/dev/kdmouse" Option "StreamsModule" "vuid3ps2" EndSection

   • Create a new InputDevice section after the preceding InputDevice section:

     Section "InputDevice" Identifier "Mouse1" Driver "mouse" Option "Device" "/dev/usb/hid1" EndSection

     ---

     Note –

     /dev/usb/hid1 is an example path for the USB mouse. Use the path in Step 4 to replace /dev/usb/hid1.

     ---

9. Save the file and exit.

10. Reboot the system from the appropriate command-line session:

    • If you are using GDM, perform the following:

      1. Type svcadm enable application/gdm2-login.

      2. Reboot the system.

    • If you are using dtlogin, reboot the system.

11. Log in to the accessible UI user's account.

12. Enable Assistive Technology Support by clicking Launch Menu => Preferences => Accessibility => Assistive Technology Support.

13. Log out of the system then log in to the accessible UI user's account again.

14. Open a terminal window and type the following command:

    % /usr/sfw/bin/gok --select-action=switch1

15. In the GOK window, click GOK and select Preferences.

16. If necessary, set up GOK to the accessible UI user's needs. Otherwise, to accept the current setup, click Apply then click OK in the GOK Preferences window.

17. Exit GOK and then restart it by clicking Launch Menu => Applications => Accessibility => On-Screen Keyboard. The following warning message might be displayed:

    The device you are using to control GOK is also controlling the system pointer.

18. Click OK.

19. Exit GOK and then repeat steps 14-17.

    The warning message is no longer displayed.

File System Creation Might Fail on Small Slices (6346510)

Creating a UFS file system with the newfs command might fail under the following conditions:

• The size of the slice is small, approximately less than 4 Mbytes.

• The size of the disk exceeds 8 Gbytes.

The error is caused by the large-size requirement of the file system for metadata. The following warning message is displayed:

Warning: inode blocks/cyl group (295) >= data blocks (294) in last
     cylinder group. This implies 4712 sector(s) cannot be allocated.
/dev/rdsk/c0t0d0s6:     0 sectors in 0 cylinders of 48 tracks, 128 sectors
         0.0MB in 0 cyl groups (13 c/g, 39.00MB/g, 18624 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
#

Workaround: As superuser, perform one of the following workarounds:

• Workaround 1: Specify the number of tracks when you use the newfs command. Follow these steps.

  1. Use the format command to find out the number of tracks to assign. For example:

     # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 SUN18G 7506 alt 2 hd 19 sec 248 /pci@1f,4000/scsi@3/sd@0,0 Specify disk (enter its number):

     In the example, the number of tracks is 19.

  2. Assign the number to the file system that you create with the newfs command. For example:

     # newfs -v -t 19 /dev/dsk/c0t0d0s6 newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y mkfs -F ufs /dev/rdsk/c0t0d0s6 4712 -1 19 8192 1024 16 10 167 2048 t 0 -1 8 128 n mkfs: bad value for nsect: -1 must be between 1 and 32768 mkfs: nsect reset to default 32 Warning: 152 sector(s) in last cylinder unallocated /dev/rdsk/c0t0d0s6: 4712 sectors in 8 cylinders of 19 tracks, 32 sectors 2.3MB in 1 cyl groups (16 c/g, 4.75MB/g, 2304 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, #

• Workaround 2: Specify the number of bytes per inode (nbpi) in the newfs command to reduce the inode density in the file system. For example:

  # newfs -i 4096 /dev/dsk/c0t0d0s6 newfs: construct a new file system /dev/rdsk/c0t0d0s6: (y/n)? y Warning: 1432 sector(s) in last cylinder unallocated /dev/rdsk/c0t0d0s6: 4712 sectors in 1 cylinders of 48 tracks, 128 sectors 2.3MB in 1 cyl groups (16 c/g, 48.00MB/g, 11648 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, #

SPARC: Problems Configuring Preferences With the GNOME On-Screen Keyboard (6329929)

Software problems affect the use of extended devices such as a second mouse device or a USB head tracker with the GNOME On-Screen Keyboard (GOK). Consequently, the user preferences Dwell Selection and Direct Selection cannot be set by using GOK. Instead, you need to set these user preferences by using a physical keyboard and mouse device.

Workaround: After you have set the system to use an extended device, perform the following procedures in sequence. First, set GOK to ensure that the core pointer is controlled by the primary mouse device. Other extended devices are then reserved for use by AT applications. Follow these steps when starting GOK for the first time:

1. Start GOK.

2. In the window where Sticky Keys have been activated, press Enter.

3. In the window that prompts you to use core pointer mode, use the arrow keys to highlight Cancel, then press Enter.

4. To set user preferences, click GOK and select Preferences.

5. Configure Dwell Selection or Direct Selection.

   • To configure Dwell Selection, follow these steps:

     1. Click the Access Methods tab.

     2. Choose Dwell Selection from the Method drop-down menu.

     3. Click the Actions tab and perform the following:

        • Choose Dwell from the Name drop-down menu.

        • Check that Activate on Dwell is selected for Behavior.

        • Check that Other input device is selected for Event Source.

     4. Click Apply.

     5. In the Actions tab, perform the following:

        • Choose Mouse Pointer from the Name drop-down menu.

        • Check that Activate on Enter is selected for Behavior.

     6. Click Apply, then click OK.

     7. Exit the GOK window.

     8. Log out and log in again.

   • To configure Direct Selection, follow these steps:

     1. Click the Access Methods tab.

     2. Choose Direct Selection from the Method drop-down menu.

     3. From the Activate drop-down menu, choose Switch1 to use mouse button 1 on the second mouse.

     4. Click Apply, then click OK.

     5. Exit the GOK window.

     6. Log out and log in again.

SPARC: Error Messages Displayed During Dynamic Reconfiguration (6312424)

During dynamic reconfiguration (DR), error messages might be displayed. The messages are displayed if you perform DR while input and output operations are active on devices that are in the DR path. After the messages are displayed, the input and output operations are retried and eventually succeed. The following is a sample that is displayed:

Jul 28 12:23:19 qame10-a scsi: [ID 107833 kern.warning] WARNING:
/ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056fa13,0 (ssd6):
Jul 28 12:23:19 qame10-a 	transport rejected fatal error
Jul 28 12:22:08 qame10-a scsi: [ID 107833 kern.warning] WARNING:
/ssm@0,0/pci@19,700000/SUNW,qlc@2,1/fp@0,0/ssd@w2100000c5056f9a7,0 (ssd36):
Jul 28 12:22:08 qame10-a 	SCSI transport failed: reason 'timeout':
retrying command

Workaround: None. Ignore the error messages.

Full-Screen Magnification and Keyboard Accessibility Features Not Working (6273030)

On your Java DS, you cannot set up the following:

• Full-screen magnification

• Keyboard accessibility features

Workaround: Perform the following steps:

1. Open the /etc/X11/gdm/gdm.conf file.

2. Depending on your system's platform, perform the following:

   • On SPARC based systems:

     1. Look for the line in the file that begins as follows:

        command=/usr/openwin/bin/Xsun

     2. Append the following modification to the line:

        +kb +accessx -dev framebuffer1 -dev framebuffer2

        For example:

        +kb +accessx -dev /dev/fbs/pfb1 -dev /dev/fbs/pfb0

   • On x86 based systems:

     1. Look for the line in the file that begins as follows:

        command=/usr/X11R6/bin/Xorg

     2. Append the following modification to the line:

        +kb +accessx

Error Messages Displayed by pkgchk After You Remove Patches for Zones (6267966)

The patchadd and patchrm commands work improperly in non-global zones with inherited file systems. Consequently, in those zones, the pkgchk command might generate error messages about packages under the following circumstances:

1. In the global zone, you apply patches for the Solaris 10 zone system by using the patchadd command.

2. You use the patchrm command to remove patches that you just recently applied.

3. In a non-global zone with inherited file systems, you check with the pkgchk command for information about a package in any of the removed patches.

The following sample message is displayed when the pkgchk command is used on SUNWcsu under the circumstances previously listed.

# pkgchk SUNWcsu
ERROR: /usr/lib/inet/certdb
   modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
   file size <36012> expected <42152> actual
   file cksum <37098> expected <19747> actual
ERROR: /usr/lib/inet/certlocal
   modtime <04/26/05 10:55:26 PM> expected <01/23/05 01:48:24 AM> actual
   file size <44348> expected <84636> actual

Workaround: None. The errors are harmless. Ignore the error messages.

Devices Not Immediately Available in Fabric Zones in a Storage Area Network (5077933)

When a fabric zone in a storage area network (SAN) is created dynamically, that zone's devices might be unavailable at the host side. If you use the command luxadm -e dump_map to display data for such devices or host bus adapters, an error message is displayed. See the following example:

# luxadm -e dump_map /dev/cfg/c5

Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type

ERROR: Unable to retrieve target port details (QLogic Corp-2312-3)ERROR

Listing the status of all the attachment points yields information similar to the following example. In this example, the fabric devices include a tape drive, but no device is indicated in c5.

# cfgadm -al

A-_ID         Type         Receptacle   Occupant     Condition 
: 
:
c5            fc-fabric    connected    unconfigured unknown
usb0/1        unknown      empty        unconfigured ok
:
:

Workaround: After configuring the fabric-connected devices, reinitialize the link to the devices by using the luxadm -e forcelip command. For the previous example, you would type the following:

# luxadm -e forcelip /dev/cfg/c5