Kodi Community Forum
Linux HOW-TO install XBMC for Linux on Asrock ION 330 with full Ubuntu Desktop - Printable Version

+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: Linux HOW-TO install XBMC for Linux on Asrock ION 330 with full Ubuntu Desktop (/showthread.php?tid=54705)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20


- BLKMGK - 2009-09-07

Install was pretty much a standard Ubuntu install, XBMC from SVN, updated ALSA. I had issues with libcurl and a corrupted database which I've seen twice now but now gotten around. Pretty straightforward install, Pulseaudio wasn't removed. Very strange I'll admit. Honestly I wish there was a standard image hosted somewhere for this build. If mine was a little less odd I'd consider using DD or Acronis and putting it somewhere for others. <sigh>

P.S. Yes, I'm on the latest BIOS. I'll be flashing again to another copy with the nicer boot logo soon!


- vikjon0 - 2009-09-08

Yes, very strange.
You could try to remove pulse audio and you could also test to temporaly rename guisettings.xml and let the system generate a new...or why not the whole .xbmc to get a totally fresh setup.
What I do not understand is that you have no sound in the desktop..


- stokedfish - 2009-09-08

Great thread, thanks guys. Everything up and running!


- stokedfish - 2009-09-10

Not sure this helps anyone, but here's a quick'n'dirty version of the commands you need to run to get most things working:

Quote:- edit /etc/apt/sources.list:

Code:
#deb cdrom:[Ubuntu 9.04 _Jaunty Jackalope_ - Release i386 (20090420.1)]/ jaunty main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.

deb http://ch.archive.ubuntu.com/ubuntu/ jaunty main restricted
deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://ch.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted
deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://ch.archive.ubuntu.com/ubuntu/ jaunty universe
deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty universe
deb http://ch.archive.ubuntu.com/ubuntu/ jaunty-updates universe
deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://ch.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty multiverse
deb http://ch.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse

## Uncomment the following two lines to add software from the 'backports'
## repository.
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
# deb http://ch.archive.ubuntu.com/ubuntu/ jaunty-backports main restricted universe multiverse
# deb-src http://ch.archive.ubuntu.com/ubuntu/ jaunty-backports main restricted universe multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
# deb http://archive.canonical.com/ubuntu jaunty partner
# deb-src http://archive.canonical.com/ubuntu jaunty partner

deb http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb-src http://security.ubuntu.com/ubuntu jaunty-security main restricted
deb http://security.ubuntu.com/ubuntu jaunty-security universe
deb-src http://security.ubuntu.com/ubuntu jaunty-security universe
deb http://security.ubuntu.com/ubuntu jaunty-security multiverse
deb-src http://security.ubuntu.com/ubuntu jaunty-security multiverse

## Nvidia Drivers
deb http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu jaunty main
deb-src http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu jaunty main

## XBMC Stable
deb http://ppa.launchpad.net/xbmc-addons/ppa/ubuntu jaunty main
deb http://ppa.launchpad.net/team-xbmc/jaunty-ppa/ubuntu jaunty main

## XBMC Unstable
# deb http://ppa.launchpad.net/team-xbmc-svn/ppa/ubuntu jaunty main

- sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 318C7509 9317790E
- sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com 318C7509 64234534
- sudo apt-key adv --recv-keys --keyserver keyserver.ubuntu.com CEC06767
- sudo apt-get update && sudo apt-get dist-upgrade
- sudo reboot
- sudo apt-get update
- sudo apt-get install xbmc xbmc-standalone
- sudo apt-get install xbmc-eventclients-*
- sudo apt-get install xbmc-scripts-*
- sudo apt-get install linux-headers-generic nvidia-glx-185
- sudo nvidia-xconfig -s --no-logo --force-generate
- sudo sed -i '40i\ Option "HWCursor" "False"' /etc/X11/xorg.conf
- sudo sed -i '50i\ Option "DynamicTwinView" "False"' /etc/X11/xorg.conf
- sudo reboot
- sudo alsamixer > unmute chans
- sudo alsactl store 0

