Umm wierd.

For me it kept failing during compile with a 404 from OpenELEC.tv
So it could have been that it wasnt available when I was trying.

Will you be posting regular Intel builds?
Or only Intel_PVR builds?

Well, when I post some, then just PVR builds because I need the PVR functionality by myself.

Hoping someone can help me.

I just tried ericab's latest build:
OpenELEC_frodo-Generic.i386-devel-20120612105025-r11290...rodo-r15840.tar.bz2
It booted fine but I had no audio so I changed the settings and rebooted. After reboot I was greeted with:

Abnormal Exit. Exited with code 255
Is Xorg running? Check /var/log/Xorg.log

I popped in another USB stick which had a previously created usb installer_script. It booted, I installed OpenElec to another USB and again I get the same error! Tried using various USB sticks can't get rid of it

A6-3500
gt430

Edit: Not sure what I did, but have managed to revert to ericab buid from the 6th

yikes

i dont know what to tell you..
next time attach some logs so we can take a look;

ive updated to OpenELEC_frodo-Generic.i386-devel-20120612144214-r11298__XBMC-nv_290.10-frodo-r15841.tar.bz2

(in Latest)

and everything is running smoothly; give it a shot.


**Edit
i'll appended the Nvidia driver version in filenames used in builds from now on


**Edit 2
i just noticed my latest build OpenELEC_frodo-Generic.i386-devel-20120612144214-r11298__XBMC-nv_290.10-frodo-r15841, i accidentally reverted back to 290.10 ... sorry .... tomorrow it will be back to 295.53 ... its proven sofar to be safe.

Intel x86_64 build is up!

SavellM wrote: What happened about the fresh PVR build? It seems like nobody has had luck so far compiling one of these...

Hmm, I'm getting random lockups with OpenELEC_frodo-Generic.i386-devel-20120612144214-r11298__XBMC-nv_290.10-frodo-r15841.

Would anyone like logs or is it a known issue that will be dealt with in time?

ericab wrote:
That is awesome about 295.53. I am going to test my GT640 card soon with that build.

Chill dude.

I've been trying to pull a PVR build for you all day, but kernel.org is down.
So Im unable to pull down linux.

As soon as kernel.org is back my hands are tied.
But it has been retrying connections for the last 5 hours.

www.downforeveryoneorjustme.com/kernel.org

Just go to www.kernel.org its down!

SavellM wrote:
Had the same problem this morning but it seems to be back up again now...

--2012-06-13 15:20:31-- www.kernel.org/pub/linux/kernel/v3.x/linux-3.2.19.tar.xz
Resolving www.kernel.org (www.kernel.org)... 149.20.20.133, 149.20.4.69
Connecting to www.kernel.org (www.kernel.org)|149.20.20.133|:80... failed: Connection timed out.
Connecting to www.kernel.org (www.kernel.org)|149.20.4.69|:80...


Still getting that

SavellM wrote:
Very odd indeed... Do you clear your sources directory before a build? To do a clean build you only need to run make clean.

The source tars, etc are cached locally in sources so the build only needs to hit the Internet for new packages/updates.

I will do a Generic PVR build now as one off... So you can get your build system up and going again...

Yup I removed everything, and started from scratch.
Might as well do it all over again

Thanks dude.

Umm kernel.org is up again now, and build is continuing...

So if you havent started with Generic PVR dont bother, mine is going

SavellM wrote:
patiently waiting for AE and PVR and hoping it will work on my system. Been waiting for this day for a long time!

Will be testing as soon as its up

SavellM wrote:
It's already off any running so I'll let it complete and post accordingly...

hey Vic, and word on that NFS patch ?
also, what is the location of this data in the source tree ?

ericab wrote:
Hey Eric, it was a little more difficult than I first thought... Basically, I had to modify the NFSFile.cpp classes to create a caching mechanism. The patch uses the negotiated buffer size (ie. 1M in my case) to cache and logically reads/seeks data in the cache... If it is not in the cache then it hits the NFS share to fetch the next 1M...

To be honest I didn't see a huge difference on my network and the more I look at it the more I think it may have something to do with libnfs as mounting the NFS share at the OS level works without a hitch... I'll keep on investigating as I really don't want permanent mounts at the OS level if I don't have to!

Happy to share the patch with you if you would like to test?

Cheers!