Mouse in Solaris 10

I have a 2 Way Manual Monitor / Keyboard / Mouse Switch Box which is connected to a Solaris 10 box & a Windows box. Since I installed Solaris 10 beta 69 on the box whenever I switch to an existing Gnome session using the switch box, the mouse no longer responds, the cursor just sits there. The keyboard is fine however. In order to get the cursor to respond I have to restart the x server with Ctrk+Alt+Bkspace, which is very irritating if I have multiple sesssions open. I did not encounter this issue with earlier builds of Solaris 9/10. This problem persists with Java Desktop in the FCS version of Solaris 10 also.
I would be grateful if anyone could advise me on a possible solution to this minor but very irritating issue.
Cheers,
Conor

That's bad luck. I tried that combination on my kvm and I couldn't get it to work. Fortunately it also has a USB port and that's how I was able to make it just removing the USB to PS/2 converter. I guess that you don't have a USB port to try in your KVM, right?

Similar Messages

No mouse on Solaris 10 with Parallels Desktop

Hi,
I just got done installing Solaris 10 on my MacBook Pro through Parallels. Almost everything installed ok, but then I found out that my mouse wouldn't work on the login screen. I logged in via the keyboard, and my mouse still wouldn't work on the desktop. Does anyone have any ideas why this might be happening? A lot of people have had this problem, as I've seen in other forums, but no one has supplied an answer yet. I would really, really like to start using the OS I spent so long configuring.
Thanks in advance, to whomever helps me fix this.

By accident, I found out that the graphics settings are remembered apparently only if a plug-and-play monitor is present (that reports its properties to the graphics adapter).
Also, during installation, be sure to watch the screen at all times. The "kdmconfig" program is apparently run also during installation. There's a 4-second window (quite at the beginning of the installation) to view the graphics properties as detected by the installer. As soon as you see this screen, hit the SPACE key to stop the timer, then verify the settings if they match your monitor and graphics adapter type. If you have the manuals of these, it's easy to figure out if the settings are appropriate. Hit ESC to start kdmconfig, it'll go right into the XSun configuration (which is used ONLY by the installer with my version of Solaris 10). The installer automatically creates a XOrg configuration and switches to XOrg after reboot (if all went well).
After successful installation of Solaris 10 (when the graphical subsystem is working), you can run "xorgconfig" (in the X binary directory) to create a "xorg.conf" file that you can place in "/etc/X11/" directory. I'm not sure if the file is actually parsed, but you can edit it to change settings if necessary.
(BTW, it would be a good idea if "kdmconfig" would allow users to enter their own maximum/minimum/fixed horizontal and vertical frequencies, edit the mode table and set +/- hsync/vsync and interlace flags, and edit a monitor setting detected automatically. I was close to hair-pulling a couple of times. Also, the installer doesn't seem to save changes to the monitor setting.)

Why keyboard and mouse right click not working in Solaris and Linux?

Hi all,
I have two problems:
1) I am working on AWT/Swing application and its working fine in window enviornment,but while running on solaris and linux mouse right-click option window not poping up.
2) Ctrl+c,Ctrl+v,Home and End keyboard key are not working in solaris and linux OS for same application.
Pls provide me some solution for these problem.
-Dinesh

Hi Nik,
Thanks for reply. I found some solution for the above problem.
For mouse right click there was problem in my source code.I have not implemented the mousePressed() method
In case of keyboard Home, End and arrow key working fine after exporting AWTUSE_TYPE4_PATCH=false; in solaris and linux
But still Ctrl-c and Ctrl-v not working.
I am using JDK1.5.0_07+Eclipse IDE 3.1
-Dinesh

I've been working on this for hours... Solaris works but mouse won't move

