Author |
Message |
hooverzilla
|
Posted: Mon Sep 20, 2004 9:11 am |
|
Joined: Sun Sep 19, 2004 10:01 pm
Posts: 7
Location:
Ottawa
|
Thank you for the reply. It did help as now I'm able to get to the login screen but unfortunately Xwindow won't start at all.
Here is the result of lspci
Code: 00:09.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
And here is the relevant part of XF86Config-4 Code: Section "Monitor" Identifier "NTSC Monitor" HorizSync 30-68 VertRefresh 50-120 Mode "720x480" #D: 34.563 MHz, H: 37.244 kHz, V: 73.897 Hz DotClock 34.564 HTimings 720 752 840 928 VTimings 480 484 488 504 Flags "-HSync" "-VSync" EndMode EndSection
Section "Device" Identifier "Hauppauge PVR 350 iTVC15 Framebuffer" Driver "ivtvdev"
### change fb1 to whatever number you got in the previous section Option "fbdev" "/dev/fb0"
### change the busid to whatever is reported by lspci. Note that ### output of lspci is hex, so add a preceding "0x" to the BusID BusID "00:09.0" EndSection Section "Screen" Identifier "TV Screen" Device "Hauppauge PVR 350 iTVC15 Framebuffer" Monitor "NTSC Monitor" DefaultDepth 24 DefaultFbbpp 32 Subsection "Display" Depth 24 FbBpp 32 Modes "720x480" EndSubsection EndSection
Section "DRI" Mode 0666 EndSection
Every time XWindow tries to start, I get the no screens found error. It would seems that every time one problem is fixed, I just hit the next one.
Thank you for your help mongo.
|
|
Top |
|
 |
tjc
|
Posted: Mon Sep 20, 2004 11:10 am |
|
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location:
Arlington, MA
|
hooverzilla wrote: Code: ### change the busid to whatever is reported by lspci. Note that ### output of lspci is hex, so add a preceding "0x" to the BusID BusID "00:09.0"
That sure doesn't look like hex to me... Either the comment is wrong or this is one of your problems. I googled for BusID and XF86Config-4 and came up with the following examples. The first one specifies the PCI bus. Code: # For dual head mode, BusID has to be specified! Check this using lspci! BusID "PCI:1:00:0"
Code: Section "Device" Identifier "Generic Video Card" Driver "nv" BusID "PCI:01:00:0" EndSection
Section "Device" Identifier "Generic Video Card1" Driver "ati" BusID "PCI:0:12:0" EndSection
This is the entry from the manual page. Quote: BusID "bus-id" This specifies the bus location of the graphics card. For PCI/AGP cards, the bus-id string has the form PCI:bus:device:function (e.g., "PCI:1:0:0" might be appropriate for an AGP card). This field is usually optional in single-head configurations when using the primary graphics card. In multi-head configurations, or when using a secondary graphics card in a single-head configuration, this entry is mandatory. Its main purpose is to make an unambiguous connection between the device section and the hardware it is representing. This information can usually be found by running the XFree86 server with the -scanpci command line option.
This one shows how to specify in hex. Code: Section "Device" Identifier "Hauppauge PVR 350 iTVC15 Framebuffer" ##Driver "ivtvdev" Driver "fbdev" ### change fb0 to whatever your card grabbed Option "fbdev" "/dev/fb0"
### change the BusID to whatever is reported by lspci, specify it as hex. BusID "00:0x0d.0" EndSection
This one shows that you can use either hex or decimal if you know how to convert properly. Code: Section "Device" Identifier "Hauppauge PVR 350 iTVC15 Framebuffer" Driver "ivtvdev" Option "fbdev" "/dev/fb1" # <-- modify if using another device BusID "PCI:2:10:0" # get the ID with lspci and be carefull to convert the value from hexa to decimal #Rotate and shadow options from fbdev have been removed, ivtvdev does not use it EndSection
|
|
Top |
|
 |