HAVE FUN! Big Grin


- funkigreendog - 2009-09-12

Sorry for the noob question, but I've never used Linux before and will be installing later this week....

Should any particular file system type be used when partitioning the drive?


- vikjon0 - 2009-09-12

Quote:Should any particular file system type be used when partitioning the drive?
I am not an expert but default in the ubuntu installer is ext3. I guess ext3 or ext2 is the way to go.


- funkigreendog - 2009-09-12

Thanks for the quick reply.

Hopefully one last stupid question. Is there any reason everything is done over ssh using the telnet session rather than on the machine itself?


- BLKMGK - 2009-09-14

vikjon0 Wrote:Yes, very strange.
You could try to remove pulse audio and you could also test to temporaly rename guisettings.xml and let the system generate a new...or why not the whole .xbmc to get a totally fresh setup.
What I do not understand is that you have no sound in the desktop..

Well, a brand new XBMC install didn't do it. However copying over my previous XBMC data files from another computer that had a running XBMC got me sound in movies\music. An .asoundrc posted by Althekiller has got me nav sounds. VERY strange for sure but my system IS finally working right!


- bbaldino - 2009-09-14

I noticed this in the advanced settings section of the wiki:

Quote: <bginfoloadermaxthreads>

Control the number of threads in the background info loader thread pool (thumb generagor, flagging, etc). Useful for tuning platforms that are low on CPU, like Xbox and Intel Atom based systems.

PHP Code:
<bginfoloadermaxthreads>5</bginfoloadermaxthreads

Has anyone messed with this and seen any improvements?


- fidoboy - 2009-09-15

kingmos Wrote:i got crossfade over hdmi working while still having the ability to direct output digital streams as DTS or Dolby Digital, maybe this is usefull for one of you Wink

this is my .asoundrc, i set up my system with the guide from the first page, so this should work for all of you ion 330 users.

Code:
# ~/.asoundrc or /etc/asound.conf
# ALSA configuration file

##### USAGE #####
# Save this file as "~/.asoundrc" (for user-specific sound configuration) or
# "/etc/asound.conf" (for system-wide sound configuration) and specify ALSA
# device names ad described in the next section.


##### DEVICE NAMES #####
# This configuration file defines four devices for use by the user.  Those
# devices are "analog", "mixed-analog", "digital", and "mixed-digital".  The
# user may also re-define "default" to be identical to one of the above-named
# devices (i.e. to send all sound output to the digital output unless otherwise
# specified).  Use the device names as described below:
#  - "analog" outputs to the analog output directly and (at least on software
#  sound cards) blocks other audio output.  After playback completes, "queued"
#  sounds are output in sequence.
#  - "mixed-analog" mixes audio output from multiple programs into the analog
#  output (so you can hear beeps, alerts, and other noises while playing back
#  an audio stream).
#  - "digital" outputs to the digital output directly.  Since most (all?)
#  digital outputs expect 48kHz PCM audio, this may not work for some playback
#  (i.e. CD's--which are 44.1kHz PCM audio--or 32kHz audio streams from TV
#  recordings, etc.).
#  - "mixed-digital"

# All other devices created within this file are used only by the configuration
# file itself and should /not/ be used directly.  In other words, do not use
# the devices "analog-hw", "dmix-analog", "digital-hw", or "dmix-digital".


##### IMPORTANT #####
# To make this ALSA configuration file work with your sound card, you will need
# to define the appropriate card and device information for the "analog-hw" and
# "digital-hw" devices below.  You can find the card and device information
# using "aplay -l".


##### Configuration File #####

