[08:58] <BluesKaj> 'Morning all
[09:04] <elfy> hi BluesKaj
[09:04] <BluesKaj> hey elfy
[09:07] <BluesKaj> elfy, kernel probs fixed yet?
[09:07] <elfy> not this morning - and nouveau was like running up a hill backwards through molasses - so I'm currently in trusty :)
[09:08] <elfy> such is the way of things sometimes :)
[09:09] <BluesKaj> ok, I'm sticking with nouveau since it runs quite well here
[09:10] <BluesKaj> for a while anyway
[09:11] <elfy> could be a xubuntu/nouveau issue
[09:11] <elfy> I'm just going to have a day in something old :)
[11:10] <JEEB> hi, it seems like there could be some intel gpu driver issues with the first gen macbook and the 3.16 kernel. Anyone else have a 1st gen macbook on hand so he/she could check if similar results are obtained?
[11:12] <JEEB> I had similar issues with (I think) 3.15 and 3.16 vanilla kernels on trusty, and now that utopic has 3.16 as its kernel I'm getting similar issues after upgrading
[11:13] <JEEB> the issues mostly lead to either no picture on screen, or the initialization going wonky, or a kernel panic happening. I haven't had the kernel panic yet so I will not be posting a screenshot of one yet :)
[13:11] <Sunstream> Is there a way I can test drive 14.1 without changing my O/S and screwing up my system
[13:12] <JEEB> it's not 1, it's 10 (separate numbers), but you can just get the daily image and run it as a live image. or you can use a virtual machine
[13:13] <BluesKaj> Sunstream, yes on live media just boot it and choose "Try Kubuntu"
[13:15] <Sunstream> Well I have to use lubuntu to have a smooth running O/S on this old celery chipped laptop
[13:16] <BluesKaj> or whatever flavour you like, excuse the typo ,,, too used to typing that
[13:16] <elfy> :p
[13:17] <JEEB> but yeah, anyone else here has an old first gen macbook?
[13:17] <JEEB> I'd like to know if I'm the only one having these issues with 3.16 with it's iGPU
[13:18] <BluesKaj> widh there was a kubuntu+1 chat, now that ubuntu is going it's own way more so than before mir etc
[13:18] <BluesKaj> wish
[13:18] <brainwash> JEEB: try 3.17 rc2 then
[13:18] <elfy> BluesKaj: you'll not be alone
[13:19] <elfy> probably an anythingbutubuntu+1 chat :p
[13:19] <JEEB> brainwash, the problem is that utopic will be released with 16, no?
[13:19] <BluesKaj> elfy, think it's time we applied to set up a separate kubuntu+1 room
[13:20] <JEEB> and I'd really like to make sure this is not something specific to me
[13:20] <JEEB> I would be surprised if it was, but I'd like to see someone else test this, too
[13:20] <brainwash> JEEB: I guess so, but you need to verify if this problem is still happening with with 3.17
[13:20] <JEEB> basically 2 times out of 3 I won't get to the login screen
[13:21] <JEEB> either because of just nothing showing up or a kernel panic. I haven't gotten the panic yet, but when I do I can photo it I guess
[13:21] <JEEB> brainwash, I would guess yes, but I guess I'll try later
[13:21] <brainwash> also, please file a bug report on launchpad
[13:21] <JEEB> I think the issue when I was on trusty happened with vanilla 3.15 and 3.16 at least
[13:21] <JEEB> from kernel.ubuntu.org repos
[13:22] <JEEB> and now utopic's standard kernel seems to do the same
[13:24] <brainwash> JEEB: well, did you already check /var/log/syslog?
[13:25] <brainwash> the kernel panic might be logged there
[13:26] <JEEB> I'll check the next time a kernel panic happens, I had gone back to the normal trusty kernel after I got tired of booting the laptop three to four+ times to get it started :D
[13:26] <JEEB> so I most probably don't have that log any more
[13:26] <JEEB> now that I'm on utopic I will of course come up with it at some point
[13:26] <brainwash> mmh, why do you run utopic in the first place?
[13:27] <JEEB> I usually upgrade to +1 release around one to two months before the official release
[13:27] <JEEB> (or clean install)
[13:27] <brainwash> so you should be familiar with the bug reporting process :)
[13:28] <JEEB> I think I have reported an issue at some point, but I was just trying to probe if anyone here had an old first-gen macbook so that I could make sure it's not some fluke for me only :D
[13:28] <elfy> BluesKaj: maybe so - not going to be somewhere I would go though :)
[13:29] <[4-tea-2]> I'm a little confused… What's the relationship between systemd and nfs on utopic? Has systemd swallowed all the stuff from nfs-common (e.g. rpc.statsd)?
[13:29] <JEEB> but yes, I do have a launchpad account
[13:30] <brainwash> JEEB: sure, I guess it's worth a try and ask if anyone here can confirm a bug
[13:31] <BluesKaj> elfy, not a kde user?
[13:31] <elfy> nope - xubuntu ;)
[13:31] <brainwash> [4-tea-2]: systemd is not used by default
[13:31] <[4-tea-2]> brainwash: that wasn't really my question. I'm using systemd on utopic. Yes, systemd-sysv.
[13:32] <[4-tea-2]> …and I got my nfs mounts w/o nfs-common, that's why I'm asking.
[13:32] <brainwash> not sure if anyone here can help you with systemd
[13:33] <_3vi1_> Anyone know if there's a specific bug filed for the black-screen-at login bug a lot of us have been seeing since around the same time the 3.16.0-11 kernel packages landed?  (http://ubuntuforums.org/showthread.php?t=2241869)  I'm puzzled as to the real cause, because there are no Xorg.0.log errors and booting to old kernel does not fix it.
[13:33] <[4-tea-2]> brainwash: That's okay, I don't need help, nothing is broken; just looking for understanding. I'll dive into the docs then.
[13:33] <elfy> _3vi1_: not seen a specific new bug reported yesterday
[13:33] <_3vi1_> elfy:  Me neither, and I've been up and down launchpad.
[13:34] <elfy> [4-tea-2]: all I can find re systemd and nfs is a bit on the wiki
[13:34] <[4-tea-2]> elfy: yeah, it's not really… comprehensive. :)
[13:35] <elfy> indeed ;)
[13:35] <[4-tea-2]> And I'm not sure it's really up to date, either.
[13:35] <elfy> [4-tea-2]: no idea - you can't tell from last edit date either
[13:36] <[4-tea-2]> elfy: " To get the timing correct we need to tell systemd explicitly that the mount depends on networking and on rpc.statd." - the current setup doesn't seem to need rpc.statd, and installing nfs-common actually fails. But, as I said, everything is working anyway, which is kinda confusing.
[13:37] <[4-tea-2]> I wasn't aware that systemd did THAT.
[13:37] <elfy> that must have been added in 2012 - diff's since then don't mention anything about that section :)
[13:38] <elfy> [4-tea-2]: not really had much to do with systemd - boot it sometimes is all - and I've not used nfs for some time either
[13:39] <elfy> _3vi1_: if you report it I'll me too it - can post it in thread as well if necessary
[13:39] <[4-tea-2]> elfy: I suspect in the mean time systemd has swallowed the non-kernel parts of nfs, too. I'm just trying to get used to it, because I expect to be running it on loads of machines at work in the foreseeable future and I want to be prepared. :)
[13:40] <elfy> :)
[13:40] <elfy> pitti would probably be the person to start with - he's the one who wanted it testing :)
[13:41] <_3vi1_> elfy:  I'm thinking about it - I'm just wishing that someone with more details and a less exotic configuration had reported it.  I'm running bumblebee, but a lot of users experiencing the error are not.
[13:41] <elfy> aaah
[13:41] <[4-tea-2]> elfy: thanks a lot, I'll keep an eye open for him.
[13:42] <elfy> _3vi1_: I get xorg errors if I try and use it - Fatal no x server type ones :)
[13:43] <_3vi1_> elfy:  I wish I had an Xorg error at this point - that would make for a good bug report.  :)  I just get the black screen, and Xorg has no complaints except for missing dri3 - which I think is normal with utopics current Xorg version.
[13:46] <elfy> I'll see if I can get one reported from my other utopic - biab
[14:00] <elfy> _3vi1_: mmm - so that's odd - installed nvidia - boots to desktop but uses nouveau
[14:02] <_3vi1_> elfy:  Weird.  I'm going to test something too - biab
[14:15] <_3vi1_> ALRIGHT!  Got my black-screen-at-boot issue fixed (knock-on-wood)
[14:23] <elfy> _3vi1_: well I've given up playing with that for the day lol
[14:23] <_3vi1_> elfy:  I got it fixed here!
[14:23] <_3vi1_> Something seems to have changed with the way the drivers are loaded...
[14:23] <_3vi1_> In my case, I just had to blacklist nvidia-343...
[14:24] <elfy> oh
[14:25] <_3vi1_> I don't know if it was previously unloading via bbswitch properly (and now it doesn't), but... that seems to have worked around it for me.
[14:25] <_3vi1_> Maybe you need to blacklist nouveau if you're trying to use nvidia, in your case.
[14:27] <elfy> possibly - though I'll just for the moment wait for a day or two see what comes out of the pipeline, one way or the other they'll need to fix it
[14:27] <elfy> thanks for the thoughts _3vi1_
[14:28] <_3vi1_> Coolio.  Thanks for puzzling on this with me too, elfy.
[14:28] <_3vi1_> I'll post my results in that thread and maybe it will help a dev with the real issue.
[14:28] <elfy> okey doke
[14:30] <elfy> aaah - I recognise the name now :p
[14:30] <_3vi1_> :p
[14:31] <_3vi1_> I'm going to run and look at my kern.log now...  My immediate suspicion is that bumblebeed is loading before the nvidia driver - causing the issue in my case.
[14:54] <popey> anyone else getting broken desktop on nvidia?
[14:55] <popey> http://paste.ubuntu.com/8188295/
[14:55] <popey> [    12.756] (EE) Failed to load module "nvidia" (module does not exist, 0)
[14:56] <BluesKaj> yup, no desktop at all with nvidia, reverted to nouveau until the bug is fixed, but nouveau seems to work ok here , but I'm using KDE not unity
[14:57] <BluesKaj> popey, ^
[14:58] <popey> gah
[14:59] <popey> BluesKaj: do you know if there's a bug for it?
[15:00] <BluesKaj> popey, dunno, I haven't checked launchpad
[15:01] <BluesKaj> bbl
[22:38] <JEEBsv> hmm, anyone else seen this with a Mesa DRI Intel(R) 945GM? http://up-cat.net/p/e65dba77
[22:42] <penguin42> I've seen hangs on Intel cards in the past, lots of different things can trigger it when some part of the stack breaks
[22:44] <chrs-> i need to troubleshoot my wifi adapter
[22:44] <chrs-> connection quality is very poor in 14.10
[22:44] <chrs-> other devices connected don't seem to have much of a problem
[22:47] <JEEBsv> I'll have to see if this kernel decides to panic at some point as the vanilla 3.16 kernel did on trusty, and at that point I might even make a bug report of sorts
[22:47] <JEEBsv> (it seems like an old 1st gen macbook is having trouble with 3.15+ or so)
[22:49] <JEEBsv> some of the time I get a black screen and never get to login, other times I get some mess on boot but actually get there, and then in other cases it just kernel panics and I never get to the login screen
[22:50] <chrs-> sometimes when i boot on my pc laptop i see garbage on the screen temporarily
[22:50] <ybon> Hi there :) Anyone able to give a hand on https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408 ?
[22:50] <chrs-> as if the video memory has random data in it or something
[22:51] <chrs-> display buffer or whatever. but it does go away. not sure if it's wroth filing something for it
[23:02] <penguin42> chrs-: Temporary crud on the screen isn't unusual as graphics drivers/systems take over
[23:10] <brainwash> chrs-: filing a bug report could help to get the problem fixed, just make sure that you provide all the needed information (details about hardware,..)
[23:18] <chrs-> yeah it seems like one of those things people just put up with or ignore
[23:18] <chrs-> it's not a huge deal, but i have no idea how hard it is to fix, could be simple for all in kow
[23:18] <chrs-> know*