🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.linux.hardware
7 messages
7 total messages Started by Eyal Lebedinsky Sun, 29 Nov 1998 00:00
problems with TV tuner
#272
Author: Eyal Lebedinsky
Date: Sun, 29 Nov 1998 00:00
105 lines
4853 bytes
Relevant configuration:
        2.1.129 kernel
        #9GXEPro PCI (S3 964 based).
        Teppro TV Tuner/Video Capture TEV560.

I am installing a TV tuner, and so far I sorted most
problems. I have two issues unresolved:

1) The sound volume control has no effect, and the mute (A) key
works in reverse. I tried all card types and tuner types and
so far I found card=3 to work best, and tuner type=1 gives
best sound.

2) I cannot use the framebuffer, which should produce the best
performance (if I understood it right).

Starting xawtv (which causes the modules to load) fails to
locate the linear framebuffer (see messages below).

Specifying "options bttv vidmem=0xf30" does not help, the
result is that overlay mode is accepted but now I get a
black screen (with good sound).

Note that X11 says "Linear FB @ 0x00000000" but later it
also says "Local bus LAW is 0xF3000000". If I use the S3
driver "MemBase 0xf3000000" option then the last message
changes to "Local bus LAW is 0xF30xxxxx" but I still get
a black screen.


The messages at xawtv startup are:
==================================

x11: 1600x1200, 16 bit/pixel, 3200 byte/scanline, DGA, VidMode
v4l: device is BT848(STB)
v4l: 1600x1200, 16 bit/pixel, 3200 byte/scanline
WARNING: v4l and dga disagree about the framebuffer base
WARNING: you probably want to insmod the bttv module with "vidmem=0xf30"
WARNING: overlay mode disabled

The X11 Server messages:
========================

XFree86 Version 3.3.2.3 / X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date: July 15 1998
        If the server is older than 6-12 months, or if your card is newer
        than the above date, look for a newer version before reporting
        problems.  (see http://www.XFree86.Org/FAQ)
Operating System: Linux 2.0.35 i686 [ELF] 
Configured drivers:
  S3: accelerated server for S3 graphics adaptors (Patchlevel 0)
      newmmio, mmio_928, s3_generic
(using VT number 7)

XF86Config: //XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) Mouse: type: Microsoft, device: /dev/mouse, baudrate: 1200
(**) Mouse: buttons: 3, 3 button emulation (timeout: 50ms)
(**) S3: Graphics device ID: "#9"
(**) S3: Monitor ID: "VS"
(**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Ty
pe1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6
/lib/X11/fonts/100dpi/"
(--) S3: PCI: 964 rev 0, Linear FB @ 0x00000000
(--) S3: chipset:   964 rev. 0
(--) S3: chipset driver: mmio_928
(**) S3: Option "number_nine"
(**) S3: Option "power_saver"
(--) S3: card type: PCI
(**) S3: videoram:  4096k
(--) S3: Detected a TI ViewPoint 3025 RAMDAC
(**) S3: Ramdac type: ti3025
(**) S3: Ramdac speed: 220 MHz
(--) S3: Using hardware cursor from Ti3020/25 RAMDAC
(**) S3: Using TI 3025 programmable clock (MCLK 54.982 MHz)
(--) S3: Setting MCLK to 55.000 MHz for #9GXE64 Pro
(--) S3: Maximum allowed dot-clock: 220.000 MHz
(**) S3: Mode "1600x1200": mode clock = 175.000
(**) S3: Mode "1600": mode clock = 170.000
(**) S3: Mode "1280x1024": mode clock = 135.000
(**) S3: Mode "1024x768": mode clock =  80.000
(**) S3: Mode "800x600": mode clock =  50.000
(**) S3: Mode "640x480": mode clock =  31.500
(**) S3: Mode "320x240": mode clock =  16.000
(--) S3: One or more modes require pixel multiplexing and
        the hardware is incapable of switching between mux/non-mux
        modes. All modes will be re-evaluated under the new constraint.
(**) S3: Mode "1600x1200": mode clock = 175.000
(**) S3: Mode "1600": mode clock = 170.000
(**) S3: Mode "1280x1024": mode clock = 135.000
(**) S3: Mode "1024x768": mode clock =  80.000
(**) S3: Mode "800x600": mode clock =  50.000
(**) S3: Mode "640x480": mode clock =  31.500
(**) S3: Mode "320x240": mode clock =  16.000
(--) S3: Operating RAMDAC in pixel multiplex mode
(**) S3: Using 16 bpp.  Color weight: 565
(**) S3: Virtual resolution set to 1600x1200
(--) S3: Local bus LAW is 0xF3000000
(--) S3: Using a banksize of 4096k, line width of 1600
(--) S3: Using a single 64x64 area at (1536,1200) for expanding pixmaps
(--) S3: Using 16 planes of 1536x110 at (0,1200) aligned 8 as font cache

--
Eyal Lebedinsky		(eyal@eyal.emu.id.au)
Re: problems with TV tuner
#273
Author: Grahame M. Kelly
Date: Sun, 29 Nov 1998 00:00
66 lines
3248 bytes
> Relevant configuration:
>         2.1.129 kernel
>         #9GXEPro PCI (S3 964 based).
>         Teppro TV Tuner/Video Capture TEV560.
> 
> 
> 1) The sound volume control has no effect, and the mute (A) key
> works in reverse. I tried all card types and tuner types and
> so far I found card=3 to work best, and tuner type=1 gives
> best sound.
> 
> 2) I cannot use the framebuffer, which should produce the best
> performance (if I understood it right).
> 
> Starting xawtv (which causes the modules to load) fails to
> locate the linear framebuffer (see messages below).
> 
> Specifying "options bttv vidmem=0xf30" does not help, the
> result is that overlay mode is accepted but now I get a
> black screen (with good sound).

