Re: [Server-devel] Fwd: [XSCE] UEFI workaround?
So to confirm there is no support for Secure Boot in RHEL-6 and hence CentOS-6. For this to work you'll definitely need CentOS7. If the NUC devices are baytrail the issue might not actually be SecureBoot at all but rather that they have a 32 bit uEFI implementation and that's not currently supported. Either in 32 bit CentOS-6 (32 bit doesn't support uEFI at all) and you currently can't boot a 64 bit OS from a 32 bit uEFI implementation even if the chip is 64 bit. Peter > Hi, > > My head is still bloody banging against the brick wall. > > I shipped the NUC 3401 to Nick, he should receive it today. (4gb memory, 1TB > drive) > > I can reliably create a usb stick from BERNIE to install XS (NEXS v31) on > systems which have a traditional bios. This scheme does not work on systems > with UEFI firmware. Microsoft requires > UEFI firmware for systems certified for Windows 8, so solving this problem > is unavoidable. > > The Zotac uses AMI firmware while the NUC 2820 and Gigabyte apparently use > the Intel firmware. > With the Intel firmware, there is a legacy mode. It also allows the hard > drive to be installed from the > usb stick. However, the system will not boot to the hard drive. So the next > step is to try the boot > in legacy mode. Another option is to upgrade the bootloader to Grub2 which > supports uefi. The > third step is to build an iso which installs a Grub2 bootloader. In the > longer run, NEXS needs to be > upgraded to CentOS 6.6 (32-bit) or, more ambitiously, to CentOS 7 (64-bit). > > The Zotac symptom I have also seen with bios systems and I think is really a > kickstart issue. If > the install is to a new drive, the usb stick is /dev/sda and the hard drive > is /dev/sdb. However, if the > drive has been partitioned (e.g. when I am installing a new version over an > old one), the hard drive > is /dev/sda and the usb stick is /dev/sdb. I have created two versions of > ks.cfg, one for each case. > However, this is not working for the Zotac which reports that there is not > enough space on the hard drive instead of re-partitioning. > > Any help will be greatly appreciated. > > Tony > > > > On 10/31/2014 12:50 PM, Adam Holt wrote: > > Tony Anderson’s is leaving to Africa in 6 days, assisting many different > school server deployments, and needs help getting around "secure" > BIOS/firmware UEFI on the following platforms: > > > - NUC 34010 - BIOS upgrade solves this, by moving jumper and inserting USB > memory stick containing newer Intel BIOS > > - NUC 2820 - installs but doesn't boot > > - Gigabyte Brix GB-BXBT-2807 > > - Zotac nano CI320 > > - Zotac ID81 Atom system but UEFI not Bios > > > Just in case you have any similar experience, please drop some hints, and > he'll happily reply here with Tons of more details he's tried :) > > -- > Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! > > -- > Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! > > > ___ > Server-devel mailing list > Server-devel@lists.laptop.org > http://lists.laptop.org/listinfo/server-devel > ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] Fwd: [XSCE] UEFI workaround?
From: Tony Anderson Date: Fri, Oct 31, 2014 at 2:28 PM Subject: Re: [XSCE] UEFI workaround? To: xsce-de...@googlegroups.com Hi, My head is still bloody banging against the brick wall. I shipped the NUC 3401 to Nick, he should receive it today. (4gb memory, 1TB drive) I can reliably create a usb stick from BERNIE to install XS (NEXS v31) on systems which have a traditional bios. This scheme does not work on systems with UEFI firmware. Microsoft requires UEFI firmware for systems certified for Windows 8, so solving this problem is unavoidable. The Zotac uses AMI firmware while the NUC 2820 and Gigabyte apparently use the Intel firmware. With the Intel firmware, there is a legacy mode. It also allows the hard drive to be installed from the usb stick. However, the system will not boot to the hard drive. So the next step is to try the boot in legacy mode. Another option is to upgrade the bootloader to Grub2 which supports uefi. The third step is to build an iso which installs a Grub2 bootloader. In the longer run, NEXS needs to be upgraded to CentOS 6.6 (32-bit) or, more ambitiously, to CentOS 7 (64-bit). The Zotac symptom I have also seen with bios systems and I think is really a kickstart issue. If the install is to a new drive, the usb stick is /dev/sda and the hard drive is /dev/sdb. However, if the drive has been partitioned (e.g. when I am installing a new version over an old one), the hard drive is /dev/sda and the usb stick is /dev/sdb. I have created two versions of ks.cfg, one for each case. However, this is not working for the Zotac which reports that there is not enough space on the hard drive instead of re-partitioning. Any help will be greatly appreciated. Tony On 10/31/2014 12:50 PM, Adam Holt wrote: Tony Anderson's is leaving to Africa in 6 days, assisting many different school server deployments, and needs help getting around "secure" BIOS/firmware UEFI on the following platforms: - NUC 34010 - BIOS upgrade solves this, by moving jumper and inserting USB memory stick containing newer Intel BIOS - NUC 2820 - installs but doesn't boot - Gigabyte Brix GB-BXBT-2807 - Zotac nano CI320 - Zotac ID81 Atom system but UEFI not Bios Just in case you have any similar experience, please drop some hints, and he'll happily reply here with Tons of more details he's tried :) -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] UEFI workaround?
On Fri, Oct 31, 2014 at 4:50 PM, Adam Holt wrote: > Tony Anderson’s is leaving to Africa in 6 days, assisting many different > school server deployments, and needs help getting around "secure" > BIOS/firmware UEFI on the following platforms: > > > - NUC 34010 - BIOS upgrade solves this, by moving jumper and inserting USB > memory stick containing newer Intel BIOS > > - NUC 2820 - installs but doesn't boot > > - Gigabyte Brix GB-BXBT-2807 > > - Zotac nano CI320 > > - Zotac ID81 Atom system but UEFI not Bios > > > Just in case you have any similar experience, please drop some hints, and > he'll happily reply here with Tons of more details he's tried :) Fedora/CentOS should work fine with Secure Boot enabled uEFI devices Peter ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] UEFI workaround?
If at all possible, the first thing to do is disable secure uefi boot. The only distro that I've found has out of the box support for secure boot is the Ubuntu family. Maybe there are others. Some firmwares don't support legacy boot anymore, so even unsecured, they need to boot using UEFI (make sure you install the proper bootloader). I've succeeded with Archlinux, and had to learn all about EFI booting. I recommend this step to Tony, then he can apply the knowledge to fedora. They have pretty good docs: https://wiki.archlinux.org/index.php/UEFI It's possible to install a fedora chroot under any system, but it's not ideal. Governments and deployments should really know better than buying crippled hardware. Perhaps this is an area where this community could produce formal recommendations that we would distribute to the people on charge of buying the hardware. It should really be a policy and even law. -- Sebastian Silva "icarito" #sugar #somosazucar (freenode IRC) Somos Azúcar - Fuente Libre - Sugar Labs "Las maestras y los maestros democráticos intervenimos en el mundo a través del cultivo de la curiosidad" - P.Freire El vie, 31 de oct 2014 a las 11:50 AM, Adam Holt escribió: Tony Anderson’s is leaving to Africa in 6 days, assisting many different school server deployments, and needs help getting around "secure" BIOS/firmware UEFI on the following platforms: - NUC 34010 - BIOS upgrade solves this, by moving jumper and inserting USB memory stick containing newer Intel BIOS - NUC 2820 - installs but doesn't boot - Gigabyte Brix GB-BXBT-2807 - Zotac nano CI320 - Zotac ID81 Atom system but UEFI not Bios Just in case you have any similar experience, please drop some hints, and he'll happily reply here with Tons of more details he's tried :) -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] UEFI workaround?
Tony Anderson's is leaving to Africa in 6 days, assisting many different school server deployments, and needs help getting around "secure" BIOS/firmware UEFI on the following platforms: - NUC 34010 - BIOS upgrade solves this, by moving jumper and inserting USB memory stick containing newer Intel BIOS - NUC 2820 - installs but doesn't boot - Gigabyte Brix GB-BXBT-2807 - Zotac nano CI320 - Zotac ID81 Atom system but UEFI not Bios Just in case you have any similar experience, please drop some hints, and he'll happily reply here with Tons of more details he's tried :) -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] copyright and licensing
On Fri, Oct 31, 2014 at 12:23 PM, Anish Mangal wrote: > +1 to both. Will do. > Huge thanks -- added to meeting Agenda here: https://docs.google.com/document/d/1o6QtzLb6e58YKWqMf_junux2XyBRLFm31un8YLcYslg PS 10AM vs 11AM NYC Time Thursday ain't yet carved in stone. Depends who wins the arm wrestle -- Californians seems to prefer 11AM NYC Time while Hong Kong residents prefer 10AM so they don't have to stay up till Midnight before things even start -- perhaps we oscillate week by week :-) > On Oct 31, 2014 9:37 PM, "Adam Holt" wrote: > >> Anish, >> >> Can you lay out the AGPL vs GPL choice before next week's Thur Nov 6 >> meeting? (10AM NYC Time, OK for you?) >> >> And make clear that content licensing (hosted by school server) is very >> different, as schools/districts/ministries-of-education quite reasonably >> insist they need to accommodate so many different kinds of content >> licenses? (Some of which licenses are plainly abusive, whereupon >> communities/families/teachers/kids need to mobilize, when "publishing >> innovation" becomes nothing more than a pretext mass surveillance and other >> privacy abuses.) >> >> On Fri, Oct 31, 2014 at 11:26 AM, Anish Mangal > > wrote: >> >>> GPL or AGPL? Can/Should we ask the IIAB maintainers and contributors for >>> permission to license under GPL if it's not too complicated? >>> On Oct 31, 2014 8:52 PM, "Tim Moody" wrote: >>> I am starting to write larger chunks of code and wondering what copyright and licensing I should include. Any suggestions welcome. (In Canada copyright rests with the author unless it is relinquished.) Most XS code has something like: # Copyright 2007, One Laptop per Child # Author: John Watlington # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU Library General Public # License along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA # 02111-1307, USA. IIAB has: This software is licensed with the BSD 2-clause license (See http://opensource.org/licenses/BSD-2-Clause) Copyright (c) 2013, Humane Informatics LLC All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Tim -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! -- Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! >>> ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] [XSCE] copyright and licensing
Anish, Can you lay out the AGPL vs GPL choice before next week's Thur Nov 6 meeting? (10AM NYC Time, OK for you?) And make clear that content licensing (hosted by school server) is very different, as schools/districts/ministries-of-education quite reasonably insist they need to accommodate so many different kinds of content licenses? (Some of which licenses are plainly abusive, whereupon communities/families/teachers/kids need to mobilize, when "publishing innovation" becomes nothing more than a pretext mass surveillance and other privacy abuses.) On Fri, Oct 31, 2014 at 11:26 AM, Anish Mangal wrote: > GPL or AGPL? Can/Should we ask the IIAB maintainers and contributors for > permission to license under GPL if it's not too complicated? > On Oct 31, 2014 8:52 PM, "Tim Moody" wrote: > >> I am starting to write larger chunks of code and wondering what >> copyright and licensing I should include. Any suggestions welcome. (In >> Canada copyright rests with the author unless it is relinquished.) >> >> Most XS code has something like: >> >> # Copyright 2007, One Laptop per Child >> # Author: John Watlington >> # >> # This program is free software; you can redistribute it and/or >> # modify it under the terms of the GNU Library General Public License >> # as published by the Free Software Foundation; either version 2 >> # of the License, or (at your option) any later version. >> # >> # This program is distributed in the hope that it will be useful, >> # but WITHOUT ANY WARRANTY; without even the implied warranty of >> # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the >> # GNU General Public License for more details. >> # >> # You should have received a copy of the GNU Library General Public >> # License along with this program; if not, write to the Free Software >> # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA >> # 02111-1307, USA. >> >> IIAB has: >> >> This software is licensed with the BSD 2-clause license >> (See http://opensource.org/licenses/BSD-2-Clause) >> >> Copyright (c) 2013, Humane Informatics LLC >> All rights reserved. >> >> Redistribution and use in source and binary forms, with or without >> modification, are permitted provided that the following conditions are >> met: >> >> Redistributions of source code must retain the above copyright >> notice, this >> list of conditions and the following disclaimer. >> Redistributions in binary form must reproduce the above copyright >> notice, >> this list of conditions and the following disclaimer in the documentation >> and/or other materials provided with the distribution. >> >> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS >> IS" AND >> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE >> IMPLIED >> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE >> DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE >> LIABLE >> FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL >> DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR >> SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER >> CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT >> LIABILITY, >> OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE >> USE >> OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. >> >> Tim >> >> -- >> Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! >> ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
[Server-devel] copyright and licensing
I am starting to write larger chunks of code and wondering what copyright and licensing I should include. Any suggestions welcome. (In Canada copyright rests with the author unless it is relinquished.) Most XS code has something like: # Copyright 2007, One Laptop per Child # Author: John Watlington # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU Library General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU Library General Public # License along with this program; if not, write to the Free Software # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA # 02111-1307, USA. IIAB has: This software is licensed with the BSD 2-clause license (See http://opensource.org/licenses/BSD-2-Clause) Copyright (c) 2013, Humane Informatics LLC All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Tim___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
