[00:48] <daftykins> !info linux-generic
[00:48] <ubot5`> linux-generic (source: linux-meta): Complete Generic Linux kernel and headers. In component main, is optional. Version 4.4.0.45.48 (xenial), package size 1 kB, installed size 12 kB
[00:48] <daftykins> !info linux-generic yakkety
[00:48] <ubot5`> linux-generic (source: linux-meta): Complete Generic Linux kernel and headers. In component main, is optional. Version 4.8.0.26.35 (yakkety), package size 1 kB, installed size 12 kB
[01:38] <R13ose> Bashing-om: I am here
[01:38] <daftykins> hi
[01:39] <R13ose> hi, I was the one with the graphics problem
[01:39] <daftykins> ah har
[01:39] <Bashing-om> R13ose: K ..  Like I say the btter responses to your grahics's issue will be in the main channel . Here is "discussion" of on-going things .
[01:40] <R13ose> Seems everyone is stuck
[01:40] <Bashing-om> better*
[01:40] <daftykins> i was playing along from home, curious what make + model system it is and whether the live session behaved differently?
[01:40] <daftykins> "dmesg | nc termbin.com 9999" on a fresh boot would be handy
[01:40] <R13ose> well I don't want to get into the live session
[01:41] <daftykins> there a particular reason for that?
[01:41] <R13ose> I don't want to restart at the moment
[01:41] <R13ose> http://termbin.com/ryat
[01:41] <daftykins> ok an acer aspire
[01:42] <Bashing-om> daftykins: R13ose ouch ! Acer with vendor lockin to Windows ??
[01:42] <daftykins> i see v5-572 - but does it have any letters after, R13ose ?
[01:42] <R13ose> I deleted Windows
[01:42] <daftykins> might either be on the hinge of the screen or on a label underneath
[01:43] <daftykins> acer have a G, a P and a PG
[01:44] <R13ose> daftykins: I don't think there are any letters
[01:44] <daftykins> ok lets see
[01:45] <daftykins> so you're on BIOS 2.09 and their latest is 2.10 which fixes something completely irrelevant
[01:46] <daftykins> i think 16.10 is a bad choice for that machine personally
[01:46] <daftykins> and your options are dwindling
[01:46] <daftykins> did you boot to 'try' mode before installing? just curious whether it behaved at all before installation
[01:47] <R13ose> model # is zrk
[01:47] <Bashing-om> daftykins: change the DSDT table ? ' sudo strings /sys/firmware/acpi/tables/DSDT | grep -i windows ' to know the options ??
[01:47] <R13ose> daftykins: some issue always on KDE.  I don't think this happened when I was using gnome.
[01:48] <daftykins> well you have one of the very problematic families of laptop for Linux, as it goes
[01:48] <daftykins> Bashing-om: yeah could be worth a go :)
[01:48] <R13ose> should I try that what Bashing-om said?
[01:49] <daftykins> yes
[01:49] <Bashing-om> R13ose: is a shot .. amd maybe not too long of one ^^ .
[01:50] <R13ose> http://pastebin.com/R0jSrW1r
[01:52] <daftykins> Bashing-om: i don't recall the rest, 'Windows 2012' it is i guess :)
[01:52] <Bashing-om> R13ose: daftykins 2012 .. maybe NOW  a long shot . R13ose, To test you woild have to reboot into grub to alter the setting .
[01:53] <Bashing-om> daftykins: Yeah - "acpi_osi=Windows 2012" on the kernel command line .
[01:54] <R13ose> what does that mean?
[01:54] <daftykins> "boot pretending to be this OS and use its' ACPI data"
[01:55] <R13ose> meaning?
[01:55] <daftykins> hmm a full explanation would take longer than just trying it really :/
[01:55] <daftykins> essentially sometimes Linux doesn't work so well because laptop manufacturers spend more time and effort making Windows power management work properly
[01:56] <daftykins> so the OS lacks the information it could benefit from to run properly
[01:56] <R13ose> lets try this.
[01:56] <Bashing-om> R13ose: ACPI == Advanced Configuration and Power Interface. It provides a way for the PC firmware (UEFI/BIOS) to declare to an Operating System how to control its platform-specific hardware.  ACPI provides several in-firmware 'tables'. One such is the Differentiated Services Description Table (DSDT). This actually contains executable code in a special ACPI 'language' which the OS has to execute. Rather like Java and its Virtual Machine. 
[01:56] <R13ose> how do I do this when I restart?
[01:57] <daftykins> you hold left shift just before the disk is about to be read from in a normal boot - still i think to get GRUB to come up
[01:58] <daftykins> anywho i will let Bashing-om do this bit as i have a date with some food, back shortly :>
[01:58] <Bashing-om> hold down Shift to get the GRUB boot menu. highlight the default entry, press 'E' to edit it, navigate to the line starting "linux ..." ... and add to the end the string (including double-quotations) "acpi_osi=Windows 2013"   - then press Ctrl+X or F10hold down Shift to get the GRUB boot menu. highlight the default entry, press 'E' to edit it, navigate to the line starting "linux ..." ... and add to the end the string (including double-q
[01:59] <Bashing-om> 2013/2012** // we want 2012 .
[02:01] <R13ose> Bashing-om: okay 2012 but do I need the quotes?
[02:03] <Bashing-om> smoke break .. smokers draw one . // R13ose Yes the quotes are needed . That silly space that Windows uses .
[02:03] <R13ose> brb
[02:09] <R13ose> back
[02:10] <R13ose> how do I make sure everything is correct?
[02:10] <Bashing-om> R13ose: Yhat was qyuck .. any the verdict is ?
[02:11] <daftykins> re-run "dmesg | nc termbin.com 9999"
[02:11] <R13ose> Bashing-om: This doesn't happen all the time so I have to wait.
[02:11] <R13ose> http://termbin.com/98np
[02:12] <daftykins> not sure if there should've been spaces either side of = as there are there
[02:13] <daftykins> "acpi_osi=Windows 2012" vs. "acpi_osi = Windows 2012"
[02:13] <R13ose> well let me know what to do and I will restart again and fix if wrong.
[02:14] <daftykins> did you type it like my first or second?
[02:14] <R13ose> second
[02:14] <daftykins> Bashing-om: what do you think?
[02:15] <R13ose> Bashing-om: wrote "acpi_osi=Windows 2013" so maybe I did this wrong
[02:15] <daftykins> my instinct says no spaces, mmm
[02:15] <R13ose> which I want to make sure before I restart again
[02:15] <Bashing-om> daftykins: R13ose boot line looks good to me . and "  0.000000] Reserving Intel graphics memory at 0x00000000aba00000-0x00000000af9fffff ' is an encouraging sign .
[02:16] <R13ose> Bashing-om: meaning?
[02:18] <Bashing-om> R13ose: entered on the grub boot line as - "acpi_osi=Windows 2012" - those quotes are needed because of the space between Windows and 2012 .
[02:18] <daftykins> turns out he entered it with spaces either side = though, not sure if that's good
[02:22] <Bashing-om> daftykins: Ouch ,, did not see that of " = " /nope that ain't good . but what is still look'n good " 0.207700] vgaarb: bridge control possible 0000:00:02.0 " .
[02:22] <R13ose> Do I have to change this?
[02:23] <R13ose> I will do acpi_osi=Windows 2012 now, if both of you think that is good
[02:25] <daftykins> yep :)
[02:25] <R13ose> yep as in?
[02:25] <daftykins> change it
[02:26] <R13ose> brb
[02:27] <Bashing-om> R13ose: Vjange it , daftykins Is this " 2.403692] fbcon: inteldrmfb (fb0) is primary device " saying it is not going to load the Intel driver ??
[02:28] <daftykins> don't think so
[02:28] <Bashing-om> daftykins: OR is this saying Intel driver is loaded " 3.418684] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device " ?
[02:29] <daftykins> earlier i did a search through the first dmesg paste for "i915" and "drm" and couldn't find any obvious issues, we might have to see another Xorg.0.log
[02:30] <daftykins> it's definitely a model sold with nvidia configurations, whether it is one or not :)
[02:31] <R13ose> back.  http://termbin.com/mj4m
[02:31] <daftykins> yep that looks better
[02:32] <daftykins> be interesting what Xorg's log says now, i think it's "pastebinit ~/.local/xorg/log/Xorg.0.log" but i can't remember
[02:32] <Bashing-om> R13ose: daftykins We have lift off ! " 1.896599] [drm] Initialized i915 1.6.0 20160711 for 0000:00:02.0 on minor 0 " .
[02:33] <daftykins> :O
[02:33] <R13ose> the text didn't save in the grub
[02:35] <R13ose> daftykins: Unable to read from: /home/shawn/.local/xorg/log/Xorg.0.log
[02:36] <daftykins> yeah you'll need to browse into ~/.local and find it, i had the path wrong
[02:36] <daftykins> silly 16.10 changing things i'm used to!
[02:38] <R13ose> daftykins: http://paste.ubuntu.com/23395570/  there is also a Xorg.1.log tpp
[02:38] <R13ose> too*
[02:39] <Bashing-om> R13ose: I expect that 16.04 still maintains the xorg log ; ' pastebinit /var/log/Xorg.0.log ' should be productive on the cuurent boot.
[02:40] <daftykins> i spy the proper intel driver labels :)
[02:40] <daftykins> from line 160
[02:41] <R13ose> Bashing-om: http://paste.ubuntu.com/23395582/
[02:41] <daftykins> so it looks like that edit has solved it, so you'll need to put it in permanently now so it's used on every boot
[02:41] <daftykins> yeah we're gonna need to see modified times on both those files
[02:41] <Bashing-om> yeah .. but we are not booting with osi= on this log file .
[02:42] <daftykins> the paste ending 82 is outdated i think
[02:42] <daftykins> oh
[02:42] <daftykins> oh dear.
[02:42] <R13ose> As I said there is Xorg.1.log too
[02:42] <daftykins> oh so you didn't pastebin that one? can you?
[02:42] <R13ose> I didn't because you said 0
[02:43] <R13ose> daftykins: http://paste.ubuntu.com/23395585/
[02:43] <R13ose> Bashing-om: http://paste.ubuntu.com/23395586/
[02:44] <daftykins> yeah i'm still new to 16.10, they've changed all the things i could rely on
[02:45] <R13ose> well is 1 better then 0
[02:45] <daftykins> it's not about better, it's about appropriate or not
[02:45] <daftykins> and the timestamps on these files are still important, you'd need to check them to see whether they're from the current boot or not
[02:47] <R13ose> Today is Oct 28 so I don't think so
[02:47] <daftykins> well i can't see the timestamps on the log files on your disk from here
[02:48] <Bashing-om> R13ose: What is the date on ' ls -al /var/log/Xorg.0.log ' ?
[02:49] <R13ose> Bashing-om: Oct 28 22:29 /var/log/Xorg.0.log
[02:52] <Bashing-om> R13ose: And your local time is now about 10:29 PM ?/ Such that file is the current one ??
[02:53] <R13ose> Bashing-om: yes 24 mins ago
[02:54] <Bashing-om> R13ose: K. then that is the current fole ! .. show that one to us . ( booted with the  osi= boot parametr ) .
[02:55] <R13ose> Bashing-om: I am in that currently
[02:56] <R13ose> Bashing-om: from line 1, I believe this is the one you are asking for: http://paste.ubuntu.com/23395582/
[02:58] <Bashing-om> R13ose: yepper, reading .
[02:58] <R13ose> I thought both of you thought this was good
[03:02] <Bashing-om> R13ose: Looks good to me EXCEPT ,,, I do not see where the i915 driver is loaded .. daftykins HUH ?
[03:03] <daftykins> well to me, that one goes back to that modeset rubbish instead of seeing the intel driver
[03:03] <daftykins> so i'm quite puzzled
[03:03] <Bashing-om> R13ose: Be aware I have limited expreience with the Intel chip set .
[03:04] <R13ose> no worries
[03:04] <daftykins> i'm feeling really lost with 16.10's behaviour, too :/
[03:04] <daftykins> you would always look for the lines with drivername(#): at the start before to indicate which driver is in use
[03:05] <daftykins> for intel, it should be intel(#):
[03:05] <daftykins> now it's got modeset(#): in there i am very lost
[03:06] <Bashing-om> Yeah ,,, I have yet to see 16.10 . I stil have my hands full with 16.04 .
[03:06] <daftykins> LTS \o/
[03:10] <Bashing-om> R13ose: show us ' sudo lshw -C display ' . Bet what we have here is that modeset(#) is linked to " Matched modesetting as autoconfigured driver 0" -> LoadModule: "fbdev" . Maybe that here fbdev is Intel 915 (???) .
[03:11] <R13ose> Bashing-om: http://pastebin.com/quYd4AnT
[03:11] <daftykins> "fbdev  is  an  Xorg  driver  for  framebuffer  devices.  This is a non- accelerated driver"
[03:12] <daftykins> hrmm
[03:19] <Bashing-om> welp. Maybe trouble shooting graphics is going to get as troublesome as troubleshooting resolve.conf in systemd. That I915 driver got loaded - somewhere/sometime !
[03:19] <daftykins> :D
[03:20]  * daftykins nuked resolvconf in the past and hardcoded it
[03:20] <daftykins> but that's servers :D
[03:22] <Bashing-om> All I know to do at this point is try the DE and see how it performs .. and if stable make the iso= parameter permanent . R13ose That gets a bit trickier //
[03:24] <daftykins> *nod*
[03:25] <daftykins> not much else to try (other than dumping 16.10 because non-LTS is never good)
[03:26] <Bashing-om> daftykins: :) R13ose LTS on a production machine .
[03:29] <R13ose> ok
[03:32] <R13ose> This was happening in 16.04 too
[03:37] <Bashing-om> R13ose: K. Just at a lose presently to know what else to do . or where else to look . Is this 16.10 install from fresh, or as a upgrade from 16.04 ( in that you carried your problems forward ?) ?
[03:39] <R13ose> upgrade
[03:43] <Bashing-om> R13ose: :( on the upgrade . Seems the problem got carried forward . However, appears It will take greater experience and knowledge than I posses to see where the problem is .
[04:02] <R13ose> be back tomorrow my time
[04:02] <R13ose> thanks for help
[04:03] <Bashing-om> R13ose: K .. U am clearing my board . we take this back up tomorrow .
[05:00] <Bashing-om> !info aplay
[05:00] <ubot5`> Package aplay does not exist in xenial
[06:16] <ducasse> morning all
[06:25]  * Bashing-om waves at ducasse in getting ready to pass it on .
[06:26]  * ducasse wishes Bashing-om a good nights sleep
[06:27] <Bashing-om> Thankee ,, and a good day to you .
[06:31]  * xXEoflaOEXx has 17.04 development branch by upgrading from 16.10 using sudo do-release-upgrade -d
[06:54] <Ben64> xXEoflaOEXx: cool?
[10:23] <R13ose> Hi
[13:11] <BluesKaj> Hi folks
[13:13] <R13ose> Hi
[22:59] <OerHeks> don't drink & sudo
[23:02] <Bashing-om> That ^ is great advise, did you not, and now there are bad consequences ?