|continued from:||Chromebook hotwiring part 1 [link]|
|continued to:||Hotwiring a Chromebook to run Minecraft continued [link]|
Summary. Installing Minecraft on a Chromebook running an Intel-based processor.
Samsung 11.6" Chromebook
|CPU:||Intel Celeron N2840|
|LCD:||11.6" HD (non-glare), UMS1|
|MEMORY:||2GB (DDR3L 1333MHz/On BD 2G)|
|HDD:||e.MMC 16GB (On Board)|
|COMMUNIC:||Intel 802.11 ac(2x2)+BT4.0|
Before we modify anything, boot the Chromebook following the manufacturer's instructions. The initial setup for the our Chromebook was a little bumpy.
Enter network information, accept license, wait while it checks for updates and determines the device configuration, ...
Get hung up the screen "Determining device configuration ..." for 15 minutes. Is this a well known installation problem? Go to https://support.google.com/chromebook and search for "determining device configuration". The top hit sends me to a google product forum [link] where it is suggested that I hold the power button until it shuts down and try again. I do this. Turning it back on, I find the power button to be a little fussy. If I hold the power on button for too long then nothing seems to happen. I need to almost just tap the power button.
Turning the Chromebook back on, it flashes a "Determining device configuration" message for a few seconds before proceeding to ask me for Email and Password. I enter these. There is a quick message like "Synching your preferences", it asks me to choose a picture to display for my account on the login screen, and then it's booting into Chromium.
Before continuing, log out, shut down; turn back on, log in. This goes smoothly, and takes only about 10 seconds total. Conclude that the Chromebook is working as expected.
I am following the instructions in Ben Schoon's article [link].
|estimated time:||10 minutes|
First, a note about keys. In his article, Ben Schoon refers to keys like F3 on the keyboard. The Chromebook I am working with has no key labeled F3. Schoon is really talking about the keys on the top row of the keyboard. What he means by F3 is the third key in from the left, starting after the escape key. Here's an annotated photo to show what I mean:
Let's proceed with the installation.
Start from the powered-off state. With the clockwise-arrow button as F3, tap together the buttons "esc + F3 + power button". This brings up a white screen with a big yellow exclamation point in the middle and a message below the exclamation point reading "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card." Don't panic. This is what you are supposed to see! The screen looks like this:
Tap together the buttons "crtl+d". This brings up a new white screen (no yellow exclamation point) with a message "To turn OS verification OFF, press ENTER. You system will reboot and local data will be cleared. To go back, press ESC." The screen looks like this:
Hit the "enter" key. The screen goes dark for a second, then comes back with a white screen with a boxed red exclamation point. Below the exclamation point is the message "OS verification is OFF. Press space to reenable". The screen looks like this:
The computer is about to beep; don't freak out. Just wait; let it beep.
The computer beeps and goes into developer mode. The Screen is still white, with a message "Preparing systems for Developer Mode. This may take a while. Do not turn your computer off until it has restarted." The screen looks like this:
Helpfully, there is a progress bar on the top indicating the percent complete and an ETA in minutes. This looks like:
(It's hard to see the progress bar in this photo).
After 6 or 7 minutes, we are back to the white screen with a boxed red exclamation point and the message "OS verification is OFF. Press space to reenable". The screen looks like this:
Just wait. The system beeps, and reboots.
Now there is a Welcome screen, like there was when I first turned the Chromebook on.
Now it's as if we are starting from scratch. Select a network, enter network password, continue; Google Chrome OS Terms: leave checkbox checked allowing the computer to send crash reports to google, hit Accept and continue; Sign in: enter email, enter password, hit Sign in.
We are again in Chromium, but now Chromium is operating in development mode.
|estimated time:||45 minutes|
Launch the Chrome browser and go to https://github.com/dnschneid/crouton. You should see something like this:
Click on the link following "Chromium OS Universal Chroot Environment" message, the goo.gl link. The browser downloads crouton, and I see a link to it in the lower left hand corner of the browser. The crouton file is small, only 4 kb, so this download takes just a second.
Back in the browser, hit "ctrl + alt + t" to open up a terminal in a new browser tab.
The last line in the terminal is crosh>. Type shell and press "enter". The terminal now reads chronos@localhost / $.
Type sudo sh -e ~/Downloads/crouton -r saucy -t kde. The terminal looks like this (with apologies for the grainy picture):
This command initiates a download and the screen fills with text. My download started at 21:22 and was done about 21:53. The total download time was thus about 30 minutes.
The last line now reads Please specify a name of the primary user:. I enter something. This is followed by Enter new UNIX password. I enter something. I enter the same thing again, to confirm. Note that what I type for the password does not show up on the screen. This is why it asks me to retype it, in case I mistyped it the first time.
Write down the primary user name and password that you just made up; you will need them shortly.
Below a line starting "Here's some tips", there are some messages which I will retype here: (1) something about audio; (2) "Future Chrome OS upgrades may break compatibility with the installed version of CRAS. Should this happen, simply update your chroot."; (3) "You can flip though your running chroot desktops and Chromium OS by hitting Ctrl+Alt=Shirt+Back and Ctrl+Alt+Shift+Forward"; (4) "You can start KDE via the startkde host command: sudo startkde"; and (5) "Unmounting /usr/local/chroots/saucy... Done! You can enter the chroot using enter-chroot." I am glad I am taking notes because the command for flipping desktops differs from what Ben Schoon reports. The screen at this point looks like this:
Now back at the command prompt chronos@localhost / $ I type sudo startkde and hit the "enter" key. After a few seconds, I am now in the kde environment.
Do some test driving. Click on the lower left icon, the Kickoff Application Launcher. In the Search window on the top, type "Terminal", This brings up the Konsole icon below. Click it; this will open up a terminal. In the terminal type gcc --version. This returns gcc (Ubuntu/Linaro 4.8.10ubuntu9) 4.8.1
|estimated time:||5 to 10 minutes|
I can switch successfully cycle between KDE and Chrome by hitting "ctrl+alt+shift+rightarrow" (rightarrow is F2); "Ctrl+Alt+Shift+leftarrow" (leftarrow is F1) works too.
Coming back to Chromium, the terminal tab reads (II) AIGLX: Suspending AIGLX clients for VT switch. If I wait, I get another message file:///usr/share/kde4/apps/plasma/plasmoids/org.kde.notifications/contents/ui/main.gml:139:9 QML Flickable: Possible anchor loop detected on fill. I am not going to worry about these messages, since everything seems to be going OK.
In Chrome, click for a new browser tab and go to https://minecraft.net/download. Scroll down to "Minecraft for Linux / Other" and click on Minecraft.jar (86 kb) to download. The download is essentially instantaneous.
|estimated time:||30 minutes|
Switch back to KDE with "ctrl+alt+shift+rightarrow". Click the Kickoff Application Launcher button in the bottom left of the screen. Once that has opened, type “kons” into the search bar and double click Konsole. This is what this step looks like:
Clicking on Konsole opens up a a terminal application. The terminal looks like this:
If I type ls then I see one directory: Downloads.
If I type pwd to check what directory I am in, then I see home/brickster36. So this is the directory where I will be installing Minecraft I think. I will next type the commands indicated by Ben Schoon to create directories and copy over the Minecraft.jar file I just downloaded. Let me repeat those commands here. My Chromebook keyboard is very sensitive, so I proofread each of the commands carefully before hitting the "enter" key.
Type mkdir ~/games and press the "enter" key. If I type ls I now see two directories: Downloads and games.
Type mkdir ~/games/minecraft and press the "enter" key.
Type mv ~/Downloads/Minecraft.jar ~/games/minecraft. If I type ls games/minecraft then I see the Minecraft.jar. This confirms that I have created the directories correctly and moved the Minecraft file to the right place.
Next I will download java. Type sudo apt-get install openjdk-6-jre. I am asked for the [sudo] password for brickster36:. This is the password that I made up to go with the user name above. I enter this password. A page of stuff prints out, the last two lines of which read "After this operation, 84.9 MB of additional disk space will be used" and "Do you want to continue [Y/n]". Type Y. The download, unpacking, and installation takes less than 5 minutes.
To confirm that java is installed in the terminal I type java -version. The terminal reports (in a 3-line message) "java version 1.6.0_31. OpenJDK Runtime Environment (IcedTea6 1.13.3) (6b31-1.13.3-1ubuntu1~0.13.10.1). OpenJDK 64-bit Server VM (build 23.25-b01, mixed mode)."
Following instructions, when I right click the Kickoff Application Launcher button button in the bottom left corner I do not see an “edit applications” choice. In the terminal type sudo apt-get install kmenuedit. It does not ask me for a password. The install takes just a few seconds. To finish the installation, I log out of kde and then log back in again. Close the terminal by typing exit then "enter". Then Leave, Logout, and, back in the terminal tab in the Chrome browser,``sudo startkde``.
I am back in kde. Now when I right click the Kickoff button, I do get an "edit applications" choice. Choosing edit applications calls up a window. In the left menu, select the Games folder, then click New Item (the second from the left icon). For the item name, type "Minecraft" into the line.
In the left-hand panel, in the Games folder, the file Minecraft is selected. In the right-hand panel, and I see empty fields I can enter information. In the General tab, in the Command field, enter java -jar Minecraft.jar. The "Enable launch feedback" is checked. In the Advanced tab, in the Work path, enter ~/games/minecraft/. Check the "Run in terminal" box. Click the Save icon (the left-most icon), wait a second, then click the upper-right-hand "x" to close the editor window.
Click on the Kickoff button, then Applications (second from left at bottom), double click Games up top. See Minecraft. Right click and choose "Add to desktop". A plain Minecraft appears in the upper left corner of the desktop.
|estimated time:||a few minutes|
Click the Minecraft icon. This opens two terminals, one terminal in the back with a black background and one terminal in the front with a white background. After maybe 10 seconds, a prompt appears in the front terminal asking for Email address or Username and Password. Enter this information.
Hit the Play button in the bottom center of the front terminal. The button says "Downloading ...". After a few minutes, the front terminal disappears, to be replaced by a Minecraft screen with moving and some sound.
Success! The game runs nicely ... "not laggy".
Playing Minecraft on the Chromebook now works like this.
- Turn on the mouse.
- When you open the Chrome book, the Chromebook boots up into the scary screen. Don't be intimidated by the loud beep. Stay cool. Hit "cntl + d" or just wait.
- Log into the Chromebook by entering your email address and password
- One in Chromium, boot the Chrome browser. Hit "ctrl + alt + t" to open up a terminal in a new browser. At the crosh prompt, type shell and press "enter". At the command prompt, type sudo startkde and press "enter"
- Once kde is booted, click on the Minecraft icon, log in, and play.
- In kde, in the upper right hand corner, hover over main, then select Leave (the last choice on the pull-down menu). Choose Logout.
- This will dump you back to Chromium, to the terminal tab in the browser. Wait a few seconds for kde to finish shutting down. When you get the command prompt back, type exit and "enter". At the crosh prompt, type exit and "enter". The terminal tab should close.
- Close the browser.
- In the lower right hand corner, hover over your user icon. Look in the upper right hand corner of the pop-up window. Select "Sign out". This sends you back to the Chromebook login screen.
- In the lower left hand corner, click shut down.
- Turn off the mouse, please.
We are running Chromium + Ubuntu Linux 13.10 on a Samsung 11.6" Chromebook, model 500C12-K01. The main use of the Chromebook is to play Minecraft in Linux. Here are some of our experiences.
TRY 1. 2.5 hours. Epic fail.
On one of the hotwired Chromebooks, sound has stopped working in Ubuntu. Sound is working in Chromium; if we go to YouTube in the Chrome browser and click on something, the video plays with sound.
Do some research, and decide that it might be a good idea to install pulseaudio. In Linux/ubuntu/kde: At the terminal, run sudo apt-get install pulseaudio. At the command line, running pulseaudio gives Stream error -22. Try rm -r ~/.config/pulse. Tried pulseaudio -k and got the reponse E: [pulseaudio] main.c: Failed to kill daemon: No such process.`` Reboot. Still no sound.
Before proceeding, it would be nice to have a volume knob. Try sudo apt-get install pavucontrol. Answer Y. This initiates a rather large download of 38 items. Click on the KDE Kickoff Application Launcher. Now under Applications, I see a new category, MultiMedia, and clicking on that category I see an application Volume Control. Clicking on this opens an application.
Now have a volume knob. On the first tab, Playback, I see a slider called Mono. It is currently pinned left -- "Silence". Slide the slider to the right, stopping at "100 percent (0 dB)". Close the Volume Control window.
How to test the audio? At the terminal, pulseaudio -k to kill the process (if it is still running) followed by cat /dev/urandom | pulseaudio. Doing this I get two errors, the first of which is Daemon already running.. Try again. At the terminal, cat /dev/urandom | pacat. No sound. Have to ctrl+c to stop.
More research. Google "Chromebook ubuntu sound not working". Try first answer in askubuntu.com, "No sound in dual OS" [link]. Follow the advice. First sudo apt-get remove --purge pulseaudio alsa-base. Answer Y when asked if I want to continue. This removing takes just a few seconds. Now, sudo apt-get install alsa-base; answer Y. This install takes just a second. Logout from Ubuntu then sudo startkde to get back in. No sound. Now sudo apt-get install pulseaudio. Logout then back in. Still no sound in Minecraft.
More research. Following on Youtube "Chromebook Ubuntu Fixes: Touchpad, Sound, and Flash!" [link]. At the terminal alsamixer. I do not see all the choices that he does. If I tab through choices, I get two possibilities: Master and CAPTURE. Select Master, then type m. The text above MASTER switches from MM to 00. Select Capture. Typing m does nothing, but there is no MM choice; there is a 3 instead. So type 3 and ... something happens. Find that I can type a number between 1 and 10; the higher the number the more lights I get in the bar chart. Choose 4; see the number 40 and three green boxes above <Capture>. Hit "esc" key to exit. Still no sound in Minecraft.
After some research I discover that I can test the audio in Chromium by running echo -a "\a" in the shell. Running this command produces a faint beep. Running the same command in the shell in Ubuntu produces no sound.
Play with alsamixer, sudo alsamixer at the $ prompt in the shell in both Chromium and Ubuntu ... to no avail.
Problem: When playing Minecraft, the screen freezes and the mouse hangs; ctrl+alt+shift-F2 doesn't do anything. We have observed this freeze happening on our dual OS Chromebook when running audio in Chrome in Chromium while simultaneously running Minecraft in Ubuntu.
Solution: Do a hard reboot by pressing at the same time "refresh + power", that is, "F3 + power".