Thinkpad T440s BIOS update via PXE fails with "invalid system disk"

Hi,
I'm trying to boot via PXE to the BIOS 2.24 update ISO image because the T440s comes without a DVD drive. The Thinkpads are running RHEL 6.5 workstation installed. I'm using syslinux 6.02 and the following menu entry:
label lenovo_t440s
    menu label Lenovo Thinkpad T440s BIOS 2.24 Update
    kernel memdisk
    append initrd=lenovo/t440s/gjuj11us.iso iso
The ISO gets loaded via TFTP and seems to boot, but then an error message appears:
Loading boot sector... booting...
Lenovo Group Limited
Invalid system disk
Replace the disk, and then press any key.
The Thinkpads come with the following SSD drive: SAMSUNG MZ7TD256HAFV-000L9.
Anyone had luck with updating BIOS via PXE boot?
We also have Thinkpads T430s. There the BIOS update ISO image loads, displays the menu, but when one presses "update firmware" then it freezes.
Regards,
Bernd

Same behaviour when I try without PXE and load memdisk and ISO file directly via GRUB using this entry in /boot/grub/grub.conf:
title ThinkPad BIOS Update
root (hd0,1)
kernel /memdisk iso
initrd /gjuj11us.iso

Similar Messages

  • Thinkpad T440 BIOS update without Windows Utility - problem

    So I wanted to update my BIOS from 2.23 to 2.30 from here - http://support.lenovo.com/us/en/downloads/ds035967. First think's first - my T440 does not have any CD/DVD, so obviously I need a bootable USB to update my BIOS. Second, I'm using Ubuntu and no longer have (or want to have) the Windows installation.
    In order to make a bootable USB with the BIOS iso file I tried 2 things:
    1) Tried following this guide - httpawww.lenzg.net/archives/358-Updating-the-BIOS-on-my-ThinkPad-T440-without-Windows-or-a-DVD-Drive.html, everything seems to be have worked, except the fact that it does not boot when I try to boot trough the USB, and I bumped there.
    2) Open a Windows on my second laptop and try to make a bootable USB from Windows (maybe it will help?). Tried both the standard Windows USB DVD Tool and got the error - "The selected file is not a valid ISO file. Please select a valid ISO file and try again." Fair enough, here I started to get suspisous that something is wrong. I tried and burned a bootable USB with PowerISO, but again as method 1) it does not boot.
    Just to mention that in my BIOS I have the Secure Boot off and both the Legacy mode and UEFI, with Legacy first.
    Any ideas how to proceed?

    Sorry, I don't know about Linux much less then nothing.
    But I'm sure there are the following tools for:
    - disk/partition management, to make primary partition on the stick as active, to be bootable
    - mount .iso image as a virtual CD to explore that one and get its content. Or, perhaps, there is .iso content viewer that supports CDFS.
    x220 | i5-2520m | Intel ssd 320 series | Gobi 2000 3G GPS | WiFi
    x220 | i5-2520m | hdd 320 | Intel msata ssd 310 series | 3G GPS | WiFi
    Do it well, worse becomes itself
    Русскоязычное Сообщество   English Community   Deutsche Community   Comunidad en Español

  • Erazer X700 new BIOS update flash is failing with 4 - Error: Rom file ROMID is not compatible

    I am trying to apply the new Erazer X700 bios update from http://support.lenovo.com/us/en/products/desktops-and-all-in-ones/lenovo-erazer-x-series-desktops/le...
    It fails when I run it in the admin cmd window, with message 4 - Error: ROM file ROMID is not compatible with existing BIOS ROMID. Any idea why I'm getting this failure?
    Has anyone successfully applied the lastest X700 downloads?

    I am also having this same exact issue. Any help would be greatly appreciated Lenovo.

  • P35 platinum combo will not boot windows after bios update via Live Update

    Hi,
    I had everything running on windows 7 fine until 2 days ago.  I installed Live Update from MSI website.  I was about to install driver updates for my motherboard, but the bios update went instead.  my pc tried to restart after the bios update installed, but it failed.  would not post and would only see black screen.
    then i removed one of my memory sticks.  it would post, but then windows would not start up.  it would get stuck at windows loading screen.  i tried to reformat with my windows cd.  but during install it would blue screen of death me.  i tried multiple times and it would always blue screen of death with different errors.  the last one i remember was a message saying i should off turn shadowing and caching.
    this all started happening after i attempted bios update via Live Update.
    Any help is greatly appreciated.
    I have a core2quad 9450
    this motherboard
    MSI P35 Platinum Combo LGA 775 Intel P35 ATX Intel Motherboard
    http://www.newegg.com/Product/Product.aspx?Item=N82E16813130141
    this ram
    G.SKILL 4GB (2 x 2GB) 240-Pin DDR2 SDRAM DDR2 1000 (PC2 8000) Dual Channel Kit Desktop Memory Model F2-8000CL5D-4GBPQ
    http://www.newegg.com/Product/Product.aspx?Item=N82E16820231145
    this harddrive
    Mushkin Enhanced Chronos MKNSSDCR120GB 2.5" 120GB SATA III MLC Internal Solid State Drive (SSD)
    http://www.newegg.com/Product/Product.aspx?Item=N82E16820226236
    this video card
    XFX PVT88PYSF4 GeForce 8800 GT 512MB
    http://www.newegg.com/Product/Product.aspx?Item=N82E16814150280
    Thanks!!!

    at a guess you need to reset bios to ahci
    a bios flash defaults to ide mode

  • I ran an iTunes update.  It failed with the message  System Error.  The program can't start because MSVCR80.DLL is missing from your computer.  Try reinstalling the program to fix this problem.   I tried reinstalling but get the same message.

    I ran an iTunes update.  It failed with the message  "System Error.  The program can't start because MSVCR80.DLL is missing from your computer.  Try reinstalling the program to fix this problem."   I tried reinstalling but get the same message.  I looked in my Recycle Bin for that file name but there is none there.  Is this a new file that iTunes wants?

    Click here and follow the instructions. You may need to completely remove and reinstall iTunes and all related components, or run the process multiple times; this won't normally affect its library, but that should be backed up anyway.
    (99683)

  • An update of iMovie failed with the message "an error has occurred." That message remains posted by iMovie on the Mac App Purchases page. iMovie is now unavailable. It will not start, update, or reinstall from purchases page. How reinitialize app?

    An update of iMovie failed with the message "an error has occurred." That message remains posted by iMovie on the Mac App Purchases page. iMovie is now unavailable. It will not start, update, or reinstall from purchases page. How do I reinitialize the app?

    Thank you again. Here's the console messages from trying to open iMovie and then opening the App Store. Clicking on the iMovie icon in App Store purchases and clicking on check for unfinished downloads:
    8/28/14 4:56:26.743 PM Dock[214]: LSOpenFromURLSpec(file:///Applications/iMovie.app/) failed with -10699
    8/28/14 4:56:47.878 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:56:47.879 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:57:50.201 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:57:50.201 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:35.745 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:35.745 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:35.824 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:35.824 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:35.847 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:35.847 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:36.276 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:36.276 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:39.448 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:39.448 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:39.449 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:39.449 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:55.996 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:55.996 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.021 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.022 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.051 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.052 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.342 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.342 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.411 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.411 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.425 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.425 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.508 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.508 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.518 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.519 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.696 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.696 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.808 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.808 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.826 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.827 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.838 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.839 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.843 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.843 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.857 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.857 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.893 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.894 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.907 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.907 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.923 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.924 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:56.969 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:56.970 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.039 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.039 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.045 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.045 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.145 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.145 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.231 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.231 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.249 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.249 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.293 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.293 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.350 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.350 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.352 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.353 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.400 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.400 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:57.402 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:57.402 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:59.814 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:59.814 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:58:59.932 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:58:59.932 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:00.697 PM acwebsecagent[127]: Connection : Failed to connect to 167.8.226.9:80. Code : 60
    8/28/14 4:59:00.698 PM acwebsecagent[127]: Connection : Caught exception. Code : 60
    8/28/14 4:59:00.698 PM acwebsecagent[127]: Connection : Failed to connect externally. Code : 60
    8/28/14 4:59:01.352 PM acwebsecagent[127]: Connection : Failed to connect to 167.8.226.9:80. Code : 60
    8/28/14 4:59:01.352 PM acwebsecagent[127]: Connection : Caught exception. Code : 60
    8/28/14 4:59:01.352 PM acwebsecagent[127]: Connection : Failed to connect externally. Code : 60
    8/28/14 4:59:01.402 PM acwebsecagent[127]: Connection : Failed to connect to 167.8.226.9:80. Code : 60
    8/28/14 4:59:01.402 PM acwebsecagent[127]: Connection : Caught exception. Code : 60
    8/28/14 4:59:01.402 PM acwebsecagent[127]: Connection : Failed to connect externally. Code : 60
    8/28/14 4:59:26.564 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:26.565 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:26.660 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:26.660 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:26.840 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:26.840 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:26.864 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:26.864 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:26.984 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:26.984 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.069 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.069 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.079 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.079 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.083 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.084 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.385 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.385 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.389 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.390 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.391 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.391 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.411 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.411 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.435 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.436 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.443 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.443 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:27.479 PM acwebsecagent[127]: Connection : Auth key is not provided or is invalid, applying connection failure policy. CMode : 2 TMode : 1
    8/28/14 4:59:27.479 PM acwebsecagent[127]: OnConnectionFailure : Fail Open - Reason = Unable to verify the license key
    8/28/14 4:59:31.036 PM acwebsecagent[127]: License : One or more of the License/Public Key can't be NULL
    8/28/14 4:59:31.036 PM acwebsecagent[127]: SSLExt : Failed to get ScanSafe headers
    8/28/14 4:59:31.036 PM acwebsecagent[127]: DownloadUpdatedConfig : Failed to download updated config. Host hostedconfig.scansafe.net. Code 0x80004005

  • Built-In Keyboard Firmware Update 1.0 fails with error 23:3 on MacBook 2,1

    I attempted to install "Built-In Keyboard Firmware Update 1.0" on two laptops tonight.
    Macbook Pro 3,1:
    Hadn't experienced the issue that the firmware would resolve. Installed the update anyway, successfully, and continued to have no problems since.
    Macbook 2,1:
    Hadn't experienced the issue that the firmware would resolve. Tried to install the update, but it failed with error "23:3". After the failure, the keyboard was non-responsive for about 30-60 seconds, during which time I assume it restored/re"booted" itself. Keyboard function was restored automatically after this time, though there was no indication that it would return, and I had to suffer a minor sweat. Still, I didn't learn I power cycled the system and tried again, but the update never installed successfully.
    Lessons learned -
    If it ain't broken...
    That said, Apple seems to have designed their hardware well enough to be able to recover from a failed firmware update. In this case, you just have to pray a little until the keyboard responds again.
    Apple: be so kind, let us know what 23:3 means, and if needed, update the Firmware Updater.
    //

    Hi,
    I was just wondering how you were able to get the macbook to accept the update? I had to take mine to apple store and get entire keyboard and trackpad replaced in my macbook. They then told me to ignore the update cause they did not have any other keyboards to replace if it happened again.

  • BIOS Update 6.70 problem with Satellite Pro C850-172

    I have two problems with updating the BIOS (the 1st is more important then the 2nd one):
    1. While trying to install BIOS Update 6.70-WIN (29/11/13) it says that:
    "The version of ROM file is the same as that of BIOS"
    and it stops. In the DOS window it shows one phrase:
    "NOT Windows 8 Platform, using Windows 7 update...".
    I use Windows 7 Home Premium 64bit system but recently there has been major automatic update done to it.
    I got lost. Is there anything I can do to update BIOS?
    2. Earlier it says that Flash process will be terminated and I need to "contact OEM BIOS engineer to add the NV storage location by HISII interface". But if I want to risk I can continue etc.
    Previously I took the risk and updating went well.
    But is there possibility to contact OEM BIOS engieneer?

    Hi
    >While trying to install BIOS Update 6.70-WIN (29/11/13) it says that:
    >"The version of ROM file is the same as that of BIOS"
    What is the present BIOS version which is available on your notebook?
    In case the BIOS is already up to date, the BIOS flash procedure will be interrupted.
    >"NOT Windows 8 Platform, using Windows 7 update...".
    Im not quite sure about the meaning of this information but it looks like the BIOS update was released for Windows 8 system and probably its required to upgrade the system from Windows 7 to Windows 8 in order to be able to flash the BIOS
    By the way: why you want to update the BIOS? Just because new version is available?
    Please note that BIOS update does not improve the notebook performance but fixes some issues. In case your notebook runs properly, the BIOS update is not very important

  • Cube failed with invalid character stics

    Hi,
    My cube failed with invalid charactersticts....data flow is source sytem to ODS and then cube.
    loading in to ODS and activation is also successful . I would like to know the reason why ODS loading & activation is not failed with above said message and why cube is failed...
    Thanks in advance.....CK

    Hi,
    BW accepts just capital letters and certain characters. The permitted characters list can be seen via transaction RSKC.
    There are several ways to solve this problem:
    1)     Removing erroneous character from R/3 (for example required vendor number that need to be changed can be found from PSA from line shown in error message)
    2)     Changing or removing character in update rules (need to done by ABAP)
    3)     Putting character to BW permitted characters, if character is really needed in BW
    4)     If the bad character only happens once then it can be directly change/removed by editing the PSA
    5)     Put ALL_CAPITAL in permitted characters. Needs to be tested first!
    Editing and updating from PSA, first ensure that the load has been loaded in PSA, then delete the request from the data target, edit PSA by double clicking the field you wish to change and save. Do not mark the line and press change this will result in incorrect data. After you have corrected the PSA, right click on the not yet loaded PSA and choose u201Cstart immediately.u201D
    Hope it will help you.
    Regards,

  • Discoverer Desktop Connections Fails With Invalid Username/Pass in r12

    Hi all;
    I have problem. I can login Discoverer Administrator from my localmachine and i can see what ppl did it there.. But when i try to login Discoverer Desktop from my localmachine its gives me Invalid Username/Pass. error.
    I even cant login my system from browser :
    http://xx.com:7778/discoverer/plus << pages comes and i fill in the blanks area like:
    Connect to : Oracle Application
    Username: sysadmin
    pass: ***
    Database: VIS
    I found some document from forums. Whihc is :
    Discoverer Is Unable to Connect to Oracle Applications database: invalid username/password      Doc ID: Note:467919.1
    Discoverer 10g (10.1.2) Connectons To Oracle E-Business Suite 12 Fails With 'Invalid Username/Password'      Doc ID: Note:443661.1
    But before i apply those patch i want to take advice from you. Coz i can login Discoverer Administrator and can use it but cant login Discoverer Desktop...its kind of wierd... i already checked what i have done in installtion and its all seems correct.
    Any idea;
    Regards
    Helios

    Discoverer supports two kinds of connections - database schema connections and apps connections. For Disco Admin, you login using a database schema, which, as you stated, works. For Disco User you login using an Apps user account (for which there is a no equivalent database scherma). To enable such a connection, you need to check the "oracle applications user" check box on the 10g Disco login screen. Also, under Tools --> Options, in the Connection tab, make sure that "connect to both standard and applications EULs" radio button is selected.
    HTH
    Srini

  • Backup Fails with Invalid RECID Error

    Hi All,
    Please help me to understand Caution -section
    below text is from
    [http://download.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmtroub.htm#447765]
    Backup Fails with Invalid RECID Error: Solution 2
    This solution is more difficult than solution 1:
    To create the control file with SQL*Plus:
       1. Connect to the target database with SQL*Plus. For example, enter:
          % sqlplus 'SYS/oracle@trgt AS SYSDBA'
       2. Mount the database if it is not already mounted:
          SQL> ALTER DATABASE MOUNT;
       3. Back up the control file to a trace file:
          SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;
       4. Edit the trace file as necessary. The relevant section of the trace file looks something like the following:
          # The following commands will create a new control file and use it
          # to open the database.
          # Data used by the recovery manager will be lost. Additional logs may
          # be required for media recovery of offline data files. Use this
          # only if the current version of all online logs are available.
          STARTUP NOMOUNT
          CREATE CONTROLFILE REUSE DATABASE "TRGT" NORESETLOGS  ARCHIVELOG
          --  STANDBY DATABASE CLUSTER CONSISTENT AND UNPROTECTED
              MAXLOGFILES 32
              MAXLOGMEMBERS 2
              MAXDATAFILES 32
              MAXINSTANCES 1
              MAXLOGHISTORY 226
          LOGFILE
            GROUP 1 '/oracle/oradata/trgt/redo01.log'  SIZE 25M,
            GROUP 2 '/oracle/oradata/trgt/redo02.log'  SIZE 25M,
            GROUP 3 '/oracle/oradata/trgt/redo03.log'  SIZE 500K
          -- STANDBY LOGFILE
          DATAFILE
            '/oracle/oradata/trgt/system01.dbf',
            '/oracle/oradata/trgt/undotbs01.dbf',
            '/oracle/oradata/trgt/cwmlite01.dbf',
            '/oracle/oradata/trgt/drsys01.dbf',
            '/oracle/oradata/trgt/example01.dbf',
            '/oracle/oradata/trgt/indx01.dbf',
            '/oracle/oradata/trgt/tools01.dbf',
            '/oracle/oradata/trgt/users01.dbf'
          CHARACTER SET WE8DEC
          # Take files offline to match current control file.
          ALTER DATABASE DATAFILE '/oracle/oradata/trgt/tools01.dbf' OFFLINE;
          ALTER DATABASE DATAFILE '/oracle/oradata/trgt/users01.dbf' OFFLINE;
          # Configure RMAN configuration record 1
          VARIABLE RECNO NUMBER;
          EXECUTE :RECNO := SYS.DBMS_BACKUP_RESTORE.SETCONFIG('CHANNEL','DEVICE TYPE DISK
          DEBUG 255');
          # Recovery is required if any of the datafiles are restored backups,
          # or if the last shutdown was not normal or immediate.
          RECOVER DATABASE
          # All logs need archiving and a log switch is needed.
          ALTER SYSTEM ARCHIVE LOG ALL;
          # Database can now be opened normally.
          ALTER DATABASE OPEN;
          # Commands to add tempfiles to temporary tablespaces.
          # Online tempfiles have complete space information.
          # Other tempfiles may require adjustment.
          ALTER TABLESPACE TEMP ADD TEMPFILE '/oracle/oradata/trgt/temp01.dbf' REUSE;
          # End of tempfile additions.
       5. Shut down the database:
          SHUTDOWN IMMEDIATE
       6. Execute the script to create the control file, recover (if necessary), archive the logs, and open the database:
          STARTUP NOMOUNT
          CREATE CONTROLFILE ...;
          EXECUTE ...;
          RECOVER DATABASE
          ALTER SYSTEM ARCHIVE LOG CURRENT;
          ALTER DATABASE OPEN ...;
    Caution:
          If you do not open with the RESETLOGS option,
    then two copies of an archived redo log for a given log sequence number may
    exist--even though these two copies have completely different contents.
    For example, one log may have been created on the original host and the other on the new host.
    If you accidentally confuse the logs during a media recovery,
    then the database will be corrupted but Oracle and RMAN cannot detect the problem.

    Please help me to understand Caution -section
    Caution:
    If you do not open with the RESETLOGS option,
    then two copies of an archived redo log for a given log sequence number may
    exist--even though these two copies have completely different contents.
    For example, one log may have been created on the original host and the other on the new host.
    If you accidentally confuse the logs during a media recovery,
    then the database will be corrupted but Oracle and RMAN cannot detect the problem.As per my understanding it says. If you don't open database with RESETLOGS option then there may be archived logs with log sequence number which is already archived on the source host. This may happen due to difference in RECIDs. Now when the database needs media recovery for this particular log sequence, you may provide any of them. So in this case, RMAN and Oracle will not be able to differentiate the two files and can accept any of the archived log files during recovery. Since the contents of two archived logs are different, because they are generated at different times and they contains different transactions. So, internally it corrupts your database.
    Rgds.

  • There are 6 updates to be made with my system and they start but after downloading and rebooting it always says that non could be installt because of an mistake, but no help, no number, no possibility to chose from...

    there are 6 updates to be made with my system and they start but after downloading and rebooting it always says that non could be installt because of an mistake, but no help, no number, no possibility to chose from...

    Do you get an error number? What is the exact message?
    Two things to try.
    - Sign out of the App Store (in the Store menu)
    - Quit the App Store
    - In Finder - Go>Go to folder...  (or Apple-shift-G)
    - Paste in the following "~/Library/Caches/ "
    - It will take you to a folder.  Delete com.apple.appstore
    - Launch the App Store.
    If that doesn't work, try an App Store reset and then try again.
    App Store Reset       Learned from Old Toad
    There is a contact link.
    App Store Support

  • 10g : WriteToFile always fails with 'invalid directory path'

    Oracle 10.1.0.3.0
    Microsoft Windows XP Service Pack 2
    I can't use XMLDOM.writeToFile. Always fails with 'invalid directory path' :
    SQL> create directory c_root as 'C:\';
    Directory created.
    SQL>
    SQL> declare
    2 doc xmldom.DOMDocument;
    3 root_elmt xmldom.DOMElement;
    4 begin
    5 doc := xmldom.newDOMDocument;
    6
    7 root_elmt := xmldom.createElement(doc, 'MessageBatch');
    8
    9 xmldom.writeToFile(doc, 'C:\docSample.xml');
    10 xmldom.freeDocument(doc);
    11
    12 end;
    13 /
    declare
    ERROR at line 1:
    ORA-29280: invalid directory path
    ORA-06512: at "SYS.UTL_FILE", line 33
    ORA-06512: at "SYS.UTL_FILE", line 436
    ORA-06512: at "XDB.DBMS_XSLPROCESSOR", line 86
    ORA-06512: at "XDB.DBMS_XMLDOM", line 4451
    ORA-06512: at line 9
    This happens with any OS directory with write permission for Everyone.
    Also tried with UTL_FILE_DIR = *, same outcome...
    Thanks in advance,
    Hugo Leote

    Look like bug 4477774. A possible workaround, somewhat unsafe, is to set UTL_FILE_PATH to '*', which will require a server restart. You then specifiy the path with unix style '/' rather than dos style '\'. You may also be able to use a path with unix style '/' rather than '*', although the bug description does not make this clear.

  • SSM BIOS Deployment Ends Sometimes Fails With Error 0x642

    Good morning,
    I am currently trying to use the SSM software to deploy a BIOS update to my 300 HP Folio 9470m and am running into an intermittent problem.  The problem I am seeing is that sometimes the deployment will fail with a 0x642 dependency error. I have not been able to determine a reason for the failure, and the same package deployment will work on a different laptop.
    The only consistency I have been able to reproduce is that if the install fails the first time, it will fail every other time on that particular laptop.
    I have included log files from a successful and unsuccessful deployment.  I have confirmed that it does not appear to be an issue with using the incorrect BIOS password, because I can set the password to the one specified when I created the deployment database and it will still sometimes fail.
    Let me know if I can provide any additional information.  Any help would be greatly appreciated.  I really would like to be able to use this software as it would make  my job managing these laptops a whole lot easier.
    Thanks,
    Raymond Northcott
    Log file from successful deployment:            https://drive.google.com/file/d/0By0fDHxxVEc6SHhZb​0VDRVRMRWc/edit?usp=sharing
    Log file from unsuccessful deployment:        https://drive.google.com/file/d/0By0fDHxxVEc6NXdEO​TV6bnJ3TGc/edit?usp=sharing
    This question was solved.
    View Solution.

    I know it is late but I have only seen this post today. 
    The team responsible for SSM does not monitor this forum.
    According to the logs you have posted, you are using SSM version 2.14 A8.
    Your version pre-dates the design and production of the 9470 folio by approximately 3 years.
    There have been many changes to SSM since 2.14.
    Please update to the latest version.
    You can ask questions about SSM and other client management tools in the HP PC Client Management Community forum.
          HP PC Client Management Community forum
    The pc client management discussion board is focused on the following topics but is not exclusive to them:
    HP Client Catalog
                    The HP Client Catalog for Microsoft System Center Configuration Manager products is used in the deployment of HP software updates (SoftPaqs) to HP commercial PCs in a Microsoft System Center environment.
    HP Driver Packs
                    HP Driver Packs contain the necessary Microsoft Windows drivers required
    to support HP hardware platform(s) listed in each of the driver pack’s release notes.
    HP Client Integration Kit
    The HP Client Integration Kit ( HP CIK ) is a plug-in for Microsoft System Center Configuration Manager.
    HP BIOS Configuration Utility
    The HP BIOS Configuration Utility ( HP BCU ) provides the ability to manage BIOS settings on HP supported desktop, workstation and notebook computers.
    HP System Software Manager
    The HP System Software Manager ( HP SSM ) is a utility for updating BIOS and device drivers on your networked PCs.
    These tools and more can be found at www.hp.com/go/clientmanagement
    Look in the Resources menu for items such as the HP CMS Download Library,  HP CMS Whitepapers or HP Driver Packs.
    The HP CMS Download Library contains the latest release version of SSM.
          HP CMS Download Library
    If you have questions about SSM or any of the other utilities listed, this is the best forum to find answers.
    thanks,
    Richard
    I work for HP but am not a company spokesperson.  Participation in the community forums is voluntary.

  • Thinkpad Yoga BIOS Update Problem after installing Windows 10

    Hi all, I've been reading tonnes of threads here trying to solve my problems (which seem to keep getting worse) to no avail. I'm reaching out to anyone that can suggest some help before I end up bricking my yoga by accident or running it over on purpose. I'll give you a timeline of the events. The machine in question is a Lenovo Thinkpad Yoga 12.5" 20CD-0032USIntel Core i5 4200U 1.60GHz Processor4GB Ram128GB SSDWindows 8.1 64 Bit preloaded (recently upgraded to Windows 10) So the saga begun just a short two days ago. I had some spare time at home and decided to download and install my free upgrade to Windows 10. I backed up all of my important documents etc to OneDrive as I intended on performing a clean install. Said clean install went flawlessly with Windows 10 installing the first time with no issues or errors. Since I had performed a clean install, all my previous apps, including the stock Lenovo apps, had been deleted. I had anticipated this and only really desired to reinstall the app that automatically adjusts the screen orientation when folding the cover back. So in an effort to find this app and any Windows 10 related updates that may be available I went to support.lenovo.com and used the handy Lenovo Bridge app to automatically detect my hardware and suggest relevant updates. While combing through the suggested software I noticed a BIOS update that noted added support for Windows 10. How great, I thought, that Lenovo would have a BIOS update ready so quickly once 10 became ready for mass consumption. I went ahead and downloaded the exe version (not the bootable CD due to the lack of CD drive on the Yoga) and ran the BIOS update. As I ran the update the laptop was plugged in, and no errors were presented, a success message appeared and indicated a reboot was necessary, after a couple seconds the system rebooted itself. Enter nightmare level 1. As soon as the system rebooted, I fired up IE about to look for more updates and......BSOD stating that there was and issue with a driver, after another reboot BSOD again with a completely different file name stating driver file missing or corrupt. Sorry I didn't write any of the file names or errors down. At this point I'm thinking that something is not jiving here between the BIOS and OS. So I tried running repair, and recovery and each time I would end up with a BSOD of some design. It was at this point I made a USB with the Windows 10 x64 ISO from Microsoft in an attempt to run the repair utilities from the USB. Again to no avail. Enter nightmare level 2 After attempting multiple tries at recovering Windows 10 and getting multiple BSOD's through the process I decided to use my Windows 10 USB to simply reformat my hard drive to eliminate any traces of my now apparently corrupt OS and do a fresh install of Windows 10. This appears to have been a significant error on my part. Now I have no OS (BIOS is still intact so at least I think I have a not-bricked motherboard) and everytime I try to boot Windows 10, or 8.1 for that matter, from a brand new USB stick I get constant BSOD's.Sometimes I get as far as the Preparing installation files 22% but am interrupted by a BSOD error at some point. So I am pleading for some help here. To me it seems like the BIOS update was the issue. I was not smart enough to have checked the BIOS version before updating so that I would know what to roll back to safely. What would you all recommend for a rollback and how do I go about doing one with no OS on the machine. I know I'm asking for a tl;dr here but appreciate any advice offered. I really dont want to get to nightmare level 3, which I guess would be a bricked laptop and a bill for a new motherboard or laptop. The BIOS I currently have is GQET45WW (1.25) -Garrett  

    Thanks for the reply ColonelONeill, It turns out that Lenovo uses an obscure PERL disk image called "eltorito". As such the directions in the link you provided did not work as most common tools (WinZip, 7zip, and WinRAR) cannot extract the image file from an eltorito iso file.  I instead just bucked up for a $50.00 Asus USB CD drive and burned the iso for version 1.25 and 1.24 onto discs. I then disabled the setting in the BIOS that prevents rolling back to a previous version and flashed to 1.24 from the disc. While this appeared to go successfully, as soon as I tried to boot from my Windows 8.1 CD I start receiving BSOD's again during installation. I then used the CD with 1.25 to go back to where I was in case it was simply a bad BIOS update at the time. Most of the BSOD's are driver related (qlfcoei.sys) which I don't understand since there is no OS other than what is on the bootable CD (or USB I've tried both) Is there anyone with a stable install of Win 8.1 x64 or 10 x64 running on a 20CD0032US that can tell me what version of BIOS they are running? My next step is to go back to a version that someone else can verify is working. Thanks again for any help.

Maybe you are looking for