does anyone have rotor.conf file for SuKaPa-6 (skyperfec)?
Is this the right channel for RTL2832u DVB-T regressions?
that's the right channel for dvb.
but for kernel module regression too? happened on 3.19->4.0 (unrelated bug forced me to stay on lts)
well, there are developers around. but they might not be looking at their irc clients atm.
sometimes you need to be patient.
http://permalink.gmane.org/gmane.linux.drivers.video-input-infrastructure/88157 it looks in keywords kinda similar
i don't get errors after disabling remote
and yes. there are mostly kernel developers. most of the drivers are in kernel and they maintain the media branch that gets merged in the main.
i always get surprised by how many times this dongle breaks and nobody notices for few releases, because everybody is on rtlsdr ;D
but this is different completely for sure
automatic bandwidth selection in vlc doesn't work anymore, seemingly selecting bandwidth=0
" rtl2832 7-0010: invalid bandwidth_hz 0"
i think i've seen that too. I thought it is vlc problem.
don't want to be a dick but "do not break userspace"
:P
i know, rule doesn't apply after so much time passed
huuuuh
this is getting weird
so behaviour has changed
low quality signal gets bandwidth set to 0
this doesn't make sense. bandwidth is something you need in order to lock the demodulator. quality is function of the demodulation.
i can only tell this one thing
changing kernel makes things works perfectly fine
best test case for immediately spotting difference would be not connecting antenna at all :D
yup
as soon as i have not perfect signal something chooses bandwidth 0
since such bandwidth wouldn't make any sense i will assume that it's a new error code that wasn't there before
k let's try now with IR remote, i thought that i had to disable that part
with remote enabled it completely fails
eg "r820t_read: i2c rd failed=-32 reg=00 len=2: 61 c8"
i2c is bus that could be shared by more than one device.
the point is that it's a regression anyway
yeh...
you are right again.
and it's not the first time it is mentioned
but since kernel trap is gone i'm lost
i think you should really talk with some developer
so better channel than this?
mchehab, crope these i know .
just stay around. they will came out, eventually.
my experience with mailinglists isn't particularly good (leads to acid atmosphere in the same time as resolved on irc ;>)
yeh...
eg. radeon issue was fixed and patched upstream in just 3h
(was killing boot)
i could ask you to do a bisect, but i've bisected kernel before... the chance that rc0 contains bugs that hang your system is non trivial.
if i had machine to bisect i would be doing that now
unless i can compile this outside of tree?
yes, i think the this branch have something like that.
but i haven't used it.
just to leave it here - if scope will be needed for debugging of this issue i has DS1052E so can do
oscilloscope ?
yup
let's hope it won't came to that :)
well it's light and very portable
but it will be pain to setup it
well, it also increase the risk of damaging your dongle...
nope
they all have SMA now
also all R820T tuners are coming corroded and barely soldered
so one has to desolder, use sandpaper and then solder back on the board ;D
this is why i love QFN packages so much
there is no way you could possibly damage package in any sane way
hehe... ok.
you know what you do :)
oh
those dongles are used for rtl-sdr
but thanks to DVB-T i could buy more of them
btw, check if the old (working) kernel supports remote at all.
what is rtl-sdr?
software defined radio driver (userspace)
and old working kernel supports remote fine
no idea actually about the new one
i have three identical dongles, two very accessible at any time
i have a feel that one issue is directly hw/sw related (i^2c/remote/tuner one) and the one with selecting bandwidth is of that do not break userspace kind
but too dumb to do more than guess
it's definitely software related.
i'm trying to understand device trees now
i mean like bad timing causing hw to glitch
like my recently discovered gate phone / lock that doesn't accept nearly half of iButtons
i should probably go back to device trees :<
reverse eng. working binary -> source
opensource.: source -> working binary