On Sun, Apr 01, 2012 at 07:50:07PM +0300, Pasi Kärkkäinen wrote:
> On Sun, Apr 01, 2012 at 02:15:39PM +0300, Mika Iisakkila wrote:
> > 1.4.2012 13:04, Pasi Kärkkäinen kirjoitti:
> >> Yep, it was from Fedora. You could always check the Fedora src.rpm
> >> for any extra patches they might have there.
On Sun, Apr 01, 2012 at 02:15:39PM +0300, Mika Iisakkila wrote:
> 1.4.2012 13:04, Pasi Kärkkäinen kirjoitti:
>> Yep, it was from Fedora. You could always check the Fedora src.rpm
>> for any extra patches they might have there..
>>
>>> I'll gladly receive a current, relevant reference that will tell
1.4.2012 15:22, Marc kirjoitti:
Why don't you cross-compile your kernel on a faster computer ?
Because I don't really have any with a suitable distribution
installed. And once it takes more than 15 minutes, it's pretty
much the same difference if it's two or six or ten hours...
I'm not going to
On 01/04/2012 13:15, Mika Iisakkila wrote:
Well, I googled a bit more, and it seems the actual problem is
in dxr3-plugin, not the drivers. The plugin is only able to
use OSS (as of Dec.2008, anyway). I'm not willing to waste time
fighting with semi-functional compatibility layers, so I'll just
k
1.4.2012 13:04, Pasi Kärkkäinen kirjoitti:
Yep, it was from Fedora. You could always check the Fedora src.rpm
for any extra patches they might have there..
I'll gladly receive a current, relevant reference that will tell
me how to use the em8300 drivers on current Ubuntu without
recompiling the
On Thu, Mar 29, 2012 at 01:47:06PM +0300, Mika Iisakkila wrote:
> 28.3.2012 22:34, Pasi Kärkkäinen kirjoitti:
>> The default audio mode of the em8300 device support utilities and kernel
>> modules (em8300 and kmod-em8300-* packages) has changed from OSS to ALSA to
>> follow upstream
>
> I googled
On 01.04.2012 11:53, Klaus Schmidinger wrote:
On 01.04.2012 11:27, Dominic Evans wrote:
I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27
My DVB-S/DVB-S2 tuners all continued to work fine, but none of my
DVB-T channels were accesible anymore.
Checking the logs I notice
On 01.04.2012 11:27, Dominic Evans wrote:
I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27
My DVB-S/DVB-S2 tuners all continued to work fine, but none of my
DVB-T channels were accesible anymore.
Checking the logs I noticed numerous "ERROR: invalid value for
parameter
I recently updated from 1.7.22 to the latest VDR developer snapshot 1.7.27
My DVB-S/DVB-S2 tuners all continued to work fine, but none of my
DVB-T channels were accesible anymore.
Checking the logs I noticed numerous "ERROR: invalid value for
parameter 'S'" entries, whenever attempting to tune to
On 1 April 2012 00:54, VDR User wrote:
>> Unfortunately, this doesn't seem to be working. I just upgraded to vdr
>> 1.7.27 and the channel name is now only a single character for every
>> channel.
>
> I had the same problem here as well. Klaus has fixed it, try the patch
Thanks. Have submitted th
10 matches
Mail list logo
