AH yes...I did mis-read your message and turned 848 into 878. The WinTV cards with the 878 chipset are card 10. Anyway, let me take another stab here. Do you have a VIA chipset on your motherboard? If you do you may want to try updating your kernel to a newer rev. There are known issues with the VIA chipset and the BTTV devices working together. In fact, my computer has a VIA chipset (and I use 2.4.8 for my kernel which works okay) but under Windows 2000, I know the perfect way to lock the syste, try running the WinTV software. Instant lockup. Works great under Windows 98 too. Nothing like putting your system to sleep the hard way ;-). Under the new Linux kernel I do not get system locks or any errors, it just works. I did have a problem with an earlier kernel release but I can't remember which one. I do know that 2.4.2 did work for me, which was what I was running until I moved to SuSE. Outside of that, I have never run into this type of problem, and probably won't be of much help. Hopefully this gets you somewhere. On Tue, 4 Sep 2001, Constant Brouerius van Nidek wrote:
My WinTV should be card 2 and is properly set and recognized ;-) The card number could be found on the SuSe pages. According to the instructions from the manual the card is set in the modules.conf No Webcam, no video. Have read the xawtv manpage and found nothing about any input. What do you mean by that. Did I overlook something important? ;-) Scanning of the channels went smooth but without any result. In Kwintv same. No channels but only the aiee error loops in the messages file. Have tried all Pal varieties, all possible areas and checked in the known local TV channels without result.
-----------------------
Did you properly set the card number? You could try this: bttv card=10
I think the WinTV cards are all listed as card 10, at least mine is. If that works, then you need to change the card listed in the modules.conf file. Also do you have any other devices? Like a web cam or any video type devices? These seem to get loaded up prior to the bttv device on my system, and this causes all sorts of problems. Check the xawtv input information. Make sure both the device and the input on the device is correct. And don't forget to scan the channels.
On Tue, 4 Sep 2001, Constant Brouerius van Nidek wrote:
On my Suse 7.2 out of the box system I have an WinTV card. It is a card with the 848 chip. Although the card is inserted in the /etc/modules.conf and should therefore be initialized after booting (I think) I do not find the card mentioned in /var/log/messages nor with dmesg. After modprobe bttv I find the card installed but wit Kwintv or Xawtv I do not get any screen movement, not even snow ;-(. Looking in the /var/log/messages I find following new lines:
tuner : TV freq out of range bttvO : irq : SCERR risc_count=07450810 bttvO : irq : SCERR risc_count=07450808 bttvO : irq : SCERR risc_count=07450808 bttvO : irq : SCERR risc_count=07450800 bttvO : irq : SCERR risc_count=07450808 bttvO : aiee : error loops bttvO : irq : SCERR risc_count=05e80014 bttvO : aiee : error loops resetting chip
after which the whole thing starts anew. Can somebody tell me what is happening and where I should look for a solution?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse .com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com
--
NTReader v0.35w(P)/Beta (Registered) in conjunction with Net-Tamer.