/srv/irclogs.ubuntu.com/2019/08/11/#ubuntu-discuss.txt

lotuspsychjegood morning to all02:04
pragmaticenigmanighty night02:06
lotuspsychjehey pragmaticenigma02:06
pragmaticenigmayo02:06
pragmaticenigmathink we finally got B|akops straightend out02:07
pragmaticenigmaat least for now02:07
lotuspsychjeoh yeah? what served him finally?02:07
daftykinsuntil next time? :)02:07
pragmaticenigmaWhat it appears to be, is the hope that Ubuntu (linux) will magicially breath new life into a 13 year old computer and have all the bells and whistles02:08
pragmaticenigmatonight it was glitchy graphics, because they were attempting to install the proprietary drivers and manually trying to install other drivers for an ATI Mobility Radeon X140002:09
pragmaticenigmaA chipset that is so old, it is best served by the default opensource drivers02:09
* daftykins chuckles02:09
pragmaticenigmaThey even claimed as much when they said everything was running smoothly on the USB live instances02:09
daftykinspolishing a turd is a true favourite of open source converts02:09
lotuspsychjei explained him, i ran xenial/bionic for years on my amd3200 + ati x800 with 2gb02:09
lotuspsychjetweaked of course but..02:10
pragmaticenigmalotuspsychje: but I imagine you are not installing the proprietary drivers for that... or if you are, you sought out the ones for that particualr chipset02:10
pragmaticenigmaI think they come away with a better understanding of what's going on at the very least... now we just have to get them to move away from Unity02:13
lotuspsychjepragmaticenigma: my x800 finally died, so i had to buy other goodies :p02:14
pragmaticenigmaThe statement I gave them about if they don't like the changes made, then move over to Lubuntu or Xubuntu ... since neither has changed much at all since 12.0402:14
pragmaticenigmaat least interface wise... under the hood they've had lots of changes, but they strive to keep a familiar interface through and through02:15
lotuspsychjeyeah he didnt want lightweight, cause ubuntu-desktop is 'purple' bling bling02:15
pragmaticenigmaright... not that you can't achieve the same feel on Lubuntu02:15
BluesKajHowdy folks11:17
EoflaOEHi BluesKaj11:17
BluesKajhi EoflaOE11:17
TJ-Sunday morning progress - fixed the mouse sending spurious scroll-wheel events... took it apart again, opened the rotating switch itself, IPA-ed it and generally poked about, and re-assembled. Must have been something conductive caught in the spring-loaded prongs11:54
EoflaOETJ-: Nice. Are there any problems left?12:22
TJ-I think I've made it smoother than it ever was but that may just be me being hyper-sensitive to it after suffering for a month or so!12:23
TJ-It's a definite relief though to not have to use the touchpad to scroll!12:24
EoflaOEOK. Would you be able to help me about making GRUB use 1440x900 resolution? Since I use 19.10 I will have to ask in #ubuntu+1.12:26
MathisenEoflaOE, edit /etc/default/grub GRUB_GFXMODE=whatever12:37
EoflaOEMathisen: I already did that in the past and updated GRUB, but it still is 1024x76812:38
Mathisentry adding GRUB_GFXPAYLOAD="keep"12:39
EoflaOEI already have it added as well.12:40
Mathisenthen im out of ideas12:40
Mathisenbut that should work12:40
EoflaOEYes, should have worked, but didn't.12:41
lotuspsychjehey EoflaOE12:44
MathisenEoflaOE, may be related https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/175383712:44
ubot5Ubuntu bug 1752767 in grub2-signed (Ubuntu Bionic) "duplicate for #1753837 grub2 regression, simultaneous console and video graphical glitches with new patch" [Undecided,Fix released]12:44
lotuspsychjeand hi Mathisen TJ-12:44
EoflaOEMathisen: I can't see --append on the 00_header. Where can it be found?12:50
TJ-EoflaOE: because the fix mentioned in those bugs removed it12:51
EoflaOEOK.12:53
EoflaOEI put the quotes around the resolution, still nothing. Did I found a bug? My GPU is AND Radeon 9200 Series.12:57
EoflaOEAMD*12:58
lotuspsychjeEoflaOE: did you test physical vs VM ?13:11
EoflaOEPhysical on my old PC.13:12
lotuspsychjeEoflaOE: no grub res problem there?13:13
EoflaOEI told it to set it to 1440x900 and updated grub, however it reverts back to 1024x768.13:14
OerHeksradeon 9200 .. too old13:18
EoflaOEYes. Too old.13:18
OerHeksi remember it is an onboard GPU13:18
EoflaOERadeon 9200 is the dedicated GPU that you can insert and remove.13:19
=== lotus|i7 is now known as lotus|NUC
TJ-EoflaOE: use 'videoinfo' from GRUB shell to find out what modes it detects (from firmware) https://www.gnu.org/software/grub/manual/grub/grub.html#videoinfo13:23
EoflaOETJ-: OK. I saw resolutions like 640x480, 800x600, 1024x768, etc. Although the preferred mode is 1440x900, it's not listed there. The 0x123 is selected. I can't go up to see the rest.13:25
TJ-EoflaOE: use "set pager=1" then rerun the command13:26
OerHeksit is not a bug, just a too old gpu, RV280 https://help.ubuntu.com/community/RadeonDriver#Supported.2C_but_hardware_is_too_old_for_Unity13:27
EoflaOETJ-: Thanks. The Cirrus CLGD 5446 PCI Video driver, Bochs PCI video driver, and the VGA Video Driver say "No Info Available",   then, on VESA BIOS Extension Video Driver, I first saw my VRAM which is 12MB which is wrong, then the paletted planar and paletted resolutions of 800x600 and 1024x760. But there is no 1440x900 resolution available on the I13:29
EoflaOEnfo.13:29
TJ-EoflaOE: which is why GRUB cannot set the mode correctly then13:34
EoflaOEOK Thanks anyways.13:35
TJ-EoflaOE: is that system UEFI or BIOS boot ?13:39
EoflaOEBIOS. My old PC can't do UEFI because it's from 2004.13:40
TJ-EoflaOE: If UEFI there ought to be a GOP driver which would correctly report modes13:40
TJ-Ahhh... ouch, that is old!13:40
ZaZaGXupdate it!13:40
TJ-Back then even VGA BIOS functions often didn't report a correct list of modes, only hard-coded standard SVGA modes, and 1440x900 isn't one of them13:41
ZaZaGXohhh ok13:41
EoflaOEOK. Thanks for the clarification.13:42
ZaZaGXI think Ubuntu doesn't like my laptop13:45
OerHeksnot only ubuntu, whole linux does not like your gpu :-(13:45
ZaZaGX:(13:46
OerHeksnot sure there are AGPx2/x4 cards supported13:47
ZaZaGXthats pretty old13:47
EoflaOEZaZaGX: What is your GPU?13:47
ZaZaGXIntel UHD graphics 62013:48
OerHeksoh, i swiched cards, intel 620 should work fine13:49
EoflaOEToo new. Mine on my new PC is UHD 630.13:49
ZaZaGXhmmm13:51
ZaZaGXDoes the new Ubuntu 18.04.3 kernel saves more battery life like in the 19.04?13:53
OerHeksZaZaGX, there are no stats about that, it depends on the services installed i guess13:53
ZaZaGXwell i remember reading since 18.10, its supposedly support better battery life13:54
ZaZaGXwell, i kind of miss Ubuntu. it gave me like 1-2 more hours of battery life14:01
Kon-lotuspsychje: You asked me if I'd reported my bug, here it is https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/183975014:58
ubot5Ubuntu bug 1839750 in linux-signed-hwe (Ubuntu) "40% performance loss in Mesa with Linux 5.0" [Undecided,New]14:58
lotuspsychjetnx Kon-15:24
lotuspsychjeKon-: can you also attach your dmesg booting 5.0.0.23 please15:25
Kon-Actually have no idea what that is15:27
lotuspsychje!dmesg | Kon-15:27
ubot5Kon-: dmesg is a console command which outputs the kernel ring buffer - an important log for diagnosing problems in  Linux. Often when something errors with hardware it will result in additional lines reported which can be seen by running dmesg in a console.15:27
Kon-Interesting, thanks15:31
lotuspsychjeKon-: you can save it in a .txt if you like, then add to the bug as attachment (booted from 5.0.0.23)15:36
lotuspsychjeKon-: it might also be interesting to describe, how you measured the 40% loss exactly? do you benchmark?15:38
Kon-Sure thing, let me go do that real quick15:39
lotuspsychjeKon-: tnx for taking your time to do this15:39
Kon-Well, I certainly want this fixed lol15:39
lotuspsychjedmesg has been attached to bug #183975015:50
ubot5bug 1839750 in linux-signed-hwe (Ubuntu) "40% performance loss in Mesa with Linux 5.0" [Undecided,New] https://launchpad.net/bugs/183975015:50
daftykinsgoing so new probably needs a PPA'd newer shiny mesa15:53
lotuspsychjenot sure whats going on, he's fine on kernel 4.1815:55
lotuspsychjeKon-: tnx for updating your bug + dmesg, pretty useful!16:01
Kon-No problem16:02
lotuspsychjeKon-: can you show us: sudo lshw -C video plz?16:05
Kon-Sure16:10
Kon-added that to the description16:12
lotuspsychjetnx16:13
lotuspsychjeTJ-: i know youre all over the place, but its raining install bugs in #ubuntu-bugs-announce16:20
jeremy31failed to install grub-efi-amd64 to /target?16:21
lotuspsychjegrub-installer & ubiquity filed against16:23
lotuspsychjebug #183976116:23
ubot5bug 1839761 in grub-installer (Ubuntu) "grub" [Undecided,New] https://launchpad.net/bugs/183976116:23
lotuspsychjebug #183976216:23
ubot5bug 1839762 in grub-installer (Ubuntu) "grub error" [Undecided,New] https://launchpad.net/bugs/183976216:23
lotuspsychjebug #183977016:23
ubot5bug 1839770 in ubiquity (Ubuntu) "NVMe. Crash during installation" [Undecided,New] https://launchpad.net/bugs/183977016:23
lotuspsychjebug #183977116:23
ubot5bug 1839771 in ubiquity (Ubuntu) "Install of 19.04 failed on Lenovo Thinkpad W520" [Undecided,New] https://launchpad.net/bugs/183977116:23
jeremy31It seems grub has problems installing to EFI with an internet connection after any update to grub packages16:24
TJ-is that for 19.10 or others ?16:27
jeremy31TJ-: pretty much everything since 18.0416:27
jeremy31There was a big outbreak on July 10, 201816:33
TJ-this may be related to gst568293's questions earlier, note in bug #1839761 UbiquitySyslog.txt " grub-installer: info: Identified partition label for /dev/sda6: msdos"16:33
ubot5bug 1839761 in grub-installer (Ubuntu) "grub" [Undecided,New] https://launchpad.net/bugs/183976116:33
TJ-What's changed in that time-frame for ubiquity to have it selecting a partition rather than whole device ?16:33
lotuspsychjegrub-installer: info: Calling 'apt-install grub-efi-amd64-signed' failed16:39
lotuspsychjethose all over the place16:39
jeremy311839761 That one is trying to EFI install with msdos partitioning16:50
TJ-jeremy31: which is perfectly valid16:55
OerHeksUEFI needs GPT, no?16:55
TJ-No16:57
TJ-UEFI spec requires support for both GPT and MSDOS labels16:57
TJ-finally found where in ubiquity source the install device is set:17:01
TJ-db_subst grub-installer/progress/step_install_loader BOOTDEV "$bootdev"17:01
TJ-d-i/source/grub-installer/grub-installer:1002:db_subst grub-installer/progress/step_install_loader BOOTDEV "$bootdev"17:01
TJ-so whatever is setting that debconf var17:02
jeremy31TJ-: is $bootdev in preseed file17:23
jeremy31https://gist.github.com/boxrick/3a4022d003daa63b7d27cca7f0f99894#file-gistfile1-txt-L4817:26
TJ-jeremy31: from what I can tell it can be but it is set from the (default) choice made in the GUI... it looks like grub-install does the correct thing now even when given a partition number. I can't be bothered to track down when that changed though!17:33
TJ-lotuspsychje: I've been going through several of those bugs and so far each one is 'user error' or 'network failure' or some form - in one case trying to install to an NTFS file-system!17:34
TJ-lotuspsychje: so maybe this a a by-product of the installer allowing/selecting a partition as the install target.17:34
TJ-this was a funny one  https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/183807017:37
ubot5Ubuntu bug 1838070 in grub2 (Ubuntu) "Unable to add dyndbg to command line" [Undecided,Invalid]17:37
OerHekslotuspsychje, "I had to turn up the brightness and it stopped"  ...?  https://www.reddit.com/r/Ubuntu/comments/cojwj8/i_was_running_ubuntu_18042_on_lenovo_thinkpad/19:08

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!