headers
hermann pitton | 1 Sep 2005 01:34
Picon

Re: saa7134 card - which one do I have?

Am Donnerstag, den 01.09.2005, 08:50 +1000 schrieb Ryan Heise:
> On Thu, Sep 01, 2005 at 08:36:42AM +1000, Ryan Heise wrote:
> > # mv /lib/modules/2.6.11-1-686/kernel/drivers/media /tmp
> > # echo "2.6.11-1.686" > .version
> > (for some reason it was detected as only "2.6.11")
> > # make install
> > # modprobe saa7134-dvb
> 
> Oops - videodev is now in /tmp.
> 
> To fix this, I tried:
> 
> # rm -rf /lib/modules/2.6.11-1-686/kernel/drivers/media
> # cp -r /tmp/media /lib/modules/2.6.11-1-686/kernel/drivers
> # echo "2.6.11-1.686" > .version
> # make install
> # modprobe saa7134-dvb
> 
> Now I get:
> 
> Sep  1 08:45:19 localhost kernel: Linux video capture interface: v1.00
> Sep  1 08:45:19 localhost kernel: saa7130/34: v4l2 driver version 0.2.14 loaded
> Sep  1 08:45:19 localhost kernel: PCI: Enabling device 0000:05:00.0 (0000 -> 0002)
> Sep  1 08:45:19 localhost kernel: ACPI: PCI interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 169
> Sep  1 08:45:19 localhost kernel: saa7134[0]: found at 0000:05:00.0, rev: 1, irq: 169, latency: 0, mmio: 0x20400000
> Sep  1 08:45:19 localhost kernel: saa7134[0]: subsystem: 16be:0003, board: Medion 7134 [card=12,autodetected]
> Sep  1 08:45:19 localhost kernel: saa7134[0]: board init: gpio is 0
> Sep  1 08:45:19 localhost kernel: saa7134[0]: i2c eeprom 00: be 16 03 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92
> Sep  1 08:45:19 localhost kernel: saa7134[0]: i2c eeprom 10: 00 ff 86 0f ff 20 ff 00 01 50 32 79 01 3c ca 50
> Sep  1 08:45:19 localhost kernel: saa7134[0]: i2c eeprom 20: 01 40 01 02 02 03 01 00 06 ff 00 1f 02 51 96 2b
(Continue reading)

Permalink | Reply | 13 comments |
headers
Ryan Heise | 1 Sep 2005 01:53
Picon
Picon
Favicon

Re: saa7134 card - which one do I have?

On Thu, Sep 01, 2005 at 01:34:16AM +0200, hermann pitton wrote:
> What you have done looks OK, but try from the snapshot again "make
> install" and after that again "make v4l_install". That deletes all in
> known places except "upgrade" and such and puts them all
> in /lib/modules/uname -r/v4l2. (except unchanged videodev)
> 
> modprobe -v tuner
> modprobe -v tda9887
> modprobe -v tda1004x
> modprobe -v saa7134-dvb

Here is the output under 2.6.11:

# modprobe -v tuner
insmod /lib/modules/2.6.11-1-686/v4l2/tuner.ko
# modprobe -v tda9887
insmod /lib/modules/2.6.11-1-686/v4l2/tda9887.ko
# modprobe -v tda1004x
insmod /lib/modules/2.6.11-1-686/v4l2/tda1004x.ko
# modprobe -v saa7134-dvb
insmod /lib/modules/2.6.11-1-686/v4l2/video-buf.ko
insmod /lib/modules/2.6.11-1-686/kernel/drivers/media/dvb/dvb-core/dvb-core.ko
insmod /lib/modules/2.6.11-1-686/v4l2/video-buf-dvb.ko
insmod /lib/modules/2.6.11-1-686/kernel/drivers/media/video/videodev.ko
insmod /lib/modules/2.6.11-1-686/v4l2/ir-common.ko
insmod /lib/modules/2.6.11-1-686/v4l2/v4l1-compat.ko
insmod /lib/modules/2.6.11-1-686/v4l2/v4l2-common.ko
insmod /lib/modules/2.6.11-1-686/v4l2/saa7134.ko
insmod /lib/modules/2.6.11-1-686/v4l2/mt352.ko
insmod /lib/modules/2.6.11-1-686/v4l2/saa7134-dvb.ko
(Continue reading)

Permalink | Reply | 10 comments |
headers
hermann pitton | 1 Sep 2005 02:08
Picon

Re: saa7134 card - which one do I have?

[...]
> 
> That should show if anything is left in unexpected places,
> often comes up firstly after a reboot.
> 
> If that still doesn't work, also on your 2.6.12, we might have to
> investigate the hardware.

