Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Apple M1 - etcher goes blank after picking image #3520

Closed
tomaszrondio opened this issue May 21, 2021 · 15 comments
Closed

Apple M1 - etcher goes blank after picking image #3520

tomaszrondio opened this issue May 21, 2021 · 15 comments

Comments

@tomaszrondio
Copy link

  • Etcher version:
    1.5.120
  • Operating system and architecture:
    Big Sur on M1
  • Image flashed:
    none :)
  • Do you see any meaningful error information in the DevTools?
    nope. Dev tools get disconnected
@rawkitscience
Copy link

Same issue here, attempted to run without the SD reader installed, no dice.

@DarkWarden85
Copy link

Same issue here, running on a raspberry pi 400 with Raspberry Pi OS.

@lurch
Copy link
Contributor

lurch commented May 26, 2021

For Raspberry Pi, see #2870
(or you could use Raspberry Pi Imager)

@2pl
Copy link

2pl commented May 29, 2021

Similar issue here, using version 1.5.120 on macbook M1 / BigSur 11.4
-opening clonezilla-live-2.7.1-22-amd64.zip => blank screen
-opening clonezilla-live-2.7.1-22-amd64.iso => works fine

@mattray
Copy link

mattray commented Jun 1, 2021

Here's the CLI output for that error:

$ /Applications/balenaEtcher.app/Contents/MacOS/balenaEtcher
(node:30189) Electron: Loading non-context-aware native module in renderer: '/Applications/balenaEtcher.app/Contents/Resources/app-arm64/generated/modules/xxhash/build/Release/hash.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(Use `balenaEtcher Helper (Renderer) --trace-warnings ...` to show where the warning was created)
(node:30189) Electron: Loading non-context-aware native module in renderer: '/Applications/balenaEtcher.app/Contents/Resources/app-arm64/generated/modules/@balena.io/usb/build/Release/usb_bindings.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
ready-to-show: 306.448ms
Checking for update
Update for version 1.5.120 is not available (latest version: 1.5.120, downgrade is disallowed).
Checking for update
Update for version 1.5.120 is not available (latest version: 1.5.120, downgrade is disallowed).
dyld: lazy symbol binding failed: Symbol not found: _lzma_get_progress
  Referenced from: /Applications/balenaEtcher.app/Contents/Resources/app-arm64/generated/modules/lzma-native/binding/lzma_native.node
  Expected in: flat namespace

dyld: Symbol not found: _lzma_get_progress
  Referenced from: /Applications/balenaEtcher.app/Contents/Resources/app-arm64/generated/modules/lzma-native/binding/lzma_native.node
  Expected in: flat namespace

attempting to burn bone-debian-10.9-iot-armhf-2021-05-28-4gb.img.xz

@jellyfish-bot
Copy link

[thundron] This issue has attached support thread https://jel.ly.fish/c0097b49-f062-40ab-a53d-2ca2551c6c6f

@Namoki
Copy link

Namoki commented Jun 28, 2021

Same here.

@alexclaydon
Copy link

I'm experiencing this on an M1 Mac. Reverting to v1.5.114 (an Intel build) resolved the issue.

@WiDesignDeveloper
Copy link

Select the application and "get info", check "open using Rosetta", it will take a while to open the first time but then will work perfectly.

@mattray
Copy link

mattray commented Aug 22, 2021

Can confirm that @WiDesignDeveloper's suggestion works.

@djaytek
Copy link

djaytek commented Aug 25, 2021

Select the application and "get info", check "open using Rosetta", it will take a while to open the first time but then will work perfectly.

yeap thank you, it worked!

@danjeltahko
Copy link

Select the application and "get info", check "open using Rosetta", it will take a while to open the first time but then will work perfectly.

Thank you, that works!

@HamishMeares
Copy link

Updating Etcher to Version 1.5.122 worked great on my M1 iMac Big Sur(11.5.2), earlier versions didn't.
No need for Rosetta, just required some permissions to write to external drive in pop-up window.

@thundron
Copy link
Contributor

thundron commented Sep 6, 2021

@HamishMeares that is extremely interesting given we got a report here #3593 saying that 1.5.122 lost the "universal" and apparently the arm64 file definitions? :/

@thundron
Copy link
Contributor

thundron commented Sep 6, 2021

we're investigating in that report anyway, so hopefully we'll have more to share either here or there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests