https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162017-11-13T09:52:53ZpfSense bugtrackerpfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350532017-11-13T09:52:53ZRenato Botelhorenato@netgate.com
<ul><li><strong>Target version</strong> set to <i>2.4.2</i></li></ul> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350542017-11-13T09:53:23ZClinton Cory
<ul><li><strong>File</strong> <a href="/attachments/2264">capture_pfsense.jpg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2264/capture_pfsense.jpg">capture_pfsense.jpg</a> added</li><li><strong>File</strong> <a href="/attachments/2265">pfsense.jpg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2265/pfsense.jpg">pfsense.jpg</a> added</li></ul><p>Example screenshots attached.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350552017-11-13T09:56:35ZClinton Cory
<ul></ul><p>Example report from a customer (serial omitted):<br />Running 2.4.1 and trying to update Netgate Coreboot from 01.00.00.09 to 01.00.00.18.</p>
<p>Incorrect flash image file size.<br />Failed to update OEM section, exiting ...<br />Updating flashing ...<br />SN: XXXXX<br />Serial Number Read from Flash XXXXX</p>
<p>Another report from the same customer - may indicate a deeper issue at play, odd since we didn't receive reports of this prior to .18*:</p>
<p>The Coreboot of the other unit upgraded succesfully from 01.00.00.14 to 01.00.00.15. I'm doing the firmware upgrade in couple of minutes on that one too.</p>
<p>After firmware upgrade on other unit, the Coreboot version is now downgraded to 01.00.00.09. After trying to update, the same problem occurs.</p>
<p>Incorrect flash image file size.<br />Failed to update OEM section, exiting ...<br />Updating flashing ...<br />SN: XXXXXXXX<br />Serial Number Read from Flash XXXXXXXX</p>
<p>Serial omitted</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350592017-11-13T10:41:27ZClinton Cory
<ul><li><strong>File</strong> <a href="/attachments/2266">J30_2.jpg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2266/J30_2.jpg">J30_2.jpg</a> added</li><li><strong>File</strong> <a href="/attachments/2267">J30.jpg</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/2267/J30.jpg">J30.jpg</a> added</li></ul><p>Here is an older report from another customer who initially reported this:<br />After trying to upgrade coreboot from 01.00.00.15 to 01.00.00.18. The system displays question marks on the serial number (in the dashboard):<br />Serial: ����������<br />And appears to go backwards on the firmware version. It says it is currently running version 01.00.00.09.</p>
<p>The customer provided screenshots of their jumper configuration and it appears to be correct (see attached photos).</p>
<p>It seems as though the v18 upgrade is triggering a downgrade or fail-over to 8M for some reason.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350682017-11-13T11:40:42ZJose Luis Duranjlduran@gmail.com
<ul></ul><p>After powering off/on the equipment, the system shows the latest version number with the proper serial (I had no physical access to the device at that time).</p>
<p>I suspect, for this platform (RCC -- not RCCVE, RCCVE works perfectly), the adi_powercycle is not working properly.</p>
<p>EDIT: Sorry, I see there is no adi_powercycle for the RCC platform (that reboot apparently is not good enough):</p>
<p><a class="external" href="https://github.com/pfsense/FreeBSD-ports/blob/237f203ce317a86824bd4544babf750d2a7c7412/sysutils/pfSense-pkg-Netgate_Coreboot_Upgrade/files/usr/local/www/netgate_coreboot_upgrade.php#L97">https://github.com/pfsense/FreeBSD-ports/blob/237f203ce317a86824bd4544babf750d2a7c7412/sysutils/pfSense-pkg-Netgate_Coreboot_Upgrade/files/usr/local/www/netgate_coreboot_upgrade.php#L97</a></p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350692017-11-13T12:06:30ZClinton Cory
<ul></ul><p>Update from the customer in my previous comment:</p>
<p>The BIOS now shows the latest version. Apparently a physical shutdown (restart) is required. Or the adi_powercycle is not working properly for that platform.</p>
<p>The “scrambled” serial number appeared after the reboot initiated by the firmware upgrade process of the Netgate_Coreboot_Upgrade pfSense-package, as I had no physical access to the device.</p>
<p>Today, the person who took the pictures had to power off and unplug the device, producing the needed power cycle. After that, it showed the serial number and firmware version correctly.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=350782017-11-13T14:27:53ZClinton Cory
<ul></ul><p>Update from the customer in my initial post:</p>
<p>Confirmed. After power cycling, the version reported was 01.00.00.18.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=351512017-11-16T06:09:04ZRenato Botelhorenato@netgate.com
<ul></ul><p>According ADI engineers XG-2758 requires a physical power cycle after upgrade coreboot and because package tries to reboot it, it ends up booting on 2nd flash (8m).</p>
<p>Package must be changed to doesn't reboot but instead add a warning on dashboard asking user to power cycle it.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=351612017-11-16T12:38:09ZJim Pingle
<ul><li><strong>Category</strong> set to <i>Coreboot</i></li><li><strong>Target version</strong> deleted (<del><i>2.4.2</i></del>)</li></ul> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=352912017-12-04T01:38:37ZTino Zidore
<ul></ul><p>I am experiencing a problem similar to this.</p>
<p>except my XG-2758 is rebooting by it self after upgrade. And it stays on version ADI_RCC-01.00.00.09-nodebug, not ADI_RCC-01.00.00.18.</p>
<p>I have tried manual power cycle but no luck.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=352922017-12-04T01:52:12ZTino Zidore
<ul></ul><p>It worked just had to unplug the power instead of pushing the red button the back.</p> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=415732019-08-16T12:59:19ZJim Pingle
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul> pfSense Packages - Bug #8047: XG-2758 - Coreboot Upgrade - Different ROM sizehttps://redmine.pfsense.org/issues/8047?journal_id=504892021-01-23T15:32:30ZArthur Brownlee IVa.e.brownlee.iv@gmail.com
<ul></ul><p>Renato Botelho wrote:</p>
<blockquote>
<p>According ADI engineers XG-2758 requires a physical power cycle after upgrade coreboot and because package tries to reboot it, it ends up booting on 2nd flash (8m).</p>
<p>Package must be changed to doesn't reboot but instead add a warning on dashboard asking user to power cycle it.</p>
</blockquote>
<p>So that's still not working for me. I'm on 01.00.00.09 currently, and no combo of power cycles/reboots seems to update it to 01.00.00.18 which it says is available.</p>