By the way, just in case, since you said you would like to keep your
2.6.11 specials. Is there other fancy stuff like some irregular/up-
downgraded/patched i2c ?

Hermann

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 1 comment |
headers
Ryan Heise | 1 Sep 2005 01:57
Picon
Picon
Favicon

Re: saa7134 card - which one do I have?

On Thu, Sep 01, 2005 at 02:08:28AM +0200, hermann pitton wrote:
> By the way, just in case, since you said you would like to keep your
> 2.6.11 specials. Is there other fancy stuff like some irregular/up-
> downgraded/patched i2c ?

I'm using alsa-1.0.9:

$ find /lib/modules/2.6.11-1-686/updates -name '*i2c*'
/lib/modules/2.6.11-1-686/updates/alsa/i2c
/lib/modules/2.6.11-1-686/updates/alsa/i2c/snd-i2c.ko

Ryan

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 0 comments |
headers
hermann pitton | 1 Sep 2005 02:22
Picon

Re: saa7134 card - which one do I have?

Am Donnerstag, den 01.09.2005, 09:53 +1000 schrieb Ryan Heise:
> On Thu, Sep 01, 2005 at 01:34:16AM +0200, hermann pitton wrote:
> > What you have done looks OK, but try from the snapshot again "make
> > install" and after that again "make v4l_install". That deletes all in
> > known places except "upgrade" and such and puts them all
> > in /lib/modules/uname -r/v4l2. (except unchanged videodev)
> > 
> > modprobe -v tuner
> > modprobe -v tda9887
> > modprobe -v tda1004x
> > modprobe -v saa7134-dvb
> 
> Here is the output under 2.6.11:
> 
> # modprobe -v tuner
> insmod /lib/modules/2.6.11-1-686/v4l2/tuner.ko
> # modprobe -v tda9887
> insmod /lib/modules/2.6.11-1-686/v4l2/tda9887.ko
> # modprobe -v tda1004x
> insmod /lib/modules/2.6.11-1-686/v4l2/tda1004x.ko
> # modprobe -v saa7134-dvb
> insmod /lib/modules/2.6.11-1-686/v4l2/video-buf.ko
> insmod /lib/modules/2.6.11-1-686/kernel/drivers/media/dvb/dvb-core/dvb-core.ko
> insmod /lib/modules/2.6.11-1-686/v4l2/video-buf-dvb.ko
> insmod /lib/modules/2.6.11-1-686/kernel/drivers/media/video/videodev.ko
> insmod /lib/modules/2.6.11-1-686/v4l2/ir-common.ko
> insmod /lib/modules/2.6.11-1-686/v4l2/v4l1-compat.ko
> insmod /lib/modules/2.6.11-1-686/v4l2/v4l2-common.ko
> insmod /lib/modules/2.6.11-1-686/v4l2/saa7134.ko
> insmod /lib/modules/2.6.11-1-686/v4l2/mt352.ko
(Continue reading)

Permalink | Reply | 9 comments |
headers
Ryan Heise | 1 Sep 2005 02:38
Picon
Picon
Favicon

Re: saa7134 card - which one do I have?

On Thu, Sep 01, 2005 at 02:22:13AM +0200, hermann pitton wrote:
> We might have to go through the hardware, every single chip, every
> single print on the PCB and its devices, also to enable debug like
> previously told might give hints for missing/changed i2c addresses.

Which debug parameters of which modules should I set?

Thanks,

Ryan

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request <at> redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
Permalink | Reply | 8 comments |
headers
Dante Passalacqua | 1 Sep 2005 03:12
Picon

Kworld V-Stream Studio TV Terminator - IR remote problem

Hi, I've been trying to get all the features of the  'Kworld V-Stream
Studio TV Terminator' card to work, and thanks to the posts of many of
you guys, so far I've

* TV: Video Ok, Audio Ok
* TV Tuner: works with tvtime, Cable 100+ channels, NTSC HRC
frecuencies. All 90+ channels tune ok, except channels 5 and 6
* Composite video: Video Ok, Audio Ok
* S-video: Not tested yet
* Radio: Works with Kradio with frequencies shifted (thanks to Jim Webb)
* IR remote: input layer is present and detects key press, but all give
the same code.

I wander if you guys have had any luck making the remote control work.

I just fetched the latest snapshot at bytesex.org (released this
afternoon) video4linux-20050831-035555.tar.gz, and I tried to follow the
procedure 'How to add remote control support to a card' outlined in
http://www.linuxtv.org/v4lwiki/index.php/Remote_controllers 

