Fed up with constantly installing new Chromium OS version from USB?
Look no further, I now present to you – “The Dev Update Server”.
Resplendant with the finest daily compilations, its ready for you to upgrade your installed ChromiumOS to the latest and greatest x86-generic version.
Check the status of the Dev Server on twitter @chromium_bot since the server needs to go offline to build the latest version at around 05:00 GMT daily. Once compiled and presented, the status will say its available.
In order to update go to command line on your deployed Chromium ([ Ctrl ] [ Alt ] [ F2 ]) and log in as chronos with the password of ‘password’ (or whatever your distribution is set to). You can also use SSH.
Then sudo to su
sudo su
Once in the admin shell, update the client with the following:
For amd64 builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:8081/update
For x86 builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update
For amd64 special builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:9080/update
For x86 special builds
update_engine_client --update --omaha_url=http://chromebld.arnoldthebat.co.uk:9090/update
This will take a while dependant on a couple of things:
- Whether the image is compiled yet (the dev server creates a sync image on 1st use which can cause timeouts)
- What other load the server is under.
- Your bandwidth (some of the updates can be large).
Simply try the update command again if you get an update error or timeout similar to the below:
LAST_CHECKED_TIME=0 PROGRESS=0.000000 CURRENT_OP=UPDATE_STATUS_REPORTING_ERROR_EVENT NEW_VERSION=0.0.0.0 NEW_SIZE=0 LAST_CHECKED_TIME=0 PROGRESS=0.000000 CURRENT_OP=UPDATE_STATUS_IDLE NEW_VERSION=0.0.0.0 NEW_SIZE=0 [1228/134834:ERROR:update_engine_client.cc(237)] Update failed.
Once its running you should see notifications from the server saying all is fine and progressing:
LAST_CHECKED_TIME=0 PROGRESS=0.000000 CURRENT_OP=UPDATE_STATUS_CHECKING_FOR_UPDATE NEW_VERSION=0.0.0.0 NEW_SIZE=0 LAST_CHECKED_TIME=1356707131 PROGRESS=0.000000 CURRENT_OP=UPDATE_STATUS_UPDATE_AVAILABLE NEW_VERSION=0.0.0.0 NEW_SIZE=237376171 LAST_CHECKED_TIME=1356707131 PROGRESS=0.000000
Finally, the download will begin:
LAST_CHECKED_TIME=1356707131 PROGRESS=0.000012 CURRENT_OP=UPDATE_STATUS_DOWNLOADING NEW_VERSION=0.0.0.0 NEW_SIZE=237376171 LAST_CHECKED_TIME=1356707131 PROGRESS=0.000012 CURRENT_OP=UPDATE_STATUS_DOWNLOADING NEW_VERSION=0.0.0.0 NEW_SIZE=237376171 LAST_CHECKED_TIME=1356707131 PROGRESS=0.002867
If all goes well, the updates will download and the install will progress to finalising:
CURRENT_OP=UPDATE_STATUS_FINALIZING NEW_VERSION=0.0.0.0 NEW_SIZE=237376171 LAST_CHECKED_TIME=1356708887
This can tale a while (go for a beer whilst waiting) but ‘should’ result in:
CURRENT_OP=UPDATE_STATUS_UPDATED_NEED_REBOOT NEW_VERSION=0.0.0.0 NEW_SIZE=237376171 [1228/154101:INFO:update_engine_client.cc(241)] Update succeeded -- reboot needed.
You should now also be able to update your stateful partition (where dev tools sit) using:
sudo stateful_update
Which in turn should output:
Downloading stateful payload from http://vps2.arnoldthebat.co.uk:8080/static/stateful.tgz HTTP/1.1 200 OK Date: Fri, 28 Dec 2012 15:42:43 GMT Last-Modified: Fri, 28 Dec 2012 15:07:27 GMT Content-Length: 42236449 Content-Type: application/x-gtar Server: CherryPy/3.1.2 Connection: Keep-Alive Successfully downloaded update Performing standard stateful update.
You ‘should’ be able to use the process above to update Hexxxeh and others vanilla builds as well but this is (as ever) completely untested.
Subsequent updates for the OS and stateful partition will now automagically point to the new dev server (you can change using the –omaha-url noted above) so all you need to do is:
update_engine_client --update
and
sudo stateful_update
Finally, in all cases, reboot your client!
Usual Caveats, E&OE stand. The Update Server could work fantastically and make you more attractive to other humans/species from other worlds as well as updating your base build perfectly. It could also create a black hole of NGC 4889 proportions and end the world as we know it as well as bricking your install completely. You have been warned!
Further details and notes available http://goo.gl/OBG2Y
I have installed your build on my desktop. Is there an easy way to be able to dual-booting like this:
https://sites.google.com/site/chromeoswikisite/home/what-s-new-in-dev-and-beta/developer-mode
Hi Onkell
No idea on the dual boot – sorry. Never had the reason to use it!!
Hi there,
This has worked brilliantly on 5th February 2013 Hexxeh code on my trusty Samsung NC10 which is now a pure Chromium install – thanks so much!
Curious – this morning (6th Feb) the inbuilt Chromium update (settings|help) recognised it was ready for an update and downloaded this almost like a *real* Chromebook – yay!
Does this process then mean that the update server is working without my needing to type “update_engine_client –update” (which works fine) but automated is soooooo much better!
Just for info for anyone other reading this, after following your instructions for the update server and the stateful_update, I also followed https://gist.github.com/rikels/4031126 to get Youtube (and some other stuff) working.
Keep up the lunacy!
Hi
Once you have run the update client once, you will stay pointed to the dev server so updates ‘should’ be automatic.
Will updates be automatic for both types of updates after updating the first time, or just the first type (non-stateful)?
Only the non stateful. Last time I checked, stateful wasn’t working anyway!
Please ignore the HTML issue in previous message – rewritten below…
Umm – just to clarify – the inbuilt Chromium update (settings|help) was after I ran your guidance.
Wondering if it is your process which has allowed the automated Chromium update…hope that’s clearer now!
Yes. Since you have updated via the dev server, subsequent updates can be started via settings/help
One more quick question – AFAYK, should ethernet work with this? Thanks
Certainly should work! What type is it since it could be drivers….
AFAIK the model is Marvell Yukon 88E8040 (from “Googling Samsung NC10 ethernet”. Advice welcome!
On the prior point, after the update server runs, should I run the stateful_update everytime, then run the sudo su for Youtube etc. as above – or is there any way of automating this into one process?
Thanks!
I’ll see what I can do about Ethernet. It can be a stinker getting modules to compile and install cleanly. I’ll let you know…
Have you looked here: http://www.marvell.com/support
In addition, try the following (completely untested but Ive compiled the drivers for fun)
sudo su
mount -o remount, rw /
cd /lib/modules/3.4.0/kernel/net/
mkdir ethernet
cd /lib/modules/3.4.0/kernel/net/ethernet
mkdir marvell
cd marvell
wget http://chromium.arnoldthebat.co.uk/files/fw/lib/modules/3.4.0/kernel/net/ethernet/marvell/skge.ko
wget http://chromium.arnoldthebat.co.uk/files/fw/lib/modules/3.4.0/kernel/net/ethernet/marvell/sky2.ko
sudo insmod /lib/modules/3.4.0/kernel/net/ethernet/marvell/skge.ko
sudo insmod /lib/modules/3.4.0/kernel/net/ethernet/marvell/sky2.ko
sudo reboot
Could you add a Broadcom BCM43XX driver? I think I should have the files (I’ve copied them from an older build but I don’t know how to add them):
brcm80211
brcmutil
brcmsmac
These are the folders but can I add them at this way?
Also : When I try to do the update
(I typed update_engine_client -update -omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update) then I only have:
Error getting dbus proxy for org.Chromium.UpdateEngine: GError (3): Could not get owner of name ‘org.Chromium.UpdateEngine’ : no such name.
What should I do?
One last thing – since this morning’s devserver is up notification, I have been unable to do any update.
update_engine_client –update generates only failures and settings¦help only says “up-to-date” presumably as there is no update to succeed behind the scenes.
I will try again tomorrow after devserver notifies it is back up but thought I would let you know anyway!
Have tried update again after today’s new compile.
Same issue. Have also tried as full path update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update rather than just update_engine_client –update.
Thoughts welcome!
Just FYI – not a one-off – have been trying all day yesterday and consistently since today’s compile reported it was up…
Looks like a stuck port in use. Try again please!
Re stateful partition – I believe thats going to always be manual since its developer specific
Hi Tony – whatever it is you did – it worked!
Thanks loads
Mind you – ethernet still doesn’t work – not bothered – just interested!
Thanks again
See above!
re. your last “see above” – tried again for ethernet and – nowt.
not urgent at all – was much more relevant to access the update server, which is sorted as above.
is there anything I should actually do re ethernet, should it just be working, aob?
Sorry – I shouldn’t have posted where I did. See below!
Reposted:
Have you looked here: http://www.marvell.com/support
In addition, try the following (completely untested but I’ve compiled the drivers for fun)
sudo su
mount -o remount, rw /
cd /lib/modules/3.4.0/kernel/net/
mkdir ethernet
cd /lib/modules/3.4.0/kernel/net/ethernet
mkdir marvell
cd marvell
wget http://chromium.arnoldthebat.co.uk/files/fw/lib/modules/3.4.0/kernel/net/ethernet/marvell/skge.ko
wget http://chromium.arnoldthebat.co.uk/files/fw/lib/modules/3.4.0/kernel/net/ethernet/marvell/sky2.ko
sudo insmod /lib/modules/3.4.0/kernel/net/ethernet/marvell/skge.ko
sudo insmod /lib/modules/3.4.0/kernel/net/ethernet/marvell/sky2.ko
sudo reboot
This brings me very close to getting my Marvell chipset working…
Insmodding sky2.ko gave me “Unknown symbol in module”. dmesg said “Unknown symbol page_address”.
In desperation, I hex-edited the module to remove “page_address” (i duplicated a nearby symbol with the same number of characters), and it loaded!
But, dmesg says:
sky2: driver version 1.30
sky2: 0000:01:00.0: cannot map device registers
sky2: probe of 0000:01:00.0 failed with error -12
So close, I can smell it 🙁
Any ideas?
I hear awful things about the sky2 driver. Would sk98lin work better?
As a followup, I ended up compiling the chromium kernel from scratch with sky2 support and injecting it into your build. It works wonderfully 😀
Hi – thanks for the ethernet update.
If it works, will it then stay usable or will it be wiped out each time there is a dev server update?
If it is going to continually be wiped, is it something you would consider adding to the build or automating as a script?
All of the above of course is defeated by the object of being cloud-connected anyway…
Hi – It will get wiped as part of Dev updates.
I am looking to wrap all changes and updates together as a post update script and more importantly, dev server based packages. The latter means once you have got them once, you will always keep them. Its just going to take time (and I dont have a lot of that at the mo!)
Noted – and thanks for all you are doing for us nuts!
I am happy – I now have a consistently updateable ChromiumOS device with only two minor scripts to run afterwards, giving me a pretty stable solution.
Ben
Umm – at the risk of being a PITA – dev server hasn’t come back up from early this morning…thanks!
Argh. I’ll have to do some proper tinkering to fix it. I’ve reset tonight with logging so will hopefully have something to fix later this week…
Hi Ben.
Can you test with update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:9020/
Hopefully that should work. If you could test again after tomorrows compile as well.
Thanks..
Forget the above – its still dead. Ill fix it on Sunday!
Hi – it actually worked fine this morning on the original basis on port 8080 .
However, as a good tester I have retested according to your comment tonight. As per your comment, the update failed at the first attempt, perhaps because after “arnoldthebat.co.uk:9020/” there is nothing further – I added “update ” after the slash and this seemed to kick off fine. However the first attempt hung indefinitely at progress 0.741818 and further attempts failed completely, whether with the suffix of “/update” or not. I have rerun the original path on port 8080 and this also crashed. Finally, I ran purely “update_engine_client –update” and this has worked as usual (presumably on the original port 8080).
I will test tomorrow after the compile again and update the comments.
Will The Dev Update Server work with builds running off of USB/SD cards? Or would it try and write to my hard disk? Thanks
One to test… It ‘should’ do the USB stick but I cannot guarantee it!
Hi – it’s your resident tester again.
Dev server has come back up this morning with the latest version according to @chromium_bot, but updates are still failing.
I will go and wait quietly now until I hear from you and I won’t play until told otherwise!
Ben
Aye – its fairly broken at the moment. I think my provider has been tinkering with IPv6 which has broken the binding on the web server. Ill have a look as soon as I can!
[EDIT] – Looks like I was right: IOError: Port 8080 not free on ‘::’ and the server bombs out
Ill get it sorted so bear with me…
Looks like the dev servers very broken @ http://chromebld.arnoldthebat.co.uk:8080. I’ll try to get it fixed this weekend..
Please bear with me until its sorted.
Just seen your latest. Will wait for further news over weekend or thereabouts!
Thanks as ever – Ben
Should be working again – I’ve just updated 2 machines successfully.
Yup – have tested this on the settings|help then again via port8080 update_engine_client and all seems fine.
Ta!
Hi! Could you also say me how I could add a driver for Broadcom BCM43XX? Because I had two files from an older Chromium build but insmod said they weren’t working.
And when I try to download every time it says it doesn’t work:
“Error getting DBus Proxy for Org.ChromiumOS.UpdateEngine: GError (3) : Could not get owner of name ‘org.chromium.UpdateEngine’ : no such name”
What can I do against that?
I’m using the 10th February Build (Developer Build-TonyD)!
Broadcom drivers are fairly broken at the moment. I’m looking to start another test build in the next few weeks. Ill post a how-to once I’ve got it working..
also, have a look http://linux.dell.com/files/cto/ for a potential working version (Feb 2013)
Thank you!
Yes! I didn’t see there was a new build! Thank you thank you!!
But will the Broadcom Driver be kept after a dev update?
Have a look here http://arnoldthebat.co.uk/wordpress/2013/02/24/how-to-get-the-broadcom-wireless-drivers-working/
Updates will remove the driver but rerun the above to pop it back
For Broadcom, have a look here http://arnoldthebat.co.uk/wordpress/2013/02/24/how-to-get-the-broadcom-wireless-drivers-working/
Hi there – things seem more stable and yesterday’s update went fine.
However, when dev server goes down to build latest compile, it shows “today’s” date as the build number. The latest compile has the previous day’s date as the build number, then the latest ARM/X86 version has “today’s” date again as the build number.
i.e. today is Wednesday 20th Feb. Three consecutive @chromiumbot messages:
Dev Server going down. Latest compile (version 20130220030101) begins
then
Latest Compile (version 20130219030101) completed. Dev Server is up!
then
Chromium ARM/x86 version 20130220030101 Instructions at…
Is this an issue or is it safe to keep running updates?
Thanks
Hi Ben
Its safe to use, just crappy scripting on my part!
Hi – today’s build (20130307030101) doesn’t seem to support any sound – which normally works fine!
As per previous emails, I run a code provided by https://gist.github.com/rikels/4031126 which is “curl -L http://goo.gl/R4Amj | bash” and this makes Youtube, MP3 etc, work fine.
I know that code hasn’t been changed – has this latest build done anything to affect my sound drivers? As before, I am running a bog-standard Samsung NC10 and your build has always worked well.
Thanks
Further – to sense-check this I downloaded yesterday’s build 20130306030101 from your repository. I tried this on USB, and then as a fresh install and sound now works fine again, even with native apps like Google Music.
I won’t do any updates from Dev Server till advised everything is fully working version again.
Regards and thanks,
Ben
Final addnedum -curiosity got the better of me and I ran today’s update (20130308030101) and the sound issues seem to have resolved in this update.
However there is now no option to put backgrounds on and a right-click on the home screen just brings up the option to auto-hide the toolbar and nothing else!
Ben
Hi Ben
I think you are falling foul of the fact these are cutting edge so expect stuff to fail as and when. In these builds I don’t change any of the default packages…
That makes sense – guess when there’s a build I am next happy with, I shall stop running updates for a while!
Just OOI then – would a build on a given day be the same regardless of developer, be it you, Hexxeh or A.N. Other?
If they are using the standard compile switches then they will be the same…. I don’t know about Hexxeh but I intend on adding packages to the builds ‘soon’. Just struggling to find the time at the mo!
Backgrounds are still not working on 16th March Build…
Could you please look at my question I’ve posted in the “Synaptics Touchpad” topic? It’s the 7th.
Thank you!
Is the Dev Update server down? I tried it for the first time yesterday and it didn’t work. So I hit the URL
http://chromebld.arnoldthebat.co.uk:8080/update
with a browser and it gives me a 500.500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "/usr/lib64/python2.6/site-packages/cherrypy/_cprequest.py", line 606, in respond
cherrypy.response.body = self.handler()
File "/usr/lib64/python2.6/site-packages/cherrypy/_cpdispatch.py", line 25, in __call__
return self.callable(*self.args, **self.kwargs)
File "/usr/lib/devserver/devserver.py", line 667, in update
return updater.HandleUpdatePing(data, label)
File "/usr/lib64/devserver/autoupdate.py", line 688, in HandleUpdatePing
protocol, app, event, update_check = autoupdate_lib.ParseUpdateRequest(data)
File "/usr/lib64/devserver/autoupdate_lib.py", line 181, in ParseUpdateRequest
request_dom = minidom.parseString(request_string)
File "/usr/lib64/python2.6/xml/dom/minidom.py", line 1928, in parseString
return expatbuilder.parseString(string)
File "/usr/lib64/python2.6/xml/dom/expatbuilder.py", line 940, in parseString
return builder.parseString(string)
File "/usr/lib64/python2.6/xml/dom/expatbuilder.py", line 223, in parseString
parser.Parse(string, True)
ExpatError: no element found: line 1, column 0
Looks like there are some XML parsing error. Keep up good work! Thanks for all your work!
Hi
That URI always fails with a HTTP 500 since its http://chromebld.arnoldthebat.co.uk:8080/ that humans should look for. The /update is what the devices call and pass specific payloads to make it actually do something!
Keep trying the update via the omaha URL. Sometimes it will work, other times it will time out due to compile load on the server…
Hi – has the dev server fallen over again? I can see that there is a new version but my computer doesn’t want to pick it up – and there is no dev server down or up this morning before new version created.
Also, last couple of days version seems really rough – not sure if this is Chromium issue (e.g. tabs not closing properly) or result of unwell dev server.
Ta as always!
Hi Ben
Ive not looked at it for a while so if its not behaving on a particular day, then simply try again the day after. The Dev Server is certainly not the most stable of beasts (more down to my scripting than anything) so expect it not to work sporadically.
As to roughness? You get what Google distribute since I don’t do anything more to it that they distribute (currently). In plan are ebuilds to package up all the stuff the community has been working on, but that works around my day job so it will take as long as it takes..
Whilst not wanting to annoy you and also recognising time is fleeting, could you please update on my query 20th March? Thanks
Updated. My you are a needy lot!
Thank you for supporting us in our need! Just for the record, it is now five days since the update server worked – and it shows failed when tried every time from chronos login too.
Will keep trying and note your comments.
Ben
No problem. I’ll take a look tomorrow!
Hi Ben
Just updated two laptops with no problems so unless last nights update fixed stuff, the problem looks to be at your end?
Have you asked the kind people on https://plus.google.com/u/0/communities/118058839614744781012 whether they are getting the same problems?
That said, the way I cobbled the dev server was far from ideal from a debug perspective, so Ill look to tweak it today so at least I can see whats going on under the hood!
Nope – as soon as I try to do update from chronos login, tells me update fail and/or reporting error event. Odd!
OK thanks Ben
Im tweaking as we speak, then Ill retest….
Testing has re-occurred and it still appears to be working. Tonight’s scripted build will show any problems but if you want to get to build 3900, feel free to try it now!!
Hi – thanks for doing this.
Still got the same problems after your testing.
Will see what the morning brings…
Still no joy. Getting “CURRENT_OP=UPDATE_STATUS_IDLE”
then
“(0325/072452:ERROR: update_engine_client.cc(248)] Update failed”.
Think I will get a new download of source and start again, but prob need to wipe netbook first…oh dear – it was all going so well!
Hi Ben
Ill have a sanity check test tonight (hopefully) just to see that its not broken. Ill let you know.
I need a sanity check myself. To check I am not broken.
Thanks as always…
Just tried again (from version 3900) and updated to 3902 without a hitch. Beginning to think you have a duff intermediate build
Also, see https://plus.google.com/u/0/110874252354659364997/posts/AZwKxPF6TCd for another couple of reports. If you update there, I can centralise stats and see if I can find a pattern. At the very least, whats the version you are using currently?
Weird – this post has now disappeared on Google+!?
Can’t post to the thread on G+!
Version 27.0.1445.2 (188786)
Platform 3877.0.2013_03_19_0545
Firmware 11CA.M015.20090908.RHU
Had been flakey for about four days before most recent update I could do on 19th March, e.g. tabs not closing properly with shadowing/ghosting.
Hope this helps…
Hi, has anyone tried this update server with the ChromiumOS image released by Dell on February 20th?
That’s the one from this page http://linux.dell.com/files/cto/ if you don’t know what I’m referring to.
Hi. It does work I believe but will scrub the wireless drivers and reset to a vanilla build
It did get rid of the wireless drivers, you were right.
And reboot is needed between the engine update and the stateful update.
Still, I’d rather be up to date, even if it means having to use a wifi dongle.
Thanks!
Hi Ben
I installed the dev server update to my Dell Mini 10, which was previolsy running Dell’s April 13 Chromium build.
The install went fine. My problem was when I tried to go into shell and get the wifi working that the sudo password was incorrect.
I have tried dell1234, facepunch,chrome, chronos and they all do not work.
Is the password something else?
Cheers
Try the password of password
Its Tony BTW, not Ben…
Cheers Tony!
Not sure what the problem is, but the update_client_engine never seems to work, it always gives back a NEW_SIZE value and that’s it. Somethimes it says it found an update, but it doesn’t update and reports an error.. update_client_engine –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update is the correct statement after sudo su?
Works for me update_engine_client –update –omaha_url=http://chromebld.arnoldthebat.co.uk:8080/update so just double check please to ensure you weren’t just unlucky!
Did try it a lot, but I will try again this evening to see if it works now.. Does it matter that I’m running Chromium from a USB diskdrive?
This are the messages I get while trying to update:
https://docs.google.com/file/d/0BwfAEr7sESpTSXQ1ZWpmMnZrUzA/edit?usp=sharing
Ive sent you a request to the doc link above. Ill have a look once approved.
Yup, I can confirm its not overly well at the mo.. Devserver complains with XBuddyException: Local artifact not in static_dir at x86-generic/latest/chromiumos_test_image.bin since the file is missing so its a change in behaviour.
Ill go and tinker and report back (hopefully) soon.
Hi
This is fixed now. Hopefully tonight’s rebuild will keep it fixed!
Posted on Google+ too –
Hiya @Rikels and @Tony latest version of plugin set with Flash etc https://gist.github.com/dz0ny/3065781 using JjY4W doesn’t work – endless loop of login screen to black to login – tested with old April version of Chromium and aok – only a problem for last two weeks. Advice/fix welcome!
Posted the same thing yesterday 🙂 https://plus.google.com/100123275722092627008/posts/G7QZE1RGU6Z
Use shagr4th’s version as posted in the comments: https://gist.github.com/shagr4th/6178203
Do do it directly from the console
$ sudo su
# curl -L http://goo.gl/oGHyPi | bash
This worked for me.
Thanks Tony, everything is ok now 🙂 Update is finally working!
Hi Tony,
I’ve checked the @chromium_bot and the server seems to be running but I’ve trying to update for a few days with no luck. Is the server ok? Should I just wait a little longer and check again tomorrow? Thanks
Hi
Compiles are failing at the moment and it looks like its from the main repo so something I may not be able to sort. As soon as upstream is fixed, the Dev Server will be working again.
Thanx for quick reply.
Yes, running from USB …still need to fall back to windows from time to time (like for doing Skype). And windows doesn’t run that well from a stick 🙂
Found an old procedure …but it lacks certain instructions that I can’t fill in myself 🙁 http://skypeonchromeos.blogspot.nl/2011/09/running-skype-on-chromeos-notebook.html
Googled for hangout fix, can’t find it …or at least not in a way I can use it. I used https://gist.github.com/shagr4th/6178203 to install Flash and stuff, but still Hangouts wants to download a plugin . Also https://gist.github.com/shagr4th/6178203 gives a headache. Could it be because Talk was faced out and Hangout came into existance.
The chat function of Hangouts work. But I like to have audio and video.
Found some instruction when you have libppgoogletalk.so but can’t find were to download it.
Much appreciated
Stefan
I have the last Dell image(10. april) installed on USB
I tried to get an update. After trying sereral times I finaly I could contact the server, but I got the following and it was looping:
LAST_CHECKED_TIME=0
PROGRESS=0.000000
CURRENT_OP=UPDATE_STATUS_REPORTING_ERROR_EVENT
NEW_VERSION=0.0.0.0
NEW_SIZE=0
LAST_CHECKED_TIME=0
PROGRESS=0.000000
CURRENT_OP=UPDATE_STATUS_IDLE
NEW_VERSION=0.0.0.0
NEW_SIZE=0
after 10 minutes it stppoed and:
[1024/101844:ERROR:update_engine_client.cc(248)] Update failed.
What am I doing wrong?
Thank you for contributing and supporting, so I’m here all day long trying to update my chromium (installed on a PC) but I’m stuck on this error under, what’s going on? I’m using the developer shell (Ctrl+alt+T) this is the only different thing, the rest is the same, and can’t worked yet. u.u
Sorry my english and thank you for help.
Uploaded with ImageShack.us
Hi
The dev server only works for ChromiuomOS installs to hard drives. USB installs wont work. VirtualBox installs can be made to work but that involves creation of a second drive to install to and overriding the install switches..
I don’t know if my screen capture will appear, so here’s the link on imageshack
http://imageshack.us/photo/my-images/856/nb4x.png
Thank you again.
Hi. I have successfully installed chromium os (last build from arnold the bat 64 bit) on my hp 655 dual boot with ubuntu. I wanted to add java, flash and pdf plugns via CLI as he explains on his site, but when i do “ctrl-alt-T” i get crosh and if i type “shell” i only get this “unknown command: shell”. If i try the other system, “ctrl-alt-F2” i only get a blank screen without any cursor. What am i supposed to do in order to have a root shell?
I cannot get the sudo stateful_update command to work whatsoever. Brand new to chromeos any help would be appreciated.
dont worry about it. Looks like the functionality has been removed..
Thanks for the update server! Works great! My only issue is with the stateful update. I get the following:
Downloading stateful payload from http://srv01.arnoldthebat.co.uk:8080/static/stateful.tgz
HTTP/1.1 404 Not Found
I’m coming from a Hexxeh build, not sure if that is relevant or not. Thanks for your help!
Hi
A couple of reports of this so I think the functionality has been removed.