Need help installing XBMCbuntu on Acer Revo R3700 please
#16
(2012-04-07, 20:33)Plaguester Wrote:
(2012-04-07, 20:10)pumkinut Wrote: Try creating an /etc/asound.conf file with the following information:
Code:
pcm.!default {
   type plug
   slave {
       pcm "hw:1,3"
   }
}
So you do the following:
Have this page open.
SSH into your XBMC box.
Type "sudo nano /etc/asound.conf"
Copy and paste the code above.
Type CTRL+x and then "y" to save.
Reboot
Make sure audio output is set to HDMI, and that the devices are set to custom with "plughw:1,3" for both output device and passthrough device.

This is super hacky and you shouldn't need to do it in recent versions of Ubuntu. Those channels on the NVidia card that were muted (MM)? Turn them on. Also make sure your volume is up. Anything S/PDIF or PCM should be on.
It's not "super hacky", and it is needed more than you think. Look at all the audio threads, and then look at how many are solved by adding an asound.conf file under /etc. It's a pain, but in a lot of cases it's necessary. Things like this should be a thing of the past when Frodo hits the scene, assuming AE makes it in.
* pumkinut crosses fingers
Reply
#17
Quote:It's not "super hacky", and it is needed more than you think. Look at all the audio threads, and then look at how many are solved by adding an asound.conf file under /etc. It's a pain, but in a lot of cases it's necessary. Things like this should be a thing of the past when Frodo hits the scene, assuming AE makes it in.
* pumkinut crosses fingers

Yes, it is hacky. On a standalone Ubuntu system, this hasn't been needed since 9.04. I also did not say that it doesn't work for XBMC. But it doesn't work for all programs and browser plugins (I recall it not working for Flash in 9.04). While it's possible that XBMCbuntu is broken in this regard, I highly doubt it.

If the channels are all unmuted and the volume is up, all you should have to do is pick the correct device. If it *still* doesn't play, then try switching the Audio Output type to Analog or Digital (rather than HDMI) and choosing the output device again.

You should be able to get audio out of ALSA via "aplay -l", "alsamixer", and "speaker-test -D plughw:X,Y" without going through PulseAudio. XBMC and Ubuntu use PulseAudio to configure ALSA. You can check pulse by doing "cat /dev/urandom | pacat" (use ctrl-c to quit). If something isn't working you can check the pulse audio configuration from the command line like this:

Code:
$ pacmd list-sinks

# It's a lot of information, to save it to a file to upload to pastebin...
$ pacmd list-sinks > output.txt
HTPC 1 - Zotac ZBOX ID80U | 4GB RAM | 64GB SSD | Openelec | Confluence
HTPC 2 - Zotac ZBOX ID41U | 4GB RAM | 60GB SSD | Openelec | Confluence
Server - unRAID Server | 3 x 2TB WD Green HDD, 1TB WD Black HDD (Cache) | Sabnzbd | CouchPotato | Sickbeard
Reply
#18
Disable On board Audio through the bios then follow these instructions. Thats how i got audio to work. Make sure you unmute in alsamixer.
http://wiki.xbmc.org/index.php?title=HOW...controller

Also, regarding overscan. You can adjust overscan in xbmcbuntu from the NVidia Panel settings. (a slider you can change till you get it right)
Reply
#19
(2012-04-07, 23:19)Plaguester Wrote: On a standalone Ubuntu system, this hasn't been needed since 9.04.
Funny, I need an asound.conf file for my brand-spanking-new XBMCbuntu install on an Intel H67 chipset mini-ITX board using the Intel IGP and audio over HDMI. Without the asound.conf I either have to choose correct passthrough audio or menu sounds. With the asound.conf file, I get both.
Reply
#20
(2012-04-07, 20:10)pumkinut Wrote: Try creating an /etc/asound.conf file with the following information:
Code:
pcm.!default {
   type plug
   slave {
       pcm "hw:1,3"
   }
}
So you do the following:
Have this page open.
SSH into your XBMC box.
Type "sudo nano /etc/asound.conf"
Copy and paste the code above.
Type CTRL+x and then "y" to save.
Reboot
Make sure audio output is set to HDMI, and that the devices are set to custom with "plughw:1,3" for both output device and passthrough device.

