| Author |
Message |
|
snaproll
|
 Posted: Mon Sep 10, 2007 11:07 am |
|
|
Joined: Sun Jul 24, 2005 4:16 pm
Posts: 508
Location:
Ft. Worth TX
|
|
Will the ivtv version used in F27 'play nice' with ir remotes ?
Previously the solution was to not load saa7134 modules, which precluded using certain PVR cards.
|
|
| Top |
|
 |
|
cecil
|
Posted: Mon Sep 10, 2007 11:17 am |
|
 |
| Site Admin |
Joined: Fri Sep 19, 2003 6:37 pm
Posts: 2659
Location:
Whittier, Ca
|
|
No one reported any issues. Perhaps you can give the definitive word.
|
|
| Top |
|
|
|
apacheark
|
Posted: Mon Sep 10, 2007 11:17 am |
|
|
Joined: Thu May 18, 2006 3:06 pm
Posts: 13
|
|
I did not comment out saa7134 in Knoppmyth.tv when I first installed R5F27 but then I found that my Hauppauge Dogbone remote was being a bit slow and unresponsive. I then DID comment out the saa7134 line and that cleared up my problem.
I have a Sempron 3000 CPU with 1GB RAM and an Nvidia 6200 AGP card. I am using a serial IR Blaster and a Hauppauge PVR-150 card.
Just my 2 cents worth...
|
|
| Top |
|
|
|
snaproll
|
Posted: Mon Sep 10, 2007 11:23 am |
|
|
Joined: Sun Jul 24, 2005 4:16 pm
Posts: 508
Location:
Ft. Worth TX
|
|
I'll be building up a new box with R5F27, (my first with a SATA drive), & a saa7134 card. I'll report back when I get up.
|
|
| Top |
|
|
|
jzigmyth
|
Posted: Mon Sep 10, 2007 11:30 am |
|
|
Joined: Thu Mar 02, 2006 5:42 pm
Posts: 410
Location:
middleton wi usa atsc
|
|
I look forward to hearing the results.
Thanks.
|
|
| Top |
|
|
|
tjc
|
Posted: Mon Sep 10, 2007 5:53 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
Having the saa7134 and thus the ir_kbd_i2c modules loaded roached the remote connected to my PVR-250. I ended up deleting /lib/modules/2.6.18-chw-13/kernel/drivers/media/video/ir-kbd-i2c.ko out of sheer aggravation.
Bottom line, ir_kbd_i2c and lirc_i2c do not play together nicely, and must occasionally be forcibly separated. My take is that your options look like this:
1) Avoid this combination of hardware. Not ideal.
2) Don't use the PVR card connection in system with a 7134 based card. Replace it with something like the StreamZap sensor. Basically solving the problem by tossing a little money at it.
3) Dummy out the guts of the ir_kbd_i2c driver or figure out how to remove the references to it in the saa7134 driver. This is the "sweat equity" approach.
|
|
| Top |
|
|
|
snaproll
|
Posted: Tue Sep 11, 2007 6:52 am |
|
|
Joined: Sun Jul 24, 2005 4:16 pm
Posts: 508
Location:
Ft. Worth TX
|
Well, my computer arrived yesterday, & a half hour later was running R5F27. Holy Shazam, Batman ! The new installer is the best ever! Straight to tier 1.
So by the time I got home & playing with the new stuff, several responses had come in on the fate of the Hauppauge remote & saa7134, & it wasn't good, & tjc was writing the manual to reflect how to deal with that. So I sidestepped & set my box up with a Streamzap remote. I have a piece of hardware that had a slow remote problem even with the Streamzap, until the saa7134 modules were banished (on E50 & F1) So I wanted to see if the Streamzap worked 'as is' (no commenting out saa7134) & as of this morning (box has run 14 hours since setup) that remote has had no problems.
(Edit: & after several days no problem ever surfaced)
I got other tweaks in mind for the box, so so far, very promising. Thanks Cecil & crew ! 
Last edited by snaproll on Thu Sep 13, 2007 9:04 am, edited 1 time in total.
|
|
| Top |
|
|
|
tjc
|
Posted: Wed Sep 12, 2007 11:34 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
|
| Top |
|
|
|
arriflex
|
Posted: Fri Sep 14, 2007 10:34 am |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
|
I took a shot in the dark at following known issue #5 in the R5F27 hints and removed ir-kbd-i2c.ko. Bad idea, I probably should have renamed it or something smart like that. Rookie mistake I suppose.
Anyway, the wiki is down right now, and I am having trouble finding info including a bad link referenced in the above line on the hints page to what I'm guessing is actually this thread. I was guessing that my cards didn't rely on the driver. I'd like to restore that file, because since doing it my backend refuses to start. Where do I find the log file that will help me trouble shoot this?
It all started because my Hauppage remote was only working some of the time.
BTW, the auto upgrade in R5F27 was the first one out of the last four that "just worked" for me. Nice work!
It wasn't until after I rebooted the first time that the remote worked, and then the next time I rebooted, it didn't. I already tried my deep power cycle as well to force the IVTV firmware load.
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
graysky
|
Posted: Fri Sep 14, 2007 4:55 pm |
|
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
tjc wrote: On the "sweat equity" front, this page has a patch which you can try... http://www.knoppmythwiki.org/index.php?page=kworld115HowToMy PVR-250's remote is missing clicks now that I've upgraded to R5F27; thanks for that link: I am trying it right now and will report back.
_________________
Retired KM user (R4 - R6.04); friend to LH users.
|
|
| Top |
|
|
|
graysky
|
Posted: Fri Sep 14, 2007 5:15 pm |
|
|
Joined: Wed Dec 10, 2003 8:31 pm
Posts: 1996
Location:
/dev/null
|
Update:
On step 7:
Code: # make drivers/media/video/ir-kbd-i2c.ko
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/docproc
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/kxgettext.o
HOSTCC scripts/kconfig/mconf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/lex.zconf.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf -s arch/i386/Kconfig
*
* Restart config...
*
*
* Suspend2
*
Suspend2 (SUSPEND2) [N/y/?] (NEW) To which I answered N the first time (that failed) to which I answered Y this time.... it went on: Code: *
* Image Storage (you need at least one allocator)
*
File Allocator (SUSPEND2_FILE) [N/y/?] (NEW) To which I answered N the first time (that failed) to which I answered Y this time... it went on: Code: Swap Allocator (SUSPEND2_SWAP) [N/y/?] (NEW) Again, the first time through I answered N, this second time though I answered Y. Code: Default resume device name (SUSPEND2_DEFAULT_RESUME2) [] (NEW)
Allow Keep Image Mode (SUSPEND2_KEEP_IMAGE) [N/y/?] (NEW) y
Replace swsusp by default (SUSPEND2_REPLACE_SWSUSP) [Y/n/?] (NEW) y
*
* Cryptographic options
*
Cryptographic API (CRYPTO) [Y/?] y
HMAC support (CRYPTO_HMAC) [Y/?] y
Null algorithms (CRYPTO_NULL) [M/n/y/?] m
MD4 digest algorithm (CRYPTO_MD4) [M/n/y/?] m
MD5 digest algorithm (CRYPTO_MD5) [Y/?] y
SHA1 digest algorithm (CRYPTO_SHA1) [M/y/?] m
SHA256 digest algorithm (CRYPTO_SHA256) [M/n/y/?] m
SHA384 and SHA512 digest algorithms (CRYPTO_SHA512) [M/n/y/?] m
Whirlpool digest algorithms (CRYPTO_WP512) [M/n/y/?] m
Tiger digest algorithms (CRYPTO_TGR192) [M/n/y/?] m
DES and Triple DES EDE cipher algorithms (CRYPTO_DES) [Y/?] y
Blowfish cipher algorithm (CRYPTO_BLOWFISH) [M/n/y/?] m
Twofish cipher algorithm (CRYPTO_TWOFISH) [M/n/y/?] m
Serpent cipher algorithm (CRYPTO_SERPENT) [M/n/y/?] m
AES cipher algorithms (CRYPTO_AES) [M/y/?] m
AES cipher algorithms (i586) (CRYPTO_AES_586) [M/n/y/?] m
CAST5 (CAST-128) cipher algorithm (CRYPTO_CAST5) [M/y/?] m
CAST6 (CAST-256) cipher algorithm (CRYPTO_CAST6) [M/n/y/?] m
TEA, XTEA and XETA cipher algorithms (CRYPTO_TEA) [M/n/y/?] m
ARC4 cipher algorithm (CRYPTO_ARC4) [M/y/?] m
Khazad cipher algorithm (CRYPTO_KHAZAD) [M/n/y/?] m
Anubis cipher algorithm (CRYPTO_ANUBIS) [M/n/y/?] m
Deflate compression algorithm (CRYPTO_DEFLATE) [M/y/?] m
LZF compression algorithm (CRYPTO_LZF) [N/m/y/?] (NEW) y
Michael MIC keyed digest algorithm (CRYPTO_MICHAEL_MIC) [M/y/?] m
CRC32c CRC algorithm (CRYPTO_CRC32C) [M/y/?] m
Testing module (CRYPTO_TEST) [M/n/?] m
#
# configuration written to .config
#
CHK include/linux/version.h
UPD include/linux/version.h
CHK include/linux/utsrelease.h
UPD include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-i386
CC arch/i386/kernel/asm-offsets.s
GEN include/asm-i386/asm-offsets.h
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/modpost.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
CC [M] drivers/media/video/ir-kbd-i2c.o
/bin/sh: .tmp_versions/ir-kbd-i2c.mod: No such file or directory
MODPOST
Seems to have encountered problems of which I know not what of 
_________________
Retired KM user (R4 - R6.04); friend to LH users.
|
|
| Top |
|
|
|
arriflex
|
Posted: Fri Sep 14, 2007 6:07 pm |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
|
I now see that with my two cards, it shouldn't matter that I deleted the file TJC mentioned. Was I suppose to get rid of a reference somewhere else?
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
arriflex
|
Posted: Fri Sep 14, 2007 6:30 pm |
|
|
Joined: Thu Feb 23, 2006 2:41 pm
Posts: 68
|
|
Just trying to bring it back to where I was before deleting ir-kbd-i2c.ko, I followed the wiki without making changes to ir-kbd-i2c.c as all I wanted was the original file. I encountered the same result, although had no trouble with answering 'N' to both questions during the make. Result being that ir-kbd-i2c.ko didn't end up in the /usr/src/linux-source-2.6.18-chw-13/drivers/media/video/ directory. I did end up with ir-kbd-i2c.c and ir-kbd-i2c.o however.
arri
_________________
Athlon 64 X2 4200+ 2GB Ram
MSI K8N Neo4-F NF4 939
ASUS N EN6200TC256/TD/64M
500gb SATA
1x Plextor PX-M402U
1x HD5000
R5.5 Upgrade from F27
|
|
| Top |
|
|
|
marc.aronson
|
Posted: Fri Sep 14, 2007 6:36 pm |
|
|
Joined: Tue Jan 18, 2005 2:07 am
Posts: 1532
Location:
California
|
The first 4 steps read:
Code: 1. Get the kernel source: wget ftp://knoppmyth.net/R5/linux-source-2.6.18-chw-13_2.6.18-chw-13-10.00.Custom_all.deb
2. dpkg -i linux-source-2.6.18-chw-13_2.6.18-chw-13-10.00.Custom_all.deb
3. cd /usr/src
4a. tar xjvf linux-source<tab>
4b. cp /boot/config-2.6.18-chw-13 /usr/src/linux-source-2.6.18-chw-13/.config
In my notes on getting kernel source, which is required to build this driver, I also show that "make-kpkg kernel_image" is required, so perhaps that is a missing step that should be step "4c".
Can anyone on the thread confirm that executing "make-kpkg kernel_image" is the right thing to do and won't damage an existing R5F27 install?
Marc
|
|
| Top |
|
|
|
tjc
|
Posted: Fri Sep 14, 2007 8:47 pm |
|
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
arriflex wrote: I took a shot in the dark at following known issue #5 in the R5F27 hints and removed ir-kbd-i2c.ko. Bad idea, I probably should have renamed it or something smart like that. Rookie mistake I suppose. Yep. You're supposed to check if you need it first. Of course without hardware details we can't help you either. Do you have a DVB, HDTV, or other card in the box which requires the saa7134 driver? Search your dmesg output for it. Code: dmesg | grep saa7134 arriflex wrote: a bad link referenced in the above line on the hints page If you told us which one it is, I might be able to fix it. Did you mean this one (which I just tested successfully)? http://mysettopbox.tv/phpBB2/viewtopic.php?t=9607If you really need the driver your best bets for recovery are: 1) Redo the auto-upgrade. It worked the first time it'll probably work even better the second because you've had the practice. 2) Boot the CD as a rescue disk, mount your root partition, and copy the driver from the CD to you harddisk. Given all the mucking about above I'd go with option #1. This time rather than deleting it try editing the init script with the following chunk from my personal post install tweaks script: Code: # Stop it from loading the dvb stuff which drags in the IR keyboard stuff
sed -si.orig -e 's/^\(modprobe dvb-bt8xx\)/#\1/' \
-e 's/^\(modprobe saa7134-dvb\)/#\1/' \
-e 's/^\(modprobe cx88-dvb\)/#\1/' \
/etc/init.d/KnoppMyth-tv
This is usually good enough, but I ended up deleting the driver because something else seemed to trigger the loading of those things regardless.
|
|
| Top |
|
|
View unanswered posts
View active topics
Print view
Previous topic Next topic 
LinHES Home
Board index
FAQ
Search
Login 
Register