|
Well, no, actually I ran into some problems with the
rebuild that I didn't have with the original, but the rebuild is
probably more correct. With the original, I did lots of experimenting
with the 2.6 kernel and SATA. I eventually gave up and stayed with
the 2.4.29 kernel. When I did the rebuild, I went straight to the
2.4.29 kernel, but then had to do a patch on the ivtv driver source to
make "depmod -ae" happy. That wasn't needed before (or maybe it was
and I didn't realize it). Anyhow, I believe the builds are pretty identical, and the failures are virtually the same as before. But all of that aside, this whole thing used to work. The only potential culprits that I seem to be left with are the pvr350 board, the motherboard ee settings, and the nvidia video board. They're the only things that haven't been reloaded. So, - Is there any EEPROM on the pvr350 board? - If so, are there any settings that do not get initialized when the driver is loaded? Maybe I should be looking at the motherboard and nvidia boards also?? Thanks for everyone's help, Don PS Distro - Slackware 10.1 Kernel - 2.4.29 |
- [ivtv-devel] Re: Is there a way to restore a trashed pvr350 ... Don