Excellent! That has fixed it for me! Many thanks! Big Grin

Now...does anyone know where the setting is to take off the clicks and whooshes when I navigate around!
Damn! Spoke too soon! I have effects, but no audio. It's still getting the "failed to initialise audio" error.
Reply
#21
And here is the aplay -l results and the Alsamixer if that's any help;

Image

Image
Reply
#22
Good. Unmute all the channels in alsamixer. Then use the following until you get one that works:

Code:
$ speaker-test -D plughw:0,3

# also try 7, 8, and 9 in place of 3

(2012-04-08, 02:06)pumkinut Wrote:
(2012-04-07, 23:19)Plaguester Wrote: On a standalone Ubuntu system, this hasn't been needed since 9.04.
Funny, I need an asound.conf file for my brand-spanking-new XBMCbuntu install on an Intel H67 chipset mini-ITX board using the Intel IGP and audio over HDMI. Without the asound.conf I either have to choose correct passthrough audio or menu sounds. With the asound.conf file, I get both.

This thread concerns the NVidia ION chip (Acer Revo). I have no idea what the support level is for the Intel chipsets. I'd be interested to know if you had the same problem with a full Ubuntu install.
HTPC 1 - Zotac ZBOX ID80U | 4GB RAM | 64GB SSD | Openelec | Confluence
HTPC 2 - Zotac ZBOX ID41U | 4GB RAM | 60GB SSD | Openelec | Confluence
Server - unRAID Server | 3 x 2TB WD Green HDD, 1TB WD Black HDD (Cache) | Sabnzbd | CouchPotato | Sickbeard
Reply
#23
(2012-04-08, 19:17)Plaguester Wrote: Good. Unmute all the channels in alsamixer. Then use the following until you get one that works:

Code:
$ speaker-test -D plughw:0,3

# also try 7, 8, and 9 in place of 3

Ouch! I get a load of fuzz from speaker-test -D plughw:0,8, nothing from the others though!
Reply
#24
Still getting the audio failed error when I select HDA Nvidia hdmi 8 (ALSA ).

To clarify, my Audio Output settings are;
Audio output - HDMI
Speaker config 2.0
Boost on downmix - yes
DD (AC3) capable receiver - yes (also tried with no)
DTS - no
Device - HDA Nvidia - hdmi 8 (ALSA)
Passthrough - as above.

