LinHES Forums
http://forum.linhes.org/

saa7134 & R5F27
http://forum.linhes.org/viewtopic.php?f=6&t=16400		 Page 1 of 2
Author:  snaproll [ Mon Sep 10, 2007 11:07 am ]
Post subject:  saa7134 & R5F27
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.
Author:  cecil [ Mon Sep 10, 2007 11:17 am ]
Post subject: 
No one reported any issues. Perhaps you can give the definitive word.
Author:  apacheark [ Mon Sep 10, 2007 11:17 am ]
Post subject: 
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...
Author:  snaproll [ Mon Sep 10, 2007 11:23 am ]
Post subject: 
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.
Author:  jzigmyth [ Mon Sep 10, 2007 11:30 am ]
Post subject: 
I look forward to hearing the results.
Thanks.
Author:  tjc [ Mon Sep 10, 2007 5:53 pm ]
Post subject: 
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.
Author:  snaproll [ Tue Sep 11, 2007 6:52 am ]
Post subject: 
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 ! :D
Author:  tjc [ Wed Sep 12, 2007 11:34 pm ]
Post subject: 
On the "sweat equity" front, this page has a patch which you can try... http://www.knoppmythwiki.org/index.php?page=kworld115HowTo
Author:  arriflex [ Fri Sep 14, 2007 10:34 am ]
Post subject: 
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
Author:  graysky [ Fri Sep 14, 2007 4:55 pm ]
Post subject: 
tjc wrote:
On the "sweat equity" front, this page has a patch which you can try... http://www.knoppmythwiki.org/index.php?page=kworld115HowTo


My 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.
Author:  graysky [ Fri Sep 14, 2007 5:15 pm ]
Post subject: 
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 :(
Author:  arriflex [ Fri Sep 14, 2007 6:07 pm ]
Post subject: 
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
Author:  arriflex [ Fri Sep 14, 2007 6:30 pm ]
Post subject: 
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
Author:  marc.aronson [ Fri Sep 14, 2007 6:36 pm ]
Post subject: 
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
Author:  tjc [ Fri Sep 14, 2007 8:47 pm ]
Post subject: 
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=9607

If 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.
Page 1 of 2 All times are UTC - 6 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/