Malin's notes: Difference between revisions

From MalinWiKi
Jump to navigation Jump to search
No edit summary
No edit summary
Line 36: Line 36:
=Crossflash Dell PERC H200 from ir to it-mode=
=Crossflash Dell PERC H200 from ir to it-mode=


The short answer is. I followed this guide:
==The short answer==
I slightly followed this guide:
 
https://blog.michael.kuron-germany.de/2014/11/crossflashing-dell-perc-h200-to-lsi-9211-8i/comment-page-1/
https://blog.michael.kuron-germany.de/2014/11/crossflashing-dell-perc-h200-to-lsi-9211-8i/comment-page-1/


Line 63: Line 65:
2. Download this zip https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/Installer_P20_for_UEFI.zip
2. Download this zip https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/Installer_P20_for_UEFI.zip


3. Extract sas2flash.efi from
3. Extract sas2flash.efi from Installer_P20_for_UEFI/sas2flash_efi_ebc_rel/
 
4. Place this to extracted files in the P20 folder
 
===Step 3 download uefi shell===
1. Download an uefi shell: [https://wiki.archlinux.org/index.php/Unified_Extensible_Firmware_Interface#Obtaining_UEFI_Shell x86_64 UEFI SHELL] I choosed version 1 as it worked for the person in the guide [https://github.com/tianocore/edk2/raw/UDK2018/EdkShellBinPkg/FullShell/X64/Shell_Full.efi Direct download link]
 
2. Extract Shell_Full.efi to the root of the memory stick. I had to rename it to Shellx64.efi to use it with my motherboard, asus P8H67_M_EVO. Check with you motherboard vendor to determine how to use efi-shell
 
===Step 4 flashing===
 
1. boot computer to efi shell
 
2. If not present with a list with devices, type map -b
 
2. On my computer the memory stick is called fs0 so I typed fs0: to change prompt to the memory stick
 
3. cd P07
 
4. sas2flash -listall will show the controller. If not, check if it is installed to a pci-e port
 
5. sas2flash.efi -c 0 -list will show controller details and take a note of the sas address number
 
6. sas2flash.efi -o -e 6 will erase the old firmware and boot rom
 
7. sas2flash.efi -o -f 6GBPSAS.FW writes the dell 6gbs firmware
 
8. sas2flash.efi -o -f 2118it.bin writes the P07 firmware
 
9. Then I rebooted
 
10. boot into efi again
 
11. cd P20
 
12. sas2flash.efi -o -f 2118it.bin writes the P20 firmware
 
===Notes===
Directly copied from the source, step number changed to fit my tutorial:
 
1. Step 6 showed “Erasing Flash Region” and then after a while “ERROR: Erase Flash Operation Failed!”. I simply proceeded and the error did not appear to affect anything.
 
2. Visit [https://blog.michael.kuron-germany.de/2014/11/crossflashing-dell-perc-h200-to-lsi-9211-8i/comment-page-1/ source] to get screenshots vit the error messages

Revision as of 20:08, 17 March 2019

rtl8812AU

https://github.com/abperiasamy/rtl8812AU_8821AU_linux.git

fjerne led-disco

/etc/modprobe.d/8188eu-blacklist.conf

options 8812au rtw_led_enable=0


for dev in $( lsblk | awk '/sd[a-z].*1,8T/ { print }' ); do echo =============================== $dev ============================ ; smartctl -a /dev/$dev ; done | pastebinit


mdadm --remove /dev/md0 failed # all failed devices

mdadm --remove /dev/md0 detached # failed ones that aren't in /dev anymore

ip addr add 192.168.0.101/24 dev eth0 ; ip route add default via 192.168.0.1 dev eth0


Mulig rekkefølge med forbehold om at et ikke stemmer, for å endre vg navn på vg med root-partisjon vgchange gammel-vg ny-vg vgchange -ay

endre i /etc/fstab

grub-install /dev/XxX

update-initramfs -k all -u

reboot

Crossflash Dell PERC H200 from ir to it-mode

The short answer

I slightly followed this guide:

https://blog.michael.kuron-germany.de/2014/11/crossflashing-dell-perc-h200-to-lsi-9211-8i/comment-page-1/

The longer answer is. I followed the guide, this way, but did it a little different

The longer answer

Prepare a usb memory stick formatted to fat32 with two folders called P07 and P20

Step 1 download old firmware

1. Download this zip archive from dell and unzip it: https://downloads.dell.com/FOLDER02950081M/1/Y2R1T_9211_FW.zip?uid=f06bb69a-8c88-4a54-ac7b-ee8826244140&fn=Y2R1T_9211_FW.zip

2. Extract 6GBPSAS.FW from Y2R1T_9211_FW/Firmware/6GbpsSASHBA_07.03.06.00_A10

3. Extract 2118it.bin from FY2R1T_9211_FW/Firmware/9211-8i_P7/

4. Extract sas2flash.efi from Y2R1T_9211_FW/sas2flash/p05/efi/

5. Place the three extracted files in the P07 folder

Step 2 download current firmware

1. Extract 2118it.bin from Y2R1T_9211_FW/Firmware/9211-8i/P20/

2. Download this zip https://docs.broadcom.com/docs-and-downloads/host-bus-adapters/host-bus-adapters-common-files/sas_sata_6g_p20/Installer_P20_for_UEFI.zip

3. Extract sas2flash.efi from Installer_P20_for_UEFI/sas2flash_efi_ebc_rel/

4. Place this to extracted files in the P20 folder

Step 3 download uefi shell

1. Download an uefi shell: x86_64 UEFI SHELL I choosed version 1 as it worked for the person in the guide Direct download link

2. Extract Shell_Full.efi to the root of the memory stick. I had to rename it to Shellx64.efi to use it with my motherboard, asus P8H67_M_EVO. Check with you motherboard vendor to determine how to use efi-shell

Step 4 flashing

1. boot computer to efi shell

2. If not present with a list with devices, type map -b

2. On my computer the memory stick is called fs0 so I typed fs0: to change prompt to the memory stick

3. cd P07

4. sas2flash -listall will show the controller. If not, check if it is installed to a pci-e port

5. sas2flash.efi -c 0 -list will show controller details and take a note of the sas address number

6. sas2flash.efi -o -e 6 will erase the old firmware and boot rom

7. sas2flash.efi -o -f 6GBPSAS.FW writes the dell 6gbs firmware

8. sas2flash.efi -o -f 2118it.bin writes the P07 firmware

9. Then I rebooted

10. boot into efi again

11. cd P20

12. sas2flash.efi -o -f 2118it.bin writes the P20 firmware

Notes

Directly copied from the source, step number changed to fit my tutorial:

1. Step 6 showed “Erasing Flash Region” and then after a while “ERROR: Erase Flash Operation Failed!”. I simply proceeded and the error did not appear to affect anything.

2. Visit source to get screenshots vit the error messages