| mort | oh this is a fun situation, I can't apt-get upgrade because I have some old linux-image-VERSION-generic packages, they depend on their corresponding linux-modules-VERSION-generic packages which aren't installable; `apt --fix-broken install`'s solution is to uninstall those old linux-image-VERSION-generic packages which is reasonable, but after | 10:28 |
|---|---|---|
| mort | removing linux packages apt wants to run update-grub; update-grub isn't working because it can't find libcrypto.so.1.1, because somehow libcrypto got updated to libcrypto.so.3 without grubcfg_proxy being updated to account for it | 10:28 |
| mort | and I can't upgrade grub because I would first have to uninstall the two broken linux-image-VERSION-generic packages | 10:28 |
| mort | in order to upgrade grub I have to let apt remove those linux packages, in order to remove those linux packages I need to upgrade grub | 10:29 |
| mort | I solved it by adding `exit 0` to the postrm scripts for those two linux image packages, but that was a hairy situation | 10:34 |
| mort | welp, seems like there is no update which fixes grubcfg_proxy | 10:41 |
| Maik | 22.04 is going to be a no-go on my T410, DMAR error issue when booting up and after clicking on the Try Ubuntu button the whole system freezes | 19:19 |
| Maik | not only the main Ubuntu desktop but other flavors too | 19:19 |
| oerheks | :-( | 19:20 |
| oerheks | maybe your fix too .. Use 'intremap=no_x2apic_optout' to override the BIOS setting. | 19:21 |
| oerheks | https://askubuntu.com/questions/1331090/dmar-firmware-bug-broken-bios | 19:21 |
| oerheks | not sure you want acpi=off too | 19:21 |
| Maik | not sure if it's even that | 19:22 |
| oerheks | sure you have the latest bios? sudo dmidecode -s bios-version | 19:22 |
| Maik | weird thing is that other distro's with the same kernel or newer work well | 19:22 |
| Maik | oerheks: there's no newer BIOS available for this 12 year old machine | 19:23 |
| oerheks | oke | 19:23 |
| oerheks | "intel_iommu=igfx_off" is an other answer? disable igp totally | 19:29 |
| Guest43 | Hi, I would like to know if there's a means to revert an update from Jammy Jellyfish to 20.04; anything I might be able to do through firmware settings or BIOS? | 21:13 |
| oerheks | Guest43, the answer in #ubuntu is correct, no downgrade, do a fresh install of 20.04 or the beta 22.04 | 21:14 |
| Guest43 | And I suppose that means that I won't be able to recover any files on my drive. | 21:15 |
| oerheks | i think you can, boot a live iso? | 21:15 |
| Guest43 | From a USB? | 21:16 |
| oerheks | yes? | 21:16 |
| oerheks | and copy to an other usb device, or 2nd hdd something | 21:16 |
| oerheks | you should have done this before upgrading, imho | 21:16 |
| Guest43 | This might be my last resort. It's worth a try. | 21:16 |
| Guest43 | I typically backup once every month. But that's on me. | 21:17 |
| ravage | major upgrades to beta releases with a backup are lame :D | 21:17 |
| Guest43 | I was careless. I didn't realize 22.04 was a beta. | 21:17 |
| Guest43 | My fuck-up | 21:18 |
| oerheks | you must have used the -d option, development | 21:18 |
| tomreyn | the 04 in 22.04 stands for april, the 22 for 2022 | 21:18 |
| Guest43 | I blindly followed these instructions here: https://linuxconfig.org/how-to-upgrade-ubuntu-to-22-04-lts-jammy-jellyfish | 21:19 |
| Guest43 | Lesson learned. | 21:19 |
| tomreyn | bad article :-/ | 21:19 |
| ravage | yep. really bad | 21:19 |
| ravage | uses all the wrong terms and no warnings | 21:20 |
| Guest43 | If booting from a live ISO works to recover my files, that'll make up for it. That's all I can ask for at this point. | 21:21 |
| guiverc | ubuntu jammy is still in alpha; beta freeze 28-march, beta release is 31-march | 21:52 |
| ravage | i dont think the term we use for the next few days matters for his problem | 21:54 |
| guiverc | no it doesn't (alpha/beta is just a label), but it's also an indication of the product; beta is more generally seen as more stable & it's not yet beta | 21:55 |
| ravage | there is no upgrade path from 20.04 to beta too. so really does not change anything here | 21:57 |
| ravage | it was just a bad idea in general | 21:57 |
| guiverc | freeze exceptions/changes are more restricted once it's beta.. not all freezes yet apply - https://discourse.ubuntu.com/t/jammy-jellyfish-release-schedule/23906 | 21:57 |
| guiverc | QA testing of the upgrade does occur; it's mostly 21.10 -> jammy currently (20.04 to jammy occurs after 22.04.1 is out months from now!) | 21:59 |
| ravage | you are preaching to the choir here :) | 21:59 |
| guiverc | :) | 22:00 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!