You are correct that I am confusing things.<br><br>12.1.0 os21 has Q4D17 (<a href="http://download.laptop.org/xo-1.75/os/official/12.1.0-21/21021o2.packages.txt">http://download.laptop.org/xo-1.75/os/official/12.1.0-21/21021o2.packages.txt</a>).<br>
<br>13.1.0 os3 has Q4D21 (<a href="http://build.laptop.org/13.1.0/os3/xo-1.75/31003o2.packages.txt">http://build.laptop.org/13.1.0/os3/xo-1.75/31003o2.packages.txt</a> - os1 & os2 also have similar).<br><br>For some reason I keep ending up off-by-one while trying to parse our new versioning scheme; sorry.<br>
<br><br><div class="gmail_quote">On Sun, Sep 23, 2012 at 9:41 PM, James Cameron <span dir="ltr"><<a href="mailto:quozl@laptop.org" target="_blank">quozl@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Oops, have I got my versions mixed? I thought it was 12.1.0 (os12)<br>
that shipped with Q4D17, and 13.1.0 (os2/os3) that currently has<br>
Q4D21.<br>
<div class="HOEnZb"><div class="h5"><br>
On Sun, Sep 23, 2012 at 09:37:57PM -0400, Samuel Greenfeld wrote:<br>
> The final version of 13.1.0 (os21) only ships with Q4D17 for XO-1.75 (Q3C07 for<br>
> XO-1.5, Q2F12 on XO-1).<br>
><br>
> I am aware that at least one USB glitch (#12034 on XO-1.5) is present in the<br>
> final release, but given this seemed non-fatal the release freeze was not<br>
> lifted to take a new firmware build.<br>
><br>
> If you believe updated firmware builds are required if we release a 13.1.1<br>
> build (and not just 14.1.0) I would recommend filing a ticket.<br>
><br>
><br>
> On Sun, Sep 23, 2012 at 9:28 PM, James Cameron <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br>
><br>
> On Sun, Sep 23, 2012 at 07:55:28PM -0500, Bruno Wolff III wrote:<br>
> > On Mon, Sep 24, 2012 at 09:28:12 +1000, James Cameron<br>
> > <<a href="mailto:quozl@laptop.org">quozl@laptop.org</a>> wrote:<br>
> > > G'day Bruno,<br>
> > ><br>
> > > Thank you for your problem report. It is interesting.<br>
> ><br>
> > I updated the trac ticket with most of what was requested.<br>
><br>
> Thanks. I'll use the ticket for summary only.<br>
><br>
> > > The install method hasn't changed. Our development builds are<br>
> > > installed using fs-update rather than the zsp file and holding<br>
> > > four game keys down. Once 13.1.0 is released, the method will be<br>
> > > the same as before.<br>
> ><br>
> > When going to 12.1.0 I held down the four buttons above the power<br>
> > switch while booting. When going to 13.1.0 I used fs-update. I was<br>
> > going by the instructions on the wiki for doing the updates.<br>
><br>
> Yes, the instructions are different, but they will be the same as<br>
> before ... once 13.1.0 is released. 13.1.0 is not yet released; you<br>
> were using a development build which requires special use of<br>
> fs-update.<br>
><br>
> > > When you upgraded your XO-1.75 to 12.1.0 an old version of Open<br>
> > > Firmware might have been present. After the upgrade, the next<br>
> > > time you had two sources of power, Open Firmware would have been<br>
> > > upgraded.<br>
> ><br>
> > I also didn't have two sources of power when I did the fs-update to<br>
> > 13.1.0, so maybe that's why the open firmware is still at Q4D17.<br>
><br>
> Yes.<br>
><br>
> There is a separate command to upgrade Open Firmware, but the<br>
> operating system boot does this automatically if two sources of power<br>
> are available ... normally at the first boot after upgrade. With only<br>
> one source of power, it will be delayed until a boot with two sources<br>
> of power.<br>
><br>
> Holding down the four buttons doesn't upgrade both the operating<br>
> system and the firmware at once, but it does upgrade the operating<br>
> system, and then the operating system upgrades the firmware at the<br>
> first available opportunity.<br>
><br>
> (In the release notes we ask for two sources of power before using the<br>
> four game keys method.<br>
> <a href="http://wiki.laptop.org/go/Release_notes/12.1.0#XO-1.75" target="_blank">http://wiki.laptop.org/go/Release_notes/12.1.0#XO-1.75</a> ... but for<br>
> development builds we expect users may manage their systems<br>
> differently.)<br>
><br>
> Using fs-update to upgrade the operating system should eventually<br>
> cause the firmware to upgrade. If this isn't happening with two<br>
> sources of power, it is a separate problem we should investigate.<br>
><br>
> > > a. what version of Open Firmware was on the XO-1.75 before the<br>
> > > upgrade to 12.1.0? I cannot guess what this was.<br>
> ><br>
> > I don't know, but probably whatever you were shipping with the<br>
> > devices a few weeks ago. Mine shipped shortly before 12.1.0 was<br>
> > released.<br>
><br>
> Thanks. I acknowledge you don't know what version worked with your<br>
> USB drive before the upgrade.<br>
><br>
> Please provide the serial number, so that I can take a guess at a<br>
> minimum firmware version. Please also use the .mfg-data command at<br>
> the ok prompt and look for the BV tag, which should list the base<br>
> firmware version used. .mfg-data also displays the SN or serial<br>
> number tag.<br>
><br>
> > > b. what version of Open Firmware was on the XO-1.75 at the time<br>
> > > of the problem in ticket #12123? I expect it was Q4D17 as this<br>
> > > was 12.1.0 build 21 contained.<br>
> ><br>
> > I can reproduce the issue on Q4D17.<br>
><br>
> Good, thanks.<br>
><br>
> > > c. what version of Open Firmware is on the XO-1.75 after the<br>
> > > upgrade to 13.1.0? I expect it will be Q4D21.<br>
> ><br>
> > It is still Q4D17.<br>
> ><br>
> > > d. if you downgrade to the version of Open Firmware you had<br>
> > > before the upgrade to 12.1.0, and then try the fs-update for<br>
> > > 13.1.0, does the problem in ticket #12123 occur?<br>
> ><br>
> > I can't refer to u: successfully if I don't plug in the drive after<br>
> > booting.<br>
> ><br>
> > > e. on Q4D21 please attach the USB drive, turn on the laptop, get<br>
> > > to the ok prompt, type p2, and tell me what is printed.<br>
> ><br>
> > I haven't got Q4D21 yet, so I can't do these tests just yet.<br>
> ><br>
> > > f. on Q4D21 please detach the USB drive, turn on the laptop, get<br>
> > > to the ok prompt, type p2, and tell me what is printed.<br>
> > ><br>
> > > g. on Q4D21 please attach the USB drive, turn on the laptop, get<br>
> > > to the ok prompt, type<br>
> ><br>
> > There were differences for the p2 command under Q4D17 depending on<br>
> > whether the drive was plugged in before or after boot.<br>
><br>
> Your p2 and scan-subtree output shows that the device does not respond<br>
> to probes if it was already plugged in when the laptop powered on.<br>
> This seems like a power on or reset problem for the drive.<br>
><br>
> Please test if this is a new behaviour of your USB drive, or a new<br>
> behaviour of Open Firmware. Downgrade to Q4D03, or if a later version<br>
> is listed in the BV tag downgrade to that, and test again with the USB<br>
> drive. You can find download links and instructions to downgrade at<br>
> <a href="http://wiki.laptop.org/go/Firmware" target="_blank">http://wiki.laptop.org/go/Firmware</a><br>
><br>
> Please test if we have already fixed this problem. Upgrade to Q4D21<br>
> and test again with the USB drive.<br>
><br>
> Please test the other two USB ports on the laptop, in case there is an<br>
> electrical problem with the port you usually use.<br>
><br>
> > > 2. the drive must spin up and become ready (if it is a mechanical<br>
> > > drive this can take some seconds),<br>
> ><br>
> > In my case it's a flash drive. (I reformtted it to ext4.)<br>
><br>
> Thanks. I have tested with a USB flash drive and a USB powered desk<br>
> lamp. The power is briefly turned on, then off for a few seconds,<br>
> then on just before the probe.<br>
><br>
> It seems unlikely, but it is possible, that your USB flash drive does<br>
> not like the brief power pulse.<br>
><br>
> Please test with a powered hub. Connect the hub to the laptop.<br>
> Connect power to the hub. Connect the flash drive to the hub. Power<br>
> up the laptop. Use p2 command.<br>
><br>
> The filesystem format of the USB flash drive should have no bearing on<br>
> the success or failure of a USB probe. But thanks for letting me know.<br>
><br>
> --<br>
> James Cameron<br>
> <a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
> _______________________________________________<br>
> Devel mailing list<br>
> <a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
> <a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
><br>
><br>
<br>
--<br>
James Cameron<br>
<a href="http://quozl.linux.org.au/" target="_blank">http://quozl.linux.org.au/</a><br>
</div></div></blockquote></div><br>