Hi, thanks a lot for help. I'm not at the machine but do know that framebuffer is running probably cause Suse has boot splash routine integrated, so Vesa Fb is fired at the start when bootsplash screen is showed. I also get occasional warning in /var/log/messages about some problems with mtrr. I'll try 32Mb when I get home. BTW, is sisfb already in Suse supplied kernel or can it be added as module to working kernel or should I recompile from scratch ? Thanks, Robert. ----- Original Message ----- From: "Thomas Winischhofer" <thomas@xxxxxxxxxxxxxxxx> To: <xfree86@xxxxxxxxxxx> Sent: Monday, March 15, 2004 1:12 AM Subject: Re: Asus Pundit (sis 651) : High CPU usage for X in mplayer - are these values sane ? > Robert Rozman wrote: > > Hi, > > > > I'm sending files requested to give proper help. Like I said it seems like > > Xv is not working (I get lower cpu if I set -vo x11 in mplayer). I suspect > > that software scaling is going on, but don't know what to do to correct this > > ( I get CPU for X 40-50% and for mplayer or mythtv frontend about 20%). I > > have Asus pundit, with P4 2.4 G. > > > > I'll appreciate any help, since this is the only major problem left... > > > > I have: > > > > uname -a -> Linux pundit 2.4.21-144-default #1 Fri Nov 14 00:01:36 UTC 2003 > > i686 i686 i386 GNU/Linux > > > > cat /proc/mtrr > > > reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 > > reg01: base=0x1c000000 ( 448MB), size= 64MB: uncachable, count=1 > > reg02: base=0xdc000000 (3520MB), size= 64MB: write-combining, count=1 > > reg03: base=0xe8000000 (3712MB), size= 32MB: write-combining, count=1 > > reg04: base=0xe1400000 (3604MB), size= 4MB: write-combining, count=1 > > Is that from before or after starting X? > > Do you have a console framebuffer driver running? > > > (WW) SIS(0): Failed to set up write-combining range > (0xe8000000,0x4000000) > > The reason for your problem is that, for some reason, MTRR setup fails, > although it obviously is supported by your kernel. At the moment I > cannot think of a reason for this. > > Does this warning message go away if you change the amount of video RAM > to, say, 32MB in the BIOS setup? > > (BTW: Why do you set "forcecrt1" to "false" when it appears that you > neither have a TV, LCD or secondary VGA connected?) > > Thomas > > -- > Thomas Winischhofer > Vienna/Austria > thomas AT winischhofer DOT net http://www.winischhofer.net/ > twini AT xfree86 DOT org > _______________________________________________ > XFree86 mailing list > XFree86@xxxxxxxxxxx > http://XFree86.Org/mailman/listinfo/xfree86 _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
