MeeGo wiki - User contributions [en]

Devices

2011-09-25T23:44:39Z

Alison: /* Tablets/Slates */ Correcting ExoPC link.

Below, you find devices where MeeGo was used successfully. The list is not complete and waits for your input.

For info: [[wikipedia:List_of_Intel_Atom_microprocessors|Wikipedia Atom list]]

==Devices compatible with MeeGo==
''sorted alphabetically''

=== Released devices ===
Meego devices, which are released and you can actually buy.
*September 2011: [http://forum.meego.com/showthread.php?t=4382 Acer Aspire 5749] Intel Core i3 2310M (Sandy Bridge) laptop
*August 2011: [http://forum.meego.com/showthread.php?t=4285 Acer Aspire One D257] with the dual-core Atom N570, the best netbook on the market
*August 2011: [http://newsroom.intel.com/community/intel_newsroom/blog/2011/05/31/chip-shot-meego-netbooks-based-on-intel-atom-arrive-at-computex Atom N435 netbooks]
** Acer Aspire One Happy 2: TBA
** [http://www.asus.com/Eee/Eee_PC/Eee_PC_X101/ Asus Eee PC X101] Atom N435 or N455
** [http://www.tcmagazine.com/tcm/news/hardware/40280/meego-powered-lenovo-ideapad-s100-gets-listed-europe Lenovo IdeaPad S100]
** [http://forum.meego.com/showthread.php?t=3922 Samsung N100]
*[http://www.evolvethree.com.au/ Evolve III Maestro] Atom Z670 Oak Trail tablet
* [http://www.linuxfordevices.com/c/a/News/WePad-and-NFS-NPad/ WeTab], 11.6-inch, Atom N450 tablet; [http://wetab.mobi/developers/ SDK] available; [http://www.wetab-community.com/ Forum]
** [[ Installing MeeGo Tablet Developer Preview on WeTab Tablet ]]
** [[ Installing MeeGo 1.1 Pinetrail Image on WeTab Tablet ]]
** See also [ http://edc.intel.com/Software/Installation-Guides/Meego/ Intel's instructions. ] They look out of date (note screenshot of 1.0).
** Review in Nixu open -blog: [https://www.nixuopen.org/blog/2010/10/meego-unboxing/ Part1] [https://www.nixuopen.org/blog/2010/11/meego-unboxing-part-2/ Part2]
* [http://www.solidblogger.com/fujitsu-lifebook-mh330-netbook-specifications/ Fujitsu LifeBook MH330] Atom N450 netbook
* [http://www.linuxfordevices.com/c/a/News/Trinity-Audio-Group-Indamixx-2-ships/ Trinity Audio's Indamixx 2], Atom N450 audio tablet for musicians.
* Amino and [http://www.aminocom.com/what-we-offer/amino-and-meego/ MeeGo TV]
**[http://www.aminocom.com/what-we-offer/hybridott/ Amino Freedom STB]

===Handsets===
General information user and developers for [[Handsets]].
* September 2011: [http://www.meegoexperts.com/2011/06/nokia-n9-announced-nokia-connections-nokiacnxn/ Nokia N9]
*[[Devices/Aava|Aava]] ([[Developing_With_The_Aava|Tips for developing with the Aava]])
*[[Devices/N900|Nokia N900]] (see install instructions at: [[ARM]])

[[Devices/Unlisted_Handsets|Unlisted Handsets]]

===Tablets/Slates===
* Q3 2011: Atom Oak Trail tablets: [http://newsroom.intel.com/docs/DOC-1976 Atom Z670 (1.5GHz) and Z650 (1.2GHz), GMA 600]
** August 2011: The [http://tablets-planet.com/2011/04/13/first-intel-atom-z670-based-windows-tablet-pc-lands-at-fcc/ ECS ElitePad S10] is MeeGo's reference Oak Trail platform. Other tablets are not supported atm.
*[http://exocommunity.com/forum/viewforum.php?f=110 ExoPC Slate] Atom N450, Broadcom Crystal HD
** [http://appdeveloper.intel.com/en-us/blog/2011/07/14/update-your-exopc-part-1 Update your ExoPC]
** [[MeeGo_IVI_on_ExoPC|Installing MeeGo on ExoPC]]
*[http://forum.meego.com/showthread.php?t=3148 Viewsonic Viewpad 10] Atom N455
*[http://www.jogglerwiki.com/wiki/MeeGo Joggler] Atom Z520, GMA500
** See [http://www.youtube.com/watch?v=vnwfVtHuhoI Joggler running Meego 1.0 Netbook UX]
** See [http://www.youtube.com/watch?v=JVL8I1B6uPs Joggler running Meego 1.0.1 IVI UX]
*[http://www.openaos.org/ Archos]
**[http://forum.meego.com/showthread.php?t=1133 Archos 9] Atom Z515, GMA500
* [http://lii-enac.fr/en/architecture/linux-input/multitouch-devices.html Linux touchscreen support]

===Netbooks===
* If you have a netbook that you have confirmed works with MeeGo, please add it below.

*[[wikipedia:Acer Aspire One|Acer Aspire]]
** One AO532-h; [http://forum.meego.com/showthread.php?t=436 memory card reader]
** One A110L
** One A150L and A150X
** One D250
** One ZG5

*[[wikipedia:Asus Eee PC|Asus EeePC]]
** 701 (root partition formatted with ext3)
** 900 (root partition formatted with ext3)
** 900A (wireless works only with MeeGo 1.0.90+)
** 900HA
** 901
** 901 Go (3G not supported yet)
** s101
** 1000
** 1000H
** 1002H (not yet tested for wireless etc)
** 1005HA
** 1005PE (Atom N450)
** 1008HA ([http://forum.meego.com/showthread.php?p=1330#post1330 well tested])
* Dell
** Latitude 2100 (including optional touchscreen)
** Inspiron Mini 9 ([http://forum.meego.com/showthread.php?t=287 some issues])
** Vostro A90 (same issues as Mini 9)
*[[wikipedia:eMachines_Netbook|eMachines]]
** eM350 (Atom N450 )
*Fujitsu
** M2010
* Gigabyte
** Q1000C (see [[Devices#Known_problems|Known problems]] below; Realtek 8172 wifi does not work)
* HERCULES
** EC-900 (wireless works only with MeeGo 1.0.90+)
* HP
** [http://forum.meego.com/showthread.php?t=4073 Mini 110]
** Mini 210 1022eo,1030-NR,1024LA, others ([http://forum.meego.com/showthread.php?t=328 Broadcom WiFi needs to be compiled separately])
** Mini 5101 HD ([http://forum.meego.com/showthread.php?t=328 Broadcom WiFi needs to be compiled separately])
* Lenovo
** [[Devices/Ideapad|S10-3t IdeaPad]]
* Medion
** Akoya Mini E1210
** Akoya Mini E1222 ([http://wiki.meego.com/Installation_of_MeeGo_on_notebook#Wireless_Drivers Realtek WiFi needs to be compiled separately])
*[[wikipedia:MSI_Wind_Netbook|MSI Wind]]
** U90/U90x
** U100
** U130
** L1350
* Nokia
** [http://www.meegoexperts.com/2011/06/nokia-booklet-3g-running-meego/ Booklet 3G] (Atom Z530)
* Packard Bell
** dot S2
* Samsung
** N130
** N140
** Q328 i3 (Duel chips Nvidia Optimus/Intel)
** N150 (except for some hotkeys (2010-11-20))
** [[wikipedia:Samsung NC10|NC10]]
** N210 Plus (except for some hotkeys. Broadcom WiFi needs to be compiled separately)
* [[wikipedia:VAIO|Sony VAIO]]
** VPCW211AX (Atom N450)
** VGN-TX3XP (Intel Core Solo 1.2GHz, Intel 945GMS video card)
** VGN-TX5MN (Intel Core Solo U1400 / 1.2 GHz, Intel GMA 950 video card, 1GB RAM)
* Toshiba Mini
** NB100
** NB200
** NB205
** NB305
** NB505 ([http://www.meabi.com/meego-wirelesswifi-configuration/ Realtek WiFi needs to be compiled separately])

===Nettops===
*Acer
**[[wikipedia:Acer Aspire Revo|Revo]] GN40
**eMachine EZ1601 and KAV60
*Asus
**[[wikipedia:ASUS Eee Box|Eeebox]] B202
**[[wikipedia:ASUS Eee Box|Eeebox]] EB1007 (It has no KVM support to develep MeeGo through QEMU)
**[[wikipedia:ASUS Eee Top|Eeetop]] ET1602
*[[wikipedia:Micro-Star International|MSI]]
**AE1900
*Samsung
**[[wikipedia:Samsung N130|n130]]

*Intel Desktop Board
**D410PT
**D510MO
**D945GCLF2 (Should work on near-identical D945GCLF as well)

===Notebooks===
* Acer Travelmate 6292
* Asus F2F (Celeron M)
* Asus U1F (Core Duo)
* Dell Inspiron 1525 (without wireless networking) [http://forum.meego.com/showthread.php?t=371]
* Dell Latitude D630 (Broadcom [http://slaine.org/_slaine/Meego_1.0_Wifi.html] wifi driver might be needed)
* Dell Latitude E6400 (Broadcom [http://slaine.org/_slaine/Meego_1.0_Wifi.html] wifi driver might be needed)
* Dell XPS M1210 CoreDuo T2400, Intel 950GM, Intel Wireless 3945abg, Linksys Webcam. [http://forum.meego.com/showthread.php?t=433]
* Fujitsu Lifebook P1610: Working: wifi, sound, screen brightness/sound volume via function keys, SD card reader, trackpoint. Not Working: touchscreenn [--[[User:Rokky|Rokky]] 22:17, 2 June 2010 (UTC)]
* Lenovo IdeaPad Y450 [http://forum.meego.com/showthread.php?t=265]
* Lenovo T60 / T61 [http://forum.meego.com/showthread.php?t=323]
* Lenovo ThinkPad R500 [http://forum.meego.com/showthread.php?t=371]
* Panasonic CF-52 (Centrino2)
* Toshiba L500 Satellite low-end Notebook (needs rtl8192se driver from RealTek for wireless)
* Toshiba Satellite U305 S5077
* Wipro WNB7PBC4830R (needs wireless driver code compilation)

===Developer Boards===
* July 2011: ST-Ericsson's dual-core [[ARM/Snowball]]
* October 2010: [[wikipedia:PandaBoard|Panda Board]], see [[ARM/OMAP4_Panda]]
*[[wikipedia:Beagle Board|Beagle Board]], see [[ARM/Meego on the Beagle]]

==Known problems==
*Netbooks requiring GMA500 drivers: [http://www.meegoexperts.com/2011/06/nokia-booklet-3g-running-meego/ Booklet 3G], as an exemple
** Try this Poulsbo/GMA500 Netbook Kickstart [[User:vgrade]]
** July 2011 [http://www.phoronix.com/scan.php?page=news_item&px=OTY2Mg GMA500 driver improvements]
*'MeeGo will not work on non-SSSE3 CPUs'
** Community page to try and rectify this [[Devices/nonSSSE3|nonSSSE3]]
*'USB booting issues due to ISOLinux/EFI BIOS bug' [http://bugs.meego.com/show_bug.cgi?id=11181|Bug 11181 - Failed to boot from USB on Positivo Mobo Black] (Affects HP Mini, Positive Mobo Black, Gigabyte Q1000C amongst others)
*Backlight brightnes changes randomly on some Asus eeePc's when trying to adjust it:
** Open /boot/extlinux/extlinux.conf and add "acpi_osi=Linux" to the line "append" in the entry labelled "meego" (eventually you might have to add "acpi_backlight=vendor" as well)

[[Category:Hardware]]

In-vehicle/IVI for users and developers

2011-09-25T23:42:23Z

Alison: /* Developers */ New ExoPC page.

== Users ==

List of MeeGo compatible [[Devices]]

=== Installation ===

*Instructions for [[ARM|N900 / ARM based devices]]
*Instructions for [[IVI-LenovoS10-3t|Lenovo S10-3t]]
*Instructions for [[MeeGo_IVI_on_ExoPC|ExoPC]]

=== Advanced Topics ===

==== Car PC Hobbyist Challenge ====

#Hardware support
#* Intel ITX motherboards: Most widely spread in the existing community
#Installation
#* Power - How much? How to switch it on?
#* Placement - Where are the components located?, Heating/Cooling
#Interfacing with system
#* startup solutions
#* Volume control
#* Touchscreen navigating/button placement
#Capabilities/Functions
#* Large Music libraries
#* Navigation
#* phone syncing

== Developers ==

[[Developer Guide]]

*Instructions for [[ARM|N900 / ARM based devices]]
*Instructions for [[IVI-LenovoS10-3t|Lenovo S10-3t]]
*Instructions for [[MeeGo_IVI_on_ExoPC|ExoPC]]

{{Developer pages}}

== Resource ==
*[http://www.mp3car.com/vbulletin/meego-vehicle/ MP3Car Forum MeeGo section]

[[Category:IVI]]

In-vehicle/IVI for users and developers

2011-09-25T23:40:24Z

Alison: /* Installation */ Adding ExoPC link.

== Users ==

List of MeeGo compatible [[Devices]]

=== Installation ===

*Instructions for [[ARM|N900 / ARM based devices]]
*Instructions for [[IVI-LenovoS10-3t|Lenovo S10-3t]]
*Instructions for [[MeeGo_IVI_on_ExoPC|ExoPC]]

=== Advanced Topics ===

==== Car PC Hobbyist Challenge ====

#Hardware support
#* Intel ITX motherboards: Most widely spread in the existing community
#Installation
#* Power - How much? How to switch it on?
#* Placement - Where are the components located?, Heating/Cooling
#Interfacing with system
#* startup solutions
#* Volume control
#* Touchscreen navigating/button placement
#Capabilities/Functions
#* Large Music libraries
#* Navigation
#* phone syncing

== Developers ==

[[Developer Guide]]

*Instructions for [[ARM|N900 / ARM based devices]]
*Instructions for [[IVI-LenovoS10-3t|Lenovo S10-3t]]

{{Developer pages}}

== Resource ==
*[http://www.mp3car.com/vbulletin/meego-vehicle/ MP3Car Forum MeeGo section]

[[Category:IVI]]

Installing MeeGo Images on WeTab Tablet

2011-09-21T15:21:33Z

Alison: /* Modifying the WeTab's bootloader */ A few missing details.

'''Warning:''' the Pinetrail image running on the WeTab has some problems as
of 1/6/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader or kernel, you may '''brick''' your system.

== What is needed ==

1. A WeTab with power cable
2. sudo/root access on the WeTab
3. Two USB flash drives, one with a mountable filesystem already on it
4. A USB keyboard and mouse
5. Another Linux system for writing to the USB drives

== Creating a bootable MeeGo drive ==

1. Plug the WeTab into the mains. You do not want the unit powering
off or sleeping while you are reflashing!

2. Download pinetrail image from the [ http://repo.meego.com/MeeGo/builds/ repo ]. I used
meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img:

''
wget http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/handset/images/meego-handset-ia32-pinetrail-mtf/meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img''

3. Follow [ http://meego.com/devices/netbook/installing-meego-your-netbook instructions ]
for using image-writer to create a bootable image on one of the USB drives (Drive 1 hereafter).

== Modifying the WeTab's bootloader ==

References: [ http://digitalorchard.blogspot.com/2010/12/wetabos-to-pure-meego.html 1]
[ http://wetabz.blogspot.com/2010/10/using-plop-boot-manager.html 2 ]

4. Now that you have a bootable image on Drive 1, you need to modify the WeTab's
bootloader to boot from USB. First download the latest version of plpbt.
I used plpbt-5.0.11:

''
wget http://download.plop.at/files/bootmngr/plpbt-5.0.13.zip''

5. Unzip the archive and copy the resulting files plpbt.bin and plpbt.img to the second
FLASH drive (hereafter called Drive 2).

6. Plug Drive 2 into the WeTab. From the WeTab's application
launcher screen, choose the terminal window icon. Then:

''
cd /boot/extlinux
sudo cp /media/<your drive name>/plpbt.bin .
sudo cp -p extlinux.conf extlinux.conf_dist
cp extlinux.conf_dist /media/<your drive name>
umount /media/<your drive name>''

7. Remove Drive 2 and plug it into the second Linux system. Then

''
cp /media/<your drive name>/extlinux.conf /tmp
<text editor of your choice> /tmp/extlinux.conf''

At the top of the file, change the lines that set "prompt" and "timeout":

''
prompt 1
timeout 15''

Remove "quiet" where is appears on "append" lines and comment out "menu hidden". Insert the following text at the top of the list of bootable images:

''
label plp
linux plpbt.bin''

Note that the exact syntax may change (the names of files may change, for example) as plpbt releases new versions. Check that the file permissions of the new extlinux.conf match those of extlinux.conf_dist. Save the extlinux.conf file and

''
sudo cp /tmp/extlinux.conf /media/<your drive name>
eject /media/<your drive name>''

8. Plug Drive 2 into the WeTab, and from its shell prompt type

''
sudo cp -p /media/<your drive name>/extlinux.conf /boot/extlinux
umount /media/<your drive name>''

Remove Drive 2. You are finished with it.

== Install MeeGo onto the WeTab ==

''Note:'' The following procedure did not work well with a USB hub, probably because plpbt comes with an old version of the EHCI drivers. For best results, insert USB drives into the WeTab's top connector and plug the keyboard directly into the bottom one. Keyboard functionality in plpbt is hit-or-miss, but the soft button always works.

9. Plug Drive 1 with the Pinetrail image into the USB drive.

10. Power the WeTab off. Power on, and while the blue LED is
flashing, cover the soft button (circular sensor in upper left-hand corner
of the surface to the left of the blue LED).

11. The plop bootloader with its green 1970s-era font will display.
Tap the soft button to advance downward. Hold the soft button to
select "USB."

12. The system should now come up in the MeeGo installer. Plug in
the USB keyboard.

13. Choose "installation" or "live-boot" as suits you. Use the USB
keyboard (or soft button) to make selections, as the touchscreen is not working!
Sometimes it's possible to advance screens with carriage-return; at
other places Alt-F will move Forward. Follow the installation instructions.

If the USB keyboard does not work, you can still use the soft button, just as
in the plop bootloader. Tap it to highlight the next item. Hold it down to boot.
'''Be careful though: unlike in the plop bootmenu, once you select the bottom-most item, you cannot go back up!'''

14. If you have installed MeeGo, you'll reach a screen which tells you
to remove the flash drive and reboot. After removing the flash
drive, plug in the USB mouse. At this point I got an X11 error indicating that the screen settings weren't detected; just ignore it, as the problem is temporary. Once MeeGo (or WeTab OS) comes up, devices plugged into a USB hub will function once more.

15. Reboot the system. You should now see the MeeGo UX launcher.
Congratulations, you have installed MeeGo!

== Problems ==

1. The touchscreen is unresponsive. (Presumably this is a driver problem. See also [http://bugs.meego.com/show_bug.cgi?id=9524 bug 9524] )

2. The UX launcher image does not utilize the whole display, which is
unsurprising since Pinetrail is a handset image. (Presumably this
problem is fixable with xrandr.)

3. The build comes with the ath3k driver rather than the [http://wetabz.blogspot.com/2010/10/multitouch-driver-on-wetab.html ath9k one] that the modem requires.

== Related Links ==
* [http://wetab-community.de/forum/viewtopic.php?f=62&t=2502 Discussion in the WeTab Community Forum]
* [http://forum.meego.com/showthread.php?t=2320 Discussion in the official Meego Forum]

Installing MeeGo Handset image on WeTab Tablet

2011-09-21T15:09:35Z

Alison: moved Installing MeeGo Handset image on WeTab Tablet to Installing MeeGo Images on WeTab Tablet: There are now several MeeGo images that run on the Pinetrail/Pineview processor, so their is no reason to restrict the title any more.

#REDIRECT [[Installing MeeGo Images on WeTab Tablet]]

Installing MeeGo Images on WeTab Tablet

2011-09-21T15:09:35Z

'''Warning:''' the Pinetrail image running on the WeTab has some problems as
of 1/6/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader or kernel, you may '''brick''' your system.

== What is needed ==

1. A WeTab with power cable
2. sudo/root access on the WeTab
3. Two USB flash drives, one with a mountable filesystem already on it
4. A USB keyboard and mouse
5. Another Linux system for writing to the USB drives

== Creating a bootable MeeGo drive ==

1. Plug the WeTab into the mains. You do not want the unit powering
off or sleeping while you are reflashing!

2. Download pinetrail image from the [ http://repo.meego.com/MeeGo/builds/ repo ]. I used
meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img:

''
wget http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/handset/images/meego-handset-ia32-pinetrail-mtf/meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img''

3. Follow [ http://meego.com/devices/netbook/installing-meego-your-netbook instructions ]
for using image-writer to create a bootable image on one of the USB drives (Drive 1 hereafter).

== Modifying the WeTab's bootloader ==

References: [ http://digitalorchard.blogspot.com/2010/12/wetabos-to-pure-meego.html 1]
[ http://wetabz.blogspot.com/2010/10/using-plop-boot-manager.html 2 ]

4. Now that you have a bootable image on Drive 1, you need to modify the WeTab's
bootloader to boot from USB. First download the latest version of plpbt.
I used plpbt-5.0.11:

''
wget http://download.plop.at/files/bootmngr/plpbt-5.0.13.zip''

5. Unzip the archive and copy the resulting files plpbt.bin and plpbt.img to the second
FLASH drive (hereafter called Drive 2).

6. Plug Drive 2 into the WeTab. From the WeTab's application
launcher screen, choose the terminal window icon. Then:

''
cd /boot/extlinux
sudo cp /media/<your drive name>/plpbt.bin .
sudo cp -p extlinux.conf extlinux.conf_dist
cp extlinux.conf_dist /media/<your drive name>
umount /media/<your drive name>''

7. Remove Drive 2 and plug it into the second Linux system. Then

''
cp /media/<your drive name>/extlinux.conf /tmp
<text editor of your choice> /tmp/extlinux.conf''

Insert the following text at the top of the list of bootable images:

''
label plp
linux plpbt.bin''

Note that the exact syntax may change (the names of files may change, for example) as plpbt releases new versions. Check that the file permissions of the new extlinux.conf match those of extlinux.conf_dist. Save the extlinux.conf file and

''
sudo cp /tmp/extlinux.conf /media/<your drive name>
eject /media/<your drive name>''

8. Plug Drive 2 into the WeTab, and from its shell prompt type

''
sudo cp -p /media/<your drive name>/extlinux.conf /boot/extlinux
umount /media/<your drive name>''

Remove Drive 2. You are finished with it.

== Install MeeGo onto the WeTab ==

''Note:'' The following procedure did not work well with a USB hub, probably because plpbt comes with an old version of the EHCI drivers. For best results, insert USB drives into the WeTab's top connector and plug the keyboard directly into the bottom one. Keyboard functionality in plpbt is hit-or-miss, but the soft button always works.

9. Plug Drive 1 with the Pinetrail image into the USB drive.

10. Power the WeTab off. Power on, and while the blue LED is
flashing, cover the soft button (circular sensor in upper left-hand corner
of the surface to the left of the blue LED).

11. The plop bootloader with its green 1970s-era font will display.
Tap the soft button to advance downward. Hold the soft button to
select "USB."

12. The system should now come up in the MeeGo installer. Plug in
the USB keyboard.

13. Choose "installation" or "live-boot" as suits you. Use the USB
keyboard (or soft button) to make selections, as the touchscreen is not working!
Sometimes it's possible to advance screens with carriage-return; at
other places Alt-F will move Forward. Follow the installation instructions.

If the USB keyboard does not work, you can still use the soft button, just as
in the plop bootloader. Tap it to highlight the next item. Hold it down to boot.
'''Be careful though: unlike in the plop bootmenu, once you select the bottom-most item, you cannot go back up!'''

14. If you have installed MeeGo, you'll reach a screen which tells you
to remove the flash drive and reboot. After removing the flash
drive, plug in the USB mouse. At this point I got an X11 error indicating that the screen settings weren't detected; just ignore it, as the problem is temporary. Once MeeGo (or WeTab OS) comes up, devices plugged into a USB hub will function once more.

15. Reboot the system. You should now see the MeeGo UX launcher.
Congratulations, you have installed MeeGo!

== Problems ==

1. The touchscreen is unresponsive. (Presumably this is a driver problem. See also [http://bugs.meego.com/show_bug.cgi?id=9524 bug 9524] )

2. The UX launcher image does not utilize the whole display, which is
unsurprising since Pinetrail is a handset image. (Presumably this
problem is fixable with xrandr.)

3. The build comes with the ath3k driver rather than the [http://wetabz.blogspot.com/2010/10/multitouch-driver-on-wetab.html ath9k one] that the modem requires.

== Related Links ==
* [http://wetab-community.de/forum/viewtopic.php?f=62&t=2502 Discussion in the WeTab Community Forum]
* [http://forum.meego.com/showthread.php?t=2320 Discussion in the official Meego Forum]

Installing MeeGo Images on WeTab Tablet

2011-09-21T15:07:59Z

Alison: /* Install MeeGo onto the WeTab */ Clarification.

'''Warning:''' the Pinetrail image running on the WeTab has some problems as
of 1/6/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader or kernel, you may '''brick''' your system.

== What is needed ==

1. A WeTab with power cable
2. sudo/root access on the WeTab
3. Two USB flash drives, one with a mountable filesystem already on it
4. A USB keyboard and mouse
5. Another Linux system for writing to the USB drives

== Creating a bootable MeeGo drive ==

1. Plug the WeTab into the mains. You do not want the unit powering
off or sleeping while you are reflashing!

2. Download pinetrail image from the [ http://repo.meego.com/MeeGo/builds/ repo ]. I used
meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img:

''
wget http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/handset/images/meego-handset-ia32-pinetrail-mtf/meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img''

3. Follow [ http://meego.com/devices/netbook/installing-meego-your-netbook instructions ]
for using image-writer to create a bootable image on one of the USB drives (Drive 1 hereafter).

== Modifying the WeTab's bootloader ==

References: [ http://digitalorchard.blogspot.com/2010/12/wetabos-to-pure-meego.html 1]
[ http://wetabz.blogspot.com/2010/10/using-plop-boot-manager.html 2 ]

4. Now that you have a bootable image on Drive 1, you need to modify the WeTab's
bootloader to boot from USB. First download the latest version of plpbt.
I used plpbt-5.0.11:

''
wget http://download.plop.at/files/bootmngr/plpbt-5.0.13.zip''

5. Unzip the archive and copy the resulting files plpbt.bin and plpbt.img to the second
FLASH drive (hereafter called Drive 2).

6. Plug Drive 2 into the WeTab. From the WeTab's application
launcher screen, choose the terminal window icon. Then:

''
cd /boot/extlinux
sudo cp /media/<your drive name>/plpbt.bin .
sudo cp -p extlinux.conf extlinux.conf_dist
cp extlinux.conf_dist /media/<your drive name>
umount /media/<your drive name>''

7. Remove Drive 2 and plug it into the second Linux system. Then

''
cp /media/<your drive name>/extlinux.conf /tmp
<text editor of your choice> /tmp/extlinux.conf''

Insert the following text at the top of the list of bootable images:

''
label plp
linux plpbt.bin''

Note that the exact syntax may change (the names of files may change, for example) as plpbt releases new versions. Check that the file permissions of the new extlinux.conf match those of extlinux.conf_dist. Save the extlinux.conf file and

''
sudo cp /tmp/extlinux.conf /media/<your drive name>
eject /media/<your drive name>''

8. Plug Drive 2 into the WeTab, and from its shell prompt type

''
sudo cp -p /media/<your drive name>/extlinux.conf /boot/extlinux
umount /media/<your drive name>''

Remove Drive 2. You are finished with it.

== Install MeeGo onto the WeTab ==

''Note:'' The following procedure did not work well with a USB hub, probably because plpbt comes with an old version of the EHCI drivers. For best results, insert USB drives into the WeTab's top connector and plug the keyboard directly into the bottom one. Keyboard functionality in plpbt is hit-or-miss, but the soft button always works.

9. Plug Drive 1 with the Pinetrail image into the USB drive.

10. Power the WeTab off. Power on, and while the blue LED is
flashing, cover the soft button (circular sensor in upper left-hand corner
of the surface to the left of the blue LED).

11. The plop bootloader with its green 1970s-era font will display.
Tap the soft button to advance downward. Hold the soft button to
select "USB."

12. The system should now come up in the MeeGo installer. Plug in
the USB keyboard.

13. Choose "installation" or "live-boot" as suits you. Use the USB
keyboard (or soft button) to make selections, as the touchscreen is not working!
Sometimes it's possible to advance screens with carriage-return; at
other places Alt-F will move Forward. Follow the installation instructions.

If the USB keyboard does not work, you can still use the soft button, just as
in the plop bootloader. Tap it to highlight the next item. Hold it down to boot.
'''Be careful though: unlike in the plop bootmenu, once you select the bottom-most item, you cannot go back up!'''

14. If you have installed MeeGo, you'll reach a screen which tells you
to remove the flash drive and reboot. After removing the flash
drive, plug in the USB mouse. At this point I got an X11 error indicating that the screen settings weren't detected; just ignore it, as the problem is temporary. Once MeeGo (or WeTab OS) comes up, devices plugged into a USB hub will function once more.

15. Reboot the system. You should now see the MeeGo UX launcher.
Congratulations, you have installed MeeGo!

== Problems ==

1. The touchscreen is unresponsive. (Presumably this is a driver problem. See also [http://bugs.meego.com/show_bug.cgi?id=9524 bug 9524] )

2. The UX launcher image does not utilize the whole display, which is
unsurprising since Pinetrail is a handset image. (Presumably this
problem is fixable with xrandr.)

3. The build comes with the ath3k driver rather than the [http://wetabz.blogspot.com/2010/10/multitouch-driver-on-wetab.html ath9k one] that the modem requires.

== Related Links ==
* [http://wetab-community.de/forum/viewtopic.php?f=62&t=2502 Discussion in the WeTab Community Forum]
* [http://forum.meego.com/showthread.php?t=2320 Discussion in the official Meego Forum]

Installing MeeGo Images on WeTab Tablet

2011-09-21T15:03:10Z

Alison: /* Modifying the WeTab's bootloader */

'''Warning:''' the Pinetrail image running on the WeTab has some problems as
of 1/6/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader or kernel, you may '''brick''' your system.

== What is needed ==

1. A WeTab with power cable
2. sudo/root access on the WeTab
3. Two USB flash drives, one with a mountable filesystem already on it
4. A USB keyboard and mouse
5. Another Linux system for writing to the USB drives

== Creating a bootable MeeGo drive ==

1. Plug the WeTab into the mains. You do not want the unit powering
off or sleeping while you are reflashing!

2. Download pinetrail image from the [ http://repo.meego.com/MeeGo/builds/ repo ]. I used
meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img:

''
wget http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/handset/images/meego-handset-ia32-pinetrail-mtf/meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img''

3. Follow [ http://meego.com/devices/netbook/installing-meego-your-netbook instructions ]
for using image-writer to create a bootable image on one of the USB drives (Drive 1 hereafter).

== Modifying the WeTab's bootloader ==

References: [ http://digitalorchard.blogspot.com/2010/12/wetabos-to-pure-meego.html 1]
[ http://wetabz.blogspot.com/2010/10/using-plop-boot-manager.html 2 ]

4. Now that you have a bootable image on Drive 1, you need to modify the WeTab's
bootloader to boot from USB. First download the latest version of plpbt.
I used plpbt-5.0.11:

''
wget http://download.plop.at/files/bootmngr/plpbt-5.0.13.zip''

5. Unzip the archive and copy the resulting files plpbt.bin and plpbt.img to the second
FLASH drive (hereafter called Drive 2).

6. Plug Drive 2 into the WeTab. From the WeTab's application
launcher screen, choose the terminal window icon. Then:

''
cd /boot/extlinux
sudo cp /media/<your drive name>/plpbt.bin .
sudo cp -p extlinux.conf extlinux.conf_dist
cp extlinux.conf_dist /media/<your drive name>
umount /media/<your drive name>''

7. Remove Drive 2 and plug it into the second Linux system. Then

''
cp /media/<your drive name>/extlinux.conf /tmp
<text editor of your choice> /tmp/extlinux.conf''

Insert the following text at the top of the list of bootable images:

''
label plp
linux plpbt.bin''

Note that the exact syntax may change (the names of files may change, for example) as plpbt releases new versions. Check that the file permissions of the new extlinux.conf match those of extlinux.conf_dist. Save the extlinux.conf file and

''
sudo cp /tmp/extlinux.conf /media/<your drive name>
eject /media/<your drive name>''

8. Plug Drive 2 into the WeTab, and from its shell prompt type

''
sudo cp -p /media/<your drive name>/extlinux.conf /boot/extlinux
umount /media/<your drive name>''

Remove Drive 2. You are finished with it.

== Install MeeGo onto the WeTab ==

9. Plug Drive 1 with the Pinetrail image into the USB drive.

10. Power the WeTab off. Power on, and while the blue LED is
flashing, cover the soft button (circular sensor in upper left-hand corner
of the surface to the left of the blue LED).

11. The plop bootloader with its green 1970s-era font will display.
Tap the soft button to advance downward. Hold the soft button to
select "USB."

12. The system should now come up in the MeeGo installer. Plug in
the USB keyboard.

13. Choose "installation" or "live-boot" as suits you. Use the USB
keyboard to make selections, as the touchscreen is not working!
Sometimes it's possible to advance screens with carriage-return; at
other places Alt-F will move Forward. Follow the installation instructions.

If the USB keyboard does not work, you can still use the soft button, just as
in the plop bootloader. Tap it to highlight the next item. Hold it down to boot.
'''Be careful though: unlike in the plop bootmenu, once you select the bottom-most item, you cannot go back up!'''

14. If you have installed MeeGo, you'll reach a screen which tells you
to remove the flash drive and reboot. After removing the flash
drive, plug in the USB mouse. At this point I got an X11 error indicating that the screen settings weren't detected; just ignore it, as the problem is temporary.

15. Reboot the system. You should now see the MeeGo UX launcher.
Congratulations, you have installed MeeGo!

== Problems ==

1. The touchscreen is unresponsive. (Presumably this is a driver problem. See also [http://bugs.meego.com/show_bug.cgi?id=9524 bug 9524] )

2. The UX launcher image does not utilize the whole display, which is
unsurprising since Pinetrail is a handset image. (Presumably this
problem is fixable with xrandr.)

3. The build comes with the ath3k driver rather than the [http://wetabz.blogspot.com/2010/10/multitouch-driver-on-wetab.html ath9k one] that the modem requires.

== Related Links ==
* [http://wetab-community.de/forum/viewtopic.php?f=62&t=2502 Discussion in the WeTab Community Forum]
* [http://forum.meego.com/showthread.php?t=2320 Discussion in the official Meego Forum]

Installing MeeGo Images on WeTab Tablet

2011-09-21T15:02:32Z

Alison: /* Modifying the WeTab's bootloader */ Updated plpbt instructions.

'''Warning:''' the Pinetrail image running on the WeTab has some problems as
of 1/6/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader or kernel, you may '''brick''' your system.

== What is needed ==

1. A WeTab with power cable
2. sudo/root access on the WeTab
3. Two USB flash drives, one with a mountable filesystem already on it
4. A USB keyboard and mouse
5. Another Linux system for writing to the USB drives

== Creating a bootable MeeGo drive ==

1. Plug the WeTab into the mains. You do not want the unit powering
off or sleeping while you are reflashing!

2. Download pinetrail image from the [ http://repo.meego.com/MeeGo/builds/ repo ]. I used
meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img:

''
wget http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/handset/images/meego-handset-ia32-pinetrail-mtf/meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img''

3. Follow [ http://meego.com/devices/netbook/installing-meego-your-netbook instructions ]
for using image-writer to create a bootable image on one of the USB drives (Drive 1 hereafter).

== Modifying the WeTab's bootloader ==

References: [ http://digitalorchard.blogspot.com/2010/12/wetabos-to-pure-meego.html 1]
[ http://wetabz.blogspot.com/2010/10/using-plop-boot-manager.html 2 ]

4. Now that you have a bootable image on Drive 1, you need to modify the WeTab's
bootloader to boot from USB. First download the latest version of plpbt.
I used plpbt-5.0.11:

''
wget http://download.plop.at/files/bootmngr/plpbt-5.0.13.zip''

5. Unzip the archive and copy the resulting files plpbt.bin and plpbt.img to the second
FLASH drive (hereafter called Drive 2).

6. Plug Drive 2 into the WeTab. From the WeTab's application
launcher screen, choose the terminal window icon. Then:

''
cd /boot/extlinux
sudo cp /media/<your drive name>/plpbt.bin .
sudo cp -p extlinux.conf extlinux.conf_dist
cp extlinux.conf_dist /media/<your drive name>
umount /media/<your drive name>''

7. Remove Drive 2 and plug it into the second Linux system. Then

''
cp /media/<your drive name>/extlinux.conf /tmp
<text editor of your choice> /tmp/extlinux.conf''

Insert the following text at the top of the list of bootable images:

''
label plp
linux plpbt.bin''

Note that the exact syntax may change (the names of files may change, for example) as plpbt releases new versions. Check that the file permissions of the new extlinux.conf match those of extlinux.conf_dist. Save the extlinux.conf file and

''
sudo cp /tmp/extlinux.conf /media/<your drive name>
eject /media/<your drive name>''

8. Plug Drive 2 into the WeTab, and from its shell prompt type

''
sudo cp -p /media/<your drive name>/extlinux.conf /boot/extlinux
umount /media/<your drive name>''

Remove Drive 2. You are finished with it.

== Install MeeGo onto the WeTab ==

9. Plug Drive 1 with the Pinetrail image into the USB drive.

10. Power the WeTab off. Power on, and while the blue LED is
flashing, cover the soft button (circular sensor in upper left-hand corner
of the surface to the left of the blue LED).

11. The plop bootloader with its green 1970s-era font will display.
Tap the soft button to advance downward. Hold the soft button to
select "USB."

12. The system should now come up in the MeeGo installer. Plug in
the USB keyboard.

13. Choose "installation" or "live-boot" as suits you. Use the USB
keyboard to make selections, as the touchscreen is not working!
Sometimes it's possible to advance screens with carriage-return; at
other places Alt-F will move Forward. Follow the installation instructions.

If the USB keyboard does not work, you can still use the soft button, just as
in the plop bootloader. Tap it to highlight the next item. Hold it down to boot.
'''Be careful though: unlike in the plop bootmenu, once you select the bottom-most item, you cannot go back up!'''

14. If you have installed MeeGo, you'll reach a screen which tells you
to remove the flash drive and reboot. After removing the flash
drive, plug in the USB mouse. At this point I got an X11 error indicating that the screen settings weren't detected; just ignore it, as the problem is temporary.

15. Reboot the system. You should now see the MeeGo UX launcher.
Congratulations, you have installed MeeGo!

== Problems ==

1. The touchscreen is unresponsive. (Presumably this is a driver problem. See also [http://bugs.meego.com/show_bug.cgi?id=9524 bug 9524] )

2. The UX launcher image does not utilize the whole display, which is
unsurprising since Pinetrail is a handset image. (Presumably this
problem is fixable with xrandr.)

3. The build comes with the ath3k driver rather than the [http://wetabz.blogspot.com/2010/10/multitouch-driver-on-wetab.html ath9k one] that the modem requires.

== Related Links ==
* [http://wetab-community.de/forum/viewtopic.php?f=62&t=2502 Discussion in the WeTab Community Forum]
* [http://forum.meego.com/showthread.php?t=2320 Discussion in the official Meego Forum]

Installing MeeGo Images on WeTab Tablet

2011-09-20T16:48:07Z

Alison: /* Modifying the WeTab's bootloader */

'''Warning:''' the Pinetrail image running on the WeTab has some problems as
of 1/6/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader or kernel, you may '''brick''' your system.

== What is needed ==

1. A WeTab with power cable
2. sudo/root access on the WeTab
3. Two USB flash drives, one with a mountable filesystem already on it
4. A USB keyboard and mouse
5. Another Linux system for writing to the USB drives

== Creating a bootable MeeGo drive ==

1. Plug the WeTab into the mains. You do not want the unit powering
off or sleeping while you are reflashing!

2. Download pinetrail image from the [ http://repo.meego.com/MeeGo/builds/ repo ]. I used
meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img:

''
wget http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.13.20110105.1/handset/images/meego-handset-ia32-pinetrail-mtf/meego-handset-ia32-pinetrail-mtf-1.1.80.13.20110105.1.img''

3. Follow [ http://meego.com/devices/netbook/installing-meego-your-netbook instructions ]
for using image-writer to create a bootable image on one of the USB drives (Drive 1 hereafter).

== Modifying the WeTab's bootloader ==

References: [ http://digitalorchard.blogspot.com/2010/12/wetabos-to-pure-meego.html 1]
[ http://wetabz.blogspot.com/2010/10/using-plop-boot-manager.html 2 ]

4. Now that you have a bootable image on Drive 1, you need to modify the WeTab's
bootloader to boot from USB. First download the latest version of plpbt.
I used plpbt-5.0.11:

''
wget http://download.plop.at/files/bootmngr/plpbt-5.0.13.zip''

5. Unzip the archive and copy the resulting files plpbt.bin and plpbt.img to the second
FLASH drive (hereafter called Drive 2).

6. Plug Drive 2 into the WeTab. From the WeTab's application
launcher screen, choose the terminal window icon. Then:

''
cd /boot/extlinux
sudo cp /media/<your drive name>/plpbt* .
sudo cp extlinux.conf extlinux.conf_dist
cp extlinux.conf /media/<your drive name>
umount /media/<your drive name>''

7. Remove Drive 2 and plug it into the second Linux system. Then

''
cp /media/<your drive name>/extlinux.conf /tmp
<text editor of your choice> /tmp/extlinux.conf''

Insert the following text at the top of the list of bootable images:

''
label plop
menu label ^plpbt
KERNEL memdisk
INITRD plpbt.img
menu default''

Note that the exact syntax may change (the names of files may change, for example) as plpbt releases new versions. Save the extlinux.conf file and

''
sudo cp /tmp/extlinux.conf /media/<your drive name>
eject /media/<your drive name>''

8. Plug Drive 2 into the WeTab, and from its shell prompt type

''
sudo cp /media/<your drive name>/extlinux.conf /boot/extlinux
umount /media/<your drive name>''

Remove Drive 2. You are finished with it.

== Install MeeGo onto the WeTab ==

9. Plug Drive 1 with the Pinetrail image into the USB drive.

10. Power the WeTab off. Power on, and while the blue LED is
flashing, cover the soft button (circular sensor in upper left-hand corner
of the surface to the left of the blue LED).

11. The plop bootloader with its green 1970s-era font will display.
Tap the soft button to advance downward. Hold the soft button to
select "USB."

12. The system should now come up in the MeeGo installer. Plug in
the USB keyboard.

13. Choose "installation" or "live-boot" as suits you. Use the USB
keyboard to make selections, as the touchscreen is not working!
Sometimes it's possible to advance screens with carriage-return; at
other places Alt-F will move Forward. Follow the installation instructions.

If the USB keyboard does not work, you can still use the soft button, just as
in the plop bootloader. Tap it to highlight the next item. Hold it down to boot.
'''Be careful though: unlike in the plop bootmenu, once you select the bottom-most item, you cannot go back up!'''

14. If you have installed MeeGo, you'll reach a screen which tells you
to remove the flash drive and reboot. After removing the flash
drive, plug in the USB mouse. At this point I got an X11 error indicating that the screen settings weren't detected; just ignore it, as the problem is temporary.

15. Reboot the system. You should now see the MeeGo UX launcher.
Congratulations, you have installed MeeGo!

== Problems ==

1. The touchscreen is unresponsive. (Presumably this is a driver problem. See also [http://bugs.meego.com/show_bug.cgi?id=9524 bug 9524] )

2. The UX launcher image does not utilize the whole display, which is
unsurprising since Pinetrail is a handset image. (Presumably this
problem is fixable with xrandr.)

3. The build comes with the ath3k driver rather than the [http://wetabz.blogspot.com/2010/10/multitouch-driver-on-wetab.html ath9k one] that the modem requires.

== Related Links ==
* [http://wetab-community.de/forum/viewtopic.php?f=62&t=2502 Discussion in the WeTab Community Forum]
* [http://forum.meego.com/showthread.php?t=2320 Discussion in the official Meego Forum]

MeeGo IVI on ExoPC

2011-09-12T04:26:58Z

Alison: /* nobdy on IVI UX on ExoPC */ Video screenshot.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg|400px|thumb|center|nobdy in IVI scrollwheel menu]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

[[File:Nobdy IVI top applications.jpg|400px|thumb|center|nobdy in IVI home screen "Top applications" tray]]

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[[File:Nobdy_qmlviewer_screenshot.jpeg|600px|thumb|left|Watch the [[Media:Nobdy_qmlviewer.mp4‎|'''two-minute video''']] of nobdy running in xterm and displaying data in qmlviewer via D-bus.]]

= Miscellany =

[http://she-devel.com/MeeGo_Meetup_Sep7_2011.pdf slides] from nobdy on ExoPC talk, September 6, 2011.

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

File:Nobdy qmlviewer screenshot.jpeg

2011-09-12T04:23:45Z

Alison: Screenshot from nobdy data conveyed to D-bus and displayed via qmlviewer on ExoPC running Tablet Preview.

Screenshot from nobdy data conveyed to D-bus and displayed via qmlviewer on ExoPC running Tablet Preview.

MeeGo IVI on ExoPC

2011-09-12T04:14:21Z

Alison: /* nobdy on IVI UX on ExoPC */ Captions.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg|400px|thumb|center|nobdy in IVI scrollwheel menu]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

[[File:Nobdy IVI top applications.jpg|400px|thumb|center|nobdy in IVI home screen "Top applications" tray]]

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[[Media:Nobdy_qmlviewer.mp4‎|Video]] of nobdy running in xterm and displaying data in qmlviewer via D-bus.

= Miscellany =

[http://she-devel.com/MeeGo_Meetup_Sep7_2011.pdf slides] from nobdy on ExoPC talk, September 6, 2011.

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-12T04:11:17Z

Alison: /* nobdy on IVI UX on ExoPC */ Link to better video.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg|400px]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

[[File:Nobdy IVI top applications.jpg|400px]]

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[[Media:Nobdy_qmlviewer.mp4‎|Video]] of nobdy running in xterm and displaying data in qmlviewer via D-bus.

= Miscellany =

[http://she-devel.com/MeeGo_Meetup_Sep7_2011.pdf slides] from nobdy on ExoPC talk, September 6, 2011.

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

File:Nobdy qmlviewer.mp4

2011-09-12T03:03:37Z

Alison: Nobdy running with dbussimple subscriber on ExoPC Tablet Preview image and collecting data via an OBDLink scanner. The data is presented by qmlviewer using tripzero's GuagesExample.qml file. More info about nobdy: http://wiki.openice.org/index.php?t

Nobdy running with dbussimple subscriber on ExoPC Tablet Preview image and collecting data via an OBDLink scanner. The data is presented by qmlviewer using tripzero's GuagesExample.qml file.

More info about nobdy: http://wiki.openice.org/index.php?title=Nobdy&oldid=4637

MeeGo IVI on ExoPC

2011-09-11T07:22:02Z

Alison: /* Miscellany */ Link to talk slides.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

[[File:Nobdy IVI top applications.jpg]]

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6135604624/in/set-72157627642835378 Flickr video] of nobdy running in xterm and displaying data in qmlviewer via D-bus.

= Miscellany =

[http://she-devel.com/MeeGo_Meetup_Sep7_2011.pdf slides] from nobdy on ExoPC talk, September 6, 2011.

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-11T07:19:50Z

Alison: /* nobdy on IVI UX on ExoPC */ Link to better video.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

[[File:Nobdy IVI top applications.jpg]]

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6135604624/in/set-72157627642835378 Flickr video] of nobdy running in xterm and displaying data in qmlviewer via D-bus.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-11T07:18:43Z

Alison: /* nobdy on IVI UX on ExoPC */ nobdy in IVI "top applications" image.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

[[File:Nobdy IVI top applications.jpg]]

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-11T07:17:16Z

Alison: /* nobdy on IVI UX on ExoPC */ new image of IVI scroll list.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

[[File:Nobdy IVI scroll list.jpg]]

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

File:Nobdy IVI scroll list.jpg

2011-09-11T07:15:26Z

Alison: nobdy in IVI home screen's application scroll list.

nobdy in IVI home screen's application scroll list.

File:Nobdy IVI top applications.jpg

2011-09-11T07:14:47Z

Alison: nobdy icon appearing in MeeGo IVI 1.2's "top applications" bar.

nobdy icon appearing in MeeGo IVI 1.2's "top applications" bar.

File:Terminator qmlviewer IVI chooser.jpg

2011-09-11T07:14:02Z

Alison: Terminator and qmlviewer in IVI's app chooser menu.

Terminator and qmlviewer in IVI's app chooser menu.

MeeGo IVI on ExoPC

2011-09-11T07:13:00Z

Alison: /* nobdy on IVI UX on ExoPC */ nobdy and qmlviewer instructions.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]]. So far, OBD scanning with OBDLink works with Tablet Preview with examplesubscriber and dbussimple subscribers receiving data from genericobd2 provider, but the invocations don't work on the IVI UX. It's not yet clear whether the problem on the IVI UX is due to incomplete configuration or a differing versions of Qt Mobility between Tablet Preview and IVI UX.

In order to view OBD data with qmlviewer, first plug the OBDLink scanner into USB. Make sure that the corresponding /dev/ttyUSB* file is world-readable and writable. After copying [[File:Plugins.xml_dbus.txt|dbus config file]] to /etc/nobdy/plugins.xml, start nobdy in an xterm as "nobdy." Crank the ignition. You should see messages appear like 'Connected to ELM version "ELM327 v1.3a"' if all is working. Invoke qmlviewer with

qmlviewer -opengl -qmlbrowser

When the browser opens, choose tripzero's GuagesExample.qml. Some of the fields should live-update and respond to the car's accelerator, etc.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-09T06:44:34Z

Alison: /* nobdy on IVI UX on ExoPC */ plugins.xml examples

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

To test nobdy with a USB-connected OBD scanner, use a config file invoking [[File:Plugins.xml_examplesubscriber.txt|examplesubscriber]], but to view live OBD data with a GUI, use a config file that supports a [[File:Plugins.xml_dbus.txt|dbus subscriber]].

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

File:Plugins.xml examplesubscriber.txt

2011-09-09T06:40:40Z

Alison: Basic plugins.xml file for testing nobdy. Rename to "plugins.xml" and move to /etc/nobdy, or invoke nobdy with -c <yourconfigfilename>.

Basic plugins.xml file for testing nobdy. Rename to "plugins.xml" and move to /etc/nobdy, or invoke nobdy with -c <yourconfigfilename>.

File:Plugins.xml dbus.txt

2011-09-09T06:39:15Z

Alison: plugins.xml file for viewing nobdy data stream with qmlviewer. Rename to plugins.xml and put in /etc/nobdy, or invoke nobdy with -c <yourconfigfilename>.

plugins.xml file for viewing nobdy data stream with qmlviewer. Rename to plugins.xml and put in /etc/nobdy, or invoke nobdy with -c <yourconfigfilename>.

MeeGo IVI on ExoPC

2011-09-09T06:21:08Z

Alison: /* nobdy on IVI UX on ExoPC */ More about making nobdy work.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy qt-qmlviewer
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

The IVI launcher/chooser will only offer to switch among programs have .desktop files in /usr/share/applications/ and icon images in /usr/share/themes/1024-600-10/icons/ and /usr/share/themes/1024-600-10/icons/launchers. For qmlviewer, I copied a random small PNG image from one of the Qt4 directories into the icon directories, renaming it "qmlviewer.png" and added a reference to it in a qmlviewer.desktop file I created by editing one of the existing files in /usr/share/applications/. For nobdy, I did the same, but first I created an icon by using a program to write "nobdy" in a box. The resulting icons in the chooser show up in the video linked below.

Nobdy is more useful with the [http://www.linux-magazine.com/Issues/2011/126/Charly-s-Column-Terminator Terminator multi-xterm-on-screen] application. Follow the posted instructions to [http://www.tenshu.net/p/terminator.html install Terminator], but first zypper install vte and vte-python from the default 1.2.0 repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-09T00:58:51Z

Alison: /* nobdy on IVI UX on ExoPC */ Fix URL.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard Trunk
zypper install nobdy
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-09T00:53:41Z

Alison: /* nobdy on IVI UX on ExoPC */ nobdy installation.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

The [http://download.meego.com/live/Trunk/standard/i586/ Trunk] repo has a nobdy package that works fine on ExoPC. However, do not update from the Trunk repo unless you know what you are doing! A safe method is

zypper ar http://download.meego.com/live/Trunk/standard/i586 Trunk
zypper install nobdy
zypper mr -d Trunk

which installs nobdy and then immediately disables the Trunk repo.

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video] of nobdy running in xterm.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-09T00:35:39Z

Alison: Removing duplicate text.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log from the tablet virtual console is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-09T00:28:35Z

Alison: /* chroot for full graphical IVI UX */ Additional instructions.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2
cd ExoPC_chroot_scripts
./ExoPC_chroot_setup

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-09T00:27:34Z

Alison: /* chroot for IVI */ Splitting section into text and graphical sections.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI text console ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== chroot for full graphical IVI UX ====

Use [[File:ExoPC_chroot_scripts.tar.bz2.txt|these scripts]] with a new IVI install to copy all the needed drivers and libraries from Tablet Preview partition to IVI partition. Try the chroot once just to debug the IVI GUI installation before trying to boot into it directly. To use the scripts:

mv ExoPC_chroot_scripts.tar.bz2.txt ExoPC_chroot_scripts.tar.bz2
tar xjf ExoPC_chroot_scripts.tar.bz2

Edit the file ExoPC_IVI.conf to reflect your system settings. Most obviously, change "IVI_ROOT" to a different partition name if your IVI image is not in /dev/sda3. Once the script has run, follow the instructions to chroot to /IVI and start the full uxlaunch GUI there. Once the uxlaunch is working in the chroot, the correct files for Intel i915 graphics are installed on the IVI partition, so users can now boot directly into the graphical runlevel 5 of IVI.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

File:ExoPC chroot scripts.tar.bz2.txt

2011-09-09T00:05:51Z

Alison: A bz2 archive renamed ".txt" for upload-permission reasons. The archive contains bash scripts for copying kernel, graphics drivers, X11 shared object libraries and graphics-intensive executables for ExoPC to IVI partition (by default on /dev/sda3) from

A bz2 archive renamed ".txt" for upload-permission reasons. The archive contains bash scripts for copying kernel, graphics drivers, X11 shared object libraries and graphics-intensive executables for ExoPC to IVI partition (by default on /dev/sda3) from Tablet UX Preview installation (by default on /dev/sda2). Edit ExoPC_IVI.conf to change the defaults for your installation or just to find out which files the IVI 1.2 image needs changed for ExoPC use.

MeeGo IVI on ExoPC

2011-09-08T23:22:09Z

Alison: /* What is working */ Fixing link.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [[In-vehicle#MeeGo_IVI_UI_.28HMI.29|ShuttleXpress]] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-08T23:20:38Z

Alison: "System updates" section and scrollwheel note.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* [http://www.amazon.com/Contour-Design-00496-0-Shuttle-Xpress/dp/B0032Y0OH0/ref=sr_1_2?ie=UTF8&qid=1309555207&sr=8-2
ShuttleXpress] scroll wheel works out-of-the-box

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Post-installation notes =

== System updates and software installation ==

Since the 1.2 release, the MeeGo-IVI project has released [http://repo.meego.com/MeeGo/updates/1.2.0/repos/oss/ia32/packages/ updates]. Do not install these with "zypper update" without careful consideration! Zypping up from these repos auto-installs kernel-adaptation-intel-automotive and its modules, plus the EMGD graphics drivers and uninstalls the kernel-adaptation-pinetrail and i915 graphics drivers that ExoPC needs. It's possible to prevent this overwrite by using "zypper al kernel-adaptation-pinetrail", etc., but then nearly nothing will update.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-08T22:57:59Z

Alison: /* MIC Kickstart version */ Some warnings about kernel incompatibility.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] with kernel-adaptation-pinetrail is available. Note that any image with the kernel-adaptation-intel-automotive will not run on devices like Lenovo S-10t netbook or ExoPC.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-06T23:36:00Z

Alison: /* nobdy on IVI UX on ExoPC */ Link to video.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

[https://secure.flickr.com/photos/99725460@N00/6122192920/ Flickr video]

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-09-06T23:11:57Z

Alison: Adding nobdy section.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= [http://wiki.openice.org/index.php?title=Nobdy&oldid=4637 nobdy] on IVI UX on ExoPC =

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T18:31:04Z

Alison: /* What is not working */ HDMI out links.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a [http://download.meego.com/live/home:/brendan:/branches:/Trunk/standard/ fix] involving CONFIG_I2C_I801 in kernel configuration and a [http://build.meego.com/package/binaries?package=chrontel&project=home%3Abrendan&repository=MeeGo_1.2 chrontel] driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T18:27:57Z

Alison: /* Install images on ExoPC SSD and Configure Bootloader */ Remove now-incorrect comment.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a fix involving CONFIG_I2C_I801 in kernel configuration and a chrontel driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T18:26:12Z

Alison: /* Dual-booting Tablet and IVI UXes */ broken link fix

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

Despite repeated attempts, this method failed to produce a bootable IVI partition but the chroot method is more convenient for development anyway. See "Known Problems" below.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a fix involving CONFIG_I2C_I801 in kernel configuration and a chrontel driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file]] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T18:24:24Z

Alison: /* Dual-booting Tablet and IVI UXes */ Detailed instructions.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

Despite repeated attempts, this method failed to produce a bootable IVI partition but the chroot method is more convenient for development anyway. See "Known Problems" below.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a fix involving CONFIG_I2C_I801 in kernel configuration and a chrontel driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

Begin by partitioning the SSD in the ExoPC, as outlined above. Install the first OS in partition /dev/sda2 and make a copy of the /boot/extlinux/extlinux.conf file. Make a second copy of the file and use a text editor it to add an entry for the second OS, which the user will boot from the same kernel but from /dev/sda3. An example [[File:Extlinux.conf.txt|extlinux.conf file] shows tablet UX booting from /dev/sda2 and IVI from /dev/sda3. In the example, IVI is booting into text-console mode because of the "3" appended to the boot parameters.

MeeGo installers want the whole disk on which they are installed, and the second installer a user runs will typically ''not'' display the same convenient behavior as GRUB, which, if appropriately coaxed, will automagically modify a single /boot/grub/grub.conf file to accomodate multiple OSes or userlands. Instead, the user has two choices:

* Tell the second installer to mount the first partition /dev/sda1 as /boot. The second installer will hang while trying to modify the /boot/extlinux/extlinux.conf file created by the first installer. A forced reboot will produce an inoperable system, as the second installer has created an empty extlinux.conf file. Boot from a USB drive, mount the /dev/sda1 filesystem and copy back the extlinux.conf file backup onto /boot on /dev/sda1 to restore the system to operability. (Note that the USB stick that is used for rescue will have its own /boot. Do not copy the file there but to the ExoPC's SSD!)

* Don't explicitly tell the second installer to create a /boot partition. The installer will create /boot in the partition where the installation of the second UX is taking place (here /dev/sda3) and will make that partition as the bootable one. Fix this problem using parted, as outlined above.

For these methods to work, the kernel to which the extlinux.conf files makes reference must, of course, be in /boot as well! It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the Master Boot Record] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T16:52:44Z

Alison: /* Dual-booting Tablet and IVI UXes */ MBR backup link.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

Despite repeated attempts, this method failed to produce a bootable IVI partition but the chroot method is more convenient for development anyway. See "Known Problems" below.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a fix involving CONFIG_I2C_I801 in kernel configuration and a chrontel driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

A dual-boot installation can use this [[File:Extlinux.conf.txt|extlinux.conf file]] to choose the kernel-adaptation-pinetrail kernel appropriate for ExoPC along with Tablet and IVI userlands. Make a back-up copy of the existing /boot/extlinux/extlinux.conf file, download Extlinux.conf.txt, and move it to /boot/extlinux/extlinux.conf. Of course you need the kernel to which the extlinux.conf files makes reference in /boot as well! Also use parted or fdisk to make sure that the /boot that the file is moved into is the one marked in the Master Boot Record as the boot partition. It's a good idea to [http://www.linuxjournal.com/magazine/hack-and-when-disaster-strikes-restoring-master-boot-record back-up the MBR] once you have a tricky installation complete.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T16:44:46Z

Alison: /* Dual-booting Tablet and IVI UXes */ Clarification of file purpose.

= Introduction =
[[File:IVI_1.2.0.90_homescreen_ExoPC_2.jpg|300px|thumb|left|IVI 1.2 menu on ExoPC]]
[[File:IVI_1.2_ring_of_apps.jpg|300px|thumb|right|IVI 1.2 homescreen on ExoPC courtesy of [[User:vgrade|vgrade]]]]

The [https://meego.com/devices/in-vehicle in-vehicle] segment of MeeGo needs development platforms which are more convenient and less expensive than an actual car console. While there are a number of attractive [[In-vehicle#MeeGo_IVI_Development_Boards|development board options]] available, as of this writing (July 21, 2011), [[ARM/hardfp|hardfp]] GPU drivers needed to run MeeGo 1.2 are lacking for ARMv7 hardware. While there are some development boards available with x86 Atom processors, the [[Devices/ExoPC|ExoPC tablet]] that has been widely distributed in the MeeGo community offers an attractive alternative. Intel's [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet UX] release targeted the ExoPC, so software support for the device is superior to that for the raw-board options. While the ExoPC does not offer the automotive-relevant hardware extensions (e.g. CAN bus, internal GPS) that some of the development boards do, the functionality can be added via USB or bluetooth.

= Installation =

== Chroot Approach ==

The installation can conveniently be bootstrapped by using a chroot method like that previously employed by [[ARM/N900/Install/chroot|N900]] and [[Hardware-accelerated_graphics_on_Pandaboard_using_MeeGo|Pandaboard]] MeeGo-porting efforts. The basic idea is to install two images, one a stable, software-complete image like Tablet UX 1.2 for Atom, and the image to be adapted to the hardware, like IVI UX 1.2. The developer boots the stable image into a text console, then uses chroot to switch to the second image's userland. Subsequently the applications of the second image can be invoked using its own libraries and settings, but on top of the first image's kernel and virtual filesystems.

=== Chroot Details ===

==== Install images on ExoPC SSD and Configure Bootloader ====

* Burn latest [https://meego.com/downloads/releases/1.2/meego-tablet-developer-preview Tablet] and [https://meego.com/downloads/releases/1.2/meego-v1.2-in-vehicle-infotainment-ivi IVI] ISO images onto two USB sticks following the existing instructions.

* Attach a USB mouse and keyboard to the ExoPC. Get an externally powered USB hub as you will need 3 ports (mouse, keyboard and USB drive) and ExoPC has only two.

* Install the Tablet UX from the USB. On the ExoPC screen, wipe the "BBS" soft button back and forth during boot, and choose to boot from the USB device using the arrow keys on the attached keyboard. Also check out these [http://appdeveloper.intel.com/en-us/blog/2011/07/07/creating-multi-boot-exopc-tablet detailed instructions] from Intel.

[[File:CreateCustomLayout.jpg|400px|thumb|center|top|Invocation of partition tool from Tablet Installer]]


* In the installer's partition tool, choose "custom layout" and set the following partition table to preserve Windows but leave room for IVI:

[[File:TabletIVIWin_PartitionTable.jpg|400px|thumb|center|top|Final partition table for Tablet, IVI and (preinstalled) Windows]]



<pre>
Disk /dev/sda: 64.0 GB, 64023257088 bytes
255 heads, 63 sectors/track, 7783 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x3da06da4
Device Boot Start End Blocks Id System
/dev/sda1 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 2563 20480000 7 HPFS/NTFS
/dev/sda3 * 2563 2595 256001 83 Linux
/dev/sda4 2595 7783 41677522+ 5 Extended
/dev/sda5 2595 5077 19937281 83 Linux
/dev/sda6 5077 7559 19938003 83 Linux
/dev/sda7 7559 7783 1802237 82 Linux swap / Solaris
</pre>



Here /dev/sda1 and /dev/sda2 belong to Windows pre-install, /dev/sda3 is /boot created by Tablet installer, /dev/sda5 isTablet UX and /dev/sda6 will be IVI UX. Note that the filesystems must be ext3. (Default btrfs does not work with partition resizing tool yet.)


* Try booting the Tablet UX and (if you wish Windows) and verify that they work as you expect.

* Now install the IVI ISO from another USB stick. Boot from it in a similar fashion, choose "custom layout" in the partition tool and put IVI in partition /dev/sda6. Do not modify the other partitions.

Despite repeated attempts, this method failed to produce a bootable IVI partition but the chroot method is more convenient for development anyway. See "Known Problems" below.

* IVI installer may make /dev/sda6 the boot partition even if you tell it that /dev/sda5 is the boot partition. If this happens, boot Tablet from a USB stick, and do the following from vt1 (Ctrl-Alt-F1):

parted /dev/sda
p (prints partition table; see /dev/sda6 has boot flag)
set 5 boot
p (check that /dev/sda5 now has boot flag)
q

Now booting from SSD (/dev/sda) should work again.

* From the tablet UX, get a terminal window, perhaps by typing "Ctrl-Alt-F1." Use [http://opensuse-tutorials.com/2008/07/zypper-tips-and-tricks/ zypper] to update the software if you wish. Install any tools you will need to inspect and edit files, for example mlocate, binutils, man, man-db and emacs.

* Using your favorite text editor, modify the bootloader configuration in /boot/extlinux/extlinux.conf in /dev/sda3 in order to make what follows easier. Set prompt 1, a longer timeout and comment out "menu hidden" and "menu background splash.jpg" as shown below. Remove the "quiet" flag to get more diagnostics during boot. Don't change the other lines. Note that your kernel versions will be different.


<pre>

# extlinux.conf
prompt 1
timeout 20
default vesamenu.c32
menu autoboot Starting Tablet
#menu hidden
menu resolution 1366 768
#menu background splash.jpg
menu title Welcome to Tablet 1.2.0.90.0.20110517.1
menu color border 0 #ffffffff #00000000
menu color sel 7 #ffffffff #ff000000
menu color title 0 #ffffffff #00000000
menu color tabmsg 0 #ffffffff #00000000
menu color unsel 0 #ffffffff #00000000
menu color hotsel 0 #ff000000 #ffffffff
menu color hotkey 7 #ffffffff #ff000000
menu color timeout_msg 0 #ffffffff #00000000
menu color timeout 0 #ffffffff #00000000
menu color cmdline 0 #ffffffff #00000000
label tablet
menu label Tablet_1.2.0.90.0 (2.6.38.2-8.12-adaptation-pinetrail)
kernel vmlinuz-2.6.38.2-8.12-adaptation-pinetrail
# append ro root=/dev/sda5 quiet vga=current
append ro root=/dev/sda5 vga=current
menu default
label ivi
menu label IVI_1.2.0 (2.6.37.6-10.5-adaptation-intel-automotive)
kernel chain.c32
append boot 6
label Other
menu label Other
kernel chain.c32
append boot 1
</pre>


==== chroot for IVI ====

* Boot tablet UX. Then:

mkdir /IVI
mount /dev/sda6 /IVI
ls /IVI

IVI filesystem should appear. Verify that what you expect is there. For example, /etc/init.d for IVI has bluetooth-ivi and speech-dispatcherd, while /etc/init.d for Tablet does not.

* Get a 3rd virtual terminal (default on Tablet UX is two) by typing

openvt /bin/bash
chvt 3

Now you should have a shell prompt in a new VT. Login at vt3 and chroot to IVI
there:

chroot /IVI /bin/bash

Now "ls /et/init.d" will show what's in /IVI, not what's in Tablet's root partition. Change back to Tablet UX user filesystem just by switching virtual terminals.

==== Running IVI's GUI in chroot Environment ====

===== Summary =====

Having the IVI text console is a first step, but the whole purpose of the exercise is to get its GUI up and running. To do so, there is some more housekeeping needed, as detailed in this [[File:ExoPC_chroot_setup.txt|ExoPC_chroot_setup script]], which is
modified from one at [[ARM/N900/Install/chroot]]. [http://www.mp3car.com/meego-in-vehicle/147946-meego-1-2-has-been-released.html Nasa's instructions regarding graphics drivers] at mp3car.com may also be helpful.

[[File:MultiMeeGoBootloader.jpg|center|300px|Note "3" appended on bootloader prompt line. Hit "tab" when bootloader first appears to get the editable line.]]

Note that the script must be run from a Tablet text console and that the Tablet UX's GUI must not be running. In order to boot the Tablet image into text-only mode, append the character "3" to the bootargs command line as shown in the image above. If you allow the Tablet GUI to come up, the method described below to start IVI UX will fail even if you try to do so from a text console. The reason is that a given login can run only one instance of X11. Before starting uxlaunch to run the IVI GUI apps, we must perform several more housekeeping tasks:

* Since IVI user apps will talk to Tablet kernel, they need access to the kernel's existing virtual filesystems in /dev/, /proc, /tmp, /sys and /var.

* Since the IVI user libraries were built for different hardware, we can copy the different shared-object libraries that ExoPC needs from the Tablet userspace to the IVI one. Most notably, the ExoPC requires different X11 configuration since it has a different touchscreen.

===== Step-by-step instructions: =====

* Download [[File:ExoPC_chroot_setup.txt]] and [[File:unmount_IVI.txt|unmount_IVI script]], put them in Tablet root account's PATH and make them executable, removing ".txt" from end of filenames. Also download [[File:make_GL_links.txt|make_GL_links script]].
* Boot ExoPC to Tablet UX text console by hitting tab when bootloader appears and appending "3" to the command line.
* The system comes up in virtual terminal 2. Change to vt1 by typing "Ctrl-Alt-F1" and login as root.
* Run ExoPC_chroot_setup from the command line. The /IVI filesystem should be mounted. Try "ls /IVI" or "mount | grep IVI."
* Copy Make_GL_links.txt to the PATH of the root account of the ''IVI'' filesystem, e.g.
mkdir /IVI/root/bin
mv Make_GL_links.txt /IVI/root/bin/Make_GL_links
chmod a+x /IVI/root/bin/Make_GL_links
* Change to vt3 with "Ctrl-Alt-F3." Login as root there.
* Run Make_GL_links.
* Execute
uxlaunch&
Take note of the ampersand to run uxlaunch in background. Running uxlaunch in foreground will prevent further switching between the 3 virtual terminal windows.
* You will be switched to vt2 and see the IVI lock-screen. Use "Ctrl-Alt-F1" to get back to terminal with Tablet user filesystem and "Ctrl-Alt-F3" to get back to IVI text console. If there are problems, viewing /IVI/home/meego/.xsession-errors or /IVI/var/log/Xorg.0.log is likely to yield the most useful diagnostics. (From IVI text console or GUI, omit the leading "/IVI" from pathnames.)

===== What is working =====

* WiFi, touchscreen and ''sometimes'' audio output from IVI menus

* Web browser, music player and some of the other apps

===== What is not working =====

(Anyone who finds other problems, please add them!)

* Real-time navigation and mapping (no internal GPS).

* Audio is intermittent; can be partially addressed by restarting pulseaudio.

* Dialer: no modem.

* HDMI out; doesn't work with Tablet or Windows either. Brendan Arfoll has a fix involving CONFIG_I2C_I801 in kernel configuration and a chrontel driver copied from WeTab repos.

* Camera, which works with Windows but not Tablet UX either under 1.2.0.90 image, but which did work work 1.2.0 release.

* Make_GL_links script shouldn't be needed . . .

== Dual-booting Tablet and IVI UXes ==

A dual-boot installation can use this [[File:Extlinux.conf.txt|extlinux.conf file]] to choose the kernel-adaptation-pinetrail kernel appropriate for ExoPC along with Tablet and IVI userlands. Make a back-up copy of the existing /boot/extlinux/extlinux.conf file, download Extlinux.conf.txt, and move it to /boot/extlinux/extlinux.conf. Of course you need the kernel to which the extlinux.conf files makes reference in /boot as well! Also use parted or fdisk to make sure that the /boot that the file is moved into is the one marked in the MBR as the boot partition.

= MIC Kickstart version =

A [http://images.formeego.org/exopc/ ready-made bootable image] is available.

To build your own image which can be booted from a flash key using the mic tool ([[Image_Creation]]), start with the following kickstart file: [http://images.formeego.org/exopc/mg-ivi-ia32-pinetrail-latest.ks mg-ivi-ia32-pinetrail-latest.ks].

Create an image using the following command :-

sudo mic-image-creator -f livecd -t ../tmp/ -k ../cache/ -c ivi-ia32-pinetrail.ks -a i586 --release=latest --pkgmgr=yum

Burn to usb stick :-

sudo dd if=meego-ivi-ia32-pinetrail-latest.img of=/dev/sdX bs=4M - replace X with your device letter (b,c..)

Boot from stick in device.

Boot takes sometime. I've not tried installing to internal flash and you may need a keyboard to configure wireless as onscreen kb is not working.

vgrade

In order to stop the accelerometer being picked up as an input device and associated mouse pointer motion, download [[File:80-suppress-accel.conf.txt]] and move it to /etc/X11/xorg.conf.d/80-suppress-accel.conf.

= Miscellany =

[[File:ExoPCstandScreenshot.png|400px|thumb|left|[[Media:ExoPCstand.mp4|Cheap hack]] for making ExoPC stand.]]

MeeGo IVI on ExoPC

2011-08-28T16:40:31Z

Alison: /* Installation */ Reordering sections

MeeGo IVI on ExoPC

2011-08-28T16:37:53Z

Alison: /* Installation */ Reordering sections

MeeGo IVI on ExoPC

2011-08-28T16:36:23Z

Alison: /* What is not working */ HDMI out note.

MeeGo IVI on ExoPC

2011-08-28T16:34:29Z

Alison: /* Install images on ExoPC SSD and Configure Bootloader */ Uploaded and linked to dual-boot extlinux.conf file, called Extlinux.conf.txt.

File:Extlinux.conf.txt

2011-08-28T16:28:29Z

Alison: /boot/extlinux/extlinux.conf file that allows dual-boot of Tablet preview and IVI images using the kernel-adaptation-pinetrail kernel that is appropriate for ExoPC.

/boot/extlinux/extlinux.conf file that allows dual-boot of Tablet preview and IVI images using the kernel-adaptation-pinetrail kernel that is appropriate for ExoPC.

Devices/ExoPC

2011-08-12T22:30:45Z

Alison: /* HDMI Output */ My previous edit was misleading.

June 2011: [http://forum.meego.com/showthread.php?t=3596 forum thread]

== How to install latest MeeGo Snapshot ==
* Download img from http://download.meego.com/snapshots/latest/images/meego-tablet-ia32-pinetrail/ (latest points to the 1.2.80 series and is currently broken, use http://download.meego.com/snapshots/ and pick a recent 1.2.'''0'''.90 directory and go to ''images'' and ''meego-tablet-ia32-pinetrail'' inside)
* Write to your usb stick with '''dd if=meego.img of=/dev/sdb bs=4M'''
* Put usb stick in tablet and boot up, press "BBS" (on the touchscreen), select usb stick, now you need a usb keyboard to select install only option
** You can go through the bootloader using the button in the top left corner of the screen, short press to move to the next entry, long press to boot it. USB keyboard is optional.

== Mobile World Congress 2011 / MeeGo Summit.fi Machines : Update Repos ==

These machines were pre-installed with MeeGo 1.1 using a trunk-daily build of 1.1.90.2.20110209.4 (see /etc/zypp/repos/core.repo on the device); this is no longer available.

In the absence of a more stable repo an alternative is to track the latest package set by setting
baseurl=http://download.meego.com/trunk-daily/builds/trunk/latest/repos/oss/ia32/packages/
in the core.repo file.

Then:
zypper ref

(If anyone is brave enough to run ''zypper up'' and potentially need to reinstall then please say how this works.)

I tried that against the latest weekly repo at that time (http://repo.meego.com/MeeGo/builds/1.1.90/1.1.99.2.20110412.6/repos/oss/ia32/packages/) and first it hung on updating libc. After a reboot it ran through, but after one more reboot the Tablet UX didn't come back up anymore. Didn't investigate it further. I'll most likely use these instructions: http://meego.com/downloads/releases/1.2/meego-tablet-developer-preview and the image for aforementioned weekly.

--[[User:Dm8tbr|Dm8tbr]] 04:30, 18 April 2011 (UTC)

== Connecting Qt Creator to the Device ==
Go to Tools->Options; then Projects section, MeeGo Device Configurations tab.

Note that the meego user seems to need sudo rights to be able to run the remote execution:
cat <<EOF > /etc/sudoers.d/su-meego
meego ALL=(ALL) NOPASSWD: ALL
EOF
chmod 440 /etc/sudoers.d/su-meego

sed -i -e's/##includedir/#includedir/' /etc/sudoers

Also, for some reason, /usr/local and /usr/local/bin end up as root:root, mode 770. Fix this with:
sudo chmod 755 /usr/local
sudo chmod 755 /usr/local/bin
This looks like it's due to Qt Creator packaging

== Old Installation Notes ==

'''Warning:''' both the handset and netbook images running on the ExoPC have some problems as
of 1/30/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader and/or kernel, you may '''brick''' your system.

Sometimes the unit won't boot when a USB mouse is plugged in. An external keyboard doesn't cause the same problems. A mouse can be attached as soon as the MeeGo splashscreen appears. This might be a power problem that would be resolved by a USB hub with an external supply.

Installing the Handset image before the Netbook saves a bit of trouble if both are desired.

The version of parted that is invoked by the MeeGo installers [http://bugs.meego.com/show_bug.cgi?id=12945 will not resize an NTFS partition], so if you want to preserve Windows, use another partitioning tool before booting the MeeGo USB stick. [http://www.sysresccd.org/Main_Page systemrescuecd] worked fine.

The installation described here shrank the Windows partition to the (recommended minimum) 20 GB, then created an extended (logical) partition in the remaining space with a 2 GB swap partition and two primary (Is this right?) partitions of equal size in the remaining space.

Windows may come up and say that the partition table has been corrupted and that it will repair it ;-). The result is that the boot flag is set for the Win System partition, which prevents the extlinux bootloader from starting. To fix the problem, boot once more from the handy systemrescuecd stick and clear the duplicate boot flag from the System partition. Presto: your MeeGo install is again accessible.

== Installation ==

[[File:systemrescuecd_gparted_ExoPC.jpg|750px|frameless|Result of successful partitioning for triple-boot. Booting Windows may cause it to set the "boot" flag on its System partition as shown here and prevent extlinux from loading. Boot again with the systemrescuecd stick to clear the duplicate flag.]]

The ExoPC has an unlocked bootloader, so installation is relatively simple. First [http://meego.com/devices/netbook/installing-meego-your-netbook prepare a USB stick] with the image of your choice. After holding the power button for 4 seconds to start the boot process, touch the "Setup" soft button in the upper-righthand corner of the screen and disable "Quiet Boot." Boot again and touch the "BBS" soft button to manually select your USB drive as the boot device.

The netbook image does not create a useful /boot/extlinux/extlinux.conf file. One way of solving the problem is to install the handset image first, mount the handset image from the netbook image and just copy over the extlinux.conf file. Copy the entry for the handset image over to the end of the extlinux.conf file and change the details in order to create a file that works for all the images, then copy back to the handset image.

Don't forget to run "zypper update" from a terminal window as soon as your image is installed.

Warning: always unmount the USB filesystem before pulling the Flash drive out of the slot.

== Handset-specific notes ==

Touchscreen works great in the as-installed image. WiFi does not. A symptom of the problem is that both the ath9k (correct) and ath3K (wrong) kernel modules are autoloaded at boot time. Edit /etc/modprobe.d/blacklist.conf and add "blacklist ath3k" and then reboot. Unfortunately, WiFi still doesn't come up even though "lsmod" shows the same drivers as on netbook image, whose WiFi works great. "dmesg" says "ADDRCONF(NETDEV_UP): wlan0: link is not ready.

Before WiFi is working the easiest ways to get files onto the handset images are either from a mounted USB stick filesystem or by mounting the MeeGo netbook filesystem read-only and copying. In order to accomplish the latter, type "fdisk -l" to list the existing partitions. Create the directory where the netbook filesystem will be mounted, e.g. "mkdir -p /netbook". Then, assuming your netbook partition is /dev/sdaX and the filesystem type is ext3, enter "mount -t ext3 -o ro /dev/sdaX /netbook". Then "ls /netbook" will display the files on the netbook partition.

== Netbook-specific notes ==

WiFi works great with the as-installed netbook image.

As installed, the netbook image [http://bugs.meego.com/show_bug.cgi?id=9524 does not have a working touchscreen]. The system responds to a screen touch by darkening slightly and moving the cursor to the upper-lefthand corner. The needed driver, hid_egalax, is not autoloaded. Manually loading the driver with "modprobe -i hid_egalax" makes the touchscreen fully functional about half the time. Other times the behavior seems to be unaffected by the driver load.

=== Netbook trunk (1.2) ===

Some notes about installing a more recent MeeGo netbook image (I used meego-netbook-ia32-1.2.80.0.20110503.2.img) on ExoPC hardware:

# Installation needs an external keyboard, but went smoothly. However, on first boot (where you have to enter default user/password etc.), the external keyboard seemed to cause some power issue (even with the tablet plugged into its adapter), where X respawns too quickly.
#: To work around this, I followed [http://forum.meego.com/showthread.php?t=447 these instructions], summarised here:
## Plug in USB keyboard.
## Boot and start bashing the space key on the external keyboard (to interrupt grub).
## In the grub menu, press Tab so you can edit the kernel boot options.
## Append ' s' (space then 's', no quotation marks). This will mean you can boot into single user mode before X starts (and the keyboard causes X to continually respawn).
## Once you have a console available, run <code>startx</code> to get a minimal X environment.
## In the terminal window, run <code>/usr/bin/firstboot</code>. This starts the normal firstboot environment with the keyboard plugged in. Fill in the necessary.
## Once you're done with firstboot, back in the terminal, use the <code>halt</code> command to shut down.
## You should now be able to boot the tablet with the keyboard plugged in.
# Once you've booted successfully, you'll probably need to use the Terminal application to do stuff.
# With more recent images, hid_egalax does appear to be autoloaded (see the previous section). However, the pointer behaviour is still a little skittish. I found that installing evtouch stabilised it a bit:
#: <code>zypper in xorg-x11-drv-evtouch</code>
# To hide the pointer, edit /etc/sysconfig/uxlaunch and add a line like this to the end of the file:
#: <code>xopts=-nocursor</code>
#: But, once the pointer is gone, it is tricky to put the pointer to the top of the screen to see the toolbar (with links to MyZone etc.). However, if you've got an external keyboard plugged in, you can press the Windows key on the external keyboard to get there.
# This one is for those of you interested in running HTML5/JS web apps on netbook: The version of Chromium installed by default on the netbook image is quite old, and behaves pretty poorly for frameworks like [http://www.sencha.com/products/touch/ Sencha Touch]. You can instead install a developer build of Chrome, which works much better.
#:# Install lsb:
#:#: <code>sudo zypper in lsb</code>
#:# Download a developer build of Chrome (to replace Chromium) from
#:#: http://www.google.com/chrome/intl/en/eula_dev.html?dl=unstable_i386_rpm
#:# Install the RPM:
#:#: <code>sudo rpm -i google-chrome-unstable_current_i386.rpm</code>
#:# Run it:
#:#: <pre>google-chrome</pre>
#:#: NB on first run, it asks you to select a search engine; I chose Yahoo!, as selecting Google didn't work (ironically).
# On the other hand, if you're happy with the version of Chromium on the netbook image, and just want to be able to use it with touch, the [https://chrome.google.com/webstore/detail/ncegfehgjifmmpnjaihnjpbpddjjebme chromeTouch extension] works pretty well. However, this mucks up touch tracking in Sencha Touch.
# I had pretty much zero luck getting a decent virtual keyboard to work. I tried matchbox-keyboard, the meegotouch keyboard ([http://wiki.meego.com/Maliit Maliit]), and fvkbd. matchbox-keyboard and fvkbd at least appeared onscreen; I had no luck with the meegotouch keyboard at all.
#: I ended up keeping fvkbd with the following small edits:
#:* I changed its .desktop file (/usr/share/applications/fvkbd.desktop) to run the keyboard docked to the bottom of the screen, by changing the Exec line to:
#:*: <code>Exec=fvkbd-gtk -d -l keyboard-s.xml</code>
#:*: (note the extra -d to dock to the bottom of the screen)
#:* I also edited the keyboard-s.xml file (/usr/share/fvkbd/keyboard-s.xml) and set the width to 1366 and height to 330 (attributes on the outermost XML element). This makes the keyboard properly span the screen without being truncated (though I didn't work out how to centre the keys on the background)
#: To use the keyboard, start the fvkbd application first (from the Applications zone), then the application you want to use. The keyboard then sits on top of the application. This can be useful for emergencies, but it's not really adequate for full, everyday use.
# For some reason I couldn't discover, the screen dims when the power lead is unplugged. I was unable to figure out how to prevent this from happening (I tried looking through the BIOS, using xset, looking at upower, tried to turn off acpi etc. to no avail). However, there is a utility for setting the backlight brightness called <code>xbacklight</code> which at least helps you reset the screen brightness (the netbook image has no software control for this, and the tablet has no hardware keys for it).
#: Install it with:
#: <code>sudo zypper in xbacklight</code>
#: Then, to set the backlight brightness to 100%, do:
#: <code>xbacklight -set 100</code>
#: (Obviously, this is less than ideal. If anyone knows how to permanently prevent the screen from dimming when the power is unplugged, please let me know.)
# The ExoPC has a light sensor (tiny rectangle next to the power LEDs in the top left). When it's on, a reduction in the ambient light causes the screen to dim. This can be quite annoying in a British spring as bright sunlight rapidly alternates with storm clouds.
#: You can turn off the light sensor temporarily with:
#: <code>sudo echo 0 > /sys/devices/platform/asus_laptop/ls_switch</code>
#: However, you have to do this manually on each boot. There's probably some way to switch it off permanently, but no one on the internet has written it down. So the easiest thing for me to do was write a script in <code>/etc/init.d/ls_switch</code> to run on each boot (see below).
#: Make sure you <code>sudo chmod +x /etc/init.d/ls_switch</code> too.
#: With this script in place, set it to run on each boot with:
#: <code>chkconfig --add ls_switch</code>
#: When you reboot, the light sensor should be off.

<pre>
# script to go in /etc/init.d/ls_switch
#!/bin/sh
#
# ls_switch Turn light sensor off
#
# chkconfig: 2345 08 92
# description: Turns light sensor off on boot
#
#
### BEGIN INIT INFO
# Provides: ls_switch
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: turn off light sensor
# Description: turn off light sensor
### END INIT INFO

# Source function library.
. /etc/init.d/functions

case "$1" in
start)
echo "disabling light sensor"
echo 0 > /sys/devices/platform/asus_laptop/ls_switch
RETVAL=$?
;;
stop)
RETVAL=0
;;
*)
echo "Usage: ls_switch {start|stop}"
RETVAL=2
;;
esac

exit $RETVAL
</pre>

== IVI-specific notes ==

[[MeeGo_IVI_on_ExoPC|IVI 1.2 running on ExoPC]]

[[Category:Hardware]]

== Hardware Fixes ==

Please add steps here how to get hardware features working on MeeGo Tablet UX that don't work out of the box:

=== Crystal HD Video Decoder (BCM70015) ===

This should probably get packaged up, but for now:

Grab the latest crystalhd driver source from http://git.wilsonet.com/crystalhd.git

<pre>
git clone http://git.wilsonet.com/crystalhd.git
</pre>

Install the kernel headers to compile the kernel module

<pre>
zypper install kernel-adaptation-pinetrail-devel
</pre>

Compile and install the kernel module (currently won't just work, due to a bug in one of the kernel headers [https://bugs.meego.com/show_bug.cgi?id=20474] )

<pre>
cd ~/crystalhd/driver/linux
autoconf
./configure
make
sudo make install
</pre>

Compile and install the user-space library libcrystalhd

<pre>
cd ~/crystalhd/linux_lib/libcrystalhd
make
sudo make install
</pre>

OPTIONAL (?): It is also possible to compile a gstreamer plugin... but you need some extra development libraries

<pre>
sudo zypper install gstreamer-devel gst-plugins-base-devel
</pre>

Then some more compiling and installing

<pre>
cd ~/crystalhd/filters/gst/gst-plugin/
./autogen.sh
./configure
make
sudo make install
</pre>

==== Hardware H.264 Video Decoding with Flash Player ====

According to Flash Player 10.3 Release Notes [http://kb2.adobe.com/cps/901/cpsid_90194.html#main_known%20issues] under section Known Issues, subsection Audio/Video, Adobe has support for the Broadcom Crystal HD BCM70015 under Linux:

*H.264 Hardware decoding on Linux is available as an experimental feature and has been tested on NVidia GT 330 and Broadcom BCM70015 GPUs. Users may choose to enable hardware decoding by adding '''EnableLinuxHWVideoDecode=1''' in an mms.cfg configuration file. Users may experiance instability and crashes while watching hardware accelerated video. Please report any issues to http://bugs.adobe.com/flashplayer.

*H.264 Video Hardware acceleration is not available for DRM-protected content on Broadcom graphics chips.

The mms.cfg file mentioned should be created in /etc/adobe/mms.cfg

=== HDMI Output ===

This can be enabled by copying the following two files from a WeTab OS installation ([http://www.wetab-community.com/index.php?/topic/12074-hdmi-ausgang/ source link]) or from [http://repo.pub.meego.com/home:/arfoll:/utils/meego_1.1_core/i586/ MeeGo 1.1 repos] chrontel-1.0-11212.1.i586.rpm package:

<pre>
rpm -qpl /tmp/chrontel-1.0-11212.1.i586.rpm
/etc/xdg/autostart/tiitoo-hdmi.desktop
/lib/firmware/chrontel/fw7036.bin
/usr/bin/tiitoo-hdmi-daemon
/usr/bin/tiitoo-hdmi.sh
</pre>

After you have copied the files, you need to load two kernel modules and start the HDMI Daemon:

<pre>
sudo modprobe i2c-i801
sudo modprobe i2c-dev
sudo tiitoo-hdmi-daemon
</pre>

=== Accelerometer ===

The fix to [http://bugs.meego.com/10886 bug 10886] was to remove the MeeGo Sensors module in the kickstart file of the Tablet Image. This, however, causes the sensor to not be accessible to Qt Mobility ([http://bugs.meego.com/17461 bug 17461]). The workaround as described in [http://bugs.meego.com/17461 bug 17461] is as follows:

* Download the RPM: [http://download.meego.com/snapshots/1.2.0.90.1.20110525.2/repos/oss/ia32/packages/i586/libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm]
* Extract it: <code>rpm2cpio libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm | cpio -idv</code>
* Copy the module (as root): <code>cp usr/lib/qt4/plugins/sensors/libqtsensors_meego.so /usr/lib/qt4/plugins/sensors/</code>

To test, you can install the '''qt-mobility-examples''' package (using <code>zypper install qt-mobility-examples</code>) and run one of the examples:

$ /usr/lib/qtmobility/examples/accel
loaded the Generic plugin
loaded the grue plugin
Loaded the MeeGo sensor plugin
New sensor "accelerometersensor" interface created with session id 10 ...
acceleration: "0.12 0.27 2.35"
acceleration: "0.12 0.29 2.39"
acceleration: "0.10 0.29 2.39"
acceleration: "0.11 0.30 2.33"

=== Display brightness ===

If for some reason the display backlight becomes too dark, you can use the following command as root to set the brightness:

echo 15 >/sys/devices/virtual/backlight/acpi_video0/brightness

The value 15 has been obtained from the file <code>/sys/devices/virtual/backlight/acpi_video0/max_brightness</code>.

Another option is to install xbacklight (available in the MeeGo repos) and run:

xbacklight -set 100

You don't need to be root to do this.

Devices/ExoPC

2011-08-12T22:29:21Z

Alison: /* HDMI Output */ Better continuity.

June 2011: [http://forum.meego.com/showthread.php?t=3596 forum thread]

== How to install latest MeeGo Snapshot ==
* Download img from http://download.meego.com/snapshots/latest/images/meego-tablet-ia32-pinetrail/ (latest points to the 1.2.80 series and is currently broken, use http://download.meego.com/snapshots/ and pick a recent 1.2.'''0'''.90 directory and go to ''images'' and ''meego-tablet-ia32-pinetrail'' inside)
* Write to your usb stick with '''dd if=meego.img of=/dev/sdb bs=4M'''
* Put usb stick in tablet and boot up, press "BBS" (on the touchscreen), select usb stick, now you need a usb keyboard to select install only option
** You can go through the bootloader using the button in the top left corner of the screen, short press to move to the next entry, long press to boot it. USB keyboard is optional.

== Mobile World Congress 2011 / MeeGo Summit.fi Machines : Update Repos ==

These machines were pre-installed with MeeGo 1.1 using a trunk-daily build of 1.1.90.2.20110209.4 (see /etc/zypp/repos/core.repo on the device); this is no longer available.

In the absence of a more stable repo an alternative is to track the latest package set by setting
baseurl=http://download.meego.com/trunk-daily/builds/trunk/latest/repos/oss/ia32/packages/
in the core.repo file.

Then:
zypper ref

(If anyone is brave enough to run ''zypper up'' and potentially need to reinstall then please say how this works.)

I tried that against the latest weekly repo at that time (http://repo.meego.com/MeeGo/builds/1.1.90/1.1.99.2.20110412.6/repos/oss/ia32/packages/) and first it hung on updating libc. After a reboot it ran through, but after one more reboot the Tablet UX didn't come back up anymore. Didn't investigate it further. I'll most likely use these instructions: http://meego.com/downloads/releases/1.2/meego-tablet-developer-preview and the image for aforementioned weekly.

--[[User:Dm8tbr|Dm8tbr]] 04:30, 18 April 2011 (UTC)

== Connecting Qt Creator to the Device ==
Go to Tools->Options; then Projects section, MeeGo Device Configurations tab.

Note that the meego user seems to need sudo rights to be able to run the remote execution:
cat <<EOF > /etc/sudoers.d/su-meego
meego ALL=(ALL) NOPASSWD: ALL
EOF
chmod 440 /etc/sudoers.d/su-meego

sed -i -e's/##includedir/#includedir/' /etc/sudoers

Also, for some reason, /usr/local and /usr/local/bin end up as root:root, mode 770. Fix this with:
sudo chmod 755 /usr/local
sudo chmod 755 /usr/local/bin
This looks like it's due to Qt Creator packaging

== Old Installation Notes ==

'''Warning:''' both the handset and netbook images running on the ExoPC have some problems as
of 1/30/2011. See below.
'''Warning:''' as with any other device, if you incorrectly reflash the bootloader and/or kernel, you may '''brick''' your system.

Sometimes the unit won't boot when a USB mouse is plugged in. An external keyboard doesn't cause the same problems. A mouse can be attached as soon as the MeeGo splashscreen appears. This might be a power problem that would be resolved by a USB hub with an external supply.

Installing the Handset image before the Netbook saves a bit of trouble if both are desired.

The version of parted that is invoked by the MeeGo installers [http://bugs.meego.com/show_bug.cgi?id=12945 will not resize an NTFS partition], so if you want to preserve Windows, use another partitioning tool before booting the MeeGo USB stick. [http://www.sysresccd.org/Main_Page systemrescuecd] worked fine.

The installation described here shrank the Windows partition to the (recommended minimum) 20 GB, then created an extended (logical) partition in the remaining space with a 2 GB swap partition and two primary (Is this right?) partitions of equal size in the remaining space.

Windows may come up and say that the partition table has been corrupted and that it will repair it ;-). The result is that the boot flag is set for the Win System partition, which prevents the extlinux bootloader from starting. To fix the problem, boot once more from the handy systemrescuecd stick and clear the duplicate boot flag from the System partition. Presto: your MeeGo install is again accessible.

== Installation ==

[[File:systemrescuecd_gparted_ExoPC.jpg|750px|frameless|Result of successful partitioning for triple-boot. Booting Windows may cause it to set the "boot" flag on its System partition as shown here and prevent extlinux from loading. Boot again with the systemrescuecd stick to clear the duplicate flag.]]

The ExoPC has an unlocked bootloader, so installation is relatively simple. First [http://meego.com/devices/netbook/installing-meego-your-netbook prepare a USB stick] with the image of your choice. After holding the power button for 4 seconds to start the boot process, touch the "Setup" soft button in the upper-righthand corner of the screen and disable "Quiet Boot." Boot again and touch the "BBS" soft button to manually select your USB drive as the boot device.

The netbook image does not create a useful /boot/extlinux/extlinux.conf file. One way of solving the problem is to install the handset image first, mount the handset image from the netbook image and just copy over the extlinux.conf file. Copy the entry for the handset image over to the end of the extlinux.conf file and change the details in order to create a file that works for all the images, then copy back to the handset image.

Don't forget to run "zypper update" from a terminal window as soon as your image is installed.

Warning: always unmount the USB filesystem before pulling the Flash drive out of the slot.

== Handset-specific notes ==

Touchscreen works great in the as-installed image. WiFi does not. A symptom of the problem is that both the ath9k (correct) and ath3K (wrong) kernel modules are autoloaded at boot time. Edit /etc/modprobe.d/blacklist.conf and add "blacklist ath3k" and then reboot. Unfortunately, WiFi still doesn't come up even though "lsmod" shows the same drivers as on netbook image, whose WiFi works great. "dmesg" says "ADDRCONF(NETDEV_UP): wlan0: link is not ready.

Before WiFi is working the easiest ways to get files onto the handset images are either from a mounted USB stick filesystem or by mounting the MeeGo netbook filesystem read-only and copying. In order to accomplish the latter, type "fdisk -l" to list the existing partitions. Create the directory where the netbook filesystem will be mounted, e.g. "mkdir -p /netbook". Then, assuming your netbook partition is /dev/sdaX and the filesystem type is ext3, enter "mount -t ext3 -o ro /dev/sdaX /netbook". Then "ls /netbook" will display the files on the netbook partition.

== Netbook-specific notes ==

WiFi works great with the as-installed netbook image.

As installed, the netbook image [http://bugs.meego.com/show_bug.cgi?id=9524 does not have a working touchscreen]. The system responds to a screen touch by darkening slightly and moving the cursor to the upper-lefthand corner. The needed driver, hid_egalax, is not autoloaded. Manually loading the driver with "modprobe -i hid_egalax" makes the touchscreen fully functional about half the time. Other times the behavior seems to be unaffected by the driver load.

=== Netbook trunk (1.2) ===

Some notes about installing a more recent MeeGo netbook image (I used meego-netbook-ia32-1.2.80.0.20110503.2.img) on ExoPC hardware:

# Installation needs an external keyboard, but went smoothly. However, on first boot (where you have to enter default user/password etc.), the external keyboard seemed to cause some power issue (even with the tablet plugged into its adapter), where X respawns too quickly.
#: To work around this, I followed [http://forum.meego.com/showthread.php?t=447 these instructions], summarised here:
## Plug in USB keyboard.
## Boot and start bashing the space key on the external keyboard (to interrupt grub).
## In the grub menu, press Tab so you can edit the kernel boot options.
## Append ' s' (space then 's', no quotation marks). This will mean you can boot into single user mode before X starts (and the keyboard causes X to continually respawn).
## Once you have a console available, run <code>startx</code> to get a minimal X environment.
## In the terminal window, run <code>/usr/bin/firstboot</code>. This starts the normal firstboot environment with the keyboard plugged in. Fill in the necessary.
## Once you're done with firstboot, back in the terminal, use the <code>halt</code> command to shut down.
## You should now be able to boot the tablet with the keyboard plugged in.
# Once you've booted successfully, you'll probably need to use the Terminal application to do stuff.
# With more recent images, hid_egalax does appear to be autoloaded (see the previous section). However, the pointer behaviour is still a little skittish. I found that installing evtouch stabilised it a bit:
#: <code>zypper in xorg-x11-drv-evtouch</code>
# To hide the pointer, edit /etc/sysconfig/uxlaunch and add a line like this to the end of the file:
#: <code>xopts=-nocursor</code>
#: But, once the pointer is gone, it is tricky to put the pointer to the top of the screen to see the toolbar (with links to MyZone etc.). However, if you've got an external keyboard plugged in, you can press the Windows key on the external keyboard to get there.
# This one is for those of you interested in running HTML5/JS web apps on netbook: The version of Chromium installed by default on the netbook image is quite old, and behaves pretty poorly for frameworks like [http://www.sencha.com/products/touch/ Sencha Touch]. You can instead install a developer build of Chrome, which works much better.
#:# Install lsb:
#:#: <code>sudo zypper in lsb</code>
#:# Download a developer build of Chrome (to replace Chromium) from
#:#: http://www.google.com/chrome/intl/en/eula_dev.html?dl=unstable_i386_rpm
#:# Install the RPM:
#:#: <code>sudo rpm -i google-chrome-unstable_current_i386.rpm</code>
#:# Run it:
#:#: <pre>google-chrome</pre>
#:#: NB on first run, it asks you to select a search engine; I chose Yahoo!, as selecting Google didn't work (ironically).
# On the other hand, if you're happy with the version of Chromium on the netbook image, and just want to be able to use it with touch, the [https://chrome.google.com/webstore/detail/ncegfehgjifmmpnjaihnjpbpddjjebme chromeTouch extension] works pretty well. However, this mucks up touch tracking in Sencha Touch.
# I had pretty much zero luck getting a decent virtual keyboard to work. I tried matchbox-keyboard, the meegotouch keyboard ([http://wiki.meego.com/Maliit Maliit]), and fvkbd. matchbox-keyboard and fvkbd at least appeared onscreen; I had no luck with the meegotouch keyboard at all.
#: I ended up keeping fvkbd with the following small edits:
#:* I changed its .desktop file (/usr/share/applications/fvkbd.desktop) to run the keyboard docked to the bottom of the screen, by changing the Exec line to:
#:*: <code>Exec=fvkbd-gtk -d -l keyboard-s.xml</code>
#:*: (note the extra -d to dock to the bottom of the screen)
#:* I also edited the keyboard-s.xml file (/usr/share/fvkbd/keyboard-s.xml) and set the width to 1366 and height to 330 (attributes on the outermost XML element). This makes the keyboard properly span the screen without being truncated (though I didn't work out how to centre the keys on the background)
#: To use the keyboard, start the fvkbd application first (from the Applications zone), then the application you want to use. The keyboard then sits on top of the application. This can be useful for emergencies, but it's not really adequate for full, everyday use.
# For some reason I couldn't discover, the screen dims when the power lead is unplugged. I was unable to figure out how to prevent this from happening (I tried looking through the BIOS, using xset, looking at upower, tried to turn off acpi etc. to no avail). However, there is a utility for setting the backlight brightness called <code>xbacklight</code> which at least helps you reset the screen brightness (the netbook image has no software control for this, and the tablet has no hardware keys for it).
#: Install it with:
#: <code>sudo zypper in xbacklight</code>
#: Then, to set the backlight brightness to 100%, do:
#: <code>xbacklight -set 100</code>
#: (Obviously, this is less than ideal. If anyone knows how to permanently prevent the screen from dimming when the power is unplugged, please let me know.)
# The ExoPC has a light sensor (tiny rectangle next to the power LEDs in the top left). When it's on, a reduction in the ambient light causes the screen to dim. This can be quite annoying in a British spring as bright sunlight rapidly alternates with storm clouds.
#: You can turn off the light sensor temporarily with:
#: <code>sudo echo 0 > /sys/devices/platform/asus_laptop/ls_switch</code>
#: However, you have to do this manually on each boot. There's probably some way to switch it off permanently, but no one on the internet has written it down. So the easiest thing for me to do was write a script in <code>/etc/init.d/ls_switch</code> to run on each boot (see below).
#: Make sure you <code>sudo chmod +x /etc/init.d/ls_switch</code> too.
#: With this script in place, set it to run on each boot with:
#: <code>chkconfig --add ls_switch</code>
#: When you reboot, the light sensor should be off.

<pre>
# script to go in /etc/init.d/ls_switch
#!/bin/sh
#
# ls_switch Turn light sensor off
#
# chkconfig: 2345 08 92
# description: Turns light sensor off on boot
#
#
### BEGIN INIT INFO
# Provides: ls_switch
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: turn off light sensor
# Description: turn off light sensor
### END INIT INFO

# Source function library.
. /etc/init.d/functions

case "$1" in
start)
echo "disabling light sensor"
echo 0 > /sys/devices/platform/asus_laptop/ls_switch
RETVAL=$?
;;
stop)
RETVAL=0
;;
*)
echo "Usage: ls_switch {start|stop}"
RETVAL=2
;;
esac

exit $RETVAL
</pre>

== IVI-specific notes ==

[[MeeGo_IVI_on_ExoPC|IVI 1.2 running on ExoPC]]

[[Category:Hardware]]

== Hardware Fixes ==

Please add steps here how to get hardware features working on MeeGo Tablet UX that don't work out of the box:

=== Crystal HD Video Decoder (BCM70015) ===

This should probably get packaged up, but for now:

Grab the latest crystalhd driver source from http://git.wilsonet.com/crystalhd.git

<pre>
git clone http://git.wilsonet.com/crystalhd.git
</pre>

Install the kernel headers to compile the kernel module

<pre>
zypper install kernel-adaptation-pinetrail-devel
</pre>

Compile and install the kernel module (currently won't just work, due to a bug in one of the kernel headers [https://bugs.meego.com/show_bug.cgi?id=20474] )

<pre>
cd ~/crystalhd/driver/linux
autoconf
./configure
make
sudo make install
</pre>

Compile and install the user-space library libcrystalhd

<pre>
cd ~/crystalhd/linux_lib/libcrystalhd
make
sudo make install
</pre>

OPTIONAL (?): It is also possible to compile a gstreamer plugin... but you need some extra development libraries

<pre>
sudo zypper install gstreamer-devel gst-plugins-base-devel
</pre>

Then some more compiling and installing

<pre>
cd ~/crystalhd/filters/gst/gst-plugin/
./autogen.sh
./configure
make
sudo make install
</pre>

==== Hardware H.264 Video Decoding with Flash Player ====

According to Flash Player 10.3 Release Notes [http://kb2.adobe.com/cps/901/cpsid_90194.html#main_known%20issues] under section Known Issues, subsection Audio/Video, Adobe has support for the Broadcom Crystal HD BCM70015 under Linux:

*H.264 Hardware decoding on Linux is available as an experimental feature and has been tested on NVidia GT 330 and Broadcom BCM70015 GPUs. Users may choose to enable hardware decoding by adding '''EnableLinuxHWVideoDecode=1''' in an mms.cfg configuration file. Users may experiance instability and crashes while watching hardware accelerated video. Please report any issues to http://bugs.adobe.com/flashplayer.

*H.264 Video Hardware acceleration is not available for DRM-protected content on Broadcom graphics chips.

The mms.cfg file mentioned should be created in /etc/adobe/mms.cfg

=== HDMI Output ===

This can be enabled by copying the following two files from a WeTab OS installation ([http://www.wetab-community.com/index.php?/topic/12074-hdmi-ausgang/ source link]) or from [http://repo.pub.meego.com/home:/arfoll:/utils/meego_1.1_core/i586/ MeeGo 1.1 repos] chrontel-1.0-11212.1.i586.rpm package:

<pre>
rpm -qpl /tmp/chrontel-1.0-11212.1.i586.rpm
/etc/xdg/autostart/tiitoo-hdmi.desktop
/lib/firmware/chrontel/fw7036.bin
/usr/bin/tiitoo-hdmi-daemon
/usr/bin/tiitoo-hdmi.sh
</pre>

then run the included scripts:

<pre>
/usr/bin/tiitoo-hdmi-daemon
/lib/firmware/chrontel/fw7036.bin
</pre>

After you have copied the files, you need to load two kernel modules and start the HDMI Daemon:

<pre>
sudo modprobe i2c-i801
sudo modprobe i2c-dev
sudo tiitoo-hdmi-daemon
</pre>

=== Accelerometer ===

The fix to [http://bugs.meego.com/10886 bug 10886] was to remove the MeeGo Sensors module in the kickstart file of the Tablet Image. This, however, causes the sensor to not be accessible to Qt Mobility ([http://bugs.meego.com/17461 bug 17461]). The workaround as described in [http://bugs.meego.com/17461 bug 17461] is as follows:

* Download the RPM: [http://download.meego.com/snapshots/1.2.0.90.1.20110525.2/repos/oss/ia32/packages/i586/libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm]
* Extract it: <code>rpm2cpio libqtsensors1-1.2.0~beta0+git2726-10.11.i586.rpm | cpio -idv</code>
* Copy the module (as root): <code>cp usr/lib/qt4/plugins/sensors/libqtsensors_meego.so /usr/lib/qt4/plugins/sensors/</code>

To test, you can install the '''qt-mobility-examples''' package (using <code>zypper install qt-mobility-examples</code>) and run one of the examples:

$ /usr/lib/qtmobility/examples/accel
loaded the Generic plugin
loaded the grue plugin
Loaded the MeeGo sensor plugin
New sensor "accelerometersensor" interface created with session id 10 ...
acceleration: "0.12 0.27 2.35"
acceleration: "0.12 0.29 2.39"
acceleration: "0.10 0.29 2.39"
acceleration: "0.11 0.30 2.33"

=== Display brightness ===

If for some reason the display backlight becomes too dark, you can use the following command as root to set the brightness:

echo 15 >/sys/devices/virtual/backlight/acpi_video0/brightness

The value 15 has been obtained from the file <code>/sys/devices/virtual/backlight/acpi_video0/max_brightness</code>.

Another option is to install xbacklight (available in the MeeGo repos) and run:

xbacklight -set 100

You don't need to be root to do this.