Re: 11.3.1 development build 32 for XO-1.75, XO-1.5 and XO-1
os32 seems to dump core on XO-1.75 if the serial console is enabled either via the enable-serial value in olpc.fth or by holding down the check key. Bummer, wad On Mar 29, 2012, at 4:56 PM, Martin Langhoff wrote: This build brings fixes to powerd and OFW on all platforms. XO-1.75 gets a kernel fix for Libertas reset. Updatable via olpc-update -- try the cmdline below. Notes: - On XO-1.75 the getty on the serial port is _disabled_ by default now (that's the workaround). It gets enabled when you hold the check game key during boot (for verbose boot). Upgrade online with: olpc-update 11.3.1_xo1.75-32 olpc-update 11.3.1_xo1.5-32 olpc-update 11.3.1_xo1-32 Download from: http://build.laptop.org/11.3.1/os32/ Fixes (please help us confirm): #11730: Libertas: command timeout, does not recover #11723: OFW XO-1.75 - only escape key should escape to prompt Changes XO-1.75: -kernel-3.0.19_xo1.75-20120320.1540.olpc.7e610e7.armv7l +kernel-3.0.19_xo1.75-20120321.1512.olpc.1398916.armv7l -olpc-firmware-q4d05-1.unsigned.noarch +olpc-firmware-q4d08-1.unsigned.noarch -olpc-powerd-46-1.fc14.armv5tel -olpc-powerd-dbus-46-1.fc14.armv5tel +olpc-powerd-47-1.fc14.armv5tel +olpc-powerd-dbus-47-1.fc14.armv5tel Changes XO-1.5: -olpc-firmware-q3c02-1.unsigned.noarch +olpc-firmware-q3c03-1.unsigned.noarch -olpc-powerd-46-1.fc14.i686 -olpc-powerd-dbus-46-1.fc14.i686 +olpc-powerd-47-1.fc14.i686 +olpc-powerd-dbus-47-1.fc14.i686 Changes XO-1: -olpc-firmware-q2f07-1.unsigned.noarch +olpc-firmware-q2f08-1.unsigned.noarch -olpc-powerd-46-1.fc14.i686 -olpc-powerd-dbus-46-1.fc14.i686 +olpc-powerd-47-1.fc14.i686 +olpc-powerd-dbus-47-1.fc14.i686 Kernel changelog XO-1.75 Daniel Drake (1): libertas: add sd8686 reset_card support cheers, m -- mar...@laptop.org -- Software Architect - OLPC - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Server-devel] xs-pkgs
On Mar 29, 2012 5:52 PM, Tim Moody timmo...@sympatico.ca wrote: (btw installing straight from cd never worked for me as it failed on the disk partitioning regardless of the options I chose) I've seen that happen when the disk has strange partitioning information. Anaconda queries the disk, gets confused, and eventually dies. We had this after trying to use a HW RAID, and then abandoning that plan for SW RAID. The RAID controller had written some odd partitioning data on the disks. Can't remember what we did to un-jinx it. Probably switched to a VT early under the installer and used fdisk to write some bog-standard partition anaconda could make sense of :-) m ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] xs-pkgs
funny thing is that it works fine under cobbler. anaconda offered to reinitialize the partition and I let it, but still didn't help. From: Martin Langhoff Sent: Friday, March 30, 2012 7:04 AM To: Tim Moody Cc: server-devel@lists.laptop.org Subject: Re: [Server-devel] xs-pkgs On Mar 29, 2012 5:52 PM, Tim Moody timmo...@sympatico.ca wrote: (btw installing straight from cd never worked for me as it failed on the disk partitioning regardless of the options I chose) I've seen that happen when the disk has strange partitioning information. Anaconda queries the disk, gets confused, and eventually dies. We had this after trying to use a HW RAID, and then abandoning that plan for SW RAID. The RAID controller had written some odd partitioning data on the disks. Can't remember what we did to un-jinx it. Probably switched to a VT early under the installer and used fdisk to write some bog-standard partition anaconda could make sense of :-) m ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] xs-pkgs
(btw installing straight from cd never worked for me as it failed on the disk partitioning regardless of the options I chose) From a kickstart file or by hand in the installer? using the cd and taking the kickstart option. Jerry ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] xs-pkgs
In our local case, the deployment purchased a supposedly RHEL-compliant server which lacked a Linux driver for its built-in RAID controller. This RAID controller created disk partitions which spanned the full size of each disk drive. These partitions appeared when the lower-level disk controller(s) were accessed directly after the RAID controller was turned off, and caused anaconda to die whenever it tried to figure out a partitioning scheme with already-full disks. Fdisk was used to delete these partitions from a Linux terminal console, and then anaconda was happy. The inverse situation also needs to be watched out for: If you are using a Linux-supported hardware RAID controller, the individual disks/controllers below it may still be accessible, and installing directly on those could make the RAID controller unhappy. On Fri, Mar 30, 2012 at 11:51 AM, Tim Moody timmo...@sympatico.ca wrote: (btw installing straight from cd never worked for me as it failed on the disk partitioning regardless of the options I chose) From a kickstart file or by hand in the installer? using the cd and taking the kickstart option. Jerry __**_ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/**listinfo/server-develhttp://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] xs-pkgs
That is not a package, the @ makes it a group definition in the *comps.xml file in /repodata on the XS iso image. You must loopback mount the iso to view the file, then have a look for that string. Well, you're right as usual. (also I said xs-pkgs remembering 0.6, when I should have said olpc-xs). I found a file '83aa5dc6a7d65fb600d12d70ec102379a719c6bad8b6acc5c0276a8439ad251f-OLPC School Server-0.7-comps.xml' in which I found group idolpc-xs/id defaulttrue/default uservisibletrue/uservisible display_order1024/display_order nameOLPC XS/name descriptionThis group is the XS server group of packages/description packagelist packagereq type=mandatoryds-backup-server/packagereq packagereq type=mandatoryidmgr/packagereq packagereq type=mandatorymoodle-xs/packagereq packagereq type=mandatoryolpc-bios-crypto/packagereq packagereq type=mandatoryusbmount/packagereq packagereq type=mandatoryxs-activation/packagereq packagereq type=mandatoryxs-activity-server/packagereq packagereq type=mandatoryxs-config/packagereq packagereq type=mandatoryxs-rsync/packagereq packagereq type=mandatoryxs-tools/packagereq packagereq type=defaultacpid/packagereq packagereq type=defaultntp/packagereq packagereq type=defaultpuppet/packagereq /packagelist /group Still don't know why this didn't install. The anaconda-ks.cfg after the install only shows the following. Does the XS need to be able to reach the internet in order for the install to succeed? %packages @Base @Core %end so it looks like these didn't install @system-admin-tools @olpc-xs xs-release epel-release yum groupinstall OLPC XS only succeeded after I deleted everything in /etc/yum.repos.d/ except my local repo. This included external mirrors for Centos and olpcxs. How do they get into this directory? ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
