On Saturday 03 December 2005 05:53 pm, [EMAIL PROTECTED] wrote:
> On Saturday 03 December 2005 07:19 pm, Keith C wrote:
> > >>>> Please post the entire section of dmesg that pertains to ivtv, as
> > >>>> well as any options you used.
> > >>>>
> > >>>> Keith C
> > >>>
> > >>> Hmm, I'm not sure what you mean by options. I'm on Gentoo and these
> > >>> are my
> > >>> "USE" flags:
> > >>> 3dnow 3dnowext -gnome -gtk aac a52 alsa acpi apache2 audiofile avi
> > >>> browserplugin cdr qt divx4linux -doc dvb dvd dvdr dvdread ethereal
> > >>> java kde
> > >>> lirc live mad mmx mmxext matroska mpeg mysql mythtv nas network
> > >>> ncurses
> > >>> quicktime real samba spell sse theora transcode truetype usb videos
> > >>> win32codecs wmf X xosd xvid pda pic
> > >>>
> > >>> complete dmesg output pertaining to ivtv:
> > >>>
> > >>> ivtv:  version 0.4.0 (tagged release) loading
> > >>> ivtv:  Linux version: 2.6.13.4 gcc-3.4
> > >>> ivtv:  In case of problems please include the debug info
> > >>> ivtv:  between the START INIT IVTV and END INIT IVTV lines when
> > >>> ivtv:  mailing the ivtv-devel mailinglist.
> > >>> ivtv0: Autodetected WinTV PVR 350 card (iTVC15 based)
> > >>> ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ
> > >>> 185
> > >>> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> > >>> lirc_i2c: chip found @ 0x18 (Hauppauge IR)
> > >>> ivtv0: i2c attach to card #0 ok [client=Hauppauge IR, addr=18]
> > >>> lirc_dev: lirc_register_plugin: sample_rate: 10
> > >>> ivtv0: Failed to load module tveeprom
> > >>> ivtv0 warning: i2c client addr: 0x50 not found for command 0x0!
> > >>> ivtv0: Error -19 reading Hauppauge eeprom.
> > >>> ivtv0: Possible causes: the tveeprom module was not loaded, or
> > >>> ivtv0: the eeprom kernel module was loaded before the tveeprom
> > >>> module.
> > >>
> > >> Module options are anything in modprobe.conf, or added to the
> > >> modprobe command, like modprobe ivtv debug=1.  It sounds liek you
> > >> don't have any.
> > >>
> > >> So let's look at what the module is telling us.  Either it can't find
> > >> the tveeprom module, or the eeprom module was either loaded first or
> > >> built into the kernel.
> > >>
> > >> Try the following :
> > >>
> > >> lsmod | grep eeprom
> > >> modinfo eeprom
> > >> modinfo tveeprom
> > >>
> > >> And we'll see where stuff is.
> > >>
> > >> Keith C
> > >
> > > In /etc/modprobe.conf I just have:
> > > alias char-major-81-0 ivtv
> > > alias char-major-81-1 ivtv
> > > alias char-major-61-* lirc_i2c
> >
> > This is good.
> >
> > > lsmod | grep eeprom gives me nothing
> > >
> > > modinfo eeprom:
> > > modinfo: could not find module eeprom
> >
> > These are good.
> >
> > > modinfo tveeprom:
> > > parm:           force:List of adapter,address pairs to boldly
> > > assume to be
> > > present
> > > parmtype:       force:array of short
> > > parm:           ignore:List of adapter,address pairs not to scan
> > > parmtype:       ignore:array of short
> > > parm:           probe:List of adapter,address pairs to scan
> > > additionally
> > > parmtype:       probe:array of short
> > > parm:           debug:Debug level (0-2)
> > > parmtype:       debug:int
> > > license:        GPL
> > > author:         John Klar
> > > description:    i2c Hauppauge eeprom decoder driver
> > > depends:        i2c-core
> > > vermagic:       2.6.13.4 gcc-3.4
> >
> > Also good.
> >
> > OK, guess we need to check to see if eeprom or tveeprom are compiled
> > into the kernel.
> >
> > I usually do this :
> >
> > cat /boot/config-`uname -r` | grep EEPROM
> >
> > But I'm not 100% sure that works in Gentoo.  This is another option :
> >
> > cat /lib/modules/`uname -r`/build/.config | grep EEPROM
> >
> > What you should see is that both eeprom and tveeprom are compiled as
> > modules (m).
> >
> > Keith C
>
> Hmm, cat /lib/modules/`uname -r`/build/.config | grep EEPROM:
> # CONFIG_SENSORS_EEPROM is not set
> CONFIG_VIDEO_TVEEPROM=m
>
> I'll set eeprom as a module and recompile, is that my problem?
>

To answer my own question; it seems that having eeprom loaded as a module does 
nothing. Anyone have any sort of suggestion as to what I can try or maybe 
where I went wrong? Could someone please post what needs to be loaded as 
modules in the kernel so I can double check?

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

Reply via email to