Eyal

I have just got my TVCard working.

1> I am running 2.1.130 kernel, xawtv-2.31 (just released yesterday)
   and I have configured the kernel with video4linux as modules only.

2> Go to the xawtv-2.30/bttv/ and do make insmod, this will build a new
   bttv, videodev, tuner, i2c and other misc drivers.
   Also replaces the /lib/modules/2.1.130/misc/ drivers with these.
   The kerenl video4linux modules are older than the xawtv release.

3> Don't forget to do MAKEDEV to create the new devices in /dev tree.

4> manually, insmod videodev, i2c, bttv, tuner together with the options
   needed for your card, (see xawtv-2.31/bttv/driver/MODULES fro details).

5> For sound I had to make a stereo patch plug (male to male) and
   put one end into the TV Card (audio out) and the other into the
   SoundBlaster (line-in) port. I control the volume, tone etc by
   Xmixer.

On my SMP system I had to ensure that there was a symbolic link
(ln -s /new-kernel/linux-2.1.130 /usr/src/linux) so that the normal
/usr/src/linux directory pointed to the system includes files correctly.
You may / may not have to do this.

After this, all as OK. The only other interesting experience was one
of the TV cards had a faulty tuner for VHF stations. Once I swapped it
the VHF stations were there but very iffy, further investigations proved
the incoming RF signal was too low. I move to a better outlet (I got 5)
and everything now works great. I have a 1"x1" composite video camera
outside watching possums (PossumCAM) with IR lighting. Works well, only
have to select Composite video on xawtv control panel.

Hope this helps you,
Cheers Grahame.

Then you should be OK. I have had to play around to get my card working
(Its a Mr.Vision TVLink Card). 
 
-- 
Member Sydeny Linux Users Group (SLUG)
AntiSpamming enabled. 
REAL email address is => gmkelly (AT) zip (DOT) com (DOT) au
Re: problems with TV tuner
#269
Author: Mike McBain
Date: Mon, 30 Nov 1998 00:00
27 lines
2231 bytes
not-for-mail@dare.demon.nl (Pieter Krul) writes:

>I still believe quite strongly that the only medium which Linux can't
>talk through are smoke-signals.

Not true! Getting the blanket to flap properly is the easy part. You can do
Morse quite quickly, although bandwidth is limited by the need to space
the dots and dashes and the problems of high winds. The real bugbear, and the
one that the LSSP (Linux Smoke Signal Project) has yet to adequately solve,
is the fire mechanism. We're aiming at unattended fire operation. The fire needs 
to be smoky, but not *too* smoky or it goes out. So we need a smokiness sensor
which can blow more air in if needed, add fuel if it's getting low, and adds
grass and leaves if it's not smoky enough.

There's a lag problem, though. When the fire gets going, and is not smoky, you
can't send messages, but it's a UDP connection with unreliable end-to-end
connectivity, so you may lose important parts of the message and not know it.
If the fire is too smoky, the signals are obscured in the 'noise' and you have
to pump up the fire.

Anyway, at least we don't have a problem with bugs.

-- 
Mike McBain                                 Faculty of Business & Economics
mjm@silas.cc.monash.edu.au                  Monash University - Clayton
+61 3 9905 2336                             Australia    3168
*** No junk mail please - I will hunt you down
Re: problems with TV tuner
#274
Author: Nick Coleman
Date: Mon, 30 Nov 1998 00:00
35 lines
2124 bytes
Grahame M. Kelly wrote:
> 
> > Relevant configuration:
> >         2.1.129 kernel
> >         #9GXEPro PCI (S3 964 based).
> >         Teppro TV Tuner/Video Capture TEV560.
> >
[snip]
> After this, all as OK. The only other interesting experience was one
> of the TV cards had a faulty tuner for VHF stations. Once I swapped it
> the VHF stations were there but very iffy, further investigations proved
> the incoming RF signal was too low. I move to a better outlet (I got 5)
> and everything now works great. I have a 1"x1" composite video camera
> outside watching possums (PossumCAM) with IR lighting. Works well, only
                                       ^^^^^^^^^^^^^^^^
                                       very impressive! 

