On 14/01/2005 Michael T. Dean wrote:
> Don't manually load them (see below).  It was good for testing, but now 
> you've given enough information to explain what was happening, so it's 
> no longer necessary (and likely to cause more problems than it solves)...

ah, so this damaged my monitor. it's broken now (too large mode), so i
definitely hope that this doesn't happen again.

i'll load ivtv directly from now on, to prevent those incidents.

> That explains why tveeprom wasn't loading correctly--the bttv module 
> (which your modprobe.conf said to load upon access of char-major-81) was 
> loading eeprom before ivtv was able to load tveeprom--exactly as the 
> error message stated.
> 
> Now that you've corrected your modprobe.conf, make sure you load ivtv by 
> issuing the command, "modprobe ivtv" and nothing else.

ok, just to go sure, i have in my modules.conf:
alias char-major-81     videodev
alias char-major-81-0   ivtv

videodev is compiled into kernel here, and i'm using kernel 2.6.10 now.

> Actually, that command belongs inside modprobe.conf.  It will not 
> execute properly from the command line (as you see below).  It simply 
> says to install ivtv-fb after installing ivtv.  If you're not using the 
> TV out, don't put it in there.

i planned to enable TV out in future, to see the screen on my Television,
but i intended to concentrate on TV in first.

> Notice no module loading problems.
> 
> May be because you're using a Via motherboard.  If it's something older 
> than the KT-400 (and all the other 400-series) motherboards (especially 
> the 266's and 133's), that's almost definitely going to be a problem.  
> Although it's getting better (thanks to Chris), I still think the $40 I 
> spent on a cheap SiS-based motherboard was the best $40 I spent.  I 
> couldn't run for more than 15 minutes (on a good day--average was less 
> than 5) without a hard system lock.

so i'm using the VIA K8T Neo (K8T800 chipset) motherboard with an AMD
Athlon64 3200+ processor, and as mentioned matrox mga g400 graphic
controller.

are there known problems with this hardware?

> As of now, you have your hardware configured correctly (with the 
> possible exception of the tda9887 option--which would not affect 
> stability, only tuning capability), so if you stick with the Via MB, you 
> may be in for a long difficult journey trying to make it work.  IMHO, 
> $40 (or even $100) for a new motherboard is far less expensive than the 
> time you'll spend trying to make the system work.

so can you recommend any athlon64 mainboard that is known to work well
with ivtv drivers?

> BTW, using the PVR-350's TV out on a Via makes an unstable system even 
> less stable.  If you're not using it, don't install ivtv-fb (i.e. leave 
> the line above out of modprobe.conf).

so i'll not load ivtv-fb any more, at least as long as i don't use TV
out.

i'll give ivtv-0.3.0a a try in the next days, and report how it worked.

bye
 jonas


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Ivtv-users mailing list
Ivtv-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ivtv-users

Reply via email to