JL wrote: > I couldn't make ivtv-fb work in FC3 either. Tried the atrpms at > stable/testing. I also tried building ivtv myself and got a > "Unable to > handle kernel NULL pointer dereference" in dmesg. I didn't > get the trace > with the atrpms package. I sent a message a few days ago about it > (http://poptix.net/ivtv/Nov-2004/msg00612.html). It was my first time > building ivtv so it's possible that the trace is not > indicative of why the atrpms ivtv packages don't work for FC3.
I've had exactly the same problem, I _was_ going to try building it myself but if you've already tried and failed there's not much point! I _think_ what is happening is that when you load ivtv-fb it reassigns the console to the fb device which then doesn't work as a text based display and locks the machine. I upped the debug messages to 255 and I got >Dec 5 16:09:57 pvr kernel: Console: switching to colour frame buffer device 90x36 There are _no_ errors but the machine effectively locks as soon as the ivtv-fb is loaded (I think it locks when it trys to write to the screen and can't) At the same time I _can_ connect but it locks after the password request, again I believe this is the point that it would write to the console with a message saying "session opened for user xxxxxx" I tried adding video=vc:0-0 to my grub.conf but it made no difference. If I try and rmmod ivtv-fb it complains about being in use (dispite not actually doing anything other than loading/unloading the driver), if I try and shutdown/reboot it locks, again no errors, all I get in my log file is >Dec 5 16:10:47 pvr shutdown: shutting down for system reboot >Dec 5 16:10:47 pvr init: Switching to runlevel: 6 Then nothing until syslogd restarts when it comes up again (after hitting the reset), again this is the point at which the console would be reporting all the shutdown messages. > Later on, I installed FC2, and it works (with the badazzz > ivtvdev driver). > I can also reboot my machine, which I couldn't do on FC3 > after probing ivtv-fb. I had to manually power down. I played lots with FC2 to get the thing working, everything worked (eventually) except sound but I installed it on a 8Gb drive with the intention of using 4 sata drives as a raid array for a /video partion, that caused problems so I swapped the 8Gb for a 120Gb drive and installed FC3. Sound now works but ivtv-fb doesn't :-( > There is definitely something different between FC2 and FC3. > For those who > just want their pvr 350 tv-out to work, I'd suggest FC2. I > still have my FC3 > install around, but I'm not sure what to do to pinpoint the problem. I'd rather not install again, I'm not sure if sound worked on FC2 to start with or if I broke it (I foolishly didn't even plug in speakers until after _everything_ else was working). I'd rather not wipe FC3 just to find that sound didn't work on FC2 anyway, would be appreciated if anyone could help. David ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ ivtv-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/ivtv-devel
