gah doorules! you dangle lovely firmares in front of me like carrots, yet i cant use them damn evga mobo!
Printable View
gah doorules! you dangle lovely firmares in front of me like carrots, yet i cant use them damn evga mobo!
new firmware 9211 do NOT install 2118IT.bin
Thanks for the warning Tilt
BTW, do you know of any board where one can disable pci slot scanning?
(last effort before I RMA the 9260 that hangs)
quote from LSI
If these steps were not followed and the MegaRAID controller hangs at power-on, try the following steps to attempt to recover the MegaRAID controller:
1. Remove the MegaRAID controller from the system
2. Disable the PCI slot scan in system BIOS
3. Insert the MegaRAID controller into the slot where the PCI slot scan was disabled and boot to DOS
4. Use "MegaCli -adpm0flash -f mr2108fw.rom" to reflash this firmware image (Mode 0 flash MUST be done in DOS)
5. Reboot the system to either the OS or DOS
5. Use "MegaCli -adpfwflash -f <older fw file name> -noverchk -a0" to flash the older firmware version
6. Use "MegaCLI -facdefset -a0" to load the factory defaults
7. Reboot the system and the MegaRAID controller should be recovered
@ Anvil - i don't think any of the ggbt boards have this.
Quote:
Originally Posted by Anvil
EVGA's and some new asus like R3E.
u can boot from HDD not from RAID and go to CMD with administration rights
then put the sas2flash and the bin file on the main folder of C:\
type c:\sas2flash -f firmwarename.bin and then hit enter.
well there is a new firmware fo the 9260 that is MAY fix the issue with the EVGA mobos, but im not gonna test it. just got this one back from RMA
So any evgan's tested new firmware for 9260? I cant do that because i used to connect to work? Any word from lsi/evga?
asked the same question of LSI, here is reply:
kinda leaves it open...needs to be tested. I am selling mine so i do not want to mess with it. there is some big nvdata changes, and that was the problem. the changelog denotes a compression/decompression logic addition that may just fix the problem.Quote:
None of our firmware releases have been tested by LSI on EVGA boards to this point. None of the defects listed were specifically referencing EVGA compatibility, though there were some NVDATA changes made.
Kind regards,
Brent VanDyke
Technical Support Engineer
Global Support Services
I've been running a raid 5 setup on a 1231ML with 8 raptors without incident for well over a year. Last week I bought 4 Phoenix Pro 120Gb SSDs, installed and configured them in a raid 0 in Windows, booted from the dvd and installed Windows 7 without a hitch but when I tried to boot back into Windows on my raid 5, it blue screened. Seems like one of my drives dropped out of the raid 5. Through many hours of trial and frustration, I discovered that when the SSDs are plugged in to the controller, whether they are configured or not, they cause a conflict that prevents the raptors from functioning. I installed Windows on a single raptor, then created a raid 0 with the 8 raptors, initialized it but as soon as I attempt to write on it, it drops off and when I reboot, the 1231 hangs until I turn my system off. When I disconnect the SSDs, the problem disappears. Strangest thing I've ever seen.
Already fixed the problem?Quote:
Originally Posted by Tiltevros
I cant find data, how much cache the 9211 have onboard... can anybody help?
16mb
LSI SAS 9211-8i 08.00.00 new firmware release
http://www.lsi.com/storage_home/prod...-8i/index.html
Product: Firmware
Version: 08.00.00.00
Release Date: 02-NOV-10
Release Type: GCA
Defects Fixed (64)
Enhancements Implemented (34)
Defects Fixed (64):
SCGCQ00102232 - PL: Unused phys not disabled on some boards
SCGCQ00150956 - Unwarranted SAS TOPOLOGY CHANGE LIST EVENT with PhyStatus change indication
SCGCQ00151226 - Possible to send a NCQ command during NCQ error handling
SCGCQ00151272 - 6001 format when inquiry is issued while format is active to a SATA device
SCGCQ00151465 - PCI Class Code SubCode value is incorrect in Thunderbolt NVDATA
SCGCQ00125128 - IR: (IR only) Removing a multipath IR disk multiple times results in a fault (0x8109).
SCGCQ00150267 - Unplugging USB end device during IOP USB TEST hangs firmware
SCGCQ00151004 - USB: Enumeration somestime causes fault 0xD04
SCGCQ00153033 - A config page request to erase log entries in the flash fails.
SCGCQ00155949 - Host and Library API names to contain 'i' to denote interfacing API.
SCGCQ00155966 - Phase 8 IT: Fault 265D during driver load and device discovery in parallel
SCGCQ00156138 - Hot Spare not getting pulled in after removing a member drive from IM volume
SCGCQ00156250 - USB - Remove debug memory allocation from USB init
SCGCQ00157653 - PM: Need to disable SAS link power mgmt due to outstanding HW issues
SCGCQ00157667 - USB - CBW, CSW and Status incorrectly has only one instance for two ports
SCGCQ00157920 - Link Reset is happening within one second after getting invalid initial FIS
SCGCQ00157932 - (IOP-Only) Need to add additional hardware EDRAM failure detection
SCGCQ00158934 - Initialization of DDR controller fails when the memory clock is 667MHz
SCGCQ00151857 - (GEMINI) Program Interrrupt seen when in FAULT routine
SCGCQ00155202 - Discovery Error 80h
SCGCQ00152992 - 0x0614 fault when aborting SATA passthrough messages
SCGCQ00099988 - PL: Msync needed to update VP_ID of SCSI IO request before posting the IO to SAS Core.
SCGCQ00149654 - iop usb portstop halts firmware
SCGCQ00149684 - Constant ORR after injecting a wrong-direction data frame
SCGCQ00150990 - Thunderbolt: Implement hardware workaround for bug track 758
SCGCQ00151363 - USB library is not using correct IOP interface functions
SCGCQ00151455 - ManPage 8 Device Type BOOT_ROM and SEEPROM should be unique types
SCGCQ00151755 - PL: Discovery Error MPI2_EVENT_SAS_DISC_DS_MULTI_PORT_DOMAIN
SCGCQ00151758 - Ethernet FWDL: Firmware download from a TFTP Server occasionally fails.
SCGCQ00152176 - Invalid interrupt from memory controller
SCGCQ00152263 - IOP: Uart console command "iop show sbr" only shows 1st copy of SBR correctly
SCGCQ00152526 - Thunderbolt: The SHELL speed is set wrong in SBR
SCGCQ00152549 - (PL-Only) Debug text strings are out of sync with the order of data
SCGCQ00152980 - Meteor with DDR enabled faults with 0002 then 265D at boot up
SCGCQ00153003 - SATL: 620F fault with reassign blocks + invalid parameter list header
SCGCQ00153048 - PL: Port Enable and Config page requests timeout during large topology discovery.
SCGCQ00153107 - Tuning needed for SATA power management
SCGCQ00153117 - SATL: Wrong tag reported when unable to determine tag
SCGCQ00153144 - Manufacturing Page Block create routine should not be part of cfgi library build.
SCGCQ00153253 - Setting the Min and Max value for the resources in Mfgpag9 to ffff leads to fwfault 0x0302
SCGCQ00153284 - CKE signal in Memory subsystem glitches when entering self refresh mode
SCGCQ00153294 - PCIe link width change returns 300a0007 loginfo even when request is honored exactly
SCGCQ00153578 - iop: iopidynmalloc() won't allocate fast - dma-able memory
SCGCQ00153605 - The SEP on a specific enclosure is not being seen.
SCGCQ00154962 - IR Load Balancing
SCGCQ00155425 - Phase 8: IR: Misleading comments in Setting and clearing data Scrub allowed flag
SCGCQ00155602 - Thunderbolt: Bugtrack 770 sys dma to bad host address
SCGCQ00155693 - Firmware might fault with code 0x4300 during SATA device initialization
SCGCQ00155755 - Fault 5803 during discovery of large topology after adjusting Ph8 Alpha FW NVDATA on Liberator B4.
SCGCQ00156721 - Fault 0x265d on port enable.
SCGCQ00125874 - Don't fault if TM sent to an Expander
SCGCQ00155280 - DMA sense data with FW instead of HW to prevent a hang of the DMA transfer.
SCGCQ00146928 - Rescaning of large topology with 90 drives during make and break of wide port not handled properly by driver
SCGCQ00154633 - 265d fault is seen when volume member drives are removed & inserted simultaneously
SCGCQ00156204 - Fault x6815 with Mustang in I/T switching running Target Resets
SCGCQ00157807 - IOP: Fault information sometimes not displayed to UART after a fault
SCGCQ00157838 - USB - FW is not able to communicate with USB end device
SCGCQ00157899 - IR: Possible data corruption with phys devices returning at DMD timer expiration
SCGCQ00158317 - Fault 6051 or Long TM response times for Target Resets
SCGCQ00158423 - Trying to flash IR firmware image on a controller with no NVSRAM faults with 265D fault code
SCGCQ00160490 - Change EEDPTagMode to 0 in default NVDATA
SCGCQ00160605 - SAS target mode transmit DMA engine incorrectly asserts Auto Response Not Sent status
SCGCQ00161827 - Update firmware to check new PCI Device ID for 9205-8e channel board
SCGCQ00161828 - Mustang default NVDATA has Device ID set to 0x80 instead of 0x86 at several places .
Enhancements Implemented (34):
SCGCQ00102813 - IOP: Change Start of Day memory allocation for Raid Accelerator request queues
SCGCQ00118431 - (IOP-Only) Add dynamic lookup of config page buffers at SOD
SCGCQ00128289 - (IOP-Only) Add firmware ManPage9 fixed Min capability
SCGCQ00136668 - Enable sending 3 identify frames
SCGCQ00140397 - MPI2: modify Host Based Discovery Action Request
SCGCQ00141686 - Ph7 IR: Do read IO load balancing for RAID10/RAID1E ASM volumes for better performance
SCGCQ00141834 - MPI2: ability to disable SATA NCQ on a per-device basis
SCGCQ00142578 - MPI2: obsolete MPI2_IOUNITPAGE1_MULTI_PATHING
SCGCQ00142855 - LSI2008 SATA NCQ enablement
SCGCQ00142923 - Allow Config Write Current of SAS IO Unit Page 1 after PortEnable
SCGCQ00142955 - Change how discovery handles spinup hold for sata devices
SCGCQ00143162 - Eliminate PL Config Page restrictions
SCGCQ00145313 - Bit 20 of RAID Volume Page 0 to comply with definition as in MPI 2 spec rev M or later
SCGCQ00146007 - Change DMA engine default threshold values for System and DDR data
SCGCQ00147761 - Customer requested change to DCR requirement placed on IOP by DDR3 library
SCGCQ00147804 - Ph8: Host Based Discovery Request change
SCGCQ00147885 - Method to prevent drivers from resetting firmware during large CLI command
SCGCQ00148227 - Send Execute Device Diagnostic ATA command during SATA Initialization
SCGCQ00148567 - pl: SATL: Support write buffer mode 7.
SCGCQ00148569 - pl: SATL: Better handling of invalid signature FIS
SCGCQ00149166 - PL: Add compile option to fault when Discovery detects Discovery Error 0x90 (SMP Timeout)
SCGCQ00150278 - Update Phase 8 Project with new MPI-2 header files
SCGCQ00151472 - Support exiting self-refresh mode in DDR3 library, for battery backed implementations
SCGCQ00151477 - Thunderbolt: Increase max message frame to 1008
SCGCQ00152166 - (NVDUMP only) Add capability to parse XSD files to provide formatted config data
SCGCQ00151361 - Allocate ISTWI device types and GPIO function codes for vendor specific use
SCGCQ00151468 - DDR3 Read and Write Leveling algorithms take too long
SCGCQ00154697 - DDR3 library needs to support different types of Raw Cards
SCGCQ00156735 - Add temperature sensor read capability to uart
SCGCQ00157613 - Thunderbolt SDMegawrapper settings rev 5
SCGCQ00159101 - Add temperature conversion
SCGCQ00151517 - USB: Create a package build
SCGCQ00152660 - Thunderbolt: Updated SDMegaWrapper values
SCGCQ00156191 - (PL-Only) Mask out unused debug code on the IO path when not used
Product: SAS2BIOS
Version: 7.15.00.00
Release Date: 01-NOV-10
Release Type: GCA
Defects Fixed (15)
Enhancements Implemented (7)
Defects Fixed (15):
SCGCQ00148745 - LSI2116 Eval Meteor boards hang going into BIOS CU
SCGCQ00148757 - Add back a partially redundant call to ResetSHEX() because other paths aren't always executed
SCGCQ00151512 - SAS2BIOS - CU: SATA Disk Capacity value always zero for expander attach
SCGCQ00148946 - After expanding second enclosure in the CU, data gets corrupted.
SCGCQ00152052 - SAS2BIOS - Calls to ReadConfigPageRaidPhysdisk0 return invalid data
SCGCQ00157065 - While activating a failed volume the BIOS CU should give some error message if the activation has failed due to any reason.
SCGCQ00158310 - SAS2BIOS CU reports different sizes for hard disks on device properties screen
SCGCQ00155163 - SAS2BIOS CU Failed to showed the first path in BIOS topology
SCGCQ00138021 - WH: Tools report volume size differently
SCGCQ00157562 - BIOSCU hangs while booting/entering CU with 2Falcon IR & 1Meteor IT HBA.
SCGCQ00160446 - One dot (".") remains behind while 'reassigning the blocks' command executed in Device Verify screen.
SCGCQ00153779 - One dot (".") remains behind while erasing the status message of a drive while verifying it.
SCGCQ00154583 - sas2 BIOS CU is not providing more descriptive error information.
SCGCQ00154677 - Invalid topology displayed if vertical scrolling has occurred and an enclosure is unplugged
SCGCQ00154707 - SAS2BIOS returns format success when device is disconnected during format
Enhancements Implemented (7):
SCGCQ00135558 - SAS2BIOS: Add support for non 512-byte sector drives in BIOS CU
SCGCQ00145547 - sas2 BIOS CU should provide more descriptive error information.
SCGCQ00147738 - Handle hardware error in 2208-1 (B0) by alternating all I/O port access and reset SHEX at start of day
SCGCQ00151383 - SAS2BIOS: CU - Add SCSI I/O Command Serial Trace in BIOS CU
SCGCQ00151267 - SAS2BIOS - Add Mustang support to SHEX reset implementation
SCGCQ00148528 - Option ROM Slot and Volume Ordering Enhancement for HP WGBU
SCGCQ00148011 - Handle hardware error in 2208-1 (B0) by alternating all I/O port access in the BIOS CU