Arch Linux

tux

Member

From: Wonderland

Registered: 2007-04-28

Posts: 6

WINE painfully slow

WINE is unbelievably slow on both of my computers with Arch - it takes like 10 minutes to start winecfg, and several minutes changing tabs.
I'm using kernel 2.6.20 with the beyond2 patchset and the same kernel config on them both. I just tried installing Debian on one of them, and WINE worked all fine with the exact same kernel and config.
I've also tried compiling WINE myself, without luck.

The only thing I could think of is that I have disabled all AGPGART and DRM support in the kernel, because I am using a PCI-Express NVIDIA graphics card. However, 3D acceleration is working all fine (I'm using NVIDIA driver 1.0.9755). And, it works fine in Debian with these settings.

Help!!

UPDATE: See next post.

Last edited by tux (2007-04-29 16:28:09)

---

Archer since 2005 - and proud of it!

tux

Member

From: Wonderland

Registered: 2007-04-28

Posts: 6

Re: WINE painfully slow

Just tried the kernel26 and kernel26beyond stock kernels - same problem!

Seriously, this is annoying. I need WINE, but Arch is the only distro out there for me.

Last edited by tux (2007-04-29 16:29:43)

---

Archer since 2005 - and proud of it!

Gullible Jones

Member

Registered: 2004-12-29

Posts: 4,863

Re: WINE painfully slow

Hmm. Any unusual console output?

tux

Member

From: Wonderland

Registered: 2007-04-28

Posts: 6

Re: WINE painfully slow

Hmm. Any unusual console output?

No, not at all. It is just damn slow...

Maybe it could have something to do with my da_DK.UTF-8 locale?

Last edited by tux (2007-05-09 21:10:33)

---

Archer since 2005 - and proud of it!

iggy

Member

From: Germany, L.E. - Leipzig

Registered: 2004-10-17

Posts: 367

Re: WINE painfully slow

same problem here! i need help! why it is so slow? is there anyone who has an idea?

---

sorry for my bad english

Theomachos

Member

From: Germany

Registered: 2007-07-31

Posts: 67

Website

Re: WINE painfully slow

same here....

---

There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce

test1000

Member

Registered: 2005-04-03

Posts: 834

Re: WINE painfully slow

This happens if you have not started network in /etc/rc.conf DAEMONS line. I think more specifically setup the lo interface.

Yes I know, there should be another way to setup the lo interface than having to startup network in DAEMONS.

---

KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein

Theomachos

Member

From: Germany

Registered: 2007-07-31

Posts: 67

Website

Re: WINE painfully slow

Hm....lo interface is set up correctly....
Must be something else

---

There is one thing even more vital to science than intelligent methods; and that is, the sincere desire to find out the truth, whatever it may be.
Charles S. Peirce

test1000

Member

Registered: 2005-04-03

Posts: 834

Re: WINE painfully slow

hmm... then perhaps something in networks... 've had this problem befor, i'll be darned to find out what the problem was... o_O

---

KISS = "It can scarcely be denied that the supreme goal of all theory is to make the irreducible basic elements as simple and as few as possible without having to surrender the adequate representation of a single datum of experience." - Albert Einstein

aka_hans

Member

Registered: 2008-03-13

Posts: 17

Re: WINE painfully slow

Did you install cabextract? I remember about a year ago I was having similar problems, installing cabextract solved it and made WINE very usable.

Bralkein

Member

Registered: 2004-10-26

Posts: 354

Re: WINE painfully slow

I've not had this specific problem with Wine, but whenever I run into issues I always try with a fresh ~/.wine directory. You could rename your current ~/.wine directory and try winecfg to see if it works better, if not you can nuke the new ~/.wine directory and rename your old one back to how it was.

Also, you could try starting something under wine on the console with extra debug output enabled to see if anything interesting comes out of there. Unfortunately, wine can produce an awful lot of debug info if you tell it to, so enabling all output is not a good idea. Try something like WINEDEBUG=warn+all winecfg

More info here http://www.winehq.org/site/docs/winedev … bg-control