Error - Unimplemented Firmware
server. The numbers given in the section titles are internal tracking numbers for change requests related to the issues. These issues are divided into the following topics: Service Processor Firmware Issues Resolved Service Processor Issues BIOS Issues Resolved BIOS Issues LSI Firmware Issues Service Processor Firmware Issues The following are current issues. Mouse Pointers Out of Sync on Windows 2003 at High Resolution (6669368) Special Character in FTP Password Disables Snapshot Feature (6674741) Service Processor Does Not Log Event or Provide Visual Alert After Hard Disk Is Removed Recovery For Accidentally Flashing Wrong Platform Firmware on Sun Fire X4600 M2 Server Use -f Option To Upgrade ILOM when Updating Firmware When you upgrade the system firmware, use the load command with the -f option. This upgrades the ILOM as well. -> load -f other_options See the ILOM documentation collection for additional details. OEM Error Messages In ILOM Logs (6608347) If you see OEM error messages in the event log, contact Oracle Customer Support. The following table shows an example of OEM error messages in the event log: 7b02 | 09/13/2007 | 16:07:27 | OEM #0x12 | | Asserted 7c02 | OEM record e0 | 00004800001111032000000000 7d02 | OEM record e0 | 10ab0000000810000006040012 7e02 | OEM record e0 | 10ab0000001111002011110020 Mouse Pointers Out of Sync on Windows 2003 at High Resolution (6669368) When JavaRConsole is used to access Windows 2003, and the remote display resolution is greater than 1024x768, the local mouse pointer goes out of sync with the remote mouse pointer. This occurs because the resolution directly supported by JavaRConsole is 1024x768; the Windows display driver detects this, and simulates the larger display using panning. This confuses the local mouse driver. Workaround Simply ignore the local mouse pointer while interacting with the remote system. Alternately, you can use a display resolution of 1024x768 or less. Special Character in FTP Password Disables Snapshot Feature (6674741) The ILOM snapshot feature does not work if an FTP password with special characters is used. For example, suppose an FTP account on server “ftp” has a user name of “user”, a password of “abc@123”. You should be able to specify that account as a snapshot with the following command: set dump_uri=ftp://user:abc%40123@ftp/ In this URI, the “%40” represents the “@” character. This syntax is not interpreted corr
can not post a blank message. Please type your message and try again. Mauiboy Level 1 (40 points) Q: hard drive diagnosis I'm hoping someone can help me out..... started up my Macbook Pro 2009 13" and got the blinking folder with question mark.I ran through all the typical stuff:reset PRAMreset SMCran First Aid from disk utility (booted from install disc)....... repair faileddecided to format from disc utility...... went to erase....... got the following error: "Disk Erase Failed with the Error Assert: Internal Error or unimplemented"even tried to just reinstall system software......but hard drive isn't recognizedso, I'm thinking I need a new HD...... .......but then someone said it could be the "hard drive controller". I https://docs.oracle.com/cd/E19121-01/sf.x4600m2/819-5032-24/html/BIOS_ILOM.html don't know how to test for that.Any way, fortunately, everything is saved to an external drive via Time Machine (Whew!)......... Is this a hard drive failure? If so, any suggestions on a good one to get ..... was looking at the WD Blue Scorpion. Thank you for any assistanct. Macbook (firewire), Mac OS X (10.5.4) Posted on Feb 7, 2013 5:46 AM I have this question too Close Q: hard drive diagnosis All https://discussions.apple.com/thread/4784949?start=0&tstart=0 replies Helpful answers by ds store, ds store Feb 7, 2013 7:07 AM in response to Mauiboy Level 7 (30,400 points) Feb 7, 2013 7:07 AM in response to Mauiboy Mauiboy wrote:started up my Macbook Pro 2009 13" and got the blinking folder with question mark.This is the firmware telling you it can't find the bootable OS your assigned to it via System Preferences > Startup.This could have a variety of meanings, or simply the firmware forgot what to boot from.The first step is to hold the option/alt key down on the builtin or wired keyboard and boot the computer into Startup Manager and see if OS X is selection, then boot from it and reset the startup volume again.ran First Aid from disk utility (booted from install disc)....... repair faileddecided to format from disc utility...... went to erase....... got the following error: "Disk Erase Failed with the Error Assert: Internal Error or unimplemented"This could mean the drive is failing.Any way, fortunately, everything is saved to an external drive via Time Machine (Whew!)......... Don't whew just yet. If the drive is bad and a corrupted OS X and software is on the TimeMachine drive, what are you going to restore with?TimeMachine is terrible backup system, it relies too much on the software to be pristine
BSOD during XP setup Discussion in 'General Hardware' started by iiee, Sep 21, 2006. Sep 21, 2006 at 3:17 PM #1 iiee Joined: May 2, 2005 Messages: 79 (0.02/day) Thanks Received: 2 System Specs Processor: i7-975 Motherboard: evga x58 Classified Cooling: Custom WFC http://www.techpowerup.com/forums/threads/problem-identified-finally-bsod-during-xp-setup.17489/ Memory: 3Gb Kingston 2000 Video Card(s): Zotac GTX 285 AMP Hard Disk(s): X25-M 2x Raid0, Gigabyte i-RAM 4Gb Optical Drive: Pioneer Blu-Ray r/w LCD/CRT Model: Dell 2709W Case: Cooler Master Stacker Sound Card: X-Fi Elite Pro Power Supply: Corsair HX1000 Software: WinXP sp3, Vista Ult-32 sp1 Firstly thanks for everyone that helped in that thread. Everything is run at stock speed, No overclock during installation. The RAM (Corsair 4400C25PT, DDR550) is giving problem. It was not damaged, error - but just did not work under bios default setting. Bios default DIMM Voltage setting was 2.60 V. At 2.6V i ran memtest86 throughout the night without single error. The voltage was increased to 2.80V then only able to pass the file copy process before 1st reboot. It was then stuck at "Install Windows" session with BSOD. 2.90V passed it until fully installed. I have used this RAM on this board at 2.70V without problem. I did not understand error - unimplemented why the RAM behaved like this now. 2.90V is consider high voltage for RAM, and it is not yet overclocked!! May be the last day of this RAM is around the corner... oh ya the rated Voltage for this RAM is 2.75V in corsair website, but i thought that 2.75V is only needed at 275Mhz. now at 200Mhz needs 2.90V, I cant imagine how high the Voltage it needs when i start overclocking. What a lesson. So passing MEMTEST86 is NOT guaranteed indeed. Hope this help those who have similar problem. Board : DFI LP NF4U-D CPU : FX55 HDD : Raptor 74G PSU : Enermax 620W VGA : X1900XTX RAM : Corsair 4400c25PT 512x2 Last edited: Sep 21, 2006 Sep 21, 2006 at 3:28 PM #2 iiee Joined: May 2, 2005 Messages: 79 (0.02/day) Thanks Received: 2 System Specs Processor: i7-975 Motherboard: evga x58 Classified Cooling: Custom WFC Memory: 3Gb Kingston 2000 Video Card(s): Zotac GTX 285 AMP Hard Disk(s): X25-M 2x Raid0, Gigabyte i-RAM 4Gb Optical Drive: Pioneer Blu-Ray r/w LCD/CRT Model: Dell 2709W Case: Cooler Master Stacker Sound Card: X-Fi Elite Pro Power Supply: Corsair HX1000 Software: WinXP sp3, Vista Ult-32 sp1 OMG ! windows report serious error even at 2.90V !! Now using 3.00V . Yet to see if any error. I may fry the RAM very soon Sep 21, 2006 at 3:37 PM #3 Seany121