(→Why can't I get online over wifi?) |
(→Can I install Dropbox?) |
||
| (26 intermediate revisions not shown) | |||
| Line 2: | Line 2: | ||
MeeGo 1.0 currently requires: | MeeGo 1.0 currently requires: | ||
| - | * CPU: | + | * CPU: 32 bit Intel Atom or Intel Core 2 CPU (support for SSSE3) |
** Note: MeeGo will not work on non-SSSE3 CPUs | ** Note: MeeGo will not work on non-SSSE3 CPUs | ||
* A compatible Intel graphics chipset. GMA-500, Nvidia, and ATI chipsets are not supported. See [[User:Vgrade]] for GMA500 instructions. | * A compatible Intel graphics chipset. GMA-500, Nvidia, and ATI chipsets are not supported. See [[User:Vgrade]] for GMA500 instructions. | ||
| Line 30: | Line 30: | ||
== How do I perform updates to receive bug fixes? == | == How do I perform updates to receive bug fixes? == | ||
| - | Updates are automatically pushed to users periodically. When updates are available for MeeGo, you should receive notifications that you have an 'Important update available'. The [[MeeGo 1.0 Netbook Updates]] page has more details, instructions and known upgrade issues. | + | Updates are automatically pushed to users periodically. When updates are available for MeeGo, you should receive notifications that you have an 'Important update available'. The [[MeeGo 1.0 Netbook Updates]] page has more details, instructions, and known upgrade issues. |
| + | |||
| + | == How do I upgrade from 1.0 to 1.1? == | ||
| + | |||
| + | We recommend that you back up your data and do a clean install of 1.1, rather than an upgrade. If you would like to upgrade anyway, instead of doing a clean install, you can read our documentation on [[Upgrading MeeGo Versions]] (pay particular attention to the caveats). | ||
== Does MeeGo run in virtual environments? == | == Does MeeGo run in virtual environments? == | ||
| Line 36: | Line 40: | ||
'''For users''': | '''For users''': | ||
| - | 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 [http://meego.com/devices/netbook/installing-meego-your-netbook run it directly off of a thumb drive]. | + | 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 [http://meego.com/devices/netbook/installing-meego-your-netbook run it directly off of a thumb drive]. |
'''For developers''': | '''For developers''': | ||
| - | The netbook UX images | + | The netbook UX images may work on virtual machines with 3D acceleration support in certain environments. There is also a chroot + Xephyr server environment available for Linux, which _can_ be used to run the MeeGo UX in a non-netbook environment |
| - | (with 3D acceleration) | + | (with 3D acceleration). |
| - | [[ | + | See the [[Developer Guide]] for more details. |
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. | 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. | ||
| Line 57: | Line 61: | ||
In many cases, you can package a driver and install it on MeeGo. | In many cases, you can package a driver and install it on MeeGo. | ||
| - | If you have a Broadcom wireless driver, Slaine has kindly created [http://slaine.org/_slaine/Meego_1. | + | If you have a Broadcom wireless driver, Slaine has kindly created [http://slaine.org/_slaine/Meego_1.2_Wifi.html an rpm of the Broadcom drivers] that you can install on MeeGo. |
| + | |||
| + | If you're having problems with the build instructions above, I suggest you check out the following thread: http://forum.meego.com/showthread.php?p=7905#post7905 | ||
| + | |||
| + | '''For EAP Networks''' | ||
| + | |||
| + | EAP networks require a conmmand configuration file. You will need to create a text file in the /var/lib/connman/ directory. File syntax and examples are available at [http://git.kernel.org/?p=network/connman/connman.git;a=blob;f=doc/config-format.txt;h=bc5a5c189847cb4f91c81254fdd8c7215c24feaa;hb=HEAD git.kernel.org] | ||
| + | Restart MeeGo to load the configuration file. | ||
== How do I install applications == | == How do I install applications == | ||
| Line 63: | Line 74: | ||
'''For Users''' | '''For Users''' | ||
| - | Go to the Applications panel, click on "Manage Apps" and search or browse for new applications. | + | Go to the Applications panel, click on "Manage Apps", and search or browse for new applications. |
'''For Developers''' | '''For Developers''' | ||
| Line 70: | Line 81: | ||
* 'sudo yum search (INSERT APP Name)' like 'sudo yum search firefox' | * 'sudo yum search (INSERT APP Name)' like 'sudo yum search firefox' | ||
* 'sudo yum install (INSERT THE FULL NAME OF PACKAGE HERE)' like 'sudo yum install firefox.i586' | * 'sudo yum install (INSERT THE FULL NAME OF PACKAGE HERE)' like 'sudo yum install firefox.i586' | ||
| + | |||
| + | In MeeGo 1.2 yum was replaced by zypper, so use these examples instead: | ||
| + | |||
| + | * 'sudo zypper search (INSERT APP Name)' like 'sudo zypper search chromium' | ||
| + | * 'sudo zypper install (INSERT THE FULL NAME OF PACKAGE HERE)' like 'sudo zypper install chromium.i586' | ||
You can also go to the website of your favorite application, find the rpm file and install it yourself ([http://www.tuxfiles.org/linuxhelp/rpminstall.html instructions for installing and administering rpm files]). | You can also go to the website of your favorite application, find the rpm file and install it yourself ([http://www.tuxfiles.org/linuxhelp/rpminstall.html instructions for installing and administering rpm files]). | ||
| Line 84: | Line 100: | ||
Sure. [http://forum.meego.com/showthread.php?t=355 Instructions for installing Skype] can be found in the forum. | Sure. [http://forum.meego.com/showthread.php?t=355 Instructions for installing Skype] can be found in the forum. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Can I run MeeGo in a dual / triple boot environment? == | == Can I run MeeGo in a dual / triple boot environment? == | ||
| Line 121: | Line 129: | ||
'''For developers''' | '''For developers''' | ||
| - | 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: | + | 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: |
* [http://standards.freedesktop.org/menu-spec/latest/ Menu spec defines the categories]. | * [http://standards.freedesktop.org/menu-spec/latest/ Menu spec defines the categories]. | ||
* [http://standards.freedesktop.org/desktop-entry-spec/latest/ Desktop entry spec defines what the desktop file looks like otherwise] | * [http://standards.freedesktop.org/desktop-entry-spec/latest/ Desktop entry spec defines what the desktop file looks like otherwise] | ||
| Line 127: | Line 135: | ||
== I've found a bug - How do I report it? == | == I've found a bug - How do I report it? == | ||
| - | We have [[ | + | We have [[Quality/How To Report Bugs|detailed instructions for how to file a bug report]]. |
== Why doesn't MeeGo run on my hardware? == | == Why doesn't MeeGo run on my hardware? == | ||
| - | The simple answer is that doesn't run on your hardware '''yet'''. Right now, MeeGo runs on a limited number of hardware configurations (see above sections for details). This is a common approach for open source software. The person or people who write the first version of the software selects a subset of hardware to get the project started. For example, the [http://www.linux.org/people/linus_post.html first version of the Linux kernel] available to the public | + | The simple answer is that it doesn't run on your hardware '''yet'''. Right now, MeeGo runs on a limited number of hardware configurations (see above sections for details). This is a common approach for open source software. The person or people who write the first version of the software selects a subset of hardware to get the project started. For example, the [http://www.linux.org/people/linus_post.html first version of the Linux kernel] available to the public ran only on a 386 with AT drives, because that was what Linus Torvalds had at the time. If the open source project is successful (as Linux has been) more and more people will begin contributing ports of the software to additional hardware platforms. Linux now supports many different hardware configurations because people were willing to put in the time to add them. |
The best way to get support for your hardware is to either write it yourself and submit patches to MeeGo or convince someone else to support your hardware (maybe your hardware vendor). You can also [http://bugs.meego.com/ file it as a feature request] and hope that someone decides to work on it. | The best way to get support for your hardware is to either write it yourself and submit patches to MeeGo or convince someone else to support your hardware (maybe your hardware vendor). You can also [http://bugs.meego.com/ file it as a feature request] and hope that someone decides to work on it. | ||
MeeGo will eventually support a broader set of hardware, but it will take time and contributions from the community to make it happen. | MeeGo will eventually support a broader set of hardware, but it will take time and contributions from the community to make it happen. | ||
MeeGo 1.0 currently requires:
Note: Additional hardware configurations will be supported in updates / future revisions. See below for an explanation of why MeeGo doesn't run on your hardware.
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.
For users
We have some instructions for Windows users that contain detailed instructions for putting the MeeGo image onto a USB drive and installing it on your netbook. Keep in mind that you will need to carefully follow these instructions to burn the image (you can't just drag and drop it) onto a USB drive.
For developers
We have pages with installation instructions for Mac / Linux and complete instructions for building images.
Troubleshooting
Please visit the Netbook install troubleshooting section for additional information.
Updates are automatically pushed to users periodically. When updates are available for MeeGo, you should receive notifications that you have an 'Important update available'. The MeeGo 1.0 Netbook Updates page has more details, instructions, and known upgrade issues.
We recommend that you back up your data and do a clean install of 1.1, rather than an upgrade. If you would like to upgrade anyway, instead of doing a clean install, you can read our documentation on Upgrading MeeGo Versions (pay particular attention to the caveats).
For users:
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.
For developers:
The netbook UX images may work on virtual machines with 3D acceleration support in certain environments. There is also a chroot + Xephyr server environment available for Linux, which _can_ be used to run the MeeGo UX in a non-netbook environment (with 3D acceleration).
See the Developer Guide for more details.
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 users
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.
For developers
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.
If you're having problems with the build instructions above, I suggest you check out the following thread: http://forum.meego.com/showthread.php?p=7905#post7905
For EAP Networks
EAP networks require a conmmand configuration file. You will need to create a text file in the /var/lib/connman/ directory. File syntax and examples are available at git.kernel.org Restart MeeGo to load the configuration file.
For Users
Go to the Applications panel, click on "Manage Apps", and search or browse for new applications.
For Developers
Open a terminal and use yum for commonly installed applications. The following example uses Firefox:
In MeeGo 1.2 yum was replaced by zypper, so use these examples instead:
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.
For Developers
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):
or, as another nasty hack, create a good /etc/resolv.conf and then run chattr +i /etc/resolve.conf. This means that the file will be immutable and not changed by any process. chattr -i /etc/resolv.conf undoes this.
For users
If you installed something other than an rpm, you might consider going back up to the previous section about installing applications
For developers
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:
We have detailed instructions for how to file a bug report.
The simple answer is that it doesn't run on your hardware yet. Right now, MeeGo runs on a limited number of hardware configurations (see above sections for details). This is a common approach for open source software. The person or people who write the first version of the software selects a subset of hardware to get the project started. For example, the first version of the Linux kernel available to the public ran only on a 386 with AT drives, because that was what Linus Torvalds had at the time. If the open source project is successful (as Linux has been) more and more people will begin contributing ports of the software to additional hardware platforms. Linux now supports many different hardware configurations because people were willing to put in the time to add them.
The best way to get support for your hardware is to either write it yourself and submit patches to MeeGo or convince someone else to support your hardware (maybe your hardware vendor). You can also file it as a feature request and hope that someone decides to work on it.
MeeGo will eventually support a broader set of hardware, but it will take time and contributions from the community to make it happen.