# Override the default output used by ALSA.  If you do not override the
# default, your default device is identical to the (unmixed) "analog" device
# shown below.  If you prefer mixed and/or digital output, uncomment the
# appropriate four lines below (only one slave.pcm line).
#
# Note, also, that as of ALSA 1.0.9, "software" sound cards have been modified
# such that their default "default" device is identical to the "mixed-analog"
# device.  Whether using an ALSA version before or after 1.0.9, it does no harm
# and has no affect on performance to redefine the device (even if the
# redefinition does not change anything).  Also, by using this ALSA
# configuration file, you once again have access to unmixed analog output using
# the "analog" device.
pcm.!default {
  type plug
## Uncomment the following to use (unmixed) "analog" by default
#  slave.pcm "analog-hw"
## Uncomment the following to use "mixed-analog" by default
#  slave.pcm "dmix-analog"
## Uncomment the following to use (unmixed) "digital" by default
#  slave.pcm "digital-hw"
## Uncomment the following to use "mixed-digital" by default
  slave.pcm "dmix-digital"
}

# Control device (mixer, etc.) for the card
ctl.!default {
  type hw
  card 0
}

# Alias for (converted) analog output on the card
# - This is identical to the device named "default"--which always exists and
# refers to hw:0,0 (unless overridden)
# - Therefore, we can specify "hw:0,0", "default", or "analog" to access analog
# output on the card
# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine
# "default" to do mixing, meaning this device is different from "default" and
# allows playback while blocking other sound sources (until playback
# completes).
pcm.analog {
  type plug
  slave.pcm "analog-hw"
}

# Control device (mixer, etc.) for the card
ctl.analog {
  type hw
  card 0
}

# Alias for (converted) mixed analog output on the card
# - This will accept audio input--regardless of rate--and convert to the rate
# required for the dmix plugin (in this case 48000Hz)
# - Note that as of ALSA 1.0.9, "software" sound card definitions redefine
# "default" to do mixing, meaning this device is identical to "default" for
# "software" sound cards.
pcm.mixed-analog {
  type plug
  slave.pcm "dmix-analog"
}

# Control device (mixer, etc.) for the card
ctl.mixed-analog {
  type hw
  card 0
}

# Alias for (converted) digital (S/PDIF) output on the card
# - This will accept audio input--regardless of rate--and convert to the rate
# required for the S/PDIF hardware (in this case 48000Hz)
pcm.digital {
  type plug
  slave.pcm "digital-hw"
}

# Control device (mixer, etc.) for the card
ctl.digital {
  type hw
  card 0
}

# Alias for mixed (converted) digital (S/PDIF) output on the card
#  - This will accept audio input--regardless of rate--and convert to the rate
#  required for the S/PDIF hardware (in this case 48000Hz)
pcm.mixed-digital {
  type plug
  slave.pcm "dmix-digital"
}

# Control device (mixer, etc.) for the card
ctl.mixed-digital {
  type hw
  card 0
}

# The following devices are not useful by themselves.  They require specific
# rates, channels, and formats.  Therefore, you probably do not want to use
# them directly.  Instead use of of the devices defined above.

# Alias for analog output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.analog-hw {
  type hw
  card 0
  # The default value for device is 0, so no need to specify
#  - Uncomment one of the below or create a new "device N" line as appropriate
#    for your sound card or
#  device 1
#  device 4
}

# Control device (mixer, etc.) for the card
ctl.analog-hw {
  type hw
  card 0
}

# Alias for digital (S/PDIF) output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.digital-hw {
  type hw
  card 0
[b]  device 3[/b]
#  - Comment out "device 1" above and uncomment one of the below or create a
#    new "device N" line as appropriate for your sound card or
#  device 2
#  device 4
}

# Control device (mixer, etc.) for the card
ctl.digital-hw {
  type hw
  card 0
}

# Direct software mixing plugin for analog output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.dmix-analog {
  type dmix
  ipc_key 1234
  slave {
    pcm "analog-hw"
    period_time 0
    period_size 1024
    buffer_size 4096
    rate 48000
    }
}

# Control device (mixer, etc.) for the card
ctl.dmix-analog {
  type hw
  card 0
}

# Direct software mixing plugin for digital (S/PDIF) output on the card
# Do not use this directly--it requires specific rate, channels, and format
pcm.dmix-digital {
  type dmix
  ipc_key 1235
  slave {
    pcm "digital-hw"
    period_time 0
    period_size 2048
    buffer_size 32768
    rate 48000
    }
}