Edit: I should go ahead and say that I've looked at EVERY tutorial and guide and post I could find all over google, for literally hours. If you know how to fix this, I'm begging you to help me.
I have a Dell Dimension 8200, 256 MB RAM, Nvidia Geforce3 Ti 200 video card. The settings that appear when I press the "enter" button on the moniter say 640X480 with H.F.: 31.53 KHz and V.F.: 60.09 Hz.
For the keyboard and mouse:
Microsoft Wireless Multimedia Keyboard 1.1 ( Model 1014 ), Microsoft Standard Wireless Optical Mouse. Both of which wirelessly connect to the computer through the Microsoft Wireless Optical Desktop Receiver 2.1, which is simply plugged into the computer into the first USB slot.
My keyboard and mouse came from the same box, so they should both work...but only one does. Both worked on Windows XP, without installing any extra drivers, so it is not a hardware issue.
I'm using Xorg. Xsun graphics won't work for me--they come up as green and black scattered text. I ran the xorgconfig and xorg.conf was automatically placed in /etc/X11/. So, I assume that was done correctly... I chose Auto for Mouse Detection, the default mouse driver /dev/mouse/, Generic English 104-key for the keyboard, no for 3-button-emulation, no for special settings, yes for card selection ( I chose #19 Nvidia, #350 Nvidia Geforce will not work. ), #3 for Moniter selection, 640x800 for all options, and 16 bit I believe for all options.
I then rebooted, and the GUI worked fine and the keyboard worked fine. I logged in and got to the desktop, where I was prompted with some windows. The mouse pointer graphic was on the screen, but I couldn't get the mouse to work. I moved the mouse ( hardware ) back and forth repeatedly, despite my efforts the pointer simply stayed at the center of the screen.
It's almost humorous, right before I can read the keyboard shortcuts for Solaris manual while navigating the subchapters with the tab button and selecting them with the enter button( it was on the first layer of the windows that popped up so I could see it without needing to click on it ), the Solaris Registration window pops up a minute or two afterwards blocking out the other windows. I can navigate with the tab button in this window as well, yet the enter key does not have the authority to hit the buttons. My only option is to use a mouse...but wait--the mouse does not move!
SO TO THE POINT! Why won't my mouse work?!
I am completely new to UNIX based systems, so Solaris is my first one. I'm used to Windows XP, so just to let you know -- when UNIX commands are mentioned, you're speaking in gibberish to me. If I need to edit any files, please clearly explain how to do so--if I need to use a UNIX text editor etc., and what-not. Because as of now, I can only edit the files with the console.
Oh great...now this is appearing when I reboot:
WARNING - The following files in / differ from the boot archive:
/etc/path_to_inst
cannot find: /etc/devices/mdi_ib_cache: No such file or directory
The recommended action is to reboot and select "Solaris failsafe"
option from the boot menu. Then follow prompts to update the boot archive.
To continue booting at your own risk, clear the service:
# svcadm clear system/boot-archive
Jul 31 16:04:33 svc.startd[7]: svc:/system/boot-archive:default:
Method "/lib/svc/method/boot-archive" failed with exit status 95.
[ system/boot-archive:default failed fatally (see 'svcs -x' for deatails) ]
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
What is going on?
Message was edited by:
NextExit

Okay I fixed it on my own by reconfiguring Xorg with a new mouse.
If anyone else somehow encounters this problem in the future, it seems like there isn't a driver for the Microsoft Wireless Optical mouse. If there is one, it doesn't come with the basic installation. Though, the keyboard works fine. The new mouse I got was a PS/2 Optical three-button mouse. It's pretty much your generic computer mouse.

Logitech MX900 Mouse & Solaris 10 x86 results in "Postattach failed for..."

This USB-Mouse will not work with Solaris 10. I have the bluetooth-set Logitech DiNovo
keyboard and MX900 mouse. As seen in the following logfile, the keyboard is recognized and
the device is created, but the mouse fails. So i have to use my old dusty ps/2 mouse
with this nice keyboard as a workaround.
dmesg-output start:
Feb 10 20:56:35 HAL9000 usba: [ID 349649 kern.info] General Purpose
USB Hub
Feb 10 20:56:35 HAL9000 genunix: [ID 936769 kern.info] hubd0 is
/pci@0,0/pci1043,80a6@1d/hub@1
Feb 10 20:56:35 HAL9000 genunix: [ID 408114 kern.info]
/pci@0,0/pci1043,80a6@1d/hub@1 (hubd0) online
Feb 10 20:56:36 HAL9000 usba: [ID 912658 kern.info] USB 1.10 device
(usb46d,c704) operating at low speed (USB 1.x) on USB 1.10 external hub:
device@1, usb_mid0 at bus address 3
Feb 10 20:56:36 HAL9000 usba: [ID 349649 kern.info] Logitech USB
Receiver 06D263
Feb 10 20:56:36 HAL9000 genunix: [ID 936769 kern.info] usb_mid0 is
/pci@0,0/pci1043,80a6@1d/hub@1/device@1
Feb 10 20:56:36 HAL9000 genunix: [ID 408114 kern.info]
/pci@0,0/pci1043,80a6@1d/hub@1/device@1 (usb_mid0) online
Feb 10 20:56:36 HAL9000 usba: [ID 912658 kern.info] USB 1.10 interface
(usbif46d,c704.config1.0) operating at low speed (USB 1.x) on USB 1.10
external hub: keyboard@0, hid0 at bus address 3
Feb 10 20:56:36 HAL9000 usba: [ID 349649 kern.info] Logitech USB
Receiver 06D263
Feb 10 20:56:36 HAL9000 genunix: [ID 936769 kern.info] hid0 is
/pci@0,0/pci1043,80a6@1d/hub@1/device@1/keyboard@0
Feb 10 20:56:36 HAL9000 genunix: [ID 408114 kern.info]
/pci@0,0/pci1043,80a6@1d/hub@1/device@1/keyboard@0 (hid0) online
Feb 10 20:56:36 HAL9000 usba: [ID 912658 kern.info] USB 1.10 interface
(usbif46d,c704.config1.1) operating at low speed (USB 1.x) on USB 1.10
external hub: mouse@1, hid1 at bus address 3
Feb 10 20:56:36 HAL9000 usba: [ID 349649 kern.info] Logitech USB
Receiver 06D263
Feb 10 20:56:36 HAL9000 genunix: [ID 936769 kern.info] hid1 is
/pci@0,0/pci1043,80a6@1d/hub@1/device@1/mouse@1
Feb 10 20:56:36 HAL9000 genunix: [ID 667643 kern.warning] WARNING:
Postattach failed for hid1
dmesg-output end
The "Postattach..." message appears 4 times while booting. Disabling
or enabling legacy usb in bios has no effect.
My hardware: P4 Northwood 3GHz, Asus P4C800E deluxe, 1024MB RAM,
Creative Audigy2, GeForce 6800GT.
Any ideas?
Bye,
Peter.

thanks for your reply! this is the (long) output:
-bash-3.00# echo '::usba_debug_buf' | mdb -k
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
hid0: hid_pm_busy_component failed: 0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsen
se: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x0 count = 0x0
s2u0: scsa2usb_handle_scsi_cmd_sub_class: opcode = 0x3 count = 0x14
ehci0: ehci_check_for_short_xfer: residue=2 direction=0x100
ehci0: ehci_check_for_short_xfer: requested data=20 received data=18
s2u0: cdb: 3 rqsense: 70 0 2 0 0 0 0 10 0 0
0 0 3a 0 0 0 0 0 0 0
s2u0: total=0x2 cmd_xfercount=0x14 residue=0x0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
hid0: hid_pm_busy_component failed: 0
>>>>
-bash-3.00#
I hope this will help
Bye,
Peter.

Solaris 8 SPARC Install- No mouse

Greetings all,
I recently acquired and heavily upgraded a Sparc 5 (170MHz Fujitsu TurboSparc) that I intend to run headlessly in a server closet, primarily on an experimental basis (the rest of our network is BSD/Linux/NT) to gain familiarity with true AT&T-spec UNIX on SPARC hardware with our limited budget (we are high-school students, after all). Although I have run Solaris 8 on x86 hardware (horrid, slow, unstable), the installation on SPARC has been fraught with annoyances such as bad magic number disklabel errors (remedied by creating a junk label under OpenBSD) and now, the lack of an accessible MouseKeys feature (I am installing on the console with a beat-up $2 Sun keyboard). I looked at some sun mice at a computer warehouse but they were trashed and I don't want useless junk in my closet (already have enough of it- pa-risc workstations and linksys POS routers, anyone?). Anyway, what I want to do is just get a quick-and-dirty install done with no mouse so that I can run w\the machine headlessly and export the window manager to a Linux workstation or NT pc with Exceed, and occasionally use a serial console on tty a to do low-level administrative tasks.
Thanks guys and girls, and sorry about the overlong post.
-Anna
System in question is:
170MHz SparcStation 5
128M Ram
cgsix framebuffer
24x panasonic SCSI cdrom
2x4.5g IBM SCA SCSI HDDs (why the #%^&# did they use SCA?!)
Slimline floppy
Weird wide SCSI+10/100 hme NIC sbus card
ScriptKiddiez Tabulating Devices Club (SKTDC)
"Your net will be pwned by us"

Hi,
I am now trying to install Solaris to my other machine... and hoping it will work. This is a K6-2 PC with 192MB RAM and 2 x 8GB harddisks.
The first disk is occupied by Trustix and Slackware (Both are Linux), and I have the entire second dirve for Solaris. Then when I boot from DCA, my machine will keep rebooting itself. IF I boot from CD, it will say cannot find drive for installing Solaris. I have used LBA/CHS/Normal mode for my harddisk - none of them work. Any idea?
Please help.
Thanks.
Jason

Optical wheel mouse (USB) on Solaris 8

After following the instruction given in the "Solaris for Intel X86 FAQ" to install XFree86 4.0.2, my Microsoft WheelMouse Optical (on a USB port) doesn't work at all. Furthermore, after adding the CDE fonts in "/usr/openwin/lib/fonts/F3bitmaps/" to XF86Config, the fonts that appear on the CDE login screen look like those bitmap figures that are stretched like craps. What should I do to make my mouse work and how can I configure the CDE so that I see the original fonts that originally comes with SUN? Please advice.

I have the same problem with my mouse. First I installed Solaris 8 - the mouse worked just fine. Then I installed Xfree86 drivers and after reconfiguring and rebooting my system my mouse doesn't work at all. I use XF86Config utility to configure the new X server. At the beginning it asks you about your mouse, so I choose "Microsoft compatible" or "Microsoft IntelliMouse" - it doesn't work. It also asks to point to the mouse driver but I'm not sure what to choose so I use the default /dev/mouse. Please advise.

What can be done to enable multiple usb "mouse" buttons in Solaris 10 ?

My usb multimedia keyboard is recognized as a "combined" usb device.
Two /dev/usb/hidx are created , one with usb keyboard driver attached, the other with the usb mouse driver attached.
Events are generated for the scroll wheel on the keyboard, but not for the cca. 30 extra buttons.
Is there a way to enable multiple buttons support for the "mouse" device ?
The OS is Solaris 10 x86 u3

I don't know how ZAxis... can make those buttons work.
Pressing those keys don't generate any event in xev.
xmodmap -pp shows a maximum of 24 buttons which I cannot map to anything.
On linux there are some drivers and applications one can use to map the keys.
On Solaris, I don't know.

How to change mouse & graphics settings on Solaris 10?

I have Solaris 10 on x86. Before under Solaris 9, I used the "kdmconfig" command to change the mouse and graphics card settings.
What is the command to do this under Solaris 10, x86? Thanks.

serendipity1276,
If you want to use Xorg in a console as root (su -) type /usr/X11/bin/xorgconfig This will walk you thru setting up X, and create a /etc/X11/xorg.conf file. After completing the setup, log out and log back in. Your new settings should take effect. One interesting thing of note concerning mouse setup. If you're using a usb mouse, you should select "auto", otherwise if you select "imps2" for example, you're X server will not start.
hope that helps,
Dave S.
Edited for spelling

Installing solaris 9 without mouse?

Hello. I have an old ultrasparc U2 kit with dual 333MHz processor. When I obtain this kit it has Linux installed. There is also a sun mouse that looks square and has 3 buttons, but the mouse is very very old (probably more then 7 years old) and extremely difficlut to use, thus I use a new serial mouse and though away the sun mouse.
Later I decide to install solaris 10, failed to start (reason: OBP version too low) I try to install solaris 9. After the first install CD finished, a small 'solaris' system is said to be installed on hdd and system rebooted to go on installation. After reboot, CDE start and the box ask my hostname, and I cannot go on any more.
Because I don't have mouse, I cannot click 'Next'. I can jump to the textfield (by TAB) where I can enter hostname, and I can never jump out of textfield. Press TAB, Enter, space... none of them works. It seems CDE is not like typical Gnome or Windows that you could switch focus by press tab repeatedly.
If there is no way to click 'Next', then I would have to pick up Linux again, which is a trouble for me (for lack of good JRE and Flash player). It's very difficult for me to buy another sun mouse. Any suggestions?

Now I got a bit further. I upgraded OBP by using solaris 9 software CD1, without mouse. Now I have OBP that is compatible with solaris 10
I begin to install solaris 10, the same result: I cannot use mouse to move focus to the first dialog about what language I prefer to use.
it's soo much trouble to work with ultra-sparc ----- every thing are non-standard...

API for Solaris 8 Mouse Events

Hi
I am looking for a Solaris 8 API so I can listen to Mouse moved events, although the mouse cursor is not over my java application window.
Any ideas?

i've seen java 1.5 (i think) has a new class to get mouse coords on screen, but i don't have java 1.5 so i can't tell exactly where to look

Solaris - USB - Mouse

I've got some troubles using USB Mouse on my fresh installed Solaris 10. Since it was installed I can't use my Mouse and I've nothing but console to use, what makes me frustrated in the long run :)
please tell me what to do to make my USB Mouse fully working, really don't know what to configure or sth...
thanks

Which release of Solaris 10 did you install? If you have Update 4 or Update 5 you are likely hitting bug 6494635 which causes some types of USB mice to stop working. This bug is already fixed in OpenSolaris and will probably be fixed in Update 6 or possibly a patch before Update 6 is released. If you have a service contract you can open a support case to request an interim relief patch to get the fix before the official patch is released for Solaris 10. Another workaround would be to install Solaris 10 Update 3 or an older release.
Information on troubleshooting USB devices is in the USB FAQ:
http://www.sun.com/io_technologies/usb/USB-Faq.html

No cursor in Solaris 10

When I boot into Solaris 10 the screen doesn't display a mouse cursor.
Eric

What kind of mouse do you have?
Maybe should you to configure your mouse with xorgconfig.

Solaris 8 installation problem on an Intel base PC

I'm quite new with Solaris. I got stuck in Solaris 8 installation just at almost the very beginning. After booting up the system from floppy and conituing pressing F2 and selecting booting from CD, I got an error message like:
cannot mount on pci@0; 0/pci-ide@7; 1/ide01/sd@0; 0:a
panic[cpu0]thread=FEC17440 vfs:mountroot
then, the system reboots itself again and again every time it reaches this point. I guess it's a problem with my CD-ROM. But the problem persists even if I change CD-ROM or move CD-ROM from secondary master to primary slave, etc. I also tried to change harddisk, but did no good to the problem. Is there any experienced users who could provide me with some solutions?
I'm using a system with: Pentium 133, 32 MB Ram, 4GB HDD, 3C905TX, ATI Rage II PCI, Matshita CR-587 CD-ROM, Serial mouse and so on. I also tried another system with: P III 450, Asus P3BF, 192MB Ram, Pioneer DVD-ROM, same HDD, and so on. The problem was still there with the latter system. However, I successfully installed Solaris 7 with the latter system before. Why can't it work with Solaris 8?
Thanks a lot for the help.

I've been having the exact same problems on a PowerEdge 500SC. I have managed to get Solaris up and running on the machine, however. I booted the DCA from the floppy disk and installed from the CD-ROM. When the DCA is ready to scan for devices I use the "Specific Scan" option to tell it to look for specific devices. I tell it to scan for all devices in the listing and in doing so the DCA finds ISA-based IDE controllers. After it provides a listing of the devices it found I use the "Device Tasks" option and the "View/Edit Devices" menu item then delete the Bus Mastering IDE controller device. Once the screen comes up to ask for a boot device, the drives will show up as on the ISA controllers.
I have to go through this process every time I boot the machine but I am able to make the system run at least.
I haven't figured out the ACPI problem, yet.
Regards,
Doug

Solaris 8 on Ultra 2 Enterprise installation problem...

I've a Sun Ultra 2 Enterprise with dual 200 Mhz UltraSPARC I and I tried to install Solaris 8, I download the binaries from Sun site and I burnt the CDs. Insert them in the CDROM drive, I type "boot cdrom", the installation started and it started also the grafical interface, the mouse doesn't work (the cursor still in the center of the screen) and appear a Console windows that asks if Solaris should use the slice c0t0d0s1 for swap, but the keybord (I use a type 5C keyboard and mouse) don't write, so I can't type "yes", but STOP+A works and on OPB I can write.
In the end, on the grafical interface of installation mouse doesn't work and I can't write (works only STOP, arrows, ecc...)
Thanks, Paolo.

Well, to install the box you could type
boot cdrom - install w
that will give you the textbased install GUI if you are booting from Solaris CD 1/2 . You might have to get a working mouse later, but this will at least install the OS for you.

Mouse in Solaris 10

Similar Messages

Maybe you are looking for