<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Trebuchet,Arial,Helvetica,sans-serif;'><div id="message"></div><div id="content">---- On Sun, 26 Apr 2020 18:20:49 +0100 <b> darylangela@gmail.com </b> wrote ----<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); padding-left: 6px; margin-left: 5px;"><div><div dir="ltr">Greetings Mythizens, wanting to incrementally play with the new beta release 20.04 I installed it alongside my working 18.04/0.29 myth system, however, install was UEFI beside Legacy, so 18.04 wouldn't boot. So I used OS-uninstaller to expunge 20.04 and 18.04 still won't boot I see a message"cx25840 11-0044: firmware v4l cx23885-avcore-01 fw load failed", then immediately into emergency mode. I reset my BIOS to only accept Legacy mode and installed a new 18.04 beside the original and it still won't boot the original, same message and shell. Is there a way to repair this? TIA Daryl</div>
_______________________________________________
<br>mythtv-users mailing list
<br><a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a>
<br><a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a>
<br><a href="http://wiki.mythtv.org/Mailing_List_etiquette" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a>
<br>MythTV Forums: <a href="https://forum.mythtv.org" target="_blank">https://forum.mythtv.org</a>
<br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;">Hello,</div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;">I'm happy to stand corrected but I'd assume the firmware error is a red herring, that's not something that would usually cause a failed boot.</div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;"><br></div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;">On you original attempt to make room for the new install, how did you do that? </div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;"><br></div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;">It sounds to me that your original root partition can not be found.</div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;"><br></div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;">This may be down to it now having a different partition number.</div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;"><br></div><div style="visibility: visible; font-family: roboto; overflow-wrap: break-word !important; line-height: normal !important;">You probably need to get a live usb running and examine where grub.cfg is expecting to find your root partition, and compare that to where it actually is.</div></div></blockquote></div></div><br></body></html>