IdeaPad Z510 States power supply to weak

Purcahsed a IdeaPad Z510 a week ago direct from lenovo.   After a fresh reboot everytime it's on A/C power and i go to the desktop I recieve a dialog message telling me the power supply is insufficient and needs to be upgraded.   I can either close the window or click buy and it takes me to the lenovo website.     I think lenovo should be sending me a new power supply or computer.   I am trying to contact them directly too, but it seems I have to pay to talk to someone with a brand new computer???? 

Hi all, I had the same problem and I received a replacemnent power supply. No change, the error message is still there. Do you have win 8.1 or win8? I do not remember if I had the error even before upgrading to win 8.1 I removed the energy manager and installed another version (from http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS037680), not for Z510.  All works ok and there is no error message. Probably they just need to update the energy manager for win 8.1 for the Z510

Similar Messages

  • MaxDB in strange state after power supply blackout

    Hello DB specialists,
    I'd like to ask if anyone has faced similar problem as we do. We had a power supply blackout in the server room and one of our UPS didn't survive. Two servers went down immediatelly - lusckly both ofthem for training purposes. When we restarted them and started all SAP systems everythink seemd ok. But after couple of days we realized, that SolMan system contained old license, which was renewed nearly a year ago. When we logged to the system, we realized that the DB is in state of more than year ago. It appears like after the DB restore.
    We localized some strange files in /sapdb/data/wrk/<SID>/DIAGHISTORY from the time of restart after the power crash.
    My question is - might it be, that the DB rebuilt itself to some previouse state after the system crush ? And if so - is there any way to restore the last state ?
    Thank you for your comments in advance.
    Best regards
    Tomas

    >
    Tomas Toth wrote:
    > But I think .. even OVERWRITE LOG mode would cause the same problem .. or does it not ?
    >
    > I remind that we are talking about non-production system, the system is used for demo purposes and there are not many changes there.
    >
    > Thx.
    > Tomas
    No, it won't.
    The key point here is, that log mode OVERWRITE still lets the logwriter do its job and with that the automatic savepoints do occur.
    It's just that the written log data is not kept from beeing overwritten without having a backup for it.
    When you crash such an instance it will startup from the last written savepoint which is likely <=10 minutes away. And depending on your log data state, all other changes made after this are still in the log volume.
    So it's quite a good choice for situations where you don't really need everything to be recoverable up to the latest minute. For example demo systems or training systems could be a use case.
    LOGWRITER OFF on the other hand completely disables the log writing and by that also the automatic savepoints.
    regards,
    Lars

  • Power Supply "Powered-Off" State

    I have power supplies in Slot 1 and Slot 2.
    Both power supplies show fully operable (power, voltage, etc) in details, however the Slot 1 power supply shows "Powered-Off"
    I have tried both N+1 and Non-Redundant power policies.
    Thanks for help in advance.

    Should be Non-Redundant with only 2 supplies.  Once selected try to re-acknowledge the chassis.  I was set these global polices first off, power and uplink # and save, acknowledge and allow time to discover and update.  What rev you using ?  Not sure of exact rev's but saw several power supply and fan bugs resolved in newer 1.4(3) code.

  • ATI Radeon 9700 Pro - Power Supply too small?

    I'm having a problem with my Powercolor 9700 Radeon Pro. My system will simply not power when i plug this video card in (no power supply start, no posting beeps, nothing).
    The 9700 pro card I have will work fine on another PC that I have with a lesser power supply and lesser cpu so I know the card is ok. My Geforce3 card works fine in the new 865PE computer, so it seems the MSI board/AGP slot is ok.
    I've tried unplugging all peripherals (HDDs, CD, DVD drives) and still no power up when the 9700 is plugged into the power supply.
    My system consist of:
    MSI 865PE Neo2 FISR(v1.7)
    P4, 2.8, 800fsb
    512MB Corsair XMS Twinx (2 256MB sticks)
    2 HDD (Western Digital, 60 & 120GB)
    DVD/CD drive
    CD-RW drive
    Soundblaster live
    2 internal case fans
    360w PS
    Stats for power supply:
    +5v - 35A
    +12v - 17A
    +3.3v - 28A
    Bios settings:
    CPU BUS (FSB) - 200
    AGP Voltage - 1.5
    PCI/AGP speed (PCI clock) - 66.33/33.33
    PCI latency timer - 32
    AGP setting - (if this is the 4x/8x setting, I can't find a way to change it)
    APIC ACPI SCI IRQ - disabled
    AGP aperature - 64MB
    Dynamic overclocking - off
    Performance mode - slow
    hyperthreading - disabled
    I've tried upping the AGP voltage to 1.6 and I have disabled cacheing.
    I read that some folks have recommended setting the AGP down to 4x, although for the life of me, I cannot find a way to do that in bios or anywhere else.
    Does this power supply sound acceptable? Do the 9700's draw their power off the 12v circuit?  If this PS is weak, then what +12v amp. should I aim for?
    Does anyone have any ideas of any of issues that might cause my system to not power up like this?
    Thanks for any help!

    Thanks for responding Sean,
    I did try upping the AGP voltage to 1.6v while only having the the 9700 card attached to the power supply.  Same result, no power-up what so ever.
    The other computer's video drivers are were the standard windows vga drivers.   I don't think that really is a problem since I can't get the computer/power supply to even come on, let alone load windows.
    What baffles me is that I have a geforce3 agp card that works fine in the neo2, and the 9700 works fine in another computer.  Other then the power supply, or a problem/setting with the mainboard, I can't imagine what the problem is.  The thing is, I don't want to shell out $100 for a power supply until I know that'll fix it.
    thanks

  • Shock Therapy - An Athlon64 / FX Power Supply Guide

    I used to make a hardware list of all the components I would like to incorporate in my next
    computer build. Normally...at the bottom of that list would be the power supply, not that I
    didn't think it was important, it's just that my other hardware was so interesting! Today, power supplys
    seem to take a back seat to blazing-speed CPU's, Dual-Cored processors, glitz and glamour
    video cards...not to mention supersonic, heat-sinked RAM and modular, gizmoe'd PSU's promising not
    only over-achiever specifications, but eye-candy as well. The lowly PSU....tucked up somewhere inside
    it's dark and lonely loft....effortlessly supplying us with the energy required for important 3D imaging
    or just funning with the latest games.
    What a power supply does is rather simple. It converts your office or home's socketed electricity to
    usable 3.3v, 5.0v and 12.0v energy...that's all. A power supply that cannot efficiently do this will-
    over time-cause computer crashes, continuous reboots and shutdowns, and worse...expensive component damage.
    And now, with faster processors such as AMD's Athlon64 and FX line of CPU's, never has there been a time, when
    choosing the right power supply is so important! This article is written for those using these high-powered CPU's!
    Well...Do we have your attention!?
    If you are experiencing these problems, or still scratching your head over that last RMA....could be
    your PSU is trying to tell you something.
    To begin with, a power supply's ratings refer to its maximum output under ideal conditions. No power
    supply is 100% efficient. In high-quantity manufacturing, power supplys may not put out any more than 60% of
    their advertised specifications. In any PSU, that rating can be further reduced by the effects of heat
    and electro-magnetic radiation. That's where "switching" power supplys come in. A switching power supply draws
    only as much current that is needed from the AC input. Buying a hefty PSU with this feature will guarantee
    that you will be paying no more for electric service, than you would with a cheaper, less powerful unit.
    One of the most common causes of power supply inefficiency, and ultimately failure is dirt. Dust and
    foreign materials can cause the beginning of the end for a power supply, by attacking the fan first.
    It begins by slowing the fan down...thus creating heat through friction, then ultimately burning it out.
    PSU's with high-quality ball bearing fans are a must. They are far more durable, and not as likely to
    become noisier as time goes by.
    As a general rule...a failing PSU will usually emit abnormal sounds, followed by unstable voltage readings....
    then the computer crashes or lock-ups, with random shutdowns, and sometimes...refusal to even power-up.
    If you think your power supply is on its last leg...better to deal with it now, or face the more serious dilemmas later on.
    APM (Advanced Power Management)
    APM is a feature originally developed by partners, Microsoft and Intel. It relates to a systems ability
    to utilize different states in regards to a systems utilization of power. On, Off, Standby and Suspend
    are examples...these are BIOS features, not PSU functions. APM only requires of the power supply, the
    function to turn power on or off through an electrical signal, and the presence of stand-by voltage.
    All ATX power supplys are required to incorporate this feature. However, if some components in a computer
    are not APM-compliant, your system may encounter errors or freezes when going into hibernate or stand-by
    modes.
    ACPI (Advanced Control Power Interface)
    It's the latest power management control that was developed by a conglomeration of IT corporations. This interface
    is O.S. derived, rather than BIOS, and all ATX power supplys should be ACPI-compliant. You should not have to be
    concerned about this feature.
    Line-Conditioning Circuitry
    A power supply component that helps control power levels, spikes and surges in
    the most unreliable of home sockets.
    EMI Filter
    This circuitry smooths the fluctuations of incoming AC currents, also known
    as Electro-Magnetic Interference - EMI filters are usually found in higher-end power supplys.
    PFCC
    Power Factor Correction Circuitry...smooths out sudden, initial spikes in power
    delivery - reducing amplitude and preventing circuit overloads.
    Connectors
    There are five main connectors found on the latest version ATX power supply.
    1) ATX main power connector - 20-pin, 24-pin, and 20 to 24-pin adapter.
    2) ATX 12v power connector (4-pin to CPU)
    3) Molex peripheral power connector
    4) Floppy power connector
    5) Serial ATA power connector
    On newer SLI-certified power supplys, you'll find two 6-pin video card connectors.
    Know What You Need
    When purchasing a power supply, make sure your parts list is all-inclusive...know ahead of time, what you expect to
    install in your system. You should also visit the motherboard manufacturer's site, as well as the CPU's. Most of the
    products will have specifics regarding power supply requirements needed for that specific component. Unfortunately, you
    really won't know how well the PSU performs until it is installed and running your system (hopefully!) This is the main reason we
    recommend the most popular brands - power supplys that have shown a duration of manufacturing quality over the years. Those are
    as follows: Antec, Enermax, OCZ, PC Power and Cooling, Tagan, and a few newcomers such as SeaSonic and Silverstone are
    worth looking into.
    If you believe you have found the PSU of choice, remember this: AMD recommends a minimum 350 watt power supply to run
    Athlon64 and FX CPU's. To that, add the 30% for power lost to heat, and the subsequent electro-magnetic radiation. Hold on with that
    calculator...throw in an additional 40% to 60% for the "potential" inaccuracies of specifications inherent in mass-produced electronics.
    Pay special attention to outputs on either single, or dual rail +12v lines. A motherboard, CPU, and graphics card can consume up to
    150 watts alone - before hooking up your remaining components. If running an SLI configured board, look for a PSU that is certified
    to run that configuration...there's only a few PSU's that lay claim to that!
    Broken down, you can look at it this way: An Athlon64/FX processor can use up to 90 watts off the +12v rail. High performance RAM
    can take in about 25 watts for each stick of 256MB system memory from the +3.3v line. PCI cards will use about 10 watts each, while
    an AGP video card can consume about 50 precious watts alone from the +5v or +12v. Hard drives? A 7,200 RPM drive...about 15 watts
    each, taken from the +5v and +12v rail. Finally, but not absolutely is the optical drives...robbing about 20 watts each, also from
    the +5v and +12v lines. So you see....not only is the +12v amp ratings of concern, but also the +5v line!
    In doing the math...on a system incorporating an Athlon64 (say a 4000+), 2 sticks of high-end RAM, 2 or 3 PCI cards, 1 mid-to-high
    end AGP video card, 2 ~ 7,200 RPM hard drives, and a couple of CD/RW or DVD/RW opticals...you're looking at a "base" requirement of 270 to 325 watts. That's for a running system...now figure boot-up loads, 30% for heat and radiation bleed-off, then a 40% safety factor for manufacturing inconsistencies...you've got a power supply in the 450 to 520 watt range!
    Modular Power Supplys:
    The pins that are used for the modular plugs are not very good at passing current. It's basically electrical resistance between the male and female components, and voltage "drops" are likely. In real world events, they will become loose, dirty, corrosive, and eventually burn. You can figure about 10% less efficiency with a modular power supply.
    Now you can understand how manufacturing "tolerances" that are inaccurate by 40% to 60%, can have such a devastating effect on
    the performance of your new system. If you follow these simple guidelines, bearing in mind the hardware you will be using, and what
    your intended use of the computer is for...then it will be one less dramatic incident when pushing the power button for the first time!
    Here's a neat little tool....a bit out of date - that can give you a basic idea of what you'll need in a PSU.
    You can apply the percentages above, for an even more accurate assesment of your PSU requirements!
    http://www.jscustompcs.com/power_supply/Power_Supply_Calculator.php?cmd=AMD

    Quote
    In doing the math...on a system incorporating an Athlon64 (say a 4000+), 2 sticks of high-end RAM, 2 or 3 PCI cards, 1 mid-to-high
    end AGP video card, 2 ~ 7,200 RPM hard drives, and a couple of CD/RW or DVD/RW opticals...you're looking at a "base" requirement of 270 to 325 watts. That's for a running system...now figure boot-up loads, 30% for heat and radiation bleed-off, then a 40% safety factor for manufacturing inconsistencies...you've got a power supply in the 450 to 520 watt range!
    Well, except the CPU, my system has all that you mentioned there (I even have 3 optical drives). And my 350W PSU has been rock solid for more than a year (BeQuiet, = Tagan, IIRC). I don't think a 4000+ needs 100W more than my 3200+ . And that link you posted says that the minimum recommended PSU for my system is 506W  xD. Come on.
    Oh, and in the place I work there are 6 amd64 with GeForce 6800 GT and 2GB RAM with 380W Antec PSUs. All 100% stable, of course.
    I would only go for >400W if I wanted to do extreme OC (with overvolting), or SLI. Otherwise, a good brand 350W PSU is more than enough.

  • TS3694 iPhone 5.....during update to iOS 7 I have lost the power supply (blackout)

    this issue , happen to my iPhone 5.....during update to iOS 7 I have lost the power supply (blackout)
    Sudden screen : USB pointing to iTunes . it shows that it need a restore and update .. after downloading the software
    and extracting .. found Error1 at the point Verify firmware . AGAIN AND
    and this is the log ..
    2014-08-11 15:46:30.611 [4472:1648]: restore library built Feb 12 2014 at 16:27:17
    2014-08-11 15:46:30.611 [4472:1648]: iTunes: iTunes 11.3.1.2
    2014-08-11 15:46:30.611 [4472:1648]: iTunes: Software payload version: 11D257 (option key)
    2014-08-11 15:46:30.611 [4472:1648]: iTunes: Using MobileRestore state machine
    [13:47:25.0555] Changing state from 'Idle' to 'Restoring'
    [13:47:25.0555] device software does not support nonce generation
    [13:47:25.0555] requested restore behavior: Erase
    [13:47:25.0570] requested variant: Erase
    [13:47:25.0570] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 061FEA80 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 061FD2E0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [13:47:26.0553] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [13:47:26.0569] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0BA32F38 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [13:47:26.0569] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
    [13:47:26.0569] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re quest.plist
    [13:47:27.0068] amai: tss_submit_job: HttpQueryInfo returned 200
    [13:47:27.0286] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
    [13:47:27.0286] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re sponse.plist
    [13:47:27.0318] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
    [13:47:27.0333] <DFU Device 0562C260>: production fused device
    [13:47:27.0333] requested restore behavior: Erase
    [13:47:27.0333] device software does not support nonce generation
    [13:47:27.0349] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#93126bb7
    [13:47:27.0349] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#93126bb7
    [13:47:27.0364] <DFU Device 0562C260>: operation 0 progress 2
    [13:47:27.0380] <DFU Device 0562C260>: operation 0 progress 5
    [13:47:27.0396] <DFU Device 0562C260>: operation 0 progress 8
    [13:47:27.0411] <DFU Device 0562C260>: operation 0 progress 10
    [13:47:27.0427] <DFU Device 0562C260>: operation 0 progress 13
    [13:47:27.0442] <DFU Device 0562C260>: operation 0 progress 16
    [13:47:27.0458] <DFU Device 0562C260>: operation 0 progress 18
    [13:47:27.0474] <DFU Device 0562C260>: operation 0 progress 21
    [13:47:27.0489] <DFU Device 0562C260>: operation 0 progress 24
    [13:47:27.0505] <DFU Device 0562C260>: operation 0 progress 26
    [13:47:27.0520] <DFU Device 0562C260>: operation 0 progress 29
    [13:47:27.0536] <DFU Device 0562C260>: operation 0 progress 32
    [13:47:27.0552] <DFU Device 0562C260>: operation 0 progress 34
    [13:47:27.0567] <DFU Device 0562C260>: operation 0 progress 37
    [13:47:27.0583] <DFU Device 0562C260>: operation 0 progress 40
    [13:47:27.0598] <DFU Device 0562C260>: operation 0 progress 42
    [13:47:27.0614] <DFU Device 0562C260>: operation 0 progress 45
    [13:47:27.0630] <DFU Device 0562C260>: operation 0 progress 48
    [13:47:27.0645] <DFU Device 0562C260>: operation 0 progress 50
    [13:47:27.0661] <DFU Device 0562C260>: operation 0 progress 53
    [13:47:27.0676] <DFU Device 0562C260>: operation 0 progress 56
    [13:47:27.0692] <DFU Device 0562C260>: operation 0 progress 59
    [13:47:27.0708] <DFU Device 0562C260>: operation 0 progress 61
    [13:47:27.0723] <DFU Device 0562C260>: operation 0 progress 64
    [13:47:27.0739] <DFU Device 0562C260>: operation 0 progress 67
    [13:47:27.0754] <DFU Device 0562C260>: operation 0 progress 69
    [13:47:27.0770] <DFU Device 0562C260>: operation 0 progress 72
    [13:47:27.0786] <DFU Device 0562C260>: operation 0 progress 75
    [13:47:27.0801] <DFU Device 0562C260>: operation 0 progress 77
    [13:47:27.0817] <DFU Device 0562C260>: operation 0 progress 80
    [13:47:27.0832] <DFU Device 0562C260>: operation 0 progress 83
    [13:47:27.0848] <DFU Device 0562C260>: operation 0 progress 85
    [13:47:27.0864] <DFU Device 0562C260>: operation 0 progress 88
    [13:47:27.0879] <DFU Device 0562C260>: operation 0 progress 91
    [13:47:27.0895] <DFU Device 0562C260>: operation 0 progress 93
    [13:47:27.0910] <DFU Device 0562C260>: operation 0 progress 96
    [13:47:27.0926] <DFU Device 0562C260>: operation 0 progress 99
    [13:47:27.0926] WinDFU::UploadData: EOF, cbRead: 554
    [13:47:27.0942] <DFU Device 0562C260>: operation 0 progress 100
    [13:47:27.0942] WinDFU::UploadData: ZLP
    [13:47:27.0957] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    [13:47:27.0957] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    [13:47:27.0957] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    [13:47:27.0957] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    [13:47:30.0968] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    [13:47:30.0968] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    [13:47:30.0968] WinDFU::ResetDevice: resetting...
    [13:47:31.0046] WinDFU::FinalizeDfuUpdate: success
    [13:47:31.0046] <DFU Device 0562C260>: DFU succeeded
    [13:47:31.0046] Finished DFU Restore Phase: Successful
    [13:47:31.0218] DFU mode device disconnected
    [13:47:31.0218] Device removed when in state Restoring, moving device to transition state
    [13:47:31.0218] Changing state from 'Restoring' to 'Transitioning'
    [13:47:31.0218] Creating timer to monitor transition
    [13:47:32.0175] DFU mode device connected
    [13:47:32.0175] Transitioning device returned, continuing restore.
    [13:47:32.0175] Canceling timer
    [13:47:32.0175] Changing state from 'Transitioning' to 'Restoring'
    [13:47:32.0175] AppleDevice::GetDeviceID: failed for iBoot
    [13:47:32.0175] requested restore behavior: Erase
    [13:47:32.0175] requested variant: Erase
    [13:47:32.0175] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 061FDC70 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 061FE378 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 0B9D5148 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0033] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 0B9D5190 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 0B9D51D8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 0B9D5220 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 0B9D5268 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 0B9D52B0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 0B9D52F8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 0B9D5340 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 0B9D5388 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 0B9D53D0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 0B9D5418 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 0B9D5460 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 0B9D54A8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 06266350 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 06266398 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 062663E0 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}"
    [13:47:33.0049] amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 064698C8 [7161907C]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [13:47:33.0064] amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
    [13:47:33.0064] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re quest.plist
    [13:47:33.0298] amai: tss_submit_job: HttpQueryInfo returned 200
    [13:47:33.0501] amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
    [13:47:33.0501] amai: AMAuthInstallDebugWriteObject: debug object written: file://localhost/C:/Users/Dell/AppData/Local/Temp/Per2046.tmp/amai/debug/tss-re sponse.plist
    [13:47:33.0501] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "iBSS" has been previously personalized; skipping it
    [13:47:33.0501] amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "LLB" has been previously personalized; skipping it
    [13:47:33.0517] amai: _AMAuthInstallBundlePopulatePersonalizedBundle: no entry in manifest found for "Diags"
    [13:47:33.0532] <DFU Device 0BA2A9D8>: production fused device
    [13:47:33.0532] requested restore behavior: Erase
    [13:47:33.0532] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:33.0532] AppleDevice::GetDeviceID: failed for iBoot
    [13:47:33.0532] WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ca28221e
    [13:47:33.0532] WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#ca28221e
    [13:47:33.0564] <DFU Device 0BA2A9D8>: operation 0 progress 0
    [13:47:33.0579] <DFU Device 0BA2A9D8>: operation 0 progress 1
    [13:47:33.0595] <DFU Device 0BA2A9D8>: operation 0 progress 2
    [13:47:33.0626] <DFU Device 0BA2A9D8>: operation 0 progress 3
    [13:47:33.0642] <DFU Device 0BA2A9D8>: operation 0 progress 4
    [13:47:33.0657] <DFU Device 0BA2A9D8>: operation 0 progress 5
    [13:47:33.0688] <DFU Device 0BA2A9D8>: operation 0 progress 6
    [13:47:33.0704] <DFU Device 0BA2A9D8>: operation 0 progress 7
    [13:47:33.0735] <DFU Device 0BA2A9D8>: operation 0 progress 8
    [13:47:33.0751] <DFU Device 0BA2A9D8>: operation 0 progress 9
    [13:47:33.0766] <DFU Device 0BA2A9D8>: operation 0 progress 10
    [13:47:33.0798] <DFU Device 0BA2A9D8>: operation 0 progress 11
    [13:47:33.0813] <DFU Device 0BA2A9D8>: operation 0 progress 12
    [13:47:33.0844] <DFU Device 0BA2A9D8>: operation 0 progress 13
    [13:47:33.0860] <DFU Device 0BA2A9D8>: operation 0 progress 14
    [13:47:33.0876] <DFU Device 0BA2A9D8>: operation 0 progress 15
    [13:47:33.0907] <DFU Device 0BA2A9D8>: operation 0 progress 16
    [13:47:33.0922] <DFU Device 0BA2A9D8>: operation 0 progress 17
    [13:47:33.0954] <DFU Device 0BA2A9D8>: operation 0 progress 18
    [13:47:33.0969] <DFU Device 0BA2A9D8>: operation 0 progress 19
    [13:47:33.0985] <DFU Device 0BA2A9D8>: operation 0 progress 20
    [13:47:34.0016] <DFU Device 0BA2A9D8>: operation 0 progress 21
    [13:47:34.0032] <DFU Device 0BA2A9D8>: operation 0 progress 22
    [13:47:34.0063] <DFU Device 0BA2A9D8>: operation 0 progress 23
    [13:47:34.0078] <DFU Device 0BA2A9D8>: operation 0 progress 24
    [13:47:34.0094] <DFU Device 0BA2A9D8>: operation 0 progress 25
    [13:47:34.0125] <DFU Device 0BA2A9D8>: operation 0 progress 26
    [13:47:34.0141] <DFU Device 0BA2A9D8>: operation 0 progress 27
    [13:47:34.0172] <DFU Device 0BA2A9D8>: operation 0 progress 28
    [13:47:34.0188] <DFU Device 0BA2A9D8>: operation 0 progress 29
    [13:47:34.0203] <DFU Device 0BA2A9D8>: operation 0 progress 30
    [13:47:34.0234] <DFU Device 0BA2A9D8>: operation 0 progress 31
    [13:47:34.0250] <DFU Device 0BA2A9D8>: operation 0 progress 32
    [13:47:34.0281] <DFU Device 0BA2A9D8>: operation 0 progress 33
    [13:47:34.0297] <DFU Device 0BA2A9D8>: operation 0 progress 34
    [13:47:34.0312] <DFU Device 0BA2A9D8>: operation 0 progress 35
    [13:47:34.0344] <DFU Device 0BA2A9D8>: operation 0 progress 36
    [13:47:34.0359] <DFU Device 0BA2A9D8>: operation 0 progress 37
    [13:47:34.0390] <DFU Device 0BA2A9D8>: operation 0 progress 38
    [13:47:34.0406] <DFU Device 0BA2A9D8>: operation 0 progress 39
    [13:47:34.0422] <DFU Device 0BA2A9D8>: operation 0 progress 40
    [13:47:34.0453] <DFU Device 0BA2A9D8>: operation 0 progress 41
    [13:47:34.0468] <DFU Device 0BA2A9D8>: operation 0 progress 42
    [13:47:34.0500] <DFU Device 0BA2A9D8>: operation 0 progress 43
    [13:47:34.0515] <DFU Device 0BA2A9D8>: operation 0 progress 44
    [13:47:34.0531] <DFU Device 0BA2A9D8>: operation 0 progress 45
    [13:47:34.0562] <DFU Device 0BA2A9D8>: operation 0 progress 46
    [13:47:34.0578] <DFU Device 0BA2A9D8>: operation 0 progress 47
    [13:47:34.0593] <DFU Device 0BA2A9D8>: operation 0 progress 48
    [13:47:34.0624] <DFU Device 0BA2A9D8>: operation 0 progress 49
    [13:47:34.0640] <DFU Device 0BA2A9D8>: operation 0 progress 50
    [13:47:34.0671] <DFU Device 0BA2A9D8>: operation 0 progress 51
    [13:47:34.0687] <DFU Device 0BA2A9D8>: operation 0 progress 52
    [13:47:34.0702] <DFU Device 0BA2A9D8>: operation 0 progress 53
    [13:47:34.0734] <DFU Device 0BA2A9D8>: operation 0 progress 54
    [13:47:34.0749] <DFU Device 0BA2A9D8>: operation 0 progress 55
    [13:47:34.0780] <DFU Device 0BA2A9D8>: operation 0 progress 56
    [13:47:34.0796] <DFU Device 0BA2A9D8>: operation 0 progress 57
    [13:47:34.0812] <DFU Device 0BA2A9D8>: operation 0 progress 58
    [13:47:34.0843] <DFU Device 0BA2A9D8>: operation 0 progress 59
    [13:47:34.0858] <DFU Device 0BA2A9D8>: operation 0 progress 60
    [13:47:34.0890] <DFU Device 0BA2A9D8>: operation 0 progress 61
    [13:47:34.0905] <DFU Device 0BA2A9D8>: operation 0 progress 62
    [13:47:34.0921] <DFU Device 0BA2A9D8>: operation 0 progress 63
    [13:47:34.0952] <DFU Device 0BA2A9D8>: operation 0 progress 64
    [13:47:34.0968] <DFU Device 0BA2A9D8>: operation 0 progress 65
    [13:47:34.0999] <DFU Device 0BA2A9D8>: operation 0 progress 66
    [13:47:35.0014] <DFU Device 0BA2A9D8>: operation 0 progress 67
    [13:47:35.0030] <DFU Device 0BA2A9D8>: operation 0 progress 68
    [13:47:35.0061] <DFU Device 0BA2A9D8>: operation 0 progress 69
    [13:47:35.0077] <DFU Device 0BA2A9D8>: operation 0 progress 70
    [13:47:35.0108] <DFU Device 0BA2A9D8>: operation 0 progress 71
    [13:47:35.0124] <DFU Device 0BA2A9D8>: operation 0 progress 72
    [13:47:35.0139] <DFU Device 0BA2A9D8>: operation 0 progress 73
    [13:47:35.0170] <DFU Device 0BA2A9D8>: operation 0 progress 74
    [13:47:35.0186] <DFU Device 0BA2A9D8>: operation 0 progress 75
    [13:47:35.0217] <DFU Device 0BA2A9D8>: operation 0 progress 76
    [13:47:35.0233] <DFU Device 0BA2A9D8>: operation 0 progress 77
    [13:47:35.0248] <DFU Device 0BA2A9D8>: operation 0 progress 78
    [13:47:35.0280] <DFU Device 0BA2A9D8>: operation 0 progress 79
    [13:47:35.0295] <DFU Device 0BA2A9D8>: operation 0 progress 80
    [13:47:35.0326] <DFU Device 0BA2A9D8>: operation 0 progress 81
    [13:47:35.0342] <DFU Device 0BA2A9D8>: operation 0 progress 82
    [13:47:35.0358] <DFU Device 0BA2A9D8>: operation 0 progress 83
    [13:47:35.0389] <DFU Device 0BA2A9D8>: operation 0 progress 84
    [13:47:35.0404] <DFU Device 0BA2A9D8>: operation 0 progress 85
    [13:47:35.0436] <DFU Device 0BA2A9D8>: operation 0 progress 86
    [13:47:35.0451] <DFU Device 0BA2A9D8>: operation 0 progress 87
    [13:47:35.0467] <DFU Device 0BA2A9D8>: operation 0 progress 88
    [13:47:35.0498] <DFU Device 0BA2A9D8>: operation 0 progress 89
    [13:47:35.0514] <DFU Device 0BA2A9D8>: operation 0 progress 90
    [13:47:35.0529] <DFU Device 0BA2A9D8>: operation 0 progress 91
    [13:47:35.0560] <DFU Device 0BA2A9D8>: operation 0 progress 92
    [13:47:35.0576] <DFU Device 0BA2A9D8>: operation 0 progress 93
    [13:47:35.0607] <DFU Device 0BA2A9D8>: operation 0 progress 94
    [13:47:35.0623] <DFU Device 0BA2A9D8>: operation 0 progress 95
    [13:47:35.0638] <DFU Device 0BA2A9D8>: operation 0 progress 96
    [13:47:35.0670] <DFU Device 0BA2A9D8>: operation 0 progress 97
    [13:47:35.0685] <DFU Device 0BA2A9D8>: operation 0 progress 98
    [13:47:35.0716] <DFU Device 0BA2A9D8>: operation 0 progress 99
    [13:47:35.0716] WinDFU::UploadData: EOF, cbRead: 1116
    [13:47:35.0732] <DFU Device 0BA2A9D8>: operation 0 progress 100
    [13:47:35.0732] WinDFU::UploadData: ZLP
    [13:47:35.0748] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
    [13:47:35.0748] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
    [13:47:35.0748] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
    [13:47:35.0748] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
    [13:47:38.0758] WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
    [13:47:38.0758] WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
    [13:47:38.0758] WinDFU::ResetDevice: resetting...
    [13:47:38.0836] WinDFU::FinalizeDfuUpdate: success
    [13:47:38.0836] <DFU Device 0BA2A9D8>: DFU succeeded
    [13:47:38.0836] Finished DFU Restore Phase: Successful
    [13:47:39.0039] DFU mode device disconnected
    [13:47:39.0039] Device removed when in state Restoring, moving device to transition state
    [13:47:39.0039] Changing state from 'Restoring' to 'Transitioning'
    [13:47:39.0039] Creating timer to monitor transition
    [13:47:41.0674] Recovery mode device connected
    [13:47:41.0674] Transitioning device returned, continuing restore.
    [13:47:41.0674] Canceling timer
    [13:47:41.0674] Changing state from 'Transitioning' to 'Restoring'
    [13:47:41.0684] requested restore behavior: Erase
    [13:47:41.0684] requested variant: Erase
    [13:47:41.0684] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [13:47:42.0512] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [13:47:42.0528] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
    [13:47:42.0528] iBoot build-version = iBoot-1940.10.58
    [13:47:42.0528] iBoot build-style = RELEASE
    [13:47:42.0528] requested restore behavior: Erase
    [13:47:42.0528] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0528] requested restore behavior: Erase
    [13:47:42.0528] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0543] unable to open device_map.txt: No such file or directory
    [13:47:42.0543] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:42.0543] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:42.0543] AMDeviceIoControl: GetOverlappedResult failed
    [13:47:42.0543] AMDeviceIoControl: pipe stall
    [13:47:42.0543] USBControlTransfer: error 31, usbd status c0000004
    [13:47:42.0543] command device request for 'getenv radio-error' failed: 2008
    [13:47:42.0543] radio-error not set
    [13:47:42.0543] unable to open device_map.txt: No such file or directory
    [13:47:42.0543] <Recovery Mode Device 0555AEB8>: production fused device
    [13:47:42.0543] requested restore behavior: Erase
    [13:47:42.0543] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0543] requested restore behavior: Erase
    [13:47:42.0543] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0543] interface has 1 endpoints, file pipe = 1
    [13:47:42.0543]
    [13:47:42.0543] <Recovery Mode Device 0555AEB8>: operation 4 progress -1
    [13:47:42.0606] unable to open device_map.txt: No such file or directory
    [13:47:42.0606] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:42.0606] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:42.0606] requested restore behavior: Erase
    [13:47:42.0606] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0606] requested restore behavior: Erase
    [13:47:42.0606] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:42.0606] <Recovery Mode Device 0555AEB8>: operation 42 progress -1
    [13:47:42.0606] requested restore behavior: Erase
    [13:47:42.0621] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:43.0651] <Recovery Mode Device 0555AEB8>: operation 5 progress -1
    [13:47:43.0994] unable to open device_map.txt: No such file or directory
    [13:47:43.0994] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:43.0994] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:43.0994] AMDeviceIoControl: GetOverlappedResult failed
    [13:47:43.0994] AMDeviceIoControl: pipe stall
    [13:47:43.0994] USBControlTransfer: error 31, usbd status c0000004
    [13:47:43.0994] command device request for 'getenv ramdisk-delay' failed: 2008
    [13:47:45.0616] <Recovery Mode Device 0555AEB8>: operation 6 progress -1
    [13:47:46.0630] <Recovery Mode Device 0555AEB8>: operation 7 progress -1
    [13:47:46.0942] <Recovery Mode Device 0555AEB8>: operation 8 progress -1
    [13:47:46.0958] unable to open device_map.txt: No such file or directory
    [13:47:46.0958] found device map entry for 0x00008950 0x00000002. boardConfig=n42ap platform=s5l8950x
    [13:47:46.0958] _AMRestoreCopyDeviceMapPlistEntryForHardware: firmwareDirectory not in options
    [13:47:46.0958] <Recovery Mode Device 0555AEB8>: operation 9 progress -1
    [13:47:46.0958] <Recovery Mode Device 0555AEB8>: Recovery mode succeeded
    [13:47:46.0958] Finished Recovery Restore Phase: Successful
    [13:47:48.0409] Recovery mode device disconnected
    [13:47:48.0409] Device removed when in state Restoring, moving device to transition state
    [13:47:48.0409] Changing state from 'Restoring' to 'Transitioning'
    [13:47:48.0409] Creating timer to monitor transition
    [13:47:52.0895] RestoreOS mode device connected
    [13:47:52.0895] Transitioning device returned, continuing restore.
    [13:47:52.0905] Canceling timer
    [13:47:52.0905] Changing state from 'Transitioning' to 'Restoring'
    [13:47:52.0905] <Restore Device 05577800>: operation 44 progress -1
    [13:47:52.0905] requested restore behavior: Erase
    [13:47:52.0905] requested variant: Erase
    [13:47:52.0905] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreKernelCache"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreRamDisk"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBEC"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "KernelCache"
    [13:47:53.0777] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
    [13:47:53.0792] amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
    [13:47:53.0792] requested restore behavior: Erase
    [13:47:53.0792] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:53.0792] device did not return saved USB log
    [13:47:53.0792] device did not return saved panic log
    [13:47:53.0792] previous restore failed with exit status 0x100
    [13:47:53.0792] connected to service com.apple.mobile.restored
    [13:47:53.0808] using protocol version 13
    [13:47:53.0808] unable to open device_map.txt: No such file or directory
    [13:47:53.0808] board config = n42ap
    [13:47:53.0808] no value returned for BootArgs
    [13:47:53.0824] _copyDeviceProperty() failed for restore bootargs
    [13:47:53.0824] no value returned for MarketingPartNumber
    [13:47:53.0824] _copyDeviceProperty() failed for mpn
    [13:47:53.0824] requested restore behavior: Erase
    [13:47:53.0824] amai: AMAuthInstallBundleCopyBuildIdentityForVariant: No baseband chipid reported. Will match Build Identity based on ap chipid and boardid only.
    [13:47:53.0839] value query for 'HardwareModel' returned 'N42AP'
    [13:47:53.0839] <Restore Device 05577800>: operation 28 progress -1
    [13:48:10.0360] previous restore failed: re:INF@ 145] created partition 1 as 'Effaceable'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 2 as 'NVRAM'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 3 as 'Firmware'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 4 as 'Filesystem'
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 4
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 5 as 'System Config'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 6 as 'Diagnostic Data'
    [13:48:10.0360] [nand_part_core:INF@ 145] created partition 7 as 'Bad Block Table'
    [13:48:10.0360] com.apple.AppleFSCompressionTypeZlib load succeeded
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 7
    [13:48:10.0360] AppleSamsungSerial: Identified Serial Port on ARM Device=uart1 at 0x32600000(0x82cc6000)
    [13:48:10.0360] L2TP domain init
    [13:48:10.0360] L2TP domain init complete
    [13:48:10.0360] PPTP domain init
    [13:48:10.0360] AppleSwissPPNFTL started with IOFlashStoragePartition provider
    [13:48:10.0360] [NAND] _FindFlashMediaAndKeepout:601 physical nand block offset 1
    [13:48:10.0360] AppleNANDFTL registered[NAND] start:356 this 0x85e41800 PROVIDER=0x85f2a400 flashMedia=0x85f2a400
    [13:48:10.0360] [NAND] WMR_Start:149 Apple PPN NAND Driver, Read/Write
    [13:48:10.0360] [NAND] WMR_Start:174 FIL_Init  [OK]
    [13:48:10.0360] AppleSamsungSerial: Identified Serial Port on ARM Device=uart3 at 0x32800000(0xde3b4000)
    [13:48:10.0360] virtual bool AppleDisplayPipe::start_hardware(IOService *), auto-detect chip
    [13:48:10.0360] [NAND] WMR_Open:371 VFL_Open    [OK]
    [13:48:10.0360] Scaler 0 enableDeviceClock(true,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 0 enableDeviceClock(true,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 0 enableDevicePower(true,0,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 0 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] void AppleDisplayPipe::setupVideoDownscalingLimits(): minimum-frequency property not found, using getClockFrequency(0) instead.
    [13:48:10.0360] Scaler 1 enableDeviceClock(true,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 1 enableDeviceClock(true,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 1 enableDevicePower(true,0,HALF_CLOCK_INDEX) = 0x0
    [13:48:10.0360] Scaler 1 enableDeviceClock(false,FULL_CLOCK_INDEX) = 0x0
    [13:48:10.0360] AppleMultitouchN1SPI: successfully started
    [13:48:10.0360] AppleH4CamIn::start - back camera expected
    [13:48:10.0360] AppleH4CamIn::start - front camera expected
    [13:48:10.0360] AppleH4CamIn::power_off_hardware
    [13:48:10.0360] AppleAP3DSH::probe found device with ID: 0x3f
    [13:48:10.0360] AppleAP3DSH::handleStart _calibrationMatrix [64699 -1892 -370] [-1570 65035 -244] [849 465 63854]
    [13:48:10.0360] AppleAP3DSH::handleStart _calibrationOffsets [518853 -714699 -1661621]
    [13:48:10.0360] AppleAP3DSH::handleStart - No calibration inverse matrix or the data is invalid, Compute locally
    [13:48:10.0360] AppleAP3DSH::handleStart _calibrationInverseMatrix [66427 1929 393] [1599 66087 261] [-895 -507 67257]
    [13:48:10.0360] AppleAP3DSH::handleStart _odr400HzSampleInterval = 2440
    [13:48:10.0360] AppleH4CamIn::setPowerStateGated: 0
    [13:48:10.0360] AppleCS35L19Amp: could not allocate control 395
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 1
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType USBHost
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 0
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType Detached
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
    [13:48:10.0360] AppleMultitouchN1SPI: detected HBPP. driver will be kept alive
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableDetect 1
    [13:48:10.0360] AppleD1972PMUPowerSource: AppleUSBCableType USBHost
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_handleUSBCableConnect cable connected, but don't have device configuration yet
    [13:48:10.0360] display-scale = 2
    [13:48:10.0360] display-rotation = 0
    [13:48:10.0360] found applelogo at /usr/share/progressui/[email protected]
    [13:48:10.0360] found display: primary
    [13:48:10.0360] display: 640 x 1136
    [13:48:10.0360] found PTP interface
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: iPod USB Interface
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: USBAudioControl
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: USBAudioStreaming
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: IapOverUsbHid
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: AppleUSBMux
    [13:48:10.0360] AppleSynopsysOTGDevice - Configuration: PTP + Apple Mobile Device + Apple USB Ethernet
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: PTP
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: AppleUSBMux
    [13:48:10.0360] AppleSynopsysOTGDevice          Interface: AppleUSBEthernet
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioControl
    [13:48:10.0360] IOAccessoryPortUSB::start
    [13:48:10.0360] virtual bool AppleUSBDeviceMux::start(IOService *) build: Jun 11 2014 20:11:28
    [13:48:10.0360] init_waste
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBMux
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function USBAudioStreaming
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function IapOverUsbHid
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function AppleUSBEthernet
    [13:48:10.0360] AppleSynopsysOTGDevice::gated_registerFunction Register function PTP
    [13:48:10.0360] AppleSynopsysOTGDevice::startUSBStack Starting usb stack
    [13:48:10.0360] IOReturn AppleUSBDeviceMux::setPropertiesGated(OSObject *) setting debug level to 7
    [13:48:10.0360] AppleBCMWLANCore::init(): IO80211-46 Jun 11 2014 20:10:03
    [13:48:10.0360] [NAND] WMR_Open:420 FTL_Open    [OK]
    [13:48:10.0360] [NAND] _publishServices:642 FTL capabilities: 0x00000001
    [13:48:10.0360] [NAND] _ppnvflGetStruct:3469 Checking borrowed blocks - count: 23 max_count: 23
    [13:48:10.0360] [NAND] _fetchBorrowedList:881 number of borrowed blocks 16
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 0
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 1
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 2
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 3
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 5
    [13:48:10.0360] [nand_part_core:INF@ 157] published partition 6
    [13:48:10.0360] 000828.945879 wlan.N[0] AppleBCMWLANCore::start(): Starting with MAC Address: <<<mac address>>>
    [13:48:10.0360] 000828.946182 wlan.N[1] AppleBCMWLANCore::setPowerStateGated():   powerState 1, fStateFlags 0x20, dev 0xc476b000 (this 1, provider 0)
    [13:48:10.0360] 000828.946197 wlan.N[2] AppleBCMWLANCore::setPowerStateGated():  Received power state change before driver has initialized, ignoring
    [13:48:10.0360] IO80211Peer::addPhyStatistics Phy stats started for addr <<<mac address>>>
    [13:48:10.0360] IO80211Peer::addPhyStatistics Tx Completion stats started for addr <<<mac address>>>
    [13:48:10.0360] IO80211PeerManager::initWithInterface cant add monitoring timer
    [13:48:10.0360] Started logging for intf
    [13:48:10.0360] IO80211PeerManager::initWithInterface: inited peer manager
    [13:48:10.0360] IO80211Interface::init peerManager=0x87cb8800
    [13:48:10.0360] start:156
    [13:48:10.0360] start:156
    [13:48:10.0360] AppleARMBacklight::start: No AAP function
    [13:48:10.0360] [effaceable:INIT] found current generation, 90, in group 1
    [13:48:10.0360] [effaceable:INIT] started
    [13:48:10.0360] [effaceable:INIT] started
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49152 62078<-usb->4608
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49153 62078<-usb->4864
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888adec8 established 62078<-lo0->49154 62078<-usb->5120
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade18 established 62078<-lo0->49155 62078<-usb->5376
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888adec8
    [13:48:10.0360] recv(13, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade18
    [13:48:10.0360] recv(14, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade18 established 62078<-lo0->49156 62078<-usb->5632
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49157 62078<-usb->5888
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49158 62078<-usb->6144
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49159 62078<-usb->6400
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49160 62078<-usb->6656
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49161 62078<-usb->6912
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49162 62078<-usb->7168
    [13:48:10.0360] unrecognized key 'BootArgs' in value query
    [13:48:10.0360] failed to handle value query for key 'BootArgs', sending back empty response
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49163 62078<-usb->7424
    [13:48:10.0360] unrecognized key 'MarketingPartNumber' in value query
    [13:48:10.0360] failed to handle value query for key 'MarketingPartNumber', sending back empty response
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] AppleUSBDeviceMux::handleConnectResult new session 0x888ade70 established 62078<-lo0->49164 62078<-usb->7680
    [13:48:10.0360] void AppleUSBDeviceMux::handleMuxTCPInput(mbuf_t) received reset, closing 0x888ade70
    [13:48:10.0360] recv(9, 4) failed: connection closed
    [13:48:10.0360] unable to read message size: -1
    [13:48:10.0360] could not receive message
    [13:48:10.0360] client protocol version 13
    [13:48:10.0360] *** UUID 4B2AC217-7071-EC47-8945-EB5E2188BE49 ***
    [13:48:10.0360] Restore options:
    [13:48:10.0360]  UUID                           => <CFString 0x19315c0 [0x2f3ad0]>{contents = "4B2AC217-7071-EC47-8945-EB5E2188BE49"}
    [13:48:10.0360]  MinimumSystemPartition         => <CFNumber 0x1931510 [0x2f3ad0]>{value = +1660, type = kCFNumberSInt64Type}
    [13:48:10.0360]  SystemPartitionSize            => <CFNumber 0x1930f50 [0x2f3ad0]>{value = +1660, type = kCFNumberSInt64Type}
    [13:48:10.0360]  SystemPartitionPadding         => <CFBasicHash 0x192f3c0 [0x2f3ad0]>{type = mutable dict, count = 5,
    [13:48:10.0360] entries =>
    [13:48:10.0360]  2 : <CFString 0x1931540 [0x2f3ad0]>{contents = "128"} = <CFNumber 0x1931570 [0x2f3ad0]>{value = +1280, type = kCFNumberSInt64Type}
    [13:48:10.0360]  3 : <CFString 0x1930f20 [0x2f3ad0]>{contents = "16"} = <CFNumber 0x192f3f0 [0x2f3ad0]>{value = +160, type = kCFNumberSInt64Type}
    [13:48:10.0360]  4 : <CFString 0x192ede0 [0x2f3ad0]>{contents = "32"} = <CFNumber 0x1931250 [0x2f3ad0]>{value = +320, type = kCFNumberSInt64Type}
    [13:48:10.0360]  5 : <CFString 0x1931960 [0x2f3ad0]>{contents = "8"} = <CFNumber 0x192ed50 [0x2f3ad0]>{value = +80, type = kCFNumberSInt64Type}
    [13:48:10.0360]  8 : <CFString 0x1931180 [0x2f3ad0]>{contents = "64"} = <CFNumber 0x1931950 [0x2f3ad0]>{value = +640, type = kCFNumberSInt64Type}
    [13:48:10.0360] }
    [13:48:10.0360]
    [13:48:10.0360] entering load_sep_os
    [13:48:10.0360] device has no sep
    [13:48:10.0360] entering partition_nand_device
    [13:48:10.0360] device supports boot-from-NAND
    [13:48:10.0360] nand device is already partitioned
    [13:48:10.0360] entering wait_for_storage_device
    [13:48:10.0360] Searching for NAND service
    [13:48:10.0360] Found NAND service: IOFlashStoragePartition
    [13:48:10.0360] NAND initialized. Waiting for devnode.
    [13:48:10.0360] entering clear_remap_variable
    [13:48:10.0360] executing /usr/sbin/nvram
    [13:48:10.0360] entering format_effaceable_storage
    [13:48:10.0360] effaceable storage is formatted, clearing it
    [13:48:10.0360] effaceable storaged cleared
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] AppleD1972PMUPowerSource: limiting USB input current to 390 mA (measured 462 mA)
    [13:48:10.0360] ** /dev/rdisk0s1s1
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is Sochi11D257.N42OS
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume Sochi11D257.N42OS appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
    [13:48:10.0360] entering check_for_restore_log
    [13:48:10.0360] found restore log (size = 28347)
    [13:48:10.0360] entering unmount_filesystems
    [13:48:10.0360] error unmounting '/mnt2': Invalid argument
    [13:48:10.0360] entering clean_NAND
    [13:48:10.0360] NAND format complete
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0 system= data=
    [13:48:10.0360] entering format_storage_for_LwVM
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] unexpected partition 'LwVM' - skipping
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system= data=
    [13:48:10.0360] entering create_filesystem_partitions
    [13:48:10.0360] User specified system partition size, skipping firmware extras size.
    [13:48:10.0360] system partition padding size is: 167772160 bytes
    [13:48:10.0360] unable to open : No such file or directory
    [13:48:10.0360] creating 2 partitions
    [13:48:10.0360] creating encrypted data partition
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] wipe entire partition: 1 (old = 0 new = 1820)
    [13:48:10.0360] block size for /dev/disk0s1s1: 4096
    [13:48:10.0360] /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] executing /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
    [13:48:10.0360] block size for /dev/disk0s1s2: 4096
    [13:48:10.0360] /sbin/newfs_hfs -s -v Data -J -P /dev/disk0s1s2
    [13:48:10.0360] executing /sbin/newfs_hfs -s -v Data -J -P /dev/disk0s1s2
    [13:48:10.0360] Initialized /dev/rdisk0s1s2 as a 13 GB case-sensitive HFS Plus volume with a 8192k journal
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] entering mount_filesystems
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] ** /dev/rdisk0s1s1
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is System
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume System appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] ** /dev/rdisk0s1s2
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is Data
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume Data appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s2 mounted on /mnt2
    [13:48:10.0360] entering resize_system_partition_to_options
    [13:48:10.0360] User specified system partition size, skipping firmware extras size.
    [13:48:10.0360] Found SystemPartitionPadding value of 167772160 bytes
    [13:48:10.0360] Erasing system partition prior to resize operation.
    [13:48:10.0360] block size for /dev/disk0s1s1: 4096
    [13:48:10.0360] /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] executing /sbin/newfs_hfs -s -v System -J /dev/disk0s1s1
    [13:48:10.0360] Initialized /dev/rdisk0s1s1 as a 2 GB case-sensitive HFS Plus volume with a 8192k journal
    [13:48:10.0360] executing /sbin/fsck_hfs
    [13:48:10.0360] ** /dev/rdisk0s1s1
    [13:48:10.0360]    Executing fsck_hfs (version hfs-277.10.5).
    [13:48:10.0360] ** Checking Journaled HFS Plus volume.
    [13:48:10.0360] ** Detected a case-sensitive volume.
    [13:48:10.0360]    The volume name is System
    [13:48:10.0360] ** Checking extents overflow file.
    [13:48:10.0360] ** Checking catalog file.
    [13:48:10.0360] ** Checking multi-linked files.
    [13:48:10.0360] ** Checking catalog hierarchy.
    [13:48:10.0360] ** Checking extended attributes file.
    [13:48:10.0360] ** Checking volume bitmap.
    [13:48:10.0360] ** Checking volume information.
    [13:48:10.0360] ** Trimming unused blocks.
    [13:48:10.0360] ** The volume System appears to be OK.
    [13:48:10.0360] executing /sbin/mount_hfs
    [13:48:10.0360] mount_hfs: Could not create property for re-key environment check: No such file or directory
    [13:48:10.0360] /dev/disk0s1s1 mounted on /mnt1
    [13:48:10.0360] Trying to resize system partition to 1908408320 bytes aka 1820 MB
    [13:48:10.0360] entering adjust_partition_preflight
    [13:48:10.0360] partition:0 requiredSize=465920
    [13:48:10.0360] no change in size
    [13:48:10.0360] Successfully resized the system partition
    [13:48:10.0360] entering maximize_data_partition
    [13:48:10.0360] entering adjust_partition_preflight
    [13:48:10.0360] partition:1 requiredSize=<<<<<IMEI>>>>>>6
    [13:48:10.0360] maximizing data partition to 13946060799 bytes
    [13:48:10.0360] entering adjust_partition_preflight
    [13:48:10.0360] partition:1 requiredSize=3404800
    [13:48:10.0360] no change in size
    [13:48:10.0360] Successfully resized data partition to consume free blocks
    [13:48:10.0360] The system partition now has a total HFS+ capacity of 1820 MB
    [13:48:10.0360] entering ramrod_probe_media
    [13:48:10.0360] device partitioning scheme is GPT
    [13:48:10.0360] find_filesystem_partitions: storage=/dev/disk0s1 system=/dev/disk0s1s1 data=/dev/disk0s1s2
    [13:48:10.0360] entering unmount_filesystems
    [13:48:10.0360] entering ramrod_ticket_update
    [13:48:10.0360] looking up root ticket hash
    [13:48:10.0360] device tree ticket-hash: <CFData 0x1930040 [0x2f3ad0]>{length = 20, capacity = 20, bytes = 0x<<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>}
    [13:48:10.0360] ticket_hash: <<<<<<<<<<<<<<<<<<UDID>>>>>>>>>>>>>>>>>>
    [13:48:10.0360] received valid ticket (2741 bytes)
    [13:48:10.0360] entering restore_images
    [13:48:10.0360] Successfully marked device node /dev/rdisk0s1s1 as static data
    [13:48:10.0360] executing /usr/sbin/asr -source asr://localhost:12345 -target /dev/disk0s1s1 -erase -noprompt --chunkchecksum --puppetstrings
    [13:48:10.0360] void AppleUSBDeviceMux::handleConnectResult(struct BulkUSBMuxSession *, errno_t) new session to port 12345 failed: 61
    [13:48:10.0360] void AppleUSBDeviceM

    Hello gamavranje,
    Thanks for using Apple Support Communities.
    The icons you're seeing on your iPhone indicate it is in recovery mode.  Please plug your iPhone into your computer, and restore it with iTunes.
    If you can't update or restore your iOS device
    http://support.apple.com/kb/HT1808
    Use iTunes to restore your iOS device to factory settings
    http://support.apple.com/kb/HT1414
    Take care,
    Alex H.

  • Power supply needed for MS-7220 (Diamond Plus) and others.

     
    The following statement is taken form the K8B Diamond Plus Manual.
    For ATX 12V power connection, it should be greater than 18A.
    If I am interpreting correctly, the ATX 12V connector should have dedicated to it a minimum of 18A.
    My first, question is if the Power Supply has two or more rails, how do you know the power dedicated to the ATX 12 connector on the Power Supply?
    Second, if a +12V rail is not dedicated the connector, how do you know what is connected to each rail of the Power Supply?
    This maybe the source of why many are saying, they have more stable system performance when using single rail Power Supplies.
    I have tried eleven different manufactures to get more detailed Power Supply specifications, but no responses; today through February 1st is the Chinese New Year.
    Those of you running the K8B Diamond Plus, what are you using for Power Supplies and are you having any instability problem?
    One thing I did find curious was that going the manuals and in most all of the newer Socket 939 motherboards have this specification, but nothing in the motherboards specifications of on the MSI Web Site about this required and the are a lot of 500-600 Watt power supplies sold that do not meet this specification.
    The statement Total Wattage does not mean a thing has even more meaning to me now.
    Are we going to have to know the Current Rating of each cable on the output of a Power Supply now to insure we are purchasing the correct Power Supply?
    Roger

    Roger
    Ihave a Tagan 580w U22 with switchable dual/combined +12v rails and it is very stable,set it combined for 35a.
    Only thing to ponder was the 4/8 pin +12v/p4 connector,power supply has the correct split 2x4pin connectors so does the board but there is a little removable cover over 4 pins,so thinking MSI fitted it there for a reason I have fitted only one 4 pin connector,no problems as yet.
    Think you may well have a point re the 18a.
    I have just given my son my old sli platinum/cpu/heatsink/ram/vga card,this setup ran  250/11/4 @ 1.4v & ram 2.5 3 3 7 1.1 @ 2.75v with the Tagan.this setup now fitted in his case but with a dual 18a rail Enermax and he can't o/c stable to the old settings.Case has better cooling than the wavemaster it all came from.
    Dont think the enermax is bad just that it supplies the power a different way.
    Regards
    Rossoevo

  • Sending command strings to a Sorensen (Ametek / Xantrex) power supply model XDL 35-5TP

    Hi all,
    I am using the above mentioned power suply to control test units during end of line tests.  I can do all the normal funtions through the manufacturers supplied library of vi's.  The problem is, I need to make sure the voltage being seen by the unit under test is correct and therefor am using the remote sense function on the power supply.  Essentially this runs a pair of sense leads to the point of measurement and allows the power supply to compensate for any voltage drop that is seen in the circuit.
    As I am on the downstream side of a solid state relay with the sense leads, I need to cycle the remote sense function so that it is not trying to compensate when the SSR is off (sense would read zero volts and try to run the voltage up to compensate for what it sees as a loss)
    The attached diagram shows how I am trying to send the command using the supplied Write Data vi but the power supply never responds to the command.  I have tried different commands with no success and am hoping there is someone that has run across this to give me a hint as to what I am doing wrong.
    Any assistance is much appeciated
    Doug
    Doug
    "My only wish is that I am capable of learning each and every day until my last breath."
    Attachments:
    Powersupplyvi.pdf ‏102 KB

    Code is attached including the TQLP library.  The manual states that white space (spaces) are ignored so it does not matter if they are present or not.  I will include that section of the manual as well and near the end of that it shows the syntax for the SENSE command that I am trying to use.
    Doug
    "My only wish is that I am capable of learning each and every day until my last breath."
    Attachments:
    Xantrex XDL Driver.vi ‏28 KB
    TQLP.LLB ‏761 KB
    Pages 39-42 from M370293-01_XDL_35-5-triple.pdf ‏110 KB

  • Problem with NEW H520 when installed new power supply & graphic card. Please help!

    My H520 was working perfectly and was running FAST..especially when rebooting. ( It was AWESOME!  )Then I installed a new power supply (Coolmax 400w) and a new graphic card (Sapphire Radeon HD6450) and then everything changed.  Now my computer is booting very SLOWLY and all the programs are taking a long time to load too.  I was getting a black screen for almost a full 2 minutes before the windows 8.0 screen would finally load up and then it hangs there for a few seconds and finally goes to the start screen in windows.  But BEFORE I installed this new hardware, when I would reboot, I would see the Lenovo splash screen come up for a few short seconds and then it instantly went to the windows welcome screen.  And even then I would barely have enough time to see the welcome screen before it instantly loaded into the windows start screen.  Everything would load up fast on the desktop too and we'd be good to go. It all took about 30 SECONDS. 
    But now? It takes MINUTES to get everything going.   After it FINALLY loads up (it takes almost 2 full minutes now!), everything hangs up.  When you first click on the desktop, it takes a few seconds for all of the icons to pop up.  Before I loaded the new hardware, everything loaded up instantly.  I didn't even see the icons load because they were already there.  But now I have to wait for them to load up before I can even see them.  And it's like that with every program and web browser I try to use now.  Everything hangs up at first and then finally loads.  The programs work but they are sluggish.
    So I uninstalled the new power supply and put back in the original 280w power supply and I took out the graphic card but it did no change.  The machine is STILL running slow on everything it does and booting very slowly.
    I have seen this problem mentioned elsewhere about Lenovo computers but there is never a solution.  Please help!  It took me a long time to save up for this computer and I have been babying it ever since.  I will never be able to afford a new one or pay for tech repair.  I need to fix this!    I was so thrilled with this computer before the hardware upgrade. This is devastating to me that it is working so poorly now when all I was trying to do was upgrade it a little bit.     Now it's performing horribly and it's only 6 months old. 
    I ran a four hour test on the hard drive and it is fine.  I ran all the system clean ups, optimizations, registry cleanups, windows disk cleaner, defragger and virus scans. Nothing is showing up as not working but there is CLEARLY a problem.  It was never this slow.   And why is it STILL acting this slow even after I uninstalled all of the new hardware that made it start acting this way and went back to the original setup?
    I'm trying to run a memory test on it now but the BIOS will NOT allow me to select another drive to boot from so I can't boot from the flash drive or CD drive to run the memory test.  I have NO IDEA what to do next and I am starting to pull my hair out in frustration.
    Please, is there anything that can be done to make it better again?
    Any help would be HUGELY appreciated.    Thank you!
    Sincerely,
    Jennifer

    I totally give up!!  I restored everything to the ORIGINAL state with drivers AND hardware and STILL everything is not working properly like it was BEFORE the upgrade.
    So this has been the WORST experience with Tech support EVER!!  I have spent DAYS on the phone for HOURS with these technicians and nobody seems to know what they are doing.  They put me on hold every 10 minutes and are gone for 10 to 15 minutes and when they come back, they seem all set on a new solution but when you ask them questions about it, they have NO CLUE how to answer and then they put you on hold again.  Nothing gets solved and after HOURS on the phone, I just tell them to stop because we are getting no where but running around in circles that make no sense.    THIS A NIGHTMARE!!
    So I totally gave up on being able to upgrade this machine.  To any future buyers, I STRONGLY recommend you do all upgrading BEFORE you get it home for the first time.  Make sure you have your power supply and graphic card INCLUDED before you bring it home or you're mostly likely going to have a NIGHTMARE upgrading it later.    Technical support is a HORROR STORY and expect to be WAITING for LOOOOONNNNG periods of time both ON THE PHONE and ONLINE and probably ending up with NO SOLUTION in the end. 
    I've VERY upset with how this turned out!!  I'm just gonna have to deal with the fact that my computer is permenantly messed up and NOBODY AT LENOVO knows how to fix it.    So I'm stuck. 
    I decided to send back the new power supply and the new graphic card because of this nightmare with tech support.  I put everything back to the way it was when I bought the computer and it is STILL acting up!!  I just want to revert it back to factory settings .. INCLUDING THE BIOS... but Lenovo said I have to send the WHOLE computer back to them to do that.  All I can do from home is restore from a point in the hard drive and that's not enough.  I need a TOTAL CLEAN INSTALL.  Everything needs to be wiped out and reset, not just restored to a previous restore point.  I've done this multiple times and all it does is erase all the programs and stuff I put on the computer.  The drivers and other codes are still the same.  And then bugs come up and things get all wonky.  I NEVER HAD THIS PROBLEM BEFORE I TRIED TO UPGRADE IT!!
    I am NOT comfortable with Lenovo's "solution". I do NOT want to send my computer back to them for them to reset it with factory disks ESPECIALLY when they stated that they are NOT responsible for any damage in transport or otherwise. I have to buy extra packaging to make sure it gets there safely. They told me to use the original box and packaging, that is the only way they can be sure it will get there safe.  Who has the original stuffing SIX MONTHS LATER?!?! I don't want to be sending my computer across the country to get jostled all over the place and have that add to the slowness of the hardware because it was jostled.
    Can't I reset it from home?  Can they not send ME the disks instead of me sending my whole computer to them?
    I'm so incredibly frustrated with this.  I hope somebody answers quickly and that I don't have to wait DAYS to get a response again. 
    I absolutely LOVED my Lenovo computer!  And then I tried to upgrade it.  BIG MISTAKE!!  Now everything is totally messed up and Lenovo's customer support for technical problems is HORRID!!
    Somebody please help.  This is driving me crazy with frustration and totally breaking my heart.  It took me a VERY long time to save up for this computer and it was my most loved possession.  It was a reward for a lot of hard times and now it's all broken and acting slow.  And it's only 6 months old.  
    Is there a solution to this very frustrating problem?
    I just want it to go back to the way it was before. 
    And is there a very low cost KNOWN TO WORK WITH THIS MACHINE upgraded graphic card and power supply?  Is there a very specific brand and make?  If so, could you let me know what it is in case I try to upgrade it again someday?
    Thank you for your time and for reading this! 
    Please have a FANTASTIC day today!!
    ~Jennifer~

  • Looking for a new quiet power supply, what do you recommend?

    the current power supply rip was an antec 480 truepower. It was ok but I'm looking for an ultra quiet supply, hope to here your recommendations. TIA.

     Jason, I think he would have some trouble getting them shipped to Australia from one of those stores. Beside that it would be less from newegg, look at the additional 20% off promo and free shipping. For me it's 3 days from order to delivery from ZZf and newegg.
     Yes, one of the Corsairs but not HX but as mentioned TX or VX, also PC P&C 610. Ignore watts, go by +12V amps and as FP mentioned consider future need for more power when choosing. Nowdays the VX450W (+12V~33A) would be considered minimum to get and also would be considered weak for many current systems.

  • IMac broken, Power Supply replacement?

    My 13 months iMac G5 20" 2GHz shut down all the time.. mostly within 10 minutes after booting.
    A friend of mine had the same problem 2 months ago. Apple replaced his Power Supply for free since the guaranty is 12 months.
    My machine is one month past guaranty, 13 months old and therefor Apple wants $200 to fix my computer!!
    As I can see my iMac ain't covered by the iMac Repair & Extentionprogram since mine is a 2GHz.. My seriealnumber starts with W8519XXXXXX..
    Does W8435xxxxxx - W8522xxxxxx mean that all serialnumbers between these two are convered by this program?
    http://www.apple.com/support/imac/repairextensionprogram/
    How can Apple charge me $200 for a obious production fault?!
    iMac G5, 2GHz, 20"   Mac OS X (10.4.7)  

    All serial numbers within the numbers listed should be covered, and your number seems to fall in that category. However, if yours is not a Rev A , Apple may feel that your problem is not the one they are dealing with. They do specifically state:
    "Some second generation iMac G5 computers have serial numbers that fall within the upper band of the ranges listed below. Only first generation iMac G5 computers are affected by this program."
    I would call them again and try, politely, to point out that not only did your warranty just expire, but that your serial number is among the affected ones and your problem is one of the ones the extension program addresses.
    Good luck,
    Miriam
    Rev A 20" iMac G5, 15"iMac G4, 15"iMac G3 DVD Mac OS X (10.4.7)

  • C3750X - Power supply OIDs problems

    Hello,
    We are trying to monitor two stacks of CISCO WS-c3750X running IOS 12.2.(58)SE.
    We can get the state of the power supplies, but after a power cycle or reboot of the switches the identifier of ONE of the Power supplies ALWAYS change. The OIDs for the rest of the PS do not vary. The problem happens in the two stacks.
    Any idea or work around?
    Kind regards
    Mark                  

    Hi,
    I'm trying to determine if the issue addressed in this post is a match with the following symptom:
    As you can see from the output below - the switch 2 power supplies appear to be healthy:
    SWITCH#show env power switch 1
    SW  PID                 Serial#     Status           Sys Pwr  PoE Pwr  Watts
    1A  C3KX-PWR-350WAC     AZS161707F3  OK              Good     Good     350/0
    1B  C3KX-PWR-715WAC     LIT16180RRU  OK              Good     Good     715/0
    SWITCH#show env power switch 2
    SW  PID                 Serial#     Status           Sys Pwr  PoE Pwr  Watts
    2A  C3KX-PWR-715WAC     LIT16180RRY  OK              Good     Good     715/0
    2B  C3KX-PWR-350WAC     AZS161707FZ  OK              Good     Good     350/0
    Yet, the snmpwalk output shows a Sw2 PS2 power supply fault:
                  snmpwalk -v1 X.X.X.X  -c READONLY .1.3.6.1.4.1.9.9.13.1.5.1
    SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1035 = STRING: "Sw1, PS1 Normal, RPS NotExist"
    SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.1036 = STRING: "Sw1, PS2 Normal, RPS NotExist"
    SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2034 = STRING: "Sw2, PS1 Normal, RPS NotExist"
    SNMPv2-SMI::enterprises.9.9.13.1.5.1.2.2035 = STRING: "Sw2, PS2 Faulty, RPS NotExist"
    Do my symptoms match with the issue addressed in this post ?
    TIA,
    Amir

  • Looking for a Power Supply

    Hi!
    I am looking for a power supply for my sound blaster speakers.
    The model is SBS 380. The power supply works on a 4.0 volt.
    Anyone who would have a spare one to sell or to inform me where
    to buy one would be most appreciated. ( I'm in Canada )
    I have be been to several stores but no ones carries 4 volts power supply.
    The one I have is no lomger functional and the sound is excellent from those speakers.
    BTW, Craetive no longer support them and have none in stock.
    Thanks,
    Gerry

     Jason, I think he would have some trouble getting them shipped to Australia from one of those stores. Beside that it would be less from newegg, look at the additional 20% off promo and free shipping. For me it's 3 days from order to delivery from ZZf and newegg.
     Yes, one of the Corsairs but not HX but as mentioned TX or VX, also PC P&C 610. Ignore watts, go by +12V amps and as FP mentioned consider future need for more power when choosing. Nowdays the VX450W (+12V~33A) would be considered minimum to get and also would be considered weak for many current systems.

  • Lenovo G550, power supply

    Hi, i have lenovo G550, when i start laptop, it works good, after 15-20 mins, power supply starts rotating for about one minute, after that , a small pause about 3-5 mins, and starts again, so from this time power supply begin rotating for every 3-4 mins .
    I have a program that controls a processor's and hdd's emperature , hdd's temperature moves from 30 - 41  C , never higher, CPU's temperature when arrive 43-44 C , power supply starts working  and when temperature of CPU arrive 33 C , power supply stop working (blowing) , so laptop never stop working.
    My question is : Is this normal work of laptop, or my laptop isn't OK ???
    Sorry for my bad english .

    To get to the power jack, you are removing most every screw on the case. Remove the panel above keyboard that houses power button, then there are more screws beneath it. Then you can get to hinges, unscrew them, find another screw at each hinge after hinge is out of the way. Also unfasten the keyboard, but don't rip it out, to find a couple more screws underneath the keyboard. And finally you can take the two halves of the case apart well enough and get in to disconnect the power jack. The DVD drive will slide out, no screws attaching it. The wiring for the power jack goes to a location by the memory where it attaches to the motherboard. I disconnected the cable by the memory and pulled it through easily.
    Should take a week for the part to arrive to me. Crossing fingers that the whole trouble is this and nothing else. Found other thread here that talks about securing the jack better: http://forums.lenovo.com/t5/Lenovo-3000-and-Value-line/G550-power-connector-is-this-a-weak-point/td-...
    Clearly there is a fault in the design of this laptop model, I think, when many people are having the same fatal issue.
    Also, now that I think of it: if you wanted to test if this was the problem for you laptop without the trouble of disassembling everything, you could easily disconnect the power jack by removing the memory cover and unplugging it there; then plug in a replacement power jack (which you'd need to order) and test. If all works, you could then go through the bother of taking everything apart (or finding someone to do it).

  • Hp p6000 desktop not starting power supply...?

    I have a solid green light on the power supply but the fan does not come on.  (nothing but the green light comes on) The start up button flickers briefly when pressed but only after being unplugged and only once until it is unplugged again. I  have gone though the hp trouble shooting page.  Any help would be greatly appreciated. 

    As you did not define the model number (just a reference to the HP p6000 series) I had to guess it was the stock 300W used in several of the models.
    It the green light is 'on' with applied voltage, but goes out when the computers power switch is depressed, that usually means the power supply has failed. Open the case, and repeat the sequence, noting the PSU light, motherboard LED, and watch the CPU fan. Now, press the computer power switch. Did the CPU fan turn briefly? If the CPU fan quit, and the motherboard LED is now off, I again would suspect the PSU.
    I am a volunteer. I am not an HP employee.
    To say THANK YOU, press the "thumbs up symbol" to render a KUDO. Please click Accept as Solution, if your problem is solved. You can render both Solution and KUDO.
    The Law of Effect states that positive reinforcement increases the probability of a behavior being repeated. (B.F.Skinner). You toss me KUDO and/or Solution, and I perform better.
    (2) HP DV7t i7 3160QM 2.3Ghz 8GB
    HP m9200t E8400,Win7 Pro 32 bit. 4GB RAM, ASUS 550Ti 2GB, Rosewill 630W. 1T HD SATA 3Gb/s
    Custom Asus P8P67, I7-2600k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX660 2GB, 750W OCZ, 1T HD SATA 6Gb/s
    Custom Asus P8Z77, I7-3770k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX670 2GB, 750W OCZ, 1T HD SATA 6Gb/s
    Both Customs use Rosewill Blackhawk case.
    Printer -- HP OfficeJet Pro 8600 Plus

Maybe you are looking for