On Thu, Feb 15, 2007 at 10:19:07AM +0100, Sander Sweers wrote: > On 2/14/07, Julian Edwards <[EMAIL PROTECTED]> wrote: > > > Can you try and remove the old firmware and download the "recommended" > > > firmware from [1]? If that does not work it looks similar to the problem > > > people had with udev. See [2] for the 2 udev hang fixes. > > > > Unfortunately this has reared its ugly head again, using the "new" > > firmware. I say "new" because I think the firmware that was being used > > beforehand was the same as the firmware at [1] except it had the padding > > at the end. Diffing the first 262144 bytes was certainly the same. > > Correct :-) > > > I also don't think its [2] because I don't have the hotplug agent. The > > firmware *is* loaded on the initial attempt at boot, it's just that it > > seems to time out on an API call. > > Can you post the kernel log + INIT IVTV, it sound like the firmware is > crashing.. > > > I don't think it's faulty hardware either. As I said, 0.7.1 worked > > perfectly. > > You can also try out 0.10rc1 with kernel 2.6.18. This is the newly > designed ivtv driver and is much improved compared to the old one. Get > it from [3]. I do not think ATrpms has this version so you will need > to build it from source. Make sure you read the README if you try > this.
It's in ATrpms, but it's in the atrpms-testing repo, not the stable
one:
http://atrpms.net/name/ivtv-0.10.x/
> Greets
> Sander
>
> [3] http://dl.ivtvdriver.org/ivtv/unstable/ivtv-0.10.0rc1.tar.gz
--
Axel.Thimm at ATrpms.net
pgpNnynEvxcQK.pgp
Description: PGP signature
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
