Hi,
sorry, if this was already answered...
Using latest driver (0.9.4), kernel 2.4.17 (RHL rawhide) and Matrox
Marvel (on a LCD, and following /etc/modules.conf:
alias char-major-250 dvb
alias char-major-81 videodev
alias char-major-81-0 dvb
alias siemens_dvb dvb
options SP8870 debug=1
options saa7146_core mode=0
options dvb init_chan=2 pids_off=0 vidmode=2
below saa7146_core VES1893 VES1820 L64781 stv0299 tuner tda8083 SP8870
below dvb saa7146_v4l
Compiled modules are copied to
# ls /lib/modules/2.4.17-0.13/dvb/
dmxdev.o dvb_filter.o dvb_net.o saa7146_core.o stv0299.o
VES1820.o
dvb_demux.o dvb_firm.o dvb.o saa7146_v4l.o tda8083.o
VES1893.o
dvbdev.o dvb_frontend.o L64781.o SP8870.o tuner.o
Running a "modprobe siemens_dvb" on root's home directory, all
modules were loaded, but running tuxview didn't show a nice picture,
also if tuxview window was moved, the picture is still on original
location.
Stopping tuxview, removing all modules, changing to the drivers
directory (where the same modules live) and running a
"modprobe siemens_dvb", all works fine afterwards using tuxview
Can anyone explain this to me? I thought, it shouldindepended from a
directory, where "modprobe" is used.
Is there a hidden feature in "modprobe"?
Or need a module a file of the local directory?
TIA,
Peter, confused
--
Info:
To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as
subject.
