A few weeks back I blogged on how to get Ubuntu installed through Crouton on a Chromebook. One of the biggest challenges I faced in setup was getting a USB 3G Modem to work. Below are my notes on how I managed to succeed.
In a few weeks time I’m going to be doing a bit of traveling for work and then a small holiday. As I will be hoping on and off planes and trains, I’m not really keen on taking my primary laptop as it is bulky and not really designed for travel.
After tossing up the pros and cons of tablets, netbooks, and ultrabooks I have bought a Acer C7 Google Chromebook and have managed to get Ubuntu 12.04 running inside a chroot environment. The whole process of getting Ubuntu installed has been much simpler than I was expecting.
For under $300 I now have basically a full lightweight system for travel on which I can watch videos, play music, edit documents, edit photos, and browse the web. While the basic Chrome OS operating system claims all these features, the reality is, it is extremely limited in what it is actually able to do.
For the last year or so I have been struggling with my laptop overheating under Ubuntu. Upon upgrading to the latest beta of Ubuntu 12.10 I have managed to completely solve the heating problem and as a result increased my battery life by more than an hour.
Two different problems have caused the heating problem. The first, a power-regression bug on i7 processors was resolved in Ubuntu 12.04 with an updated kernel.
The second is caused by the Nvidia Optimus Hybrid Graphics card in my laptop not being properly controlled by Ubuntu. Problems with Hybrid Graphics under linux are well documented and there are quite a few different “solutions” available, however, I have been unable to get any to work until now.
A few months back I installed the Bumblebee project, and despite the packages successfully installing, the hybrid graphics card never worked and battery life remained terrible.
Upon upgrading to the latest Ubuntu beta I noticed a problem in the logs during the install of one of the bumblebee packages: bbswitch-dkms
The package would “successfully” install, however, the terminal output would show that the kernel module was never built.
The problem lies in missing kernel header packages. While the Ubuntu Wiki pages do not detail any requirement for the installation of kernel headers other sites do, however, these other sites only focus on the kernel headers for the currently installed kernel. And, if you update the kernel without new headers, it is possible that the kernel module will no longer work and the overheating problem will return.
This is how I setup my system so that I would always have the latest official Ubuntu kernel and headers with bumblebee working:
1. Install the linux-headers-generic package:
sudo apt-get install linux-headers-generic
2. Setup the Bumblebee PPA:
sudo add-apt-repository ppa:bumblebee/stable
3. Update the package information:
sudo apt-get update
4. Install the bbswitch-dkms package:
sudo apt-get install bbswitch-dkms
Before moving on make sure that the output from the above command shows that the module was successfully installed.
5. Install the rest of Bumblebee:
sudo apt-get install bumblebee bumblebee-nvidia
6. Restart and then test if Bumblebee is working:
The second command runs the opengl test using the Optimus graphics card and the output in terminal of the FPS should be much greater than the previous command. Bumblebee should now be successfully installed and you should notice a large decrease in CPU heat and an increase in battery life.
In my opinion during the install of the bbswitch-dkms package a check should be made for the required kernel headers to build the kernel module, if the packages aren’t found a proper error and suggested solution, such as the installation of the headers package should be suggested. A silent fail that keeps the rest of the installation running only provides the end user that false hope that things are working fine.
Over the weekend I upgraded one of my computers to the new beta of Ubuntu. Upon restarting the computer I got dumped into grub-rescue with the message missing-xputs. Part of the cause of this was having Adobe CS3 installed in my dual boot with Windows 7.
When you install Adobe products a little DRM program called FlexNet gets installed into your boot sector which is also where grub resides. When grub is upgraded along with Ubuntu it flicks a warning about the FlexNet being in the sector but then continues to install. However, when you restart grub will not run and will be unable to boot your system into either Ubuntu or Windows.Read more
These instructions will hopefully help those who are testing the Beta over the next few days to get full hardware acceleration from their graphics cards.
These instructions are based off Ubuntu’s guide here: https://help.ubuntu.com/community/RadeonHD and I can only comment on my set up, I cannot guarantee that they will work for anyone else.
Firstly make sure that you graphics card is not already working properly, in a terminal type:
glxinfo | grep “renderer string”
If you see “software rasterizing” as the output then the drivers are NOT working right, if you see something else then they most likely are.
First prepare your system for installing the new drivers, do this by removing the old drivers and making sure you have the right libraries installed:
sudo sh /usr/share/ati/fglrx-uninstall.sh
If the file cannot be found then it is good, just means the driver was never installed in the first place.
sudo apt-get purge xorg-driver-fglrx fglrx-amdcccle fglrx-kernel-source xorg-driver-fglrx-dev
Package not found errors here are also really good.
sudo apt-get --reinstall install libgl1-mesa-glx xserver-xorg-core
Make sure that the reinstall of these two packages completes properly. (Note: the reinstall flag has two – before it not one, some web browsers render the double dash as a single long dash).
Next you need to install a new Kernel, Ubuntu 10.04 will ship with 2.6.32 but at a minimum (at the moment) you need 2.6.33, this is simple to do though:
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/linux-headers-2.6.33-020633-generic_2.6.33-020633_amd64.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/linux-headers-2.6.33-020633_2.6.33-020633_all.deb http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.33/linux-image-2.6.33-020633-generic_2.6.33-020633_amd64.deb
sudo dpkg -i linux*
Now reboot and make sure that you boot into the new kernel and not the old one.
Add the following address to your systems software sources:
Reload the sources list when prompted, then go to update manager, check for new updates, install all the new updates that are listed. Once installed reboot your system.
Now try “glxinfo | grep “renderer string” again and hopefully it will no longer display software raster and instead something a lot more promising.