View previous topic :: View next topic |
Author |
Message |
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Sun Jun 26, 2005 11:36 pm Post subject: Win TV in Gentoo |
|
|
Hi
There are no drivers for my WinTV Go TV Card for Windows XP x64. What are the chances of getting it working in AMD64 Gentoo?
If there is any chance, how would I go about it?
Thanks for your time
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
Fredde Tux's lil' helper
Joined: 08 Feb 2005 Posts: 98
|
Posted: Mon Jun 27, 2005 6:48 am Post subject: |
|
|
Hi!
WinTV Go uses the bttv driver. You also have to enable i2c and video4linux in the kernel. |
|
Back to top |
|
|
m707 Tux's lil' helper
Joined: 31 Oct 2003 Posts: 121 Location: Germany
|
Posted: Mon Jun 27, 2005 1:13 pm Post subject: |
|
|
Fredde wrote: | WinTV Go uses the bttv driver. You also have to enable i2c and video4linux in the kernel. |
Nes .
Unfortunately Hauppage is one of that companies that change specs without changing the
brand name . Old versions of the Win TV Go were equipped with the bttv8x8, however, the
never ones use the cx88 chip.
lspci should give you a hint, which driver to choose. _________________ bye maik |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Mon Jun 27, 2005 2:52 pm Post subject: |
|
|
If I get this working I'm likely to ditch Windows XP x64 and move to Gentoo...
OK, I googled as well as reading your posts (aren't I a good boy? ) and I've enabled the right stuff in the kernel I think.
gentoo jim # lspci -v | grep -i video
0000:02:06.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
There is some weird stuff in dmesg
cx88[0]/0: AUD_STATUS: 0x772 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x732 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x772 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x6f2 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x772 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x732 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x672 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x772 [mono/no pilot] ctl=BTSC_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0x6b2 [mono/no pilot] ctl=BTSC_AUTO_STEREO
this goes on and on many times
So is this a good sign, or a bad sign?
What software package should I merge to test the tuner?
Thanks!
Jim
Edit: If I press Alt-F12 (which I assume is where the real time logging goes --> noob alert) the cx88[0]/0 stuff is appearing every second, is there a way to turn off this status reporting every second? It's going to surely fill my log files?! _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
m707 Tux's lil' helper
Joined: 31 Oct 2003 Posts: 121 Location: Germany
|
Posted: Tue Jun 28, 2005 8:44 am Post subject: |
|
|
In line with your lspci output your card is indeed equiped with a cx88 chip.
In spite the author claims his information outdated I would start here
http://www-users.york.ac.uk/~jcs116/wintv_cx88.html
AFAIK the cx88 driver still has some issues and if you fail I would advise to use newest source
from
http://linux.bytesex.org/v4l2/drivers.html
and try if that fixes the situation.
The most cx88 tv-cards have a stereo audio chip, but IIRC the WinTV Go is just mono. I suppose
that the driver is looking for stereo chip as it is more common and while failing to get such device
it is messing your logs.
Unfortunately I am not that familiar with this driver and I dunno if there is a flag to tell it to stop
searching for stereo devices, but probably you can find someting useful in the v4l mailing list archives.
Good luck. _________________ bye maik |
|
Back to top |
|
|
bdamon n00b
Joined: 27 Feb 2004 Posts: 5 Location: Rochester NY
|
Posted: Tue Jun 28, 2005 7:06 pm Post subject: |
|
|
fatboyjim wrote: |
There is some weird stuff in dmesg
cx88[0]/0: AUD_STATUS: 0x772 [mono/no pilot] ctl=BTSC_AUTO_STEREO
So is this a good sign, or a bad sign?
What software package should I merge to test the tuner?
|
It has been a while since I messed with these cards but here is what I recall:
The flag I used to stop the logging and get my WinTV Radio card to work is
modprobe cx8800 tuner=43 audio_debug=0
Run lsmod and see what modules are loaded you may be using the cx88xx module.
Your tuner may vary but the audio_debug=0 should stop the logging messages.
I used Tvtime to watch tv.
Ben |
|
Back to top |
|
|
ipic Guru
Joined: 29 Dec 2003 Posts: 383 Location: UK
|
Posted: Wed Jun 29, 2005 3:01 pm Post subject: |
|
|
m707 wrote: |
AFAIK the cx88 driver still has some issues and if you fail I would advise to use newest source
from
http://linux.bytesex.org/v4l2/drivers.html
and try if that fixes the situation.
The most cx88 tv-cards have a stereo audio chip, but IIRC the WinTV Go is just mono. I suppose
that the driver is looking for stereo chip as it is more common and while failing to get such device
it is messing your logs.
|
The V4l2 drivers went through a quiet patch when Gerd Knor resigned as Kernel maintainer, but there is plenty activity again now. However, the link given above is out of date - you should go to http://linuxtv.org/v4lwiki/index.php/Main_Page to get the latest, including quite good instructions on how to get and build the latest CVS copies.
Also, I see you are in the UK, so you are in luck - PAL-I on this chip supports Stereo. But, you need to fiddle a bit to get it. The messages you see come from the drivers trace on every sample of the chip. As previously posted, you need Code: | modprobe cx88xx audio_debug=0 | to switch it off. I would suggest creating a specific module file in /etc/modules.d to keep your module settings in. I have one called /etc/modules.d/wintv and its contents are: Code: | alias char-major-81 videodev
alias char-major-81-0 cx8800
options cx88xx audio_debug=0 core_debug=0 ir_debug=0 i2c_debug=0
options tda9887 port1=1 port2=0 pal=i debug=0
options tveeprom debug=0
options tuner tuner_debug=0 pal=i
| Whenever you change this file you need to run to generate the /etc/modules.conf file.
Last bit of work - you have to ensure that your TV application is forcing the PAL-I TV norm. PAL is not good enough - it defaults to PAL-BG in the driver and you get static as sound. You need an application called xawtv installed, so and this gives you some commands to drive the v4l interface directly. The way I do it is to start tvtime, then from command line enter Code: | v4lctl setnorm PAL-I | and then switch tvtime channels up and down.
As an alternative, use mplayer, which allows you to set the TV norm from the command line. If you are a beginner you may find the mplayer documentaton a little bit daunting though!
Finally, you may need to work with your mixer settings a bit, to make sure that the TV card to Sound card connection is being picked up correctly.
Hope this helps.
Regards
Ian
Last edited by ipic on Wed Jun 29, 2005 9:19 pm; edited 1 time in total |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Wed Jun 29, 2005 6:05 pm Post subject: |
|
|
Cheers, will give it a go when I get home _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
crazycat l33t
Joined: 26 Aug 2003 Posts: 838 Location: Hamburg, Germany
|
Posted: Wed Jun 29, 2005 8:40 pm Post subject: |
|
|
don't forget to load v4l module in your xorg.conf file. |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Thu Jun 30, 2005 8:58 pm Post subject: |
|
|
OK, I'm clearly doing something wrong here
I've built "Conexant 2388x (bt878 successor) support" into the Kernel
Code: | v4lctl setnorm PAL-I |
Gives me
v4l2: open /dev/video0: No such file or directory
v4l2: open /dev/video0: No such file or directory
v4l: open /dev/video0: No such file or directory
no grabber device available
And right enough, there is no /dev/video0... _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Thu Jun 30, 2005 9:20 pm Post subject: |
|
|
Oh OK, it's not doing that any more
I can't seem to tune the television properly... I'm sure I'll work it out soon enough
Trying to input from my VCR on both Composite and S-Video results in Black and White on the screen which is annoying, need it in colour really
Any ideas?
Cheers
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
ipic Guru
Joined: 29 Dec 2003 Posts: 383 Location: UK
|
Posted: Thu Jun 30, 2005 9:50 pm Post subject: |
|
|
fatboyjim wrote: |
I can't seem to tune the television properly... I'm sure I'll work it out soon enough
Trying to input from my VCR on both Composite and S-Video results in Black and White on the screen which is annoying, need it in colour really
|
You didn't say which version of the kernel you are using. would be useful to know. If its not 2.6.12, the cx88 module will not be up to date, an will not tune TV correctly.
Even if its 2.6.12, it will not be up to date. If you look at the v4l wiki reference I gave above, you will see one page devoted to building the V4l modules from their CVS site. I strongly recommend that you do that - it will most likely solve your TV problem.
As for black and white, have you tried adjusting colour, contrast and hue? Especially hue, which has to be 100% or 0% to work on cx88 v4l drivers before 28th June 2005. (The V4l CVS changelog will show you when that change appeared).
Regards
Ian |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Thu Jun 30, 2005 10:46 pm Post subject: |
|
|
Code: | gentoo jim # uname -r
2.6.11-gentoo-r11 |
It's an amd64 system and 2.6.12 is masked
Turning hue down to 0 fixed the colour problem, thanks for that (and sorry I didn't read up on that before!)
Just rebooting with new kernel options and drivers from CVS
Thanks for your help, it is appreciated.. haven't been using linux long <as you may be able to tell;)> _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Thu Jun 30, 2005 11:01 pm Post subject: |
|
|
Hmmm, OK. Removed the card from being built into the kernel.
Built the modules from cvs as per the instructions and made them available to the OS (make install)
linuxtv.org wrote: | 6) Now you can install the driver you need into the OS. All of them in CVS were built.
My particular driver needs:
modprobe -v cx8800
modprobe -v cx88-dvb |
Are those the drivers I need to be modprobing? I get errors on both
Code: |
gentoo jim # modprobe -v cx8800
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/btcx-risc.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/v4l1-compat.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/video-buf.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx88xx.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx8800.ko
FATAL: Error inserting cx8800 (/lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx8800.ko): Unknown symbol in module, or unknown parameter (see dmesg)
|
It would seem this is the relevant part of dmesg
Code: | kobject_register failed for btcx_risc (-17)
Call Trace:<ffffffff8014ad00>{param_get_int+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff8014ad00>{param_get_int+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
kobject_register failed for v4l1_compat (-17)
Call Trace:<ffffffff8014ad00>{param_get_int+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff8014ad00>{param_get_int+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
kobject_register failed for video_buf (-17)
Call Trace:<ffffffff80175760>{alloc_pages_current+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff80175760>{alloc_pages_current+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
kobject_register failed for cx88xx (-17)
Call Trace:<ffffffff8013df70>{__request_region+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff8013df70>{__request_region+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
cx8800: Unknown symbol cx88_core_irq
cx8800: Unknown symbol cx88_newstation
|
Trying to modprobe the second module brings even more errors, but I doubt I need it seeing as the -dvb module is for digital television.. correct?
Code: |
gentoo jim # modprobe -v cx88-dvb
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/video-buf.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/video-buf-dvb.ko
WARNING: Error inserting video_buf_dvb (/lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/video-buf-dvb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/btcx-risc.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx88xx.ko
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx8802.ko
WARNING: Error inserting cx8802 (/lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx8802.ko): Unknown symbol in module, or unknown parameter (seedmesg)
insmod /lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx88-dvb.ko
FATAL: Error inserting cx88_dvb (/lib/modules/2.6.11-gentoo-r11/kernel/drivers/media/video/cx88/cx88-dvb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
|
Again dmesg spews out a lot of stuff
Code: | kobject_register failed for video_buf (-17)
Call Trace:<ffffffff80175760>{alloc_pages_current+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff80175760>{alloc_pages_current+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
video_buf_dvb: Unknown symbol dvb_dmxdev_init
video_buf_dvb: Unknown symbol dvb_register_adapter
video_buf_dvb: Unknown symbol dvb_dmx_release
video_buf_dvb: Unknown symbol dvb_net_init
video_buf_dvb: Unknown symbol dvb_dmx_swfilter
video_buf_dvb: Unknown symbol dvb_dmxdev_release
video_buf_dvb: Unknown symbol dvb_net_release
video_buf_dvb: Unknown symbol dvb_unregister_frontend
video_buf_dvb: Unknown symbol dvb_register_frontend
video_buf_dvb: Unknown symbol dvb_unregister_adapter
video_buf_dvb: Unknown symbol dvb_dmx_init
kobject_register failed for btcx_risc (-17)
Call Trace:<ffffffff8014ad00>{param_get_int+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff8014ad00>{param_get_int+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
kobject_register failed for cx88xx (-17)
Call Trace:<ffffffff8013df70>{__request_region+0} <ffffffff80260f46>{kobject_register+70}
<ffffffff8013df70>{__request_region+0} <ffffffff80151c78>{load_module+5624}
<ffffffff8014d899>{remove_wait_queue+25} <ffffffff80278bac>{write_chan+876}
<ffffffff8047eafa>{thread_return+42} <ffffffff80272584>{tty_ldisc_deref+116}
<ffffffff80272cb9>{tty_write+633} <ffffffff8017bddf>{vfs_write+287}
<ffffffff80151fa7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
cx8802: Unknown symbol cx88_core_irq
cx88_dvb: Unknown symbol videobuf_dvb_unregister
cx88_dvb: Unknown symbol videobuf_dvb_register
|
It would appear the the driver is getting installed at boot time anyway?? Seeing as I am still receiving the
Code: | cx88[0]/0: AUD_STATUS: 0xe1a6 [mono/pilot c1] ctl=A2_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0xe1b2 [mono/no pilot] ctl=A2_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0xe1ba [mono/pilot c2] ctl=A2_AUTO_STEREO
cx88[0]/0: AUD_STATUS: 0xe1f2 [mono/no pilot] ctl=A2_AUTO_STEREO |
sort of messages in dmesg every second or two
How would I go about stopping it from being loaded at boot, because I clearly haven't told it to do this.. it isn't in modules.autoload.d either
Thanks for your time
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Thu Jun 30, 2005 11:34 pm Post subject: |
|
|
OK we're nearly there. Turned out earlier errors were because I didn't copy the kernel over to /boot! So the card was still built into the kernel
Silly me..
Right. So I did
This is the dmesg output for that
Code: |
kobject_register failed for v4l1_compat (-17)
Call Trace:<ffffffff8014ad10>{param_get_int+0} <ffffffff80260f76>{kobject_register+70}
<ffffffff8014ad10>{param_get_int+0} <ffffffff80151c88>{load_module+5624}
<ffffffff8014d8a9>{remove_wait_queue+25} <ffffffff80278c2c>{write_chan+876}
<ffffffff8047d7da>{thread_return+42} <ffffffff802725b4>{tty_ldisc_deref+116}
<ffffffff80272ce9>{tty_write+633} <ffffffff8017be0f>{vfs_write+287}
<ffffffff80151fb7>{sys_init_module+119} <ffffffff8010e4ca>{system_call+126}
cx2388x v4l2 driver version 0.0.4 loaded
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI interrupt 0000:02:06.0[A] -> GSI 18 (level, low) -> IRQ 209
cx88[0]: subsystem: 0070:3401, board: Hauppauge WinTV 34xxx models [card=1,autodetected]
TV tuner -1 at 0x1fe, Radio tuner -1 at 0x1fe
tveeprom: Hauppauge: model = 34705, rev = J198, serial# = 2930320
tveeprom: tuner = <unknown> (idx = 98, type = -32512)
tveeprom: tuner fmt = PAL(D/K) (eeprom = 0x50, v4l2 = 0x00000e10)
tveeprom: audio_processor = MSP3425 (type = 15)
cx88[0]: registered IR remote control
cx88[0]/0: found at 0000:02:06.0, rev: 5, irq: 209, latency: 32, mmio: 0xe7000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
|
It all seems to be OK but I'm slightly concerned about tuner= <unknown>
TVTime still doesn't work properly, we're in colour now no probs.. but still cant tune
Too tired to think about it now so going to bed
Cheers
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
ipic Guru
Joined: 29 Dec 2003 Posts: 383 Location: UK
|
Posted: Fri Jul 01, 2005 8:14 am Post subject: |
|
|
There appear to be two problems.
First one is that the v4l1_compat has failed to load. Personally, I have never seen this one. It may be something to do with AMD64, or something wrong in the way you built the drivers. If you are sure you followed the wiki instructions for build (including the kernel options), I'd suggest googling around to see if it comes up, and failing that search the v4l mailing list archives http://marc.theaimsgroup.com/?l=linux-video and failing that join the mailing list and ask for help.
It may be that this is not important, but I fear that applications may be using the v4l API, rather than the V4l2 API, and without this module some applications may not work correctly.
Second one looks like you have to play hunt the tuner, thanks to Hauppage's approach to changing chips & tuners but keeping model numbers the same. The cx88xx module has a parameter called 'tuner'. You can make it consider different tuner types by giving it tuner type number on each load. For example: Code: | options cx88xx tuner=38 [other optons] | will set the tuner type on load to the Philips PAL/SECAM multi (FM1216ME MK3). A list of tuner types can be found here http://linuxtv.org/v4lwiki/index.php/Tuners and also in the documentation directory of the v4l CVS copy you downloaded.
If you are changing module parameters, you have to make sure that all the v4l modules are unloaded before you modprobe with the new setting. The surest way to do this is a reboot - but many people object to that. If you do a modprobe after a clean reboot, and do lsmod before and after the modprobe, you should be able to work out which modules were loaded by v4l. Alternatively, remove anything that matches a name in the v4l source tree.
Rather than go through all 45 tuners one by one, I found it easier to (very carefully) pull off the white Hauppage sticker from the silver tuner box on the card. Undeneath that you will find the original makers model number, which is very likely to match something in the list.
Should you find one that works, it would be nice to post it to the v4l mailing list so they can update the autodetection code.
Regards
Ian |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Fri Jul 01, 2005 11:22 am Post subject: |
|
|
I am tempted to unmask the unstable kernel and see if that makes a difference...
Will try doing what you've posted when I get back from work, thanks again _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Fri Jul 01, 2005 10:11 pm Post subject: |
|
|
If I
Code: | modprobe cx88xx tuner=1 |
or just
Then it all appears to work, but TVTime says "No signal"
I need to
for it to work at all
It would seem that v42l_common module only gets loaded when I modprobe cx8800 .. it does NOT get loaded when I probe simply cx88xx
If I modprobe v42l_common manually it still doesn't work, until I load cx8800
OK, hope that made _some_ sense!
Still unable to tune, I imagine this is because the tuner hasn't been detected,as you said earlier. Here comes the next problem
Code: | modprobe -v cx8800 tuner=1 |
dmesg: cx8800: Unknown parameter `tuner'
We're getting there... slowly... right? _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
ipic Guru
Joined: 29 Dec 2003 Posts: 383 Location: UK
|
Posted: Fri Jul 01, 2005 10:46 pm Post subject: |
|
|
Maybe - you do need to read the previous posts more carefully.
The tuner option is on cx88xx - NOT cx8800.
Earlier I saaid to create a /etc/modules.d file for the options. If you do that, and set the options there, then when you do the modprobe you might stand a chance.
And tuner=1 doesn't stand a chance of working.
Regards
Ian |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Fri Jul 01, 2005 11:06 pm Post subject: |
|
|
I assume I need to rebuild the cvs stuff every time I rebuild the kernel? It doesn't appear to work otherwise
I created the options file, that's fine
ipic wrote: |
The tuner option is on cx88xx - NOT cx8800. |
If I Code: | modprobe cx88xx tuner=38 | then TVTime doesn't work (no signal), as I said earlier. I have to modprobe cx8800 afterwards to get anything to come up in TVTime. Although I think this is the normal behaviour
Thanks for putting up with me
EDIT: I've decided to go hunt the tuner... as discussed earlier.
Code: | modprobe -v cx88xx tuner=XXX
modprobe -v cx8800 |
This all goes through with no errors. TVTime is full of static, with signal detection turned on I get a blue screen, with it turned off I'm unable to tune, all channels look the same anyway, static
EDIT2: I've now gone through all of the Philips tuner=XX options and no joy with any of them. I went for the Philips ones as under the white sticker there was a small chip with a philips logo... although I get the feeling this may not have been the tuner chip and I'll have to rip that metal casing off the tuner part of the board.
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
ipic Guru
Joined: 29 Dec 2003 Posts: 383 Location: UK
|
Posted: Sat Jul 02, 2005 9:21 pm Post subject: |
|
|
One more thing to try, it may help pin the tuner down.
Do this: Code: | modprobe tda9887
dmesg | and then see if a message like this appears in the dmesg output: Code: | tda9885/6/7: chip found @ 0x86 |
If it does, you have some more options before you start hacking code.
Regards
Ian |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Mon Jul 04, 2005 6:13 pm Post subject: |
|
|
nope, gives me no dmesg output
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
fatboyjim Apprentice
Joined: 12 Jul 2004 Posts: 227 Location: UK
|
Posted: Thu Jul 28, 2005 7:30 pm Post subject: |
|
|
Bump, I've tried using the kernel drivers just now and still have no luck
Anyone else who can help me?
Thanks
Jim _________________ -----------------------
fatboyjim
Gentoo/AMD64 Arch Tester (Inactive) |
|
Back to top |
|
|
|