I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
The initial release is based on MATE desktop environment. Expect to see KDE, XFCE, LXDE, and SUGAR to land in the next few days.
Exact steps: (assume the sdcard is /dev/sdz)
# fetch the remix image wget http://parasense.fedorapeople.org/f19-chromebook-MATE.img.xz
# write the image to sdcard sudo xzcat f19-chromebook-MATE.img.xz > /dev/sdz
# resize the rootfs partition sudo sgdisk -p -a8192 -e -d5 -n5:0:0 -t5:8300 -c5:'ROOTFS' -p /dev/sdz
# resize the rootfs ext4 filesystem sudo e2fsck -f /dev/sdz5 sudo resize2fs /dev/sdz5
#THE END
For more details please visit our REMIX site at: https://fedoraproject.org/wiki/Architectures/ARM/F19/Remixes
Please note this is an unofficial REMIX image. For support, you can find me (masta) in #fedora-arm on IRC
Thanks, -Jon Disnard fas: parasense irc: masta
On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
Sorry to slightly hijack this thread. I will try your remix later.
Reading the comments on https://lwn.net/Articles/557132/#Comments it seems as if the news on KVM on the Chromebook is not good. It doesn't boot into HYP mode, and there's no way to make it boot into HYP mode, so KVM won't be supported. Is that right?
Rich.
On 07/05/2013 05:07 AM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
Sorry to slightly hijack this thread. I will try your remix later.
Reading the comments on https://lwn.net/Articles/557132/#Comments it seems as if the news on KVM on the Chromebook is not good. It doesn't boot into HYP mode, and there's no way to make it boot into HYP mode, so KVM won't be supported. Is that right?
That's roughly what I'd expect to be the case. There might be a signed U-Boot someone has hacked that does enable HYP mode, but otherwise I suspect you're out of luck. I'll ask around during Linaro Connect.
Note that this is also specifically why I had the UEFI binding for ARMv8 modified (a long time ago, in a galaxy far far away) such that we *always* mandate that the OS be entered at the EL2 exception level (not privilege level in ARMv8 - different), and that we have a standard way to install a Hypervisor. Unfortunately, on 32-bit systems, you need to rely upon a magic SMC or similar to do it, and we can't rely on that being available, or standardized yet. Bottom line is this goes away.
Jon.
On Fri, Jul 05, 2013 at 11:30:01AM -0400, Jon Masters wrote:
On 07/05/2013 05:07 AM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
Sorry to slightly hijack this thread. I will try your remix later.
Reading the comments on https://lwn.net/Articles/557132/#Comments it seems as if the news on KVM on the Chromebook is not good. It doesn't boot into HYP mode, and there's no way to make it boot into HYP mode, so KVM won't be supported. Is that right?
That's roughly what I'd expect to be the case. There might be a signed U-Boot someone has hacked that does enable HYP mode, but otherwise I suspect you're out of luck. I'll ask around during Linaro Connect.
I asked about this on #kvm-arm earlier today and got this long reply:
11:58 < rwmjones> I'm reading a comment here: 11:58 < rwmjones> https://lwn.net/Articles/557561/ 11:58 < rwmjones> which suggests that KVM on the Samsung Chromebook 2012 (ARM A15 version) isn't possible because the bootloader doesn't boot into HYP mode 11:58 < rwmjones> is this true? if so is there a way around it? 11:59 < pm215> IIRC the bootloader gets control in secure-SVC 11:59 < pm215> it is from there possible to get to NS-HYP 11:59 < pm215> it's just that the stock bootloader doesn't do this before booting the kernel 11:59 < rwmjones> so what's involved in making it work? 11:59 < pm215> somebody needs to write some code and get it into the bootloader 12:00 < rwmjones> ok, and the bootloader can be replaced (next comment down suggests this requires soldering)? 12:01 < pm215> I believe this to be true, though I don't have a chromebook 12:01 < pm215> I think you get the google bootloader to chain boot some other bootloader which you do have control of, and then that can actually boot your os 12:02 < suihkulokki> or maybe we could just prepend some code in front of the kernel zimage that switches to HYP mode? 12:02 < pm215> nope 12:02 < suihkulokki> damn 12:02 < pm215> we spent quite a long time being very firm that the ABI here is "bootloader's job to get this right" 12:03 < pm215> there are some u-boot patches currently going through code review to do the go-to-hyp-mode thing properly for arndale 12:03 < pm215> hopefully if they get upstream it will be more straightforward to say "ok, I have $other-board and it needs to do this too" 12:05 < apritzel> which would require that the Chromebook u-boot support is upstream as well 12:05 < apritzel> AFAIK this is not the case currently
[There's more of this, but that seems to cover the main points]
Reading around this, it does seem as if it's possible to get from secure SVC to HYP (although not easy).
Rich.
Was there ever a resolution to this? I am happy to file a bug in the chromium tracker to get this looked at, if needed.
Adam
On Fri, Jul 5, 2013 at 12:16 PM, Richard W.M. Jones rjones@redhat.com wrote:
On Fri, Jul 05, 2013 at 11:30:01AM -0400, Jon Masters wrote:
On 07/05/2013 05:07 AM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
Sorry to slightly hijack this thread. I will try your remix later.
Reading the comments on https://lwn.net/Articles/557132/#Comments it seems as if the news on KVM on the Chromebook is not good. It doesn't boot into HYP mode, and there's no way to make it boot into HYP mode, so KVM won't be supported. Is that right?
That's roughly what I'd expect to be the case. There might be a signed U-Boot someone has hacked that does enable HYP mode, but otherwise I suspect you're out of luck. I'll ask around during Linaro Connect.
I asked about this on #kvm-arm earlier today and got this long reply:
11:58 < rwmjones> I'm reading a comment here: 11:58 < rwmjones> https://lwn.net/Articles/557561/ 11:58 < rwmjones> which suggests that KVM on the Samsung Chromebook 2012 (ARM A15 version) isn't possible because the bootloader doesn't boot into HYP mode 11:58 < rwmjones> is this true? if so is there a way around it? 11:59 < pm215> IIRC the bootloader gets control in secure-SVC 11:59 < pm215> it is from there possible to get to NS-HYP 11:59 < pm215> it's just that the stock bootloader doesn't do this before booting the kernel 11:59 < rwmjones> so what's involved in making it work? 11:59 < pm215> somebody needs to write some code and get it into the bootloader 12:00 < rwmjones> ok, and the bootloader can be replaced (next comment down suggests this requires soldering)? 12:01 < pm215> I believe this to be true, though I don't have a chromebook 12:01 < pm215> I think you get the google bootloader to chain boot some other bootloader which you do have control of, and then that can actually boot your os 12:02 < suihkulokki> or maybe we could just prepend some code in front of the kernel zimage that switches to HYP mode? 12:02 < pm215> nope 12:02 < suihkulokki> damn 12:02 < pm215> we spent quite a long time being very firm that the ABI here is "bootloader's job to get this right" 12:03 < pm215> there are some u-boot patches currently going through code review to do the go-to-hyp-mode thing properly for arndale 12:03 < pm215> hopefully if they get upstream it will be more straightforward to say "ok, I have $other-board and it needs to do this too" 12:05 < apritzel> which would require that the Chromebook u-boot support is upstream as well 12:05 < apritzel> AFAIK this is not the case currently
[There's more of this, but that seems to cover the main points]
Reading around this, it does seem as if it's possible to get from secure SVC to HYP (although not easy).
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Wed, Aug 7, 2013 at 4:47 PM, Adam Goode adam@spicenitz.org wrote:
Was there ever a resolution to this? I am happy to file a bug in the chromium tracker to get this looked at, if needed.
None that I'm aware of but if you could file a bug in the chromium tracker that would be fab.
Peter
Adam
On Fri, Jul 5, 2013 at 12:16 PM, Richard W.M. Jones rjones@redhat.com wrote:
On Fri, Jul 05, 2013 at 11:30:01AM -0400, Jon Masters wrote:
On 07/05/2013 05:07 AM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
Sorry to slightly hijack this thread. I will try your remix later.
Reading the comments on https://lwn.net/Articles/557132/#Comments it seems as if the news on KVM on the Chromebook is not good. It doesn't boot into HYP mode, and there's no way to make it boot into HYP mode, so KVM won't be supported. Is that right?
That's roughly what I'd expect to be the case. There might be a signed U-Boot someone has hacked that does enable HYP mode, but otherwise I suspect you're out of luck. I'll ask around during Linaro Connect.
I asked about this on #kvm-arm earlier today and got this long reply:
11:58 < rwmjones> I'm reading a comment here: 11:58 < rwmjones> https://lwn.net/Articles/557561/ 11:58 < rwmjones> which suggests that KVM on the Samsung Chromebook 2012 (ARM A15 version) isn't possible because the bootloader doesn't boot into HYP mode 11:58 < rwmjones> is this true? if so is there a way around it? 11:59 < pm215> IIRC the bootloader gets control in secure-SVC 11:59 < pm215> it is from there possible to get to NS-HYP 11:59 < pm215> it's just that the stock bootloader doesn't do this before booting the kernel 11:59 < rwmjones> so what's involved in making it work? 11:59 < pm215> somebody needs to write some code and get it into the bootloader 12:00 < rwmjones> ok, and the bootloader can be replaced (next comment down suggests this requires soldering)? 12:01 < pm215> I believe this to be true, though I don't have a chromebook 12:01 < pm215> I think you get the google bootloader to chain boot some other bootloader which you do have control of, and then that can actually boot your os 12:02 < suihkulokki> or maybe we could just prepend some code in front of the kernel zimage that switches to HYP mode? 12:02 < pm215> nope 12:02 < suihkulokki> damn 12:02 < pm215> we spent quite a long time being very firm that the ABI here is "bootloader's job to get this right" 12:03 < pm215> there are some u-boot patches currently going through code review to do the go-to-hyp-mode thing properly for arndale 12:03 < pm215> hopefully if they get upstream it will be more straightforward to say "ok, I have $other-board and it needs to do this too" 12:05 < apritzel> which would require that the Chromebook u-boot support is upstream as well 12:05 < apritzel> AFAIK this is not the case currently
[There's more of this, but that seems to cover the main points]
Reading around this, it does seem as if it's possible to get from secure SVC to HYP (although not easy).
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On 7 August 2013 16:51, Peter Robinson pbrobinson@gmail.com wrote:
On Wed, Aug 7, 2013 at 4:47 PM, Adam Goode adam@spicenitz.org wrote:
Was there ever a resolution to this? I am happy to file a bug in the chromium tracker to get this looked at, if needed.
None that I'm aware of but if you could file a bug in the chromium tracker that would be fab.
Well it is possible to get KVM running on the Chromebook, it isn't perfect but it does work (somethings will be dropped - suspend/resume to name one). To give it a whirl you should read www.virtualopensystems.com/media/chromebook/chromebook.pdf
I've not looked at integrating the changes into a distro, but there's no reason one couldn't use it as a starter for 10.
Regards,
Andy
On Fri, Jul 5, 2013 at 12:16 PM, Richard W.M. Jones rjones@redhat.com wrote:
On Fri, Jul 05, 2013 at 11:30:01AM -0400, Jon Masters wrote:
On 07/05/2013 05:07 AM, Richard W.M. Jones wrote:
On Wed, Jul 03, 2013 at 11:59:28AM -0500, Jon wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
Sorry to slightly hijack this thread. I will try your remix later.
Reading the comments on https://lwn.net/Articles/557132/#Comments it seems as if the news on KVM on the Chromebook is not good. It doesn't boot into HYP mode, and there's no way to make it boot into HYP mode, so KVM won't be supported. Is that right?
That's roughly what I'd expect to be the case. There might be a signed U-Boot someone has hacked that does enable HYP mode, but otherwise I suspect you're out of luck. I'll ask around during Linaro Connect.
I asked about this on #kvm-arm earlier today and got this long reply:
11:58 < rwmjones> I'm reading a comment here: 11:58 < rwmjones> https://lwn.net/Articles/557561/ 11:58 < rwmjones> which suggests that KVM on the Samsung Chromebook 2012 (ARM A15 version) isn't possible because the bootloader doesn't boot into HYP mode 11:58 < rwmjones> is this true? if so is there a way around it? 11:59 < pm215> IIRC the bootloader gets control in secure-SVC 11:59 < pm215> it is from there possible to get to NS-HYP 11:59 < pm215> it's just that the stock bootloader doesn't do this before booting the kernel 11:59 < rwmjones> so what's involved in making it work? 11:59 < pm215> somebody needs to write some code and get it into the bootloader 12:00 < rwmjones> ok, and the bootloader can be replaced (next comment down suggests this requires soldering)? 12:01 < pm215> I believe this to be true, though I don't have a chromebook 12:01 < pm215> I think you get the google bootloader to chain boot some other bootloader which you do have control of, and then that can actually boot your os 12:02 < suihkulokki> or maybe we could just prepend some code in front of the kernel zimage that switches to HYP mode? 12:02 < pm215> nope 12:02 < suihkulokki> damn 12:02 < pm215> we spent quite a long time being very firm that the ABI here is "bootloader's job to get this right" 12:03 < pm215> there are some u-boot patches currently going through code review to do the go-to-hyp-mode thing properly for arndale 12:03 < pm215> hopefully if they get upstream it will be more straightforward to say "ok, I have $other-board and it needs to do this too" 12:05 < apritzel> which would require that the Chromebook u-boot support is upstream as well 12:05 < apritzel> AFAIK this is not the case currently
[There's more of this, but that seems to cover the main points]
Reading around this, it does seem as if it's possible to get from secure SVC to HYP (although not easy).
Rich.
-- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
arm mailing list arm@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/arm
On Wed, Aug 07, 2013 at 11:47:28AM -0400, Adam Goode wrote:
Was there ever a resolution to this? I am happy to file a bug in the chromium tracker to get this looked at, if needed.
Not that I know of, but in the meantime we found this interesting document:
https://lists.cs.columbia.edu/pipermail/kvmarm/2013-July/006481.html
I've not had time to work on this recently, but I'm getting an external hard drive for my Chromebook soon and I hope I can start using that for Fedora.
Rich.
As promised the other desktop environment spins have landed:
KDE LXDE MATE MINIMAL XFCE
These are located at my Fedora people page [1] Instruction are located on the Fedora-arm remix wiki [2]
Going forward I plan to gradually improve these images. * The next step is to provide a better kernel more inline with Fedora kernel standards. * Later down the road hope to use the Fedora Multi-Platform kernel once upstream Exynos support improves. * nv-u-boot (chainned bootloader) support
Some folks have expressed interest in an easy way to put these images on the internal SSD. That should be possible, but I've not tried. Will probably provide a tarball of the minimal rootfs to enable people to update the script published earlier this year by Daniel Berrangé [3]
[1] http://parasense.fedorapeople.org/ [2] https://fedoraproject.org/wiki/Architectures/ARM/F19/Remixes [3] https://www.berrange.com/posts/2013/03/31/automated-install-of-fedora-18-arm...
Thanks, -Jon Disnard fas: parasense irc: masta
On Wed, Jul 3, 2013 at 12:59 PM, Jon Parasense@fedoraproject.org wrote:
I'm pleased to announce the availability of Fedora 19 for the 2012 Samsung Chromebook featuring ARM Exynos dual core A15 processor.
The initial release is based on MATE desktop environment. Expect to see KDE, XFCE, LXDE, and SUGAR to land in the next few days.
Exact steps: (assume the sdcard is /dev/sdz)
# fetch the remix image wget http://parasense.fedorapeople.org/f19-chromebook-MATE.img.xz
# write the image to sdcard sudo xzcat f19-chromebook-MATE.img.xz > /dev/sdz
# resize the rootfs partition sudo sgdisk -p -a8192 -e -d5 -n5:0:0 -t5:8300 -c5:'ROOTFS' -p /dev/sdz
# resize the rootfs ext4 filesystem sudo e2fsck -f /dev/sdz5 sudo resize2fs /dev/sdz5
#THE END
For more details please visit our REMIX site at: https://fedoraproject.org/wiki/Architectures/ARM/F19/Remixes
Please note this is an unofficial REMIX image. For support, you can find me (masta) in #fedora-arm on IRC
Thanks, -Jon Disnard fas: parasense irc: masta
-
Adam Goode -
Andrew Wafaa -
Jon -
Jon Masters -
Peter Robinson -
Richard W.M. Jones