On Sunday 24 August 2008 17:03:40 Ingo Steiner wrote:
> Hi Hans,
>
> On 24.08.2008 12:20, Hans Verkuil wrote:
> > On Friday 22 August 2008 20:53:08 Ingo Steiner wrote:
> >> On 22.08.2008 20:17, Andy Walls wrote:
> >>> On Thu, 2008-08-21 at 15:12 +0200, Ingo Steiner wrote:
> >>>> Hans,
> >>>>
> >>>> thank you very much for your offer to build an ivtv version
> >>>> which probably supports s2ram!
> >
> > Hi Ingo,
> >
> > Bad news, I'm afraid. I think I was too hasty in offering to help
> > out. I did not have time this weekend, I know I'll have no time
> > next weekend and very likely the weekend after that, and then I'll
> > go on vacation for almost three weeks. And the two weekends after
> > that it's also unlikely that I will have time. So basically I don't
> > see this happening until mid-October. If it was just a small thing,
> > then I could squeeze it in, but I need to do research on how to
> > properly implement something like this and I suspect that the
> > driver might need quite a bit of work.
> >
> > In addition, the fact that it apparently doesn't work after
> > modprobing ivtv after wake-up makes me very suspicious. That should
> > just work fine. Is the card seen at all after the modprobe? What
> > does the kernel log show?
>
> I now performed following Steps:
> at 16:46 unloaded ivtv:
> 'rmmod ivtv'
> and entered s2ram (on Ubuntui Hardy = Bereitschaft)
>
> at 16:48
> wake-up again by pressing space bar
> load module ivtv 'modprobe ivtv'
>
> and here you receive the /var/log/kern.log:
> (hope you are not worried because I paste it here):
>
> +++++++++++++++++++++++++++++++++++++++
<snip>
> ++++++++++++++++++++++++++++
>
> I also do attach it here because you also get the mail personally.
> Does it give you an indication, why things do not start-up
> completely?
>
> I really do not want to push you with this matter, so if you do not
> have the time, don't worry. I am using ivtv now since 2 years and on
> a desktop-PC s2ram is not such essential (though I intentionally
> invested in ECC-RAM to prevent from RAM-errors ;-)
> If you need other info/log from my system, just let me know!
Hmm, everything looks perfect. Everything is initialized fine and the
firmwares are loaded.
What exactly is going wrong? Turn on debugging with: 'ivtvctl -D0x41b'
and try to capture. What does the logging report?
Regards,
Hans
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
