| sem | Hey I decided to try out the 22.04 Live Image to see if I should upgrade from 20.04 | 17:00 |
|---|---|---|
| sem | So far everything seems normal except I get weird graphics things in some apps like Discover and Firefox. When I move the mouse around I get a bunch of wrong pixels in the active window. Is that a graphics driver problem? | 17:01 |
| sem | I want to make sure I can resolve this on the live environment before I try updating, but idk how to start | 17:02 |
| sem | THere are no drivers available in the additional drivers gui | 17:03 |
| tomreyn | installing and activating proprietary drivers would require a reboot, which makes no sense with a non-persistent system | 17:05 |
| tomreyn | so in case you are lacking, for example, nvidia drivers there, then such artifacts can be entirely normal. | 17:06 |
| sem | is there a way to test the nvidia drivers without committing to an upgrade? Can I install onto a USB drive, say? | 17:15 |
| sem | i have a 64 GB one I could use | 17:15 |
| tomreyn | sure | 17:22 |
| sem | Ok -- it seems that the tricky part will be what to do with GRUB -- will the installer install a new grub on the USB? Can the GRUB on my hard disk detect linux on the USB Drive? | 17:31 |
| arraybolt3 | That probably depends on whether you're using a BIOS or UEFI system. | 17:33 |
| arraybolt3 | On BIOS, it should install GRUB to the USB drive, and you can use a boot order or boot menu to select the correct drive to boot. | 17:33 |
| arraybolt3 | On UEFI, I don't know what exactly happens, but I believe it does something to the EFI partition on your main drive. | 17:34 |
| arraybolt3 | Either way you should be able to boot the USB, but you *might* encounter problems booting the already installed system after installing to the USB. (I did once - it was resolvable but a bit tricky to fix.) | 17:34 |
| sem | I am on BIOS, and I do see the option to install GRUB to the USB Drive. | 17:37 |
| sem | The problem I'm running into is the manual doesn't explain what Flags are needed: I assume "boot" and "root" ? https://manual.lubuntu.me/stable/1/1.3/installation.html | 17:38 |
| arraybolt3 | Root mount point, boot flag should work. | 17:38 |
| sem | ok, thanks | 17:39 |
| arraybolt3 | (obligatory reminder to make very sure you're wiping the right drive :) ) | 17:39 |
| sem | yes -- luckily it has a label to help | 17:40 |
| sem | one thing I noticed is that if you set "Install boot loader on" to the USB drive, but then go back and make a change, it resets itself to "Install boot loader on" the first hard drive... which is not good | 17:41 |
| sem | also the installer told me to use GPT instead of MBR so I'm trying to do that now | 17:42 |
| arraybolt3 | eh, if you use GPT you have to set slightly different flags | 17:43 |
| arraybolt3 | and use a different partition layout | 17:43 |
| arraybolt3 | for a drive the size you're using, I'd ignore than and just use MBR. | 17:43 |
| arraybolt3 | (I don't know the backstory behind how that warning got added, but I might should ask the other devs - I personally think it's somewhat unhelpful in its current state.) | 17:44 |
| sem | Ok, I'll go back and undo it. Yeah I wasn't sure why it recommends GPT over MBR; last time I researched it MBR seemed way simpler. | 17:47 |
| sem | Is there anything I can to to tell the installer that it is installing onto a USB flash drive, so if possible it should keep acting like a live system and not write too often to disk? | 17:53 |
| sem | whoa the installer display is completely broken on my system | 17:57 |
| sem | i'll try to send a picture | 17:57 |
| sem | it is either a black screen or it looks like a screensaver | 17:59 |
| sem | https://i.ibb.co/ydxCc41/imgbb.jpg | 18:04 |
| sem | is that a known bug? | 18:10 |
| sem | Is there a way to follow what the installer is doing via the terminal? | 18:25 |
| sem | top shows that calamares and rsync are still running so that's good | 18:27 |
| arraybolt3 | whoa what? | 18:35 |
| arraybolt3 | lol, that looks wrong | 18:35 |
| arraybolt3 | definitely not a known bug, probably it's the NVIDIA issues you were talking about before. | 18:35 |
| arraybolt3 | I don't think there's a way to follow what the installer is doing sadly. | 18:36 |
| arraybolt3 | I'd just wait, I dunno, thirty minutes to give it time to do everything, then reboot and hope for the best. | 18:36 |
| arraybolt3 | (I dunno = I don't know how fast your system and flash drive(s) are). | 18:36 |
| sem | i think they're pretty slow :) | 18:47 |
| sem | I'm keeping an eye on top and it is still very high hardware wait | 18:47 |
| sem | want me to report it? Some kind of generic "hey I was installing lubuntu on an old system, and the installer did this?" | 18:48 |
| arraybolt3 | As long as you're not doing it from the live session, sure. The package name is `calamares`. | 18:56 |
| arraybolt3 | I don't know if you already have experience filing bug reports on Launchpad, but you want to report against the Launchpad package, **not** the upstream Calamares repo on GitHub. | 18:56 |
| sem | i would typically report things on launchpad, but I've made mistakes before about what package to target on there | 18:59 |
| sem | I'll wait until it installs and then report it from the new install | 19:00 |
| sem | out of curiosity why not report it from the live instance? Will it not be able to send the right kind of hardware information automatically? | 19:00 |
| arraybolt3 | sem: If it's an NVIDIA problem, Firefox *may* glitch out in the same way Calamares just did. | 19:17 |
| arraybolt3 | Thus my thinking it, get your NVIDIA drivers installed first, then once everything's working smoothly try reporting. | 19:17 |
| sem | gotcha | 19:17 |
| sem | i'm gonna keep letting it do its thing and check back in a few hours | 19:18 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!
