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

The MEGA Windows on Arm thread #12

Open
daveb778 opened this Issue Apr 21, 2018 · 1,487 comments

Comments

Projects
None yet
@daveb778

daveb778 commented Apr 21, 2018

So i've gotten pretty close to getting windows 10 arm to boot. But for some reason after selecting the boot device it wont no longer detect the keyboard, when the press any key to continue prompt arrives. The numlock light will turn on but no matter what button i press nothing happens. Also since it doesnt detect a keyboard input it will go back to the last screen and the system seems to lock up at that point.
img_20180420_221029

@daveb778

This comment has been minimized.

daveb778 commented Apr 21, 2018

I've also tried two different keyboards both seem to not have an effect.

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 21, 2018

Do me a favor and repeat your experiment with the input being done over the serial input instead of USB. I bet you’ll discover similar behavior.

Actually, please send me a serial log of your experiments produced by a debug build of the UEFI firmware. That should help immensly.

I’ve seen something similar with winload.efi - it draws the pretty “uh-oh” blue screen, but the keys to reboot or exit to firmware don’t work - almost as if the code is waiting for a debugger or if interrupts are disabled. With a debug edk2 build I saw periodic UEFI messages stop printing as well.

@thchi12

This comment has been minimized.

thchi12 commented Apr 21, 2018

You can try applying the wim file manually,make two partitions on your sdcard or USB,one FAT and one NTFS,then use dism to apply the image and bcdboot to create boot files.

@thchi12

This comment has been minimized.

thchi12 commented Apr 21, 2018

AFAIK,using the latest firmware Windows still hang at the boot screen,there seems no sign of loading and no 0xc0000225

@daveb778

This comment has been minimized.

daveb778 commented Apr 21, 2018

Sadly i don't have a serial cable to hook up to the pi, tho im not too sure how to communicate with it that way my guess is a serial to usb and putty on my pc. I've seen people posting images of the 0xc0000225 blue screen and i have no idea how they are even getting that far.

@thchi12

This comment has been minimized.

thchi12 commented Apr 21, 2018

Juat as I said,apply the install.wim manually

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

Folks, I've updated the readme.md file with the steps required to build arm64 WinPE USB media. You should be able to follow them provided you have a Windows 10 machine (any will do, x86, amd64 or arm64).

Also, see https://github.com/andreiw/RaspberryPiPkg/tree/master/Binary/prebuilt/2018Apr21-GCC49, which should make it more obvious what is happening. See screenshot. You should be able to repeat my "success" (for lack of a better term, given that we're crashing somewhere in NT after UEFI exits).

img_0673

Since the current version (Apr 21st) and latest WoA WinPE bits seem to act much more reasonably than this ticket implies, I'm closing it as resolved.

@andreiw andreiw closed this Apr 22, 2018

@andreiw andreiw reopened this Apr 22, 2018

@andreiw andreiw changed the title from Usb Keyboard Not Working On Prompt to Windows on Arm doesn't work [Was: Usb Keyboard Not Working On Prompt] Apr 22, 2018

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

Guys, take a look at https://github.com/andreiw/RaspberryPiPkg/tree/master/Binary/prebuilt/2018Apr22-GCC49 and the latest notes in readme.md. Everything you need to repeat is in there.

I can get WinPE booting. If it wasn't for https://twitter.com/ntauthority 's helpful hint, wouldn't be anywhere close.

img_8602 2
img_0957
img_7883 3
img_9027

@andreiw andreiw closed this Apr 22, 2018

@andreiw andreiw reopened this Apr 22, 2018

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

I'll see if I can make any progress on SMP.

