If you are looking for a video teaching how to replace the ball top of a Mad Catz Street Fighter IV FightStick Tournament Edition look no further. You’ll need a Sanwa LB-30-N Joystick Bat Top and Sanwa Joystick Adapter. I bought my parts from Lizard Lick.
To replace the ball top for a bat top, you will need to remove all the hex screws and open the top of your FightStick. On the bottom of the joystick, put a knife or a flat screwdriver and loose the ball top.
Watch the video around 4m10s to see what’s the procedure looks like.
Fujitsu made some SPARC machines sold under the brand PRIMEPOWER. It runs Solaris but to see the hardware information you need to use some specific tools that Fujitsu developed.
PLEASE READ THE DOCUMENTATION BEFORE USING THIS UTILITY
This utility updates the driver configuration parameters
on an live system. Extreme care MUST be taken to insure
that the specified parameters are correct for this system.
Failure to do so may render this system unusable, and/or
panic the system.
This utility utilizes the devfsadm utility, which depending on
the system and the number of devices, may take some time to
complete.
Do you wish to continue (y/n)? y
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: starting execution
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: utility verson is: 1.01
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: driver version: 4.18
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: os level is: 9
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: system call checks done
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: Found qla2300 driver ioctl device path at: ‘/devices/pci@1e,600000/SUNW,qlc@2:devctl’
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: buffer allocated and populated
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with /usr/bin/pkill call
Dec 16 14:50:47 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: calling driver ioctl
Dec 16 14:50:48 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: ioctl OK — status is: 0; detail status is 0
Dec 16 14:50:48 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with driver call
Dec 16 14:50:48 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: starting /usr/sbin/devfsadm call
Dec 16 14:51:15 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with /usr/sbin/devfsadm call
Dec 16 14:51:15 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: starting /usr/sbin/update_drv call
Dec 16 14:51:25 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished with /usr/sbin/update_drv call
Dec 16 14:51:25 /opt/QLogic_Corporation/drvutil/qla2300/qlreconfig: finished
Check if there is any data synchronization running between the System Controllers. The File Propagation State must be set as active and there must not show any file in Active File or Queued Files.
e20k-sc0:sms-svc> showdatasync
File Propagation State: ACTIVE
Active File: -
Queued Files: 0
Each system controller must not have any status different from Good to prevent the failover. The failover must be active.
e20k-sc0:sms-svc> showfailover -v
SC Failover Status: ACTIVE
Status of Shared Memory:
HASRAM (CSB at CS0): …………………………………Good
HASRAM (CSB at CS1): …………………………………Good
Status of e20k-sc0:
Role: …………………………………MAIN
SMS Daemons: …………………………………Good
System Clock: …………………………………Good
Private I2 Network: …………………………………Good
Private HASRAM Network: …………………………………Good
Public Network:
Group “C1″: …………………………………..Up
eri0: …………………………………..Up
eri3: …………………………………..Up
Logical IP Addr. – C1:…………………………………..Up
System Memory: ………………………………….4.9%
Disk Status:
/: ………………………………….3.6%
Console Bus Status:
EXB at EX0: …………………………………Good
EXB at EX1: …………………………………Good
EXB at EX2: …………………………………Good
EXB at EX3: …………………………………Good
EXB at EX4: …………………………………Good
EXB at EX5: …………………………………Good
EXB at EX6: …………………………………Good
EXB at EX8: …………………………………Good
EXB at EX9: …………………………………Good
EXB at EX10: …………………………………Good
EXB at EX11: …………………………………Good
EXB at EX12: …………………………………Good
EXB at EX13: …………………………………Good
EXB at EX14: …………………………………Good
EXB at EX15: …………………………………Good
EXB at EX16: …………………………………Good
EXB at EX17: …………………………………Good
Status of e20k-sc1:
Role: ………………………………..SPARE
SMS Daemons: …………………………………Good
System Clock: …………………………………Good
Private I2 Network: …………………………………Good
Private HASRAM Network: …………………………………Good
Public Network:
Group “C1″: …………………………………..Up
eri0: …………………………………..Up
eri3: …………………………………..Up
Logical IP Addr. – C1:……………………………..Inactive
System Memory: ………………………………….4.6%
Disk Status:
/: ………………………………….3.5%
Console Bus Status:
EXB at EX0: …………………………………Good
EXB at EX1: …………………………………Good
EXB at EX2: …………………………………Good
EXB at EX3: …………………………………Good
EXB at EX4: …………………………………Good
EXB at EX5: …………………………………Good
EXB at EX6: …………………………………Good
EXB at EX8: …………………………………Good
EXB at EX9: …………………………………Good
EXB at EX10: …………………………………Good
EXB at EX11: …………………………………Good
EXB at EX12: …………………………………Good
EXB at EX13: …………………………………Good
EXB at EX14: …………………………………Good
EXB at EX15: …………………………………Good
EXB at EX16: …………………………………Good
EXB at EX17: …………………………………Good
You run setfailover force to perform the failover. If there is a problem on the spare clock input, it can cause a domain stop (it is going to power off all the domains)
e20k-sc0:sms-svc> setfailover force
Forcing failover. Do you want to continue (yes/no)? yes
The spare clock input on some boards might be bad. Forcing a failover now is likely to cause the affected domains to domain stop (Dstop).
Do you want to continue (yes/no)? yes
Checking service status
e20k-sc0:sms-svc> showfailover -r
SPARE
When you manually failover, the automatic failover is disabled
According to the website, it had drivers for Windows XP and Windows Vista but no support for Windows 7. I solved this problem by installing a beta driver available at the SteelSeries blog. Other people reported success right-clicking the driver installer and selecting to execute in Windows Vista combatibility mode.
The third Supercomputer according to the Top 500 List is getting a CPU upgrade by Cray. The AMD Quad-Core processors are being replaced by Six-Core processors without having to replace any board.
Summary:
Adapter at hardware path 0/2/1/0 : Fibre Channel driver has gone into
non-participating mode
Description of Error:
lbolt value: 3207
The Fibre Channel Driver has gone into non-participating mode
Frame Manager Status Register = 0x200002ff
Probable Cause / Recommended Action:
A cable or hardware problem exists. This can also be caused due
to the Tachyon TL adapter changing its AL_PA across a LIP.
Do the following:
1. Verify that the fiber optic cable is functional and securely
attached to the Fibre Channel Mass Storage Adapter.
2. After checking the cabling, execute a loopback test using
fcmsutil.
Command syntax is as follows:
/opt/fcms/bin/fcmsutil <device_file> lb plm
If the problem persists after verifying fiber optic cabling,
replace the adapter
Additional Event Data:
System IP Address…: 10.122.100.24
Event Id…………: 0x4a6874a300000000
Monitor Version…..: B.01.00
Event Class………: I/O
Client Configuration File………..:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version…: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4a68739100000000
Additional System Data:
System Model Number………….: 9000/800/rp4440
OS Version………………….: B.11.11
EMS Version…………………: A.04.20
STM Version…………………: A.49.00
Latest information on this event: http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#23
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
Driver Status Code………………: 0×00000017
Length of Logged Hardware Status….: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000003 00000C87 00000001 00000001 200002FF 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E 63
Checking the device file.
root@hp-ux:/ # ioscan -fnC fc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/2/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter /dev/td0
fc 1 0/6/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter /dev/td1
I tried to pass td1 as argument but it needed the full path.
Emerson Takahashi