> have to select Composite video on xawtv control panel.
> 
> Hope this helps you,
> Cheers Grahame.
> 
> Then you should be OK. I have had to play around to get my card working
> (Its a Mr.Vision TVLink Card).
> 
> --
> Member Sydeny Linux Users Group (SLUG)
> AntiSpamming enabled.
> REAL email address is => gmkelly (AT) zip (DOT) com (DOT) au

I'd no idea you could do this with Linux!  Is this easy and cheap?  Can
you give an idea how much the cards are?

Thanks,
Nick.
Re: problems with TV tuner
#275
Author: Pieter Krul
Date: Mon, 30 Nov 1998 00:00
24 lines
1609 bytes
Nick Coleman wrote:
>Grahame M. Kelly wrote:
[snip]
>> outside watching possums (PossumCAM) with IR lighting. Works well, only
>                                       ^^^^^^^^^^^^^^^^
>                                       very impressive! 
>
>I'd no idea you could do this with Linux!  Is this easy and cheap?  Can
>you give an idea how much the cards are?

As said by somebody before:

I still believe quite strongly that the only medium which Linux can't
talk through are smoke-signals.

Regards,

Pieter

-- 
This machine runs Linux 2.0.36 on a Pentium II (Deschutes).
It has 256872 kB memory, and was down for backups from
10:01 am to 10:02 am last Saturday. It said "PURGE COMPL     ".
Is it necessary to reboot now and if so, how can this be done ?
Re: problems with TV tuner
#270
Author: jedi
Date: Wed, 02 Dec 1998 00:00
48 lines
2478 bytes
On Mon, 30 Nov 1998 10:22:35 +1100, Nick Coleman <nicholas.coleman@ssmb.com.au> wrote:
>Grahame M. Kelly wrote:
>> 
>> > Relevant configuration:
>> >         2.1.129 kernel
>> >         #9GXEPro PCI (S3 964 based).
>> >         Teppro TV Tuner/Video Capture TEV560.
>> >
>[snip]
>> After this, all as OK. The only other interesting experience was one
>> of the TV cards had a faulty tuner for VHF stations. Once I swapped it
>> the VHF stations were there but very iffy, further investigations proved
>> the incoming RF signal was too low. I move to a better outlet (I got 5)
>> and everything now works great. I have a 1"x1" composite video camera
>> outside watching possums (PossumCAM) with IR lighting. Works well, only
>                                       ^^^^^^^^^^^^^^^^
>                                       very impressive! 
>
>> have to select Composite video on xawtv control panel.
>> 
>> Hope this helps you,
>> Cheers Grahame.
>> 
>> Then you should be OK. I have had to play around to get my card working
>> (Its a Mr.Vision TVLink Card).
>> 
>> --
>> Member Sydeny Linux Users Group (SLUG)
>> AntiSpamming enabled.
>> REAL email address is => gmkelly (AT) zip (DOT) com (DOT) au
>
>I'd no idea you could do this with Linux!  Is this easy and cheap?  Can
>you give an idea how much the cards are?

	It's the camera...

	...the 848/878 are video overlay cards.

	Just feed it any video signal, tune it in and do the
	video capture (gui or command line)...

	Peruse the page below for a screen shot.

-- 
Unix had  startmenus and taskbars before Microsoft         |||
even had a decent memory manager for DOS.                 / | \

	In search of sane PPP docs? Try http://penguin.lvcm.com
Re: problems with TV tuner
#271
Author: Grahame M. Kelly
Date: Wed, 02 Dec 1998 00:00
39 lines
2118 bytes
> 
> 	It's the camera...
> 
> 	...the 848/878 are video overlay cards.
> 
> 	Just feed it any video signal, tune it in and do the
> 	video capture (gui or command line)...
> 
> 

Original problem with being able to get UHF TV stations bit not
VHF stations has been resolved. The problem is/was in Australia we
have RF line sockets (usually on a flying lead) that have a centre
pin of 2.4mm diag, whereas the Philips tuners (and probably most
others) have a centre female accepting a 3.2mm diag plug. This
0.8mm difference therefore doesn't make a DC contact, but acts
as a capacitor of approx 10pf (my guess) and measurements I have
done indicate that I get a input signal loss of 10-20db (channel
dependent). So on my system, in my location, I has able to get
UHF (signal strength was 60db input) and not VHF (where signal 
strength was only 32db). Solution: Got a Coax TV plug to RCA
socket adapter (Tandy #PA3675 - A$2.75) and put this component
inline before the tuner. Be aware to not push the RCA plug in too
far because it somes lose or touches an internal tuner coil which
may effect reception.


TV Camera was CCIR standard going directly to the composite video
port of the BT848 card. 

Grahame

-- 
Member Sydeny Linux Users Group (SLUG)
Website = http://www.slug.org.au
Mailing List = slug@slug.org.au

AntiSpamming enabled. 
REAL email address is => gmkelly (AT) zip (DOT) com (DOT) au
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads