mandrake 10.1 x86_64 sn95g5 weird mouse, pause problem
 

Hello,

I had no problem installing mandrake 10.1 x86_64 on my new shuttle sn95g5, 512M ddr 400, 250G sata drive. The os installed, ethernet no probs, mouse, no probs. nvidia geforce 5200, using the nvidia drivers.

For some reason, every 10 - 15 seconds, the mouse will pause in its motion, before continuing on. It isn't exactly life-threatening, it just really annoys me. I will be going along, feeling just fine, then all of a sudden the mouse will just pause for about a second before it moves again.

Anyone else seen this, and found a solution? My eyes are bleeding out of my head from searching for a problem like this one.

thx

same here
 

I'm experiencing the same behaviour on my Shuttle SN95G5(v1.3) - The mouse freezes every 10 seconds for a second or so. Only with nvidia's proprietory drivers in use (not vesa). I have a GeForce 6600 GT, 1 GB ram, AMD64 3500+ and 300 GB sata HD running Mandrake 10.1 OE x86_64.

Actually it seems that my keyboard is freezing at the same moments as the mouse is doing so...

Have you (or anyone else) found a solution to this rather anoying bug?

Thank you.

Thanks god i'm not alone...
I have exactly the same problem and it's pretty anoying... The whole system seems to freeze every 7 seconds... I've tried with x86 basic installation and it's the same.

Where can it come from and how do we stop this? Any clue? I'll check by myself but if somebody can help...

"Solved"
 

Actually I solved it somehow. I installed SuSE Linux 9.2 for x86_64. This weird mouse behaviour is not there. I've been using Mandrakelinux for the last couple of years, but now that SuSE is working better on my machine, so I'm back to SuSE it seems... (Untill someone can confirm that this bug is no more in mdk at least. :) ) Too bad - I like Mandrake.

Anyway; I have no idea of what the root of this problem might be. It seems to be Mandrake only at least...

-mj

Well i don't know if it's from mandrake but i was about to try another distrib too. But too bad, i like mandrake too...

The problem seems to not be only the mouse or keyboard. I've been looking at my computer and i see that everytime the freeze occur, the hard drive is being access. It's seems like the whole system is freezing at the same time. But I don't see any suspicious process at that time... i tried to update bios and everything, different configs, but none has work... i'm giving up...
Well i think i'll have to try Suse too!

If somebody has a clue...

Not solved after all - but found probable source
 

Actually today the problem migrated to my SuSE-installation as well. It was not here yesterday. I also noticed that my network card had changed name in 'lspci'. Now it's using the sk98lin-driver. (I can't remember if it used another one before.) It even receives another IP-address from our DHCP-server. So I tried to disable the network to see if that was the source of this trouble - and lo and behold - it was. If I'm stopping the network the mouse and keyboard (and everything else) behaves. Not a good solution this either...
I'll try to see if I can fix this by using another module for the network card or giving it parameters... This is just weird.
-mj

Update
 

Well it seems definetly to be network card related this problem. I do a 'lsmod' with and without this wird behaviur and diff the output and I get;
And a 'tail -f /var/log/messages' gives a lot of errors like theese;
Here is one that seems to have the same trouble as us; http://pcworld.pricegrabber.com/rati...771/id_type=M/

Hmmm...

This really is weird. The network was up and running yesterday. No bugs. Another weird incident was that when I started Windows after installing SuSE, Windows couldn't find the network card! Rebooted Windows and it could. And now this morning when I started SuSE - it has this bug related to the network card. Maybe it's something with our Shuttles, or do other Marvell users experience this as well?

Re: Update
 

I have seen the same behavior with my SN95G5 - if I reboot the computer without powering off, windoze or linux have problems detecting the Marvell on-board NIC correctly. The only workaround I've found is to physically remove power between boots (I've tried disabling all wake-on-LAN settings from the BIOS with no success).

TV

Found a workaround
 

http://www.lxtreme.nl/index.pl/blog/1101900807 has a solution to the problem. Quite a "hacky" workaround, but it works. Finally I can remove my USB network card.
-mj

fix found for sn95g5 vpd errors with lan device
 

I recently found that it is possible to fix the Marvell Yukon Gigabit ethernet device so that it does not produce errors related to the VPD Keys. The issue is that the VPD data was not correctly installed by Shuttle onto the ethernet device. The way to fix this is to utilize a patch put out by ASUS at:

http://www.asus.com/support/download...ch.zip~zaqwedc

This link has a dos-executable and patch that will correct the checksum error, even though it was intended for the K8V motherboard, and not the shuttle SN95G5. However, both boards have the same ethernet device with the same problem, and I found that the solution has worked on three different systems.

good luck.