Blog status

For the most part, this blog has been abandoned for something a bit easier for others to update.

Please re-join us @ http://elinux.org/CR48 and help make it a great repository for CR48 knowledge.

Dev build crashing on google search?

If you have the voice search extension installed and enabled, right click on the microphone icon in the top right, and select disable. Seems to fix the problem.

Proxy Settings

One of my biggest gripes so far with the CR48, is waiting for it to detect proxy settings anytime the wifi reconnects. Every time it comes out of suspend, it takes way to long to discover I'm not (and never) use a proxy, before it will let me do anything online.

I was unable to find a place in the settings where I could change this, but I stumbled across chrome://settings/proxy which lets you default it to direct connection!

Now my chromebook works a lot faster coming out of standby and getting back on the net!

About: Pages

For awhile now, we've known we could go to the address about:version or about:flags and get more information or different settings.

I've found theirs an in depth listing of these pages at about:about

List of About pages

• about:appcache-internals
• about:blob-internals
• about:view-http-cache
• about:credits
• about:dns
• about:flags
• about:gpu
• about:histograms
• about:memory
• about:net-internals
• about:plugins
• about:stats
• about:sync
• about:tasks
• about:tcmalloc
• about:terms
• about:version
• about:linux-proxy-config
• about:sandbox
• about:network
• about:os-credits

For Debug

The following pages are for debugging purposes only. Because they crash or hang the renderer, they're not linked directly; you can type them into the address bar if you need them.

• about:crash
• about:hang
• about:shorthang
• about:gpucrash
• about:gpuhang

Be warned however, about:sync has been crashing my browser, however it works fine on my other PC.

Ambient Light Sensor

It seems the features will never cease. The CR48's got a ambient light sensor in it as well, located just to the right of the webcam's eye.

If your display brightness isn't cranked all the way up, and you come into an area of increased light (or presumably walk outside) the display will brighten up for you.

Don't believe me? Turn the screen brightness down in a dim room, and hit the webcam with a flashlight!

Making /mnt/stateful_partition exec friendly

Finally found out how to make the /mnt/stateful_partition exec permission persistant.

open up a shell

CTRL-ALT-T

shell

sudo su

open up /sbin/chromeos_startup - i'll use nano, as I have a tutorial for installing it

nano /sbin/chromeos_startup

Now, when scrolling around in nano, the screen will not refresh properly when scrolling up/down pages, but, we can press CTRL-L to make it redraw the screen

While in nano, CTRL-C will give you you're current cursor position.

We want to edit lines 51, 58, and 67.

Remove noexec, from each of those lines

The line should then look something like .... -o nodev,nosuid .....

You can also remove the ,nosuid if you'll be wanting to install and SUID programs on the stateful partition.

Save the file by pressing CTRL-X and answering Y and pressing enter for the filename.

Reboot, and your stateful partition should be remounted with the correct options from this point forward.

Installing a VNC Viewer, part 2

Installing VNCViewer
**You need to follow the instructions in the Notes post first, to make the partitions writeable

Open up a shell on the cr-48, and

sudo su
mkdir /mnt/stateful_partition/opt (if you haven't already)
cd /mnt/stateful_partition/opt
wget http://www.calliesfarm.com/chromeos/java.tar.gz
wget http://www.calliesfarm.com/chromeos/vncviewer.tar.gz
tar -zxvf java.tar.gz
tar -zxvf vncviewer.tar.gz
rm -rf java.tar.gz vncviewer.tar.gz
ln -s /usr/bin/java jre1.6.0_23/bin/java
mv vncviewer/vncviewer /usr/bin

after it's installed, you should be able to run

vncviewer

however, since there are no close window widgets, there's two ways to disconnect.. either navigate to the vnc server icon once connected, and tell it to disconnect you. or, kill it from the terminal.

Also, in theory, you should be able to link the java plugin to the browser plugins directory, and get java working in browser, however it doesn't work for me, and I'm not sure why at the moment.

It's got shortcomings, but it's a start.