[00:11] laga, when you check in, can you let me know what to do about /proc not unmounting after chrooting or doing some mcc work on a diskless image. Worked the first time, but now I go back, and I get a "can't umount, device busy on the /proc mount of the image." I now can't commit changes or finish the updates due to this. Haven't found anything at the forums. [00:16] I must be doing something dumb if it's not a common error. [01:41] Anyone around who can help with myth-web I am getting "Fatal error: Allowed memory size of 33554432" even though I have updated php.ini to be higher then 32M yet it keeps reporting the same size anyone know know were that setting is to increase? [01:44] RobertLaptop, try in #mythtv-user The developers hang in there they maybe able to help you [01:45] ok [01:45] developers of mythweb that is [01:45] Must be something wrong with that since I am the only one in that room. [01:46] #mythtv-users [01:46] sorry [01:46] can any one help with trouble shooting/ setup a mythtv, [01:46] I have a p 4 2.2 ghz soyo MB, Pchdtv Hd-3000 and a Hauppauge hvr 1600 or wintv-HVR-1600, Loaded MythtvUbuntu 8.10, [01:46] no Guide no tv, [01:46] was able to get it to record with no sound. [01:46] Current status No Tv blank data on the guide, [01:51] Hello [01:52] I just installed Mythbuntu 8.10 and am having video problems with my ATI Radeon 7000 [01:52] it doesn't seem to find a video driver [01:52] can anyone help? [02:00] found it. mythweb.conf.apache defines a memory limit separte from the standard php file [02:00] so I just need to adjust /etc/apache2/sites-available/mythweb.conf [02:48] anyone know how to unmount /proc within chroot without rebooting? [02:58] fixed it .. using umount -l from within chroot solves it.. [03:15] I'm encountering an "NVP: prebuffering pause" Followed by "NVP: Waiting for prebuffer.." errors during playback... LiveTV is no problem can anyone help point me towards a solution? [03:49] Hi, I've got Lirc running sucessfully, love the mythbuntu control centre, but its needing a modprobe after I reboot. Any clues? [04:03] cat /etc/modules for a hint [04:14] anyone know on when mythtv-fixes will hit the repos [04:15] the slowness of program guide and how unresponsive it is sometimes makes me really hate this amd x2 2350 cpu i am using [04:31] Shadow____X: US weekly builds should be working now [04:32] oh yeah [04:32] nice [04:32] how can i update it then [04:33] Shadow____X: http://www.mythbuntu.org/auto-builds [04:33] thanks [04:36] updating now [04:36] hopefully it is faster [04:37] that would be nice [04:43] should i reboot or just restart backend === Shadow____X is now known as Shadow_X === Shadow_X is now known as Shadow__X [05:51] can someone help me hook my frontend to my backend? [05:53] i guess i really need to know how to find out what my username and password for the database are [05:53] is the default username mythtv? [05:54] sorry i accidentally left the room [05:57] MythbuntuGuest20, go under /etc/mythtv [05:57] there will be a fill that says mysql your user name and pass ford the db are there [05:59] awesome [06:02] yup also your going to need to enable remote connects on the mysql server if the frontend isnt the same machine the backend is on [06:02] by setting the pin to 0000 and changing the IP to a real ip? [06:04] no goto mythbuntu control center and under services enable remote connections to mysql [06:05] i just checked and i aleady had it enabled [06:06] i got my frontend to the watchtv ... etc screen and it says the backend doesnt seem to be running [06:06] make sure its running [06:06] does the backend have a frontend on it [06:07] i just ran mythbackend and it says couldnt bind port... so im assuming its running [06:07] alright [06:07] open mythbackend setup [06:07] then close it [06:08] top said it is running but i will try that [06:08] if top says its running [06:08] thats fine [06:09] connect to the mysql database remotely [06:09] do i need to be connecting with 6543 [06:09] or 3306 [06:09] leave the ports default [06:09] but you should put in real ip information in the mythbackend setup [06:09] like the ip address of the machine [06:11] i did [06:12] it is acting like it is fine and the front end loads without saying "cant connect to db?" [06:12] but when i go to watch tv it tells me it cant find the backend [06:12] can you wach recordings [06:12] when i go to that it says the same thing [06:13] you can look at the log [06:13] or run it in terminal [06:13] i have had that problem before but forgot how i fixed it [06:15] where are the logs at? [06:16] /var/logs [06:17] i think it thinks its not the master backend server [06:17] it says "adding tv as slave backend server" tv is my hostname [06:17] hmm [06:18] on the backend make sure the configuration is correct [06:18] in the first step [06:18] that defines the backends [06:18] it says connecting to 127.0.0.1 [06:18] which i changed [06:18] lemme double check [06:19] 127.0.0.1 is localhost [06:19] yeah [06:19] what should my master backend ip be? [06:20] the ip of the backend [06:20] well i mean should it be a real ip too? [06:20] or localhost [06:20] only deal with real ips [06:20] thats probably my problem [06:20] brb [06:20] ok [06:28] ok now it seems like it wants to play. when i hit watch tv it goes to a black screen [06:28] after that it put a show in my recordings menu but said it was empty [06:30] !blank [06:30] Sorry I don't know about blank [06:30] i didnt install the ati drivers on the backend machine [06:30] !blank% [06:30] If you try to watch tv and are greeted with a blank screen and a return to the menu then please check the permissions on your recording directory. It should be owned by mythtv:mythtv, have permissions of 775, and not be inside your home directory [06:30] ohh [06:30] can it have 777 permissions? [06:31] surely [06:31] Sure that will be fine [06:31] i forgot, how do i add ownership? chown? i always just do chmod 777 cause i am the only user on my machines [06:31] Bad prcatice :) [06:32] chown user:group /path/ [06:32] sweet thanks [06:32] np [06:36] was i looking at the right thing that was sayings the default directory was /var/lib/mythtv/recordings ? [06:36] i was looking under storage groups > default [06:37] Sounds right, that's probably not you're problem then. [06:37] well under live tv there was no group or directory set [06:38] just under default [06:39] does my backend need video drivers installed? [06:39] or do i need to enable any of these codecs? [06:40] ffmpeg seems kind of crucial [06:41] hauppauge pvr-150 [06:42] Naw, a 150 encodes mpeg by itself and mythtv has it's own copy off ffmpeg built in. [06:42] And you will only need video drivers if you want to run a frontend. [06:43] so all seems like it should work [06:43] under storage directories > live tv, do i need to have anything in there? there are no directories in that. [06:44] If there's nothing there it will just use the default. [06:45] damn [06:45] MythbuntuGuest20: Please watch your language. [06:54] can anybody help me with mythvodka? [09:05] hey, whoever told showed me the command line to ddrescue thank you it works like a charm, I don't know what I was doing before, but now I can rip my dvd's off to my backend [10:09] So, does anyone know how frequently and by what criterias the mythbuntu bugreports are being handled? [10:09] I have bug #303549 still untouched even though it was created 2008-11-29 [10:09] Bug 303549 in mythbuntu "Technisat Cablestar 2 PCI support dropped in Mythbuntu 8.10" [Undecided, New] http://www.launchpad.net/bugs/303549 === N1X0N is now known as Nixon === N1X0N is now known as Nixon === N1X0N is now known as Nixon [15:51] Anyone have a guess what "Screens found, but none have usable configuration" might be with the NV driver? [15:57] Good morning all... [15:58] morning [15:59] Enox, look at /var/log/Xorg.0.log* [15:59] superm1- Okay, lemme boot it up and check that file. [15:59] Has anyone played with booting two separate platforms from tftp and mythbuntu? I would like to optimize the kernel for my amd64 frontends and my VIA cpu front ends. [16:00] I can't seem to find any unique pxe substrings to tell what cpu each platform is... any ideas? [16:02] Enox, it's two files, that's why i left the * [16:02] it might be the .old version or the current version [16:02] Anything in particular I'm looking for? [16:03] Failed to initialize the NVIDIA graphics device PCI:1:0:0 [16:03] (EE) Screen9s) found, but none have usable configuration. [16:05] VGA compatible controller: nVidia Corpriation GeForce 8400 GS (rev a1) [16:05] Enox, nothing more detailed on there? [16:06] Lemme stuff it on a webpage :) 1 sec [16:06] i'll be back in a bit, so i'll take a look then. just leave the link herre [16:08] http://www.l93.com/tmp/Xorg.0.log.old.txt [16:08] ^^ Try that :0 [16:10] does anyone know how to grab the vendor-class-identifier during the PXE boot process? [16:11] superm1- Any insights? [16:21] Enox, try to modprobe nvidia and see if you can [16:22] Done. [16:22] no problemds [16:22] lsmod -> nvidia 6909268 0 [16:22] and dmesg shows no errors? [16:22] hm [16:22] Lemme check [16:23] whats xorg.conf look like? [16:23] I rmmmod'd it [16:23] Then modprobed it again [16:23] Got NVRM: Loading NVIDIA UNIX x86 Kernel Module 177.82 [16:24] yeah that's fine [16:24] Looks like: http://www.L93.com/tmp/xorg.conf.txt [16:24] I'm rather glad networking works ;) [16:25] yeah pretty straightforward [16:25] so walk through this then: http://us.download.nvidia.com/XFree86/Linux-x86/177.82/README/chapter-08.html [16:26] that's what they are referring to [16:29] superm1- None of the problems listed on that page seem to be similar to mine. [16:29] tge first one? === N1X0N is now known as Nixon [16:32] superm1- "...does not appear to be receiving interrupts generated by the NVIDIA graphics device" ? [16:32] Grepping for interrupt produces no results [16:34] superm1- I've read each of the problems, none come close to matching my no screens error. [16:37] I haven't had problems with X in years. [16:38] Is it better to just install myth on a normal distribution or something? [16:39] * Antharian fights with dhcpd and vendor-class-identification [16:39] * Antharian loses [16:39] Am I required to select screen resolutions anywhere during setup? It almost seems like it doesn't know which resolution to pick. [16:40] Enox: what is your output device (monitor/tv) hdmi/dsub/dvi [16:40] It's a normal DVI computer montir. Syncmaster 225BW [16:41] any chance the EDID is not being detected correctly? [16:41] The 8400GS card(silent) has DVI & VGA outputs. [16:41] What's EDID? :) [16:41] Extended display identificatin data [16:41] basically is is what eliminates all the old ModeLine bits. [16:41] It's a relatively new monitor [16:41] I've used it with an older version of Ubuntu on another computer with no problems. [16:42] A much older version of Ubuntu :) [16:42] Mine is too... but I had issues with it and had to drop back to a modeline command to get it to work [16:42] Any way to test EDID ? [16:42] when I upgraded to newer nVidia drivers, this problem came around [16:42] care to try my xorg.conf? [16:42] is your monitor capable of 1920x1080? [16:42] Sure [16:42] Hmm [16:42] Lemme check [16:43] 1680x1050 [16:43] That's maximum & native. [16:43] hmmm... my xorg.conf may not work... you need to find the video timings for your specific monitor [16:43] I figured for testing I'd set up Myth to work with a normal computer monitor and over the air signal [16:44] how familiar are you with the xorg.conf layout? [16:44] I haven't had problems with X in like.. 8 years..So I haven't really done anything with it in that time. [16:44] It's all worked pretty magically. [16:44] Essentially there are two lines to add to the xorg.conf [16:44] 1 - in the "Monitor" section [16:45] 2 - in the "Screen" sections [16:45] in the monitor section: ModeLine "1920x1080" 148.35 1920 2008 2052 2200 1080 1084 1089 1125 +HSync +VSync [16:46] in the "Screen" section: SubSection "Display" [16:46] Depth 24 [16:46] Modes "1920x1080" [16:46] EndSubSection [16:46] If I remember correctly the sync values have to be specific to my monitor, right? [16:46] yes. [16:46] Lemme do some web searches and see [16:46] so doing a google search on modeline and your monitor name may yield some good results [16:46] Does myth have to run at any other resultion besides 1680x1024 ? [16:46] nope [16:46] it will scale itself correctly [16:47] Ahh cool. [16:47] what is the exact make/model? I don't mind doing a bit of googling while I hope for someone to come up with PXE boot solutions for me ;) [16:48] Syncmaster 225BW. I found a page that suggests it may have higher than 1680..But newegg says 1680 so I'm trying to see which is correct. [16:49] modeline "1680x1050@60" 147.14 1680 1784 1968 2256 1050 1051 1054 1087 -hsync +vsync [16:49] is that the one you found as well? [16:49] http://ubuntuforums.org/showthread.php?t=221174&page=63 [16:49] I found that but I think it's wrong. [16:49] At least.. the 1920x part is wrong. [16:49] Can LCDs be damaged by driving them at the wrong hsync/vsync ? [16:50] I remember CRTs could be [16:50] I can't speak for your milage, but I know as I tweak mine and get things wrong, the display just tells me invalid signal [16:51] Okay I added the montiro section [16:51] ...monitor section lines. [16:52] then in the subsection for display inside the "screen" add the "Modes "1680x1050@60" line. [16:53] or as many of the modes you are willing to add into the system. [16:53] What's the easiest way to try out the new config? [16:53] Cntrl-Alt-Backspace [16:54] Oh wow [16:54] I think it's working. :) [16:54] cool... [16:55] I connected my HVR-1600 to a antinnea for testing [16:55] now fix my PXE boot question ... :-O [16:55] ;) [16:55] This seems like a reasonable way to test right? [16:55] sure [16:55] you may even try the 1920x1080 settings [16:55] see what you get [16:56] X config files sure have gotten simpler over the years [16:56] Last time I messed with one it was...much larger. [16:56] well, they still can be... depends on how new the hardware you have is. [16:56] Newer is better or worse? ;) [16:56] haha... 6 of one half a dozen of the other [16:57] :-!freaking PXE [16:57] Should it say stuff about VESA in my Xorg.log ? [16:58] Ahh.. I think I'm not using the nvidia driver, lemme try and reboot. [16:58] hmmm? maybe... there are VESA standards for screen blanking and such [16:58] there also may be a few extra tweaks for the card itself [16:58] I'm able to rmmod nvidia (lol) [16:58] Lemme try a reboot [16:59] in your "Screen" section make sure that the Device specified is the same one that loads the "nvidia" driver [16:59] Driver "nvidia" [16:59] Does x64 myth work just as well as x32 by the way? [16:59] VendorName "NVIDIA Corporation" [16:59] Option "UseEDIDFreqs" "FALSE" [16:59] Option "UseEDIDDpi" "FALSE" [16:59] Option "ModeValidation" "NoEdidModes" [16:59] Option "ExactModeTimingsDVI" "TRUE" [17:00] Option "AllowDDCCI" "FALSE" [17:00] Option "UseEDIDFreqs" "FALSE" [17:00] Option "ModeValidation" "NoVesaModes, NoDFPNativeResolutionCheck, NoVirtualSizeCheck, NoPredefinedModes" [17:00] yup [17:00] A few years ago some codecs didn't work with 64-bit..Musta fixed that. It was just with xine. [17:00] that's what I've been using for over 6 months now and have been quite happy with it [17:00] Hmm, problem parsing the config file [17:00] Lemme see what I messed up [17:02] Are there any tools in Mythbuntu to look at the detailed logs of DHCP? I need to see what the vendor-class-identifier is reporting back from my diskless stations. [17:03] It's saying Modes isn't a valid thing to have in Section "Screen" [17:04] it's not in the screen section [17:04] it will be in the subsection "Display" [17:04] Ahh.. so I have to add a totally new section [17:04] Or is it a subsection of Screen? [17:04] right subsection of screen [17:04] id: [17:05] err: ie [17:05] Section "Screen" [17:05] Identifier "Screen0" [17:05] Device "Device0" [17:05] Monitor "Monitor0" [17:05] DefaultDepth 24 [17:05] SubSection "Display" [17:05] Depth 24 [17:05] Modes "1920x1080" [17:05] EndSubSection [17:05] EndSection [17:05] make sense? [17:05] Got it, lemme give it a spin. [17:05] Make sure the Device pointed to (in my case, Device0) points to the nVidia driver section [17:06] arg [17:07] !pastebin | Antharian [17:07] Antharian: when pasting more than 5 lines of data please use http://mythbuntu.pastebin.com so you don't flood the channel. Then please post the link in the channel. [17:07] tgm: sorry [17:07] np, future reference [17:08] anyone know if there's a problem w/myth running w/ an old nvidia 280 sd card [17:08] I've heard of conflicts [17:10] Sigh. Same screens problem. [17:11] How hard is it to install Myth onto a normal linux distribution? [17:11] Enox: there may be other options still missing [17:12] I feel pretty confident I can install a normal linux dist and X will work..Just wondering if the subsequent Myth install would be harder or easier than this X stuff. [17:12] http://mythbuntu.pastebin.com/d55268a37 [17:12] 50/50 [17:13] the updates are definitely nice to have with mythbuntu... if you can stick with that, over all you will be much happier. [17:13] Hmm [17:13] I just can't believe X doesn't work. [17:14] Yeah, mine is specific to this LCD. If I move it to my JVC or my Sony, all is good. [17:14] have you tried a newer driver? [17:14] Nope [17:14] Is one hard to install? [17:14] SUPER Easy [17:14] what is your card again? [17:15] 8400? [17:15] Vidia 8400GS [17:15] Sorry NVidia :) [17:15] http://www.nvidia.com/object/linux_display_amd64_180.22.html [17:22] How can I kill off X so i can run the NVIDIA thing? [17:22] alt-ctl-f1 [17:22] log in [17:22] become root [17:23] sudo su - [17:23] I did that so far :) [17:23] runlevel 1 [17:23] or runlevel S [17:23] Aha [17:23] Runlevel command doesn't work [17:23] says "unknown" [17:24] oops lied to you [17:24] sorry [17:25] Tried init 1 [17:26] Well that failed. [17:26] What's the X process called? It isn't X. [17:26] I can just killall it [17:26] init 1 [17:27] That brought X up, somehow. [17:27] not, gdm will just restart it [17:27] And my CA-F1 stuff just goes to messed up screens now [17:27] you can also do [17:27] So i can kill gdm ? [17:27] /etc/init.d/gdm stop [17:28] I'll try that after the reboot. init 1 did bad bad things [17:28] you may have to ssh into the box [17:34] killall xinit works ;) [17:38] Now it's saying there's no valid nvidia GPU on the system . . . [17:39] did you already reboot after the driver install? [17:39] Out of curiosity.. Is there a reason I can't 'watch TV' with the limited graphics? [17:39] Resolution & such seem fine. [17:39] I think the XVideo extensions are not available with the VESA driver. it would probably be pretty poor quality... but who knows. [17:40] It doesn't do anything when I do watch TV [17:40] The CPu is pretty good and such, shouldn't need the acceleration from vcard. [17:41] I have a AMD X2 Dual Core 4000+ in mine and watching it without XVideo extentions is not possible. [17:41] if your CPU is stronger, then perhaps you will have good luck. [17:42] I'd just kinda like see..something. :) [17:42] Any guess why watchtv doesn't do anything at all? [17:42] did you set up and recognize your tv card? [17:42] then scan for channels? [17:42] I didn't scan for channels [17:43] Maybe I need to do that. [17:43] that would do it [17:45] How does one scan for channels? :) [17:49] mythtv-setup [17:49] external program [17:49] Ahh cool. Was looking around in the frontend. [17:52] 1General 2Capture Cards 3Video Sources 4Input sconnections 5Channel Editor 6Storage Directories [17:52] probably need to go through all of them at some point or another [17:53] but typically going in order is best [17:53] I have.. My capture card is in ther and such [17:53] I just dont see a 'scan' option [17:53] There's a channel editor..But it seems to want to add individual channels [17:54] hang on... [17:56] did you do number 3 [17:56] you have to for channels [17:56] Yes.. schedulesdirect is in there [17:56] what type of course is it [17:57] Listings Grabber: North America (schedulesdirect.org) (Internal) [17:57] No data direct lineup selected [17:57] Oh wait.. perform EIT scan? [17:58] Do I need a lineup selected? [17:59] what type of tuner do you have [17:59] HVR-1600 [17:59] Connected to an analog antinnea for now [17:59] there we go [18:00] alright so dd you goto schedules direct and pay for the service [18:00] I haven't paid.. I'm on my 7 day trial [18:00] also you know in a month there wont be any analog service if you are in the use [18:00] But I have an account and such [18:00] Yes, I'm aware. [18:00] you couild t ry scanning atsc with that antenna [18:00] I'm sure I'll connect Myth to cable by then.. I just figured this would be simpler for now. [18:00] How do I scan atsc? [18:01] um, you will need an atsc antenna [18:01] a digital antenna [18:01] well you take the cable forom the antenna and move it from the analog input on the 1600 to the digital one [18:01] One can't scan analog? [18:02] tgm4883_laptop, i thought you just need a uhf and vhf antenna [18:02] i used one of those and atsc worked fine [18:02] Ahh.. so an analog antinnea works fine for digital? [18:02] i even got fm [18:02]