Thierry Vignaud wrote: >"Brian J. Murrell" <[EMAIL PROTECTED]> writes: > >>>falling back to bttv-0.7.9x ... >>> >>Was this a serious solution? >> >>It is unacceptable. If bttv-0.8.33 caused problems with prior >>kernels then I could understand it but it hasn't -- I have been >>using bttv-0.8.x for my last half dozen MDK kernels at least and it >>has worked fine. It is obvious that something new introduced >>between 2.4.18.2mdk-1-1mdk and 2.4.18.10mdk-1-1mdk has caused a >>problem. >> >>bttv-0.8.x is much superior to bttv-0.7.9x. >> >even you reports some problems. > >so don't come back crying on mandrake because we release stable >drivers whereas you want support for unstable drivers you compiled >yourself. > >we don't support unstable softwares. >we offer support for releases. >cooker isn't a support mailling list, but a development list. >regarding this, i'll better spent my time on v4l userland apps rather >than on bttv. > I ran into the same problem with ATI GATOS experimental driver (km) as well. When I tried to capture video, all I got was a freeze and blinking CAPS + SCROLL lock. Kernel magic SysRq keys worked, though.
I tried it on kernel-2.4.18.11-1-1mdk So this may not be related to bttv driver at all, rather v4l issue in general. Michal Bukovjan
