[02:04] good morning to all [02:06] nighty night [02:06] hey pragmaticenigma [02:06] yo [02:07] think we finally got B|akops straightend out [02:07] at least for now [02:07] oh yeah? what served him finally? [02:07] until next time? :) [02:08] What 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 whistles [02:09] tonight 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 X1400 [02:09] A chipset that is so old, it is best served by the default opensource drivers [02:09] * daftykins chuckles [02:09] They even claimed as much when they said everything was running smoothly on the USB live instances [02:09] polishing a turd is a true favourite of open source converts [02:09] i explained him, i ran xenial/bionic for years on my amd3200 + ati x800 with 2gb [02:10] tweaked of course but.. [02:10] lotuspsychje: but I imagine you are not installing the proprietary drivers for that... or if you are, you sought out the ones for that particualr chipset [02:13] I 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 Unity [02:14] pragmaticenigma: my x800 finally died, so i had to buy other goodies :p [02:14] The 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.04 [02:15] at least interface wise... under the hood they've had lots of changes, but they strive to keep a familiar interface through and through [02:15] yeah he didnt want lightweight, cause ubuntu-desktop is 'purple' bling bling [02:15] right... not that you can't achieve the same feel on Lubuntu [11:17] Howdy folks [11:17] Hi BluesKaj [11:17] hi EoflaOE [11:54] 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 prongs [12:22] TJ-: Nice. Are there any problems left? [12:23] 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:24] It's a definite relief though to not have to use the touchpad to scroll! [12:26] OK. 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:37] EoflaOE, edit /etc/default/grub GRUB_GFXMODE=whatever [12:38] Mathisen: I already did that in the past and updated GRUB, but it still is 1024x768 [12:39] try adding GRUB_GFXPAYLOAD="keep" [12:40] I already have it added as well. [12:40] then im out of ideas [12:40] but that should work [12:41] Yes, should have worked, but didn't. [12:44] hey EoflaOE [12:44] EoflaOE, may be related https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1753837 [12:44] Ubuntu 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] and hi Mathisen TJ- [12:50] Mathisen: I can't see --append on the 00_header. Where can it be found? [12:51] EoflaOE: because the fix mentioned in those bugs removed it [12:53] OK. [12:57] I put the quotes around the resolution, still nothing. Did I found a bug? My GPU is AND Radeon 9200 Series. [12:58] AMD* [13:11] EoflaOE: did you test physical vs VM ? [13:12] Physical on my old PC. [13:13] EoflaOE: no grub res problem there? [13:14] I told it to set it to 1440x900 and updated grub, however it reverts back to 1024x768. [13:18] radeon 9200 .. too old [13:18] Yes. Too old. [13:18] i remember it is an onboard GPU [13:19] Radeon 9200 is the dedicated GPU that you can insert and remove. === lotus|i7 is now known as lotus|NUC [13:23] 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#videoinfo [13:25] TJ-: 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:26] EoflaOE: use "set pager=1" then rerun the command [13:27] it is not a bug, just a too old gpu, RV280 https://help.ubuntu.com/community/RadeonDriver#Supported.2C_but_hardware_is_too_old_for_Unity [13:29] TJ-: 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 I [13:29] nfo. [13:34] EoflaOE: which is why GRUB cannot set the mode correctly then [13:35] OK Thanks anyways. [13:39] EoflaOE: is that system UEFI or BIOS boot ? [13:40] BIOS. My old PC can't do UEFI because it's from 2004. [13:40] EoflaOE: If UEFI there ought to be a GOP driver which would correctly report modes [13:40] Ahhh... ouch, that is old! [13:40] update it! [13:41] 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 them [13:41] ohhh ok [13:42] OK. Thanks for the clarification. [13:45] I think Ubuntu doesn't like my laptop [13:45] not only ubuntu, whole linux does not like your gpu :-( [13:46] :( [13:47] not sure there are AGPx2/x4 cards supported [13:47] thats pretty old [13:47] ZaZaGX: What is your GPU? [13:48] Intel UHD graphics 620 [13:49] oh, i swiched cards, intel 620 should work fine [13:49] Too new. Mine on my new PC is UHD 630. [13:51] hmmm [13:53] Does the new Ubuntu 18.04.3 kernel saves more battery life like in the 19.04? [13:53] ZaZaGX, there are no stats about that, it depends on the services installed i guess [13:54] well i remember reading since 18.10, its supposedly support better battery life [14:01] well, i kind of miss Ubuntu. it gave me like 1-2 more hours of battery life [14:58] lotuspsychje: You asked me if I'd reported my bug, here it is https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1839750 [14:58] Ubuntu bug 1839750 in linux-signed-hwe (Ubuntu) "40% performance loss in Mesa with Linux 5.0" [Undecided,New] [15:24] tnx Kon- [15:25] Kon-: can you also attach your dmesg booting 5.0.0.23 please [15:27] Actually have no idea what that is [15:27] !dmesg | Kon- [15:27] Kon-: 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:31] Interesting, thanks [15:36] Kon-: you can save it in a .txt if you like, then add to the bug as attachment (booted from 5.0.0.23) [15:38] Kon-: it might also be interesting to describe, how you measured the 40% loss exactly? do you benchmark? [15:39] Sure thing, let me go do that real quick [15:39] Kon-: tnx for taking your time to do this [15:39] Well, I certainly want this fixed lol [15:50] dmesg has been attached to bug #1839750 [15:50] bug 1839750 in linux-signed-hwe (Ubuntu) "40% performance loss in Mesa with Linux 5.0" [Undecided,New] https://launchpad.net/bugs/1839750 [15:53] going so new probably needs a PPA'd newer shiny mesa [15:55] not sure whats going on, he's fine on kernel 4.18 [16:01] Kon-: tnx for updating your bug + dmesg, pretty useful! [16:02] No problem [16:05] Kon-: can you show us: sudo lshw -C video plz? [16:10] Sure [16:12] added that to the description [16:13] tnx [16:20] TJ-: i know youre all over the place, but its raining install bugs in #ubuntu-bugs-announce [16:21] failed to install grub-efi-amd64 to /target? [16:23] grub-installer & ubiquity filed against [16:23] bug #1839761 [16:23] bug 1839761 in grub-installer (Ubuntu) "grub" [Undecided,New] https://launchpad.net/bugs/1839761 [16:23] bug #1839762 [16:23] bug 1839762 in grub-installer (Ubuntu) "grub error" [Undecided,New] https://launchpad.net/bugs/1839762 [16:23] bug #1839770 [16:23] bug 1839770 in ubiquity (Ubuntu) "NVMe. Crash during installation" [Undecided,New] https://launchpad.net/bugs/1839770 [16:23] bug #1839771 [16:23] bug 1839771 in ubiquity (Ubuntu) "Install of 19.04 failed on Lenovo Thinkpad W520" [Undecided,New] https://launchpad.net/bugs/1839771 [16:24] It seems grub has problems installing to EFI with an internet connection after any update to grub packages [16:27] is that for 19.10 or others ? [16:27] TJ-: pretty much everything since 18.04 [16:33] There was a big outbreak on July 10, 2018 [16:33] 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] bug 1839761 in grub-installer (Ubuntu) "grub" [Undecided,New] https://launchpad.net/bugs/1839761 [16:33] What's changed in that time-frame for ubiquity to have it selecting a partition rather than whole device ? [16:39] grub-installer: info: Calling 'apt-install grub-efi-amd64-signed' failed [16:39] those all over the place [16:50] 1839761 That one is trying to EFI install with msdos partitioning [16:55] jeremy31: which is perfectly valid [16:55] UEFI needs GPT, no? [16:57] No [16:57] UEFI spec requires support for both GPT and MSDOS labels [17:01] finally found where in ubiquity source the install device is set: [17:01] db_subst grub-installer/progress/step_install_loader BOOTDEV "$bootdev" [17:01] d-i/source/grub-installer/grub-installer:1002:db_subst grub-installer/progress/step_install_loader BOOTDEV "$bootdev" [17:02] so whatever is setting that debconf var [17:23] TJ-: is $bootdev in preseed file [17:26] https://gist.github.com/boxrick/3a4022d003daa63b7d27cca7f0f99894#file-gistfile1-txt-L48 [17:33] 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:34] 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] lotuspsychje: so maybe this a a by-product of the installer allowing/selecting a partition as the install target. [17:37] this was a funny one https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1838070 [17:37] Ubuntu bug 1838070 in grub2 (Ubuntu) "Unable to add dyndbg to command line" [Undecided,Invalid] [19:08] lotuspsychje, "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/