=== kermiac_ is now known as kermiac
=== kermiac is now known as kermiac_
=== cypher_ is now known as czajkowski
[11:08] <davmor2> morning all
[11:08] <davmor2> iso's installed over the weekend so that's good news :)
[11:19] <ara> morning davmor2
=== kermiac_ is now known as kermiac
=== kermiac is now known as kermiac_
[12:15] <davmor2> ara: why does the tracker now suddenly have a the drupal favicon rather than the ubuntu testing one it used to have?
[12:16] <ara> davmor2, I have no idea, it's been like that since the latest pull from trunk code, but I haven't had the time to have a look to it
[12:34] <ara> davmor2, I sent you an email
[12:36] <davmor2> ara:  got it :)
[12:52] <davmor2> ara: I'm getting kernel issue on todays iso
[12:52] <ara> davmor2, but do you get to install?
[12:54] <davmor2> it's the old ecc bug back meh
[12:54] <davmor2> ara: yeap it installed
[12:54] <ara> davmor2, which bug?
[12:56] <davmor2> ara: https://bugs.launchpad.net/bugs/422536
[12:56] <ubot4> Launchpad bug 422536 in linux (Ubuntu Karmic) (and 5 other projects) "EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded. (affects: 888) (dups: 112)" [Undecided,Fix released]
[13:05] <ara> morning cr3
[13:07] <davmor2> morning cr3
[13:08] <davmor2> cr3: are you getting kernel issues on 64bit at all?
[13:08] <ara> davmor2, do you get a kernel oop?
[13:09] <davmor2> ara: apport is triggered the system itself is up and running you just get regular messages off of apport
[13:11] <cr3> davmor2: I haven't noticed any issues as I'm attending PyCon in Atlanta. I'm flying out in a few hours, so catch you tomorrow
[13:11] <davmor2> :) no probs
[13:33]  * ara -> lunch
=== fader|away is now known as fader_
[14:04] <fader_> morning all
[14:05] <fader_> You know it's going to be One Of Those Days when the first thing you have to do is find a bootable CD and do some grub repair work on your system :/
[14:06] <fader_> ara: Good afternoon!
[14:06] <davmor2> fader_: HAHA
[14:06] <davmor2> fader_: morning
[14:06] <ara> fader_, afternoon
[14:07] <davmor2> fader_: that's why I have a production machine and separate testing machines ;)
[14:07] <fader_> ara: I tried to do the proprietary X driver tests but was never able to get a lucid install working on my nVidia system :(  I'll try again for this week.
[14:07] <fader_> davmor2: Yeah, I do too, but I thought I'd be okay if I installed lucid on an external drive to do the nVidia tests
[14:08] <ara> fader_, oka
[14:08] <fader_> I totally forgot that grub would get installed unless I specifically told it not to.  Which wasn't even a problem until I got to the Lex office today without the external drive with grub on it...
[14:08] <davmor2> Opps
[14:08] <fader_> ara: The good news is that it finally installed yesterday.  The bad news is that it just wouldn't boot afterward :)
[14:08] <davmor2> ooooppppsss even
[14:10] <fader_> Indeed
[14:10] <davmor2> fader_: if it helps it worked here but I get a kernel issue on 64 bit :)
[14:10] <fader_> Huh, just realized I should have tried 'rescue mode' on the live CD... I wonder if that has a 'fix my MBR' button.
[14:11] <davmor2> fader_: was it an alternate cd?
[14:11] <fader_> davmor2: Heh, sounds like you got farther than I did.  Plymouth came up and just stayed there.  I left it for a couple of hours but no dice.  Ctrl+alt+Fx worked so I know the system wasn't hung.
[14:11] <fader_> davmor2: No, daily-live
[14:11] <fader_> From Sunday
[14:12] <fader_> Prior to that I couldn't even manage to get an install to work from either daily-live or alternate
[14:12] <davmor2> yeah sunday's is the first that worked for me too
[14:13] <davmor2> fader_: the problem is that there is no rescue mode on the live cd :P
[14:13] <fader_> I don't feel quite so bad then... I was starting to think I was bad luck
[14:13] <fader_> :)
[14:13] <fader_> davmor2: Ah, meh.  I didn't even think of it until I had already booted in live mode and popped open gnome-terminal
[14:24] <fader_> davmor2: Out of curiosity, were you using i386 or amd64 lucid yesterday when you had your kernel issue?
[14:25] <davmor2> fader_: it's 64bit https://bugs.launchpad.net/bugs/422536
[14:25] <ubot4> Launchpad bug 422536 in linux (Ubuntu Karmic) (and 5 other projects) "EDAC amd64: WARNING: ECC is NOT currently enabled by the BIOS. Module will NOT be loaded. (affects: 888) (dups: 112)" [Undecided,Fix released]
[14:26] <fader_> Huh.  Just wondered if it were related to why I couldn't get past Plymouth, but it doesn't look like it
[14:28] <davmor2> fader_: do you have a white flashy cursor on a black background?
[14:31] <fader_> davmor2: Nope, it goes to the Ubuntu logo and sits there
[14:32] <davmor2> fader_: do you see the mouse cursor?
[14:32] <fader_> davmor2: Nope, I don't believe so
[14:32] <fader_> I can't say right now as I don't have the drive on me
[14:33] <davmor2> fader_: if it does try hitting enter
[14:33] <davmor2> it might reset itself and you get the gdm screen
[14:34] <fader_> davmor2: IIRC I tried punching all sorts of buttons, but I'll give it another shot
[14:34] <fader_> The only thing that worked was ctrl+alt+F1 which got me a VT with a couple of bootup messages but no login prompt
[14:34] <davmor2> fader_: that's your problem you only need to tap the key, you probably broke the keyboard punching it ;)
[14:34] <fader_> So I doubt that GDM was running yet
[14:34] <fader_> Heh
=== fader_ is now known as fader|away
=== fader|away is now known as fader_
=== BalleClorin_ is now known as BalleClorin
=== schwuk_ is now known as schwuk
=== fader_ is now known as fader|lunch
=== fader|lunch is now known as fader_
[19:27] <charlie-tca> plymouth and NVidia 6200 are broken again. Now it simply shuts off my monitor until the desktop is starting.
[19:28] <fader_> charlie-tca: You had better luck than I did :)
[19:28] <charlie-tca> Got to wait at least 1 full minute, maybe more for it to turn back on
[19:29] <fader_> That's a good way to have flicker-free boot... if the monitor is off it can't flicker
[19:30] <fader_> :)
[19:30] <davmor2> charlie-tca: are you sure and it's not just giving you a cursor line?
[19:30] <charlie-tca> Oh, I'm sure the monitor power lite changed to yellow, and the screen is completely blank
[19:31] <davmor2> charlie-tca: Ohhhhhh nice
[19:31] <charlie-tca> heh
[19:31] <davmor2> it's a power saving feature
[19:31] <charlie-tca> Yeah, that's what I was thinking... Except I really want to know it is still doing something.
[19:32] <charlie-tca> It doesn't shut down or restart, either, now.
[19:33]  * charlie-tca thinks that's why it is called testing... instead of using!
[19:39] <davmor2> charlie-tca: what happens if you set a resolution size in the boot line?
[19:39] <davmor2> I'm wondering if it is using the max the card is capable of rather than the max of the monitor
[19:40] <charlie-tca> I haven't tried that. I am still waiting to see the desktop again
[19:40] <charlie-tca> good point. Next reboot, I'll try it and see
[19:42] <davmor2> charlie-tca: just a thought  I know mine used to max out on my old monitor till gdm kicked in
[19:45] <charlie-tca> nope
[19:45] <charlie-tca> it doesn't care
[19:46] <davmor2> :(
[19:46] <charlie-tca> well, I did get to the desktop twice now in just 1 hour!
[19:47] <charlie-tca> Maybe this just isn't my day for this
=== fader_ is now known as fader|away