RE: TV Tuner

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,
How can I know where is the tv tuner located. I checked /dev/video0-4, tried changing the devices in tvtime, no change.
How can I find which /dev file is represending the tv tunr.
There is also a device file called vttuner. I tried to change the device to that on tvtime.
Still no change.


Renjoy K Henry
Technical Consultant
Phone: 080-51221111; Extn: 81360
Mobile: +91-9886378820


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of [email protected]
Sent: Tuesday, September 14, 2004 10:30 PM
To: [email protected]
Subject: fedora-list Digest, Vol 7, Issue 149

Send fedora-list mailing list submissions to
	[email protected]

To subscribe or unsubscribe via the World Wide Web, visit
	http://www.redhat.com/mailman/listinfo/fedora-list
or, via email, send a message with subject or body 'help' to
	[email protected]

You can reach the person managing the list at
	[email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of fedora-list digest..."


Today's Topics:

   1. Re: Please help: TV Tuner card ([email protected])
   2. Re: Please help: TV Tuner card (Michael Gargiullo)
   3. Re: FC2 not working properly (Alexander Dalloz)
   4. Re: Disk problem (James Wilkinson)
   5. Re: Please help: TV Tuner card (Alexander Dalloz)
   6. Re: problem with php dependency (Jim Patterson)
   7. Re: Please help (Alexander Dalloz)
   8. Re: file creation date (James Wilkinson)
   9. Re: Installing Linux (Rainer)
  10. tcopy (Will McCorkle)
  11. Re: Minolta Magicolor 2350EN printer (Dr. Michael J. Chudobiak)
  12. Re: Minolta Magicolor 2350EN printer (Keith Lofstrom)
  13. Freed up space, now what? (Mark Haney)


----------------------------------------------------------------------

Message: 1
Date: Tue, 14 Sep 2004 21:41:51 +0530
From: <[email protected]>
Subject: Re: Please help: TV Tuner card
To: <[email protected]>
Message-ID:
	<[email protected]>
Content-Type: text/plain; charset="us-ascii"

Skipped content of type multipart/alternative-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1447 bytes
Desc: image001.jpg
Url : /archives/fedora-list/attachments/20040914/13961d16/attachment.jpg

------------------------------

Message: 2
Date: Tue, 14 Sep 2004 12:19:06 -0400
From: Michael Gargiullo <[email protected]>
Subject: Re: Please help: TV Tuner card
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain

Some cards just don't work correctly

Where is this device listed?  /dev/what?

I have a Haupaggue winTV PVR - works beautifully at /dev/video0

What happens if you cat /dev/video0 > test.mpg

Have you looked at /dev/video0-4 ?

On Tue, 2004-09-14 at 12:11, [email protected] wrote:
> I am pasting the messages I got .
> 
> The file /etc/syconfig/hwconf gives the message:
> 
> class: OTHER
> 
> bus: PCI
> 
> detached: 0
> 
> driver: saa7134
> 
> desc: "Philips Semiconductors|SAA7130 Video Broadcast Decoder"
> 
> vendorId: 1131
> 
> deviceId: 7130
> 
> subVendorId: 18d0
> 
> subDeviceId: 2100
> 
> pciType: 1
> 
> pcidom: 0
> 
> pcibus: 0
> 
> pcidev: 8
> 
> pcifn: 0
> 
>  
> 
> When I do an lspci I get this message for the card:
> 
>  
> 
> 00:08.0 Multimedia controller: Philips Semiconductors SAA7130 Video
> Broadcast Decoder (rev 01)
> 
>  
> 
> [[email protected] saa7134]# pwd
> 
> /usr/src/linux-2.6.5-1.358/drivers/media/video/saa7134
> 
> [[email protected] saa7134]# ls
> 
> Makefile saa7134-cards.c saa7134.h saa7134-input.c saa7134-
> 
> reg.h saa7134-tvaudio.c saa7134-video.c
> 
> saa6752hs.c saa7134-core.c saa7134-i2c.c saa7134-oss.c saa7134-
> 
> ts.c saa7134-vbi.c
> 
>  
> 
> I think the drivers are installed properly for the TV tuner card. The
> kernel is 2.6.5-1.358 Fedora Core 2.
> 
>  
> 
> But the tvtime is not able to detect the device since it looks by
> default to the device /dev/video0.
> 
> Also it says only a particular set of drivers are supported by tvtime.
> 
>  
> 
> What should I do to make this working.
> 
>  
> 
>  
> 
> Renjoy K Henry
> Technical Consultant
> Phone: 080-51221111; Extn: 81360
> Mobile: +91-9886378820
> 
>  
> 
>  
> 
> 
> 
> ______________________________________________________________________
> -- 
> fedora-list mailing list
> [email protected]
> To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list




------------------------------

Message: 3
Date: Tue, 14 Sep 2004 18:21:48 +0200
From: Alexander Dalloz <[email protected]>
Subject: Re: FC2 not working properly
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-15"

Am Di, den 14.09.2004 schrieb Julien Le Houérou um 17:10:

> Hi, i juste upgraded to 2.6.8-1.521smp, with the brand new video drivers
> from nvidia (6111), and it remains the hell :

[ snip ]

> Julien Le Houérou

I wonder how often we will see this mail on this list. Now it is 3 times
with subject lines:

"Gnome not working after upgrade"  11:36
"Help !"  15:25
"FC2 not working properly" 17:10

I deeply feel you should rethink your posting behaviour :(

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp 
Serendipity 18:18:09 up 15 days, 15:34, load average: 0.34, 1.17, 1.30 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : /archives/fedora-list/attachments/20040914/d08350ba/attachment.bin

------------------------------

Message: 4
Date: Tue, 14 Sep 2004 17:24:55 +0100
From: James Wilkinson <[email protected]>
Subject: Re: Disk problem
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Alexander Dalloz wrote:
> Either the drive /dev/hdc is dieing or it has a problem with DMA.

... or there's a cable problem, or there's a problem with the IDE
adapter. I've got a motherboard with a dodgy IDE adapter that's only fit
for CD-ROMs that throws that problem occasionally.

The adapter is a HighPoint device on the PCI bus: the on-board IDE ports
work fine, so I haven't replaced it.

James.

-- 
E-mail address: james |  ... File not found, I'll load something *I* think
@westexe.demon.co.uk  |  is interesting.




------------------------------

Message: 5
Date: Tue, 14 Sep 2004 18:35:30 +0200
From: Alexander Dalloz <[email protected]>
Subject: Re: Please help: TV Tuner card
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Am Di, den 14.09.2004 schrieb [email protected] um 18:11:

> driver: saa7134
> 
> desc: "Philips Semiconductors|SAA7130 Video Broadcast Decoder"

So it is a supported hardware.

> When I do an lspci I get this message for the card:

> 00:08.0 Multimedia controller: Philips Semiconductors SAA7130 Video
> Broadcast Decoder (rev 01)

> I think the drivers are installed properly for the TV tuner card. The
> kernel is 2.6.5-1.358 Fedora Core 2.

First of all, update your kernel to the latest version. The kernel ships
with the driver module needed:

$ /sbin/modinfo saa7134
description:    v4l2 driver module for saa7130/34 based TV cards
author:         Gerd Knorr <[email protected]> [SuSE Labs]
license:        GPL
parm:           irq_debug:enable debug messages [IRQ handler]
parm:           core_debug:enable debug messages [core]
parm:           gpio_tracking:enable debug messages [gpio]
parm:           video_nr:video device number
parm:           ts_nr:ts device number
parm:           vbi_nr:vbi device number
parm:           radio_nr:radio device number
parm:           oss:register oss devices (default: no)
parm:           dsp_nr:oss dsp device number
parm:           mixer_nr:oss mixer device number
parm:           tuner:tuner type
parm:           card:card type
parm:           latency:pci latency timer
parm:           i2c_debug:enable debug messages [i2c]
parm:           i2c_scan:scan i2c bus at insmod time
parm:           oss_debug:enable debug messages [oss]
parm:           oss_rate:sample rate (valid are: 32000,48000)
parm:           ts_debug:enable debug messages [ts]
parm:           tsbufs:number of ts buffers, range 2-32
parm:           ts_nr_packets:size of a ts buffers (in ts packets)
parm:           audio_debug:enable debug messages [tv audio]
parm:           audio_ddep:audio ddep overwrite
parm:           audio_clock_tweak:Audio clock tick fine tuning for cards
with audio crystal that's slightly off (range [-1024 .. 1024])
parm:           vbi_debug:enable debug messages [vbi]
parm:           vbibufs:number of vbi buffers, range 2-32
parm:           video_debug:enable debug messages [video]
parm:           gbuffers:number of capture buffers, range 2-32
parm:           noninterlaced:video input is noninterlaced
parm:           disable_ir:disable infrared remote support
parm:           ir_debug:enable debug messages [IR]
vermagic:       2.6.8-1.521smp SMP 686 REGPARM 4KSTACKS gcc-3.3
depends:       
i2c-core,ir-common,video-buf,videodev,v4l2-common,soundcore,v4l1-compat

> But the tvtime is not able to detect the device since it looks by
> default to the device /dev/video0.

After rebooting with the current kernel load the driver with modprobe if
it is not loaded automatically (lsmod shows you).

/dev/video0 is the default video device tvtime accesses, right. That is
no problem. If your TV card runs on a different video device use the
proper parameter for tvtime. "man tvtime" and "tvtime --help" should
always be the first steps.

-d, --device=DEVICE        video4linux device (defaults to /dev/video0).

> Also it says only a particular set of drivers are supported by tvtime.

Don't know. A google search should help. Else try out xawtv which is for
instance packaged for FC by ATrpms.net.

> Renjoy K Henry

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp 
Serendipity 18:26:10 up 15 days, 15:42, load average: 0.50, 0.67, 0.99 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : /archives/fedora-list/attachments/20040914/85edf0fa/attachment.bin

------------------------------

Message: 6
Date: Tue, 14 Sep 2004 11:42:20 -0500
From: Jim Patterson <[email protected]>
Subject: Re: problem with php dependency
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Alexander Dalloz wrote:

>Am Sa, den 11.09.2004 schrieb Alexander Dalloz um 22:20:
>
>  
>
>>>rpm -Uvh php*sybase*.rpm
>>>error: Failed dependencies:
>>>        libcomn.so is needed by php-4.3.2-11.1.ent.sybase
>>>        libcs.so is needed by php-4.3.2-11.1.ent.sybase
>>>        libct.so is needed by php-4.3.2-11.1.ent.sybase
>>>        libintl.so is needed by php-4.3.2-11.1.ent.sybase
>>>        libsybtcl.so is needed by php-4.3.2-11.1.ent.sybase
>>>      
>>>
>
>Btw. this RPM 4.3.2-11.1 is rather old. I hardly doubt it is security
>fixed to latest state. I really hope you know what you are doing.
>
>Alexander
>
>
>  
>
Thanks for the info.  This is an internal system and I'm basically 
recompiling with different configuration.  I wanted to start with a 
version that I know works and has worked with other databases.  Once I 
get this one working I'll configure another system with the latest 
updates and get it working.  I'm just trying to minimize debug issues, 
between version and configuration.

Thanks
Jim




------------------------------

Message: 7
Date: Tue, 14 Sep 2004 18:41:00 +0200
From: Alexander Dalloz <[email protected]>
Subject: Re: Please help
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="us-ascii"

Am Di, den 14.09.2004 schrieb Pavel R um 18:45:

> >Simply unreadable. My Gnome PDF viewer shows nothing but crappy signs.

> Alexander, try using any other pdf viewer. There is a known problem with 
> gnome pdf viewer displaying garbage.

Thanks for the hint, ggv displays the PDF properly.

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13
Fedora GNU/Linux Core 2 (Tettnang) kernel 2.6.8-1.521smp 
Serendipity 18:39:47 up 15 days, 15:56, load average: 0.46, 0.73, 0.85 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : /archives/fedora-list/attachments/20040914/7b64fd06/attachment.bin

------------------------------

Message: 8
Date: Tue, 14 Sep 2004 17:42:31 +0100
From: James Wilkinson <[email protected]>
Subject: Re: file creation date
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Michael Griffin wrote:
> How do I display/retrieve the date a file was created (using bash
> shell)?

You don't: not portably across filesystem types, anyway. Sorry.

There are three times kept in a Unix-type filesystem: the access time
(atime: when someone last "read" the file's contents), the modification
time (mtime, the last time someone wrote to the file's contents), and
the status change time (ctime, when someone last changed things like
permissions or filename: the "meta-data" stored by the filesystem
about the file).

You use ls -l for the modification time, ls -lu for the access time,
and ls -lc for the status time.

File creation date is not recorded. It may be the same as the mtime or
the ctime, or it may not.

Having said all that, some non-native filesystems supported by Linux
keep this data. I'm not aware of any way of getting it, though.

James.

-- 
E-mail address: james | "The US Air Force is removing harmful "greenhouse"
@westexe.demon.co.uk  | gases from the cooling systems of intercontinental
                      | ballistic missiles. This will minimise damage to the
                      | ozone layer in the event of a nuclear holocaust."
                      |     -- The Guardian.




------------------------------

Message: 9
Date: Tue, 14 Sep 2004 12:49:03 -0400
From: Rainer <[email protected]>
Subject: Re: Installing Linux
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii; format=flowed

looks possibly like bad ram. went through this lately. try memtest86 and 
put your ram in, one at a time in bank1 and do the test thoroughly for 
each stick. i was impatient and it delayed my diagnosis by a week. also 
check the minimum requirements for a graphical install - you seem to be 
a little on the low side. good luck




------------------------------

Message: 10
Date: Tue, 14 Sep 2004 11:52:29 -0500
From: "Will McCorkle" <[email protected]>
Subject: tcopy
To: <[email protected]>
Message-ID:
	<[email protected]xx>
Content-Type: text/plain; charset="us-ascii"

I have recently been given the dubious task of copying a bunch of 8mm
exabyte tapes. I have gotten fc2 to recognize the Mammoth drives I have
installed, but there is no way I know of to do tape to tape copy. I
found a copy of tcopy compiled for Linux, but it is 2 years old and
doesn't seem to work. Any suggestions on an alternate software to copy
tape to tape would be wonderful. 

 

Thank You

Will McCorkle

Systems Administrator

DG Systems

[email protected]

972-581-2119

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: /archives/fedora-list/attachments/20040914/7acb2e98/attachment.htm

------------------------------

Message: 11
Date: Tue, 14 Sep 2004 12:54:19 -0400
From: "Dr. Michael J. Chudobiak" <[email protected]>
Subject: Re: Minolta Magicolor 2350EN printer
To: For users of Fedora Core releases <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Actually, the 2350EN seems to works OK from CUPS if I connect using 
socket://myprinter instead of http://myprinter/ipp. So something about 
the combination of CUPS + IPP + 2350EN is the problem.

CUPS + Appsocket (port 9100) + 2350EN is fine.

- Mike



> Hi,
> 
> Has anyone gotten the Minolta Magicolor 2350EN network color laser 
> printer to work with FC1?




------------------------------

Message: 12
Date: Tue, 14 Sep 2004 09:57:33 -0700
From: Keith Lofstrom <[email protected]>
Subject: Re: Minolta Magicolor 2350EN printer
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii


Mike writes:
> Has anyone gotten the Minolta Magicolor 2350EN network color laser
> printer to work with FC1?

At an off-site client, about a year ago, I was able to get Redhat 9
and CUPS working with a Minolta QMS Magicolor 2200 .  I remember some
issues involving the correct printer driver.  I used the ZjStream printer
driver, which claims to drive the 2300 printers.  Another issue was
getting the IP address right ("what's an IP address?" said the Windoze
maintainer).

Other associated buzzwords for your googling pleasure may be foo2zjs,
JBIG, and Zenographics.   The printer is still configured, though not
used;  I can look up more things in the appropriate config files, if
you tell me which files you want examined.  And if you fly me down
to my clients in San Jose, I can re-test it there ;-).

Sorry that I don't remember more, but perhaps that helps.

Keith

-- 
Keith Lofstrom          [email protected]         Voice (503)-520-1993
KLIC --- Keith Lofstrom Integrated Circuits --- "Your Ideas in Silicon"
Design Contracting in Bipolar and CMOS - Analog, Digital, and Scan ICs




------------------------------

Message: 13
Date: Tue, 14 Sep 2004 12:58:41 -0400
From: Mark Haney <[email protected]>
Subject: Freed up space, now what?
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain

Okay, I freed up resized my ntfs partition to give me more room for FC2
since I was close to running out, but now what?  How do I add that space
to an existing partition, which is preferable?  Or would it make more
sense to just partition it and mount separately?


--------------------------------------
Mark Haney
Network Administrator
InterAct Public Safety Systems
[email protected]
Fedora Core release 2 (Tettnang) Kernel: 2.6.8-1.521 GNU/Linux 
12:57:04 up 3 min, 1 user, load average: 0.99, 0.68, 0.27 




------------------------------

--
fedora-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/fedora-list


End of fedora-list Digest, Vol 7, Issue 149
*******************************************



[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]
  Powered by Linux