How to enable OCP(Intel X520/X550) iscsi/pxe/wol option rom
1.Boot up to UEFI with "bootutil" utility (EFIx64 folder)
Enable iscsi option
2.bootutil64e.efi -up=iscsi+efi -nic=1
(Yes)
If fw image exist(Overwrite)
(Yes)
Set primary port
3.bootutil64e.efi -bootenable=iscsiprimary -nic=1
4.bootutil64e.efi -bootenable=iscsisecondary -nic=2
---------------------------------------
[PXE]
bootutil64e.efi -up=pxe+efi -nic=1
-----------------------------------------
[WOL] wake on lan
bootutil64e.efi -WOLENABLE -all
2014年12月30日 星期二
2014年12月23日 星期二
How to check linux vga driver
How to check linux vga driver 2016/4/22 update
#Xorg :1 -configure
#cat /var/log/Xorg.1.log
finding LoadModule: "ast" (Do not use grep)
module version=0.99.10
ast is a vga vender, you can find video to find your vga vender then
check "module version" is your driver version
#Xorg :1 -configure
#cat /var/log/Xorg.1.log
finding LoadModule: "ast" (Do not use grep)
module version=0.99.10
ast is a vga vender, you can find video to find your vga vender then
check "module version" is your driver version
2014年12月10日 星期三
How to set root auto login RHEL 7.0 / SLES 12
How to set root auto login RHEL 7.0 / SLES 12
RHEL 7.0
Edit /etc/gdm/custom.conf to add [daemon]
add the following two lines in the [daemon]
section:
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=root
RHEL 7.0
Edit /etc/gdm/custom.conf to add [daemon]
add the following two lines in the [daemon]
section:
[daemon]
AutomaticLoginEnable=true
AutomaticLogin=root
SLES 12
Open Terminal.
Edit the /etc/sysconfig/displaymanager file.
vi /etc/sysconfig/displaymanager |
To enable the autologin, place your user name (in my case “raj”) in the DISPLAYMANAGER_AUTOLOGIN field; it will look like below.
## Type: string ## Default: # # Define the user whom should get logged in without request. If string # is empty, display standard login dialog. # DISPLAYMANAGER_AUTOLOGIN="root" |
To disable auto login, remove the username from the DISPLAYMANAGER_AUTOLOGIN field; it will look like below.
## Type: string ## Default: # # Define the user whom should get logged in without request. If string # is empty, display standard login dialog. # DISPLAYMANAGER_AUTOLOGIN="" |
2014年10月30日 星期四
How to run perfomance on Intel GPGPU(MIC) under linux
How to run perfomance on Intel GPGPU(MIC) under linux
Please setup MPSS service first
http://lisoulin.blogspot.tw/2014/10/how-to-stress-intel-gpgpumic-under-linux.html
A.Install Linpack
1.Dowload linpack package from Intel website
https://software.intel.com/en-us/articles/intel-math-kernel-library-linpack-download
2.Copy l_lpk_p_11.2.0.003 to SLES OS
3.Unzip package
#tar zxvf l_lpk_p_11.2.0.003.tgz
B.Install Intel® C++ Composer XE 2013
1.Dowload Composer XE package from Intel website
https://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-fortran-composer-xe-2013-sp1-for-linux
2.Copy l_ccompxe_2013_sp1.4.211_redist to SLES OS
3.Unzip package
#tar zxvf l_ccompxe_2013_sp1.4.211_redist.tgz
4.Install composer xe package
#cd l_ccompxe_2013_sp1.4.211_redist
#./install.sh
accept
C.Install micperf
1.Install micperf rpm
#cd /mpss-3.4.1/perf
#rpm -ivh *.rpm
2.Setup micperf
#cd /usr/src/micperf/micp-3.4.1
#./setup.py install
D.Setting environment
#export PYTHONPATH=/usr/src/micperf/micp-3.4.1
#echo $PYTHONPATH
#export MKLROOT=/linpack_11.2.0
#echo $MKLROOT
#source /root/bin/compileravars.sh intel64
E.Running Linpack
Running linpack with default parameter
#micprun -k linpack
The deafualt parameter will be
micprun -k linpack -p '--matrix_size 36864 --num_rep 3--lead_dim 36928'
The performance result is GFlops
Try to run linpack with different parameter to find out best GFlops value
#micprun -k linpack -p '--matrix_size 10000 --num_rep 3 --lead_dim 10000'
Please setup MPSS service first
http://lisoulin.blogspot.tw/2014/10/how-to-stress-intel-gpgpumic-under-linux.html
A.Install Linpack
1.Dowload linpack package from Intel website
https://software.intel.com/en-us/articles/intel-math-kernel-library-linpack-download
2.Copy l_lpk_p_11.2.0.003 to SLES OS
3.Unzip package
#tar zxvf l_lpk_p_11.2.0.003.tgz
B.Install Intel® C++ Composer XE 2013
1.Dowload Composer XE package from Intel website
https://software.intel.com/en-us/articles/redistributable-libraries-for-the-intel-c-and-fortran-composer-xe-2013-sp1-for-linux
2.Copy l_ccompxe_2013_sp1.4.211_redist to SLES OS
3.Unzip package
#tar zxvf l_ccompxe_2013_sp1.4.211_redist.tgz
4.Install composer xe package
#cd l_ccompxe_2013_sp1.4.211_redist
#./install.sh
accept
C.Install micperf
1.Install micperf rpm
#cd /mpss-3.4.1/perf
#rpm -ivh *.rpm
2.Setup micperf
#cd /usr/src/micperf/micp-3.4.1
#./setup.py install
D.Setting environment
#export PYTHONPATH=/usr/src/micperf/micp-3.4.1
#echo $PYTHONPATH
#export MKLROOT=/linpack_11.2.0
#echo $MKLROOT
#source /root/bin/compileravars.sh intel64
E.Running Linpack
Running linpack with default parameter
#micprun -k linpack
The deafualt parameter will be
micprun -k linpack -p '--matrix_size 36864 --num_rep 3--lead_dim 36928'
The performance result is GFlops
Try to run linpack with different parameter to find out best GFlops value
#micprun -k linpack -p '--matrix_size 10000 --num_rep 3 --lead_dim 10000'
2014年10月7日 星期二
How to check sata link under linux
How to check sata link under linux
#dmesg | grep -i sata | grep link
#dmesg | grep -i sata | grep link
How to text TXT under linux (Old)
How to text TXT under linux 2015/06/03 update
TXT only support in BIOS legacy mode , not support UEFI mode.
TXT only support in BIOS legacy mode , not support UEFI mode.
- Install
trousuers and trousers-devel
#rpm –ivh
trousers-devel-0.3.4-4.e16.x86_64.rpm
- Unzip
the tboot source code to a folder under root
Type the following
command:
# tar -xzvf
tboot.1.8.tar.bz2 -C /root
# cd /root/tboot-1.8/
- Browse
to the tboot source code and execute “make all”
This
compile successfully and generates a tboog.gz image which needs to be copied to
the /boot folder.
Type the following
command:
#cp /root/tboot-1.8/tboot/tboot.gz /boot/
#cp /root/tboot-1.8/tboot/tboot.syms /boot/
- Once
tboot and the Linux kernel 3.1.5 is compiled and images are generated we
should modify the menu.lst file in /boot folder. Just copy the existing boot entry and modify it like
this
a)
title
Red Hat Enterprise Linux Sever + TBOOT
b)
root
(hd0,0) --- # use what is there in your
original menu.lst
c)
kernel /tboot.gz logging=serial,vga,memory
d)
module
/vmlinuz-*.*.* root=/dev/VolGroup00/LogVol00 ro # use what is there in your original menu.lst
e)
module
/initramfs-*.*.*.img # use what is there in your
original menu.lst
1.1.1.1.2
Booting
tboot
Now reboot the system and
select the Linux with Intel® Trusted Execution technology from the boot loader.
Now your system should boot with a set of tboot messages to the Linux login
prompt.
1.1.1 R.
TXT.MeasuredLaunchEnvironment.Function
1.1.1 R.
TXT.MeasuredLaunchEnvironment.Function
logged in as root
Proceed
to the folder where tboot was extracted and compiled.
Browse
to /tboot-1.6/utils folder
Execute
the txt-stat utility in the terminal by typing “./txt-stat”<ENTER> (dump log: ./txt-stat >> *.log)
Verify
if the log mentions “Measured Launch :
TRUE”
How to change monitor resolution under linux text mode
How to change monitor resolution under linux text mode
When you modify wrong VGA resolution, then you cannot login the graph mode
Try to modify under text mode
RHEL:
Delete the file
#rm -rf .config/monitor.xml
#reboot
SLES:
#sax2
When you modify wrong VGA resolution, then you cannot login the graph mode
Try to modify under text mode
RHEL:
Delete the file
#rm -rf .config/monitor.xml
#reboot
SLES:
#sax2
How to check CPU/Memory watt by node manager
How to check CPU/Memory watt by node manager
test under linux
Check CPU watt
#ipmi-oem intelnm -h x.x.x.x -u root -p superuser get-node-manager-statistics domainid=1
Check Memory watt
#ipmi-oem intelnm -h x.x.x.x -u root -p superuser get-node-manager-statistics domainid=2
test under linux
Check CPU watt
#ipmi-oem intelnm -h x.x.x.x -u root -p superuser get-node-manager-statistics domainid=1
Check Memory watt
#ipmi-oem intelnm -h x.x.x.x -u root -p superuser get-node-manager-statistics domainid=2
How to stress Intel GPGPU(MIC) under linux
How to stress Intel GPGPU(MIC) under linux (kncptu ,knc, ptu) 2015/3/13 update
MIC card test under RHEL
Dowload latest MPSS package from Intel website
https://software.intel.com/en-us/articles/intel-manycore-platform-software-stack-mpss#lx34rel
1.Intall driver MPSS
2.#tar xvf mpss-3.2-rhel-6.0.tar
3.#yum install*.rpm
4.#modprobe mic (If you can not load mic modules, please use old mpss version , mpss 3.4 has issue)
5.#micctrl --initdefaults
8.#ssh mic0
If you cannot ssh to mic0, please use ip
#ifconfig=>check mic0 ip
#ssh x.x.x.x (mic0 ip)
9.#mkdir tmp
If system reboot automatically, please stop bmc watchdog
#service bmc-watchdog stop
If you want to retest, please go to step 7
/opt/mpss/3.4.1/sysroots/klom-mpss-linux/bin/micsmc-gui (RHEL)
This will open a graphical Linux application showing the temperature and power for the MIC cards
MIC card test under SLES
Dowload latest MPSS package from Intel website
https://software.intel.com/en-us/articles/intel-manycore-platform-software-stack-mpss#lx34rel
1.Intall driver MPSS
2.#tar xvf mpss-3.2.suse-11.3.tar
5.#micctrl --initdefaults
6.#service mpss start
7.#ssh mic0
9.#exit
10.#scp ./KncPtuGen mic0:tmp
11.#ssh mic0
12.#cd tmp
13.#./KncPtuGen -P100
MIC card test under RHEL
Dowload latest MPSS package from Intel website
https://software.intel.com/en-us/articles/intel-manycore-platform-software-stack-mpss#lx34rel
1.Intall driver MPSS
2.#tar xvf mpss-3.2-rhel-6.0.tar
3.#yum install*.rpm
4.#modprobe mic (If you can not load mic modules, please use old mpss version , mpss 3.4 has issue)
5.#micctrl --initdefaults
6.#micctrl --sshkeys=root mic0
7.#service mpss restart8.#ssh mic0
If you cannot ssh to mic0, please use ip
#ifconfig=>check mic0 ip
#ssh x.x.x.x (mic0 ip)
9.#mkdir tmp
10.#exit
11.#scp ./KncPtuGen mic0:tmp
11.#scp ./KncPtuGen mic0:tmp
13.#cd tmp
14.#./KncPtuGen -P100If system reboot automatically, please stop bmc watchdog
#service bmc-watchdog stop
If you want to retest, please go to step 7
/opt/mpss/3.4.1/sysroots/klom-mpss-linux/bin/micsmc-gui (RHEL)
This will open a graphical Linux application showing the temperature and power for the MIC cards
MIC card test under SLES
Dowload latest MPSS package from Intel website
https://software.intel.com/en-us/articles/intel-manycore-platform-software-stack-mpss#lx34rel
1.Intall driver MPSS
2.#tar xvf mpss-3.2.suse-11.3.tar
vi /etc/modprobe.d/unsupported-modules
(SLES 12=>vim /etc/modprobe.d/10-unsupported-modules)
(SLES 12=>vim /etc/modprobe.d/10-unsupported-modules)
=>allow_unsupported_modules 1
3.#zypper install *.rpm
4.#modprobe mic3.#zypper install *.rpm
5.#micctrl --initdefaults
6.#service mpss start
7.#ssh mic0
(If ssh requre password, please try
to ssh ip directly)
8.#mkdir tmp9.#exit
10.#scp ./KncPtuGen mic0:tmp
11.#ssh mic0
12.#cd tmp
13.#./KncPtuGen -P100
run ‘/opt/intel/mic/bin/micsmc-gui’ (SLES)
This will open a graphical Linux application showing the temperature and power for the MIC cards
2014年8月13日 星期三
How to check PCIe card link speed under linux
How to check PCIe card link speed under linux
#lspci -vv
(vv not w)
refer:http://unix.stackexchange.com/questions/393/how-to-check-how-many-lanes-are-used-by-the-pcie-card
#lspci -vv
(vv not w)
refer:http://unix.stackexchange.com/questions/393/how-to-check-how-many-lanes-are-used-by-the-pcie-card
RHEL6 UEFI:error 13 :invalid or unsupported executable format
RHEL6 UEFI:error 13 :invalid or unsupported executable format
After you install RHEL6 UEFI mode, you cannot enter into OS,any you see the error message
error 13 :invalid or unsupported executable format
You install the OS with tboot pacakge.
You have to re-install OS without tboot package.
Refer:http://support.lenovo.com/us/en/documents/ht075591
After you install RHEL6 UEFI mode, you cannot enter into OS,any you see the error message
error 13 :invalid or unsupported executable format
You install the OS with tboot pacakge.
You have to re-install OS without tboot package.
Refer:http://support.lenovo.com/us/en/documents/ht075591
2014年8月12日 星期二
dmar: DRHD: handling fault status reg 2
dmar: DRHD: handling fault status reg 2
When you enable vt-d ,then system cannot boot to linux OS.
When you enable vt-d ,then system cannot boot to linux OS.
You have to disable vt-d first, then modify
the grub.conf
(intel_iommu=on => off)
2014年8月1日 星期五
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Method 1:
1. mknod /dev/ipmi0 c 254 0
2. chkconfig --level 5 ipmi on
---------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------
Method 2:
[root@localhost ~]# ipmitool sdr
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
such file or directory
Get Device ID command failed
Unable to open SDR for reading
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No
such file or directory
Get Device ID command failed
Unable to open SDR for reading
First, you should try #sudo ipmitool sdr
Execute below command:
(Sudo is for Ubuntu)
[root@localhost ~]#sudo modprobe ipmi_watchdog
[root@localhost ~]#sudo modprobe ipmi_poweroff
[root@localhost ~]#sudo modprobe ipmi_devintf
[root@localhost ~]#sudo modprobe ipmi_si
[root@localhost ~]#sudo modprobe ipmi_msghandler
[root@localhost ~]# sudo ipmitool sdr
[root@localhost ~]#sudo modprobe ipmi_devintf
[root@localhost ~]#sudo modprobe ipmi_si
[root@localhost ~]#sudo modprobe ipmi_msghandler
[root@localhost ~]# sudo ipmitool sdr
2014年7月4日 星期五
How to rebuild/upgrade glibc
How to rebuild/upgrade glibc
This sample is update Glibc 2.5 to 2.7 (RHEL 5.3 x86)
Download package
ftp://ftp.gnu.org/gnu/glibc/glibc-2.7.tar.gz
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.18.tar.gz
ftp://ftp.gnu.org/gnu/glibc/glibc-linuxthreads-2.5.tar.bz2
Prepare the kernel headers
# tar zxvf linux-2.6.18.tar.gz
# cd linux-2.6.18
# make mrproper
# make menuconfig
(you don't need to actually configure anything; just accept the defaults and then exit out of menuconfig)
# make dep (ignore warning)
# mkdir -p /usr/include/linux-2.6.18
# cp -a include/linux /usr/include/linux-2.6.18/
# cp -a include/asm* /usr/include/linux-2.6.18/
Building glibc
# tar zxvf glibc-2.7.tar.gz
# cp glibc-linuxthreads-2.5.tar.bz2 /glibc-2.7
# tar jxvf /glibc-2.7/glibc-linuxthreads-2.5.tar.bz2
# mkdir /build
# cd /build
# ../glibc-2.7/configure --prefix=/usr --disable-profile --enable-add-ons \
--with-headers=/usr/include/ --libexecdir=/usr/bin
#vi config.make
add "-march=i686" after "CFLAGS = -g -O2"
# make (If you meet error while make, you need to execute "make clean", then make again)
# make install
# ls /lib/libc-*
libc-2.7.so
Rerfer:
http://www.oregontechsupport.com/articles/glibc.php
http://www.linuxsir.org/bbs/thread368805.html
This sample is update Glibc 2.5 to 2.7 (RHEL 5.3 x86)
Download package
ftp://ftp.gnu.org/gnu/glibc/glibc-2.7.tar.gz
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/linux-2.6.18.tar.gz
ftp://ftp.gnu.org/gnu/glibc/glibc-linuxthreads-2.5.tar.bz2
Prepare the kernel headers
# tar zxvf linux-2.6.18.tar.gz
# cd linux-2.6.18
# make mrproper
# make menuconfig
(you don't need to actually configure anything; just accept the defaults and then exit out of menuconfig)
# make dep (ignore warning)
# mkdir -p /usr/include/linux-2.6.18
# cp -a include/linux /usr/include/linux-2.6.18/
# cp -a include/asm* /usr/include/linux-2.6.18/
Building glibc
# tar zxvf glibc-2.7.tar.gz
# cp glibc-linuxthreads-2.5.tar.bz2 /glibc-2.7
# tar jxvf /glibc-2.7/glibc-linuxthreads-2.5.tar.bz2
# mkdir /build
# cd /build
# ../glibc-2.7/configure --prefix=/usr --disable-profile --enable-add-ons \
--with-headers=/usr/include/ --libexecdir=/usr/bin
#vi config.make
add "-march=i686" after "CFLAGS = -g -O2"
# make (If you meet error while make, you need to execute "make clean", then make again)
# make install
# ls /lib/libc-*
libc-2.7.so
Rerfer:
http://www.oregontechsupport.com/articles/glibc.php
http://www.linuxsir.org/bbs/thread368805.html
2014年7月1日 星期二
Use AMISCE tool to update BIOS configuration under linux
Use AMISCE tool to update BIOS configuration under linux
Test fucntion without change dump file
1.Copy SCELNX_64 to Linux_Flash folder
2.cd Linux_Flash
3#afulnx_64 /MAKEDRV
4.#afulnx_64 /GENDRV [Option 1] / (ex:./afulnx_64 /GENDRV 2.6.32-71.e16.x86_64 /)
[Option 1]: Specific kernel source 'KERNEL=XXXX' , #uname-r to check
5.#make
6.#SCELNX_64 /o /s nvram.txt /h Hii.db /v /q
7.Reboot to BIOS, change some BIOS configuration
8.Save,boot to linux
9.Boot to OS, cd AMI_SCE folder
10.#SCELNX_64 /i /s nvram.txt (Restore BIOS to original configuration)
11.Reboot to BIOS, check if configuration is back
--------------------------------------------------------
Dump all BIOS configuration:
# ./SCELNX_64 /o /s NVRAM.txt
-----------------------------------------------------
Change password by modify dump file
Set BIOS Administrator/User password through SCE utility:
0. Set BIOS Administrator/User password and dump nvram file(contain password) with below command
./SCELNX_64 /o /c /l list.txt /n nvram.txt /h hii.db
1. Dump nvram file(no password) with below command
./SCELNX_64 /o /c /l list.txt /n nvram.txt /h hii.db
2. Edit dumped nvram file to change "Variable Data" about AMITSESetup to set BIOS password. (see nvram.txt in step 0)
No password
Variable Name
AMITSESetup
Variable Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01
Username /password =>是 Admin / 111111 ; User / 111
Variable Name
AMITSESetup
Variable Data
6A 93 87 26 20 BA 6C 4D C7 E0 22 74 7D 07 D8 9A
33 2E 8E C1 E9 54 44 E8 9F 7B FA 0E 55 A2 B0 35
0B C9 66 5C C1 EF 1C 83 6A 93 87 26 20 BA 5D 4D
F6 E0 13 74 7D 07 D8 9A 33 2E 8E C1 E9 54 44 E8
9F 7B FA 0E 55 A2 B0 35 0B C9 66 5C C1 EF 1C 83
00
3. Update nvram file to system using following command.
./SCELNX_64 /i /l list.txt /n nvram.txt
4. Reset system and check if BIOS password is set.
Refer:
ftp://12.230.196.227/joel_drivers/BIOS%20Flash%20Utilities/Linux%20Bios%20Flash%20Procedure/UEFI/v2.37/ROMUtils_2.37/LNX/afulnx32/readme_afulnx.txt
Test fucntion without change dump file
1.Copy SCELNX_64 to Linux_Flash folder
2.cd Linux_Flash
3#afulnx_64 /MAKEDRV
4.#afulnx_64 /GENDRV [Option 1] / (ex:./afulnx_64 /GENDRV 2.6.32-71.e16.x86_64 /)
[Option 1]: Specific kernel source 'KERNEL=XXXX' , #uname-r to check
5.#make
6.#SCELNX_64 /o /s nvram.txt /h Hii.db /v /q
7.Reboot to BIOS, change some BIOS configuration
8.Save,boot to linux
9.Boot to OS, cd AMI_SCE folder
10.#SCELNX_64 /i /s nvram.txt (Restore BIOS to original configuration)
11.Reboot to BIOS, check if configuration is back
--------------------------------------------------------
Dump all BIOS configuration:
# ./SCELNX_64 /o /s NVRAM.txt
-----------------------------------------------------
Change password by modify dump file
Set BIOS Administrator/User password through SCE utility:
0. Set BIOS Administrator/User password and dump nvram file(contain password) with below command
./SCELNX_64 /o /c /l list.txt /n nvram.txt /h hii.db
1. Dump nvram file(no password) with below command
./SCELNX_64 /o /c /l list.txt /n nvram.txt /h hii.db
2. Edit dumped nvram file to change "Variable Data" about AMITSESetup to set BIOS password. (see nvram.txt in step 0)
No password
Variable Name
AMITSESetup
Variable Data
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01
Username /password =>是 Admin / 111111 ; User / 111
Variable Name
AMITSESetup
Variable Data
6A 93 87 26 20 BA 6C 4D C7 E0 22 74 7D 07 D8 9A
33 2E 8E C1 E9 54 44 E8 9F 7B FA 0E 55 A2 B0 35
0B C9 66 5C C1 EF 1C 83 6A 93 87 26 20 BA 5D 4D
F6 E0 13 74 7D 07 D8 9A 33 2E 8E C1 E9 54 44 E8
9F 7B FA 0E 55 A2 B0 35 0B C9 66 5C C1 EF 1C 83
00
3. Update nvram file to system using following command.
./SCELNX_64 /i /l list.txt /n nvram.txt
4. Reset system and check if BIOS password is set.
Refer:
ftp://12.230.196.227/joel_drivers/BIOS%20Flash%20Utilities/Linux%20Bios%20Flash%20Procedure/UEFI/v2.37/ROMUtils_2.37/LNX/afulnx32/readme_afulnx.txt
Program Broadcom 57810 MAC address under DOS
Program Broadcom 57810 MAC address under DOS
Enter DOS mode
c:\ediag -b10eng
1:>nvm cfg 1= MAC (20:1a:06:d7:3a:01)
#dev 2 (Enter)
2:>nvm cfg 1=MAC (20:1a:06:d7:3a:02)
#dev (Enter)
Verify MAC address
Enter DOS mode
c:\ediag -b10eng
1:>nvm cfg 1= MAC (20:1a:06:d7:3a:01)
#dev 2 (Enter)
2:>nvm cfg 1=MAC (20:1a:06:d7:3a:02)
#dev (Enter)
Verify MAC address
2014年6月3日 星期二
Make UID blinking by IPMI command
Make UID blinking by IPMI command
#ipmitool -H 192.168.x.x -U root -P superuser chassis identify
UID LED will blink 15 seconds
#ipmitool -H 192.168.x.x -U root -P superuser chassis identify
UID LED will blink 15 seconds
switch RHEL to "vesa" video driver
switch RHEL to "vesa" video driver
Download and install
(http://pkgs.org/centos-6/russian-fedora-free-x86_64/system-config-display-2.2-3.el6.R.x86_64.rpm.html)
system-config-display-2.2-3.el6.R.x86_64.rpm
Source package:
system-config-display-2.2-3.el6.R.src.rpm
#system-config-display --set-driver=vesa
#reboot
2014年5月19日 星期一
Intel MIC GPGPU test under RHEL 6.5 (intel xeon phi)
Intel MIC GPGPU test under RHEL 6.5 (intel xeon phi)
.Install Intel® MPSS OFED.
#yum install ofed/*.rpm
#yum install psm/*.rpm
#micinfo
#sudo micctrl -w
mps: mic0: ready
2.Start MPSS service
If you are new install
#micctrl --initdefaults
If you want to keep old configuration
# micctrl --resetdefaults
#service mpss start
mic0: online
Set MPSS service start when OS boot
#chkconfig mpss on
.Install Intel® MPSS OFED.
#yum install ofed/*.rpm
#yum install psm/*.rpm
#micinfo
#sudo micctrl -w
mps: mic0: ready
2.Start MPSS service
If you are new install
#micctrl --initdefaults
If you want to keep old configuration
# micctrl --resetdefaults
#service mpss start
mic0: online
Set MPSS service start when OS boot
#chkconfig mpss on
2014年5月8日 星期四
Linux 各種壓縮與解壓縮指令
Linux 各種壓縮與解壓縮指令
.tar (僅打包,無壓縮)
套件名稱:tar。
打包:
[ root@linux ~ ]
$ tar cvf FileName.tar DirName
解包:
[ root@linux ~ ]
$ tar xvf FileName.tar
.gz
套件名稱:gzip。
壓縮
[ root@linux ~ ]
$ gzip FileName
解壓縮1:
[ root@linux ~ ]
$ gunzip FileName.gz
解壓縮2:
[ root@linux ~ ]
$ gzip -d FileName.gz
.tar.gz
套件名稱:gzip。
壓縮:
[ root@linux ~ ]
$ tar zcvf FileName.tar.gz DirName
解壓縮:
[ root@linux ~ ]
$ tar zxvf FileName.tar.gz
bz
壓縮:unkown。
解壓縮1:
[ root@linux ~ ]
$ bzip2 -d FileName.bz
解壓縮2:
[ root@linux ~ ]
$ bunzip2 FileName.bz
.tar.bz
壓縮:unkown。
解壓縮:
[ root@linux ~ ]
$ tar jxvf FileName.tar.bz
.bz2
套件名稱:bzip2。
壓縮:
[ root@linux ~ ]
$ bzip2 -z FileName
解壓縮1:
[ root@linux ~ ]
$ bzip2 -d FileName.bz2
解壓縮2:
[ root@linux ~ ]
$ bunzip2 FileName.bz2
.tar.bz2
套件名稱:bzip2。
壓縮:
[ root@linux ~ ]
$ tar jcvf FileName.tar.bz2 DirName
解壓縮:
[ root@linux ~ ]
$ tar jxvf FileName.tar.bz2
.xz
套件名稱:xz-utils。
壓縮:
[ root@linux ~ ]
$ xz -z FileName.xz DirName
解壓縮:
[ root@linux ~ ]
$ xz -d FileName.xz
.tar.xz
套件名稱:xz-utils。
壓縮:
[ root@linux ~ ]
$ tar Jcvf FileName.tar.xz DirName
解壓縮:
[ root@linux ~ ]
$ tar Jxvf FileName.tar.xz
.Z
壓縮:compress FileName
解壓縮:
[ root@linux ~ ]
$ uncompress FileName.Z
.tar.Z
壓縮:
[ root@linux ~ ]
$ tar Zcvf FileName.tar.Z DirName
解壓縮:
[ root@linux ~ ]
$ tar Zxvf FileName.tar.Z
.tgz
套件名稱:gzip。
壓縮:
[ root@linux ~ ]
$ tar zcvf FileName.tgz FileName
解壓縮:
[ root@linux ~ ]
$ tar zxvf FileName.tgz
.tar.tgz
套件名稱:gzip。
壓縮:
[ root@linux ~ ]
$ tar zcvf FileName.tar.tgz FileName
解壓縮:
[ root@linux ~ ]
$ tar zxvf FileName.tar.tgz
.7z
套件名稱:p7zip-full。
壓縮:
[ root@linux ~ ]
$ 7z a FileName.7z FileName
使用密碼 (PASSWORD) 壓縮:
[ root@linux ~ ]
$ 7z a FileName.7z FileName -pPASSWORD
解壓縮:
[ root@linux ~ ]
$ 7z x FileName.7z
.zip
套件名稱:zip。
壓縮:
[ root@linux ~ ]
$ zip FileName.zip DirName
解壓縮:
[ root@linux ~ ]
$ unzip FileName.zip
.rar
套件名稱:rar, unrar。
壓縮:
[ root@linux ~ ]
$ rar a FileName.rar DirName
解壓縮1:
[ root@linux ~ ]
$ rar e FileName.rar
解壓縮2:
[ root@linux ~ ]
$ unrar e FileName.rar
.lha
套件名稱:lha。
壓縮:
[ root@linux ~ ]
$ lha -a FileName.lha FileName
解壓縮:
[ root@linux ~ ]
$ lha -e FileName.lha
.tar (僅打包,無壓縮)
套件名稱:tar。
打包:
[ root@linux ~ ]
$ tar cvf FileName.tar DirName
解包:
[ root@linux ~ ]
$ tar xvf FileName.tar
.gz
套件名稱:gzip。
壓縮
[ root@linux ~ ]
$ gzip FileName
解壓縮1:
[ root@linux ~ ]
$ gunzip FileName.gz
解壓縮2:
[ root@linux ~ ]
$ gzip -d FileName.gz
.tar.gz
套件名稱:gzip。
壓縮:
[ root@linux ~ ]
$ tar zcvf FileName.tar.gz DirName
解壓縮:
[ root@linux ~ ]
$ tar zxvf FileName.tar.gz
bz
壓縮:unkown。
解壓縮1:
[ root@linux ~ ]
$ bzip2 -d FileName.bz
解壓縮2:
[ root@linux ~ ]
$ bunzip2 FileName.bz
.tar.bz
壓縮:unkown。
解壓縮:
[ root@linux ~ ]
$ tar jxvf FileName.tar.bz
.bz2
套件名稱:bzip2。
壓縮:
[ root@linux ~ ]
$ bzip2 -z FileName
解壓縮1:
[ root@linux ~ ]
$ bzip2 -d FileName.bz2
解壓縮2:
[ root@linux ~ ]
$ bunzip2 FileName.bz2
.tar.bz2
套件名稱:bzip2。
壓縮:
[ root@linux ~ ]
$ tar jcvf FileName.tar.bz2 DirName
解壓縮:
[ root@linux ~ ]
$ tar jxvf FileName.tar.bz2
.xz
套件名稱:xz-utils。
壓縮:
[ root@linux ~ ]
$ xz -z FileName.xz DirName
解壓縮:
[ root@linux ~ ]
$ xz -d FileName.xz
.tar.xz
套件名稱:xz-utils。
壓縮:
[ root@linux ~ ]
$ tar Jcvf FileName.tar.xz DirName
解壓縮:
[ root@linux ~ ]
$ tar Jxvf FileName.tar.xz
.Z
壓縮:compress FileName
解壓縮:
[ root@linux ~ ]
$ uncompress FileName.Z
.tar.Z
壓縮:
[ root@linux ~ ]
$ tar Zcvf FileName.tar.Z DirName
解壓縮:
[ root@linux ~ ]
$ tar Zxvf FileName.tar.Z
.tgz
套件名稱:gzip。
壓縮:
[ root@linux ~ ]
$ tar zcvf FileName.tgz FileName
解壓縮:
[ root@linux ~ ]
$ tar zxvf FileName.tgz
.tar.tgz
套件名稱:gzip。
壓縮:
[ root@linux ~ ]
$ tar zcvf FileName.tar.tgz FileName
解壓縮:
[ root@linux ~ ]
$ tar zxvf FileName.tar.tgz
.7z
套件名稱:p7zip-full。
壓縮:
[ root@linux ~ ]
$ 7z a FileName.7z FileName
使用密碼 (PASSWORD) 壓縮:
[ root@linux ~ ]
$ 7z a FileName.7z FileName -pPASSWORD
解壓縮:
[ root@linux ~ ]
$ 7z x FileName.7z
.zip
套件名稱:zip。
壓縮:
[ root@linux ~ ]
$ zip FileName.zip DirName
解壓縮:
[ root@linux ~ ]
$ unzip FileName.zip
.rar
套件名稱:rar, unrar。
壓縮:
[ root@linux ~ ]
$ rar a FileName.rar DirName
解壓縮1:
[ root@linux ~ ]
$ rar e FileName.rar
解壓縮2:
[ root@linux ~ ]
$ unrar e FileName.rar
.lha
套件名稱:lha。
壓縮:
[ root@linux ~ ]
$ lha -a FileName.lha FileName
解壓縮:
[ root@linux ~ ]
$ lha -e FileName.lha
mellanox OFED infiniband test under RHEL 6.5
mellanox OFED infiniband test under RHEL 6.5
Download latest OFED SW
https://www.openfabrics.org/downloads/OFED/
BIOS setting of SUT:
v Disable SpeedStep/Hyper-threading/C3/C6 in BIOS CPU configuration.
The test steps are seperated to
1.Install OFED,
2. ib IP setting
3.ssh key setting
4.run script
---------------------------------------------------------------------------
1.Install OFED
#cd OFED
#chkconfig opensmd on
make sure state is Active in ibstat
Set ib ip address in SUT2
#ifconfig ib0 10.0.0.2 255.255.255.0
Disable iptables on both SUT1 and SUT2
#service iptables stop
Check SUT1 and SUT2 connect
(SUT1)# ping 10.0.0.2
3.ssh key setting
Download latest OFED SW
https://www.openfabrics.org/downloads/OFED/
BIOS setting of SUT:
v Disable SpeedStep/Hyper-threading/C3/C6 in BIOS CPU configuration.
The test steps are seperated to
1.Install OFED,
2. ib IP setting
3.ssh key setting
4.run script
---------------------------------------------------------------------------
1.Install OFED
#cd OFED
#./install.sh
From the following menu select 2 “Install OFED Software”
InfiniBand OFED Distribution Software Installation Menu
1) View OFED Installation Guide
2) Install OFED Software
3) Show Installed Software
4) Configure IPoIB Network Interface and OpenSM Server
5) Uninstall InfiniBand Software
6) Build OFED Software RPMs
Q) Exit
Select Option [1-6]:
|
From the following sub-menu select 3 “All packages (all of openib, mpi)”
Select OFED Software
1) Basic (InfiniBand modules and basic user level libraries)
2) HPC (InfiniBand modules and libraries, mpi and diagnostic tools)
3) All packages (all of openib, mpi)
4) Customize
Q) Exit
Select Option [1-4]:
|
After selecting the complete installation you will be prompted for the compiler used for compiling the 2 MPI packages included in the distribution. Accept the default of gcc when prompted.
Install complete and successfully.
2. ib IP setting
#/etc/init.d/openibd start
#service opensmd start#chkconfig opensmd on
make sure state is Active in ibstat
#ibstat
Set ib ip address in SUT1
#ifconfig ib0 10.0.0.1 255.255.255.0
Set ib ip address in SUT2
#ifconfig ib0 10.0.0.2 255.255.255.0
Disable iptables on both SUT1 and SUT2
#service iptables stop
Check SUT1 and SUT2 connect
(SUT1)# ping 10.0.0.2
3.ssh key setting
From the host 10.0.0.1 perform the following steps:
#ssh 10.0.0.2 (ssh “ip”)
At the prompt similar to the following, type yes and press Enter.
----------------------------------------------------------------------------------------------------photo
The authenticity of host 'localhost (10.0.0.2)' can't be established.
RSA key fingerprint is 23:35:92:2b:df:5b:d6:1b:6a:32:24:ee:18:d2:82:18.
Are you sure you want to continue connecting (yes/no)?
-----------------------------------------------------------------------------------------------------
Enter root password then type exit.
Generate authentication keys
cd ~/.ssh
ssh-keygen –t rsa
Continue to press enter to accept default file name and no passphrase.
-----------------------------------------------------------------------------------------------------------photo
[root@localhost ~/.ssh]# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/root/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
7a:e0:dc:a5:ec:99:0a:7a:33:4f:d6:ee:9d:5c:7d:c2 root@localhost
------------------------------------------------------------------------------------------------------------
Create the authorized_keys file for uutn1.
cat id_rsa.pub >> authorized_keys
Copy the authorized_keys file to the initiator host uutn1.
scp authorized_keys 10.0.0.2:~/.ssh/10.0.0.2.id
From the initiator host 10.0.0.2 perform the following steps.
cd ~/.ssh
cat 10.0.0.2.id >> authorized_keys
Re-do test, you have to clear the old key
Clear all existing auth-keys in SUT1 (unsvr) and SUT2 (unsvr1)
SUT1) # rm -rf ~/.ssh/*
SUT2) # rm -rf ~/.ssh/*
SUT1) # rm -rf ~/.ssh/*
SUT2) # rm -rf ~/.ssh/*
4.run script
install perftest-2.0-2.el6.x86_64.rpm
(Download from :http://mirror.centos.org/centos/6/os/x86_64/Packages/perftest-2.0-2.el6.x86_64.rpm)
#rpm -ivh perftest-2.0-2.el6.x86_64.rpm--force
1Open a new file using an editor such as vi and copy the sample script from below into the file. Save the file and use chmod to make it executable
#vim runall
chmod +x ./runall
#!/bin/sh
# trivial script to launch all server/client bandwidth and latency
# tests with ssh. Must be launched from client. Uses test defaults
# and runs both unidirectional and bidirectional bandwidth tests.
# examples: runall <servername> or runall <server_ip>
BW_TESTS="rdma_bw ib_read_bw ib_send_bw ib_write_bw"
LAT_TESTS="rdma_lat ib_read_lat ib_send_lat ib_write_lat"
OFED_BINDIR=/usr/bin
SERVER=$1
run ()
{
server=$1
shift
ssh $server $* >& /dev/null &
#give server time to start
sleep 2
$* $server
status=$?
wait
return $status
}
if [ $# -lt 1 ] ; then
echo "Usage: runall <server>"
exit 3
fi
for test in $BW_TESTS ; do
run $SERVER $OFED_BINDIR/$test
run $SERVER $OFED_BINDIR/$test -b
done
for test in $LAT_TESTS ; do
run $SERVER $OFED_BINDIR/$test
done
|
2. Run the script. If desired, you can redirect the output to a file for inclusion in the final report. A sample of the output is provided below.
./runall <server name or IP address>
Or
./runall <server name or IP address> > <output file>
local address: LID 0x05, QPN 0x830405, PSN 0xbc893c RKey 0x7a002400 VAddr 0x002aedf208f000
remote address: LID 0x04, QPN 0x810405, PSN 0xe022f6, RKey 0x12002400 VAddr 0x002b1b7d7fb000
Bandwidth peak (#0 to #989): 744.555 MB/sec
Bandwidth average: 744.527 MB/sec
Service Demand peak (#0 to #989): 4535 cycles/KB
Service Demand Avg : 4535 cycles/KB
local address: LID 0x05, QPN 0x840405, PSN 0xaf75dc RKey 0x002400 VAddr 0x002b5970ce6000
remote address: LID 0x04, QPN 0x820405, PSN 0xca1275, RKey 0x18002400 VAddr 0x002af22122a000
Bandwidth peak (#0 to #890): 1344.07 MB/sec
Bandwidth average: 1343.9 MB/sec
Service Demand peak (#0 to #890): 2512 cycles/KB
Service Demand Avg : 2512 cycles/KB
------------------------------------------------------------------
RDMA_Read BW Test
Connection type : RC
local address: LID 0x05, QPN 0x850405, PSN 0x416402 RKey 0x6002400 VAddr 0x002ab8a3128000
remote address: LID 0x04, QPN 0x830405, PSN 0x1d2d1e, RKey 0x1e002400 VAddr 0x002ad71ee91000
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec]
65536 1000 722.06 722.04
------------------------------------------------------------------
------------------------------------------------------------------
RDMA_Read Bidirectional BW Test
Connection type : RC
local address: LID 0x05, QPN 0x860405, PSN 0xb27762 RKey 0xc002400 VAddr 0x002b353f60e000
remote address: LID 0x04, QPN 0x840405, PSN 0xf4a018, RKey 0x24002400 VAddr 0x002b42dc3e2000
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec]
65536 1000 1213.91 1213.91
------------------------------------------------------------------
------------------------------------------------------------------
Send BW Test
Inline data is used up to 400 bytes message
Connection type : RC
local address: LID 0x05, QPN 0x870405, PSN 0x893f8f
remote address: LID 0x04, QPN 0x850405, PSN 0x52149e
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec]
65536 1000 743.12 743.12
------------------------------------------------------------------
------------------------------------------------------------------
Send Bidirectional BW Test
Inline data is used up to 400 bytes message
Connection type : RC
local address: LID 0x05, QPN 0x880405, PSN 0x7879ae
remote address: LID 0x04, QPN 0x860405, PSN 0xbd3577
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec]
65536 1000 1319.16 1319.16
------------------------------------------------------------------
------------------------------------------------------------------
RDMA_Write BW Test
Inline data is used up to 400 bytes message
Number of qp's running 1
Connection type : RC
Each Qp will post up to 100 messages each time
local address: LID 0x05, QPN 0x890405, PSN 0xf51a5b RKey 0x1e002400 VAddr 0x002ab514275000
remote address: LID 0x04, QPN 0x870405, PSN 0x82d78, RKey 0x36002400 VAddr 0x002b8f7954e000
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec]
65536 5000 744.72 744.72
------------------------------------------------------------------
------------------------------------------------------------------
RDMA_Write Bidirectional BW Test
Inline data is used up to 400 bytes message
Number of qp's running 1
Connection type : RC
Each Qp will post up to 100 messages each time
local address: LID 0x05, QPN 0x8a0405, PSN 0x17cc0 RKey 0x24002400 VAddr 0x002af1b8b05000
remote address: LID 0x04, QPN 0x880405, PSN 0x23d292, RKey 0x3c002400 VAddr 0x002af1a056b000
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations BW peak[MB/sec] BW average[MB/sec]
65536 5000 1345.45 1345.45
------------------------------------------------------------------
local address: LID 0x05 QPN 0x8b0405 PSN 0x61f8fa RKey 0x2a002400 VAddr 0x00000000509001
remote address: LID 0x04 QPN 0x890405 PSN 0x8879fe RKey 0x42002400 VAddr 0x00000000509001
Latency typical: 3.8045 usec
Latency best : 3.72367 usec
Latency worst : 179.276 usec
------------------------------------------------------------------
Read Req Latency Test
local address: LID 0x05 QPN 0x8c0405 PSN 0x168f09 RKey 0x30002400 VAddr 0x0000000050c080
remote address: LID 0x04 QPN 0x8a0405 PSN 0x287769 RKey 0x48002400 VAddr 0x0000000050c080
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations t_min[usec] t_max[usec] t_typical[usec]
2 1000 8.49 18.40 8.61
------------------------------------------------------------------
------------------------------------------------------------------
Send Latency Test
Inline data is used up to 400 bytes message
Connection type : RC
local address: LID 0x05 QPN 0x8d0405 PSN 0xf2d6d8
remote address: LID 0x04 QPN 0x8b0405 PSN 0x3da316
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations t_min[usec] t_max[usec] t_typical[usec]
2 1000 5.08 63.87 5.13
------------------------------------------------------------------
------------------------------------------------------------------
RDMA_Write Latency Test
Inline data is used up to 400 bytes message
Connection type : RC
local address: LID 0x05 QPN 0x8e0405 PSN 0x5c8536 RKey 0x3e002400 VAddr 0x0000000050c002
remote address: LID 0x04 QPN 0x8c0405 PSN 0xcb23fc RKey 0x56002400 VAddr 0x0000000050c002
Mtu : 2048
------------------------------------------------------------------
#bytes #iterations t_min[usec] t_max[usec] t_typical[usec]
2 1000 3.70 24.04 3.79
------------------------------------------------------------------
|
訂閱:
文章 (Atom)
-
[Office] 自從您上次存檔後檔案 (filename.xls) 可能已由另一位使用者變更 當您嘗試將 Microsoft Excel 活頁簿儲存到網路伺服器時,如果該伺服器正在執行例如 Services for Macintosh 的中繼服務,或是在開啟活頁簿時出現...
-
Use AMISCE tool to update BIOS configuration under linux Test fucntion without change dump file 1.Copy SCELNX_64 to Linux_Flash folder 2...
-
I would like to thank you for all your support during the past years and hope that you will continue to extend the same to my replacement, ...