Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#12526 - tuning breaked on cx24123 demodulator? SkyStar2
Attached to Project:
Arch Linux
Opened by Christian Galander (igprolin) - Sunday, 21 December 2008, 14:37 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 31 May 2009, 14:32 GMT
Opened by Christian Galander (igprolin) - Sunday, 21 December 2008, 14:37 GMT
Last edited by Roman Kyrylych (Romashka) - Sunday, 31 May 2009, 14:32 GMT
|
DetailsDescription:
I have many problems with my Technisat SkyStar2 since i upgrade my RAM to 8 GB. This can't was successfully initiated by archlinux but i can't watch tv. in dmesg i found some errors, e.g.: CX24123: cx24123_i2c_readreg: reg=0x0 (error=-121) CX24123: wrong demod revision: 87 On linuxtv.org i found following: http://www.linuxtv.org/pipermail/linux-dvb/2008-October/029989.html : It seems an update of dvb-core breaks tuning of cx24123 Additional info: * package version(s) all players e.g. MPlayer or Xine * config and/or log files etc. Steps to reproduce: Upgrade to 8 GB RAM and use a tv tuner card with the cx24123 demodulator ;-). 
dmesg.output
(28 KiB)
|
This task depends upon
Closed by Roman Kyrylych (Romashka)
Sunday, 31 May 2009, 14:32 GMT
Reason for closing: Upstream
Additional comments about closing: see the last comment
Sunday, 31 May 2009, 14:32 GMT
Reason for closing: Upstream
Additional comments about closing: see the last comment
Comment by Glenn Matthys (RedShift) -
Wednesday, 24 December 2008, 08:09 GMT
- Field changed: Status (Unconfirmed → Researching)
- Field changed: Category (Kernel → Upstream Bugs)
- Field changed: Severity (High → Low)
Well, they are working on it :-). So for now, either limit the system memory installed. Does this still happen with 2.6.27.10?
Comment by Roman Kyrylych (Romashka) -
Sunday, 31 May 2009, 14:32 GMT
Well, this is upstream issue, and no updates on this are given here, so I'm closing this.