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

64 bit version #33

Open
AZdave opened this issue Feb 7, 2022 · 4 comments
Open

64 bit version #33

AZdave opened this issue Feb 7, 2022 · 4 comments

Comments

@AZdave
Copy link

AZdave commented Feb 7, 2022

Hi I have a pi-400 running
$ uname -a
Linux larosa-400R64 5.10.92-v8+ #1514 SMP PREEMPT Mon Jan 17 17:39:38 GMT 2022 aarch64 GNU/Linux

And I'm trying to get the 32 bit full desk top in Pi-Power--Tools.

I just get a black screen with no error indicated.

@Botspot
Copy link
Owner

Botspot commented Feb 7, 2022

I presume you are using Pi Power Tools to boot an image in a virtual desktop environment.
Behind the black box you will notice a navy-blue terminal window. This is the virtual desktop's main TTY console. If the username and password is not pi and raspberry, then you will have to manually login to the console before the desktop session will appear.

If the OS you're trying to run doesn't have a desktop session, then you can either ignore the black window, or go into Pi Power Tools settings and make it boot to CLI.

@Botspot Botspot closed this as completed Feb 7, 2022
@AZdave
Copy link
Author

AZdave commented Feb 12, 2022

I can not figure out how to login in to the shell propmt I get.

@Botspot
Copy link
Owner

Botspot commented Feb 12, 2022

I can not figure out how to login in to the shell propmt I get.

Could you send a screenshot of what you see?

@Botspot Botspot reopened this Feb 12, 2022
@nitz
Copy link

nitz commented Apr 18, 2023

Hi @Botspot,

While the issue of 64-bit versions may not be the core of the problem @AZdave is running into, I thought this may be a good spot to mention that a 64-bit flavor would be nice. I kept running into issues before I realized that the compiled executables in ./functions (buffer and zerofree) are armhf executables and thus fail to load & run on aarch64.

In particular, buffer failing prevents the "Flash" operation from working.

Cheers & thanks for the fantastic tool!

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

3 participants