[00:56] <notlistening> Hi is the 64 but mythubuntu iso going to run on an atom 330 ion system?
 *bit
[01:45] <Essobi> notlistening: Umm... don't think that's 64 bit... or even a compat archi...
[01:53] <tmetro> That was my initial impression of Atom too, but the other day I looked it up and read:
[01:54] <tmetro> http://en.wikipedia.org/wiki/Intel_Atom
[01:54] <tmetro> "Atom implements the x86 (IA-32) instruction set; x86-64 is so far only activated for the Atom 230 and 330 desktop models. N and Z series Atom models cannot run x86-64 code."
[01:54] <Essobi> welp.. give it a twirl then
[01:55] <tmetro> So it's just a power-saving x86 compatible CPU, where more instructions are implemented in microcode, rather than hardware, and thus take more cycles.
[02:02] <Essobi> ...
[02:02] <Essobi> I guess it takes less power to cycle the microcode then to flop the gates on real hardware..
[02:09] <notlistening> i'll whirl it up as soon as i get the ATX power connector adaptor tomorrow
[14:59] <Essobi> Morning.
[17:13] <fdlinux> hi
[17:14] <rhpot1991> hi
[17:14] <wombo> hi
[17:14] <fdlinux> having a problem with setting the date to rtc alarm with MythWakeSet , will give the output
[17:14] <fdlinux> frederik@myth:~$ sudo sh /usr/bin/MythWakeSet.sh
[17:14] <fdlinux> date: invalid date `  +0200'
[17:14] <fdlinux> if i do it manually , it works , so that's no problem
[17:15] <fdlinux> or doesn't anyone have a goot howto because there are alot for it
[17:16] <fdlinux> i am also running 9.04
[17:16] <fdlinux> i know i got it working 7 months ago  , but don't remember how
[17:17] <fdlinux> anyone got a idea ?
[17:23] <superm1> fdlinux, try using bash instead of sh
[17:24] <superm1> sh assumes POSIX compatibility
[17:25] <fdlinux> then it doesn't find the file
[17:25] <superm1> eg sudo bash /usr/bin/MythWakeSet.sh fails because it cant find the file?
[17:25] <superm1> but sudo sh /usr/bin/MythWakeSet.sh works?
[17:25] <superm1> that's bizarre
[17:26] <fdlinux> if i do it as root is says can't open bash
[17:26] <superm1> is your bash messed up?
[17:26] <superm1> does 'which bash' work?
[17:26] <fdlinux> out /bin/bash
[17:27] <fdlinux> output
[17:27] <superm1> and 'sudo which bash' doesn't work?
[17:28] <fdlinux> same output
[17:29] <superm1> then it should be working just fine
[17:30] <fdlinux> stil the problem
[17:31] <fdlinux> anyone here using MythWakeSet ? or something else?
[17:32] <fdlinux> using the script for ubuntu : https://help.ubuntu.com/community/MythTV/Install/WhatNext/ACPIWake
[17:43] <bobbob1016> For some reason mythbuntu started going to sleep on me after 5 minutes of watching a video.  I've tried the xset dpms thing, and all my settings say never go to sleep, any ideas?
[17:43] <bobbob1016> Seems like it started after an update.
[17:45] <fdlinux> anyone?
[17:45] <fdlinux> otherwise i do a reinstall , maybe i did something terrible wrong
[17:56] <bobbob1016> fdlinux: Just so you know, people here aren't ignoring you, they aren't here usually.  So "otherwise I do a reinstall" doesn't help, patience does though.
[17:57] <fdlinux> i shall wait , my gf should be here in minutes so the mce will be there for movies:)
[18:45] <hanfm> hallo, ich habe ein frisches mythbuntu 9.04 aufgesetzt, das system fährt auch hoch und die xfce4 oberfläche funktioniert einwandfrei, allerdings sieht man in mythtv nur einen grauen hintergrund mit schwarzen balken. weiß jemand woran dass liegen könnte
[20:53] <Joker_-_> Hey. I'm getting artifacts when listening to TV. Could it be related to the fact I have resized the screen? (NVidia drivers + tv-out + crt TV = 1 inche missing all around the screen). Mythbuntu 64 bits, nvidia geforce 9800, proprietary drivers.
[20:53] <Joker_-_> hauppauge pvr-150 tv-tuner
[20:55] <Seeker`> what sort of artifacts?
[20:55] <Joker_-_> Hard to describe, it's not like the artifacts you get when overclocking a video card too hard, but the screen flickers.
[20:55] <Joker_-_> it's not all the time either
[20:56] <Joker_-_> I was suspecting a poor signal but now the tv-tuner is hooked directly to the cable tv, no splitter or anything... still get that flickering.
[20:56] <Joker_-_> and the image is "as sharp as cable can be" if I check it directly trough the TV.
[20:57] <Joker_-_> I have found that the signal seems to have much noise when getting out of the tv-tuner card tho
[20:58] <Joker_-_> oh, discard that, I forgot it's not a tv-out the tv-tuner has.
[20:58] <Joker_-_> I tought I found the problem when I first tryed that but it's not a tv-out, it's an FM-in... :)
[20:58] <Joker_-_> well, discard the noise thing, not the whole problem :)
[21:00] <Joker_-_> any idea?
[21:06] <Seeker`> is it horizontal lines when the screen pans?
[21:07] <Joker_-_> nope, more like parts of the image are getting anywhere... liek a corrupted jpeg image
[21:07] <Seeker`> hmm
[21:08] <Seeker`> was wondering if it was the image tearing
[21:09] <Joker_-_> it seems to be worse from time to time. Getting a real cause --> effect isnt simple but I'd say when the contrast is higher, it's worse. There is defenitly a pattern tho.
[21:09] <Seeker`> what do you mean "aren't getting anywhere"?
[21:09] <Joker_-_> sometimes when listening to a channel where 2 camera are kind of static, switching from one to an other. one can flicker all the time, and the other wont
[21:09] <Joker_-_> probably related to the background or something like that
[21:09] <Seeker`> hmm
[21:09] <Seeker`> no idea then
[21:10] <Joker_-_> Seeker`: as if the image was deconstructed in pieces and reconstructed with some pieces randomly getting anywhere on the screen
[21:11] <Joker_-_> just like a jpeg corruption. Parts of the image gets miss-aligned and all..
[21:11] <Seeker`> sure it isn't a bad signal?
[21:12] <Joker_-_> it could be the tv-tuner that encodes in mpeg2 and somehow bugs for some reasons...
[21:12] <Joker_-_> Seeker`: I can't be 100% sure as I can't "see" the signal the tuner gets versus the noise the computer gives to it, but if I hook the tv directly to that same cable, it's cristal clear
[21:13] <Seeker`> hmm
[21:13] <Seeker`> my tuner is worse at getting a signal than the TV
[21:13] <Seeker`> haven't tried my 150 in ages
[21:13] <Joker_-_> I tought it was a signal problem since it was working fine in a previous appartment where I had cable, then mooved and didnt had cable and it started to do that. Now I got the cable back and it stills does it so...
[21:14] <Joker_-_> yeah I tend to agree with that, I should try a signal booster maybe?
[21:14] <Seeker`> if you've got one it can't hurt
[21:14] <Joker_-_> I tryed to put a video between the cable and my mythtv box btu ti didnt helped at all..
[21:14] <Joker_-_> maybe the video doesnt have such a big boost.
[21:15] <Seeker`> maybe
[21:15] <Joker_-_> I had a real cable booster in my previous appartment where it worked tho...
[21:15] <Joker_-_> so it might just be it.
[21:15] <Seeker`> i'd say give it a go
[21:15] <Joker_-_> I'll see if I can find a new one. Hope it's not too expensive
[21:15] <Seeker`> you can always return it if it doesn't help :P
[21:15] <Joker_-_> good point
[21:20] <Joker_-_> 15$ they got some in stock
[21:20] <Joker_-_> imma try that
[21:20] <Joker_-_> I'll keep you posted
[21:21] <Seeker`> :)
[21:21] <Seeker`> good luck
[22:04] <Seeker`> this is *really* bugging me now
[22:04] <Seeker`> stuttering video / audio
[22:04] <Seeker`> for no appearent reason
[22:30] <Seeker`> anyone?
[22:40] <SHADOW_V1> Seeker`, whats the problem
[22:40] <Seeker`> sound randomly cuts out for half a second or so
[22:40] <Seeker`> usually as a Tv program is changing scene
[22:40] <SHADOW_V1> from where recordings
[22:40] <SHADOW_V1> live tv
[22:40] <SHADOW_V1> wha
[22:41] <Seeker`> both
[22:42] <SHADOW_V1> ok when did it start happeneing
[22:42] <Seeker`> SHADOW_V1: last few days
[22:43] <SHADOW_V1> what are you recording over
[22:44] <Seeker`> recording freeview using a hauppage nova-t 500
[22:44] <SHADOW_V1> could be wheather or the satellite needs to be moved
[22:45] <SHADOW_V1> not too shure on sattellite stuff
[22:45] <Seeker`> the signal is fine
[22:45] <Seeker`> its not sattelite
[22:45] <Seeker`> its DVB-T
[22:45] <SHADOW_V1> oh ok
[22:45] <SHADOW_V1> you dont get any video problems just sound problems
[22:45] <Seeker`> its more sound problems than video
[22:45] <SHADOW_V1> but you still get video problems
[22:46] <Seeker`> occasionally the screen goes black for 1/2 second, but rarely
[22:46] <SHADOW_V1> because i expereince problems close to that here with sound popping and hissing and you see artifacts on the screen
[22:46] <SHADOW_V1> but thats due to poor signal quality
[22:47] <Seeker`> no, its as if the sound just stops, my AV receiver shows that it isn't receiving any audio, then it displays "Linear PCM", like the audio stream is closing then opening again
[22:47] <SHADOW_V1> could it be a stream problem
[22:48] <Seeker`> dont think so, video continues as normal
[22:48] <Seeker`> hmm, i'm tail -f'ing the mythfrontend log
[22:48] <Seeker`> it just did it again
[22:49] <Seeker`> 2009-07-08 22:48:15.321 AutoExpire: CalcParams(): Max required Free Space: 3.0 GB w/freq: 15 min
[22:50] <Seeker`> I wouldn't have thought that it would have problems with doing stuff at once
[22:50] <Seeker`> its running on a Core 2 Q6700
[22:51] <Seeker`> but the sound disappearing does'nt always coincide with stuff appearing in the logs
[22:51] <Seeker`> ah! no! I've been tailing the wrong thing
[22:51] <Seeker`> I've been tailing the backend
[22:52] <Seeker`> 2009-07-08 22:50:20.270 WriteAudio: buffer underrun
[22:52] <Seeker`> get that in the front end
[22:54] <Seeker`> SHADOW_V1: still there?
[23:27] <Evil_Ether> I have a Hauppauge Nova-S Plus on an upgraded 9.04 and it stopped working in the middle of the day with out a reboot. Myth backend says 'could not get card info #0 subtype: unknown'.
[23:28] <Evil_Ether> dmesg http://mythbuntu.pastebin.com/m69347db3
[23:32] <Joker_-_> For the records, I enabled some opengl thing that was said to reduce flickering, disabled DVI (or something liek that - for captions) and it worked
[23:32] <Joker_-_> it's not flickering anymore
[23:32] <Joker_-_> thx