hooverzilla
|
Posted: Mon Sep 20, 2004 12:43 pm |
|
Joined: Sun Sep 19, 2004 10:01 pm
Posts: 7
Location:
Ottawa
|
You're right, I changed it and recompiled the drivers and now it works, kinda. I was getting alot of stuttering so I enabled in playback options the card and lost everything, so I did :
Code: rm -f /dev/fb0autodetect rm -f /dev/fb1 mknod /dev/fb1 c 29 1 chmod 666 /dev/fb1 chown mythtv /dev/fb1
Which made the picture come back perfectly but I lost sound output from my sound card. I tried jacking up the volume in aumix but that didn't change anything and I also tried the audio outputs from the pvr350 with the same result. I'll search the forums for an answer but if anyone has had this problem before I'm all ears.
P.S. Sorry for the bad english. I'm a frenchy.
|
|
Top |
|
 |
mongo
|
Posted: Mon Sep 20, 2004 7:14 pm |
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
did you enable the 350 output in the setup?
also after you get audio working on the 350 , because live-tv & playback audio is piped out the 350, and dvd, mp3, (all others) is through your sound card, best thing is to pipe the 350 output to your sound card's line in. make sure its un-muted. a quite a few posts on this boards on this.
Just a quick note, I helped a friend setup a box with the 350, He has 65 " HDTV, and Directv HDTV IRD. He recorded some HD stuff (using th s-video output to the 350) while I was there to test things out. We both had to pick up our jaws off the ground. Don't get me wrong on this, switching to the HD source was better, but I've NEVER seen SD look SOOOOOOO good.
|
|
Top |
|
 |
hooverzilla
|
Posted: Mon Sep 20, 2004 10:55 pm |
|
Joined: Sun Sep 19, 2004 10:01 pm
Posts: 7
Location:
Ottawa
|
Alright, here's a little update.
I physically moved the card over by one slot and that fixed the sluggish playback of the card when the Use the pvr350's tv out/decoder is in use. Now I still don't have any sound either from the sound card or from the rca out of the pvr350. So I did this:
Code: cd /usr/src # The ivtv compile needs the src files. tar xvfj linux-2.4.25-chw.tar.bz2
cd /usr/local/lib/ivtv/driver make clean # I suppose I could have used 'make install' but I was testing # and didn't want to add to my problems. make
cp msp3400.o /lib/modules/2.4.25-chw/kernel/drivers/media/video/ # And answer yes to overwrite the existing file.
# Then, if you don't like extra files just lying around: cd /usr/src rm -rfd linux-2.4.25-chw # to delete the source files previously extracted.
which seems to of fixed just about everyones problem except for me. I reboot the computer and I still don't have any sound. I tried this command Code: test_ioctl -a
and it would seems as though it's not muted Code: Volume = 58950 Mute = 0
I also checked to make sure in aumix and alsamixer that the levels were set properly.
And so I'm all out of ideas since it would appear that after these steps, everyones sound problem has been fixed. If I do managed to get it going I'll write a little howto from start to finish to help out the newbs like me. Oh and for the record if I disable the Use the pvr-350's tv out/encoder, I do get sound and picture although it's very jittery.
|
|
Top |
|
 |
mongo
|
Posted: Fri Sep 24, 2004 7:00 am |
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
Well I tried few drivers from CK's site, and end up with stable encoders, but start having problems with the 350's output. until I tried :
http://67.18.1.101/~ckennedy/ivtv/OLD_g ... ck100z.tgz
my system has been up for the last 3 days without any issues with the 250 in the pundit, and the 350 on the via motherboard.
Here is what I did to update the drivers....
1. Extract the kernel source (kernel-2.4.25-chw.tar.bz2) in /usr/src
2. download & extract the ivtv driver from the link above.
3. perform the following commands
Quote: cd drivers make make install
4. make a backup of /etc/mythtv/modules/ivtv 5. edit the ivtv, here is a copy of mine Quote: alias char-major-81 videodev alias char-major-61 lirc_i2c options ivtv #options tuner type=2 #options msp3400 once=1 simple=1 #options saa7127 enable_output=1 output_select=1 add below ivtv msp3400 saa7115 saa7127 tuner add above ivtv lirc_dev lirc_i2c ivtv-fb
reboot and enjoy.
|
|
Top |
|
 |