It would be nice to figure out where the MCCI (https://twitter.com/NTAuthority/status/957886027594641409) USB driver for DWC_OTC can be found.

The rest of the RPi3 drivers are open source and could be hypothetically build with the EWDK (https://github.com/ms-iot/bsp/tree/master/drivers) - untried, but it seems like @NTAUTHORITY built some.

@daveb778

This comment has been minimized.

daveb778 commented Apr 22, 2018

Wow you guys got pretty far, I'm gonna try this in a bit and see what happens.

@thchi12

This comment has been minimized.

thchi12 commented Apr 22, 2018

wow That's amazing!
Is it possible to use PSCI to get SMP?WOA needs either mppp or psci to get multicore.
According to https://zhuanlan.zhihu.com/p/34572676
Windows has built in support for BCM interrupts,and what's the problem that prevents windows from starting up?

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

This firmware already exposes PSCI support (go boot Linux and see ;-)), but the ACPI tables are as-is from MS-IoT and thus still report MPPP and no PSCI in FADT.

@thchi12

This comment has been minimized.

thchi12 commented Apr 22, 2018

In the earlier versions there were acpi tables for psci ,I wonder whether adding only dsdt ,csrt,dbg2 could help or not.

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

@thchi12, nope, unrelated.

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

As far as RPi3 support there appears to be a check in Hal validating PIC is not a BCM PIC. That’s why you need a debugger attached to patch out the ‘bls’ following the subtraction and compare.

@daveb778

This comment has been minimized.

daveb778 commented Apr 22, 2018

Would it be possible to use the usb driver from the windows IoT? Cause im trying to get my hands on the file for it.

@thchi12

This comment has been minimized.

thchi12 commented Apr 22, 2018

I don't think arm32 drivers can be used on arm64@daveb778

@daveb778

This comment has been minimized.

daveb778 commented Apr 22, 2018

@thchi12 Good point i didnt think that through.

@andreiw

This comment has been minimized.

Owner

andreiw commented Apr 22, 2018

You need a 64-bit driver. IoT core is 32-bit. Hypothetically, if I understood @NTAUTHORITY correctly, the driver might have shipped as part of the NT-based 64-bit Wndows Mobile. I don’t know much about the later, in terms of which version first had AArch64 support (8.1 or 10...).

@daveb778

This comment has been minimized.

daveb778 commented Apr 22, 2018

@andreiw I see, i guess the does beg the question how do we get hold of it.

@thchi12

This comment has been minimized.

thchi12 commented Apr 22, 2018

It seems that rx-130 phones may have win10m arm64

@daveb778

This comment has been minimized.

daveb778 commented Apr 22, 2018

Oh, also trying to make the pe disk but i keep running into errors. https://puu.sh/A8iYa/2f307aa6a4.png

@thchi12

This comment has been minimized.

thchi12 commented Apr 22, 2018

Well you can try to grab uup and make an installtion media,keeping only the efi and boot.wim under sources

@daveb778

This comment has been minimized.

daveb778 commented Apr 22, 2018

Nvm just tried a smaller sdcard that did the trick.

@Jarusss

This comment has been minimized.

Jarusss commented Oct 19, 2018

Guys, were you able to run WiFi or Ethernet?

@GlowingObsidian

This comment has been minimized.

GlowingObsidian commented Oct 20, 2018

@Jarusss I don't think WiFi and ethernet is available yet.

@RafeFails

This comment has been minimized.

RafeFails commented Oct 20, 2018

Is there touchscreen drivers yet?

@Andrew752

This comment has been minimized.

Andrew752 commented Oct 20, 2018

@GlowingObsidian I have a 5V and 2.4a power supply already (I have bought it recently) and i have tried it and it works very well with me and i think yours will do the same. I think you are right, the 17134 is more smooth and fast.

@GlowingObsidian

This comment has been minimized.

GlowingObsidian commented Oct 21, 2018

@Andrew752 then the culprit was indeed the power supply. But you misunderstood one of my points I guess. I was trying to say that in my case 17672 was working pretty smooth and fast and the usb drivers were a bit stable.

@tYLERGlockner

This comment has been minimized.

tYLERGlockner commented Oct 23, 2018

when I start up it just sits at "Press ESC in 1 seconds to skip startup.nsh or any other key to continue." when I try to boot on my raspberry pi, i have hit almost every key and nothing has happened, what do I do?(once I finihed installing it on my micro sd card, I put it in and started the boot up prosses, after the RBPi Screen where I could Esc and overclock the CPU, it comes up to this
20181022_232221

@mrmajik45

This comment has been minimized.

Contributor

mrmajik45 commented Oct 23, 2018

UEFI couldn't find the OS. So you're at stuck at a terminal.

@NJKDNSJKB

This comment has been minimized.

NJKDNSJKB commented Oct 27, 2018

why can we not run the cmd the files on windows that are given by the website

@Andrew752

This comment has been minimized.

Andrew752 commented Oct 28, 2018

@GlowingObsidian I would like to tell you a fact i haven't tried any other builds beside 17672 and i don't knew if the other one works good like this or no [seems no because you said that] but my only big problem now is the USB drivers [not stable] and the WiFi and Bluetooth drivers [no drivers].

@GlowingObsidian

This comment has been minimized.

GlowingObsidian commented Oct 28, 2018

@Andrew752 yep the biggest issue write now are the buggy usb drivers which seem to just randomly stop working after using for 15-20 mins or an hour if that somehow gets fixed then we would automatically be able to get WiFi through the USB.

@Andrew752

This comment has been minimized.

Andrew752 commented Oct 28, 2018

@GlowingObsidian Yes, good point. i hope this problem will be fixed soon.

@GlowingObsidian

This comment has been minimized.

GlowingObsidian commented Oct 28, 2018

@Andrew752 if somehow we could get hibernation to work then we would be able to boot the Pi really quick.

@mrmajik45

This comment has been minimized.

Contributor

mrmajik45 commented Oct 28, 2018

@mariobalanica

This comment has been minimized.

mariobalanica commented Oct 28, 2018

Hibernation does not use the RAM.

@5ft24dave

This comment has been minimized.

5ft24dave commented Oct 28, 2018

Any updates as to why the .cmd files from https://uup.rg-adguard.net/ error out? would really like to try this out, but without these running, I can't go any further... Is there something I am missing on my Windows 10 PC for this?

@Andrew752

This comment has been minimized.

Andrew752 commented Oct 28, 2018

Amm.. currently i don't have any issue with boot time but what is really annoying i think not just for me is the USB drivers and the Bluetooth and WiFi drivers.

@5ft24dave

This comment has been minimized.

5ft24dave commented Oct 28, 2018

is there a method of creating the .iso from the files downloaded by aria2?

@garrett1002

This comment has been minimized.

garrett1002 commented Oct 29, 2018

what in the most stable version for arm64 as of oct 29 2018

@Andrew752

This comment has been minimized.

Andrew752 commented Oct 31, 2018

@5ft24dave to use (https://uup.rg-adguard.net) [method] you need fast Internet connection and sort of "continued connected" (not the one which get disconnected after a seconds).

@5ft24dave

This comment has been minimized.

5ft24dave commented Oct 31, 2018

I've got a solid internet connection, no issues with it dropping, and for speed,
41136933

@5ft24dave

This comment has been minimized.

5ft24dave commented Oct 31, 2018

On a whim, I decided to try it on my laptop, which is running Windows 7... It ran without any issues.
It appears that my desktop PC running Windows 10 is having issues with the expand command, and that is where it dies out.

@Andrew752

This comment has been minimized.

Andrew752 commented Nov 3, 2018

I don't knew what to tell you but i have Windows 10 on my laptop and i have downloaded 3 builds without any problems.

@5ft24dave

This comment has been minimized.

5ft24dave commented Nov 3, 2018

just weird.
I actually looked in the cmd file for the command it was using with the expand, and tried it by itself, then did an expand --help, and that -f parameter is invalid
C:\Program Files\VCG\MeshLab>expand -f
expand: invalid option -- f
Try `expand --help' for more information.

C:\Program Files\VCG\MeshLab>expand --help
Usage: expand [OPTION]... [FILE]...
Convert tabs in each FILE to spaces, writing to standard output.
With no FILE, or when FILE is -, read standard input.

-i, --initial do not convert TABs after non whitespace
-t, --tabs=NUMBER have tabs NUMBER characters apart, not 8
-t, --tabs=LIST use comma separated list of explicit tab positions
--help display this help and exit
--version output version information and exit

Instead of -t NUMBER or -t LIST, -NUMBER or -LIST may be used.

Report bugs to bug-textutils@gnu.org.

C:\Program Files\VCG\MeshLab>expand --version
expand (GNU textutils) 2.0
Written by David MacKenzie.

and windows version info:

Windows 10, Version 1803, OS Build 17134.376

@binarymaster

This comment has been minimized.

binarymaster commented Nov 5, 2018

@SparrOSDeveloperTeam said:

Instead of doing Windows 10, maybe we should try and aim for building ReactOS and get it to work on the Pi. ReactOS is essentially the same thing and can be natively built as ARM.

There at least three problems that you would encounter with ReactOS on ARM:

  1. It has ARM32 port, but its not maintained for some years, you will probably have to fix ARM build first
  2. ReactOS does not have ARM64 port yet (but feel free to port it :)
  3. And to boot on RPi (and other WoA devices) it will require UEFI boot (which is not available in ReactOS at this moment)

Also keep in mind that ReactOS is alpha software, which means not stable.

...and why your post disappeared from the thread? 🤔

@driver1998

This comment has been minimized.

driver1998 commented Nov 5, 2018

@5ft24dave I am 90% sure that expand here is meant to be the Microsoft File Expansion Utility, expand.exe, which is built in to Windows for years.
Do you have some GNU tools installed? Remove those from your PATH for now.

C:\Users\driver1998>expand
Microsoft (R) File Expansion Utility
Copyright (c) Microsoft Corporation. All rights reserved.

No files specified.

C:\Users\driver1998>expand /?
Microsoft (R) File Expansion Utility
Copyright (c) Microsoft Corporation. All rights reserved.

Expands one or more compressed files.

EXPAND [-R] Source Destination
EXPAND -R Source [Destination]
EXPAND -I Source [Destination]
EXPAND -D Source.cab [-F:Files]
EXPAND Source.cab -F:Files Destination

  -R            Rename expanded files.
  -I            Rename expanded files but ignore directory structure.
  -D            Display list of files in source.
  Source        Source file specification.  Wildcards may be used.
  -F:Files      Name of files to expand from a .CAB.
  Destination   Destination file | path specification.
                Destination may be a directory.
                If Source is multiple files and -r is not specified,
                Destination must be a directory.

C:\Users\driver1998>
@5ft24dave

This comment has been minimized.

5ft24dave commented Nov 5, 2018

I didn't think to check that. I will see what is there and remove it from my PATH.
Thanks

@5ft24dave

This comment has been minimized.

5ft24dave commented Nov 5, 2018

That was it. Winavr Arduino IDE. Moved the PATH statements for that to the end of my path and it runs windows expand.exe first. Running fine with no errors. Thank you

@WinonPi

This comment has been minimized.

WinonPi commented Nov 16, 2018

Hi all, i have install windows 10 pro in rasp... its ok , but more driver for USB dont work ....
In my test ,

  • keyboard work logitech K270 in wi-fi mod ( only key and no work mouse)

  • all mouse Trust work

  • Hama adapter USB /ETHERNET crash win10 pro

tomorrow, test with other Trust branded ethernet usb adapters

@falkor2k15

This comment has been minimized.

falkor2k15 commented Nov 20, 2018

Did u guys see this update here? virtio-win/kvm-guest-drivers-windows#177

Does this help re: rp3? I guess it only applies to virtualization.

@kingdevnl

This comment has been minimized.

kingdevnl commented Nov 20, 2018

virtualization only, those are for QEMUKVM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment