Re: B2s and OFW
Mike C. Fletcher wrote: ... I just upgraded a B2-2 machine that we're wanting to reassign to another developer. Seem to have bricked the machine. Used an auto-reinstallation image (machine appeared to have the original B2-2 firmware and OS image 216 to start), upgrade to Q2D07 seemed to go fine. Unplugged, removed battery, waited, replaced battery, replaced power... no battery-charging light any more, no response on the power button at all. The machine has been sitting unused for many, many months. Had power applied for about 1/2 hour before the upgrade attempt, charging light was showing properly then. And this morning, with the battery removed, it booted and upgraded itself fine. Adding the battery back while it's running seems to show it charging. So, guess this was just a fluke. Sorry for the noise, Mike -- Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
B2s and OFW
Hi Mitch! Would you recommend using firmware version q2d07 on a B2-1 unit? And, btw, I assume 'save-nand' in q2c25 won't create the respective crc file, right? It did not in a test, at least. Thanks a lot! Ricardo Carrano ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: B2s and OFW
On 17.01.2008 02:02, Mitch Bradley wrote: Ricardo Carrano wrote: Hi Mitch! Would you recommend using firmware version q2d07 on a B2-1 unit? Yes. So Q2D07 has been tested on B2-1? How about B1 and B2-2? IIRC there were some EC changes incompatible to B1 and B2 models. (I assume my A-Test board will have to stay with some really early firmware, especially because it needs that CL2.5 patch.) Regards, Carl-Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: B2s and OFW
Yes, I installed q2d07 in two B2-1 units. I am experiencing problems with battery charging, (hence my question). But it seems is is just a coincidence. Those units did not have a pre-q2d07 life that I know and maybe the problem was already there. Thank you very much! Mitch! -- RC On Jan 16, 2008 11:13 PM, Carl-Daniel Hailfinger [EMAIL PROTECTED] wrote: On 17.01.2008 02:02, Mitch Bradley wrote: Ricardo Carrano wrote: Hi Mitch! Would you recommend using firmware version q2d07 on a B2-1 unit? Yes. So Q2D07 has been tested on B2-1? How about B1 and B2-2? IIRC there were some EC changes incompatible to B1 and B2 models. (I assume my A-Test board will have to stay with some really early firmware, especially because it needs that CL2.5 patch.) Regards, Carl-Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: B2s and OFW
Carl-Daniel Hailfinger wrote: On 17.01.2008 02:02, Mitch Bradley wrote: Ricardo Carrano wrote: Hi Mitch! Would you recommend using firmware version q2d07 on a B2-1 unit? Yes. So Q2D07 has been tested on B2-1? How about B1 and B2-2? IIRC there were some EC changes incompatible to B1 and B2 models. I don't have a B2-2, so I can't test that. But I don't know of any reason why it wouldn't work. I just loaded Q2D07 on a B1. It seems to be working okay from the firmware side of things - I can do copy-nand network accesses and dir nand:\ and things like that. But the kernel is hanging somewhere in the early startup - no kernel messages on either the screen or the serial port. I'm not entirely surprised; IIRC that B1 was flaky the last time I tested it, which was some time ago. Oh, I see what is happening. This B1 has a bad 14 MHz clock - the OFW diags caught the problem. So my best guess is that Q2D07 is good on everything B and later. (I assume my A-Test board will have to stay with some really early firmware, especially because it needs that CL2.5 patch.) We aren't supporting A-test anymore with the EC code. Regards, Carl-Daniel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: B2s and OFW
Mitch Bradley wrote: ... I don't have a B2-2, so I can't test that. But I don't know of any reason why it wouldn't work. I just loaded Q2D07 on a B1. It seems to be working okay from the firmware side of things - I can do copy-nand network accesses and dir nand:\ and things like that. But the kernel is hanging somewhere in the early startup - no kernel messages on either the screen or the serial port. I'm not entirely surprised; IIRC that B1 was flaky the last time I tested it, which was some time ago. Oh, I see what is happening. This B1 has a bad 14 MHz clock - the OFW diags caught the problem. So my best guess is that Q2D07 is good on everything B and later. I just upgraded a B2-2 machine that we're wanting to reassign to another developer. Seem to have bricked the machine. Used an auto-reinstallation image (machine appeared to have the original B2-2 firmware and OS image 216 to start), upgrade to Q2D07 seemed to go fine. Unplugged, removed battery, waited, replaced battery, replaced power... no battery-charging light any more, no response on the power button at all. The machine has been sitting unused for many, many months. Had power applied for about 1/2 hour before the upgrade attempt, charging light was showing properly then. It's possibly just a coincidence that it's bricked on this update (might have done it on any update, the machine has been sitting unused for a long time, there could be a battery-discharge issue or the like). Anyway, if someone has advice on how to un-brick (or debug) it would be appreciated, Mike -- Mike C. Fletcher Designer, VR Plumber, Coder http://www.vrplumber.com http://blog.vrplumber.com ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
