http://wiki.linuxmce.org/api.php?action=feedcontributions&user=Davegravy&feedformat=atomLinuxMCE - User contributions [en]2024-03-28T20:22:46ZUser contributionsMediaWiki 1.24.1http://wiki.linuxmce.org/index.php?title=1004_Video_Hardware_Compatibility_List&diff=335941004 Video Hardware Compatibility List2012-12-12T03:21:31Z<p>Davegravy: </p>
<hr />
<div>[[Category: Hardware Lists]]<br />
[[Category: Compatibility]]<br />
= GPU Compatibility List =<br />
<br />
The purpose behind this page is to give a compatibility probability list for unsupported chipsets, and to confirm these when possible. <br />
<br />
'''<font size=3> -- All GPU's listed here are considered UNSUPPORTED --</font>''' though this matrix seeks to give you solutions we will not automate, but have figured out as workarounds. All GPU's ''not'' listed here are currently believed to be supported. If not please notify [http://wiki.linuxmce.org/index.php/User:L3mce L3mce] preferably in IRC, or at the forum.<br />
<br />
Some common information you will want to get and use. Please give this data when creating a ticket or forum post about a card not working/not listed here.<br />
<br />
<br />
* Begin any of this sort of work as root. All commands in this matrix assume you are root. If you have ssh'ed into your MD, you are already root. If you are on a hybrid then:<br />
sudo -i<br />
* Update PCI IDs<br />
update-pciids<br />
* Detailed card information<br />
lspci -nn | grep -w 'VGA'<br />
* Card PCI ID<br />
lspci -nn | grep -w 'VGA' | sed 's/.*://;s/\].*//'<br />
* Audio cards that ALSA can see<br />
aplay -l<br />
* Look at ALSA config file<br />
cat /etc/asound.conf<br />
* Look at xine config file<br />
tail -4 /etc/pluto/xine.conf<br />
* Check ALSA version<br />
apt-cache policy alsa-base | grep Installed<br />
* Check ALSA backports installation status<br />
apt-cache policy linux-backports-modules-alsa-$(uname -r) | grep Installed<br />
<br />
All together, minus rooting:<br />
update-pciids<br />
lspci -nn | grep -w 'VGA'<br />
lspci -nn | grep -w 'VGA' | sed 's/.*://;s/\].*//'<br />
aplay -l<br />
cat /etc/asound.conf<br />
tail -4 /etc/pluto/xine.conf<br />
apt-cache policy alsa-base | grep Installed<br />
apt-cache policy linux-backports-modules-alsa-$(uname -r) | grep Installed<br />
<br />
<br />
'''Audio''': For the terms of this list, "audio" refers to digital audio from the card, typically HDMI audio. For further understanding of how audio currently works, please see the new [http://wiki.linuxmce.org/index.php/Audio_in_1004 audio scheme] for possible resolution of audio issues without installing things you do not need. '''If your cards audio device shows up in aplay then nothing more is required to install''', only a configuration change is necessary, as detailed in the link.<br />
<br />
<br />
===nVidia===<br />
<table border="1" bordercolor="#FFCC00" style="background-color:#FFFFCC" width="100%" cellpadding="3" cellspacing="3"><br />
<tr style="background-color:#000000"><br />
<td><font color="white">Series</font></td><br />
<td><font color="white">Model</font></td><br />
<td><font color="white">Video OOTB</font></td><br />
<td><font color="white">Audio OOTB</font></td><br />
<td><font color="white">Resolution</font></td><br />
</tr><br />
<tr><br />
<td>GT</td><br />
<td>4xx</td><br />
<td style="background-color:#00FF00">Yes</td><br />
<td style="background-color:#FF0000">No</td><br />
<td>[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Upgrade_Kernel_to_Natty Upgrade Kernel to Natty]<br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_.25_Support Update ALSA]<BR><br />
Change line 225 of SetupAudioVideo.sh CardDevice from 7 to 9 <BR><br />
Change audio config in MythTV frontend to "plughw:1,9"</td><br />
</tr><br />
<tr><br />
<td>GTX</td><br />
<td>5xx</td><br />
<td style="background-color:#FFFF00">Sometimes</td><br />
<td style="background-color:#FF0000">No</td><br />
<td>Try first running a [http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Speaker_Test Speaker test]; setting dParam=3. <br><br />
if this produces sound, then change line 225 of SetupAudioVideo.sh CardDevice from 7 to 3. Try other params listed in link absent success. <BR><br />
<br />
SHOULD your card not be listed in aplay then: <br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Upgrade_Kernel_to_Natty Upgrade Kernel to Natty]<br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_.25_Support Update ALSA]</td><br />
</tr><br />
<tr><br />
<td>GT</td><br />
<td>6xx</td><br />
<td style="background-color:#00FF00">Yes</td><br />
<td style="background-color:#FF0000">No</td><br />
<td>[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Upgrade_Kernel_to_Natty Upgrade Kernel to Natty]<br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_.25_Support Update ALSA]</td><br />
</tr><br />
</table><br />
<br />
<br />
===Intel===<br />
<table border="1" bordercolor="#FFCC00" style="background-color:#FFFFCC" width="100%" cellpadding="3" cellspacing="3"><br />
<tr style="background-color:#000000"><br />
<td><font color="white">Series</font></td><br />
<td><font color="white">Model</font></td><br />
<td><font color="white">Video OOTB</font></td><br />
<td><font color="white">Audio OOTB</font></td><br />
<td><font color="white">Resolution</font></td><br />
</tr><br />
<tr><br />
<td>Sandy Bridge</td><br />
<td>All</td><br />
<td style="background-color:#00FF00">Yes</td><br />
<td style="background-color:#00FF00">Yes</td><br />
<td>This should be working, out of the box. If something went wrong, then do the following:<br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Upgrade_Kernel_to_Natty Upgrade Kernel to Natty]</td><br />
</tr><br />
<tr><br />
<td>Ivy Bridge</td><br />
<td>All</td><br />
<td style="background-color:#FF0000">No</td><br />
<td style="background-color:#FF0000">No</td><br />
<td>[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Upgrade_Kernel_to_Latest_Oneiric Upgrade Kernel to Latest Oneiric]<br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_.25_Support Update ALSA]</td><br />
</tr><br />
</table><br />
<br />
<br />
===ATI===<br />
<table border="1" bordercolor="#FFCC00" style="background-color:#FFFFCC" width="100%" cellpadding="3" cellspacing="3"><br />
<tr style="background-color:#000000"><br />
<td><font color="white">Series</font></td><br />
<td><font color="white">Model</font></td><br />
<td><font color="white">Video OOTB</font></td><br />
<td><font color="white">Audio OOTB</font></td><br />
<td><font color="white">Resolution</font></td><br />
</tr><br />
<tr><br />
<td>HD</td><br />
<td>57xx and up</td><br />
<td style="background-color:#FF0000">No</td><br />
<td style="background-color:#FF0000">No</td><br />
<td>Due to a known bug in repo catalyst utility, aticonfig does not find these cards.<br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ATI_Catalyst_Support Add ATI Catalyst Support] <br><br><br />
'''If''' audio is a problem, please '''first''' change the [http://wiki.linuxmce.org/index.php/Audio_in_1004 config] and test again. Failing that:<br><br />
[http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_Backport_.24_Support Add ALSA Backport .24 Support], reboot, and test [http://wiki.linuxmce.org/index.php/Audio_in_1004 configs]<br><br />
Failing that: apt-get remove --purge -yf linux-backports-modules-alsa-$(uname -r) <br><br />
Then [http://wiki.linuxmce.org/index.php/1004_Video_Hardware_Compatibility_List#Add_ALSA_.24_Support Add ALSA .24 Support], reboot, and try the different [http://wiki.linuxmce.org/index.php/Audio_in_1004 configs]</td><br />
</tr><br />
</table><br />
<br />
<br />
==dpkg==<br />
Should any of the solutions below throw back dpkg errors then:<br />
dpkg --configure -a<br />
A working system should NOT produce any result. If it DOES produce output, then it has tried to fix itself. Try commands again. If there are STILL problems, you need further assistance to stabilize your system.<br />
<br />
<br />
==MythTV==<br />
Some of these configurations cause MythTV to not utilize !default correctly... so in the MythTV '''front-end''' (NOT backend) setup/general, you may need to specify HDMI or plughw:1,7 from the detected options available in the audio setup. In some rare cases with ATI or Intel you may find it necessary to drop the device number... so turn its auto-detected "plughw:1,7" into "plughw:1". I recommend using a keyboard with a delete key, because in myth, backpsace takes you back a menu.<br />
<br />
To get to MythTV general setup, open MythTV, once it finishes tuning a channel, press escape. Don't do it to quick or myth will think it died and try to respawn. <br />
This will take you your recorded programs most likely. Press esc. Choose Setup. Choose General. Audio is on the second page as memory serves. Left and right in the Audio field will scroll through the options.<br />
<br />
<br />
= Solutions =<br />
All solutions here can be copied/pasted, but '''assume you are root'''. Please begin sessions by typing "sudo -i" without quotes and enter your pass when prompted. It is recommended that you '''reboot''' after any of these solutions. /usr/pluto/bin/RebootWithAVWizard.sh is probably best for testing after applying solutions.<br />
<br />
<br />
==Add Intel Advanced Support==<br />
apt-add-repository ppa:kernel-ppa/ppa<br />
apt-add-repository ppa:glasen/intel-driver<br />
# For additional performance issues, the following may help<br />
# apt-add-repository ppa:f-hackenberger/x220-intel-mesa<br />
apt-get update<br />
<br />
<br />
==Add nVidia Current Driver Support==<br />
With the 304+ nvidia driver we recommend pulling down alsa .25 at the same time as prescribed here.<br />
<br />
/usr/pluto/bin/Stop_X.sh<br />
add-apt-repository ppa:ubuntu-x-swat/x-updates<br />
apt-get update<br />
apt-get install -y nvidia-current<br />
<br />
<br />
==Add ATI Catalyst Support==<br />
/usr/pluto/bin/Stop_X.sh<br />
wget -P /tmp http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-12.10-x86.x86_64.zip<br />
apt-get install unzip<br />
unzip /tmp/amd-driver-installer-catalyst-12.10-x86.x86_64.zip ~/<br />
sh ~/amd-driver-installer-catalyst-12.10-x86.x86_64.run<br />
Then follow the instructions.<br />
<br />
<br />
==Add ALSA Backport .24 Support==<br />
apt-get install -yf linux-backports-modules-alsa-$(uname -r)<br />
<br />
<br />
==Add ALSA .24 Support==<br />
add-apt-repository ppa:team-iquik/alsa<br />
apt-get update<br />
apt-get install -y alsa-base<br />
apt-get install -y alsa-utils<br />
<br />
<br />
==Speaker Test==<br />
'''<font color=red>NOTE: This command sequence requires the user set the cParam and dParam values</font>'''<br />
<br />
Where '''cParam'''=<your card #> and '''dParam'''=<your device #>. For the standard discovery need, these will be revealed by:<br />
aplay -l | grep -i hdmi<br />
nVidia GT chipsets reveal device numbers 3, 7, 8, and 9. Almost all of them are device 7. If you see the devices in aplay and you do not have audio, test each until you get signal.<br />
<br />
cParam=<br />
dParam=<br />
<br />
if [[[[ -n "$cParam" ]]]] && [[[[ -n "$dParam" ]]]]; then<br />
. /usr/pluto/bin/Utils.sh; if [[[[ "$AlternateSC" -ge "1" ]]]]; then <br />
speaker-test -c2 -l1 -t sine -Dplughw:${cParam},${dParam}<br />
else <br />
speaker-test -c2 -l1 -t sine -Dplughw:${cParam}<br />
fi<br />
else StatusMessage "You must set the variables for both cParam and dParam. They cannot equal null"<br />
fi<br />
<br />
<br />
==Upgrade Kernel to Natty==<br />
CurKernel="-generic"<br />
if uname -r | grep "pae"; then CurKernel="-generic-pae"; fi<br />
NewKernel="linux-image${CurKernel}-lts-backport-natty"<br />
NewHeaders="linux-headers${CurKernel}-lts-backport-natty"<br />
apt-get -yf install "$NewKernel"<br />
apt-get -yf install "$NewHeaders"<br />
apt-get update<br />
apt-get -yf dist-upgrade<br />
<br />
<br />
==Upgrade Kernel to Latest Oneiric==<br />
CurKernel="-generic"<br />
if uname -r | grep "pae"; then CurKernel="-generic-pae"; fi<br />
NewKernel="linux-image-3.0.0-26${CurKernel}"<br />
NewHeaders="linux-headers-3.0.0-26${CurKernel}"<br />
apt-get -yf install "$NewKernel"<br />
apt-get -yf install "$NewHeaders"<br />
apt-get update<br />
apt-get -yf dist-upgrade</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Developer_Goals&diff=31288Developer Goals2012-05-31T19:36:38Z<p>Davegravy: /* golgoj4 */</p>
<hr />
<div>This page serves as a summary developers and their of current short or midterm development goals, and is for information's sake ONLY. It is not intended to serve as any sort of commitment by any developer, and there's no ETA attached to any goal. The goals are ordered as per the approximate priority given to them by each developer. <br><br />
<br />
=foxi=<br />
* Asterisk 1.8<br />
* IPv6 support<br />
<br />
=golgoj4=<br />
* QML-based orbiter (qOrbiter) both for mobile devices (especially android) and media directors<br />
* Background mobile device services to interface with LMCE automation<br />
<br />
=hari=<br />
* Zwave feature additions<br />
<br />
=l3mce=<br />
* Streamlined DVD install process<br />
* Improvements to video and audio card detection and configuration<br />
* Move button debugging<br />
* Qorbiter development support<br />
<br />
=merkur2k=<br />
* Qorbiter testing<br />
<br />
=posde=<br />
* iOrbiter (Orbiter for iOS)<br />
<br />
=tshack=<br />
* Refactoring work on game player</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Developer_Goals&diff=31287Developer Goals2012-05-31T19:36:02Z<p>Davegravy: /* l3mce */</p>
<hr />
<div>This page serves as a summary developers and their of current short or midterm development goals, and is for information's sake ONLY. It is not intended to serve as any sort of commitment by any developer, and there's no ETA attached to any goal. The goals are ordered as per the approximate priority given to them by each developer. <br><br />
<br />
=foxi=<br />
* Asterisk 1.8<br />
* IPv6 support<br />
<br />
=golgoj4=<br />
* QML-based orbiter both for mobile devices (android) and media directors<br />
* Background mobile device services to interface with LMCE automation<br />
<br />
=hari=<br />
* Zwave feature additions<br />
<br />
=l3mce=<br />
* Streamlined DVD install process<br />
* Improvements to video and audio card detection and configuration<br />
* Move button debugging<br />
* Qorbiter development support<br />
<br />
=merkur2k=<br />
* Qorbiter testing<br />
<br />
=posde=<br />
* iOrbiter (Orbiter for iOS)<br />
<br />
=tshack=<br />
* Refactoring work on game player</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Developer_Goals&diff=31286Developer Goals2012-05-31T19:35:15Z<p>Davegravy: /* l3mce */</p>
<hr />
<div>This page serves as a summary developers and their of current short or midterm development goals, and is for information's sake ONLY. It is not intended to serve as any sort of commitment by any developer, and there's no ETA attached to any goal. The goals are ordered as per the approximate priority given to them by each developer. <br><br />
<br />
=foxi=<br />
* Asterisk 1.8<br />
* IPv6 support<br />
<br />
=golgoj4=<br />
* QML-based orbiter both for mobile devices (android) and media directors<br />
* Background mobile device services to interface with LMCE automation<br />
<br />
=hari=<br />
* Zwave feature additions<br />
<br />
=l3mce=<br />
* Streamlined DVD install process<br />
* Improvements to video and audio card detection and configuration<br />
* Move button debugging<br />
<br />
=merkur2k=<br />
* Qorbiter testing<br />
<br />
=posde=<br />
* iOrbiter (Orbiter for iOS)<br />
<br />
=tshack=<br />
* Refactoring work on game player</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Developer_Goals&diff=31285Developer Goals2012-05-31T19:23:58Z<p>Davegravy: </p>
<hr />
<div>This page serves as a summary developers and their of current short or midterm development goals, and is for information's sake ONLY. It is not intended to serve as any sort of commitment by any developer, and there's no ETA attached to any goal. The goals are ordered as per the approximate priority given to them by each developer. <br><br />
<br />
=foxi=<br />
* Asterisk 1.8<br />
* IPv6 support<br />
<br />
=golgoj4=<br />
* QML-based orbiter both for mobile devices (android) and media directors<br />
* Background mobile device services to interface with LMCE automation<br />
<br />
=hari=<br />
* Zwave feature additions<br />
<br />
=l3mce=<br />
* Streamlined install process<br />
* Video card support beyond NVIDIA<br />
* Move button debugging<br />
<br />
=merkur2k=<br />
* Qorbiter testing<br />
<br />
=posde=<br />
* iOrbiter (Orbiter for iOS)<br />
<br />
=tshack=<br />
* Refactoring work on game player</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Developer_Goals&diff=31284Developer Goals2012-05-31T19:22:18Z<p>Davegravy: Created page with "This page serves as a summary developers and their of current short or midterm development goals, and is for information's sake ONLY. It is not intended to serve as any sort of c..."</p>
<hr />
<div>This page serves as a summary developers and their of current short or midterm development goals, and is for information's sake ONLY. It is not intended to serve as any sort of commitment by any developer, and there's no ETA attached to any goal. The goals are ordered as per the approximate priority given to them by each developer. <br><br />
<br />
=foxi=<br />
* Asterisk 1.8<br />
* IPv6 support<br />
<br />
=golgoj4=<br />
* QML-based orbiter both for mobile devices (android) and media directors<br />
* Background mobile device services to interface with LMCE automation<br />
<br />
=hari=<br />
* Zwave feature additions<br />
<br />
=l3mce=<br />
* Streamlined install process<br />
* Video card support beyond NVIDIA<br />
<br />
=merkur2k=<br />
* Qorbiter testing<br />
<br />
=posde=<br />
* iOrbiter (Orbiter for iOS)<br />
<br />
=tshack=<br />
* Refactoring work on game player</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Custom_Display_Resolutions&diff=31140Custom Display Resolutions2012-05-25T15:14:10Z<p>Davegravy: typo fix</p>
<hr />
<div>{| align="right"<br />
| __TOC__<br />
|}<br />
[[Category:Documentation]]<br />
[[category: AV Wizard]]<br />
[[Category:Tutorials]]<br />
If you have a display designed for use with a computer rather than as a regular TV, such as a plasma display, it is possible that the native resolution of the display is not one of the options presented by the [[AVWizard]]. In this case, with a small amount of tweaking it is possible to get the media director to drive the display at its native resolution, which will give you optimum picture quality.<br />
<br />
==Enable EDID==<br />
<br />
By default, LinuxMCE disables EDID - please see the [[EDID]] page for the details. However in this case you are probably better off re-enabling it. This should be done by editing <code>/usr/pluto/templates/xorg.conf.in</code>, which is the template from which the [[AVWizard]] automatically creates new Xorg configurations. You will find a line in this file like:<br />
<br />
Option "UseEDID" "false"<br />
<br />
Simply change <code>false</code> to <code>true</code> and save the file. Now we need to regenerate the Xorg config, but first we need to ensure that the right resolution is visible in the [[AVWizard]].<br />
<br />
==Adding new resolutions to the A/V Wizard==<br />
<br />
The resolutions visible in the wizard are set in the file <code>/usr/pluto/share/Resolutions.conf</code>. The resolution you need may well already be in there, but with visibility disabled. For instance, 1360x768 is already in there, and only requires the visibility flag to be toggled to make it appear in the wizard.<br />
<br />
If your required resolution is not in there, copy a block from one of the other resolutions and modify it accordingly.<br />
<br />
=== Resolutions.conf ===<br />
The Resolutions.conf file is parsed using the libconfuse library. libconfuse provides means of creating structured, yet simple, configuration files. This particular file is composed by entries like this:<br />
<br />
resolution<br />
{<br />
name = "640x480" #(1)<br />
width = 640 #(2)<br />
height = 480 #(2)<br />
aspect_ratio = "4:3" #(3)<br />
modeline #(4)<br />
{<br />
refresh = 60 #(4.1)<br />
builtin = true #(4.2)<br />
x11 = "" #(4.3)<br />
workaround #(4.4)<br />
{<br />
driver = {"nvidia"}<br />
x11 = "25.18 640 656 752 800 480 490 492 525"<br />
}<br />
}<br />
modeline<br />
{<br />
refresh = 75<br />
builtin = true<br />
}<br />
visible = true #(5)<br />
}<br />
<br />
==== (1) The "name" field ====<br />
This field is used as the name of the resolution when it is displayed by the A/V Wizard, and when retrieving ModeLines with <code>/usr/pluto/bin/X-GetModeline</code><br />
==== (2) The "width" and "height" fields ====<br />
These fields give the dimensions for the screen for the specified resolution. A resolution can have any name (even "WagaWaga" could be used, if meaningful to someone), and these values would then define the dimensions in pixels for that resolution.<br />
==== (3) The "aspect_ratio" field ====<br />
This field is for display purposes alone. It is displayed by the A/V Wizard next to the resolution name.<br />
==== (4) The "modeline" section ====<br />
This section is optional. It can be skipped. In that case, a modeline will be generated by xtiming.pl.<br />
<br />
You can have multiple modeline sections in a resolution block.<br />
<br />
* (4.1) The "refresh" selector<br />
If you include a modeline section, you must specify the "refresh" field. This field specifies to which refresh rate of the current resolution does the modeline apply.<br />
<br />
* (4.2) The "builtin" directive<br />
When set to "true", this says that the X server has a built-in modeline for this resolution and refresh rate combination and no modeline should be generated<br />
<br />
* (4.3) The "x11" field<br />
This field contains the modeline for this resolution and refresh rate combination, minus the modeline name, i.e. starting from the dot clock value.<br />
<br />
If the mode is built-in, the x11 directive is ignored. If the mode is not built-in, and x11 is empty, then xtiming.pl is used to generate a modeline.<br />
<br />
* (4.4) The "workaround" sub-section<br />
This section is optional. This section is used for cases when it is known that the general settings described in the section are buggy for certain display drivers.<br />
<br />
If you include this section, you need to specify the "driver" selector. The "driver" selector is a list of the following form: <code>{"driver1","driver2",...}</code><br />
<br />
This subsection can have the "x11" and "builtin" fields, with the same meaning and syntax as described above.<br />
<br />
==== (5) The "visible" directive ====<br />
This directive is used by A/V Wizard to decide if to display the resolution in the resolutions box or not.<br />
<br />
=== Caveat ===<br />
'''Furthermore''', unfortunately these resolutions are also hardcoded in <code>/usr/pluto/bin/AVWizard-Common.sh</code> - look for the line starting <code>Resolutions_HDTV</code> and add your custom resolution to the shell array. This is arguably a bug where the code does not gracefully handle resolutions which are listed in <code>/usr/pluto/share/Resolutions.conf</code> but not listed in <code>/usr/pluto/bin/AVWizard-Common.sh</code>.<br />
<br />
=== Orbiter size ===<br />
When you add a resolution, you may also want to add an Orbiter size to match it.<br />
<br />
The Orbiter sizes are kept in the '''Size''' table. This is a good SQL statement to add a size:<br />
INSERT INTO Size SET Description='<b>Size Name</b>', Width=<b>Width</b>, Height=<b>Height</b>, ScaleX=<b>ScaleX*</b>, ScaleY=<b>ScaleY*</b>, ScaleMenuBg='S', ScaleOtherGraphics='F';<br />
<br />
I don't know what ScaleMenuBg and ScaleOtherGraphics mean, but except for the Nokia 770 size, all the other entries have them like that.<br />
<br />
==== ScaleX and ScaleY ====<br />
You can't set ScaleX and ScaleY just to any values. The end result depends greatly on these. If you get them wrong, the size of your Orbiter will be incorrect (and OrbiterGen will die if you set any of them to 0).<br />
<br />
Here's how to compute the right values:<br />
* For 4:3 resolutions<br />
ScaleX = int(Width / 2.84444444444)<br />
ScaleY = int(Height / 1.6)<br />
* For 16:9 resolutions<br />
ScaleX = int(Width / 2.13333333333)<br />
ScaleY = int(Height / 1.6)<br />
<br />
These formulas are using the value ratios determined from the existing sizes.<br />
<br />
Another way is to use this size for reference: 2128x1596. This is the "base" resolution of UI1. The idea is that you want to scale this down to your resolution: XxY. In this case, the formulas are:<br />
<br />
ScaleX = round(X/2128*1000)<br />
ScaleY = round(Y/1596*1000)<br />
<br />
UI2 seems to override these values in OrbiterGen.sh. A comment in OrbiterGen.cpp says: <i>UI2 is always 16:9 and needs to be edge-to-edge, so we will ignore the normal scaling rules and always scale the full image</i><br />
<br />
'''Fix me''': Determine a general formula for general aspect ratios.<br />
<br />
==Run the A/V Wizard==<br />
Running the A/V Wizard will regenerate the correct Xorg configuration<br />
<br />
[[AVWizard Step by Step|Proceed through the wizard]], selecting the resolution which you have just made appear, and make sure the display is happy with the setting. If not, switch to the tty1 virtual console via Control-Alt-F1, log in, and check the most recently modified Xorg logfile written by the wizard's test (this is probably <code>/var/log/Xorg.1.log</code>) to find out why it didn't work.<br />
<br />
==Prevent LinuxMCE from changing the Xorg config==<br />
<br />
This is a bit of an ugly hack, and if the above is done correctly I'm not sure if it's even needed. Nevertheless, if you want to get really creative and write your own xorg.conf, this is the way to protect it from being overwritten:<br />
<br />
Edit <code>/usr/pluto/bin/Xconfigure.sh</code> and add the following lines immediately below the <code>#!/bin/bash</code>:<br />
<br />
echo "$0 neutered to preserve custom xorg.conf"<br />
exit 0<br />
<br />
<br />
==Diskless Media Director==<br />
<br />
Chroot into the MD and perform the steps mentioned above to add the custom resolution.<br />
<br />
To chroot into the MD, first make sure it is turned off<br />
<br />
From the web admin, determine the ID of the MD you wish to modify.<br />
<br />
cd /usr/pluto/diskless/<br />
chroot <mediadirector-id><br />
<br />
Then perform the above steps.<br />
<br />
*This worked for me, if someone could verify and remove this remark -Pnuts</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Android_Orbiter&diff=29480Android Orbiter2012-02-11T18:26:22Z<p>Davegravy: </p>
<hr />
<div>=LinuxMCE Orbiter for Android=<br />
This wiki page serves 2 purposes: To serve as an intermediate install guide for the Android LinuxMCE Orbiter, and to serve as a point of reference for future developers.<br />
<br />
==History==<br />
The Android orbiter is the result of a very tricky process. We utilize the LinuxMCE libraries, qt libraries, and wrap them inside java for execution on the Android device. Besides using vanilla Qt Creator, we also utilize Neccesitas, a cross platform compiler that takes the Native c++ and wraps it for executing inside the Android JNI <br />
<br />
=Installation=<br />
Please note, you will need 50mb of storage space on the devices internal storage. NOT the sd card. You will also need to install via wifi!!<br />
*Download the testing apk: http://lasmarthomes.com/QOrbiter-release.apk<br />
*Install the .apk<br />
*When it is finished, it will ask you for to download Ministro II, which in turns might need additional libs which are automatically downloaded.<br />
. Do this and let it finish.<br />
QOrbiter is now installed!<br />
<br />
==Configuration==<br />
You will need to prepare for the addition of the device to your system before it can be used by following these steps.<br />
*Create a new QOrbiter device as a child of the core. MAKE SURE to set the default user and location. '''Make a note of the device number'''<br />
*Quick Reload the router when asked. <br />
*Generate the orbiter config by visiting this page http://<you-core-address>/lmce-admin/qOrbiterGenerator.php?d=<the-device-number><br />
<br />
Now you will need to decide on a skin. Eventually, this will be a cleaner process. For the moment, it isnt :)<br />
All skins live on the core and will be accessible from http://<your-route-ip>/lmce-admin/skins The following instructions are for the core machine.<br />
<br />
All skins need a skins directory:<br />
mkdir -p /var/www/lmce-admin/skins<br />
===Phones===<br />
You will need to checkout the skin using subversion. <br />
svn co http://svn.linuxmce.org/svn/branches/LinuxMCE-1004/src/qOrbiter/qOrbiter_src/qml /var/www/lmce-admin/skins<br />
This will download the skins to the proper location.<br />
<br />
===Tablets===<br />
You will need to download the skin from its current home, and unzip it into the proper directory.<br />
wget http://www.lasmarthomes.com/tabletskin.zip<br />
unzip -d /var/www/lmce-admin/skins/android/phone/ tabletskin.zip<br />
<br />
Now your tablet skin is installed.<br />
<br />
==Running the device==<br />
*Assuming the previous steps were completed, you can now connect.<br />
*The default ip it connects to is 192.168.80.1<br />
*Enter the device number you previously made note of for the device number<br />
*If your core address is not standard, it will hang. you can kill the device and edit the config.xml at the location listed below.<br />
<br />
The configuration file is located on the SDCard under /LinuxMCE<br />
<br />
==Remote Access==<br />
<br />
In order to use qOrbiter from outside your internal LMCE network, you need to:<br />
*Open ports 2757 & 3450 on your firewall via webadmin<br />
*Change the host line in LinuxMCE/config.xml on your Android device to your CORE's external IP address.</div>Davegravyhttp://wiki.linuxmce.org/index.php?title=Community&diff=19539Community2009-06-30T17:26:53Z<p>Davegravy: </p>
<hr />
<div>Right, having looked at the detail in this post [http://forum.linuxmce.org/index.php?topic=8411.0] i felt its time to see what we are made of as a community, please add your details.<br />
<br />
<br />
GUIDE: copy'n'paste the following lines then append them into the table below (prior to the final line that contains '|}'). This formatting should make it easier for the 'big 5' to work out who can contribute what...<br />
<pre><br />
| Your username<br />
| Your relevant expertise/experience <br />
| Your other experience/expertise<br />
| Your approx time available for the project<br />
| Your time zone or location<br />
| Your particular interest area (if any)<br />
|-<br />
</pre><br />
<br />
<br />
<br />
{| border="1"<br />
!Username<br />
!Relevant expertise/experience<br />
!Other Experience/Expertise<br />
!Time available for the project<br />
!Time zone or location<br />
!Particular Interest Area (If any)<br />
|-<br />
| Geekyhawkes<br />
| advanced newbie<br />
| use to some C+/linux/ubuntu/ html / xml / flash<br />
| few evenings a week<br />
| UK GMT<br />
| User documentation, newbie guides, website design , wiki topics and guides. Line by line intros to get 810 up and running regardless of user experiance.<br />
|-<br />
| tmoore<br />
| advanced newbie<br />
| 14 yrs software product management, IT management consulting, marketing, network & systems management, UNIX admin<br />
| about 3 hrs a week on average<br />
| GMT-7<br />
| Product strategy, team management,(non-technical) marketing & communications<br />
|-<br />
| qball4<br />
| regular user<br />
| HADesigner, graphic design, hardware a/v distribution systems<br />
| average 20-40 hrs/wk available<br />
| US CST<br />
| User Interface, new orbiter platforms<br />
|-<br />
| Fastie81<br />
| advanced newbie<br />
| work with linux/Red Hat/ubuntu day to day / Project Manager / Systems Administrator / Quick Learner<br />
| My work load goes up and down so would have few days one week and none another<br />
| GMT +12 (NZ)<br />
| User Documentation, guides, wiki guides. I would like to learn some coding. Adding Hardware support ,Devices Templates.<br />
|-<br />
| Techstyle<br />
| Advanced Newbie<br />
| System builder, Linux newbie, some Wiki writing experience / PMP (Project Management Professional), MBA, Mechanical Engineer, Entrepreneur<br />
| 1hr per day<br />
| US central (Milwaukee, WI)<br />
| Anything structured<br />
|-<br />
| nite_man<br />
| regular user<br />
| Integrator, consultant, GSD, Ruby, Maemo Orbiter / More then 10 years of software development - Perl, PHP, Linux sysadmin<br />
| 2-4 hours per day<br />
| UTC+2:00 Nicosia, Cyprus<br />
| Admin site, Maemo Orbiter, posting news, blogging, Russian translation<br />
|-<br />
| Daballiemo<br />
| regular user<br />
| Worked my way through Linux/Ubuntu/Fedora mainly on virtualization / Working within MOD and about 15 years of exp. with "paper" documentation<br />
| About 3-6 hours a week<br />
| GMT +1, Amsterdam<br />
| Virtualization and interfacing (webui, remote, keyboard, touch aso)<br />
|-<br />
| SteveC<br />
| LMCE Newbie but keen to get cracking.<br />
| Electronics/Software Engr, C/C++ for 15years.<br />
| Approx 5 hours/week<br />
| UTC+10:00 Brisbane, Australia<br />
| Main interests relate to external hardware interfaces eg. Clipsal CBUS lighting, Caddx/Networx Alarm system.<br />
|-<br />
| Lemming86_au<br />
| Advanced Newbie<br />
| IT Consultant, Network Engineer, Asterisk Admin (No programming experience, yet)<br />
| 3-5 hours/Week<br />
| UTC+9:30 Adelaide, Australia<br />
| Asterisk<br />
|-<br />
| castlec<br />
| LMCE Noob. Linux regular user/noob<br />
| Java Dev, C++ trained (University).<br />
| 3-5 hours/Week<br />
| UTC-5 Ohio, USA<br />
| <br />
|-<br />
| ZuG<br />
| Regular User<br />
| Linux, PHP and a bit of C. Very familiar with Asterisk and OpenVPN<br />
| 3-5 hours/Week<br />
| GMT Cardiff, United Kingdom<br />
| OpenVPN development<br />
|-<br />
| ccoudsi<br />
| Regular user <br />
| 15+ years embedded hardware design, 8+ years engineering manager, Assembly, C, Perl, Ruby (newbie)<br />
| 5-8 hours a week<br />
| UTC-08 PT<br />
| Security Panels<br />
|-<br />
| colinjones<br />
| Regular User<br />
| Bit of bash, some simple coding, learning C++, familiar with the DCE system<br />
| ~15-20 hours/Week<br />
| UTC+10, Sydney, Australia<br />
| LMCE!<br />
|-<br />
| sp00nhead<br />
| User since Pluto days<br />
| IT support & Training, want to be python coder, solid knowledge of Linux systems<br />
| ~5 hours/week unless i get hooked again.<br />
| GMT Crewe, UK<br />
| take the LMCE framework and make it as popular as xbmc/boxee!<br />
|-<br />
| darrenmason<br />
| User/Developer since Pluto days, familiar with the codebase and architecture<br />
| IT Consultant with Software engineering background specialising in Integration. Have developed in C++/Java and various other languages<br />
| Varies depending upon family but can/will find time if interest level is there<br />
| UTC+10, Sydney, Australia<br />
| New devices, Microcontroller integration, Constrained resources Media Directors, DLNP <br />
|-<br />
| patricez<br />
| Advanced Newbie <br />
| Tech addict. Dev Team Manager, have experience in C,SQL,Xen,vmware,citrix,Asterisk,network...<br />
| Varies depending my job(s) and family but could be 5-10hrs/week<br />
| UTC-5, Quebec, Canada<br />
| Home Automation, VOIP, Virtualization, Networking <br />
|-<br />
| PeteK<br />
| User Since Pluto, some development work submitted to Pluto (early Insteon) <br />
| Avionics Engineer, Hardware/Software C++ experience<br />
| Shooting for 5-10 hrs/week<br />
| UTC-8/-7 Mojave, CA, USA<br />
| Automation Interfaces<br />
|-<br />
| davegravy<br />
| LMCE Newbie<br />
| Electrical/Acoustical Engineer, Project Manager. Java, Assembly, some C++ learned in university.<br />
| 5-10hrs/week hopefully<br />
| UTC-5, Toronto, Canada<br />
| Home Automation, VOIP, Documentation<br />
|}</div>Davegravy