Thanks for the offer of assistance. I am getting only static when I do a test capture with the PVR350. There is no sound, just simply a blizzard of static in the window. I am only using my monitor right now. I figure that I better get the thing working on the monitor before I worry about TV. :) I also have no idea what is going on with the remote. Whenever I try to see if I'm getting any signal using irw, I get a connection refused. A remote hasn't been my biggest worry yet though. I'd like to see some TV before I worry about sitting back on the couch! I've included info from dmesg below. If you need any other info for troubleshooting, please let me know, and I will get it to you ASAP. Thanks alot for your help.

ivtv: ==================== START INIT IVTV ====================
ivtv: version 0.2.0 (rc3e) loading
ivtv: Linux version: 2.4.26
ivtv: In case of problems please include the debug info
ivtv: between the START INIT IVTV and END INIT IVTV lines when
ivtv: mailing the ivtv-devel mailinglist.
ivtv: Autodetected WinTV PVR 350 card
ivtv: Found an iTVC15 based chip
ivtv: Unreasonably low latency timer, setting to 64 (was 32)
ivtv: XXX PCI device: 0x1130 vendor: 0x8086
ivtv: i2c attach [client=Philips NTSC (FI1236,FM1236 and,ok]
i2c-core.o: client [Philips NTSC (FI1236,FM1236 and] registered to adapter [ivtv i2c driver #0](pos. 0).
ivtv: i2c attach [client=saa7127[0],ok]
i2c-core.o: client [saa7127[0]] registered to adapter [ivtv i2c driver #0](pos. 1).
msp34xx: ivtv version
ivtv: i2c attach [client=MSP3448W-A2,ok]
i2c-core.o: client [MSP3448W-A2] registered to adapter [ivtv i2c driver #0](pos. 2).
i2c-core.o: adapter ivtv i2c driver #0 registered as adapter 0.
ivtv: i2c attach [client=tveeprom[0],ok]
i2c-core.o: client [tveeprom[0]] registered to adapter [ivtv i2c driver #0](pos. 3).
ivtv: Tuner Type 47, Tuner formats 0x00001000, Radio: yes, Model 0x00ad2598, Revision 0x00000001
ivtv: NTSC tuner detected
ivtv: Radio detected
saa7115: starting probe for adapter ivtv i2c driver #0 (0x10005)
ivtv: i2c attach [client=saa7115[0],ok]
i2c-core.o: client [saa7115[0]] registered to adapter [ivtv i2c driver #0](pos. 4).
ivtv: Encoder revision: 0x02050032
ivtv: Encoder Firmware is buggy, use version 0x02040011
ivtv: Decoder revision: 0x02020023
ivtv: Configuring WinTV PVR 350 card with 9 streams
ivtv: Create DMA stream 0 using 256 16384 byte buffers 4194304 kbytes total
ivtv: Registered v4l2 device, streamtype 0 minor 0
ivtv: Create DMA stream 1
ivtv: Registered v4l2 device, streamtype 1 minor 32
ivtv: Create stream 2 using 40 52224 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 2 minor 224
ivtv: Create DMA stream 3 using 455 4608 byte buffers 2097152 kbytes total
ivtv: Registered v4l2 device, streamtype 3 minor 24
ivtv: Create stream 4
ivtv: Registered v4l2 device, streamtype 4 minor 64
ivtv: Create DMA stream 5 using 16 65536 byte buffers 1048576 kbytes total
ivtv: Registered v4l2 device, streamtype 5 minor 16
ivtv: Create stream 6 using 1024 2048 byte buffers 262144 kbytes total
ivtv: Registered v4l2 device, streamtype 6 minor 228
ivtv: Create stream 7
ivtv: Registered v4l2 device, streamtype 7 minor 232
ivtv: Create DMA stream 8
ivtv: Registered v4l2 device, streamtype 8 minor 48
ivtv: Setting Tuner 47
ivtv: Setting audio matrix to input 3, output 1
ivtv: Switching standard to NTSC.
ivtv: ivtv_enc_thread: pid = 1452, itv = 0xe0a0b7e0
ivtv: ivtv_dec_thread: pid = 1453, itv = 0xe0a0b7e0
ivtv: Initialized WinTV PVR 350, card #0
ivtv: ==================== END INIT IVTV ====================
ivtv: i2c attach [client=Hauppauge IR,ok]
i2c-core.o: client [Hauppauge IR] registered to adapter [ivtv i2c driver #0](pos. 5).
ivtv: ENC: User stopped capture.




lirc info


[EMAIL PROTECTED]:~$ dmesg |grep lirc lirc_dev: IR Remote Control driver registered, at major 61 lirc_i2c: chip found @ 0x18 (Hauppauge IR) lirc_dev: lirc_register_plugin:sample_rate: 10 [EMAIL PROTECTED]:~$ irw connect: Connection refused

btw...if you're seeing this twice, it's because I replied to the copy of the message not realizing that that went straight to you and not the list.

Shaun

On Monday, February 14, 2005, at 07:45 PM, Vidal Sainz wrote:

The link you included is a pretty good howto for getting Myth running on Slackware. If you used that then Myth is probably installed correctly, you just needs to get your hardware working right.

If you describe the problems you are having, I might be able to walk you through it.



[EMAIL PROTECTED] wrote:

Hey Matt,

I greatly appreciate the ready to go package library for Slackware. I decided to go with Slackware too when I first got into Linux. It's been a tough uphill learning curve, but sadistically, I have fun doing it. I have hit road blocks in set up while attempting to use instructions I found for setting up a Myth system on Slack 9.1. Since you are also using Slack and a newer version at that..do you have anything written up for step by step instructions on how to get everything working? I feel like there is just a small item missing from the existing instructions, but with my limited knowledge, don't know how to pinpoint it. These are the instructions I used. When you installed 10.1, did you keep the kernel at 2.4.29, or did you upgrade the kernel?

http://home.comcast.net/~homebrewracing/Mythtv.txt
thanks Shaun



List,

I maintain my own slackware packages to make updating software and rebuilding servers easier.

I have just recently started building slackware 10.1 packages and also built the latest release of myth.

I figured I would post a link so that anyone on the list that also wants to use the packages can:

http://www.aptalaska.net/~matt.s/mythtv/

For people new to slackware and linux, slackware is a very simple distribution that uses minimal amounts of patching, kernel.org kernels, and leaves out complex things that are not required for myth (and many other applications) such as pam.

Installing slackware 10.1, qt, blackbox, and the packages at the site above will quickly yield a functional myth box with minimal complexity.

Enjoy,
schu

-- "Life is tough, but it's tougher when you're stupid" -- John Wayne
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



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

_______________________________________________

mythtv-users mailing list

[email protected]

http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users



-- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.



On Monday, February 14, 2005, at 07:45 PM, Vidal Sainz wrote:

The link you included is a pretty good howto for getting Myth running on Slackware. If you used that then Myth is probably installed correctly, you just needs to get your hardware working right.

If you describe the problems you are having, I might be able to walk you through it.



[EMAIL PROTECTED] wrote:

Hey Matt,

I greatly appreciate the ready to go package library for Slackware. I decided to go with Slackware too when I first got into Linux. It's been a tough uphill learning curve, but sadistically, I have fun doing it. I have hit road blocks in set up while attempting to use instructions I found for setting up a Myth system on Slack 9.1. Since you are also using Slack and a newer version at that..do you have anything written up for step by step instructions on how to get everything working? I feel like there is just a small item missing from the existing instructions, but with my limited knowledge, don't know how to pinpoint it. These are the instructions I used. When you installed 10.1, did you keep the kernel at 2.4.29, or did you upgrade the kernel?

http://home.comcast.net/~homebrewracing/Mythtv.txt
thanks Shaun



List,

I maintain my own slackware packages to make updating software and rebuilding servers easier.

I have just recently started building slackware 10.1 packages and also built the latest release of myth.

I figured I would post a link so that anyone on the list that also wants to use the packages can:

http://www.aptalaska.net/~matt.s/mythtv/

For people new to slackware and linux, slackware is a very simple distribution that uses minimal amounts of patching, kernel.org kernels, and leaves out complex things that are not required for myth (and many other applications) such as pam.

Installing slackware 10.1, qt, blackbox, and the packages at the site above will quickly yield a functional myth box with minimal complexity.

Enjoy,
schu

--
"Life is tough, but it's tougher when you're stupid" -- John Wayne
_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


_______________________________________________
mythtv-users mailing list
[email protected]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Reply via email to