SETI..Linux...wine - a fix

[Hubris]

I (and several others) experienced some issues running the NT CLI under the WINE emulator under Linux. This is THE FASTEST way to crunch, however there are occasional issues where the client will refuse to transmit results that are a little larger than standard.

At the time I gave up....preferring to run the slow native Linux client as opposed to checking the box daily to see if it was stuck.

Evidently this is fairly easily solved with the right shell script.

Link to TPR

As stated in the thread....credit goes to Maojc and TFWitt from our friends over at TPR.

[Ned Slider]

Thank you Hubris for posting this

That's a great neat workaround to what can be an annoying problem - we should have thought of that, hats off

Perhaps someone who is registered with the TPR forums could post thanks from the pond in that thread.

Hubris, out of interest do you have any 3-way comparisions for times running Win/Native cli vs Linux/Native cli vs Linux/Wine/NT cli on the same (or similar) hardware with the same (or similar) workunit?

Ned

[GAMMAGOAT]

Is this a problem only when auto transmitting, or is it always present? I would like to use linux but would hate to lose time trying to figure out how to use info on link. I can hardly use windows.

[Ned Slider]

This is a very specific intermittant problem that only affects people trying to run the WINDOWS seti client under LINUX using wine. (the reason people do this is that the windows client under linux is faster than the native linux client on linux).

The simplist thing to do is run the linux client on linux and you'll be fine

Ned

[Hubris]

I myself have never done comparisons of the 3 as you stated. Maojc of TPR has done these comparisons.....running the NT CLI under Wine is actually slightly faster than running native under Windows, and is considerably faster than the native linux client.

Originally posted by Ned Slider on 04-06-2004 at 01:42 PM
Thank you Hubris for posting this

That's a great neat workaround to what can be an annoying problem - we should have thought of that, hats off

Perhaps someone who is registered with the TPR forums could post thanks from the pond in that thread.

Hubris, out of interest do you have any 3-way comparisions for times running Win/Native cli vs Linux/Native cli vs Linux/Wine/NT cli on the same (or similar) hardware with the same (or similar) workunit?

Ned

[Ned Slider]

Yes, I've only ever compared under linux with and without wine (and as we know, wine is significantly faster). Perhaps I'll run the benchmark on a dual boot machine to get a like for like comparison for windows too.

Ned

[thelmores]

if only linux would get some descent video drivers/games, i swear i would drop windows for good!

interesting stuff here........

will have to try and incorporte into our seti linux faq......

[elusive-dragon]

thelmores with WINEX you can play many games on linux anyway..though ive never used it yet personally...

yet!

Just havent had the time, though I actually paid for a copy of WINE but SUSE has been out of stock forever now lol

[thelmores]

yea, things are getting closer, but i still cant give up windows for gaming...... yet!

[GAMMAGOAT]

Hmm. One question remains, is this problem only when auto transmitting or would one always have to worry about it poping up.

[Hubris]

I found the problem popped up about once per week...I'd come back to my computer and find it wasn't transmitting the workunit.

Running this script, you'd never have to worry about this problem.

[GAMMAGOAT]

Thank you Hubris. I was just wondering if I would have any problems stocking up on completed wu's and then transmitting them manually. I know very little about linux and would like to get it and seti up and running togather with out alot of fuss at first.
thanks again.

[elusive-dragon]

only reason ive not switched all my systems to linux...as badly as i want to...as far as i know its hard to oc with linux, windows has clockgen now and thats such an easy way to squeeze so much more out of a system!

[Ned Slider]

As long as you choose a recent up to date distro then linux can be extremely easy and quick to install these days. I used RedHat 9 and was installed and crunching seti within 1 hour

Although you may have problems with your listed MB - the nForce2 LAN adaptor is not recognised by most distro's out of the box so you'll need to install a driver - sometimes not easy under linux - or put in a older pci nic card that is autodetected. If you're new to linux, it'd be very temped to throw in an older pci card before you install and that could save you a LOT of hassle

Wine is not the easiest thing to set up, so if you want to be up and running quick, just download the native linux client and run it the same way you would with the dos client

Ned

[Ned Slider]

Originally posted by Ned Slider on 04-06-2004 at 08:42 PM
Hubris, out of interest do you have any 3-way comparisions for times running Win/Native cli vs Linux/Native cli vs Linux/Wine/NT cli on the same (or similar) hardware with the same (or similar) workunit?

Ned

Here's the answer for anyone interested, same hardware, same WU (AR=0.417) so it's a true like for like comparison. No special tweaking was done.

Sony laptop, XP1400+ at 1200 MHz, 100fsb, PC133 SDRAM memory at 133fsb. All using V3.03 client, times in hh:mm

WinXP: 5:02
Native linux (RH9): 5:36
WinNT client under wine/linux (RH9) 5:00

Ned