I have the onboard audio disabled in the BIOS (since which I've not had the effects noises either)
Reply
#25
Got it! It's not DD but I'm not so fussed as it's only going through the telly.

I've changed it to;

Audio output - Analog
Speaker config 2.0
Boost on downmix - yes
Device - Defaults (ALSA)

That'll do me for now. If I can get DD working it would be great for the future, but for now this is fine.

Thanks so much for the help on this guys! Very much appreciated! Smile

Now then.... are my NVidia graphics drivers up to date...?!
Reply
#26
Looks like this is my Nvidia driver.... are they up to date?

matthew@Revo:~$ dpkg -l | grep nvidia
ii nvidia-current 280.13-0ubuntu6 NVIDIA binary Xorg driver, kernel module and VDPAU library
ii nvidia-settings 280.13-0ubuntu2 Tool of configuring the NVIDIA graphics driver
matthew@Revo:~$
Reply
#27
Your older TV may not properly handle the DD or DTS signal sent from the PC when the output type is HDMI. However, anyone using the TV speakers for output won't be able to tell any difference in quality (XBMC will be doing the decoding rather than the TV). If you were to hook it up to a receiver, you should be able to switch the output type without issues.

Your NVidia drivers are up to date.
HTPC 1 - Zotac ZBOX ID80U | 4GB RAM | 64GB SSD | Openelec | Confluence
HTPC 2 - Zotac ZBOX ID41U | 4GB RAM | 60GB SSD | Openelec | Confluence
Server - unRAID Server | 3 x 2TB WD Green HDD, 1TB WD Black HDD (Cache) | Sabnzbd | CouchPotato | Sickbeard
Reply
#28
Ah, great, thanks for clarifying both of those! Wink
Reply
#29
Ah, another problem. It keeps dropping the LAN connection. When I'm in Windows it's fine so it's defaintely not the card or anything between the router and PC, but when I'm in Ubuntu it keeps going. I've gone into XBMCbuntu and when I'm in there it keeps flashing up with a message saying it's disconnected. Any ideas?
Reply
#30
(2012-04-08, 19:17)Plaguester Wrote: Good. Unmute all the channels in alsamixer. Then use the following until you get one that works:

Code:
$ speaker-test -D plughw:0,3

# also try 7, 8, and 9 in place of 3

(2012-04-08, 02:06)pumkinut Wrote:
(2012-04-07, 23:19)Plaguester Wrote: On a standalone Ubuntu system, this hasn't been needed since 9.04.
Funny, I need an asound.conf file for my brand-spanking-new XBMCbuntu install on an Intel H67 chipset mini-ITX board using the Intel IGP and audio over HDMI. Without the asound.conf I either have to choose correct passthrough audio or menu sounds. With the asound.conf file, I get both.

This thread concerns the NVidia ION chip (Acer Revo). I have no idea what the support level is for the Intel chipsets. I'd be interested to know if you had the same problem with a full Ubuntu install.
Then why did I need an asound.conf file for my integrated GF9300 on a mini-ITX board with Dharma on a minimal Maverick install? And what difference would a minimal vs XBMCBuntu vs full install give? It's mostly just software packages that XBMC does not need. Drivers and dependencies should be installed for each type of setup. A minimal or XBMCBuntu installation should have no problems with hardware that a full installation would solve, unless there is specific software in the GUI that would be needed.
<thread derail over>

Finchy,
If you're going straight to your TV and not passing through to an Audio/Video Receiver, there's no need to check DD or DTS capable receiver options, because your TV is just going to output stereo regardless. Plus, as Plaguester said, the television most likely cannot decode DTS audio (most can't due to licensing issues) and may or may not decode AC3 (Dolby Digital Signals). This is the case with my LG LCD TV, I can feed it AC3 audio and it decodes, passesthrough, and/or downmixes to stereo just fine. DTS just causes static, because it does not have the codecs for DTS decoding.

As for the LAN connection, I tried looking online for the specific PHY for the 3700. All I could find was that it was a Realtek chipset, as are a lot of LAN chipsets now. What you can do is the following. Drop to a terminal window and type in the following:
Code:
dmesg | grep eth0
It could also be eth1, but it's probably eth0. This should tell you what LAN chipset the OS sees and then what driver it's loading. For example on my current laptop:
Code:
mint@mint ~ $ dmesg | grep eth0
[    1.330459] e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:26:b9:ce:cb:7f
[    1.330462] e1000e 0000:00:19.0: eth0: Intel(R) PRO/1000 Network Connection
[    1.330488] e1000e 0000:00:19.0: eth0: MAC: 7, PHY: 8, PBA No: 1004FF-0FF
[   21.740337] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   24.876885] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[   24.877049] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   35.360052] eth0: no IPv6 routers present
Linux is showing that I have an Intel PRO/1000 LAN connection with the e1000e driver loaded. There are a couple of Realtek chipsets where the default driver r8169 is loaded, and causes all kinds of problems. The solution is to revert back to the r8168 driver, but you need to compile and load it yourself. My current HTPC motherboard has the problematic chipset, which is how I found out about it.

You can also see if r8168 or r8169 is loaded by issuing the following command:
Code:
lsmod | grep r816*
This will show you whether or not the 8169 or 8168 drivers are loaded for your LAN adapter.
Reply

Logout Mark Read Team Forum Stats Members Help
Need help installing XBMCbuntu on Acer Revo R3700 please0