> > The ivy tv page at http://ivtv.sourceforge.net can tell you how to > > set up the lirc drivers for the pvr250/350. I set that up some time > > ago, so don't now remember details. > > Lets compare notes. What gcc version are you using? Do you use the > kernel i2c modules, or the ebuild (if so, which version)? Would you > mind posting the ivtv section of your /etc/modules.conf?
gcc version: I think it updated to 3.2.3-r3 a few days ago. i2c: kernel; I had no idea there was an ebuild modules.conf: I haven't touched it. For now I use a script I wrote to load the modules. I just thought it would be easier to edit that to adapt to changes until I think the box is ready for every-day use. When I do work on it, I would be happy to share it. > > > For a WM, I decided that something a little nicer than twm was in > > order, so I used waimea. Lots of people have had good luck with any > > of the *box WMs. > > The latest DirectFB includes support for the CLE266 video, so > I've been > bypassing X and running directly from the framebuffer. Works great. I don't think that mythtv works on the framebuffer. I seem to recall that the qt libraries need a good deal of work still to work well on on the framebuffer. The framebuffer has never been important to me, other than to have a better-looking console. Vesa-fb works fine for that. Overall, I've not really had any problems with it, until I tried to use the -epia kernels (mythfrontend locks) or tried to use via's binary drivers. I found that I couldn't use the Xfree drivers unless I used their kernel modules. When I use their kernel modules, I have to use their videodev. When I use their videodev, ivtv breaks. ugh. I do have high hopes for the -epia kernel with ivor's work added in. good luck -rex -- [EMAIL PROTECTED] mailing list
