/srv/irclogs.ubuntu.com/2014/08/30/#ubuntu+1.txt

=== Kamilion|ZNC is now known as Kamilion
BluesKaj'Morning all08:58
elfyhi BluesKaj09:04
BluesKajhey elfy09:04
BluesKajelfy, kernel probs fixed yet?09:07
=== mswart_ is now known as mswart
elfynot this morning - and nouveau was like running up a hill backwards through molasses - so I'm currently in trusty :)09:07
elfysuch is the way of things sometimes :)09:08
BluesKajok, I'm sticking with nouveau since it runs quite well here09:09
BluesKajfor a while anyway09:10
elfycould be a xubuntu/nouveau issue09:11
elfyI'm just going to have a day in something old :)09:11
JEEBhi, 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:10
JEEBI 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 upgrading11:12
JEEBthe 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 :)11:13
=== JEEBsv_ is now known as JEEBsv
=== ochosi_ is now known as ochosi
=== ochosi__ is now known as ochosi
=== mibofra_ is now known as mibofra
=== jseutter_ is now known as jseutter
=== Kamilion|ZNC is now known as Kamilion
SunstreamIs there a way I can test drive 14.1 without changing my O/S and screwing up my system13:11
JEEBit'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 machine13:12
BluesKajSunstream, yes on live media just boot it and choose "Try Kubuntu"13:13
SunstreamWell I have to use lubuntu to have a smooth running O/S on this old celery chipped laptop13:15
BluesKajor whatever flavour you like, excuse the typo ,,, too used to typing that13:16
elfy:p13:16
JEEBbut yeah, anyone else here has an old first gen macbook?13:17
JEEBI'd like to know if I'm the only one having these issues with 3.16 with it's iGPU13:17
BluesKajwidh there was a kubuntu+1 chat, now that ubuntu is going it's own way more so than before mir etc13:18
BluesKajwish13:18
brainwashJEEB: try 3.17 rc2 then13:18
elfyBluesKaj: you'll not be alone13:18
elfyprobably an anythingbutubuntu+1 chat :p13:19
JEEBbrainwash, the problem is that utopic will be released with 16, no?13:19
BluesKajelfy, think it's time we applied to set up a separate kubuntu+1 room13:19
JEEBand I'd really like to make sure this is not something specific to me13:20
JEEBI would be surprised if it was, but I'd like to see someone else test this, too13:20
brainwashJEEB: I guess so, but you need to verify if this problem is still happening with with 3.1713:20
JEEBbasically 2 times out of 3 I won't get to the login screen13:20
JEEBeither 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 guess13:21
JEEBbrainwash, I would guess yes, but I guess I'll try later13:21
brainwashalso, please file a bug report on launchpad13:21
JEEBI think the issue when I was on trusty happened with vanilla 3.15 and 3.16 at least13:21
JEEBfrom kernel.ubuntu.org repos13:21
JEEBand now utopic's standard kernel seems to do the same13:22
=== evil is now known as _3vi1_
brainwashJEEB: well, did you already check /var/log/syslog?13:24
brainwashthe kernel panic might be logged there13:25
JEEBI'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 :D13:26
JEEBso I most probably don't have that log any more13:26
JEEBnow that I'm on utopic I will of course come up with it at some point13:26
brainwashmmh, why do you run utopic in the first place?13:26
JEEBI usually upgrade to +1 release around one to two months before the official release13:27
JEEB(or clean install)13:27
brainwashso you should be familiar with the bug reporting process :)13:27
JEEBI 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 :D13:28
elfyBluesKaj: maybe so - not going to be somewhere I would go though :)13:28
[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
JEEBbut yes, I do have a launchpad account13:29
brainwashJEEB: sure, I guess it's worth a try and ask if anyone here can confirm a bug13:30
BluesKajelfy, not a kde user?13:31
elfynope - xubuntu ;)13:31
brainwash[4-tea-2]: systemd is not used by default13:31
[4-tea-2]brainwash: that wasn't really my question. I'm using systemd on utopic. Yes, systemd-sysv.13:31
[4-tea-2]…and I got my nfs mounts w/o nfs-common, that's why I'm asking.13:32
brainwashnot sure if anyone here can help you with systemd13:32
_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 yesterday13:33
_3vi1_elfy:  Me neither, and I've been up and down launchpad.13:33
elfy[4-tea-2]: all I can find re systemd and nfs is a bit on the wiki13:34
[4-tea-2]elfy: yeah, it's not really… comprehensive. :)13:34
elfyindeed ;)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 either13:35
[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:36
[4-tea-2]I wasn't aware that systemd did THAT.13:37
elfythat must have been added in 2012 - diff's since then don't mention anything about that section :)13:37
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 either13:38
elfy_3vi1_: if you report it I'll me too it - can post it in thread as well if necessary13: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:39
elfy:)13:40
elfypitti would probably be the person to start with - he's the one who wanted it testing :)13:40
_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
elfyaaah13:41
[4-tea-2]elfy: thanks a lot, I'll keep an eye open for him.13:41
elfy_3vi1_: I get xorg errors if I try and use it - Fatal no x server type ones :)13:42
_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:43
elfyI'll see if I can get one reported from my other utopic - biab13:46
elfy_3vi1_: mmm - so that's odd - installed nvidia - boots to desktop but uses nouveau14:00
_3vi1_elfy:  Weird.  I'm going to test something too - biab14:02
=== Evil is now known as _3vi1_
_3vi1_ALRIGHT!  Got my black-screen-at-boot issue fixed (knock-on-wood)14:15
elfy_3vi1_: well I've given up playing with that for the day lol14: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:23
elfyoh14:24
_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:25
elfypossibly - 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 it14:27
elfythanks for the thoughts _3vi1_14:27
_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
elfyokey doke14:28
elfyaaah - I recognise the name now :p14:30
_3vi1_:p14:30
_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:31
=== zoktar_ is now known as zoktar
=== siel_ is now known as siel
popeyanyone else getting broken desktop on nvidia?14:54
popeyhttp://paste.ubuntu.com/8188295/14:55
popey[    12.756] (EE) Failed to load module "nvidia" (module does not exist, 0)14:55
=== aljosa_ is now known as aljosa
=== dkessel_ is now known as dkessel
BluesKajyup, 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 unity14:56
BluesKajpopey, ^14:57
popeygah14:58
popeyBluesKaj: do you know if there's a bug for it?14:59
BluesKajpopey, dunno, I haven't checked launchpad15:00
BluesKajbbl15:01
=== zoktar_ is now known as zoktar
=== Pici` is now known as Pici
=== brainwash_ is now known as brainwash
JEEBsvhmm, anyone else seen this with a Mesa DRI Intel(R) 945GM? http://up-cat.net/p/e65dba7722:38
penguin42I've seen hangs on Intel cards in the past, lots of different things can trigger it when some part of the stack breaks22:42
chrs-i need to troubleshoot my wifi adapter22:44
chrs-connection quality is very poor in 14.1022:44
chrs-other devices connected don't seem to have much of a problem22:44
JEEBsvI'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 sorts22:47
JEEBsv(it seems like an old 1st gen macbook is having trouble with 3.15+ or so)22:47
JEEBsvsome 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 screen22:49
chrs-sometimes when i boot on my pc laptop i see garbage on the screen temporarily22:50
ybonHi there :) Anyone able to give a hand on https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1363408 ?22:50
ubottuLaunchpad bug 1363408 in nvidia-graphics-drivers-331 (Ubuntu) "nvidia proprietary drivers are broken" [Undecided,Incomplete]22:50
chrs-as if the video memory has random data in it or something22:50
chrs-display buffer or whatever. but it does go away. not sure if it's wroth filing something for it22:51
penguin42chrs-: Temporary crud on the screen isn't unusual as graphics drivers/systems take over23:02
brainwashchrs-: 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:10
chrs-yeah it seems like one of those things people just put up with or ignore23: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 kow23:18
chrs-know*23:18

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