[00:04] no takers? [00:07] waited 16 minutes :( [00:07] I just saw it [00:07] * tgm4883_laptop sighs === superm1|away is now known as superm1 [00:51] i'm sending my cable box output via svideo into a usb2wintv. at first it's in color. but as soon as i change the channel it's in black and white. any idea what i have wrong? === superm1 is now known as superm1|away [00:55] what do you have to do to restore color? === gbutters is now known as gbutters_afk [01:21] help a newb pleasae - i have i installed but can not get any tv signal [01:23] you're going to have to provide more info than that to get help [01:24] installed on hardy 8.04 dell pc dual boot with xp [01:25] i have an icon in aps/sound.video for mythtv frontend [01:25] maybe some information about where you get TV and what kind of tuner would be useful and what exactly the problem is [01:26] tv from local cable - analog and tuner is a motherboard tv card built in by dell - xp is media center version [01:26] unless you're running MythTV on Windows, it's irrelevant [01:26] ok [01:27] what else can i tell you? [01:27] what happens? [01:27] how is it different from what you expect? [01:28] Greybear1, i'd go with the output of lspci and refer him to the manual [01:28] myth front end starts up grey background orange hilighted font for Watch TV but pressing enter at that point does nothing, no messages no tv [01:28] yeah, you're probably right tgm [01:28] i'm guessing you didn't do mythtv-setup [01:29] i did run thru it from system menu but i really didnt input much [01:29] you're referring to the MCC? [01:30] does it hurt to rerun it? [01:31] start at page 97 [01:31] terminal window started but has hung now. should i paste any of the text? [01:38] ive been thru that mcc setup and i reallt don't see that i have anything required. when i run the ap and choose Information Center/System Status, Tuner Status reads Tuner 1 is unavailable so I'm thinking it has not found the TV Tuner card. [01:38] did you run mythtv-setup? [01:39] yes [01:39] so, it found the tuner card and got listings? [01:42] i guess thats where im struggling. the only thing i changed in the General tab was channel freq to US Cable [01:42] Capture cards has 4 entries [01:43] New, Delete all cards on Dell, Delete all cards, [01:43] and v4l:/dev/video0 [01:43] so, did you add an entry for your card? [01:43] is the v4l the card? [01:43] whatever type of card you have [01:45] anyway ubuntu or myth detects? im not sure i know otherwise. [01:45] syntax error [01:46] card type listed when i select add new card is analog v4l capture card [01:46] is that correct? [01:46] and i can't access the field to change it to anything else [01:47] dunno - i have no documentation [01:47] there is a "probed info" line that reads "failed to open". meaningful? [01:48] sounds like to me [01:48] does failure sound good to you? [01:48] http://mythtv.org/wiki/index.php/Video_capture_card [01:48] no thats why i mentioned it... [01:49] i'll read thru that - thanks [01:49] good [01:51] Hi all === MythbuntuGuest70 is now known as Travi [01:52] My screen resolution isnt getting setup properly. if anyone has a moment can you take a look at the details here http://ubuntuforums.org/showthread.php?t=897100 [01:54] you're never going to get very good quality from S-Video [01:54] the edges are cut off because of overscan [01:55] is that a problem from using s-video? [01:55] http://en.wikipedia.org/wiki/Overscan [01:55] or being casued by something else [01:55] already there ;) [01:56] the main point is, don't use S-video for an LCD TV [01:56] All right [01:56] Greybearl I'm gonna have a look at XP device manager to see if the tuner card brand/model is listed. [01:56] doesn't it have DVI, HDMI, or D-Sub input? [01:56] I just happened to have the cables for it. Ill see what else it supports [01:56] you can use lspci to find the device too [01:56] dvi most likely. im checking now [01:57] hi all... i'm using mythbuntu 8.04 with ubuntu desktop... i'm having some interesting resolution issues that just started up on me. could use some help [01:57] first off: i'm using a 1080p tv. using dvi to hdmi [01:57] when i boot up the computer it's as though i'm zoomed in [01:58] i move my mouse to the edges of the screen to find icons etc. [01:58] so in order to regain the correct resolution i have to log out and back in [01:58] that's if i use hdmi port 3 on my tv... using ports 1 or 2 the zoom won't go away [01:59] the other issue i'm having is: i absolutely can not prevent mythtv from starting up at reboot... i have unchecked the box in the myth control center but it won't save my setting [02:00] so... any help on these two things would be much appreciated. I'm getting frustrated. haven't had any issues for months and can't figure out what I didn't to cause these problems [02:00] Ok, thanks greybear. I am going to try dvi to hmdi [02:00] yeah, digital is what you should be using if at all possible [02:03] but TVs are often very bad at behaving like monitors [02:03] it took me a long time to find a good mode for my LCD TV [02:03] try to stick to common ones like 720p@60 [02:04] it's been so long since i had this box running i forgot how i solved my svideo out being black and white [02:05] maybe the chroma wire is broken [02:08] Greybear1, i don't think so. i set this up about a year ago and had this issue. i fixed it somehow. we recently moved and i'm setting it up again. just forgot what the fix was :) [02:09] It sounds like Intrepid Mythbuntu should feel exactly like Hardy? [02:09] Er, I should say, Myth front-end in Mythbuntu. [02:09] Lots of control panel and infrastructure improvements, but basically the same Myth? [02:10] Greybear1 - sitting on the xp media center side now reading device mgr for dell dimension e510. Only thing I see is Radeon x600. [02:11] that doesn't help much [02:11] Googled the machine and found a review that reads "This entry-level Media Center PC lacks a TV tuner and digital audio ports, but serves well as a home or home office PC" [02:12] yet i do have coax input and can see/record tv..... [02:12] well that sounds like your problem [02:12] Hotkey, that's a media center? lol [02:12] larson9999 I know!!!! [02:12] sheesh... [02:13] Hotkey, actually, that's a reviewer? [02:13] larson9999 ya via about.com [02:14] and thats pulling a pcworld review [02:14] maybe the manufacturer's site is a better source [02:14] http://support.dell.com/support/edocs/systems/dimE510/ [02:14] just going there now [02:14] i feel dirty. i picked up xp home at a thrift store today for $2 so i could run magicjack. [02:14] another reviewer writes what a great tuner his 510 has! lol [02:15] larson9999, that's a good deal [02:15] It's a collectable, probably be worth 10X that in 4 years. [02:15] im sure [02:15] does it have a tuner card i can borrow :) [02:15] if you have a Dimension E510 with a tuner card, it wasn't original equipment [02:19] this xp home notwithstanding, i have had a string of good thrift store luck in the last week. 3 p4 2.66mgz machines with 1 gig ram for $15 each, windows server 2003 enterprise 25 cals sealed for $16 i sold for $500 on ebay. and a nintendo ds for $2.49 [02:19] Greybear1 ya it is - i ordered it - dell site lists e510 with several different tv cards........knowing which i have is a mystery [02:19] http://support.dell.com/support/downloads/driverslist.aspx?c=us&l=en&s=gen&ServiceTag=&SystemID=DIMENSION%205150/E510&os=WW1&osl=en&catid=&impid= [02:20] well, the owner's manual doesn't say anything about tuners [02:20] nice [02:21] im running belarc advisor to see if it picks it up [02:21] as I said before, you should be using lspci in Linux [02:24] Greybear1 now i know what lspci is. linux newb here. [02:25] I'm glad you're learning [02:25] trying - thanks for helping. [02:25] you're welcome [02:26] belarc lists RADEON X600 256MB HyperMemory [Display adapter] [02:26] and RADEON X600 256MB HyperMemory Secondary [Display adapter] [02:26] no other video/display items [02:26] those sound like display devices [02:26] and I don't know what belarc is [02:26] under multimedia i read "ATI Unified AVStream Driver" [02:27] belarc is the windows version of lspci [02:28] so, is that the video capture device? [02:29] i have no idea. prolly have to crcack it open and see for myself [02:31] if your device isn't on http://mythtv.org/wiki/index.php/Video_capture_card#Capture_Card_Matrix I wouldn't get my hopes up [02:31] as hokey as this has been its prolly not - if i add a new one what would you recommend? [02:32] depends entirely on the TV source [02:33] basic cable - i dont think i can pull in hd ota without big antenae [02:33] I've had pretty good experience with the PVR-150 [02:34] the PVR-500 has two tuners [02:34] nice [02:34] there are less expensive ones, but I don't have MythTV experience with any [02:44] hey all, I really need some help getting x configured, it's like my video card (via unichrome km400) isn't being detected. I ran linux on this laptop for years, so I know x works, but the mythbuntu setup doesn't see it for some reason. [02:45] can you just put the right driver in xorg.conf manually? [02:45] Greybear1 im still at it and found more detail about the radeon x600 - looks like its a dual purpose video card. [02:45] http://support.dell.com/support/edocs/video/P97737/en/index.htm [02:45] well, the important question is whether there's a Linux driver for it [02:46] Greaybear1, I tried - but the xorg.conf file itself is screwy - there's no modes, and the screens are configured [02:46] errrr ! i can't figure this out. everything else is in color. only when i watch tv is it black and white. the nvdia [02:46] Xorg doesn't necessarily need modes, but it does need a device [02:46] I ran Xorg -configure to get a custom configuration, but starting up with it gave me the same error (fatal server error no screens found) [02:47] Greybear1, I get this even with vesa set as the driver [02:47] larson9999: maybe your color Xv parameter is turned to zero [02:47] "no screens found" doesn't mean anything specific [02:47] you'll have to look earlier [02:48] Greybear1, where's that setting? [02:48] "color" [02:48] k, let me check the log [02:51] Greybear1 I didnt find it on the Capture card wiki rom your link above. I'll get a new one. Thanks for the help. [02:51] Greybear1, I keep seeing this - "ViaPanelGetIndex: Mode not supported by Panel." [02:51] is the mythbuntu kernel setup differently? [02:51] than what? [02:52] I get this with different resolutions [02:52] Not using default mode "640x350" (unknown reason) [02:52] (II) CHROME(0): Not using default mode "320x175" (bad mode clock/interlace/doublescan) [02:52] which mode do you expect to work? [02:53] I'm installing on a laptop, so 1024x768 [02:53] well, if you had Xorg working on it, perhaps you can use that config [02:54] can't gone [02:54] sigh [02:55] maybe a LiveCD will work [02:55] Nope [02:55] it's WEIRD [02:55] if you can find one that has the right Xorg mode, use its config [02:55] how many have you tried? [02:55] what do you mean? [02:55] there are many LiveCD systems [02:56] I used mythbuntu and mythdora - got the same problem on both [02:56] so, what did work? [02:56] but I've run live CD's on this before and they worked fine, but never "myth" cd's [02:56] regular ubuntu [02:56] then use it [02:57] that's my next step, but I was hoping to have the stripping down done for me [02:57] oh well [02:57] http://mythbuntu.org/existing-ubuntu [02:57] my thanks, I'll bookmark that and download ubuntu [02:57] if you want a minimal system, start with the Ubuntu alternate install CD and install the "text" system [02:57] ok [02:58] then, install the "mythbuntu-control-centre" package [02:58] hopefully, that'll pull in everything you need [02:58] but, I'm not sure how Xorg configuration will work [02:59] ok [02:59] if the regular Ubuntu desktop LiveCD sets a correct mode, that's more sure to work [02:59] well, I'll boot the live CD and make sure that works first [02:59] that mythdora didn't work as well concerns me [03:00] you said Ubuntu works [03:00] you can always remove packages later if you want to save space [03:00] yup [03:01] Mythbuntu is just a few extra packages that are already in the Ubuntu repositories and the installer CD [03:01] so, installing from an existing Ubuntu system ends up in almost exactly the same place [03:01] ok [03:02] they're not really separate projects [03:02] yah, it's just the preconfiguring I like - but oh well, if ubuntu works, I'll be glad [03:03] I used the Ubuntu alternate install CD [03:03] I was using Ubuntu for MythTV before Mythbuntu came along [03:04] that's how I installed it on my previous box [03:04] ok [03:04] all you need to know right now is how to get Xorg to run with the mode you want [03:05] if a LiveCD does that, just steal its config [03:05] it wouldn't even have to be Ubuntu [03:05] yup [03:07] dangit [03:07] I was hiping to be playing tonight, but now it's too late [03:07] thanks though greybear === gbutters_afk is now known as gbutters_zzzz [03:07] night [03:07] sure [04:41] lmao, tgm4883_laptop got you with the WASP knife [05:02] Greybeard, hey you there? [05:03] yes [05:03] greybeard :p not greybear [05:03] something changed my nick [05:04] So I think that i foudn the problem [05:04] after I did a reboot it didnt work right? [05:04] ok [05:04] But I think I know why === Greybear1 is now known as blah === blah is now known as Greybear1 [05:04] I have it set to /dev/dsp, when i did a reboot, i was getting my webcams microhpeon as the input [05:05] now for whatever reason, when i reboot, some times my mixer will be set to the tvcard, some times the hdaintel onboard sound, some times the audigy 2 card [05:05] yep [05:05] I think when that happens, it changes which device is assigned to which dsp number [05:05] that's why you should avoid using the OSS emulation devices [05:05] yeah, it's not stable [05:05] Hmmm, how do i do that? [05:05] that's why it's better to use an Alsa device name that contains the CARD [05:06] Hmmm well all these devices are using the alsa driver... or am i not following you? [05:06] the device nodes /dev/dsp* are the old OSS-style interface [05:07] if you use ALSA drivers, it provides those device nodes to emulate OSS [05:07] but it's generally better to use the native ALSA names [05:08] for one thing, you can always get the right device when you have multiple [05:08] gotcha... if only it would let me use the names [05:08] arecord -L gives you valid ALSA names [05:09] Greybear1, yeah, but remember when i try and put anythign in the audio device section of mythtv setup it wont let me [05:09] it will only take dev/dsp& [05:09] yeah, that seems to be the real problem [05:10] Btw you wouldnt happen to know of a way to make my mixer default to my audigy card would ya? I always have to go in and change it before i can use the adjust volume on my keyboard [05:10] ajhtiredwolf go into bios and disable onboard? [05:10] I don't think ajhtiredwolf can do that [05:10] squish102, if it had that option :-p, but even that wont help me, there are about 5 devices that it switches between [05:10] I think all devices are in use for something [05:11] there might be a way to cause the drivers to be loaded in a predictable order [05:12] there is a way to set the default device used, but i already have audigy2 set as default, other than that yeah i wonder if there is a way to set the order [05:12] I am kinda doubting it though [05:12] default in what? [05:12] sound card used [05:12] I assume you're talking about a particular application [05:13] I dont think so, but i did it a while ago, i was given advice in #ubuntu [05:13] you can configure the default Alsa devices in a config file [05:13] I believe that was it [05:13] but that won't help your MythTV recording problem [05:14] http://alsa-project.org/main/index.php/Asoundrc [05:14] right... so in your mythtvsetup you are able to put whatever you want into there? [05:15] I haven't had to configure this myself, since I don't need to have MythTV capture audio [05:15] so, I was surprised to find that it won't accept ALSA device names [05:15] Gotcha.. btw it was asoundconf set-default-card audigy2 that i did [05:15] the frontend configuration does accept ALSA names for playback device [05:16] oh, I wasn't aware of asoundconf [05:16] that's probably easier than doing it manually [05:17] that will affect any apps that use alsa-lib, which unfortunately doesn't seem to include mythbackend [05:18] So I guess my only chance is to stop the soundcards from changing order [05:18] yeah, that may be the only option [05:18] heh unfortunately ive tried to do that befoer but never gotten anywhere [05:19] probably the best way to do it would be in the udev configuration [05:20] btw i added the string of commands rmmod saa7134 sudo modprobe saa7134 card=42 tuner =5 alsa=1 to that file you suggested but i still have to do it manually before it works [05:21] I'm looking at http://www.mythtv.org/wiki/index.php/Device_Filenames_and_udev#Obtaining_identifying_information [05:21] I guess we don't know what the critical time is for loading that module [05:22] so, when you start up the machine, the saa7134 module is loaded, but you can't capture video? [05:22] but if you unload it and reload it, it starts working? [05:22] That seems to be the case yes [05:23] but i have to rmmod saa7134_alsa some times as well [05:23] it sounds like maybe that card just isn't very well supported [05:24] Not at all [05:24] I think that udev HOWTO in the MythTV wiki should do it [05:25] Im reading through it [05:25] what was the file that you said i should add those commands to ? [05:26] the file /etc/rc.local should run every time you boot [05:26] it runs as root, so you don't need to put sudo in it [05:26] I put rmmod saa7134_alsa [05:26] rmmod saa7145 [05:26] modprobe saa7134 card=42 tuner=43 alsa=1 [05:27] in it, just like that [05:27] after editing it, run it manually: "sudo /etc/rc.local" to make sure it's working [05:27] better use /sbin/modprobe to be safe [05:27] the PATH may be different [05:27] /sbin/modprobe and /sbin/rmmod [05:28] make sure you add your lines before the "exit 0" that's already there [05:29] it said that saa7134_alsa does not exist in /proc/modules [05:29] that means the module wasn't loaded [05:30] mm... tv is working [05:30] ok so basically that is just saying its an unnecesary step? [05:30] I'm not sure [05:31] I don't know what problem you're trying to work around [05:31] trying to rmmod a module that isn't loaded is harmless [05:32] ok so anyway, i tried doing rmmod saa7134 then i ran sudo /etc/rc.local [05:32] and it didnt work [05:32] what did it say? [05:32] is the module loaded? [05:32] Module saa7134_alsa does not exist in /proc/modules [05:32] how do i check if it is loaded? [05:32] lsmod|grep saa7134 [05:33] lsmod just lists loaded modules [05:33] did nothing [05:33] so it doesnt look like the modprobe is working [05:33] if it doesn't output anything, it means the module isn't loaded [05:33] is /etc/rc.local executable? [05:34] I beleve so since it is giving me an error when trying to run it [05:34] so? [05:34] what error? [05:34] ERROR: Module saa7134_alsa does not exist in /proc/modules [05:34] ok, so what's the contents of the file? [05:35] /sbin/rmmod saa7134_alsa [05:35] /sbin/rmmod saa7134 [05:35] /sbin/modprobe saa7134 card=42 tuner=43 alsa=1 [05:35] what happens if you run each of those lines individually on the command line? [05:36] ERROR: Module saa7134_alsa does not exist in /proc/modules [05:36] ERROR: Module saa7134 does not exist in /proc/modules [05:37] it worked after I did the last command [05:37] after doing sudo /sbin/modprobe saa7134 card=42 tuner=43 alsa=1 [05:37] which loads the module [05:37] then those work [05:37] so if the it hits an error ( the module isnt loaded ) then does it not execute the other lines? [05:37] if the lines are identical in the script file, they should have the same effect [05:38] that shouldn't be the case [05:38] ok i just ran sudo /etc/rc.local after loading the module [05:38] and it didnt give me an error [05:38] and it appears to have worked [05:39] I just noticed that the top line is "#!/bin/sh -e" [05:39] hmm i ran it again and it said RROR: Module saa7134 is in use by saa7134_alsa [05:39] that means any command that fails will cause the script to exit immediately [05:40] that is commented out htough [05:40] no, it's the shebang [05:40] Should I removei t? [05:40] #! is a special sequence [05:40] remove the "-e" [05:40] make the top line "#!/bin/sh" [05:41] ERROR: Module saa7134 is in use by saa7134_alsa [05:41] the line before that is rmmod saa7134_alsa so it should be doing that first.. [05:41] you have to remove saa7134_alsa before saa7134 [05:41] yeah, that is how it is set up [05:42] make sure there are no typos [05:42] lol, yeah nm [05:43] Alihgt hopefully that will work on boot [05:43] yeah, it probably will now [05:43] Is there a way to set it to automitcally go to telivision vs composite1 or s-video? [05:43] probably [05:43] that's a detail of the card I imagine [05:44] MythTV should set the capture card input when it starts recording [05:44] v4l2-ctl might do it [05:44] Alright, now onto setting the audio device [05:45] mmm and where is v4l2-ctl? [05:46] oddly, it's in ivtv-utils [05:46] I'm not sure if it works on non-ivtv v4l2 devices [05:47] Dont have that [05:47] don't have which? [05:47] install ivtv-utils if it's not already [05:49] maybe it would be simplest to add the correct modules to /etc/modprobe.d/blacklist then load them in rc.local [05:49] then you might be able to define the audio device order [05:51] Ok so like, ad whatever the name of the Audigy2, the intel, and the saa7134 are to the blacklist file, then tell rc.local to load them in a certain order? [05:51] right [05:52] I think any module names you put in that file shouldn't be autoloaded by Ubuntu startup scripts [05:52] and I think /dev/dsp? devices are numbered in the order the driver module is loaded [05:52] THere are qutie a few things listed under devices when i go to system preferences sound.. would i need to add them all? [05:53] there is audigy 2 zs, sb0350 alsa mixer [05:53] well, you need to determine which linux modules are audio drivers [05:53] Where can i list those? [05:53] ls asound or something? [05:54] lsmod [05:55] so, for instance, snd_emu10k1 is the main module for an Audigy card [05:55] if you put that at the end of /etc/modprobe.d/blacklist I think the Audigy devices won't appear [05:56] Hmm im actually not seeing audigy2 listed here, i see the saa7134 [05:56] but no audigy [05:56] listed where? [05:56] under lsmod [05:57] that's because the module is called snd_emu10k1 [05:57] alright, there seem to be allot that have to do with saa7134 [05:58] we're only interested in ALSA sound drivers right now [05:58] when opening the sound utility in system preference, under devices there is listed saa7134(ALSA) [05:58] saa7134_alsa seems to be the sound capture driver for your card, right? [05:58] but you said it doesn't seem to work [05:59] Correct [05:59] well, audio out works [05:59] out of what? [05:59] i have a wire going from the audio out port of the tuner device, to the audio in of the audigy 2 [05:59] the saa7134 [06:00] you have to do that because saa7134_alsa doesn't work [06:00] if it worked, it would allow MythTV to capture on the TV card instead of having to go the Audigy line in [06:00] alright, so which devices should i add to blacklist? [06:01] we know saa7134_alsa and snd_emu10k1 [06:01] are there any others? [06:01] The hda_intel [06:01] and the logitech webcam [06:02] so that's snd-hda-intel [06:02] what about the webcam? [06:04] Im not sure what it is named [06:04] It isnt listed under devices as far as i can see [06:04] what's the model? [06:04] I know that right now it is dev/sbd [06:04] sbd0 i mean [06:04] weird [06:04] I don't know what sbd means [06:05] let me try this [06:05] I thought a camera would be /dev/video something [06:05]