willem
|
Posted: Wed Sep 29, 2004 1:39 pm |
|
Joined: Tue Feb 03, 2004 3:23 am
Posts: 159
Location:
Friesland, The Netherlands
|
Thanks Mongo for your write up. Just to make sure I got it straight. In the first post you state:
Quote: So when the Tivo died, I built a system with a Pundit & pvr-250. I went ahead and put together a second system with old parts (pIII 733) and a 350, with the plan if I have too much trouble with the output, I'll switch out to a Nvida video card.
the outcome... 350's output has been ROCK solid, Live TV, recording, xvid, avi, DVD playback, DVD ISOs (Yes, Mythvideo will play an ISO), you name it. A complete shock to me after all the trolling...
Does this mean when playing back DivX/Xvid stuff on a PIII 733 it doesn't stutter? If so, that would be fantastic! I tried the PVR-350's TV-out on my Celeron 700. The Live TV playback was very, very good but when I noticed that DivX playback stuttered badly (because it lacked hardware Xv support) I switched back to using my GeForce MX440 for TV-out.
If the ivtv-0.1.10-pre2-ck100z version allows smooth DivX playback I may give the PVR-350 TV-out a try again!
|
|
Top |
|
 |
mongo
|
Posted: Wed Sep 29, 2004 8:22 pm |
|
Joined: Fri Sep 17, 2004 6:16 am
Posts: 8
|
Don't think the 700 cele is going to cut it. I think the X driver allowed DMA transfers to the output, but lacked hardware Xv support.
So you will need something to do the full decode.
|
|
Top |
|
 |
willem
|
Posted: Thu Sep 30, 2004 12:55 am |
|
Joined: Tue Feb 03, 2004 3:23 am
Posts: 159
Location:
Friesland, The Netherlands
|
Ah well, maybe hardware Xv support is added in the future (if the card supports it at all).
I'm also thinking about making a dedicated backend and frontend someday. That way the PVR-350 would be moved from the TV anyway...
|
|
Top |
|
 |
SnapperDragon
|
Posted: Sun Oct 03, 2004 7:40 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
What is the reasoning behind moving the card to a different pci slot? I only have 1 in my shuttle box. Same blinking cursor. After I added the "vc" stuff, I got a dark screen with some dim spots, and then X complained that it could not load.
Any more thoughts? Where did you find out about the VC option that can be passed via lilo?
Thanks.
|
|
Top |
|
 |
SnapperDragon
|
Posted: Sun Oct 03, 2004 8:27 pm |
|
Joined: Sat Feb 28, 2004 10:04 am
Posts: 173
Location:
Canton, MI USA
|
Never mind, found it in the driver source.
|
|
Top |
|
 |
rkremser
|
Posted: Tue Oct 19, 2004 10:58 pm |
|
Joined: Wed Sep 08, 2004 10:15 pm
Posts: 82
|
hopefully someone is still recieving emails for responses to this thread. I'm stuck at the blinking cursor and unable to do anything with the computer. How can i get into a console to change settings. I don't have another computer handy or the knowhow to do a ssh session. Thanks for any help you can provide
|
|
Top |
|
 |
tvboy
|
Posted: Thu Oct 21, 2004 8:22 am |
|
Joined: Tue Jun 15, 2004 2:16 am
Posts: 51
Location:
Germany
|
If you still have a monitor hooked up to your box, you can switch by ALT-F2. You may have to hit that a few times. that should bring you back to the console.
|
|
Top |
|
 |
rkremser
|
Posted: Thu Oct 21, 2004 8:27 am |
|
Joined: Wed Sep 08, 2004 10:15 pm
Posts: 82
|
Ahh thanks, i'll try that next time, I was able to setup a ssh this time and that worked but this would have been much easier.
|
|
Top |
|
 |