Unfortunately my system came with Shuttle's latest BIOS Update.
And from the look of their BIOS history, it doesn't seem like they even
attempted to address the problem like ASUS, although I know for a fact
that plenty of people have contacted them about this problem. (Which by
the way they have not yet replied back to me).
You can see the BIOS History here:
http://www.shuttle.com/share/fae/hq/download/bios_rdm/readmefx43g.htm
Hauppauge recommended installing the ATI 4-in-1 update, but I believe
that that is a windows application.
Still Open to suggestions
-danny
On Wednesday, October 12, 2005, at 02:29 AM, Adam Forsyth wrote:
You did upgrade your BIOS to the newest version first right to make
sure that doesn't fix it?
On 10/12/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Really?
Wow, that's good news, as I am stuck with the hardware.
Well I guess I will just use some nasty windows PVR software until the
i2c problem is worked out. If any of the developers need me to run
tests on my system, I'd be happy to.
Its a shame, I really did like everything about MythTV.
-danny
On Wednesday, October 12, 2005, at 01:31 AM, Adam Forsyth wrote:
Why does it work in windows and not in Linux? Someone please, any
advice.
Heh, we'd all love to know. It's a Linux i2c problem that causes it,
not a straight hardware conflict, I'm pretty sure.
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
