On Mon, 2005-08-01 at 12:24 +1000, Ross wrote:
> On 8/1/05, Richard Röjfors <[EMAIL PROTECTED]> wrote:
> > This is my /etc/modprobe.d/ivtv
> > 
> > options ivtv tda9887=0 ivtv_std=2 cardtype=6 tuner=55 radio=0
> 
> Are all of these needed? What happens if you specify no module
> options? Cardtype and ivtv_std shouldn't be needed, neither should
> tuner (but this obviously isn't getting detected correctly).

Actually I had a hardware problem with my last card. It was randomly
detected as a 150 or 250. Thats why I leaved them there..

I removed the options and it was correctly detected as a 150, but the
tuner is still detected like this:

tveeprom: Hauppauge: model = 26034, rev = C197, serial# = 7886509
tveeprom: tuner = <unknown> (idx = 97, type = 0)
tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x44, v4l2 = 0x00000e07)
tveeprom: audio_processor = MSP3400C (type = 4)

> 
> Do you have device alias lines? ie:
> alias char-major-81 videodev
> alias char-major-81-0 ivtv

Yes when I want the modules automatically loaded...

> 
> Can you give some more information:
> What do you see from lspci -v? What distro are you running? Custom or
> prebuilt kernel? What hardware (motherboard/cpu)?

This is what lspci -v gives me:

0000:02:0d.0 Multimedia video controller: Internext Compression Inc
iTVC16 (CX23416) MPEG-2 Encoder (rev 01)
        Subsystem: Hauppauge computer works Inc.: Unknown device 8003
        Flags: bus master, medium devsel, latency 64, IRQ 209
        Memory at f4000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [44] Power Management version 2

I'm using debian sarge, unstable. I have built my own 2.6.11 kernel with
debian patches..

CPU is a 2,5 GHz Celeron clocked down to like 1,9 GHz or something...

Motherboard is a Asus AS8 or something, don't really remember the
correct name of it...


> 
> > > I agree, it seems to be using and old version of tveeprom.
> > 
> > Ooops, but how can that happen? Isn't the one bundled with ivtv the
> > correct to use?
> 
> Yes
> 
> > > > tveeprom: tuner = <unknown> (idx = 97, type = 0)
> > >
> > > It's not detecting the tuner correctly for starters
> > 
> > Nope it has never done. I checked other peoples postings and found that
> > tuner type 55 should apply to my card.
> 
> I think this shows a deeper problem.
> 
> > > tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x44, v4l2 = 0x00000e07)
> 
> > The tveeprom.ko I use is the one provided by ivtv, right now ivtv 0.3.7a
> > 
> > [EMAIL PROTECTED]:~/src/ivtv-0.3.7a/driver$ sudo modinfo tveeprom
> > filename:       /lib/modules/2.6.11-myth/ivtv/tveeprom.ko
> 
> You are correct, I was misunderstanding the tveeprom output. Is your
> card a PAL D/K only card? (I didn't know they were made) Or is
> tveeprom making another mistake?

Hmm I'm not in to these different pal-standards. But it truly a PAL
card, I think we have something called PAL-B in sweden(?) And the card
is bought here and shall work with our tv standards..


Any ideas!?

/Richard



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
ivtv-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ivtv-devel

Reply via email to