So I added a few lines to 'saa7134-input.c'

        case SAA7134_BOARD_KWORLD_TERMINATOR:
                ir_codes     = md2819_codes;
                mask_keycode = 0;
                polling      = 50; // ms 

and 'saa7134-input.c'

        case SAA7134_BOARD_KWORLD_TERMINATOR:
(Continue reading)

Permalink | Reply | 1 comment |
headers
Michael Krufky | 1 Sep 2005 03:19
Gravatar

[BUG] kobject_register failed for ... BT878

Lukas Kasprowicz wrote:
> Hi, Yesterday from irc. I tried your HOWTO, looks working fine, but with gentoo i get following:
> 
>>marina video4linux # scripts/merge-trees.sh
>>creating symlinks
>>patching file Make.config
>>patching file Makefile
>>patching file cx88-dvb.c
>>patching file saa7134-dvb.c
> 
> Looks good :)

Lukas-

Thank you for testing the v4l/dvb tree-merge scripts on your dvb-bt8xx 
board.  I've taken the liberty of cc'ing this to the mailing lists, 
because I don't know exactly how to fix your problem, and it would be a 
good idea to have it posted somewhere public.

>>marina video4linux # make install
>>
>>Eliminating old V4L modules (errors on this step is not a problem)..
>>make: [rminstall] Fehler 1 (ignoriert)
>>
>>
>>Installing new V4L modules at corresponding Kernel dir...
>>install -d /lib/modules/2.6.12-gentoo-r9/kernel/drivers/media/common
>>install -m 644 -c 
>>ir-common.ko /lib/modules/2.6.12-gentoo-r9/kernel/drivers/media/common
>>install -d /lib/modules/2.6.12-gentoo-r9/kernel/drivers/media/dvb/frontends
(Continue reading)

Permalink | Reply | 6 comments |
headers
John Mulligan | 1 Sep 2005 04:50
Picon

cx88 card - Kernel upgrade makes it impossible to change channels

Hi folks,

I've searched the list and the closest thing I found similar to my problem was 
this post:

http://marc.theaimsgroup.com/?l=linux-video&m=109269200430229&w=2

When I went from 2.6.11 to 2.6.13 I lost the ability to change channels.  It 
seems stuck on whatever station it was tuned to before I boot into the newer 
kernel.  I'm not sure how relevant this is but I noticed with the older 
kernel doing a 'v4lctl setfreq <some-big-number>' would cause an message to 
be printed in dmesg, now nothing happens at all. 

This is what I get when the driver loads:

cx2388x v4l2 driver version 0.0.5 loaded
cx88[0]: subsystem: 0070:3401, board: Hauppauge WinTV 34xxx models 
[card=1,autod
etected]
TV tuner 44 at 0x1fe, Radio tuner -1 at 0x1fe
tveeprom: Hauppauge: model = 34132, rev = J158, serial# = 7281385
tveeprom: tuner = Philips FM1236 MK3 (idx = 58, type = 4)
tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000)
tveeprom: audio_processor = MSP3416 (type = 14)
cx88[0]: registered IR remote control
cx88[0]/0: found at 0000:01:08.0, rev: 5, irq: 9, latency: 64, mmio: 
0xfa000000
tda9885/6/7: chip found  <at>  0x86
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
(Continue reading)

Permalink | Reply | 5 comments |
headers
Mauro Carvalho Chehab | 1 Sep 2005 05:14
Picon
Favicon

Re: [PATCH 2.6] I2C: Drop I2C_DEVNAME and i2c_clientname

Em Qua, 2005-08-31 às 13:56 -0700, Greg KH escreveu:
> On Wed, Aug 31, 2005 at 12:34:58PM -0300, Mauro Carvalho Chehab wrote:
> > Em Ter, 2005-08-30 ?s 23:20 +0200, Jean Delvare escreveu:
> > > Hi Mauro,
> > > 
> > > > (...) it would be nice not to have a different I2C
> > > > API for every single 2.6 version :-) It would be nice to change I2C
> > > > API once and keep it stable for a while.
> > 
> > > The Linux 2.6 development model is designed around a relatively fast
> > > move from -mm to Linus' tree, which implies incremental changes all the
> > > time. I'm only doing that.
> > 	It is ok to change code, but, IMHO, API should be more stable.
> 
> I take it you have not read Documentation/stable_api_nonsense.txt yet?
	No I din't :-)
> If not, please do, it shows that what you are asking for will not
> happen.
	I was not asking for a 'stable' one.. but a less variant... anyway, I
can survive with this policy ;-)
> 
> good luck,
> 
> greg k-h
> 
Cheers, 
Mauro.

--
video4linux-list mailing list
(Continue reading)

Permalink | Reply | 0 comments |

Gmane