This update resolves some important bugs ( See Ubuntu Security Notice 4432). It may be useful, for the purpose of avoiding such a misalignment in future, to ensure that the grub installer on your system is configured to install to the correct devices. There are numerous ways to achieve this, depending on your environment, but running the Boot-repair live disk worked for me. It's not actually necessary to go back to the previous version ( although that will work ), because it's not the grub runtime per se that is broken. This might not show up as a problem as long as no new dependency was introduced between the parts.Īll flavours of solution involve reinstalling grub to ensure that the two parts are aligned. If the install locations/drives are configuration - driven, and one of these locations can't be reached, then somehow a mismatch has arisen between that configuration data and reality. All that the update needs to do by default is put each part where the current parts are, because obviously that worked. This is actually still a bit of a mystery to me. Ideally, failure to do this should cause grub installation to fail, and the system should be reverted to a safe state. The root cause of the problem is that the grub update has not ensured that both parts have been updated. I would have expected the second, but the grub build system is a work of considerable art, so I don't know :). It's not 100% clear to me if grub_calloc belongs in the second, larger part or the first. The visible, run-time problem occurs when these parts are not aligned, and the function grub_calloc is not supplied. These parts must be aligned - neither part must require any functionality from the other part which is not actually there. But for most of it's functionality, it needs the second part. The first, most basic, part is the part that is started on bootup. On 'non-UEFI' systems, grub is installed in two separate parts. OK, thanks to lots of people ! Here's what I think I now understand. Is my best bet just to boot from a live CD and see if I can roll back the update to grub somehow? I noticed that this update also included 'firmware', not sure if that could be related. To me, 'symbol not found' implies some sort of build error with the grub package, but I don't really know how grub works. I'm dropped into the 'grub rescue' shell, but have no idea what to do there that might be useful. Brand String: Intel(R) Core™ / i7-5650U CPU 2.Just ran the latest batch of updates on 20.04 (Xubuntu), and now I'm getting a GRUB error: symbol 'grub_calloc' not found.Information about my test system from its BIOS: Happy to poke at this some more if there are additional things I should try. If I mount the boot partitions from the two images and run diff -r on them, they don’t appear to have any differences aside from resin changing to balena in a couple filenames.ĭoing a binary diff on the two images shows that they’re (of course) not identical, but I’m not sure which differences are significant.įor now, I’m going to just base my custom builds on 2.71.7, but obviously it’d be preferable to be able to track more recent changes as they appear. No logs or debug messages or title or anything I can paste here, just the hardware manufacturer’s splash screen for a few seconds and then an empty black display with the cursor. If I then walk forward to the next tagged version: git checkout -b bad v2.72.0+rev1Īnd write the resulting image to the exact same USB stick and put it in the exact same test system, it doesn’t even get as far as showing the grub boot menu: all I get is a completely blank screen except for a flashing cursor in the upper left. I get a flasher image that boots successfully when I write it to a USB stick and put it in my test system (details about the system at the bottom of the post). The problem seems to have been introduced in v2.72.0+rev1.įrom a balena-intel clone, if I do export MACHINE=genericx86-64-ext But if I build an older revision, it boots fine. The short version: If I build a genericx86-64-ext image from the current balena-intel master branch, the USB stick isn’t bootable on my UEFI-based system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |