Windows on ARM
-
@stokehall said in Windows on ARM:
UBUNTU to 24.04 LTS and will then install Kernel 6.11
Just be aware the needed kernel is for fos linux and not the fog server’s host OS.
-
@stokehall said in Windows on ARM:
UBUNTU server 24.04.1 LTS ARM64 and that gives me the same error as MarkG,
Please keep testing, but I’m going to suspect the current class of linux kernels will need to be updated to 6.11 to support these new processors. Its the linux kernel devs that need to have one of these devices in their hands to debug. We’ll see mainstream linux support soon on this. This isn’t really a fog problem, but a linux kernel issue. We’ll get there when one of the fog developers have one of these systems soon too.
-
@george1421 is this the kernel that is downloaded and installed inside the fog web interface? I’m currently working through a tftp authentication issue to upgrade this.
-
@stokehall said in Windows on ARM:
is this the kernel that is downloaded and installed inside the fog web interface?
yes. but the file bzImage does go into /tftpboot it goes into /var/www/fog/service/ipxe directory.
You can also manually download the kernels from here: https://github.com/FOGProject/fos/releases and then place them in the path.
-
@george1421 I have had some small success on testing and with Oracular Desktop from 16th Sept I have managed to get it to the language selection on instal with the GUI, however it is not taking any inputs so it is definitely not a working image but it is closer than anything else so far. I have not been able to get any Linux to get any further than a small underscore on physical hardware but over VM I am able to reach the language. I can see that the system has not crashed, as the clock is updating although only if i close and reopen the VM.
This was accessed from here but I have not managed to get the 190924 version to work yet and cannot see the one I used listed: https://cdimage.ubuntu.com/daily-live/current/I fixed my TFTP issues and upgraded the kernel but as expected it is still not going any further in FOG.
-
@stokehall Thank you for the update. I didn’t think Ubuntu was going to start using kernel 6.11 for their 24.10 release, but it seems like they are, so I’ll take a look over the weekend.
-
@stokehall Just a quick oracular review and it will eventually ship with linux kernel 6.11, and it kind of works with the latest ARM processors. But we are getting close and kernel 6.11 is probably a good place to start. We might want to start with the default config for the qualcom processors and then add in the bits that FOG needs. Linux kernel 6.11 was released on 15-Sep.
-
@rodluz @george1421 Have you had any progress with this project?
-
@stokehall @george1421 I have the 6.11 kernel booting, however I am unable to get the keyboard and networking working. It seems like this keyboard issue is also affecting Linux distributions trying to build for the X1 SOCs like Ubuntu.
I have not been able to test anything on the init (imaging, registering, etc) because of the networking and keyboard issue. Also, Buildroot has not updated their linux headers to include 6.11 so I can build the new init needed. -
@rodluz That is strangely reassuring that you are seeing the same result I was, I did worry that I was doing something wrong or was unlucky when my inputs were not registering. I guess there is still a bit of work to be done to get this working. Hopefully the 6.11 supported linux headers drop soon.
-
@rodluz Good going. I also saw the issues with the lenovo’s ARM notebooks. I think we may need to wait until 6.12 is released. Yeah, without networking or keyboard you are kind of stuck. I was thinking that we could just ssh into the fos engine to bypass the keyboard issue, but then no network and no way to set root’s password. That would have to be done using buildroot to assign a default password to root. Not worth the effort until you get keyboard access. I just has a flash of an idea of a serial console, but that system probably doesn’t have a real serial port either.
-
@george1421 This seems positive, looks like we may have a working solution by the end of the year. Unfortunately as the laptops we are testing this on are the CEO’s and CTO’s new ones, I will not be able to keep hold of them much longer and so they will be unavailable for testing in 2 weeks time. I will keep following the progress of this forum but wont be able to lend a hand to testing.