# Control device (mixer, etc.) for the card
ctl.dmix-digital {
  type hw
  card 0
}
change the bold code for spdif (in section pcm.digital-hw). should be device 2 i guess (haven't tested it though)

in xbmc you need to change toe following settings in the audio hardware section:

audio output device: mixed-digital
passthrough output device: digital

hope this is usefull!

Thanks kingmos, it's working fine, but i don't have sound when playing passtrough... i'm not sure why Huh. However 2.0 sounds (like mp3 music, etc) is playing fine...

any ideas?


- jimsmith - 2009-09-16

Hi, I am a total noob - would like to order the Asrock 330 with XMBC to replace my popcorn A-110 with 500gb HDD.

I wanted to check - can I mimic the NAS (Samba) function of the Popcorn Hour? I currently use it as a server for my SONOS. What would be the setup? Ubunto+XMBC? I am a total noob so any advice gratefully appreciated.

Also, I am a bit confused over IR remotes. With the correct setup for use as XMBC+NAS, do I just need a MCE compatible remote, or does it really have to be microsoft own brand? Ideally, I have a Harmony One that I would like to use.

Many thanks!


- grubia - 2009-09-16

jimsmith Wrote:Hi, I am a total noob - would like to order the Asrock 330 with XBMC to replace my popcorn A-110 with 500gb HDD.

I wanted to check - can I mimic the NAS (Samba) function of the Popcorn Hour? I currently use it as a server for my SONOS. What would be the setup? Ubunto+XBMC? I am a total noob so any advice gratefully appreciated.

Also, I am a bit confused over IR remotes. With the correct setup for use as XBMC+NAS, do I just need a MCE compatible remote, or does it really have to be microsoft own brand? Ideally, I have a Harmony One that I would like to use.

Many thanks!
Hi,
I'm using Asrock 330 with XBMC also as home server with samba,nfs,ssh,wins,ftp servers and also as a torrent downloader with web console. I'm using it as a replacement for TVIX 6500 and i must say that i'm more than satisfied with the results.
In order for you to use harmony remote you will need ir receiver and microsoft one is cheapest solution that i can find for USB IR receiver with media center remote. You can then program your harmony remote and use it with microsoft's receiver under linux.


- jimsmith - 2009-09-16

thanks for the reply - just to confirm - you are using a microsoft own brand MCE IR receiver? I ask because in the UK I am having trouble finding any at all - there are a few on ebay at crazy prices (£45), whereas generic microsoft MCE remotes/receivers from hong kong cost about £10...


- grubia - 2009-09-17

jimsmith Wrote:thanks for the reply - just to confirm - you are using a microsoft own brand MCE IR receiver? I ask because in the UK I am having trouble finding any at all - there are a few on ebay at crazy prices (£45), whereas generic microsoft MCE remotes/receivers from hong kong cost about £10...

I'm using one like this. I bought it for ~12 £. So if you wait a few days a cheaper one will appear on ebay.
Good luck.
P.S.
Buy "original" one like this as I bought one from HK first which broke in 2 days.


- pecinko - 2009-09-17

grubia Wrote:I'm using one like this. I bought it for ~12 £. So if you wait a few days a cheaper one will appear on ebay.
Good luck.
P.S.
Buy "original" one like this as I bought one from HK first which broke in 2 days.

I bought Genius remote and I am using its IR receiver with Logitech Harmony (Genius remote works, I wanted to control other devices as well). So no, it is does not have to be MS original. However, using MS clone IR receiver will probably save you a lot of trouble.

EDIT: http://www.geniusnet.com/geniusOnline/online.portal?_nfpb=true&productPortlet_actionOverride=%2Fportlets%2FproductArea%2Fcategory%2FqueryPro&_windowLabel=productPortlet&productPortletproductId=653067&_pageLabel=productPage&test=portlet-action