[linux-dvb] Re: Driver problem with SuSE 7.2

[Klaus Schmidinger <Klaus.Schmidinger@cadsoft.de>]

Klaus Schmidinger wrote:
> 
> Klaus Schmidinger wrote:
> >
> > Klaus Schmidinger wrote:
> > >
> > > I am trying to install the latest DVB driver on a SuSE 7.2 system,
> > > running kernel 2.4.4-4GB (as it comes with SuSE).
> > >
> > > The driver compiles ok, but when I load it I get "kernel BUG" errors
> > > in the log file and soon after that the machine completely hangs, so that
> > > I have to do a hard reset.
> > >
> > > I have uploaded the error messages to
> > >
> > >   ftp://ftp.cadsoft.de/pub/etc/vdr/suse72.errors.txt
> > >
> > > to avoid clogging the list. If somebody could give me a hint what might
> > > be going wrong here, I would appreciate that very much.
> > >
> > > Are there any known special things to consider when running the DVB driver
> > > on SuSE 7.2/kernel 2.4.4?
> > >
> > > Klaus
> >
> > One more observation: if I remove all sound modules (everything starting with "snd")
> > and do
> >
> >   export TOPDIR=/usr/src/linux
> >   make insmod
> >
> > in the DVB/driver directory (the "export..." appears to be necessary, otherwise
> > I get an error message from some kernel source script) the driver loads without
> > error messages and there are no "kernel BUGs". I get 'n-tv' on the video out and
> > everything appears to be fine. I can even start VDR and switch channels, but when I
> > start replaying a recording, after showing a few frames the system completely freezes
> > again :-(
> >
> > Could it be that there is a problem between the sound modules and the DVB modules?
> >
> > These are the sound modules that are installed on this system:
> >
> > snd-synth-emu10k1       4288   0  (unused)
> > snd-synth-emux         26592   0  [snd-synth-emu10k1]
> > snd-seq-midi-emul       4480   0  [snd-synth-emux]
> > snd-seq-virmidi         8496   0  [snd-synth-emux]
> > snd-seq-midi            3568   0  (unused)
> > snd-seq-midi-event      2992   0  [snd-seq-virmidi snd-seq-midi]
> > snd-seq                42656   0  [snd-synth-emux snd-seq-virmidi snd-seq-midi snd-seq-midi-event]
> > snd-card-emu10k1        2320   0
> > snd-emu10k1            21936   0  [snd-synth-emu10k1 snd-card-emu10k1]
> > snd-pcm                30560   0  [snd-emu10k1]
> > snd-timer               8560   0  [snd-seq snd-pcm]
> > snd-emux-mem            1616   0  [snd-synth-emux snd-emu10k1]
> > snd-rawmidi             9664   0  [snd-seq-midi snd-emu10k1]
> > snd-ac97-codec         24576   0  [snd-emu10k1]
> > snd-mixer              24224   0  [snd-emu10k1 snd-ac97-codec]
> > snd-seq-device          4032   0  [snd-synth-emu10k1 snd-synth-emux snd-seq-midi snd-seq snd-card-emu10k1 snd-rawmidi]
> > snd                    34032   1  [snd-synth-emux snd-seq-virmidi snd-seq-midi snd-seq-midi-event snd-seq snd-card-emu10k1 snd-emu10k1 snd-pcm snd-timer snd-emux-mem snd-rawmidi snd-ac97-codec snd-mixer snd-seq-device]
> > soundcore               3632   4  [snd]
> >
> > Klaus
> 
> Today I have made several experiments to further track down this problem
> and found that by simply loading the two modules
> 
>   i2c_core
>   saa7146_code.o
> 
> the system became unstable. i2c_core by itself doesn't cause any problems,
> and also installing all of the modules VES1893.o, VES1820.o, tda8083.o, stv0299.o
> and tuner.o (which all use i2c_core) doesn't cause problems.
> 
> Now the question is: is i2c_core or saa7146_code.o the troublemaker?

Sorry about the typo: that's of course 'saa7146_core.o'

Klaus
-- 
_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10
CadSoft Computer GmbH                   Fax:   +49-8635-6989-40
Hofmark 2                               Email:   kls@cadsoft.de
D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de
_______________________________________________________________


-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.