=== cwaydt3 is now known as cwaydt === WrathOfA1hilles is now known as WrathOfAchilles [02:22] how do i do an unattended or script based upgrade from 18.04 to 20.04 ? I'm looking to upgrade an image on a server, automatically without user interaction. [06:21] Good morning === denningsrogue684 is now known as denningsrogue68 [17:05] waveform, the instructions in your article worked perfectly and I could now run 20.04 from usb stick, thank you very much! [17:05] only problem now is a black border around the image on screen, anyone know how to get rid of that? [17:46] linuxr, disable_overscan=1 in config.txt [17:47] (then reboot) [17:48] waveform, can I change this config.txt from the runnning system? [17:49] sure, it's just a text file -- but it is owned by root so you'll need something like "sudo vim /boot/firmware/config.txt" (assuming you're happy with vim; use nano or whatever you prefer otherwise) [17:50] waveform, great, will try [17:52] waveform, just append to the end of the file? [17:53] sure [17:59] waveform, that did the trick, thanks! what's the reason for this not being disabled by default? [18:14] linuxr, it's a pi thing generally: a lot of Pis are plugged into TVs which deliberately "overscan", i.e. leave the edges of the picture off (for historical broadcast TV reasons). That means there's a choice: boot with a black border for monitor users, or boot with the edges of the screen potentially cropped off for TV users. The former case is merely ugly, but the latter case is a usability problem given things like the menu bar potentially [18:14] disappear [18:15] hence the default is "ugly but safe" [18:15] waveform, ah I see, interesting [18:19] I seem to recall on the hirsute images we added disable_overscan=1 by default to the boot config as ubuntu users are rather more likely to be using a monitor than a TV and this saves fiddling with the boot config for new users, but I think most distros (including raspios, and historical ubuntu versions) still use the "safe but ugly" default [18:21] waveform, now that you explain it this makes sense absolutely [18:25] could it not be detected automatically on first boot with a "If you can't read this you need to enable overscan!" :D (but obviously an inverted message meaning!) [19:43] TJ-, on raspios there is a nice setup wizard which does ask on one of the pages "do you see a black border around this display?". It'd be nice to add something like that to ubuntu, but obviously that's a lot more work than just sticking disable_overscan=1 in the config.txt and if the latter proves "good enough" I doubt there'd be sufficient interest in dedicating developer time to it (given it would also be specific to one platform and [19:43] therefore more complex than adding something that would appear on all platforms) [19:44] indeed, I was being rather tongue-in-cheek [19:45] heh - well, you were right on the money with it given that's pretty much exactly what raspios does [19:47] yeah, long time since I installed that way, and most of our Pi's are headless. === znf_ is now known as znf === jelly-home is now known as jelly === tomreyn_ is now known as tomreyn