On Mon, 14 Nov 2005 23:40:48 +0100 Luca Olivetti <luca@xxxxxxxxxxx> wrote: > En/na Ville Skytt? ha escrit: > > On Mon, 2005-11-14 at 13:40 -0700, Vladimir Shved wrote: > > > >> Also tried Dxr3/Hollywood+, TV-out is nice, OSD is much improved but still > >> very unstable. > > > > These problems seem to have gone completely away here (even with setting > > the plugin OSD flush rate to 0) in normal use after installing text2skin > > (CVS) and starting to use a less challenging (?) skin than ST:TNG, > > currently the latest enElchi with the DXR3 compatible logos. > > but they're not gone here with the same skin ;-) > (not much difference between enElchi or enigma or ST:TNG). > (I'm not complaining, the video quality is good and the osd is > usable...but not completely stable). > I had Dxr3 lockups too until I figured out it was an interrupt problem. On my 64-bit system it crashed erratically and also often when there was some network traffic. I tried to get every device it's own IRQ, but the motherboard thought otherwise and I couldn't get all the cards fit without sharing IRQ's. Finally I enabled IO-APIC in the kernel and that gave additional interrupt numbers so that by swapping some cards it worked properly. For some reason both my DVB devices and Dxr3 were sensitive to shared IRQ's, or perhaps it was some other misbehaving driver. Now the system works 24/7 with perhaps one Dxr3 lockup every week. That could be due to bad signal or DVB-card problems as well because sometimes one of the two DVB-T cards seems to go out for lunch. Haven't figured it out yet, but at least it doesn't crash the machine and a simple module reloading cycle fixes the problem. -- Niko Mikkil?
