Jump to content

Archived

This topic is now archived and is closed to further replies.

maca

Only 64-bit images supported?

Recommended Posts

Installed .iso onto USB using Rufus. Getting error message only 64-bit images support in top right (when trying to start scan on laptop). I have used my main PC instead of the laptop I am trying to fix. Not sure what is causing this and there seems to be no mention of this error only on google or this forum. Please help.

Share this post


Link to post
Share on other sites

What is the laptop?

What CPU does it have?

Does it have a 32-bit UEFI BIOS or a 64-bit UEFI BIOS?

The eset_sysecuse_live_enu.iso does not support UEFI32 systems.

Try to configure the BIOS to Legacy-boot.

 

Share this post


Link to post
Share on other sites
33 minutes ago, Steve2926 said:

What is the laptop?

What CPU does it have?

Does it have a 32-bit UEFI BIOS or a 64-bit UEFI BIOS?

The eset_sysecuse_live_enu.iso does not support UEFI32 systems.

Try to configure the BIOS to Legacy-boot.

 

Thinkpad E560

i5-6200U

cant seem to find whether the UEFI BIOS is 32 or 64bit

Share this post


Link to post
Share on other sites
1 hour ago, maca said:

Thinkpad E560

i5-6200U

cant seem to find whether the UEFI BIOS is 32 or 64bit

This device has a 64 bit processor. Therefore, UEFI/BIOS is 64 bit. So that is not the issue.

Appears LIveRescue .iso download from Eset web site auto detects what OS version is installed. It will download either 32 or 64 bit .iso based on this detection.

Did you download the SysRescue .iso on this Thinkpad device? Or perhaps from another PC that had a 32 bit version of Widows installed on it?

Share this post


Link to post
Share on other sites
45 minutes ago, itman said:

This device has a 64 bit processor. Therefore, UEFI/BIOS is 64 bit. So that is not the issue.

Appears LIveRescue .iso download from Eset web site auto detects what OS version is installed. It will download either 32 or 64 bit .iso based on this detection.

Did you download the LiveGrid .iso on this Thinkpad device? Or perhaps from another PC that had perhaps a 32 bit version of Widows installed on it?

I downloaded on 64bit windows 10 installed on my PC

Share this post


Link to post
Share on other sites

The only thing I can think off at this point is the problem lies in Rufus for some reason.

You can use built-in Win 10 features to create a bootable USB from here: https://fossbytes.com/create-bootable-usb-without-software-windows-10-using-command-prompt/ . In regards to the section on copying files from the SysRescue .iso to the usb drive,  you will first have to mount the .iso file via Win Explorer to get access to the files. How to do that is shown here: https://www.windowscentral.com/how-mount-or-unmount-iso-images-windows-10 .

Share this post


Link to post
Share on other sites

I tried this method and ended up getting the same error. I'm starting to think I may have the 32bit download?

Or is choosing fat32 effecting this? as Rufus was auto choosing this.

and choosing NTFS the laptop wont boot to the usb at all, the BIOS screen just refreshes

Share this post


Link to post
Share on other sites

Seemingly working!

Managed to get the legacy BIOS to boot and it work.

Not sure if this is an issue but there is text coming up saying:

"watchdog: BUG: soft lockup - CPU2 stock for 22s! [swapper/0:1]"

this has occurred a number of times is this okay?

Share this post


Link to post
Share on other sites
6 hours ago, maca said:

"watchdog: BUG: soft lockup - CPU2 stock for 22s! [swapper/0:1]"

Appears this parameter has to be added to the Grub boot menu:

Quote

Try booting with the parameter "nomodeset".

https://www.reddit.com/r/linux4noobs/comments/abae2k/watchdog_bug_soft_lockup_cpu2_stuck_for_22s/

I really know nothing about Linux but suspect the version of Linux being used by SysRescue is not compatible with your PC hardware. I also suspect the above parameter has to be added to in one of the files in the SysRescue .iso file downloaded. In other words, the .iso mounted in Win 10, the applicable file found, and the parameter added. Then, the bootable media recreated.

At this point, I advise you contact Eset technical support for Australia for further assistance.

Share this post


Link to post
Share on other sites

Thanks, for all the help.

As you said this seems to be a Linux issue, so will try out that link.

 

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...