| Batshua | Hi. New problem from me. Mythbackend is giving me a "failed to bind to port 6543" error. | 00:57 |
|---|---|---|
| Batshua | I'm not sure it /ever/ worked since I'm still figuring out how to set everything up. | 00:57 |
| Batshua | But I think I have everything else set up so far except the remote, which, guess what? Is not officially supported. I hear rumors of people making it work, but I haven't heard anything concrete about how to do that. Anyone who could help with that, that'd be awesome. If not, I assume I can make things work with zap. | 01:07 |
| Batshua | ... If I'm really wrong about that, feel free to slap me upside the head. | 01:10 |
| acloseX | what's the IP address you have your Mythbackend set at? | 01:15 |
| acloseX | i think by default it's localhost | 01:15 |
| acloseX | did you change it? | 01:15 |
| Batshua | they should both be at 127.0.0.1 or whatever be's the default | 01:21 |
| Batshua | wherein when I ran mythtv-setup, that's what I put. | 01:21 |
| acloseX | you didn't change any of the default ports, did you? | 01:22 |
| Batshua | I hope not? | 01:22 |
| Batshua | the defaults should be as they are | 01:23 |
| Batshua | I broke it once already so I made sure it was as it should have been. | 01:23 |
| acloseX | :) | 01:23 |
| Batshua | ... but it's not working. | 01:24 |
| acloseX | did you restart the backend? | 01:24 |
| Batshua | I /can't/. | 01:24 |
| Batshua | That's the problem. | 01:24 |
| Batshua | running mythbackend exits at Failed to bind port 6543. | 01:24 |
| acloseX | oh, so when you start it it just dies... | 01:25 |
| acloseX | is something else running on that port? | 01:25 |
| Batshua | not that I know of. | 01:26 |
| acloseX | try: netstat | grep 6543 | 01:26 |
| Batshua | blank line. prompt. | 01:26 |
| Batshua | so I'm gonna say "no". | 01:26 |
| acloseX | hmm | 01:27 |
| Batshua | my mythbox is totally cursed. I researched stuff for months before I went shopping and yet all KINDS of things aren't working right. or maybe *I* am the one who is cursed. but in any event, at least y'all are patient and helpful. | 01:28 |
| acloseX | :) | 01:28 |
| acloseX | heh, i know how you feel | 01:28 |
| acloseX | i did the same thing | 01:28 |
| Batshua | my dad is freaking out at me | 01:28 |
| Batshua | because he for some reason thought it would be up and running the day I built it. | 01:28 |
| acloseX | had a Mythbox running fine and decided to build a new one that could handle HD to replace the first | 01:28 |
| Batshua | and I'm like, ... it's REALLY not that simple. | 01:29 |
| Batshua | oh dear. | 01:29 |
| acloseX | so i'm partially working :) | 01:29 |
| Batshua | so, story. i went shopping for some screws for my case because the one I bought came up short on screws (horrible plastic topped thumbscrews, anyhow) | 01:30 |
| Batshua | and the guy at the store was like | 01:30 |
| Batshua | you know the acrylic cases aren't shielded against emf pulses, right? | 01:30 |
| Batshua | and I was just thinking | 01:30 |
| Batshua | you know, if we get hit by a NUCLEAR BOMB | 01:30 |
| acloseX | :) | 01:30 |
| Batshua | my biggest concern WON'T be my mythbox. | 01:30 |
| Batshua | I mean, yeah, it'll suck because if we get nuked we probably won't have tv anyway | 01:31 |
| Batshua | but I bet I'll be too busy trying to survive to worry about whether or not I can record shows. | 01:31 |
| Batshua | I dunno, that's just me. Maybe my priorities are screwed up. | 01:33 |
| acloseX | did you do the myth install yourself, from scratch? or are you using a distro, like MythBuntu or MythDora? | 01:34 |
| Batshua | I installed Ubuntu | 01:34 |
| Batshua | and then I added on mythbuntu | 01:35 |
| acloseX | added Myth via synaptic? | 01:35 |
| Batshua | yes, I /believe/ so | 01:38 |
| Batshua | I can't remember what I did. | 01:38 |
| Batshua | I've done SO MUCH CRAP since I started building this box | 01:39 |
| acloseX | MythBuntu is a linux distro that bundles Mythtv with it, as is MythDora, KnoppMyth and a couple others | 01:39 |
| acloseX | :) | 01:39 |
| Batshua | which sadly was like, ... 2 weeks ago. | 01:39 |
| acloseX | it might be easier to try one of those solutions | 01:39 |
| Batshua | yeah, you can add on mythbuntu | 01:39 |
| Batshua | to a regular install | 01:39 |
| Batshua | which is what I did. | 01:39 |
| Batshua | you suggesting a wipe? | 01:39 |
| acloseX | they're almost out of the box type deals | 01:39 |
| Batshua | *flails* well, I guess I best start downloading now if I want help setting it up tonight. | 01:40 |
| acloseX | well, :) since i'm no guru, that's what i'd do. especially since it's a newish system | 01:40 |
| Batshua | oh, wait, I can't set it up until wed night | 01:40 |
| Batshua | but whatever, I can start downloading tonight. | 01:40 |
| acloseX | maybe someone else will chime in and can help you out | 01:41 |
| acloseX | i'm sorry i don't have any better suggestions :} | 01:42 |
| Batshua | it's alright, at least you tried. | 01:42 |
| Batshua | I'll download it, and see what happens. | 01:42 |
| Batshua | of course, the fun part will be wiping the right partition to do this, because my /Videos and my /Music are different HDs and they already have Stuff on them | 01:56 |
| Batshua | this is why I am waiting a couple days until my hand-holding SO can help me out. | 01:56 |
| acloseX | ok, so here's my problem | 02:09 |
| acloseX | fresh install of MythBuntu 8.10 | 02:10 |
| acloseX | things appear to be happy, but my HDHR is always marked as unavailable | 02:10 |
| acloseX | looking in the mythbackend.log after a reboot i see that the backend attempts to 'discover' the HDHR, but it gets an error: | 02:11 |
| acloseX | Starting up as the master server. | 02:11 |
| acloseX | 2009-02-03 20:08:05.725 HDHRChan(1011014d/0), Error: Unable to send discovery request | 02:11 |
| acloseX | eno: Network is unreachable (101) | 02:11 |
| acloseX | 2009-02-03 20:08:05.746 HDHRChan(1011014d/1), Error: Unable to send discovery request | 02:11 |
| acloseX | eno: Network is unreachable (101) | 02:11 |
| acloseX | ERROR: no valid capture cards are defined in the database. | 02:11 |
| acloseX | Perhaps you should read the installation instructions? | 02:11 |
| acloseX | then i realize it looks like the backend is looking for the HDHR before networking has been initialized | 02:11 |
| acloseX | so... | 02:11 |
| acloseX | how do i bump networking up in the boot order? | 02:11 |
| acloseX | i see my PVR-250 recognized in dmsg, but no mention of the HDHR in there | 02:13 |
| acloseX | here's a clean listin of my logs: http://mythbuntu.pastebin.com/f24be213c | 02:15 |
| acloseX | i can ping my HDHR at its IP address successfully from the Mythbox | 02:24 |
| acloseX | and the hdhomerun_config discover command finds it ok | 02:24 |
| tritium | acloseX: why would you expect to see the HDHR listed in dmesg? | 02:26 |
| * acloseX scratches head | 02:26 | |
| acloseX | not sure. i kind of assumed the system would look for it | 02:27 |
| tritium | nope | 02:27 |
| acloseX | but i guess it's not really a part of the system, is it... | 02:27 |
| tritium | No. | 02:27 |
| acloseX | but it is still possible that the backend is looking for it before the network is set up..? | 02:28 |
| acloseX | is there any way to get the backend to rescan for the HDHR manually? | 02:33 |
| tritium | acloseX: update-rc.d can be used to modify initscripts, but it appears that mythtv-backend is started *after* networking is. | 02:34 |
| tritium | Are you relying on network-manager for your network connection? | 02:35 |
| acloseX | i'm guessing so, as i see it in the logs | 02:36 |
| acloseX | whatever is the default :) | 02:36 |
| tritium | acloseX: well, how is your network configured? Static IP? Dynamic IP? | 02:37 |
| acloseX | it's dynamic, but my router reserves an IP for my Mythbox based on it's mac | 02:37 |
| acloseX | maybe that's my prob... | 02:37 |
| acloseX | i have had the HDHR working | 02:38 |
| acloseX | but it might have been with a static IP | 02:38 |
| tritium | acloseX: where did you configure it? Through network-manager? | 02:38 |
| tritium | Pastebin your /etc/network/interfaces, please | 02:38 |
| acloseX | sure, one sec | 02:38 |
| acloseX | no need to pastebin :) | 02:38 |
| acloseX | it's two lines | 02:39 |
| acloseX | auto lo | 02:39 |
| acloseX | iface lo inet loopback | 02:39 |
| acloseX | let me double check my router settings | 02:39 |
| tritium | Then you're definitely using network-manager | 02:40 |
| tritium | I suggest you configure your IP, even dynamic if you want, in /etc/network/interfaces | 02:40 |
| acloseX | ok, i'll give that a try | 02:41 |
| acloseX | looking at my router, which does my dhcp | 02:41 |
| tritium | I doubt it's your router. | 02:41 |
| acloseX | i do have an IP reserved for the mythbox based on mac address | 02:41 |
| acloseX | i'll set up /etc/network/interfaces and see if that helps | 02:42 |
| tritium | Yes, but network-manager initializes too late. Don't use it. | 02:42 |
| acloseX | /aclose | 03:02 |
| acloseX | tritium, you still there? :) | 03:21 |
| tritium | acloseX: yes | 03:21 |
| acloseX | i've updated my /etc/network/interfaces | 03:22 |
| acloseX | and turned off network manager | 03:22 |
| tritium | good | 03:22 |
| acloseX | and restarting networking i do get the correct IP, but i'm unable to connect to the outside world | 03:22 |
| tritium | Did you configure a gateway? | 03:23 |
| foxbuntu | tritium, acloseX why are you doing this? | 03:23 |
| tritium | foxbuntu: network-manager is starting after mythtv-backend initscript runs | 03:24 |
| acloseX | yeah, but might not be correct. here's my network/interfaces: http://mythbuntu.pastebin.com/d3b603c33 | 03:24 |
| acloseX | my routers IP address is 10.0.0.1 | 03:24 |
| foxbuntu | tritium, then adjust the initscript with rc | 03:24 |
| acloseX | which i 'assumed' would be the gateway | 03:25 |
| tritium | foxbuntu: that was my first suggestion, if you scroll up | 03:25 |
| foxbuntu | acloseX, you need a default route | 03:25 |
| foxbuntu | tritium, making these changes is a bad idea and doesnt fix the real issue, just covers up its symptoms and is not supportable/sustainable | 03:25 |
| tritium | foxbuntu: standard networking configuration in /etc/network/interfaces is a bad idea? How so? | 03:26 |
| foxbuntu | tritium, not that, disabling network-manager this way is the bad idea | 03:27 |
| tritium | I never suggested he disable it. | 03:28 |
| acloseX | foxbuntu: i disabled it according to the Ubuntu NetworkManger docs :) | 03:28 |
| acloseX | bad idea? | 03:28 |
| acloseX | sorry, maybe i misunderstood tritium | 03:28 |
| foxbuntu | acloseX, what changed to cause this to happen? | 03:28 |
| acloseX | new install | 03:29 |
| foxbuntu | of? | 03:29 |
| foxbuntu | 9.04? | 03:29 |
| acloseX | trying to get my HDHR working again | 03:29 |
| foxbuntu | 8.10? | 03:29 |
| acloseX | 8.10 | 03:29 |
| foxbuntu | updated? | 03:29 |
| foxbuntu | or no? | 03:29 |
| acloseX | for some reason it looks like mythbackend starts up and does the discovery for the HDHR before networking is available | 03:29 |
| acloseX | yes, updated | 03:29 |
| foxbuntu | acloseX, that was an issue some time ago | 03:30 |
| foxbuntu | acloseX, static IP or DHCP? | 03:30 |
| acloseX | i was using DHCP with my DHCP server(router) reserving an IP | 03:30 |
| foxbuntu | that should be fine | 03:31 |
| tritium | I had the same issue when I tried using a wireless card, and relying on network-manager. I reverted to ethernet, and configuring in /etc/network/interfaces | 03:31 |
| foxbuntu | tritium, thats the same as setting a static IP in network-manger | 03:32 |
| acloseX | i'm ethernet | 03:32 |
| foxbuntu | acloseX, you might try a static IP with network manager to check if its DHCP response time that is your real problem | 03:33 |
| tritium | foxbuntu: no, I tried that. network-manager didn't touch /etc/network/interfaces at all. It has its own config files, it would appear. And, it got configured later. | 03:33 |
| tritium | I believe its settings are in /etc/NetworkManager/ | 03:33 |
| acloseX | ok, i think i've undone what i did :) | 03:34 |
| foxbuntu | tritium, no, it does edit /etc/network/interfaces | 03:35 |
| foxbuntu | acloseX, give a static address via network-manager a try | 03:35 |
| tritium | foxbuntu: I assure you it did not | 03:35 |
| foxbuntu | tritium, I am not going to argue, its not worth my time | 03:35 |
| tritium | I'm not arguing. | 03:36 |
| acloseX | ok. is ther ean easy way to use NM in MythBuntu? | 03:36 |
| acloseX | it doesn't apper to be in System -> whatever :) | 03:36 |
| foxbuntu | acloseX, very easy | 03:36 |
| foxbuntu | acloseX, right click the Computer looking icon by the clock | 03:36 |
| foxbuntu | Edit Connections | 03:36 |
| acloseX | got it | 03:37 |
| acloseX | in IPv4 Settings, i switched Method to Manual | 03:43 |
| foxbuntu | ok | 03:44 |
| acloseX | added the IP i want, its netmask and gateway | 03:44 |
| acloseX | also updated DNS and Search | 03:44 |
| foxbuntu | ok | 03:44 |
| acloseX | added a route | 03:44 |
| acloseX | but the 'ok' button is greyed out | 03:44 |
| foxbuntu | shouldnt need to add the route | 03:44 |
| foxbuntu | it will generate one for you | 03:44 |
| acloseX | ok, removed | 03:45 |
| acloseX | 'ok' is still unaccessible | 03:45 |
| foxbuntu | on the main part of the IPv4 settings? | 03:45 |
| acloseX | on the main window panel | 03:46 |
| acloseX | i can cancel or close the window | 03:46 |
| foxbuntu | hmm | 03:47 |
| acloseX | i'm logged in as my default user | 03:47 |
| foxbuntu | try restarting network-manager | 03:47 |
| foxbuntu | acloseX, that should be fine | 03:48 |
| acloseX | oh, in network connections, maybe i needed to add a new connection instad of editing the default 'Auto eth0'? | 03:49 |
| foxbuntu | nope | 03:49 |
| foxbuntu | you did it right | 03:49 |
| acloseX | as soon as i switch to Manual the 'ok' button goes grey | 03:50 |
| foxbuntu | did you click add to add an IP? | 03:51 |
| acloseX | yes | 03:51 |
| acloseX | well, now it appears ok :) | 03:52 |
| acloseX | not sure what i did | 03:52 |
| foxbuntu | ok | 03:52 |
| acloseX | i had it all filled out before :) | 03:52 |
| foxbuntu | make sure the IP is set (Right Click the Icon Again > Connection Info) then reboot and see if things work for you | 03:54 |
| acloseX | ok, networking appears to be correct | 03:57 |
| acloseX | HDHR is still unreachable upon boot | 03:58 |
| acloseX | but IP and everythig stuck | 03:58 |
| tritium | acloseX: can you pastebin your /etc/network/interfaces for me, please? | 03:58 |
| rhpot1991 | acloseX: have you tried powering down the HDHR and powering it back up? | 03:58 |
| rhpot1991 | I had mine get stuck one and that fixed it | 03:59 |
| acloseX | no, i haven't tried that. not a bad idea | 03:59 |
| acloseX | but i can ping it and can discover it using the hdhomerun_config discover tool/cmd | 03:59 |
| foxbuntu | acloseX, also, if you have done so, try updating the firmware on the HDHR | 03:59 |
| acloseX | foxbuntu: http://paste.ubuntu.com/113457/ | 04:00 |
| acloseX | not much in there | 04:01 |
| tritium | acloseX: as I suspected. Thanks. Same thing happened to me. | 04:01 |
| acloseX | that is what the default was when i first started | 04:01 |
| acloseX | i'll double check my HDHR firmware, but it's been updated in the last coule months | 04:02 |
| foxbuntu | acloseX, then its prob fine | 04:02 |
| tritium | foxbuntu: as you can see, I was not arguing. I was stating fact. | 04:02 |
| foxbuntu | tritium, mine has my network-manager settings in it and a line # Generated By NetworkManager at the top | 04:03 |
| foxbuntu | tritium, thats the end of the conversation, if you have more idea to add to resolve (not mask) acloseX's issue, feel free to add to that conversation as this one is fruitless | 04:04 |
| acloseX | i had sen that in the /etc/resolve.conf, but not in /etc/network/interfaces | 04:04 |
| acloseX | here is my most recent mythbackend.log: http://paste.ubuntu.com/113459/ | 04:04 |
| tritium | foxbuntu: I never tried to mask his issue. I'm not sure why you'd accuse me of that. | 04:04 |
| foxbuntu | tritium, last warning, its over, drop it | 04:05 |
| tritium | Take it easy. No need for accusations or anger. | 04:06 |
| acloseX | line 13 of that log, any idea why it's stating 'eno: Network is unreachable...', instead of 'eth0'? | 04:07 |
| acloseX | i'm using the onboard nic in my mobo and there is only one... | 04:09 |
| tritium | acloseX: my suspicion would still be that there's nothing in your /etc/network/interfaces to configure the interface. | 04:09 |
| foxbuntu | acloseX, you can try auto eth0 | 04:10 |
| foxbuntu | in that config | 04:10 |
| foxbuntu | put it at the top | 04:10 |
| foxbuntu | then reboot | 04:10 |
| acloseX | sure thing | 04:11 |
| rhpot1991 | sudo /etc/init.d/networking restart | 04:12 |
| acloseX | :) | 04:12 |
| acloseX | too late | 04:12 |
| rhpot1991 | could use that instead of rebooting | 04:12 |
| foxbuntu | rhpot1991, the reboot is to test the rc | 04:12 |
| acloseX | i'll try to remember that for next time :) | 04:12 |
| * rhpot1991 isn't really paying attention much | 04:13 | |
| * foxbuntu noticed | 04:13 | |
| rhpot1991 | heh | 04:13 |
| foxbuntu | ;) | 04:13 |
| hads | You and your rebooting | 04:13 |
| acloseX | fox, rhpot, are you guys Mythbuntu developers? or just helping out and being friendly? | 04:14 |
| acloseX | system is back up | 04:14 |
| acloseX | ifconfig looks good | 04:14 |
| acloseX | mythbackend.log still Unable to discover.... | 04:15 |
| acloseX | i'll give the HDHR a reboot too :) | 04:16 |
| rhpot1991 | hads: I tried to stop him :) | 04:16 |
| hads | :) | 04:16 |
| foxbuntu | hads, yea yea | 04:16 |
| foxbuntu | hads, www.foxmediasystems.com | 04:17 |
| foxbuntu | hads, ;) | 04:17 |
| hads | I was waiting for that :) | 04:17 |
| foxbuntu | there now we got it all out of the way for the night | 04:17 |
| foxbuntu | well day for you | 04:17 |
| acloseX | cool | 04:18 |
| acloseX | i 'thought' that would be an interesting business | 04:19 |
| acloseX | but i'm no Linux/Myth guru :) | 04:19 |
| foxbuntu | acloseX, interesting it has been | 04:19 |
| rhpot1991 | acloseX: I develop some things | 04:20 |
| foxbuntu | rhpot1991, bugs :) | 04:20 |
| foxbuntu | lol | 04:20 |
| rhpot1991 | foxbuntu: and month long SRU journeys | 04:20 |
| acloseX | :) | 04:20 |
| foxbuntu | rhpot1991, yeah, SRUs = bad | 04:20 |
| acloseX | no luck with a restart of the HDHR either. | 04:22 |
| acloseX | it gets the same IP, and i can ping/discover it | 04:22 |
| acloseX | rebooting the mythbox it's still unreachable | 04:22 |
| * foxbuntu is trying to find the bug report related to this | 04:23 | |
| foxbuntu | rhpot1991, there was a bug for this some time back wasnt there? | 04:23 |
| acloseX | i thought i had seen some mention of it on the Mythtv mailing list | 04:24 |
| rhpot1991 | foxbuntu: I'm not sure sorry | 04:25 |
| acloseX | but, at the time, i had the thing working :) so didn't pay too much attention to it | 04:25 |
| acloseX | i can't seem to find it searching the archives | 04:25 |
| foxbuntu | acloseX, I found that | 04:25 |
| foxbuntu | I am reading through it now | 04:25 |
| foxbuntu | acloseX, you could try moving the rc script | 04:28 |
| foxbuntu | couldnt hurt at this point | 04:28 |
| acloseX | the /etc/update-rc.d script? | 04:28 |
| foxbuntu | acloseX, no | 04:29 |
| foxbuntu | acloseX, ls /etc/rc2.d/*mythtv-backend | 04:29 |
| foxbuntu | then like on my system it would be: sudo mv /etc/rc2.d/S20mythtv-backend /etc/rc2.d/S99mythtv-backend | 04:30 |
| acloseX | oh, ok | 04:30 |
| foxbuntu | that will make mythtv-backend startup last | 04:31 |
| foxbuntu | which should allow networking enough time to come all the way up | 04:31 |
| foxbuntu | which for some reason on your machine its doing slowly | 04:31 |
| acloseX | weird that it had worked before though | 04:31 |
| foxbuntu | acloseX, you can check out the other logs (or use mythbuntu-log-grabber to get them) to see if there is something indicating why networking is slow | 04:32 |
| acloseX | any particular log i should focus on? | 04:33 |
| foxbuntu | prob the syslog | 04:33 |
| acloseX | i ws looking through the grabber last night | 04:33 |
| acloseX | i'll see if anything stands out | 04:33 |
| foxbuntu | with the script moved try to reboot and see if things come up normally | 04:34 |
| foxbuntu | acloseX, is this a clean install of 8.10 or an upgrade from earlier releases | 04:35 |
| acloseX | fresh install | 04:35 |
| foxbuntu | k | 04:35 |
| foxbuntu | yeah, the network-manager bug I was thinking of is from 7.10 | 04:35 |
| foxbuntu | thats really old | 04:36 |
| acloseX | http://mythbuntu.pastebin.com/fb2dfca5 | 04:36 |
| acloseX | no luck on the reboot | 04:38 |
| foxbuntu | intresting | 04:40 |
| foxbuntu | well looking at your syslog the NIC is coming online normal | 04:40 |
| foxbuntu | acloseX, in your tuner configuration in mythtv-setup, did you use the default of FFFFFF for the hdhr id or use your actual id? | 04:41 |
| acloseX | actual id | 04:41 |
| acloseX | 1011014D | 04:42 |
| foxbuntu | ok | 04:42 |
| foxbuntu | ....it __shouldnt__ matter if you only have one | 04:42 |
| foxbuntu | but just trying to rule things out | 04:42 |
| acloseX | yep, only one | 04:42 |
| acloseX | well, i'm done for tonight | 04:45 |
| acloseX | i really appreciate the help/suggestions | 04:45 |
| acloseX | maybe i'll think of what i did differently this time around and be able to slap myself upside the head :) | 04:46 |
| foxbuntu | ok | 04:47 |
| foxbuntu | night | 04:47 |
| acloseX | thx again | 04:48 |
| YooPhGluP | does anyone know how to get an pvr-150mce card to work?????? | 06:34 |
| pteague | anybody have any opinions on zotac mobos? i'm thinking of getting http://www.newegg.com/Product/Product.aspx?Item=N82E16813500020 for a frontend | 16:48 |
| pteague | any idea if the intel e1200 celeron will play hi-def video ? | 17:17 |
| foxbuntu | pteague, likely not | 18:18 |
| pteague | i may just stick with getting http://www.newegg.com/Product/Product.aspx?Item=N82E16813121359 then | 18:19 |
| foxbuntu | pteague, I have one of those | 18:20 |
| foxbuntu | ...havent had time to test it yet | 18:20 |
| foxbuntu | but I have a FE built and sitting around based on that | 18:20 |
| foxbuntu | pteague, if your worried about hd video, I would suggest you stick to a microATX board and a full proc | 18:21 |
| foxbuntu | pteague, also to get the best performance from the Atom you will need an LPIA kernel' | 18:22 |
| foxbuntu | ...which has its own can of worms as I understand (and there isnt a mythbuntu build for) | 18:22 |
| pteague | i have the previous atom 230 that i'm currently using for my frontend... i'm planning to get the 330 & use the 230 for my fileserver | 18:25 |
| foxbuntu | hows it working for HD video? | 18:26 |
| foxbuntu | ...and are you using lpia? | 18:26 |
| pteague | not using hd video yet... i've got a pvr-500 in my backend & frontend is currently only plugged into a 19" widescreen | 18:27 |
| foxbuntu | oh | 18:28 |
| foxbuntu | I just need to make it happen, I have everything I need to test it | 18:28 |
| foxbuntu | lol | 18:28 |
| foxbuntu | I have piles of hardware in my home office now | 18:28 |
| pteague | it runs ok, but the 230 is limited to 1gb ram... the 330 has a 2gb, it's a bit faster processor, & i'm hoping the video will be a bit better... 230 only has a d-sub | 18:28 |
| foxbuntu | and a 40" 1080p LCD | 18:29 |
| pteague | 1 thing i was looking at was http://www.newegg.com/Product/Product.aspx?Item=N82E16813500020 - d-sub + dvi & i think i saw 1 of these had an hdmi adapter... only issue is you have to buy cpu separately | 18:29 |
| pteague | i'm thinking a geforce 7100 should be able to maybe possibly handle the hd ? | 18:30 |
| foxbuntu | if it supports VDPAU i think it would be ok | 18:31 |
| foxbuntu | but iirc thats only 8xxx+ | 18:31 |
| foxbuntu | pteague, check out the antec fusion mini | 18:31 |
| foxbuntu | its a pretty nice case, little larger than you are looking but gives you much better hardware options | 18:32 |
| pteague | the zotac i was originally looking at is an AM2+/AM2, but has a geforce 8200 which my understanding is there's a bug in the drivers - http://www.newegg.com/Product/Product.aspx?Item=N82E16813500021 | 18:32 |
| foxbuntu | pteague, yes there is a bug in the 8200 | 18:32 |
| foxbuntu | as in they dont work | 18:32 |
| foxbuntu | at least last time I tired them | 18:32 |
| yepun | I am facing instability in loading the firmware dvb-fe-tda10046.fw for my PCI TV card using the module tda1004. Frequently it goes in timeout and after a bit it load the correct revision but I get a process continuously running at 10-15% of CPU! any idea/suggestions? | 21:25 |
| yepun | I have also the syslogs for additional info if someone had a similar problem | 21:27 |
| oobe | /j #poo | 22:11 |
| oobe | woops | 22:11 |
| === oobe is now known as oobe_ | ||
| === oobe_ is now known as oobe | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!