MeeGo 1.0 currently requires:
Note: Additional hardware configurations will be supported in updates / future revisions.
We have a list of netbooks that are officially supported and that other users have been testing.
We recommend that you fully test MeeGo without disrupting your existing operating system by running it directly off of a thumb as described in the install guide.
Note: You may still find that some wireless cards or other components in your netbook are not be supported in this 1.0 release. Please report any issues in the netbook section of the forum, and we'll try to get them fixed as soon as possible.
You will need to burn the image (you can't just drag and drop it) onto a USB flash drive. We have some technical installation instructions now. Note: Noel is writing some additional user instructions for less technical users.
Please visit the Netbook install troubleshooting section for additional information.
Running MeeGo in a virtual environment is not recommended for most end users. The best way to use MeeGo without disrupting your existing operating system is to run it directly off of a thumb drive.
The netbook UX images are not designed to work on virtual machines, as 3D acceleration support is not available. However, the MeeGo SDK includes a chroot + Xephyr server environment which _can_ be used to run the MeeGo UX in a non-netbook environment (with 3D acceleration):
However, you'll still need to be using a modern Linux distro (like Ubuntu or Fedora) on hardware which supports MeeGo, as listed in "Will MeeGo work on my netbook?" above.
For most people, this should just work; however, certain wireless drivers are not available in open source Linux distributions. You should test that your wireless card is supported before installing MeeGo by running it directly off of a thumb drive.
In many cases, you can package a driver and install it on MeeGo.
If you have a Broadcom wireless driver, Slaine has kindly created an rpm of the Broadcom drivers that you can install on MeeGo.
Go to the Applications panel, click on "Manage Apps" and search or browse for new applications.
Open a terminal and use yum for commonly installed applications. The following example uses Firefox:
You can also go to the website of your favorite application, find the rpm file and install it yourself (instructions for installing and administering rpm files).
In general, if you install the rpm, it should put icons and everything else in the correct places. If not, see the section below about getting icons to appear in the correct menus.
Caveat: Work in process instructions for installing codecs can be found in the forum, but they involve compiling the codecs, and it is not a simple process.
Sure. Instructions for installing Skype can be found in the forum.
We don't have official instructions for this yet, but several people have been able to get this working:
Go to Applications/System Tools, open the Terminal and run the command "gnome-keyboard-properties". You can set layouts here and they will be persistent. More information can be found in a forum thread on this topic.
Right now, you cannot manually change your DNS configuration without resetting it after every reboot. This is a known issue that will be fixed in an update for command line DNS settings. There is also a bug filed requesting that the UI contain DNS settings.
Here is a simple workaround (more details):
If you installed something other than an rpm, you might consider going back up to the previous section about installing applications
If you need to manually add the icon, standard linux desktop rules apply for the application categories. Basically you need to add a desktop file in the right place if it was not added properly during the installation: