Re: [mythtv-users] Myth/spdif no audio, mplayer works fine
I found mine on ebay. On Wed, 30 Mar 2005 08:35:54 -0600, Andrew Close [EMAIL PROTECTED] wrote: sorry to hijack this thread, but where would i look to get an SPDIF connector for my motherboard? Chaintech, the manufacturer, doesn't appear to carry a connector as an accessory anymore. my mobo does have posts labeled for SPDIF out though. i've looked at various computer/electronics shops online, but i can only seem to find sound cards that are SPDIF capable. what should i search on to find an adapter? thanks for any help. you may now resume the initial thread. ;) andy ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Myth/spdif no audio, mplayer works fine
It was a while ago. I think I typed in ASUS SPDIF and it gave me a mess of crap. Here is a link to ebay with an ASUS SPDIF module. It MIGHT work for your Chaintech. You might have to adjust the pins, I am not sure. Jim On Wed, 30 Mar 2005 08:48:53 -0600, Andrew Close [EMAIL PROTECTED] wrote: On Wed, 30 Mar 2005 08:44:40 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I found mine on ebay. hi Jim, i tried a quick search on ebay yesterday and didn't see anything. what were you using as search criteria? maybe i was trying to be too specific: motherboard spdif connector thanks andy On Wed, 30 Mar 2005 08:35:54 -0600, Andrew Close [EMAIL PROTECTED] wrote: sorry to hijack this thread, but where would i look to get an SPDIF connector for my motherboard? Chaintech, the manufacturer, doesn't appear to carry a connector as an accessory anymore. my mobo does have posts labeled for SPDIF out though. i've looked at various computer/electronics shops online, but i can only seem to find sound cards that are SPDIF capable. what should i search on to find an adapter? thanks for any help. you may now resume the initial thread. ;) andy ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] DCT-6200 w/ FireWire -- Looking for Input..
720p will be more space. It is a progressive scan whereas the 1080i is an interlaced scan. Electronically, 1080i is equivalent to 540p. That should give you an idea. As far as how much space, I am not sure. I don't have a high def TV yet. On Wed, 30 Mar 2005 08:44:18 -0800, Big Wave Dave [EMAIL PROTECTED] wrote: Are there any recommendationso n FireWire PCI cards? I've been looking at all the usual places, just wanted to avoid any problematic ones. Heh, NOT the on-board crap on one of my Asus boards, it didn't work worth a damn... However, I've had good success with the FireWire port on a SoundBlaster Audigy, as well as the card in my master backend right now, which is a Western Digital branded card, NEC OrangeLink chipset. So, it looks like I'll go with the following setup... Intel 3Ghz w/ HT 512MB DDR RAM 300GB UDMA/100 Drive NVidia MX4000 (using SVIDEO out) FireWire Host Adapter It seems like this will be sufficient from what everyone has been saying. How fast does HD use up disk space? Does the raw firewire dump provide 1080i or 720p? I don't need 1080i... I don't even need 720p... but I'm guessing the 720p will require less space. Thanks, Dave Are Your Friends Lemmings? -- http://www.lemmingshirts.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Watching regular DVD's on MythTV
My don't you use Xine instead of mplayer? It has support for DVD menus which is sweet. It also is a lot easier to configure for AC3 or any sort of audio out. I just tell it to use PassThrough for all my audio and it gets thrown out in AC3 for DVDs and PCM for everything else. Just make sure your asound.conf (or .asound) is correct. I had inadvertantly commented out a line and mplayer worked fine, but Xine wouldn't pass out audio. It's all working swizzle now. On Wed, 30 Mar 2005 11:04:44 -0800, Richard Sears [EMAIL PROTECTED] wrote: Hey Everyone - I know that there 'appears' to be issues around watching DVD's (actual, physical DVDs) under MythTV, but I cannot seem to put my finger on the resolution. I know I need some typs of decoder or codec to allow MPlayer (and hench Myth) the ability to watch DVDs just like I do with my Denon DVD player. Can someone point me in the right direction for the best solution. Thanks -- ** Richard J. Sears Vice President American Internet Services [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.adnc.com 858.576.4272 - Phone 858.427.2401 - Fax INOC-DBA - 6130 I fly because it releases my mind from the tyranny of petty things . . Work like you don't need the money, love like you've never been hurt and dance like you do when nobody's watching. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Watching regular DVD's on MythTV
Well I know that attitude won't get you anywhere. How was he supposed to know you meant LEGAL issues? You NEVER specified that. Is he supposed to read your mind like the fools that work under you? The reason I call them fools is because only a FOOL would want to work with an egotistical person like yourself who thinks the world revolves around them. I have seen too many Vice Presidents, or Directors with the same attitude and it is FRIGHTENING how you people manage to KEEP your jobs!! Next time, do us all a favor and visit a different mailing list. Anthony was nothing but helpful. Get a clue buddy. BTW: Why would I be able to LEGALLY play DVDs in Windoze and not in *nux? On Wed, 30 Mar 2005 14:30:05 -0800, Richard Sears [EMAIL PROTECTED] wrote: Anthony - Don't worry - you don't sound like a jerk, you sound like an idiot. The reason (which you missed) around the appears is the legal issue of playing DVDs under Linux and the codec and decoder issues surronding these things. As quick a wit as you are at striking out, I am surprised that you missed that. Thaks for nothing and please don't bother responding to any of my posts in the future. Thanks On Wed, 30 Mar 2005 16:38:09 -0500, Anthony Vito [EMAIL PROTECTED] wrote: I know that there 'appears' to be issues around watching DVD's (actual, physical DVDs) under MythTV, but I cannot seem to put my finger on the resolution. That's such an executive response. I can almost hear Lumbergh's voice in the text. There 'appears' to be issues with your.. umm, TPS reports. All jokes aside.. Do you seriously think anyone could possibly hope to do anymore then guess at solutions with the mannor in which you've stated your problem? I don't want to sound like a jerk, but given the credentials at the bottom of your email, you should know how to properly form a technical question. Answer these, and the minds on this list will surely solve all your problems very quickly. How is your myth installed, and what version? ( rpms or compiled ) What did you do to setup DVD playing in myth? What happens when you play a DVD in myth? What do you expect to happen when you play a DVD in myth? I know I need some typs of decoder or codec to allow MPlayer (and hench Myth) the ability to watch DVDs just like I do with my Denon DVD player. Can someone point me in the right direction for the best solution. -- Anthony Vito [EMAIL PROTECTED] -- ** Richard J. Sears Vice President American Internet Services [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.adnc.com 858.576.4272 - Phone 858.427.2401 - Fax INOC-DBA - 6130 I fly because it releases my mind from the tyranny of petty things . . Work like you don't need the money, love like you've never been hurt and dance like you do when nobody's watching. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Editing .asoundrc for Xine 5.1 passthru with SB Live!
I assume you are trying to output via SPDIF. What do you get when you
run aplay -l. That's a lowercase L. That will list out your devices
on your sound card. In my asound.conf I have my digital out PCM as
device 0,2. Here is my asound.conf:
# Override the default output used by ALSA.
# If you do not override the default, your default
# device is identical to the (unmixed) analog device
# shown below. If you prefer mixed and/or digital
# output, uncomment the appropriate four lines below
# (only one slave.pcm line).
pcm.!default {
type plug
## Uncomment the following to use mixed analog by default
# slave.pcm dmix-analog
## Uncomment the following to use unmixed digital by default
slave.pcm digital-hw
## Uncomment the following to use mixed digital by default
# slave.pcm dmix-digital
}
# Alias for analog output on the nForce2 (hw:0,0)
# - This is identical to the device named default--which
# always exists and refers to hw:0,0 (unless overridden)
# - Therefore, we can specify hw:0,0, default, or analog
# to access analog output on the nForce2
pcm.analog {
type plug
slave.pcm analog-hw
}
# Control device (mixer, etc.) for the nForce2 card
ctl.analog {
type hw
card 0
}
# Alias for (rate-converted) mixed analog output on the
# nForce2 (hw:0,0)
# - This will accept audio input--regardless of rate--and
# convert to the rate required for the dmix plugin
# (in this case 48000Hz)
pcm.mixed-analog {
type plug
slave.pcm dmix-analog
}
# Control device (mixer, etc.) for the nForce2 card
ctl.mixed-analog {
type hw
card 0
}
# Alias for (rate-converted) digital (S/PDIF) output on the
# nForce2 (hw:0,2)
# - This will accept audio input--regardless of rate--and
# convert to the rate required for the S/PDIF hardware
# (in this case 48000Hz)
pcm.digital {
type plug
slave.pcm digital-hw
}
# Control device (mixer, etc.) for the nForce2 card
ctl.digital {
type hw
card 0
}
# Alias for mixed (rate-converted) digital (S/PDIF) output on the
# nForce2 (hw:0,2)
# - This will accept audio input--regardless of rate--and
# convert to the rate required for the S/PDIF hardware
# (in this case 48000Hz)
pcm.mixed-digital {
type plug
slave.pcm dmix-digital
}
# Control device (mixer, etc.) for the nForce2 card
ctl.mixed-digital {
type hw
card 0
}
# The following devices are not useful by themselves. They
# require specific rates, channels, and formats. Therefore,
# you probably do not want to use them directly. Instead use
# of of the devices defined above.
# Alias for analog output on the nForce2 (hw:0,0)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.analog-hw {
type hw
card 0
# The default value for device is 0, so no need to specify
}
# Control device (mixer, etc.) for the nForce2 card
ctl.analog-hw {
type hw
card 0
}
# Alias for digital (S/PDIF) output on the nForce2 (hw:0,2)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.digital-hw {
type hw
card 0
device 2
}
# Control device (mixer, etc.) for the nForce2 card
ctl.digital-hw {
type hw
card 0
}
# Direct software mixing plugin for analog output on
# the nForce2 (hw:0,0)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.dmix-analog {
type dmix
ipc_key 1234
slave {
pcm analog-hw
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
}
# Control device (mixer, etc.) for the nForce2 card
ctl.dmix-analog {
type hw
card 0
}
# Direct software mixing plugin for digital (S/PDIF) output
# on the nForce2 (hw:0,2)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.dmix-digital {
type dmix
ipc_key 1235
slave {
pcm digital-hw
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
}
# Control device (mixer, etc.) for the nForce2 card
ctl.dmix-digital {
type hw
card 0
}
In here, change the hw0,2 to whatever aplay -l displays. I hopw it helps.
Jim
On Wed, 30 Mar 2005 21:06:43 -0500, Nate Thompson
[EMAIL PROTECTED] wrote:
I was just wondering if anyone has had any luck getting their SB Live! Card
to play a DD5.1 soundtrack via Xine using the 'Pass Thru' setting in the
setup menu? Whenever I select this option, I only get garbled sound output.
I'm assuming it is because I am using a very basic .asoundrc file that isn't
configured properly. Has anyone tried to use Jarod's updated file
(http://wilsonet.com/mythtv/asoundrc.txt) that he made for his Audigy with a
standard SB Live! card? Any tips would definitely be apprechiated. If it
matters, I believe I am using ALSA 1.06.
Nate Thompson
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] PCR-250 Sound Issues
I have a PVR-250 that I bought through Ebay and it is sitting in my backend box. FC3 installed using APT. Kernel = 2.6.10-1.760 I believe. The problem is, I notice poor sound quality when recording off of this card. It's not STATICY per se (well maybe), but it doesn't sound as loud/good as a recording done on my PVR-350 card. I can switch back and forth between the live feed from cable and my MythBox and there is a HUGE difference. You know when you have a tape recording that you turn up REALLY loud between songs. You can hear that same staticy noise behind the audio for the TV show (Dukes of Hazzard if you must know :-)~ ). The thing is, the static isn't constant, but only when there is sound coming from the show. If no one is talking, no cars jumping etc, there is no static. I am REALLY hoping there isn't anything wrong with the card. The backend originally had the 350 in it, then I added the 250 a couple weeks later. In the setup of it, I ran the commands from Jarod's website: # /usr/bin/ivtvctl -u 0x3000 # /usr/bin/ivtvctl -p 4 # /usr/bin/ivtvctl -f width=720,height=480 Is there anything else I should have done? I setup the tuner in modprobe.conf to be: options ivtv tuner=47,50 The tuner for the second card was listed out, but could it be possible that the wrong one is listed? Could that cause this sound issue? Do I have a bad card? Thanks! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Watching regular DVD's on MythTV
You just can't let it go can you asshole? GIVE UP. YOU LOSE. We proved you are an ignorant hypocritical fool. So are you gonna dance naked with Rush hoping that no one will watch? BTW, with an attitude like that, you won't keep them for long. Eitherway, you aren't the one keeping your business going. Your technicians are. Trust me, I know. You are superfluous. Watch out for the mutiny jackass. On Wed, 30 Mar 2005 20:48:28 -0800, Richard Sears [EMAIL PROTECTED] wrote: Hey Matt - Thankfully I have customers such as Rush Limabugh, Oprah, Anthony Robbins, CNBC, State Street Bank, Motorola, SAIC, Sony and about 50,000 others Matt, I don't need your business. And yes, please do the traceroutes. http://store.rushlimbaugh.com http://boutique.oprah.com http://tapesandtransccripts.oprah.com http://cnbc.burrellesluce.com http://store.anthonyrobbins.com But I appreciate the thought. On Wed, 30 Mar 2005 19:20:14 -0600, Matt [EMAIL PROTECTED] wrote: At the rate you are going, I can't see why anyone on this list would want to reply to you with any help from this point on given your unnecessary attitude. Anthony was trying to help you out by telling you the information we all need to help you out.. but he's absolutely right, you're question really didn't give us any information to go off of. The majority of people who use Myth to play DVDs have absolutely NO issues and the information on how to accomplish that is abundant on the e-mail lists, in the documentation, in user write-ups, and in google. If you want people to help you out, don't come on a mailing list and start calling people idiots. You'll see how quickly these idiots come to ignore you. Politeness gets you a long way, acting the way you do only makes you look like the fool. Also, I now know from your signature that if I ever had to do business with American Internet Services... that I wouldn't. On Wed, 30 Mar 2005 14:30:05 -0800, Richard Sears [EMAIL PROTECTED] wrote: Anthony - Don't worry - you don't sound like a jerk, you sound like an idiot. The reason (which you missed) around the appears is the legal issue of playing DVDs under Linux and the codec and decoder issues surronding these things. As quick a wit as you are at striking out, I am surprised that you missed that. Thaks for nothing and please don't bother responding to any of my posts in the future. Thanks On Wed, 30 Mar 2005 16:38:09 -0500, Anthony Vito [EMAIL PROTECTED] wrote: I know that there 'appears' to be issues around watching DVD's (actual, physical DVDs) under MythTV, but I cannot seem to put my finger on the resolution. That's such an executive response. I can almost hear Lumbergh's voice in the text. There 'appears' to be issues with your.. umm, TPS reports. All jokes aside.. Do you seriously think anyone could possibly hope to do anymore then guess at solutions with the mannor in which you've stated your problem? I don't want to sound like a jerk, but given the credentials at the bottom of your email, you should know how to properly form a technical question. Answer these, and the minds on this list will surely solve all your problems very quickly. How is your myth installed, and what version? ( rpms or compiled ) What did you do to setup DVD playing in myth? What happens when you play a DVD in myth? What do you expect to happen when you play a DVD in myth? I know I need some typs of decoder or codec to allow MPlayer (and hench Myth) the ability to watch DVDs just like I do with my Denon DVD player. Can someone point me in the right direction for the best solution. -- Anthony Vito [EMAIL PROTECTED] -- ** Richard J. Sears Vice President American Internet Services [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.adnc.com 858.576.4272 - Phone 858.427.2401 - Fax INOC-DBA - 6130 I fly because it releases my mind from the tyranny of petty things . . Work like you don't need the money, love like you've never been hurt and dance like you do when nobody's watching. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- ** Richard J. Sears Vice President American Internet Services [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.adnc.com 858.576.4272 - Phone 858.427.2401 - Fax INOC-DBA - 6130
Re: [mythtv-users] Watching regular DVD's on MythTV
It's really easy to start a flame war when you sound like a complete jackass then try to blame others for your faults. A marine would never do that. You would think that with a CCNA (big whoop, my 15 yr old cousin is a CCNA) you would better understand Linux and the GNU license!! Either way, you are not worth the time anymore. I have done what I set out to do, prove you wrong. You still haven't proven to me and EVERYONE ELSE IN THIS THREAD that you aren't a complete douch. Lata bitch tits! On Wed, 30 Mar 2005 20:53:38 -0800, Richard Sears [EMAIL PROTECTED] wrote: Your right Jim, This just keep getting better and better by the minute. Its rather interesting that a flame war can be started in a few short e-mails. You called me a dumb f**k..? Just to set the record straight - former US Marine, CCNA, CSE, MCP, F5SE, CFI, CFII, COMM ASMEL, Rotor, FAA Accident Prevention Counselor, Current President of two school boards, president of my flying club, self employed for the last 16 years and a millionaire - all by 37. As far as blowing my boss - notice the part about being self employed..? While I am good at many things, self fellatio is not one of them. If thats a dumb f**k - I gladly accept that title. :-) Geeze I love the internet !! On Wed, 30 Mar 2005 18:52:25 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Alright buddy. Let's break down your original email. I know that there 'appears' to be issues around watching DVD's (actual, physical DVDs) under MythTV, but I cannot seem to put my finger on the resolution. Let's see, issues around watching DVDs...No mention of legality there. Sounds more like you couldn't figure out MythDVD I know I need some typs of decoder or codec to allow MPlayer (and hench Myth) the ability to watch DVDs just like I do with my Denon DVD player. * If you actually read the lists, you would know that MPLAYER supports PLAYING DVDs up to the menu and that Xine will do what you want (play ACTUAL DVDS IN LINUX). When you say decoder or codec you make NO MENTION OF LEGALITY ISSUES. Damn, this is getting more difficult by the minute! Can someone point me in the right direction for the best solution. Why don't you crawl back to your crappy ISP and blow your boss because that is the ONLY way you are gonna keep your job. Dumb fuck. How about NOT flaming considerate people just because you can't word your questions corrrectly. -- ** Richard J. Sears Vice President American Internet Services [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.adnc.com 858.576.4272 - Phone 858.427.2401 - Fax INOC-DBA - 6130 I fly because it releases my mind from the tyranny of petty things . . Work like you don't need the money, love like you've never been hurt and dance like you do when nobody's watching. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] PCR-250 Sound Issues
After you mentioned the --device=/dev/video1, I remembered that I did do that cuz the output was crazy. So why would I need msp3400? I thought that was for a different card (not PVR-*50)? On Wed, 30 Mar 2005 22:12:50 -0700, Mr. Myth [EMAIL PROTECTED] wrote: I am no expert here recording that you turn up REALLY loud between songs. You can hear that same staticy noise behind the audio for the TV show (Dukes of Hazzard if you must know :-)~ ). The thing is, the static isn't constant, but only when there is sound coming from the show. If no one is talking, no cars jumping etc, there is no static. I am REALLY hoping there isn't anything wrong with the card. The backend originally had the 350 in it, then I added the 250 a couple weeks later. In the setup of it, I ran the commands from Jarod's website: # /usr/bin/ivtvctl -u 0x3000 # /usr/bin/ivtvctl -p 4 # /usr/bin/ivtvctl -f width=720,height=480 This only effects the first card. You probably want something like /usr/bin/ivtvctl -u 0x3000 -d /dev/video0 /usr/bin/ivtvctl -p 4 -d /dev/video0 /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video0 /usr/bin/ivtvctl -u 0x3000 -d /dev/video1 /usr/bin/ivtvctl -p 4 -d /dev/video1 /usr/bin/ivtvctl -f width=720,height=480 -d /dev/video1 Is there anything else I should have done? I setup the tuner in modprobe.conf to be: options ivtv tuner=47,50 With the recent 0.2.x drivers you should remove that line and let it auto detect your tuners. So you should have something like: # ivtv modules setup alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 ivtv alias tveeprom tveeprom-ivtv alias msp3400 msp3400-ivtv Assuming you are using atrpms. Michael ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] When do we get this feature in Myth???
I love the quote from the Tivo spokesperson: Our goal is in no way to interfere with the TiVo experience, TiVo spokesman David Shane said. Advertisement goes directly AGAINST the nature of TiVo. Anything to appease corporations. I dropped TiVo because of the monthly charges and the fact that they could come in and unhack my box to eliminate certain features like TivoWeb, telnet etc. On Tue, 29 Mar 2005 12:26:03 -0600, Andrew Close [EMAIL PROTECTED] wrote: http://news.zdnet.com/2100-1040_22-5644197.html just kidding :D maybe Myth will get the respect it deserves now. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] The nvidia-settings tool and Myth (keeping overscan right)
I have tried creating a mode line by using the PowerStrip method and my screen didn't change AT ALL while pressing buttons. If I went to far with the screen expansion, the entire TV would go black with some crazy horizontal lines on top. How were you able to get your SVID out to do a mode line? On Mon, 14 Mar 2005 10:17:11 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I was kinda hoping not to have to do a modeline...it looks like that might be the only way. On Mon, 14 Mar 2005 08:56:13 -0500, Dewey Smolka [EMAIL PROTECTED] wrote: It took me a while to fix the screen size after I upgraded -- I accidentally lost all my original config files -- but I finally got the size right by tweaking the mode lines in XF86Config. Note: This is MythTV 0.17 from Knoppmyth R5V12. I'm using an Nvidia Geforce 2 with S-video out to the TV only. Before I added the extra mode lines, Myth would display to the TV at 800x600, leaving about 1 to 1.5 of unused space on the left and right sides of the screen. With these settings, the display reaches all the way to the right side of the screen and almost all the way to the left side without having to monkey around with nvtv or nvidia-settings. Here are the relevant lines from XF86Config-4: [I commented out the DDC-probed settings to prevent the system from going to 800x600. This may not be a necessary step. The lines that work are the ones under the Inserted from gossamer-threads comment.] Section Monitor Identifier Monitor0 Option DPMS true Option TVStandard NTSC-M Option ConnectedMonitor TV Option TVOutFormat SVIDEO Option NoLogo 1 Option TVOverScan 0.8 VendorName KDS ModelName KDS1983 HorizSync 30 - 50 # DDC-probed VertRefresh 60 # DDC-probed # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine 768x576 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine 768x576 63.07 768 800 960 1024 576 578 590 616 # Inserted from gossamer-threads.com/lists/users/42881#42881 Modeline 720x576/50p 27.15 720 736 880 896 576 578 579 606 # 27 MHz, 3 0.3 kHz, 50.0 Hz Modeline 768x576/50p 29.09 768 792 936 960 576 578 579 606 # 29 MHz, 3 0.3 kHz, 50.0 Hz Modeline 800x600/50p 31.60 800 824 968 1000 600 602 603 632 # 32 MHz, 31.6 kHz, 50.0 Hz Modeline 1024x768/50p 44.80 1024 1056 1200 1280 768 770 772 808 # 45 M Hz, 35.0 kHz, 43.3 Hz Modeline 640x480/50p 20.20 640 656 800 800 480 482 483 505 # 20 MHz, 2 5.2 kHz, 50.0 Hz # These are the DDC-probed settings reported by your monitor. # 1600x1200, 75.0Hz; hfreq=93.75, vfreq=75.00 #ModeLine 1600x1200 202.50 1600 1664 1856 2160 1200 1201 1204 1250 + hsync +vsync # 1280x1024, 85.0Hz; hfreq=91.15, vfreq=85.02 #ModeLine 1280x1024 157.50 1280 1344 1504 1728 1024 1025 1028 1072 + hsync +vsync # 1152x864, 75.0Hz; hfreq=67.50, vfreq=75.00 #ModeLine 1152x864108.00 1152 1216 1344 1600 864 865 868 900 + hsync +vsync # 1024x768, 85.0Hz; hfreq=68.68, vfreq=85.00 #ModeLine 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 + hsync +vsync # 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03 #ModeLine 1024x768 78.75 1024 1040 1136 1312 768 769 772 800 + hsync +vsync # 1024x768, 70.0Hz; hfreq=56.48, vfreq=70.07 #ModeLine 1024x768 75.00 1024 1048 1184 1328 768 771 777 806 - hsync -vsync # 800x600, 85.0Hz; hfreq=53.67, vfreq=85.06 #ModeLine 800x600 56.25 800 832 896 1048 600 601 604 631 + hsync +vsync # 800x600, 75.0Hz; hfreq=46.88, vfreq=75.00 #ModeLine 800x600 49.50 800 816 896 1056 600 601 604 625 + hsync +vsync # 800x600, 72.0Hz; hfreq=48.08, vfreq=72.19 #ModeLine 800x600 50.00 800 856 976 1040 600 637 643 666 + hsync +vsync # 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32 #ModeLine 800x600 40.00 800 840 968 1056 600 601 605 628 + hsync +vsync # 640x480, 85.0Hz; hfreq=43.27, vfreq=85.01 #ModeLine 640x480 36.00 640 696 752 832 480 481 484 509 - hsync -vsync # 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00 #ModeLine 640x480 31.50 640 656 720 840 480 481 484 500 - hsync -vsync # 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94 #ModeLine 640x480 25.17 640 648 744 784 480 482 484 509 - hsync -vsync EndSection [...] Section Screen Identifier Screen0 Device Card0 Monitor
Re: [mythtv-users] MythTV Overscanning Screen?
There is a section in Jarod's how to that explains how to eliminate this. I can't remember where it's at. On Tue, 29 Mar 2005 16:51:23 -0500, Jason M. Sullivan [EMAIL PROTECTED] wrote: I'm running a Fedora Core 3, ATrpms, Jarod-instructed MythTV setup (0.17), and I'm having problems with the image overscanning my display. Watching TV looks fine (though it's hard to tell), but the Xwindows desktop (and MythTV as a result) seems too big for the display (ie. there's stuff beyond the visible edge of the screen that I need to see, like Next and Finish buttons in the MythTV setup (I got it working despite that, but I'd like to get that part tweaked right). I've got a Hauppage PVR-350, btw. -- Jason M. SULLIVAN [EMAIL PROTECTED] |c-oo http://www.jason0x21.org \_- That's not music, that's just sound! - J. David Fries ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] SVid Out Problems(PowerStrip xvidtune)
I have tried xvidtune, telling it to widen the screen and move it up. The numbers change, but the screen does nothing. I have also tried loading windows on a seperate hard drive and running powerstrip with no joy. I can change the numbers so far then boom, screen goes ape. But up to that point, the screen doesn't move. Does xvidtune and PowerStrip only work ong VGA/DVI out? How can I move the screen around with out using OVERSCAN in Xorg and not using the nvidia-settings tool? Thanks! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Blue band right side of picture
Does anyone have any more comments on this? On Fri, 18 Mar 2005 16:59:49 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I also am having this problem. After looking closely at my screen, I have noticed some things: The blue bands are actually the background of X I guess, or Myth I don't know. The picture seems to be too far to the right. The whole thing looks like it could go left and up several pixels. On the far right of the picture, it looks as if it is off the screen. Here is what I am trying to explain. There is a blue background, X. It is the size of the screen indicated in the xorg.conf. The output from the nvidia card is not evenly placed on the screen. The output is slightly to far to the left on the horizontal axis but not on the vertical. There is more of a space on the top of the screen than the bottom. When I run the overscan from nvidia-settings, the screen reaches the bottom and the left first. There is a picture that is layed over the top of the background. We will call this the image. In my case the image is not covering the screen completely. It is right several pixels and down several pixels which means I can see the blue background on the top and left of the screen. I tried the xvidtune and it did absolutely nothing. I told it to test the settings and nothing happened. The screen didn't look like it moved at all. I applied the moving left settings and tried to play a recording and still had the same blue bars. Will xvattr allow me to move the screen over? It obviously controls the color settings. What else can it do (man xvattr doesn't reveal much). On Fri, 18 Mar 2005 10:10:05 -0500, Mark L. Cukier [EMAIL PROTECTED] wrote: xvattr changes the background from blue to black, which would in fact eliminate the blue bar. However, my real problem is the black space to the right of the blue bar. my picture is shifted to the left about 3-2!!! This is the problem I'd really like addressed - Mark Phill Edwards wrote: I just switched from my nVidia TV-out back to my PVR350. The TV Quality is much better... however, now I seem to be having this same problem!!! I have a thin blue line down the rightside of my screen, with a thicker black (dead) area to the right of that. overscan doesn't seem to fix anything... this seems to be the area where the right side of the PVR350 ENDS! Has anyone experienced this? Any fixes? I tried running xvidtune, but PVR350 doesn't seem to like any of the modlines involving making the picture wider! Errmmm - what's wrong with the solution posted in this thread re xvattr? Regards, Phill ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- -- *Mark L. Cukier*, /Design Engineer/ PE Microcomputer Systems 710 Commonwealth Avenue Boston, MA 02215 _ e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone : (617) 353-9206 x19 fax : (617) 353-9205 _ visit us on the web at: http: //www.pemicro.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Strange Menu Button Behavior in Myth
I have been having issues with the buttons in Myth. Buttons in the setup, buttons when I go to exit out are all acting strange. When I use the keyboard to scroll to the button I want, I hit either ENTER or the SPACE BAR and the app just sits there looking at me. The button actually depresses on screen, but Myth does nothing. If I move my mouse around enough, I can get the buttons to light up (like they are highlighted) and then I click on the button and the command executes immidiately (I don't actually see the mouse cursor, but I know it's there and just being hidden by the app). It's very strange. In Jarod's Guide, there is a section on keeping focus on the mouse, so I did that after I started seeing this behavior and haven't seen any difference. I must have rebuilt my frontend half a dozen times in the past 2 months and this is the first time I have seen this happen. I am not sure if this is relevant, but it seems like after I got my LIRC working to the point of seeing output from IRRECORD, I started having this issue. Using the remote on my frontend doesn't work in MYTH yet, but that is a seperate thread. Anyone seen this or have any clues? Thanks! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Strange Menu Button Behavior in Myth
No prob about firing back questions, thats how you get an answer. To answer your Q's, I don't compile. I am using FC3 and am installing from FTP site (my own internal). I am then using ATRPMs to install nvidia, kernel, lirc, myth etc. On Thu, 24 Mar 2005 09:54:59 -0500, Ken Edwards [EMAIL PROTECTED] wrote: I have seen this on my GFs laptop that runs FC3, but not on a Gentoo machine or Mac OS X. I haven't had the time lately to troubleshoot, but my first guess might be a bad binary somewhere. You say you rebuilt your frontend a bunch of times, so I'm guessing that you are building from source. What about QT, have you upgraded that? Is that compiled from source or a binary? Sorry about just firing back questions, but that's all I have at the moment as well! Ken. On Thu, 24 Mar 2005 08:48:06 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I have been having issues with the buttons in Myth. Buttons in the setup, buttons when I go to exit out are all acting strange. When I use the keyboard to scroll to the button I want, I hit either ENTER or the SPACE BAR and the app just sits there looking at me. The button actually depresses on screen, but Myth does nothing. If I move my mouse around enough, I can get the buttons to light up (like they are highlighted) and then I click on the button and the command executes immidiately (I don't actually see the mouse cursor, but I know it's there and just being hidden by the app). It's very strange. In Jarod's Guide, there is a section on keeping focus on the mouse, so I did that after I started seeing this behavior and haven't seen any difference. I must have rebuilt my frontend half a dozen times in the past 2 months and this is the first time I have seen this happen. I am not sure if this is relevant, but it seems like after I got my LIRC working to the point of seeing output from IRRECORD, I started having this issue. Using the remote on my frontend doesn't work in MYTH yet, but that is a seperate thread. Anyone seen this or have any clues? Thanks! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Stable release branch starting post-0.18
Cheese and beer. Explosive. On Wed, 23 Mar 2005 09:35:35 -0600, Alex Cruz [EMAIL PROTECTED] wrote: On Wednesday 23 March 2005 09:18 am, Neil Bird wrote: Around about 23/03/05 09:32, Jarod Wilson typed ... Hey folks, I've volunteered to be the sucker/punching bag to try to maintain a stable release branch of Myth. This all seems oddly familiar to a recent discussion on the lkml... :-) Comments/suggestions welcome. I suggest we all owe you a beer :) In fact, most of us probably owe you several already, so I hope your liver's strong ;-) Is a 0.18 semi-imminent, then? I second Neil's suggestion. If you're ever in the greater Madison WI area, I'll buy you several good beers...and some cheese, too :-) -alex ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Re: USB MCE IR Receiver
Alright. I have fixed the 4KSTACKS issue and commented out the
EXTRAVERSIONS in the MAKEFILE. I successfully compiled LIRC. After
moving my .ko dev and mceusb files to their correct locations, I
rebooted the machine and received this error in my /var/log/messages:
Mar 20 18:31:05 mythfrontend kernel:
/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
mceusb_setup2 - Unsuccessful initialization
Mar 20 18:31:05 mythfrontend kernel: usbcore: registered new driver lirc_mceusb
Mar 20 18:31:05 mythfrontend kernel:
/home/mythtv/compile/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c: USB
Microsoft IR Transceiver Driver v0.2.jim
You can see that at the end, I tacked on the .jim to the .h driver
file in the #DEFINE section. I have compared my PRODUCTID and
VENDORID numbers to the ones in the lirc_mceusb.h file I made and they
are identical to my ProdID and VendorID. I have found the
mceusb_setup2 location in the lirc_mceusb.c file. Here is what it
says:
static void mceusb_setup2( struct usb_device *udev, struct usb_skel* dev )
{
char data[16];
int res, size;
memset( data, 0, 16 );
res = usb_control_msg(udev, usb_rcvctrlpipe(udev, 0),
USB_REQ_GET_STATUS, USB_DIR_IN, 0, 0,
data, 2, HZ);
dprintk(%s - Get Status: res = %d, status = 0x%x 0x%x,
__func__, res, data[0], data[1]);
memset( data, 0, 16 );
res = usb_control_msg(udev, usb_sndctrlpipe(udev, 0),
USB_REQ_SET_CONFIGURATION, 0, 1, 0,
data, 0, HZ);
dprintk(%s - Set Configuration #1: res = %d, __func__, res);
/* Doesn't seem strictly necessary, but the Windows driver does it */
memset( data, 0, 16 );
data[0] = 0;
data[1] = 0xFF;
data[2] = 0xAA;
data[3] = 0xFF;
data[4] = 0x0B;
res = usb_bulk_msg(udev, usb_sndbulkpipe(udev,
dev-bulk_out_endpointAddr),
data, 5, size, HZ);
dprintk(%s - Send #1: res = %d, data = 0x%x 0x%x, size=%d,
sendAddr=%d, __func__, res, data[0],
data[1], size, dev-bulk_out_endpointAddr);
if (res == -ETIMEDOUT)
{
err(%s - Unsuccessful initialization, __func__);
return;
}
memset( data, 0, 16 );
res = usb_bulk_msg(udev, usb_rcvbulkpipe(udev,
dev-bulk_in_endpointAddr),
data, 16, size, HZ);
dprintk(%s - Receive #1: res = %d, size=%d, receiveAddr=%d,
__func__, res, size, dev-bulk_in_endpointAddr);
memset( data, 0, 16 );
data[0] = 0xFF;
data[1] = 0x18;
res = usb_bulk_msg(udev, usb_sndbulkpipe(udev,
dev-bulk_out_endpointAddr),
data, 2, size, HZ);
dprintk(%s - Send #2: res = %d, size=%d, sendAddr=%d,
__func__, res, size, dev-bulk_out_endpointAddr);
memset( data, 0, 16 );
res = usb_bulk_msg(udev, usb_rcvbulkpipe(udev,
dev-bulk_in_endpointAddr),
data, 16, size, HZ * 5);
dprintk(%s - Receive #2: res = %d, size=%d, receiveAddr=%d,
__func__, res, size, dev-bulk_in_endpointAddr);
}
I am a little confused by the two memset(data,0,16) that is listed
above. What could be the problem here? Thanks!!
On Sat, 19 Mar 2005 17:23:59 +0100, Axel Thimm [EMAIL PROTECTED] wrote:
On Fri, Mar 18, 2005 at 06:49:05PM -0600, Jim Oltman wrote:
Axel,
I built lirc against the kernel source I downloaded from ATRPMs.
Shouldn't this be setup and ready to go with 4KSTACKS and match the
kernel I have installed already? I know these are nooB questions but
I am about as noob as they get with compiling. Thanks!
Instructions for setting up your kernel sources can be found in Fc3'
release notes. You will need to copy over the right .config file and
remove any EXTRAVERSION from the top Makefile.
On Wed, 16 Mar 2005 14:22:19 +0100, Axel Thimm [EMAIL PROTECTED] wrote:
On Tue, Mar 15, 2005 at 09:31:06PM -0600, Jim Oltman wrote:
lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be
'2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4'
Looks like you didn't build against a kernel source tree matching the
kernel you want to target. Unfortunatley that's an open issue with
RH's infrastructure for building external kmdls. Check the release
notes for how to get the kernel sources set up and also check the
kernel specfile for which steps are needed to configure/prepare the
kernel sources.
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
--
Axel.Thimm at ATrpms.net
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] Re: USB MCE IR Receiver
Axel, I built lirc against the kernel source I downloaded from ATRPMs. Shouldn't this be setup and ready to go with 4KSTACKS and match the kernel I have installed already? I know these are nooB questions but I am about as noob as they get with compiling. Thanks! On Wed, 16 Mar 2005 14:22:19 +0100, Axel Thimm [EMAIL PROTECTED] wrote: On Tue, Mar 15, 2005 at 09:31:06PM -0600, Jim Oltman wrote: lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4' Looks like you didn't build against a kernel source tree matching the kernel you want to target. Unfortunatley that's an open issue with RH's infrastructure for building external kmdls. Check the release notes for how to get the kernel sources set up and also check the kernel specfile for which steps are needed to configure/prepare the kernel sources. -- Axel.Thimm at ATrpms.net ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] record HDTV over Satellite is now possible?
Where is this written up at? On Wed, 16 Mar 2005 12:49:35 -0500, James Armstrong [EMAIL PROTECTED] wrote: Vincent K. Britton wrote: They are around $600 - $999. While that is expensive, its all relative when you consider that a DirecTV receiver with Tivo is $999. Vince Subject: Re: [mythtv-users] record HDTV over Satellite is now possible? There is a lot of information about these boxes at the avsforums. They're ridiculously expensive so I don't think anyone has tried them with Mythtv. Back when I was researching them (about a year ago) there were a lot of problems with them but they could be fixed by now. Tom FYI, they now have a 'do it yourself' kit for $399. You install and build you own processor cpu from old junk 486 computer. I have been thinking about it. Just need to save some money. - James ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Darren, Have you had any luck? I haven't had a chance to work on this tonight due to work. On Mon, 14 Mar 2005 22:58:13 -0700, Darren Richards [EMAIL PROTECTED] wrote: Ah, it all makes sense now. I hadn't read through the entire thread. Well, it looks as if I have enough information at my disposal to either get my new remote working, or really screw things up. Either way, I'm up for a challenge. Thanks, darren On Mon, 14 Mar 2005 21:19:40 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: The problem is the original source doesn't work with the newer MCE remotes. If you look for one of my previous posts, then you will see a newer lirc_mceusb.c attached that you will need to overwrite the existing file. Since I don't use Fedora Core, I can't tell you the best way to get it running. The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ After that you can either unload the lirc_mseusb and lirc_dev modules and reload them, or you can reboot your system let the modules be loaded at startup. (Assuming you have the appropriate entries in modules autoloading config file.) --- Darren Richards [EMAIL PROTECTED] wrote: I guess I don't understand... What's the point in recompiling from source if you're grabbing the same version that mythtv-suite installed? I thought the whole point was to install a new version whcih (hopefully) has support for my new fancy remote and IR receiver. By the way, have you noticed the range and directionality on that thing? From anywhere in the room, I can literally point the remote in any direction and have the light on the receiver light up. Once we get it to work, this thing will work *really* well. -darren On Mon, 14 Mar 2005 21:56:06 -0600, Jim Oltman [EMAIL PROTECTED] wrote: As I unserstand it, if you do that, you will damage the mythtv-suite install. I tried something similar when i was trying to install an older version of LIRC. It damaged the mythtv-suite install. I had to format my drive and start over. I think I might be able to get the lirc source from Axel's site. If I would have read far enough down the page, I would have seen the src rpm there. I think I can use the same rpm -i to get the source for that. But it is only a hunch. Am I close guys? On Mon, 14 Mar 2005 20:47:19 -0700, Darren Richards [EMAIL PROTECTED] wrote: Jim, Isn't there a way to uninstall the version of LIRC installed with mythtv? I'm not asking rhetorically, but because I really don't know. Couldn't you just do an apt-get remove LIRC? -darren On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman [EMAIL PROTECTED] wrote: If you are using ATRPMs to install mythtv, then lirc-lib is already installed. Since that is a certain version of LIRC that is used in that setup, if you get the wrong version of LIRC to compile, it won't work. That is why we need to know what version is on ATRPMs. I will email that list and try and find out.I just did, let's see who responds. Thanks! On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards [EMAIL PROTECTED] wrote: Andy, If there's an update in the source code that may make my new IR receiver work, I'll definitely try my hand at compiling LIRC. Your IR blaster walkthrough already saved the day for me once before, so I have high confidence... I'll let you know how it goes. Thanks, darren On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long [EMAIL PROTECTED] wrote: If you'd like to give compiling LIRC another chance, Pete and I have written a guide for doing it on FC3. It's directed at enabling more devices than 2 with LIRC (now not needed for ATRPMS due to a change a few days ago), but should be pretty straightforward. May be worth a shot if you'd like to try. http://lircsetup.com/lirc/trouble/kernsource.php -Andy On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards [EMAIL PROTECTED] wrote: My USB MCE remote just came in the mail today. I figured if there's a link to it from Jarod's guide, I should be able to get it working. Imagine my dismay when I started searching the archives and came across this thread. Jim, I'm in exactly the same boat as you. Even
[mythtv-users] Re: USB MCE IR Receiver
Yeah Axel, I noted in a later email that i should have scrolled further down the page. Nothing like a noob mistake to end a Monday. I am not really familiar with CVS or compiling which is why I was asking those questions about which version. My bad. I think i will be able to compile the current version with the MCE receiver fix (I hope). If not, then I get to format my frontendagain! Again, sorry for the mixup. Jim On Tue, 15 Mar 2005 20:00:09 +0100, Axel Thimm [EMAIL PROTECTED] wrote: On Mon, Mar 14, 2005 at 05:45:15PM -0600, Jim Oltman wrote: I just looked on ATRPMs website and there is no listing for getting the source code for the lirc drivers. Don't be impatient and just scroll to the bottom of the page ... There is also no mention of exactly what CVS version I am using (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, I have no idea. So, if there is no pre/cvs mark in the version/release, wouldn't it make sense to assume it is a release cut and no cvs/pre? Anyone know what version I could be running? I would LOVE to get this remote going so I could move on to bugging the list about other problems! :-) Thanks! I'd suggest checking with the lirc list for either a patch backported to 0.7.0 or a release for 0.7.1. On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666
Re: [mythtv-users] Re: USB MCE IR Receiver
Where does this deposit the new lirc_mceusb and lirc_dev modules? I have only found the old versions, I think. They say they were last modified on March 5th. Obviously, today is the 15th. snip From Joe Huffner The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ /snip This is not in my FC3 load. Can anyone tell me where these drivers ended up? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to fix it was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running tail -f /var/log/messages. Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: usb 2-2: bulk timeout on ep1in In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe --- Jim Oltman [EMAIL PROTECTED] wrote: After deleting the section in my rc.local about the mknod /dev/lirc0 c 61 0 and replacing it with: ln -s /dev/lircd /dev/lirc0 I am no longer getting errors from lircd in the /var/log/messages. IRW runs but I am not seeing anything when I press buttons on my Hauppauge remote (it has also been setup in the correct lircrc files). When I run irrecord I am getting errors about lircd not being started. I am going to try commenting out the other section in rc.local pertaining to MCEUSB and see what happens. On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61 lirc_mceusb After implementing these changes, I can do a cat /var/log/messages and see what I showed you before about the driver being loaded for the USB Microsoft IR Transceiver. But I also get this listed: Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on /dev/lircd Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal I am however getting errors on boot in the Show/Hide Details window. Where can I view the errors that it is showing me? They disappear to quickly to read. I am pretty sure the info I want to see (about the errors on boot in Show/Hide window) is not listed in /var/log/messages. On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson [EMAIL PROTECTED] wrote: On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: What I meant in that statement is that I got it to recognize the receiver in the /var/log/messages but it is still not working. Yes, but *how* did you get it to recognize the receiver? P.S. - Please do not erase the whole text of the email you are replying to. That makes it quite difficult to follow the thread. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID
Re: [mythtv-users] Re: USB MCE IR Receiver
BTW, I meant the compile that I did following the instructions located here: http://lircsetup.com/lirc/trouble/kernsource.php On Tue, 15 Mar 2005 20:13:29 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Where does this deposit the new lirc_mceusb and lirc_dev modules? I have only found the old versions, I think. They say they were last modified on March 5th. Obviously, today is the 15th. snip From Joe Huffner The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ /snip This is not in my FC3 load. Can anyone tell me where these drivers ended up? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to fix it was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running tail -f /var/log/messages. Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: usb 2-2: bulk timeout on ep1in In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe --- Jim Oltman [EMAIL PROTECTED] wrote: After deleting the section in my rc.local about the mknod /dev/lirc0 c 61 0 and replacing it with: ln -s /dev/lircd /dev/lirc0 I am no longer getting errors from lircd in the /var/log/messages. IRW runs but I am not seeing anything when I press buttons on my Hauppauge remote (it has also been setup in the correct lircrc files). When I run irrecord I am getting errors about lircd not being started. I am going to try commenting out the other section in rc.local pertaining to MCEUSB and see what happens. On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61 lirc_mceusb After implementing these changes, I can do a cat /var/log/messages and see what I showed you before about the driver being loaded for the USB Microsoft IR Transceiver. But I also get this listed: Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on /dev/lircd Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal I am however getting errors on boot in the Show/Hide Details window. Where can I view the errors that it is showing me? They disappear to quickly to read. I am pretty sure the info I want to see (about the errors on boot in Show/Hide window) is not listed in /var/log/messages. On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson [EMAIL PROTECTED] wrote: On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: What I meant in that statement is that I got it to recognize the receiver in the /var/log/messages but it is still not working. Yes
Re: [mythtv-users] Re: USB MCE IR Receiver
I re-ran this and instead of changing the MAX IRCTL devices, I left them as is. This then ran fine. I am about to try these modules to see if they work! On Tue, 15 Mar 2005 20:18:48 -0600, Jim Oltman [EMAIL PROTECTED] wrote: BTW, I meant the compile that I did following the instructions located here: http://lircsetup.com/lirc/trouble/kernsource.php On Tue, 15 Mar 2005 20:13:29 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Where does this deposit the new lirc_mceusb and lirc_dev modules? I have only found the old versions, I think. They say they were last modified on March 5th. Obviously, today is the 15th. snip From Joe Huffner The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ /snip This is not in my FC3 load. Can anyone tell me where these drivers ended up? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to fix it was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running tail -f /var/log/messages. Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: usb 2-2: bulk timeout on ep1in In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe --- Jim Oltman [EMAIL PROTECTED] wrote: After deleting the section in my rc.local about the mknod /dev/lirc0 c 61 0 and replacing it with: ln -s /dev/lircd /dev/lirc0 I am no longer getting errors from lircd in the /var/log/messages. IRW runs but I am not seeing anything when I press buttons on my Hauppauge remote (it has also been setup in the correct lircrc files). When I run irrecord I am getting errors about lircd not being started. I am going to try commenting out the other section in rc.local pertaining to MCEUSB and see what happens. On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61 lirc_mceusb After implementing these changes, I can do a cat /var/log/messages and see what I showed you before about the driver being loaded for the USB Microsoft IR Transceiver. But I also get this listed: Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on /dev/lircd Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal I am however getting errors on boot in the Show/Hide Details window. Where can I view the errors that it is showing me? They disappear to quickly to read. I am pretty sure the info I want to see (about the errors on boot in Show
Re: [mythtv-users] Re: USB MCE IR Receiver
I really hate to keep bugging people, but I am receiving an error in my /var/log/messages after I got the new lirc_dev and lirc_mceusb drivers put in the /lib/modules/2.6.10-1.770/updates/drivers/lirc (location of my other lirc drivers). Here is the error: lirc_dev: version magic '2.6.10-prep 686 REGPARM gcc-3.4' should be '2.6.10-1.770_FC3 686 REGPARM 4KSTACKS gcc-3.4' The version of the kernel I got for compiling came from ATRPMs: http://www.atrpms.net/dist/fc3/kernel/kernel-2.6.10-1.770_14.rhfc3.at.src.rpm.html This is obviously not the right file. Should I be grabbing the spec file instead of the RPM file? Any help would be appreciated. Thanks! On Tue, 15 Mar 2005 21:12:27 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I re-ran this and instead of changing the MAX IRCTL devices, I left them as is. This then ran fine. I am about to try these modules to see if they work! On Tue, 15 Mar 2005 20:18:48 -0600, Jim Oltman [EMAIL PROTECTED] wrote: BTW, I meant the compile that I did following the instructions located here: http://lircsetup.com/lirc/trouble/kernsource.php On Tue, 15 Mar 2005 20:13:29 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Where does this deposit the new lirc_mceusb and lirc_dev modules? I have only found the old versions, I think. They say they were last modified on March 5th. Obviously, today is the 15th. snip From Joe Huffner The easiest way would be to download version 0.7.0 of lirc from www.lirc.org, overwrite the lirc_mceusb.c file with the newer one, compile the new version, copy the new lirc_dev.ko and lirc_mceusb.ko over the existing lirc modules (Make sure to make a backup copy of the original module files). They should be located in /lib/modules/*your kernel version*/misc/ /snip This is not in my FC3 load. Can anyone tell me where these drivers ended up? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to fix it was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running tail -f /var/log/messages. Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: usb 2-2: bulk timeout on ep1in In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe --- Jim Oltman [EMAIL PROTECTED] wrote: After deleting the section in my rc.local about the mknod /dev/lirc0 c 61 0 and replacing it with: ln -s /dev/lircd /dev/lirc0 I am no longer getting errors from lircd in the /var/log/messages. IRW runs but I am not seeing anything when I press buttons on my Hauppauge remote (it has also been setup in the correct lircrc files). When I run irrecord I am getting errors about lircd not being started. I am going to try commenting out the other section in rc.local pertaining to MCEUSB and see what happens. On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61
Re: [mythtv-users] Shopping for an HDTV for Myth
How well does this frontend work for HD? It sounds like you are going to be selling these frontends. Do you have any writeups for setting up the software? Any special Myth gotchas? Jim On Mon, 14 Mar 2005 08:29:45 -0500, David George [EMAIL PROTECTED] wrote: On 3/12/2005 10:34 PM, Ron Johnson wrote: On Sat, 2005-03-12 at 22:27 -0500, john roberts wrote: I've helped several of my friends build MythTV boxes and they have many different makes/models of HDTV's. I would say the best HDTV I've seen so far has been the Samsung. Any particular model, or are all Samsungs good, like Sony used to be? My three year old Samsung rear projection can be a pain sometimes. It was very difficult to create a usable modeline for it[1] and the remote control is horrible (no longer a problem now that I have Myth :-) ). I have only heard *good* things about the DLPs though so they are probably better now. [1] I am using VGA out an nVidia FX5200 ultra with Audio Authority 9A60 -- David HDTV capable frontend I am working on (now with a picture) http://mythhd.info ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] The nvidia-settings tool and Myth (keeping overscan right)
I was kinda hoping not to have to do a modeline...it looks like that might be the only way. On Mon, 14 Mar 2005 08:56:13 -0500, Dewey Smolka [EMAIL PROTECTED] wrote: It took me a while to fix the screen size after I upgraded -- I accidentally lost all my original config files -- but I finally got the size right by tweaking the mode lines in XF86Config. Note: This is MythTV 0.17 from Knoppmyth R5V12. I'm using an Nvidia Geforce 2 with S-video out to the TV only. Before I added the extra mode lines, Myth would display to the TV at 800x600, leaving about 1 to 1.5 of unused space on the left and right sides of the screen. With these settings, the display reaches all the way to the right side of the screen and almost all the way to the left side without having to monkey around with nvtv or nvidia-settings. Here are the relevant lines from XF86Config-4: [I commented out the DDC-probed settings to prevent the system from going to 800x600. This may not be a necessary step. The lines that work are the ones under the Inserted from gossamer-threads comment.] Section Monitor Identifier Monitor0 Option DPMS true Option TVStandard NTSC-M Option ConnectedMonitor TV Option TVOutFormat SVIDEO Option NoLogo 1 Option TVOverScan 0.8 VendorName KDS ModelName KDS1983 HorizSync 30 - 50 # DDC-probed VertRefresh 60 # DDC-probed # TV fullscreen mode or DVD fullscreen output. # 768x576 @ 79 Hz, 50 kHz hsync ModeLine 768x576 50.00 768 832 846 1000 576 590 595 630 # 768x576 @ 100 Hz, 61.6 kHz hsync ModeLine 768x576 63.07 768 800 960 1024 576 578 590 616 # Inserted from gossamer-threads.com/lists/users/42881#42881 Modeline 720x576/50p 27.15 720 736 880 896 576 578 579 606 # 27 MHz, 3 0.3 kHz, 50.0 Hz Modeline 768x576/50p 29.09 768 792 936 960 576 578 579 606 # 29 MHz, 3 0.3 kHz, 50.0 Hz Modeline 800x600/50p 31.60 800 824 968 1000 600 602 603 632 # 32 MHz, 31.6 kHz, 50.0 Hz Modeline 1024x768/50p 44.80 1024 1056 1200 1280 768 770 772 808 # 45 M Hz, 35.0 kHz, 43.3 Hz Modeline 640x480/50p 20.20 640 656 800 800 480 482 483 505 # 20 MHz, 2 5.2 kHz, 50.0 Hz # These are the DDC-probed settings reported by your monitor. # 1600x1200, 75.0Hz; hfreq=93.75, vfreq=75.00 #ModeLine 1600x1200 202.50 1600 1664 1856 2160 1200 1201 1204 1250 + hsync +vsync # 1280x1024, 85.0Hz; hfreq=91.15, vfreq=85.02 #ModeLine 1280x1024 157.50 1280 1344 1504 1728 1024 1025 1028 1072 + hsync +vsync # 1152x864, 75.0Hz; hfreq=67.50, vfreq=75.00 #ModeLine 1152x864108.00 1152 1216 1344 1600 864 865 868 900 + hsync +vsync # 1024x768, 85.0Hz; hfreq=68.68, vfreq=85.00 #ModeLine 1024x768 94.50 1024 1072 1168 1376 768 769 772 808 + hsync +vsync # 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03 #ModeLine 1024x768 78.75 1024 1040 1136 1312 768 769 772 800 + hsync +vsync # 1024x768, 70.0Hz; hfreq=56.48, vfreq=70.07 #ModeLine 1024x768 75.00 1024 1048 1184 1328 768 771 777 806 - hsync -vsync # 800x600, 85.0Hz; hfreq=53.67, vfreq=85.06 #ModeLine 800x600 56.25 800 832 896 1048 600 601 604 631 + hsync +vsync # 800x600, 75.0Hz; hfreq=46.88, vfreq=75.00 #ModeLine 800x600 49.50 800 816 896 1056 600 601 604 625 + hsync +vsync # 800x600, 72.0Hz; hfreq=48.08, vfreq=72.19 #ModeLine 800x600 50.00 800 856 976 1040 600 637 643 666 + hsync +vsync # 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32 #ModeLine 800x600 40.00 800 840 968 1056 600 601 605 628 + hsync +vsync # 640x480, 85.0Hz; hfreq=43.27, vfreq=85.01 #ModeLine 640x480 36.00 640 696 752 832 480 481 484 509 - hsync -vsync # 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00 #ModeLine 640x480 31.50 640 656 720 840 480 481 484 500 - hsync -vsync # 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94 #ModeLine 640x480 25.17 640 648 744 784 480 482 484 509 - hsync -vsync EndSection [...] Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultColorDepth 24 SubSection Display Depth [each display subsection] Modes 640x480 EndSubSection ___ This has worked well for me, and seems a better solution than loading tweaks through scripts. If anyone wnats the full XF86Config-4 file, let me know On Mon, 14 Mar 2005 13:00:55 +, Neil Bird [EMAIL PROTECTED] wrote: Around about 08/03/05 17:21, Jim Oltman typed
Re: [mythtv-users] Mythvideo listing suddenly empty
How big does this DB-dump get?
On Mon, 14 Mar 2005 08:17:29 -0800, Ian Forde [EMAIL PROTECTED] wrote:
On Mon, 2005-03-14 at 07:25 +, David Morrison wrote:
After spending ages carefully entering all the information about my
videos into MythVideo, my videometadata table seems to have emptied
itself and lost everything. What logs can I look at to find out
how/when/why this might have happened?
Obviously, I'm not doing any backups otherwise I wouldn't be grumbling
so much :-)
Which is why I put this little gem into a script in /etc/cron.daily:
#!/bin/sh
datenow=`date +%Y%m%d`
mysqldump --opt mythconverg /var/lib/backups/mysqldump-${datenow}.sql
gzip -9 /var/lib/backups/mysqldump-${datenow}.sql
Make it executable, create the directory /var/lib/backups/ and you're
golden...
-I
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to fix it was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running tail -f /var/log/messages. Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: usb 2-2: bulk timeout on ep1in In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Shopping for an HDTV for Myth
How much did this system set you back, excluding the LED board. How did you get the IR sensor working off the motherboard? Do you have link for that? On Mon, 14 Mar 2005 12:21:40 -0500, David George [EMAIL PROTECTED] wrote: On 3/14/2005 11:13 AM, Jim Oltman wrote: How well does this frontend work for HD? Are you referring to the link in my sig? (Hard to tell because you didn't trim your quote to the relevant portion of the message you were replying to. :-( ) If so, I am still working on it. :-) I hope to have everything usable within a couple of weeks. It sounds like you are going to be selling these frontends. Thought about it at one time, but I don't think I could make them inexpensive enough for people to buy them from me. I am still thinking about possibly selling the LED boards and a pre-configured compact flash with Linux and Myth already setup for the technically challenged and for people that are just too busy to want to mess with it. Do you have any writeups for setting up the software? Any special Myth gotchas? Not yet. I am a horrible writer, so step-by-step instructions may never happen. As for gotchas the biggies are waiting for better CN400 support from the unichrome project (these guys are amazing, especially considering they get *no* help from VIA) and adding support for the VT1625 HDTV encoder. -- David HDTV capable frontend I am working on (now with a picture) http://mythhd.info ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] PVR-350 and MythTV recording quality sample
It really depends on your cable signal quality to begin with. My cable company really gives me crappy service in the lower channels (locals). When I get to the network stations, (TNT, TBS, Spike) it starts to look MUCH better. When I record M*A*S*H it looks fantastic. It's like the old saying, garbage in, garbage out. On Mon, 14 Mar 2005 11:29:18 -0600, Alex Cruz [EMAIL PROTECTED] wrote: Can somebody post somewhere (or point me to) an example TV recording using the PVR-350 and MythTV? Before I spend the $$ on one of these, I'd like to see what the combo is truly capable of. Thanks. -alex ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] looking for A7N8X-E sound advice
I bought the plug on ebay. Of course, I haven't used it yet. Here is
my modprobe.conf for my A7N8X-E DLX.
alias eth0 sk98lin
alias eth1 forcedeth
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0
/usr/sbin/alsactl restore /dev/null 21 || :
remove snd-intel8x0 { /usr/sbin/alsactl store /dev/null 21 || : ;
}; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
Instead of a .asound, I made an asound.conf and placed it in the /etc
directory. It works PERFECTLY for me. You just have to make sure to
specify the correct settings in MythFrontend for MythTV and for
MythMusic.
# Override the default output used by ALSA.
# If you do not override the default, your default
# device is identical to the (unmixed) analog device
# shown below. If you prefer mixed and/or digital
# output, uncomment the appropriate four lines below
# (only one slave.pcm line).
pcm.!default {
type plug
## Uncomment the following to use mixed analog by default
# slave.pcm dmix-analog
## Uncomment the following to use unmixed digital by default
slave.pcm digital-hw
## Uncomment the following to use mixed digital by default
# slave.pcm dmix-digital
}
# Alias for analog output on the nForce2 (hw:0,0)
# - This is identical to the device named default--which
# always exists and refers to hw:0,0 (unless overridden)
# - Therefore, we can specify hw:0,0, default, or analog
# to access analog output on the nForce2
pcm.analog {
type plug
slave.pcm analog-hw
}
# Control device (mixer, etc.) for the nForce2 card
ctl.analog {
type hw
card 0
}
# Alias for (rate-converted) mixed analog output on the
# nForce2 (hw:0,0)
# - This will accept audio input--regardless of rate--and
# convert to the rate required for the dmix plugin
# (in this case 48000Hz)
pcm.mixed-analog {
type plug
slave.pcm dmix-analog
}
# Control device (mixer, etc.) for the nForce2 card
ctl.mixed-analog {
type hw
card 0
}
# Alias for (rate-converted) digital (S/PDIF) output on the
# nForce2 (hw:0,2)
# - This will accept audio input--regardless of rate--and
# convert to the rate required for the S/PDIF hardware
# (in this case 48000Hz)
pcm.digital {
type plug
slave.pcm digital-hw
}
# Control device (mixer, etc.) for the nForce2 card
ctl.digital {
type hw
card 0
}
# Alias for mixed (rate-converted) digital (S/PDIF) output on the
# nForce2 (hw:0,2)
# - This will accept audio input--regardless of rate--and
# convert to the rate required for the S/PDIF hardware
# (in this case 48000Hz)
pcm.mixed-digital {
type plug
slave.pcm dmix-digital
}
# Control device (mixer, etc.) for the nForce2 card
ctl.mixed-digital {
type hw
card 0
}
# The following devices are not useful by themselves. They
# require specific rates, channels, and formats. Therefore,
# you probably do not want to use them directly. Instead use
# of of the devices defined above.
# Alias for analog output on the nForce2 (hw:0,0)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.analog-hw {
type hw
card 0
# The default value for device is 0, so no need to specify
}
# Control device (mixer, etc.) for the nForce2 card
ctl.analog-hw {
type hw
card 0
}
# Alias for digital (S/PDIF) output on the nForce2 (hw:0,2)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.digital-hw {
type hw
card 0
device 2
}
# Control device (mixer, etc.) for the nForce2 card
ctl.digital-hw {
type hw
card 0
}
# Direct software mixing plugin for analog output on
# the nForce2 (hw:0,0)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.dmix-analog {
type dmix
ipc_key 1234
slave {
pcm analog-hw
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
}
# Control device (mixer, etc.) for the nForce2 card
ctl.dmix-analog {
type hw
card 0
}
# Direct software mixing plugin for digital (S/PDIF) output
# on the nForce2 (hw:0,2)
# Do not use this directly--it requires specific rate,
# channels, and format
pcm.dmix-digital {
type dmix
ipc_key 1235
slave {
pcm digital-hw
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
}
# Control device (mixer, etc.) for the nForce2 card
ctl.dmix-digital {
type hw
card 0
}
In MythTVFrontend ---Setup for the audio device I put in ALSA:digital
(this is my default setting in the asound.conf above). For the mixer
device, I put in: default. For MythMusic setup I did the same thing,
ALSA:digital. I am not sitting in front of my machine right now or I
would have the exact menu structure down. Good luck!
On Mon, 14 Mar 2005 13:05:56 -0800, Reza Naima [EMAIL PROTECTED] wrote:
are you able to record and playback via the s/pdif connector? I know
that the record connector is a header on the motherboard itself,
thinking of just making an adaptor myself as I've no idea where I can
buy the special board that
Re: [mythtv-users] pchdtv3000 compile help
From what I understand ( i don't have an HDTV, so I might not be the best to listen to!), you can use the firewire output from your set top box to record the HD coming over cable (no need to worry about QAM) and use your PCHDTV 3000 card for OTA HD. Keep in mind that many set top boxes have a firewire output but they all aren't enabled. Search the mailing list to see if you can figure out if it is enabled or not. On Mon, 14 Mar 2005 16:18:16 -0500, Michael Haan [EMAIL PROTECTED] wrote: Somewhat related, I guess, so I thought I'd add it on. Having *just* gotten my myth box running this weekend, I'm looking ahead to adding hdtv capability. Someone mentioned that the pchdtv also supports QAM - so, does that mean that if i were to use it, I'd be able to tune my digital cable without the set top box? On Mon, 14 Mar 2005 10:35:45 -0800, Gregg [EMAIL PROTECTED] wrote: Yes I am running ivtv. I have these lines in my modprob.conf... alias tveeprom tveeprom-ivtv # ivtv modules setup alias char-major-81 videodev alias char-major-81-0 ivtv alias char-major-81-1 cx8800 install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install lirc_i2c Do I just remove the tveeprom line? I did a find but did not see a tveeprom specific to pcHDTV. Forgive me I am kinda new to this stuff. -Gregg Got ivtv also installed on that box, by chance? In my recent experience, that error is from using ivtv's tveeprom. The pcHDTV-provided tveeprom will work fine for most ivtv cards also, and should eliminate that error, so just use it instead. -- Jarod Wilson [EMAIL PROTECTED] Got a question? Read this first... http://catb.org/~esr/faqs/smart-questions.html MythTV, Fedora Core ATrpms documentation: http://wilsonet.com/mythtv/ MythTV Searchable Mailing List Archive http://www.gossamer-threads.com/lists/mythtv/ ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
I just looked on ATRPMs website and there is no listing for getting the source code for the lirc drivers. There is also no mention of exactly what CVS version I am using (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, I have no idea. Anyone know what version I could be running? I would LOVE to get this remote going so I could move on to bugging the list about other problems! :-) Thanks! On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. --- Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization
Re: [mythtv-users] DirecTV w/out serial port
www.tivocommunity.com Look for Serial Adapter. I don't have the exact specs on me right now, sorry. This cable worked for my DTivo Series 1 box. It could work for you! On Mon, 14 Mar 2005 17:26:27 -0800, Kelly [EMAIL PROTECTED] wrote: The port says RF Remote I have a HD Sat receiver from DirecTV made by Hughes and it has the same plug. The documentation for that box says it is for setting up a Remote Control antenna. So if anyone knows of a cable that goes from my 9pin serial box to this type of plug, I would be very grateful. kel On Mon, 14 Mar 2005 17:04:52 -0500, Mark L. Cukier [EMAIL PROTECTED] wrote: Kel: That plug on the back of your DirectTV may well be a serial port!!! The serial port on the back of my series 1 TiVo is the same thing... As for how to test that, I'm not sure but I'd be it's what you're looking for! (do you have the documentation for your Box?) - Mark Kelly wrote: I'm down to just a few issues while waiting for my HD-3000 card. Sound. Looks like I need a plug for my SAT receiver for RCA R/L out to a single or double(?) plug for the input on my SB sound card. Then I can see if I got sound working. Next, and the most disappointing, I seem to have the only DirecTV reciver w/out a friggin serial port. I have a plug that is the same as what is on my PVR-250 IR plug. So does this mean I need a IRBlaster to stick to the front of my SAT and the other end to my COM1? I have read that this makes changing channels have a 4 - 5 second delay. DirecTV Hughes Model GAEBO Kel ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- -- *Mark L. Cukier*, /Design Engineer/ PE Microcomputer Systems 710 Commonwealth Avenue Boston, MA 02215 _ e-mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone : (617) 353-9206 x19 fax : (617) 353-9205 _ visit us on the web at: http: //www.pemicro.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
After reading this tutorial, it seems that I could damage my current lirc install. Is this correct? I guess I could always save the lirc_mceusb file I need...and then re-install my entire frontend exactly the way I have it now (kernel and all). Not horrible I guess, considering I have done it several times. It still comes down to knowing which version of lirc to grab from the CVS snapshots. Any thoughts? On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long [EMAIL PROTECTED] wrote: If you'd like to give compiling LIRC another chance, Pete and I have written a guide for doing it on FC3. It's directed at enabling more devices than 2 with LIRC (now not needed for ATRPMS due to a change a few days ago), but should be pretty straightforward. May be worth a shot if you'd like to try. http://lircsetup.com/lirc/trouble/kernsource.php -Andy On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards [EMAIL PROTECTED] wrote: My USB MCE remote just came in the mail today. I figured if there's a link to it from Jarod's guide, I should be able to get it working. Imagine my dismay when I started searching the archives and came across this thread. Jim, I'm in exactly the same boat as you. Even if there was a magical fix in CVS, I've never successfully compiled anything in my life. I'm completely dependent upon apt-get and ATRPMS. Please, please keep us posted if you come up with anything. I'll start digging into this probably tomorrow, and maybe I'll have some luck... -darren On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I just looked on ATRPMs website and there is no listing for getting the source code for the lirc drivers. There is also no mention of exactly what CVS version I am using (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, I have no idea. Anyone know what version I could be running? I would LOVE to get this remote going so I could move on to bugging the list about other problems! :-) Thanks! On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. --- Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 23:04:11 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile
Re: [mythtv-users] Re: USB MCE IR Receiver
If you are using ATRPMs to install mythtv, then lirc-lib is already installed. Since that is a certain version of LIRC that is used in that setup, if you get the wrong version of LIRC to compile, it won't work. That is why we need to know what version is on ATRPMs. I will email that list and try and find out.I just did, let's see who responds. Thanks! On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards [EMAIL PROTECTED] wrote: Andy, If there's an update in the source code that may make my new IR receiver work, I'll definitely try my hand at compiling LIRC. Your IR blaster walkthrough already saved the day for me once before, so I have high confidence... I'll let you know how it goes. Thanks, darren On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long [EMAIL PROTECTED] wrote: If you'd like to give compiling LIRC another chance, Pete and I have written a guide for doing it on FC3. It's directed at enabling more devices than 2 with LIRC (now not needed for ATRPMS due to a change a few days ago), but should be pretty straightforward. May be worth a shot if you'd like to try. http://lircsetup.com/lirc/trouble/kernsource.php -Andy On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards [EMAIL PROTECTED] wrote: My USB MCE remote just came in the mail today. I figured if there's a link to it from Jarod's guide, I should be able to get it working. Imagine my dismay when I started searching the archives and came across this thread. Jim, I'm in exactly the same boat as you. Even if there was a magical fix in CVS, I've never successfully compiled anything in my life. I'm completely dependent upon apt-get and ATRPMS. Please, please keep us posted if you come up with anything. I'll start digging into this probably tomorrow, and maybe I'll have some luck... -darren On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I just looked on ATRPMs website and there is no listing for getting the source code for the lirc drivers. There is also no mention of exactly what CVS version I am using (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, I have no idea. Anyone know what version I could be running? I would LOVE to get this remote going so I could move on to bugging the list about other problems! :-) Thanks! On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. --- Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev
Re: [mythtv-users] Re: USB MCE IR Receiver
There is a lirc0.7.0_45.src RPM. Could I use the same command in your HOWTO that is used for the kernel source? rpm -i lirc-0.7.0-45.rhfc3.at.src.rpm ??? What do you think? Am I thinking correctly? On Mon, 14 Mar 2005 21:13:10 -0600, Jim Oltman [EMAIL PROTECTED] wrote: If you are using ATRPMs to install mythtv, then lirc-lib is already installed. Since that is a certain version of LIRC that is used in that setup, if you get the wrong version of LIRC to compile, it won't work. That is why we need to know what version is on ATRPMs. I will email that list and try and find out.I just did, let's see who responds. Thanks! On Mon, 14 Mar 2005 19:57:11 -0700, Darren Richards [EMAIL PROTECTED] wrote: Andy, If there's an update in the source code that may make my new IR receiver work, I'll definitely try my hand at compiling LIRC. Your IR blaster walkthrough already saved the day for me once before, so I have high confidence... I'll let you know how it goes. Thanks, darren On Mon, 14 Mar 2005 20:28:00 -0600, Andy Long [EMAIL PROTECTED] wrote: If you'd like to give compiling LIRC another chance, Pete and I have written a guide for doing it on FC3. It's directed at enabling more devices than 2 with LIRC (now not needed for ATRPMS due to a change a few days ago), but should be pretty straightforward. May be worth a shot if you'd like to try. http://lircsetup.com/lirc/trouble/kernsource.php -Andy On Mon, 14 Mar 2005 19:01:33 -0700, Darren Richards [EMAIL PROTECTED] wrote: My USB MCE remote just came in the mail today. I figured if there's a link to it from Jarod's guide, I should be able to get it working. Imagine my dismay when I started searching the archives and came across this thread. Jim, I'm in exactly the same boat as you. Even if there was a magical fix in CVS, I've never successfully compiled anything in my life. I'm completely dependent upon apt-get and ATRPMS. Please, please keep us posted if you come up with anything. I'll start digging into this probably tomorrow, and maybe I'll have some luck... -darren On Mon, 14 Mar 2005 17:45:15 -0600, Jim Oltman [EMAIL PROTECTED] wrote: I just looked on ATRPMs website and there is no listing for getting the source code for the lirc drivers. There is also no mention of exactly what CVS version I am using (0.7.0pre 4 or 5 or 6 or 7 or 8). I know that I have lirc 0.7.0-45 from ATRPMs but other than that, I have no idea. Anyone know what version I could be running? I would LOVE to get this remote going so I could move on to bugging the list about other problems! :-) Thanks! On Mon, 14 Mar 2005 14:44:10 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Unless ATRPMS have been updated, then the only way to get this to work would be to compile the drivers. My guess is that these drivers will be updated in the not-too-distant-future, but exactly when that happens is up to the lirc maintainers. Then the RPMS will have to be udpated as well. Something you can try is to leave your current lirc installed. 1. Download the same version you have installed. 2. Copy the the previously attached source code to the appropriate place. 3. Configure and compile source. 4. Copy the new lirc_mceusb and lirc_dev modules over the existing files. (After making a backup of the originals of course.) 5. Unload the modules, then load the new modules. (Or reboot for the easiest way.) About your questions concerning my modprobe.conf and what not. I don't have anything currently in their except ethernet and video. Since my remote wasn't working with lirc yet, there was no reason to put anything in there. Also, I am running gentoo, so I don't know the exact format of the modprobe.conf file, but my guess is you would just want the module name you would want to load. In this case it would just be lirc_mceusb, all the other modules required by lirc should be loaded. --- Jim Oltman [EMAIL PROTECTED] wrote: Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc
Re: [mythtv-users] Re: USB MCE IR Receiver
So you didn't have to mess with any /dev/ttyUSB0 stuff? I am gonna cross my fingers and hope that this will work too. On Sun, 13 Mar 2005 12:00:42 -0800, Jarod Wilson [EMAIL PROTECTED] wrote: On Sunday 13 March 2005 10:48, Jim Oltman wrote: Has anyone had any luck getting this IR Receiver to work? I know that Jared has, but someone else has GOT to be using it too. I believe there were some hardware changes somewhere along the line, and so my relatively old MCE USB receiver Just Works with lirc, while some newer ones may not. Only theory I've got anyhow. My relevant modprobe.conf stuff is simply: alias char-major-61 lirc_mceusb On Sat, 12 Mar 2005 17:21:47 -0600, Jim Oltman [EMAIL PROTECTED] wrote: [...] # LIRC Setup alias char-major-188-0 usbserial options usbserial vendor=0x0471 product=0x0815 alias lirc0 lirc_mceusb install lirc_mceusb ;\ /sbin/modprobe --ignore-install lirc_mceusb [...] -- Jarod Wilson [EMAIL PROTECTED] Got a question? Read this first... http://catb.org/~esr/faqs/smart-questions.html MythTV, Fedora Core ATrpms documentation: http://wilsonet.com/mythtv/ MythTV Searchable Mailing List Archive http://www.gossamer-threads.com/lists/mythtv/ ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Well it didn't work. When I do a cat /var/log/messages | grep usb I get this:
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver usbfs
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver hub
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver hiddev
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver usbhid
Mar 13 15:21:21 mythfrontend kernel: drivers/usb/input/hid-core.c:
v2.0:USB HID core driver
Mar 13 15:21:21 mythfrontend kernel: usb 3-2: new full speed USB
device using ohci_hcd and address 2
At one point, I actually got the usb3-2 to attach to a device I made
called /dev/ttyUSB0 but nothing after that. Here is my modprobe.conf:
alias eth0 sk98lin
alias eth1 forcedeth
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0
/usr/sbin/alsactl restore /dev/null 21 || :
remove snd-intel8x0 { /usr/sbin/alsactl store /dev/null 21 || : ;
}; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
# nvidia kernel module
alias char-major-195 nvidia-1_0-6629
# LIRC Setup
alias char-major-61 lirc_mceusb
#Per Jared's instructions
#alias char-major-188-0 usbserial
#options usbserial vendor=0x0471 product=0x0815
#alias ttyUSB0 lirc_mceusb
#install lirc_mceusb /sbin/modprobe lirc
# /sbin/modprobe --ignore-install lirc_mceusb
There has got to be a way to get this working. Any ideas? Can I
provide anymore information?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Can someone tell me what this means in my /var/log/messages?
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: accepted new client on
/dev/lircd
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: could not get file
information for /dev/lirc
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: default_init(): No
such file or directory
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: caught signal
On Sun, 13 Mar 2005 15:37:28 -0600, Jim Oltman [EMAIL PROTECTED] wrote:
Well it didn't work. When I do a cat /var/log/messages | grep usb I get this:
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver usbfs
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver hub
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver hiddev
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver usbhid
Mar 13 15:21:21 mythfrontend kernel: drivers/usb/input/hid-core.c:
v2.0:USB HID core driver
Mar 13 15:21:21 mythfrontend kernel: usb 3-2: new full speed USB
device using ohci_hcd and address 2
At one point, I actually got the usb3-2 to attach to a device I made
called /dev/ttyUSB0 but nothing after that. Here is my modprobe.conf:
alias eth0 sk98lin
alias eth1 forcedeth
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0
/usr/sbin/alsactl restore /dev/null 21 || :
remove snd-intel8x0 { /usr/sbin/alsactl store /dev/null 21 || : ;
}; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
# nvidia kernel module
alias char-major-195 nvidia-1_0-6629
# LIRC Setup
alias char-major-61 lirc_mceusb
#Per Jared's instructions
#alias char-major-188-0 usbserial
#options usbserial vendor=0x0471 product=0x0815
#alias ttyUSB0 lirc_mceusb
#install lirc_mceusb /sbin/modprobe lirc
# /sbin/modprobe --ignore-install lirc_mceusb
There has got to be a way to get this working. Any ideas? Can I
provide anymore information?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
OK. I got my box to recognize the IR receiver. Now what? Here is my
/var/log/messages pertaining to lirc:
Mar 13 17:26:30 mythfrontend kernel: lirc_dev: IR Remote Control
driver registered, at major 61
Mar 13 17:26:30 mythfrontend kernel: usbcore: registered new driver lirc_mceusb
Mar 13 17:26:30 mythfrontend kernel:
/var/tmp/bach-build/BUILD/lirc-0.7.0/drivers/lirc_mceusb/lirc_mceusb.c:
USB Microsoft IR Transceiver Driver v0.2
Mar 13 17:26:33 mythfrontend gdm-autologin(pam_unix)[4734]: session
opened for user mythtv by (uid=0)
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: accepted new client on
/dev/lircd
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: could not get file
information for /dev/lirc
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: default_init(): No
such file or directory
Mar 13 17:26:42 mythfrontend lircd 0.7.0[4134]: caught signal
On Sun, 13 Mar 2005 17:12:58 -0600, Jim Oltman [EMAIL PROTECTED] wrote:
Can someone tell me what this means in my /var/log/messages?
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: accepted new client on
/dev/lircd
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: could not get file
information for /dev/lirc
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: default_init(): No
such file or directory
Mar 13 17:03:08 mythfrontend lircd 0.7.0[4135]: caught signal
On Sun, 13 Mar 2005 15:37:28 -0600, Jim Oltman [EMAIL PROTECTED] wrote:
Well it didn't work. When I do a cat /var/log/messages | grep usb I get
this:
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver usbfs
Mar 13 15:21:18 mythfrontend kernel: usbcore: registered new driver hub
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver hiddev
Mar 13 15:21:21 mythfrontend kernel: usbcore: registered new driver usbhid
Mar 13 15:21:21 mythfrontend kernel: drivers/usb/input/hid-core.c:
v2.0:USB HID core driver
Mar 13 15:21:21 mythfrontend kernel: usb 3-2: new full speed USB
device using ohci_hcd and address 2
At one point, I actually got the usb3-2 to attach to a device I made
called /dev/ttyUSB0 but nothing after that. Here is my modprobe.conf:
alias eth0 sk98lin
alias eth1 forcedeth
alias snd-card-0 snd-intel8x0
options snd-card-0 index=0
install snd-intel8x0 /sbin/modprobe --ignore-install snd-intel8x0
/usr/sbin/alsactl restore /dev/null 21 || :
remove snd-intel8x0 { /usr/sbin/alsactl store /dev/null 21 || : ;
}; /sbin/modprobe -r --ignore-remove snd-intel8x0
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
# nvidia kernel module
alias char-major-195 nvidia-1_0-6629
# LIRC Setup
alias char-major-61 lirc_mceusb
#Per Jared's instructions
#alias char-major-188-0 usbserial
#options usbserial vendor=0x0471 product=0x0815
#alias ttyUSB0 lirc_mceusb
#install lirc_mceusb /sbin/modprobe lirc
# /sbin/modprobe --ignore-install lirc_mceusb
There has got to be a way to get this working. Any ideas? Can I
provide anymore information?
___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
What I meant in that statement is that I got it to recognize the receiver in the /var/log/messages but it is still not working. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61 lirc_mceusb After implementing these changes, I can do a cat /var/log/messages and see what I showed you before about the driver being loaded for the USB Microsoft IR Transceiver. But I also get this listed: Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on /dev/lircd Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal I am however getting errors on boot in the Show/Hide Details window. Where can I view the errors that it is showing me? They disappear to quickly to read. I am pretty sure the info I want to see (about the errors on boot in Show/Hide window) is not listed in /var/log/messages. On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson [EMAIL PROTECTED] wrote: On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: What I meant in that statement is that I got it to recognize the receiver in the /var/log/messages but it is still not working. Yes, but *how* did you get it to recognize the receiver? P.S. - Please do not erase the whole text of the email you are replying to. That makes it quite difficult to follow the thread. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. Legality/morality of using open wireless points: If I leave my door unlocked are you going to come into my house in the middle of the night because you need to use the restroom? I pay a fixed rate for water. It's cold water so there is no electricity usage. No financial loss. I have 2.5 bathrooms, so no loss of usage on my end. Is this OK? Please, try this and we'll see if it's OK. http://www.warchalking.org/comments/2002/9/22/223831/236/135 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Re: USB MCE IR Receiver
After deleting the section in my rc.local about the mknod /dev/lirc0 c 61 0 and replacing it with: ln -s /dev/lircd /dev/lirc0 I am no longer getting errors from lircd in the /var/log/messages. IRW runs but I am not seeing anything when I press buttons on my Hauppauge remote (it has also been setup in the correct lircrc files). When I run irrecord I am getting errors about lircd not being started. I am going to try commenting out the other section in rc.local pertaining to MCEUSB and see what happens. On Sun, 13 Mar 2005 18:57:27 -0600, Jim Oltman [EMAIL PROTECTED] wrote: Here is where I am at so far. In my /etc/rc.d/rc.local I made these changes... #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff. touch /var/lock/subsys/local mknod /dev/lirc0 c 61 0 -I added this line in hopes it would attach to a line in my modprobe /usr/X11R6/bin/xset -dpms /usr/X11R6/bin/xset s off /usr/bin/mtd --daemon # I added these next two lines /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd In my /etc/modprobe.conf I have added this line: alias char-major-61 lirc_mceusb After implementing these changes, I can do a cat /var/log/messages and see what I showed you before about the driver being loaded for the USB Microsoft IR Transceiver. But I also get this listed: Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: accepted new client on /dev/lircd Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: could not open /dev/lirc0 Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: default_init(): No such device Mar 13 18:54:11 mythfrontend lircd 0.7.0[4134]: caught signal I am however getting errors on boot in the Show/Hide Details window. Where can I view the errors that it is showing me? They disappear to quickly to read. I am pretty sure the info I want to see (about the errors on boot in Show/Hide window) is not listed in /var/log/messages. On Sun, 13 Mar 2005 18:38:09 -0600, Ron Johnson [EMAIL PROTECTED] wrote: On Sun, 2005-03-13 at 17:58 -0600, Jim Oltman wrote: What I meant in that statement is that I got it to recognize the receiver in the /var/log/messages but it is still not working. Yes, but *how* did you get it to recognize the receiver? P.S. - Please do not erase the whole text of the email you are replying to. That makes it quite difficult to follow the thread. -- - Ron Johnson, Jr. Jefferson, LA USA PGP Key ID 8834C06B I prefer encrypted mail. Legality/morality of using open wireless points: If I leave my door unlocked are you going to come into my house in the middle of the night because you need to use the restroom? I pay a fixed rate for water. It's cold water so there is no electricity usage. No financial loss. I have 2.5 bathrooms, so no loss of usage on my end. Is this OK? Please, try this and we'll see if it's OK. http://www.warchalking.org/comments/2002/9/22/223831/236/135 ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Fwd: [mythtv-users] Re: USB MCE IR Receiver
Since I used apt-get to install lirc and mythtv-suite, I take it that is would be EXTREMELY difficult for me to compile this new driver into lirc especially since I have never compiled anything in my entire life (except for those 2 semesters in college compiling C code that barely worked). As I understand it, mythtv-suite already has the lirc-lib included. Is there a way around all this? Does anyone know? My version of the mce_usb driver is listed as v0.2 but doesn't mention anything about this Dan Conti. Also, on ATRPMs it looks like Axel last updated the lirc drivers on Mar 5th 12:27 CET. Could you tell me how you were able to get your MCE IR receiver up and working (assuming I have the right driver). What did you put in your /etc/modprobe.conf? I didn't have a /dev/lirc0 only a /dev/lircd so in my rc.local I put these statements in: ln -s /dev/lircd /dev/lirc0 chmod 666 /dev/lirc0 /sbin/modprobe lirc_mceusb /usr/sbin/lircd --device=/dev/lirc0 --output=/dev/lircd Am I incorrect? Should I be doing something different? Thanks! On Sun, 13 Mar 2005 20:20:20 -0800 (PST), Joe Huffner [EMAIL PROTECTED] wrote: Just an FYI for those of us who bought one of the updated MCE remotes and receivers. I was checking out the lirc mailing list and someone has update the driver to include support. From what I can tell the update has not been updated in CVS. I found the info at: http://search.gmane.org/?query=mcegroup=gmane.comp.hardware.lirc Basically what I did was overwrite the lirc_mceusb.c in the drivers/lirc_mceusb directory with the source found in the mailing liste. (I have attached the new source file.) Then went through the install process documented. I used version .7.0 of lirc. Please note, from what I have read and experienced, there are some initialization problems. What seemed to fix it was unplugging the receiver and plugging it back in, until I no longer got an error message stating the device did not initialize. You can check this by running tail -f /var/log/messages. Also, I read that running kernel 2.6.11 seemed to fix the initialization problem. However I cannot confirm this as I am running Gentoo Dev Kernel 2.6.9-r9. Another problem I am having is that I am getting non-stop error messages stating: usb 2-2: bulk timeout on ep1in In fact, I was getting about 4 of those messages per second. If/when I get time I am planning to upgrade to 2.6.11 to see if this fixes the issue. -joe ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
[mythtv-users] USB MCE IR Receiver
My last post was about this very same thing, but I wasn't specific enough and I caused a very nice person, Martin, to spend an aweful lot of time helping me out. Apologies again! Getting down to it. When I boot with the MCE USB receiver plugged in, cat /var/log/messages | grep usb gives me this output: Mar 12 11:36:41 mythfrontend kernel: usbcore: registered new driver usbfs Mar 12 11:36:41 mythfrontend kernel: usbcore: registered new driver hub Mar 12 11:36:44 mythfrontend kernel: usbcore: registered new driver hiddev Mar 12 11:36:44 mythfrontend kernel: usbcore: registered new driver usbhid Mar 12 11:36:44 mythfrontend kernel: drivers/usb/input/hid-core.c: v2.0:USB HID core driver Mar 12 11:36:45 mythfrontend kernel: usb 3-2: new full speed USB device using ohci_hcd and address 2 I am not sure what settings to put in my modprobe.conf and if I need to edit lircd in /etc/rc.d/init.d/ or not. Here is the pertinent part of my modprobe.conf after I followed some directions at FedoraForum.org (http://fedoraforum.org/forum/showthread.php?t=27829highlight=ttyUSB0): # LIRC Setup alias char-major-188-0 usbserial options usbserial vendor=0x0471 product=0x0815 alias lirc0 lirc_mceusb install lirc_mceusb ;\ /sbin/modprobe --ignore-install lirc_mceusb Can anyone please point me in the right direction? What am I doing wrong? Here are my system stats: Frontend System: 2500+ Athlon 512MB PC2700 RAM Asus A7N8X-E DLX Mobo Chaintech FX5200 128MB RAM DVD+R drive, Floppy drive MCE USB IR Receiver/Blaster Using Jarod's Guide FC3 running vanilla 2.6.10_770 kernel APT-GET all components (lirc, nvidia drivers, mythtv-suite, etc all done on 3-11-05) Thanks to Jarod for his wonderful guide. Because of him I had a great Mythbox going for months. And thanks to me for mucking it up!! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Is mythTV ready for prime time?
I completely agree. MythTV is a fantastic app, but can be a pain in the rear to get up and working. I have to say that without Jared Wilson's guide (www.wilsonet.com), I would not be the happy MythTV user I am today. His site convinced me to start using Myth in the first place. I had never really tinkered in Linux before that but this program will really make you work. If you really want to get Myth up and working, I suggest following his guide. It is near fool-proof. There are some things here or there (USB MCE IR receivers for one) that aren't included yet, but this mailing list really helps out. Keep at it, and I am sure you will be as happy as we all are. On Sat, 12 Mar 2005 16:29:00 -0900, jonr [EMAIL PROTECTED] wrote: Justin Gombos wrote: After fighting with database issues on Suse 9.1, I switched to KnoppMyth, which supposedly auto-installs all the prereqs and sets up the database. Yet it cannot connect to the master backend database. I'm throwing in the towel. Looking at the archives of this list, it appears that this tool is still packed with gotchas, one complication after another. Does anyone else share the same thoughts, or am I just having unusual difficulties? My first attempt to install myth was using Jarods guide w/ FC2,pvr350, amd1800XP and nvidia geforce2. When I got to the end of the guide I had myth running...almost. :) I had to change the ivtv driver because of A/V synch problems but thats not a myth problem. Try that route and see if your luck changes. Jon ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Shopping for an HDTV for Myth
AVS Forums would be your best bet. They can tell you EVERYTHING you EVER wanted to know about HDTVs and some things you wish that NO human being would know. On Sat, 12 Mar 2005 22:27:04 -0500, john roberts [EMAIL PROTECTED] wrote: I've helped several of my friends build MythTV boxes and they have many different makes/models of HDTV's. I would say the best HDTV I've seen so far has been the Samsung. -John - Original Message - From: Jack Heneghan [EMAIL PROTECTED] To: [EMAIL PROTECTED], Discussion about mythtv mythtv-users@mythtv.org Subject: Re: [mythtv-users] Shopping for an HDTV for Myth Date: Sat, 12 Mar 2005 18:10:04 -0700 I have a Samsung DLP with DVI and VGA interfaces along with a number of Component, S-video and composite inputs. I am still in the process of acquiring the mythTV components , but I have used it as a PC monitor and it works very well. A 50 monitor can be a bit overwhelming , the wireless keyboard certainly helps. JCH Moasat wrote: I have an MX4000 but I may upgrade that to something with DVI. I'm wondering if any users that have a working HDTV/Myth setup could offer any pointers for buying a nice HDTV. I currently have a Hitachi that never really played well with Myth and my AA VGA to YUV converter. (Never could get a good modeline that wasn't either off-center of too large or small to fit on screen.) What brands/technologies seem to work the best and look good as well. I'm thinking of getting a DLP based TV unless someone has had a super bad experience. Thanks for any help, Mike ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- ___ NEW! Lycos Dating Search. The only place to search multiple dating sites at once. http://datingsearch.lycos.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] Is mythTV ready for prime time?
I feel I have to respond to this. I had a DirecTivo. It was 100 times easier to setup than Myth ever was. That is not to say that Myth isn't 1000 times better than TiVo. Myth has so many more functions. I completely agree with Rob here. Tivo is cool...but it is like a gateway drug. It will definately lead you into harsher distros. I can't praise Myth enough. Excellent work! On Sat, 12 Mar 2005 23:36:53 -0600, Rob Nichols [EMAIL PROTECTED] wrote: On Sat, Mar 12, 2005 at 06:07:19PM -0700, Justin Gombos wrote: [snip] I'm throwing in the towel. Looking at the archives of this list, it appears that this tool is still packed with gotchas, one complication after another. Does anyone else share the same thoughts, or am I just having unusual difficulties? I built a gentoo box about a year ago. I think it took me about a week to get everything setup, working a couple hours a day. I was fairly new to gentoo, so that accounted for some of that time (but very experienced with linux). I believe it is getting easier to install, but really can't be a good judge of such things. So it took some time, but I learned a lot. It was all worth it. MythTV is just unbelievably cool. I never had a TiVo, but talking with TiVo friends I think MythTV is quite a bit cooler than TiVo. Yes, it's also probably more money and definitely more work than TiVo. Anyway... any setup troubles were worth it to me! I hope you get yours sorted out and working. Once you do you can never go back to normal TV. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] HELP about TV output
I have followed Jarod's guide as best i could. In his guide he says to setup the XORG.CONF file to have the monitor (TV in my case) use DPMS. Then use the xset command to turn off DPMS for your monitor. I was having the same issue, and I went into the XORG.CONF file and commented out (#) the line for DPMS in the MONITOR settings. It doesn't go to a blank screen anymore. On Fri, 11 Mar 2005 09:38:15 -0600, Ashu Desai [EMAIL PROTECTED] wrote: I have tried using the xvidtuner but it doesn't seem to be permanent. It kinds of resets itself after a few hours and also when I reboot. Anyway to solve this?? Also, how in the world do I remove the screen from going blank when there's no activity? I want the screen to remain as it is... Thanks Ash. On Mon, 7 Mar 2005 23:47:13 -0500, Robin Smith [EMAIL PROTECTED] wrote: If the blue line is just when watching recorded programs/live TV, you may find the best adjustment is the MythTV overscan (Setup TV Settings Playback). I have mine overscanning by 2 in both directions and offset by -1 in both directions. I also tweaked my MythTV GUI with a custom GUI size/position in Setup Appearance and have Use GUI Size for TV playback set to On. It took some trial and error, but things are sweet now. Robin On Mon, 7 Mar 2005 11:08:06 -0800, Jarod Wilson [EMAIL PROTECTED] wrote: On Monday 07 March 2005 05:44, Ashu Desai wrote: Hi, I tried what you said, it didn't work. So I thought I should try with the highest number 1 and then go down as needed. That didn't work either. The blue line remains there. I even tried to reboot after the changes, thinking that maybe that's where the problem is. It's like nothing works!!! Also, this is only when watching TV or recordings. If I go to weather or system info or the main menu, the blue line isn't there...(if this helps anyone) Use nvidia-settings to adjust your overscan. On Sat, 05 Mar 2005 16:10:56 -0500, Calvin Harrigan [EMAIL PROTECTED] wrote: Ashu Desai wrote: Hi, I did the overscan option. I went for TVOverScan upto 5.5, but nothing happened!!! Thanks in advance for your help. --a-- On Fri, 04 Mar 2005 11:29:30 -0500, Calvin Harrigan [EMAIL PROTECTED] wrote: Ashu Desai wrote: Hello guys, A newbie here. I wrote a couple of weeks back, and although a few guys tried to help me, it didnt work. My appeal again: I am running pvr-250 (980) on a P3-650 Mhz-640 Mb RAM computer. When I watch TV or the recording (since it's going to record the way it comes on TV), I get a blue line on the left side the the upper side. Someone suggested xattr thing with an at the end; but that didn't work. Someone also suggested modifying the /usr/bin/nVidia-Settings-1.0-6629 file but that didn't work either. I am at at brickwall now. Nothing works and I hate watching my myth tv now with that bar SOMEONE PLEASE HELP!!! Any help is appreciated as always... Thanks, Ash. -- -- ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users What nvidia chipset does you setup use? If it's geforce 4 or greater, use the overscan option in the xorg.conf file. For example: Section Device Identifier Videocard0 Driver nvidia VendorName Chaintech BoardName nVidia GeForce 4 MX 440 Option RenderAccel 1 # TV Out Setup Option TVStandard NTSC-M Option TVOutFormat SVIDEO Option TVOverScan 0.5 EndSection Increase the value by .05 until the lines disappears. Calvin... 5.5 is not a valid value, 0.55 is. Perhaps that's what you mean? If it didn't work try .85 and see if there is any change. Valid values are between 0.0-1.0 -- Jarod Wilson [EMAIL PROTECTED] Got a question? Read this first... http://catb.org/~esr/faqs/smart-questions.html MythTV, Fedora Core ATrpms documentation: http://wilsonet.com/mythtv/ MythTV Searchable Mailing List Archive http://www.gossamer-threads.com/lists/mythtv/ ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org
Re: [mythtv-users] dvd playback on pvr 350
Does XINE use a zoom command? On Fri, 11 Mar 2005 15:14:14 -0500, John Kuhn [EMAIL PROTECTED] wrote: Rick Ingersoll wrote: I just got my box working using the pvr-350 for x and using the decoder for tv playback. I used jarod's guide for setting it up. What parameters do I need to make the xine or mplayer to use the pvr 350. I know I can set x11, but last time I did that, it did not fill the whole screen and it tried to playback the directors audio track. What should I be using and what are the command line parameters Thanks, Rick ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users I believe you need to add the -zoom command --John ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] USB IR Receiver
Here I go again sounding like an idiot. I have no idea how to do that. But from what it sounds like, I am going to have to uninstall LIRC via apt, then grab the source for LIRC...and patch that somehow...and then compile it all the while crossing my fingers hoping it works. Correct? Anywhere you could point me to start the process? On Wed, 9 Mar 2005 10:24:53 -0700, Vladimir Shved [EMAIL PROTECTED] wrote: There are no known packages that work with USB UIRT out of the box, you have to compile LIRC by yourself. -Original Message- From: [EMAIL PROTECTED] [mailto:mythtv-users- [EMAIL PROTECTED] On Behalf Of Jim Oltman Sent: Wednesday, March 09, 2005 10:20 AM To: Discussion about mythtv Subject: Re: [mythtv-users] USB IR Receiver These are the lines from Jarod's Guide I am using to grab lirc: # apt-get install lirc-kmdl-$KVER # apt-get install lirc So you are saying there is a specific lirc-kmdl... for USB? I can start the LIRC daemon without problems...but I really need to know how to setup the USB receiver and where I should get these packages from. Thanks! On Tue, 8 Mar 2005 11:11:31 -0700, Vladimir Shved [EMAIL PROTECTED] wrote: You don't need any LIRC modules, lirc_serial is for com port IR devices, you need kernel driver module(forgot its name) for USB UIRT and actual LIRC daemon(lircd) needs to start on startup(need script in /etc/init.d and link to it like from /etc/rc2.d etc.). Actual LIRC must have USB UIRT support, you need to build LIRC from sources, I'm not sure if there are any binaries exists that support USB UIRT. When building from sources, either you need patch or get latest CVS sources. I did not try CVS but I've read somewhere that USB UIRT made to CVS, so it has to be supported. Check USB UIRT support forums, LIRC mail list for more info. -Original Message- From: [EMAIL PROTECTED] [mailto:mythtv-users- [EMAIL PROTECTED] On Behalf Of Jim Oltman Sent: Tuesday, March 08, 2005 10:57 AM To: Discussion about mythtv Subject: Re: [mythtv-users] USB IR Receiver But what are the lines that I will need in my modprobe.conf? This is what I have so far in it (from Jarod's guide) alias char-major-61 lirc_serial options lirc_serial irq=4 io=0x3f8 install lirc_serial /bin/setserial /dev/ttyS0 uart none ;\ /sbin/modprobe --ignore-install lirc_serial Instead of lirc_serial, will it be lirc_usb? I have no idea. Thanks! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] USB IR Receiver
Great. Thanks Vlad! On Wed, 9 Mar 2005 10:36:38 -0700, Vladimir Shved [EMAIL PROTECTED] wrote: Check USB UIRT support forums in Dev section and LIRC mail list for help on that. LIRCs documenation has instructions on how to compile it. USB UIRT forums: http://166.70.183.44/phpBB2/ LIRC Documentation: http://www.lirc.org/html/index.html LIRC mail list sign up here: http://lists.sourceforge.net/lists/listinfo/lirc-list LIRC mail list archives: http://sourceforge.net/mailarchive/forum.php?forum=lirc-list -Original Message- From: [EMAIL PROTECTED] [mailto:mythtv-users- [EMAIL PROTECTED] On Behalf Of Jim Oltman Sent: Wednesday, March 09, 2005 10:28 AM To: Discussion about mythtv Subject: Re: [mythtv-users] USB IR Receiver Here I go again sounding like an idiot. I have no idea how to do that. But from what it sounds like, I am going to have to uninstall LIRC via apt, then grab the source for LIRC...and patch that somehow...and then compile it all the while crossing my fingers hoping it works. Correct? Anywhere you could point me to start the process? On Wed, 9 Mar 2005 10:24:53 -0700, Vladimir Shved [EMAIL PROTECTED] wrote: There are no known packages that work with USB UIRT out of the box, you have to compile LIRC by yourself. -Original Message- From: [EMAIL PROTECTED] [mailto:mythtv-users- [EMAIL PROTECTED] On Behalf Of Jim Oltman Sent: Wednesday, March 09, 2005 10:20 AM To: Discussion about mythtv Subject: Re: [mythtv-users] USB IR Receiver These are the lines from Jarod's Guide I am using to grab lirc: # apt-get install lirc-kmdl-$KVER # apt-get install lirc So you are saying there is a specific lirc-kmdl... for USB? I can start the LIRC daemon without problems...but I really need to know how to setup the USB receiver and where I should get these packages from. Thanks! On Tue, 8 Mar 2005 11:11:31 -0700, Vladimir Shved [EMAIL PROTECTED] wrote: You don't need any LIRC modules, lirc_serial is for com port IR devices, you need kernel driver module(forgot its name) for USB UIRT and actual LIRC daemon(lircd) needs to start on startup(need script in /etc/init.d and link to it like from /etc/rc2.d etc.). Actual LIRC must have USB UIRT support, you need to build LIRC from sources, I'm not sure if there are any binaries exists that support USB UIRT. When building from sources, either you need patch or get latest CVS sources. I did not try CVS but I've read somewhere that USB UIRT made to CVS, so it has to be supported. Check USB UIRT support forums, LIRC mail list for more info. -Original Message- From: [EMAIL PROTECTED] [mailto:mythtv-users- [EMAIL PROTECTED] On Behalf Of Jim Oltman Sent: Tuesday, March 08, 2005 10:57 AM To: Discussion about mythtv Subject: Re: [mythtv-users] USB IR Receiver But what are the lines that I will need in my modprobe.conf? This is what I have so far in it (from Jarod's guide) alias char-major-61 lirc_serial options lirc_serial irq=4 io=0x3f8 install lirc_serial /bin/setserial /dev/ttyS0 uart none ;\ /sbin/modprobe --ignore-install lirc_serial Instead of lirc_serial, will it be lirc_usb? I have no idea. Thanks! ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] The nvidia-settings tool and Myth (keeping overscan right)
For me, this isn't a solution. When I reboot my machine with a different OVERSCAN setting, it actually takes on the screen with the SHOW/HIDE DETAILS because that fills in the entire screen just like I want. When it goes into KDE, it doesn't keep that overscan. This is confusing to me because I thought that in the SHO/HIDE details screen, X has already been started. Am I missing something? On Tue, 8 Mar 2005 11:28:10 -0500, Jason Blair [EMAIL PROTECTED] wrote: Put this in a place where it will be run each time you log in: nvidia-settings --load-config-only On Tue, 8 Mar 2005 07:10:23 -0500, Pete Stagman [EMAIL PROTECTED] wrote: I have no problem keeping the settings. I know that nvidia-settings saves the settings when you exit it. What I do is tweak my settings, close it, restart it and leave it running minimized. It always survives reboots for me that way. As long as I don't close it before shutdown. --Pete On Tue, 8 Mar 2005 23:04:31 +1100, Phill Edwards [EMAIL PROTECTED] wrote: One of the few remaining issues for me is using all of my TV's screen real-estate. If I use the 'nvidia-settings' tool, I can set up the overscan so that the image completely fills my TV. Unfortunately, it doesn't last. Especially if I use MythGame to launch an external application that resizes things (StepMania and TuxRacer for example). When I return to Myth the screen is no longer maximized. I've found that the only way to reliably get the screen maximized again is to quit Myth, fire up the nvidia-settings GUI, twiddle the size slider, then quit the GUI. Even running 'nvidia-settings --load-config-only' doesn't do it. I know this isn't a Myth issue, it's poor design on nVidia's part, but how are other people dealing with nvidia-settings? Does anybody have a way to re-maximize the display without leaving Myth, or at least without having to bring up the GUI? You could try putting this in the Devices section of your xord.conf or equivalent: Option TVOverScan 0.60 Obviously change 0.60 to suit your needs! Regards, Phill ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users -- Lirc, FC3, and an Irblaster? www.lircsetup.com ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
Re: [mythtv-users] USB IR Receiver
But what are the lines that I will need in my modprobe.conf? This is what I have so far in it (from Jarod's guide) alias char-major-61 lirc_serial options lirc_serial irq=4 io=0x3f8 install lirc_serial /bin/setserial /dev/ttyS0 uart none ;\ /sbin/modprobe --ignore-install lirc_serial Instead of lirc_serial, will it be lirc_usb? I have no idea. Thanks! On Tue, 8 Mar 2005 10:35:37 -0700, Vladimir Shved [EMAIL PROTECTED] wrote: I was building a home-brew IR receiver. I finally got all the parts together and was soldering them up to the PCB board I got and it didn't work. Long story short, I want to use a USB IR receiver. Jarod has his MCE receiver working in his setup and I wanted to know how to go about doing that? Will it give a crazy dev listing that I will need to put into myth? Any help would be appreciated. Thanks! It works here with LIRC. ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users ___ mythtv-users mailing list mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
