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?
Regards,
Hans
> >>
> >> Of course I am prepared to test here. I do think the environment
> >> is quite suitable as my motherboard ASUS M2N-E and the other
> >> components support s2ram.
> >>
> >> For your information:
> >> I did try already to unload the module before calling s2ram and
> >> re-load it after wake-up with no success. Here the modules loaded
> >> on my system:
> >
> > Ingo,
> >
> > How did you try to do the module load and unload?
>
> I did not try to perform this by modify the involved
> scrips/configuration. I just manually did:
>
> rmmod ivtv (before s2ram)
> modprobe ivtv (after wake-up).
>
> To me it seems that from the TV-Card's PCI-slot the power is removed
> and the card therefor 'forgets' the loaded firmware. I do not know
> whether just loading ivtv module also loads the firmware?
> Maybe the card also needs initialisation to bring it up.
> What I always observe:
> after wake-up from s2ram the power consumption of the whole PC is
> about 5 watts less than before. This only comes back to normal level
> after reboot.
>
> With best regards,
> Ingo
>
> > On my Fedora 7 system
> > I had (s2disk?) working a while ago (I haven't tested recently). I
> > did it so I could use the power button on my remote to turn off
> > mythtv and put the machine into suspend. Here are some of the
> > notes I have:
> >
> >
> > Fix the pm-suspend config to unload and reload ivtv module:
> >
> >
> > $ su - root
> > # cp /usr/lib/pm-utils/defaults /etc/pm/config.d/unload_module
> > # vim /etc/pm/config.d/unload_module
> > # cat /etc/pm/config.d/unload_modules
> > # pm-utils suspend/hibernate config file
> > # system defaults are in /usr/lib/pm-utils/defaults
> > # hal calls pm-utils to do suspend on Fedora 7
> >
> > #HIBERNATE_RESUME_POST_VIDEO="no"
> >
> > SUSPEND_MODULES="ivtv cx18 "
> >
> > #DISABLE_HIBERNATE="no"
> > #DISABLE_SUSPEND="no"
> > # chown root:root /etc/pm/config.d/unload_module
> > # chmod 755 /etc/pm/config.d/unload_module
> > # exit
> >
> >
> >
> > Fix udev rules so mythbackend can work after resume:
> >
> > $ su - root
> > # cd /etc/udev/rules.d
> > # vim 55-local.rules
> > # cat 55-local.rules
> > KERNEL=="video*", GROUP="mythtv"
> > KERNEL=="radio*", GROUP="mythtv"
> > KERNEL=="vbi*", GROUP="mythtv"
> > SUBSYSTEM=="dvb", GROUP="mythtv"
> > # udevcontrol reload_rules
> > # exit
> >
> >
> > I did the stuff below as well for the sake of mythtv running as
> > non-root user, but it didn't matter/or didn't work. This stuff
> > only probably gets checked on an event that doesn't happen on
> > resume (hal database updated with *new* ivtv device, pam console
> > transfer/revert))
> >
> >
> > Add /etc/security/console.perms.d/60-local.perms to give dvb & v4l
> > access to mythtv group:
> >
> > # permission definitions for mythbackend
> > #<console> 0660 <sound> 0660 root.mythtv
> > <console> 0660 <v4l> 0660 root.mythtv
> > <console> 0660 <dvb> 0660 root.mythtv
> >
> >
> >
> >
> > On resume have HAL give mythtv permissions to /dev/video again:
> >
> > $ su - root
> > # vim
> > /usr/share/hal/fdi/policy/20thirdparty/90-grant-v4l-devices-to-myth
> >tv-group.fdi # cat
> > /usr/share/hal/fdi/policy/20thirdparty/90-grant-v4l-devices-to-myth
> >tv-group.fdi <?xml version="1.0" encoding="UTF-8"?>
> >
> > <deviceinfo version="0.2">
> > <device>
> > <!-- grant access to v4l devices to mythtv group so
> > mythbackend works --> <match key="info.capabilities"
> > contains="access_control"> <match key="info.capabilities"
> > contains="video4linux"> <append key="access_control.grant_group"
> > type="strlist">mythtv</append> </match>
> > <match key="info.capabilities" contains="dvb">
> > <append key="access_control.grant_group"
> > type="strlist">mythtv</append> </match>
> > </match>
> > </device>
> > </deviceinfo>
> > # /sbin/service haldaemon restart
> > # exit
> >
> >
> >
> > Regards,
> > Andy
> >
> >> lsmod |grep ivtv
> >> ivtv 152512 0
> >> i2c_algo_bit 8452 1 ivtv
> >> cx2341x 14596 1 ivtv
> >> tveeprom 20624 1 ivtv
> >> videodev 30720 1 ivtv
> >> v4l2_common 21888 6
> >> wm8775,cx25840,tuner,ivtv,cx2341x,videodev v4l1_compat
> >> 15492 2 ivtv,videodev
> >> i2c_core 28544 13
> >> wm8775,cx25840,tuner,tea5767,tda8290,tuner_simple,mt20xx,tea5761,i
> >>vtv,i2c_algo_bit,tveeprom,nvidia,i2c_nforce2
> >>
> >> I am running here Ubuntu-Hardy amd64 with kernel:
> >>
> >> cat /proc/version
> >> Linux version 2.6.24-19-generic ([EMAIL PROTECTED]) (gcc version 4.2.3
> >> (Ubuntu 4.2.3-2ubuntu7)) #1 SMP Fri Jul 11 21:01:46 UTC 2008
> >>
> >> If you need any more information, please let me know.
> >>
> >> Many thanks and regards,
> >> Ingo
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
