logo elektroda
logo elektroda
X
logo elektroda

Unable to Access BIOS on Fujitsu Lifebook A532 Laptops after Clonezilla & Windows 10 Setup

strzelb@ 9036 7
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16334987
    strzelb@
    Level 10  
    Three proprietary Fujitsu Livebook A532 laptops have the same problem - unable to boot to BIOS setup using F2 or F12.

    It started with the fact that I prepared a bootable pendrive with CLONEZILLA and an image of a configured WIN 10.
    So in order to start it, I did the following:
    1. I set up the USB boot sequence in the BIOS.
    2. I had to set up a supervisor password - because only then the BIOS allowed to disable the SECURITY BOOT option
    3. First reboot and everything started as planned.
    4. Second reboot - BIOS automatically restored HDD as bootable drive.
    5. The system boots from HDD and Windows flashes ....

    And here comes the problem - I can't get into the BIOS anymore !!!!!!
    After pressing F2 and entering the supervisor password, a black screen appears and there is no further reaction. Nothing at all - just fan noise.
    After rebooting, Windows wakes up normally. You just can't enter the BIOS.

    I tried to reset the BIOS by pulling the battery off the motherboard - but it is mounted so that it cannot be removed. There is a reset jumper on the board (I found info on the internet), but it only resets the RTC clock settings - after shorting it and restarting, there is still a BIOS password and a black screen.

    I even tried to upload a new BIOS - downloaded from the Fujitsu website - but it crashes some image incompatibility or something ...

    I have no ideas anymore.
    Regards Tomasz.
  • ADVERTISEMENT
  • #2 16335153
    Kolobos
    IT specialist
    After disconnecting the disk, can you enter the BIOS?
  • ADVERTISEMENT
  • #3 16335218
    RADU23
    Moderator of Computers service
    strzelb@ wrote:
    I even tried to upload a new BIOS - downloaded from the Fujitsu website - but it crashes some image incompatibility or something ...

    Specify the error message more precisely (take a picture and post).
  • ADVERTISEMENT
  • #4 16338912
    strzelb@
    Level 10  
    Kolobos wrote:
    After disconnecting the disk, can you enter the BIOS?


    Regardless of whether the USB drive is connected or not - you cannot exit to setup. There is only a request for a supervisor password ... and after entering (I anticipate the next question) correct password - I can see the darkness.
  • ADVERTISEMENT
  • #5 16338915
    Kolobos
    IT specialist
    I did not write about "usb disk" but about the disk installed in the computer.
  • #6 16338928
    strzelb@
    Level 10  
    RADU23 wrote:
    Specify the error message more precisely (take a picture and post).


    I have already resolved the error message problem. I have to admit it's my fault. I tried to upload an older BIOS version than was originally installed in the computer. The latest BIOS was successfully loaded. The problem is that after entering setup and entering the supervisor password ...... I still see darkness.

    Added after 4 [minutes]:

    Kolobos wrote:
    I did not write about "usb disk" but about the disk installed in the computer.


    Without HDD too ..... dark. I just checked.
  • #7 16338951
    miecho18
    IT specialist
    Only the programmer will help here.
  • #8 16338965
    strzelb@
    Level 10  
    miecho18 wrote:
    Only the programmer will help here.

    Crow's face !!! :-(

Topic summary

The discussion revolves around an issue faced by multiple Fujitsu Lifebook A532 laptops, where the user is unable to access the BIOS setup after attempting to boot from a USB drive containing Clonezilla and a Windows 10 image. Despite setting the USB boot sequence and entering a supervisor password to disable Secure Boot, the user encounters a black screen upon pressing F2 to enter BIOS. Attempts to reset the BIOS by removing the battery have not resolved the issue. Responses suggest checking if the BIOS can be accessed with the HDD disconnected, but the user confirms that the problem persists regardless of the HDD's presence. The user later realizes that attempting to upload an older BIOS version may have contributed to the issue, but even after loading the latest BIOS, the problem remains unresolved.
Summary generated by the language model.
ADVERTISEMENT