On Sat, 19 Nov 2005 14:00:17 +0100, "Hans Verkuil" <[EMAIL PROTECTED]>
said:
> On Saturday 19 November 2005 13:50, Xenna wrote:
> > On Sat, 19 Nov 2005 13:32:13 +0100, "Hans Verkuil"
> > <[EMAIL PROTECTED]>
> >
> > said:
> > > On Saturday 19 November 2005 13:25, Xenna wrote:
> > > > On Sat, 19 Nov 2005 13:07:28 +0100, "Hans Verkuil"
> > > > <[EMAIL PROTECTED]>
> > > >
> > > > said:
> > > > > On Saturday 19 November 2005 12:58, Xenna wrote:
> > > > > > On Sat, 19 Nov 2005 12:35:42 +0100, "Hans Verkuil"
> > > > > > <[EMAIL PROTECTED]>
> > > > > >
> > > > > > said:
> > > > > > > On Saturday 19 November 2005 11:51, Xenna wrote:
> > > > > > > > On Sat, 19 Nov 2005 11:26:41 +0100, "Hans Verkuil"
> > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > >
> > > > > > > > said:
> > > > > > > > > On Saturday 19 November 2005 11:21, Xenna wrote:
> > > > > > > > > > On Sat, 19 Nov 2005 11:00:38 +0100, "Hans Verkuil"
> > > > > > > > > > <[EMAIL PROTECTED]>
> > > > > > > > > >
> > > > > > > > > > said:
> > > > > > > > > > > On Saturday 19 November 2005 10:47, Xenna wrote:
> > > > > > > > > > > > L.S,
> > > > > > > > > > > >
> > > > > > > > > > > > I have recently set up a MytTV server from
> > > > > > > > > > > > scratch . I started out with a single PVR350
> > > > > > > > > > > > which work fine, both the tuner and TV-Out. I was
> > > > > > > > > > > > very happy with MythTV so a week ago I went out
> > > > > > > > > > > > and bought a PVR500. (both cards are quite new
> > > > > > > > > > > > which may be part of the problem).
> > > > > > > > > > > >
> > > > > > > > > > > > The two cards work perfectly on their own, but
> > > > > > > > > > > > whenever I try to use them together in the system
> > > > > > > > > > > > the PVR350 fails altogether and the PVR500 limps
> > > > > > > > > > > > on with only one tuner.
> > > > > > > > > > > >
> > > > > > > > > > > > Log of the PVR350 on its own:
> > > > > > > > > > > > http://pastebin.com/435195 Log of the PVR500 on
> > > > > > > > > > > > its own: http://pastebin.com/435196 Log and
> > > > > > > > > > > > problem description of both cards together:
> > > > > > > > > > > > http://pastebin.com/435194
> > > > > > > > > > > >
> > > > > > > > > > > > /etc/modprobe.conf: http://pastebin.com/435199
> > > > > > > > > > > >
> > > > > > > > > > > > System specs:
> > > > > > > > > > > > MSI K8N Neo2 Platinum-54G,S939,nForce3 Ultra,
> > > > > > > > > > > > GLAN AMD Athlon 64 3200+, 2.0Ghz, 512Kb
> > > > > > > > > > > > cache,S-939,Box Dane-Elec 1Gb Dual-Channel Kit,
> > > > > > > > > > > > 2x512Mb, PC3200 Matrox G400 AGP Dual Head 32MB
> > > > > > > > > > > > Fedora Core 4 (i386)
> > > > > > > > > > > > IVTV 0.4.0 (RPM install according to
> > > > > > > > > > > > http://wilsonet.com/mythtv/fcmyth.php)
> > > > > > > > > > > >
> > > > > > > > > > > > I've seen many reports of these cards working
> > > > > > > > > > > > well together (that's why I bought the PVR500)
> > > > > > > > > > > > but I've also seen reports of problems similar
> > > > > > > > > > > > (or somewhat different) to mine. I'm thinking
> > > > > > > > > > > > that perhaps newer versions of the Hauppauge
> > > > > > > > > > > > cards have come out that the IVTV drivers are not
> > > > > > > > > > > > quite compatible with.
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks very much in advance for any help.
> > > > > > > > > > > >
> > > > > > > > > > > > If I need to do some more testing let me know!
> > > > > > > > > > >
> > > > > > > > > > > Make sure you use no module options at all (I saw
> > > > > > > > > > > from the log that you use at least a enable_output
> > > > > > > > > > > option for saa7127). Make sure the cards do not get
> > > > > > > > > > > too hot (overheating is one cause for problems). It
> > > > > > > > > > > has nothing to do with newer version since they
> > > > > > > > > > > work fine on their own.
> > > > > > > > > >
> > > > > > > > > > Hi Hans,
> > > > > > > > > >
> > > > > > > > > > Thanks for looking into this.
> > > > > > > > > >
> > > > > > > > > > I commented all the modprobe.conf option lines out as
> > > > > > > > > > seen below:
> > > > > > > > > >
> > > > > > > > > > # ivtv modules setup
> > > > > > > > > > alias char-major-61 lirc_i2c
> > > > > > > > > > alias char-major-81 ivtv
> > > > > > > > > > alias char-major-81-0 ivtv
> > > > > > > > > > alias char-major-81-1 ivtv
> > > > > > > > > > alias char-major-81-2 ivtv
> > > > > > > > > > alias tveeprom tveeprom-ivtv
> > > > > > > > > > alias msp3400 msp3400-ivtv
> > > > > > > > > > #options ivtv ivtv_debug=1 tuner=5
> > > > > > > > > > #options saa7127 enable_output=1 output_select=0
> > > > > > > > > > pal=1 install ivtv /sbin/modprobe --ignore-install
> > > > > > > > > > ivtv #; /sbin/modprobe ivtv-fb
> > > > > > > > > > #install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe
> > > > > > > > > > --ignore-install lirc_i2c
> > > > > > > > > >
> > > > > > > > > > Unfortunately the situation remains exactly the same.
> > > > > > > > > > Overheating seems unlikely. The cards are not hot to
> > > > > > > > > > the touch at all and the system is hardly doing any
> > > > > > > > > > work at all.
> > > > > > > > > >
> > > > > > > > > > Do you have any other suggestions?
> > > > > > > > >
> > > > > > > > > If you switch the cards around, does that make any
> > > > > > > > > difference? Can you make the kernel log available of
> > > > > > > > > the ivtv
> > > > > > > > > initialization now that you have removed the module
> > > > > > > > > options?
> > > > > > > >
> > > > > > > > Switching the cards around was one of the first things I
> > > > > > > > tried, but it didn't make any difference (surprisingly -
> > > > > > > > to me - the PVR350 is detected as the first card no
> > > > > > > > matter which order I put them in).
> > > > > > > >
> > > > > > > > The log with the module options removed is here:
> > > > > > > > http://pastebin.com/435225
> > > > > > > >
> > > > > > > > > It's a weird one, never seen something like this
> > > > > > > > > before.
> > > > > > > >
> > > > > > > > I was afraid of that :(
> > > > > > >
> > > > > > > Interesting problem: it looks as if the I2C bus of the
> > > > > > > pvr350 isn't detected. Run the i2cdetect program (part of
> > > > > > > the lm-sensors package):
> > > > > > >
> > > > > > > First run: i2cdetect -l
> > > > > >
> > > > > > I did that, it gave no output, then I tried "i2cdetect -v
> > > > > > -l", which gave:
> > > > > >
> > > > > > Warning: Unsupported flag "-v"!
> > > > > > Syntax: i2cdetect [-y] [-a] [-q|-r] I2CBUS [FIRST LAST]
> > > > > >         i2cdetect -l
> > > > > >         i2cdetect -V
> > > > > >   I2CBUS is an integer
> > > > > >   With -a, probe all addresses (NOT RECOMMENDED)
> > > > > >   With -q, uses only quick write commands for probing (NOT
> > > > > > RECOMMENDED) With -r, uses only read byte commands for
> > > > > > probing (NOT RECOMMENDED) If provided, FIRST and LAST limit
> > > > > > the probing range. With -l, lists installed busses only
> > > > > > Error: No I2C busses found!
> > > > > > Be sure you have done 'modprobe i2c-dev'
> > > > > > and also modprobed your i2c bus drivers
> > > > > >
> > > > > > So I tried 'modprobe i2c-dev' and then i2cdetect worked. It
> > > > > > seems the i2c-dev module isn't loading automatically. (don't
> > > > > > know if it should)
> > > > > >
> > > > > > This had me hoping that perhaps the cards would now function
> > > > > > properly but the symptoms appear to remain unchanged.
> > > > > >
> > > > > > > This shows all I2C busses. For each ivtv bus run:
> > > > > > >
> > > > > > > i2cdetect -a X (where X is the bus number, e.g. 3 for bus
> > > > > > > i2c-3).
> > > > > > >
> > > > > > > Please report the output of these commands.
> > > > > >
> > > > > > http://pastebin.com/435253
> > > > >
> > > > > It's definitely I2C bus related. Can you try the following:
> > > > > first modprobe i2c-dev, wait a second, then run 'modprobe ivtv
> > > > > debug=33'. Please report the ivtv messages in the kernel log.
> > > > > What is the output of i2cdetect -y -a 2? If it is still all
> > > > > 'XX', then remove the PVR500 card and go through the same
> > > > > process again.
> > > >
> > > > I'm not sure how to prevent the ivtv module from loading in the
> > > > first place so I tried rmmod ivtv, this crashed the system
> > > > immediately (tried twice) with a lot of 'Kernel panic' console
> > > > messages. How do I stop the ivtv frm loading automatically on
> > > > Fedora C4?
> > >
> > > I think it is enough to comment these lines in modprobe:
> > >
> > > alias char-major-81 ivtv
> > > alias char-major-81-0 ivtv
> > > alias char-major-81-1 ivtv
> > > alias char-major-81-2 ivtv
> > >
> > > You may have to run depmod afterwards (I'm never sure if that's
> > > needed or not). If that doesn't help just remove ivtv.ko from the
> > > lib/modules/.../ivtv directory and use insmod instead of modprobe
> > > to load the ivtv.ko from the ivtv/drivers directory (I assume
> > > you've built the driver from the source).
> >
> > I had to remove the ivtv.ko from the modules tree to stop it loading.
> > I haven't built the driver from source so I moved it to /tmp and did
> > 'modprobe i2c-dev' and then 'insmod /tmp/ivtv.ko debug=33', resulting
> > in:
> >
> > insmod: error inserting './ivtv.ko': -1 Unknown symbol in module
> >
> > The kernel log said at the same time:
> >
> > Nov 19 13:49:08 alastor kernel: i2c /dev entries driver
> > Nov 19 13:49:35 alastor kernel: ivtv: no version for "struct_module"
> > found: kernel tainted.
> > Nov 19 13:49:35 alastor kernel: ivtv: Unknown symbol i2c_bit_add_bus
> > Nov 19 13:49:35 alastor kernel: ivtv: Unknown symbol i2c_bit_del_bus
> > Nov 19 13:49:35 alastor kernel: ivtv: Unknown symbol
> > video_unregister_device
> > Nov 19 13:49:35 alastor kernel: ivtv: Unknown symbol
> > video_device_alloc Nov 19 13:49:35 alastor kernel: ivtv: Unknown
> > symbol
> > video_register_device
> > Nov 19 13:49:35 alastor kernel: ivtv: Unknown symbol video_usercopy
> > Nov 19 13:49:35 alastor kernel: ivtv: Unknown symbol
> > video_device_release
> 
> Weird, it's all loaded automatically for me. You probably have to run 
> 'modprobe videodev' and modprobe some i2c module. You may have to 
> revert the changes, run modprobe ivtv, then lsmod. Make a note (or put 
> in a file) of the loaded modules and see which i2c modules are loaded. 
> Then try again, but this time modprobe videodev and the i2c modules. I 
> think it will work then. It's all compiled into the kernel for me (I 
> build my own kernel), so I don't see all these modules.

Well, I just tried some sensible looking stuff (I'm in unknown waters
here):
modprobe i2c-dev
modprobe videodev
modprobe i2c-via

And then the 'insmod /tmp/ivtv.ko' command worked. 

$ lsmod|grep "i2c\|ivtv"
ivtv                  227348  0
i2c_via                 4677  0
i2c_algo_bit            9417  2 ivtv,i2c_via
videodev                9921  1 ivtv
i2c_dev                13121  0
i2c_nforce2             7361  0
i2c_core               21697  11
wm8775,cx25840,tda9887,msp3400,saa7127,saa7115,tuner,tveeprom,i2c_algo_bit,i2c_dev,i2c_nforce2

The initialization log reads: http://pastebin.com/435306

(it looks like it didn't recognize the debug parameter)

Regards,
Xenna

_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to