https://bugs.kde.org/show_bug.cgi?id=371190
--- Comment #11 from wgbuchh...@t-online.de --- (In reply to Mauro Carvalho Chehab from comment #10) > (In reply to wgbuchholz from comment #9) > > (In reply to Mauro Carvalho Chehab from comment #4) > > > (In reply to Mauro Carvalho Chehab from comment #3) > > > > (In reply to knossos456 from comment #2) > > > > > Same here with lowest C/N and V2.05 > > > > > was ok with v1.22, perhaps AGC problem ? > > > > > > > > I double-checked the logic: Kaffeine doesn't check if the signal > > > > is too weak for DVB-S/S2. I suspect that this bug is, instead, > > > > related to a DiSEqC bug, as I got a report that Kaffeine is not > > > > sending the right command to the DiSEqC switch. I'll need to > > > > investigate it further. Unfortunately, right now, I don't have > > > > any environment to test DiSEqC. > > > > > > I applied some patches today meant to fix Kaffeine. Unfortunately, > > > there's a > > > bug also at libdvbv5. So, you need to update libdvbv5 too, from upstream, > > > in > > > order to be able to test it. > > > > I have made a test with v4-utils-1.12.2 (libdvbv5) and kaffeine-2.0.5-1. > > The scan seems to be scanning across all LNB's (four), searching for the > > same transponder which is defined in 'scanfile.dvb', regardless the > > satellite name. See attachments. > > There were some bugs at libdvbv5 with regards to support for multi-LO LNBf > devices like the Universal type. It was fixed this Monday. > > Could you please test again, compiling v4l-utils from its source? You can > get its source from its master repository with: > > git clone git://linuxtv.org/v4l-utils.git > > and build/install it with: > > ./bootstrap.sh && configure && make && sudo make install Hello, I've made the test. The changes in libdvbv5 did not solve the problem of the DiSEqC commands. In one search for a special satellite the address of lnb must not change, but it does! The address is changing over all four positions f8, f9, fa and fb. Thank you for your support! -- You are receiving this mail because: You are watching all bug changes.
