InfiniteMac OSx86

InfiniteMac OSx86 (http://infinitemac.com/forum.php)
-   Leopard 10.5 (http://infinitemac.com/forumdisplay.php?f=85)
-   -   [Solved] AMD Dual Core Timing Issue AKA Mouse Bug (http://infinitemac.com/showthread.php?t=734)

agrafuese 03-22-2008 09:00 PM

"change pets" ... i like that one, it's almost better than "change girlfriends" ... almost ;)

please, no red button. i'm on 33 hours! this might be a record for me.

Ianxxx 03-22-2008 09:50 PM

Glad to see your up and running agrafuese 33 hours cool.
I seem to have found a solution for myself too.
I now have my processor overclocked, the timings on my memory are a lot faster than they should be, seem to be able to alter anything and system remains stable. Been uploading downloading torrents & encoding videos, running as many apps as I can watching two movies at the same time. Every thing is still smooth as it should be.
The answer for me was my memory is now running at 398 mhz as apposed to 400mhz.
Weird but it seems to work 100% so far.

WinLinMac01 03-23-2008 01:12 AM

Red bull anyone? Go to you local store and pick up a few energy drinks to consume, lol. =)

Quote:

[cite] agrafuese:[/cite]"change pets" ... i like that one, it's almost better than "change girlfriends" ... almost ;)

please, no red button. i'm on 33 hours! this might be a record for me.

agrafuese 03-25-2008 01:51 AM

Haha...more like we need to buy red bull for our computers :) No more slowdown issues right? Or maybe it would be too fast then ;)

Well I've been up for days now...I THINK. I am faced with a very strange issue now. I left my computer on since Saturday morning, left for the weekend and came back now (it is now Monday afternoon where I am). Before I left, I had nothing running except for Transmission downloading 4 large torrents. When I woke my display up just now, I was presented with the Login window. So I thought my computer had restarted itself. I logged in and went to Console to see if I had any error messages. The odd thing is, there was no report of any kind of rebooting! So at first, I thought that Leopard had some kind of built-in auto-logout security feature if there was no user activity for two days. But then, I opened up Transmission and found that my torrents had stopped. So why would Leopard log me out if torrents were still running?? Does anyone know anything about this? When I look at my Console messages over the past couple of days, there are only two messages worth noting:

Code:

3/22/08 4:34:16 PM bootlog[53] BOOT_TIME: 1206228844 0
3/23/08 4:34:10 PM com.apple.launchd[1] (com.apple.dashboard.advisory.fetch[222]) Exited with exit code: 1

Another strange thing is, I cleared my console before I left on Saturday, and there is nothing before those two lines of code. Also, even if I were logged out by Leopard, wouldn't Transmission still be sitting there when I log back in? Am I wrong about that? I am so confused right now :\

WinLinMac01 03-25-2008 01:53 AM

That is very strange, but is this mouse-related? Looks like an entirely different issue.

Quote:

[cite] agrafuese:[/cite]Haha...more like we need to buy red bull for our computers :) No more slowdown issues right? Or maybe it would be too fast then ;)

Well I've been up for days now...I THINK. I am faced with a very strange issue now. I left my computer on since Saturday morning, left for the weekend and came back now (it is now Monday afternoon where I am). Before I left, I had nothing running except for Transmission downloading 4 large torrents. When I woke my display up just now, I was presented with the Login window. So I thought my computer had restarted itself. I logged in and went to Console to see if I had any error messages. The odd thing is, there was no report of any kind of rebooting! So at first, I thought that Leopard had some kind of built-in auto-logout security feature if there was no user activity for two days. But then, I opened up Transmission and found that my torrents had stopped. So why would Leopard log me out if torrents were still running?? Does anyone know anything about this? When I look at my Console messages over the past couple of days, there is are only two messages worth noting:

Code:

3/22/08 4:34:16 PM bootlog[53] BOOT_TIME: 1206228844 0
3/23/08 4:34:10 PM com.apple.launchd[1] (com.apple.dashboard.advisory.fetch[222]) Exited with exit code: 1

Another strange thing is, I cleared my console before I left on Saturday, and there is nothing before those two lines of code. Also, even if I were logged out by Leopard, wouldn't Transmission still be sitting there when I log back in? Am I wrong about that? I am so confused right now :\

agrafuese 03-25-2008 01:55 AM

Yeah, you're right, sorry. I kind of went off on a tangent there. I should post this in another thread. I've grown too comfortable blabbing on in this one, hehe.

onAir 03-25-2008 02:27 AM

hey
didnt read all 9 sites of this thread - weird i dontknow if the mouse problem is still active...
anyway i had the same prob and i enter following kernel flag to my boot.plist:

<key>Kernel Flags</key>
<string>idlehalt=0</string>

thats all
never had any bad mouse issue again

______________________________________________


is it possible that only amd dual cores have this problem?
would be an explanation for that, coz win xp needs the amd dual core optimitzer for running fine.
and coz there is certainly no mac verison of the optimizer the second core should or should not interact in idle.
hmm sounds logically, anyway the kernel flag works for me ;)


cheers

WinLinMac01 03-25-2008 02:32 AM

This can work, definitely. I can't believe it works, lol. =) - Cheers indeed.

Quote:

[cite] onAir:[/cite]hey
didnt read all 9 sites of this thread - weird i dontknow if the mouse problem is still active...
anyway i had the same prob and i enter following kernel flag to my boot.plist:

<key>Kernel Flags</key>
<string>idlehalt=0</string>

thats all
never had any bad mouse issue again

cheers

agrafuese 03-25-2008 02:33 AM

what exactly is that string meant to do (aside from it fixing your mouse) ?

onAir 03-25-2008 02:38 AM

im think its preventing the second core for stopping in idle mode