Welcome To Australia's No.1 Media Center Community!
You Are Currently Viewing As A Guest - you'll need to register in order to participate in our community and make this annoying message disappear!
By registering you'll be able to post & reply to questions, set up your own image gallery & blog, communicate privately with other members, create & respond to polls, access downloads and other "members only" features.
Registration is fast, simple and absolutely free - so why not join our community today - you'll be glad you did! If you experience any problems with the registration process or your account, please send a message to Mike
Fine tuning questions on xbmc
this thread has 58 replies and has been viewed 6622 times
Contents of LinuxDrivers.zip is below. I have bolded the two files I think may be relevant. They both have "tar" as part of their extension, but not sure what to do now.
cd realtek-linux-audiopack-4.06a.tar
./configure
make
make install
Up to this point. Changed into the realtek-linux-audiopack-4.06a folder. Other commands didn't work. There was a Readme.txt file in the folder which gave instructions on how to install. Basically run the following command
./install
Ran this command - after lots and lots of code scrolling by, installation finished.
Rebooted.
Still no sound. No change in output from running aplay -l:
dad@myth-frontend:~/Documents/downloads/patches/LinuxDrivers/Audio/Others/realtek-linux-audiopack-4.06a$ ls
alsa-driver-1.0.14-4.06a.tar.bz2 install version
alsa-lib-1.0.14.tar.bz2 Readme.txt
alsa-utils-1.0.14.tar.bz2 test.wav.bz2
dad@myth-frontend:~/Documents/downloads/patches/LinuxDrivers/Audio/Others/realtek-linux-audiopack-4.06a$ cat Readme.txt
The source code copy from www.alsa-project.org. ver:3.3-4
Linux Source Code for ALC audio codec
Support Codec list:
====AC97 Codec=====
ALC100,100P
ALC200,200P
ALC650D
ALC650E
ALC650F
ALC650
ALC655
ALC653
ALC658
ALC658D
ALC850
ALC101
ALC202
ALC250
ALC203
====HD Audio codec ====
ALC260
ALC262
ALC660
ALC861
ALC880
ALC882
ALC883
ALC885
ALC888
Installation:
This Source Code is from www.alsa-project.org.
For driver installation, please follow below steps.
Automatic install:
execute
./install
Manual install:
Step 1. unzip source code
tar xfvj alsa-driver-1.0.xx.tar.bz2
Step 2. Turn on sound support (soundcore module, default turn on)
Step 3. Complied source code
a. cd alsa-driver-1.0.xx
b. ./configure
c. make
d. make install
e. ./snddevices
Step 4. Edit your /etc/modules.conf or conf.modules depending on the distribution
(Please refer to the attached modules.conf)
snd-xxxx is the card ID.
-- Azalia controller --ALC880 ALC882 ALC260 ALC262 ALC883 ALC885 ALC888
--- Intel ICH6 ICH7 ---------
snd-hda-intel
--- ATI chipset -----
snd-atiixp
-- AC97 controller --ALC655 ALC650 ALC250 ALC255
--- Intel ICH6 ICH7 , SiS 7012 and NVidia----------
snd-intel8x0
--- Via8233 Via686a -------------------------------
snd-via82xx
--- ATI Chipset -------------------------------
snd-atiixp
Copy and paste this to the bottom of your /etc/modules.conf or /etc/modprobe.conf file.
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-xxxx
# OSS/Free portion
alias char-major-14 soundcore
alias sound-slot-0 snd-card-0
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
Step 5. reboot your machine
Step 6. Use the alsamixer the disable mute (All audio line default is mute)
*Must to compile and to install the ALSA library and utility. (Use automatic install is already install)
excute alsamixer
Note: 1. The most detail information, can refer the alsa-kernel/Documenttation/ALSA-Configuration.txt in the azx-021705.tar.bz2.
2. Kernel Version must be 2.2.14 or later.
3. All mixer channels are muted by default. You must use a native
or OSS mixer program to unmute appropriate channels.
4. If can not compile the source code, try to rename the /usr/src/linux-2.x -> /usr/src/linux.
5. The driver added to support the SPDIF functoin.
6. a. You can download the alsa-lib-1.0.9 and alsa-utils-1.0.9a form the www.alsa-project.org, then unzip and install them.
b. Suggest use "alsamixer" to control mixer function.
c. Used "alsaconf" can autodetect which drive you need to install (step 4).
7. SUSE Distribution must install the ncurses package.
dad@myth-frontend:~/Documents/downloads/patches/LinuxDrivers/Audio/Others/realtek-linux-audiopack-4.06a$
I think I may recover my backup image (prior to all the latest attempts to get digital sound working) and try to install again.
See if that works - unless you have other ideas.
As for the shares, could not mount to the backend from the frontend:
Code:
root@myth-frontend:~# mount -t cifs //mythserver/images /mnt -o username=dad,password=******
mount: wrong fs type, bad option, bad superblock on //mythserver/images,
missing codepage or helper program, or other error
(for several filesystems (e.g. nfs, cifs) you might
need a /sbin/mount.<type> helper program)
In some cases useful info is found in syslog - try
dmesg | tail or so
When you say no sound did you go back through the alsamixer and unmute everything a re-try the commands above to play something with mplayer etc?
Your samba config is identical to mine as far as I can see.
The relevant bits of mine are:
Code:
# smb.conf is the main Samba configuration file. You find a full commented
# version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
# samba-doc package is installed.
# Date: 2006-05-02
[global]
workgroup = Libertyave
client ntlmv2 auth = yes
#printcap name = cups
#cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \\%L\profiles\.msprofile
logon home = \\%L\%U\.9xprofile
logon drive = P:
restrict anonymous = no
domain master = no
max protocol = NT
ldap ssl = No
server signing = Auto
add machine script = /usr/sbin/useradd -c Machine -d /var/lib/nobody -s /bin/false %m$
create mask = 775
directory mask = 775
preferred master = no
acl compatibility = winnt
server string = Home Server
[images]
comment = Clonezilla images
inherit acls = Yes
path = /home/rick/Documents/images
read only = no
guest ok = Yes
force group = users
I noticed in your output above it looks like you don't have a return after the last line in your samba.conf as your output looked like:
Code:
force group = usersdad : /home/dad >
Maybe edit that file and add a blank line at the bottom and save it again and restart samba:
sudo su -
/etc/rc.d/samba restart
I just mounted my images share with:
mount -t cifs //beast/images -o username=rick,password=<my password> /mnt
and it worked. I don't know if cifs is installed out of the box with mythbuntu, try the same line with:
mount -t smbfs //mythserver/images -o username=dad,password=<your password> /mnt
Got this back from BLKMGK over at the XBMC forums:
Quote:
I had the same issues on Mythbuntu when I was using it and in fact I think I had to install a GUI mixer so I could figure things out. Hope that is of some help!
You can install one on the frontend with:
sudo su -
sudo apt-get install alsamixergui
then log out of root and run it:
exit
alsamixergui
Have aplay and see what you can see. BLKMGK said he had two SPDIF devices on his hardware which probably makes sense if there is a coax one and HDMI.
Have a re-read of my last post about samba. I think you got a copy of it and I added something afterwards with regard to the missing end of line character in your samba config file.
I noticed in your output above it looks like you don't have a return after the last line in your samba.conf as your output looked like:
Code:
force group = usersdad : /home/dad >
Maybe edit that file and add a blank line at the bottom and save it again and restart samba:
sudo su -
/etc/rc.d/samba restart
Don't quite understand. Do I remove ":/home/dad >" from the line and add a blank line or just add a blank line? In the copy of your file, you did not have the ":/home/user >" at the end.
Digital Sound
I recovered the image from the backup so as to have a clean install. A few thoughts/issues:
Installed alsamixergui but I don't see how this is any different from alsamixer - it gives no additional functionality or info.
Is there another gui I could try?
By recovering the image I no longer have the updated Linux Drivers. Updated the drivers , but didn't see any difference.
The only other item found that may cause issues is that ALSA apparently looks by default for devices to be at DEVICE 0 and this appears to be at DEVICE 3. The temporary workaround for this is to create a symbolic link from /dev/snd/pcmC<CARD>D<EVICE>p to /dev/snd/pcmC<CARD>D0p. This may not be necissary in your case. Also, I have not figured out why this the sym link was required. I am still investigating this.
aplay -l shows my two digital devices to be devices 1 and 3, with analog being device 0. Should I be assigning my digital device to device 0? If so, how?
Sorry it took so long to answer, been away for the weekend with no PC access.. Think the Mr's and kids thought I was going to die when I found my optus wireless didn't work where we were staying
I survive though!
Quote:
Originally Posted by Duffy
Arkay
Don't quite understand. Do I remove ":/home/dad >" from the line and add a blank line or just add a blank line? In the copy of your file, you did not have the ":/home/user >" at the end.
Ah!!! There should be no :/home/dad on there at all. The line should just read:
force group = users
Quote:
Digital Sound
I recovered the image from the backup so as to have a clean install. A few thoughts/issues:
Installed alsamixergui but I don't see how this is any different from alsamixer - it gives no additional functionality or info.
Is there another gui I could try?
By recovering the image I no longer have the updated Linux Drivers. Updated the drivers , but didn't see any difference.
aplay -l shows my two digital devices to be devices 1 and 3, with analog being device 0. Should I be assigning my digital device to device 0? If so, how?
Is it just easier to go a buy a sound card? If yes, which one?
Duffy
Hmm. Without me being there I really can't tell what's going on. I can't even really think what to try next. That's the sort of thing where I'd just try a dozen different things until I got it to work. The annoying thing is that I know that board does work.
I would probably be inclined to just get a pci soundcard but as to which one I don't know. The soundblaster Audigy series are always well supported but I don't know if you can get one anymore.
This page confirms they are good for Linux. The Audigy 2 ZS is available new on ebay and appears to work fine.
I do have a couple of audigy 1/2 cares here though if you want to try one out and see?
Every board I've tried with onboard audio has worked so far. I think you're having issues because of this HDMI crap that the movie studios and MS have pushed into the PC market.
The other option you could try if you have the time and patience is to post on the myth/u/buntu forums and see if you can get some direct help with your board from someone who has one.
Had one other thought on the audio thing with that board.
Mythbuntu 8.10 is out. It's possible that it has a later version of Alsa that may be configured properly for the SPDIF on your board. You could take an image of the current system then apply the upgrade to 8.10 and see if it fixes anything. o hard in trying. If not just go back to the previous install.
I can't really think of anything else obvious to try. Particularly when I've been told by someone with the same board that it should work out of the box
Here's a link to the Arch wiki alsa page. Might be some things in there to try as well.
Been doing some more reading on that board. What a nightmare.
It would seem that the thing has more than one sound device. Apparently the HDMI audio output is an intel device and the SPDIF is a realtek one. I've read something on windows forums that says you must disable the intel side in order to get spdif to function at all.
It could be that your auto loaded modules for sound are loading the intel drivers and ignoring the realtek portion of the sound.
If that's the case we may need to blacklist the intel sound modules in order to get SPDIF to work.
Can you post up an:
lsmod
cat /etc/modprobe.d/alsa-base
So I can see what audio Linux thinks it has. It may not help but it's worth a try
Also, what is in the bios on that thing? Is there anything that looks like you can disable audio over HDMI but not spdif for example?
Cheers,
Arkay.
P.S. I bloody hate being beaten by problems like this...
Firstly, noticed you were away for the weekend. Must admit, I felt lost, but hope you enjoyed your time away from all of this.
Secondly, thanks for persisting with this.
Thirdly, just noticed your signature. Is that new or am I just hopeless? (You don't have to answer that)
I do like it your signature though.
Before trying 8.10, I think you are right re SPDIF being Intel and digital being Realtex. aplay -l shows device 3 to be Intel and device 1 to be ALC883 Digital (ALC883 is a Realtex codec).
Where the 1 at the end is the device number of the digital device (it is also 1 in my case). I noticed that the alsa-base file has similar commands, but not this command.
Firstly, noticed you were away for the weekend. Must admit, I felt lost, but hope you enjoyed your time away from all of this.
Sure did Though it was a mini holiday, away just long enough to be completely dark on the fact that I didn't take the whole week off!
Quote:
Secondly, thanks for persisting with this.
No worries. Just want people to enjoy what I do.. Perfect operation and functionality.
Quote:
Thirdly, just noticed your signature. Is that new or am I just hopeless? (You don't have to answer that)
Well. I will answer it...... It's new thanks to Mike who saw it somewhere on the net and suggested it'd be a great sig for me.
Quote:
I do like it your signature though.
Me too though I'm not doing much for advertising Linux with all these bloody Mythbuntu frontend problems. I really wish I'd done an Arch frontend as well now so I had a perfect do this, do that set of instructions. Mind you, that would probably make the front end build as long as the backend was
Quote:
Before trying 8.10, I think you are right re SPDIF being Intel and digital being Realtex. aplay -l shows device 3 to be Intel and device 1 to be ALC883 Digital (ALC883 is a Realtex codec).
Hmm, interesting. I f I can just find the post that mentioned disabling the Intel part to allow Alsa a load the ALC883 up.
Ok. According to a ubuntu thread you can identify your soundcard codec with:
cat /proc/asound/card0/codec#* | grep Codec
It should return ALC883 if the hardware spec of your board is right.
Because the output jacks vary from board to board and also in laptops that use the ALC883 chip sometimes you have to pass different arguments to the driver to tell it which way to configure your board.
According to the doco you need to edit /etc/modprobe.d/alsa-base or /etc/modprobe.conf at the top of the file is fine. (Can you tell I haven't had to do this on my setup?) and add or change the line:
Code:
options snd-hda-intel model=<option>
Code:
where <option> is one of the following:
ALC883/888
3stack-dig 3-jack with SPDIF I/O
6stack-dig 6-jack digital with SPDIF I/O
3stack-6ch 3-jack 6-channel
3stack-6ch-dig 3-jack 6-channel with SPDIF I/O
6stack-dig-demo 6-jack digital for Intel demo board
acer Acer laptops (Travelmate 3012WTMi, Aspire 5600, etc)
acer-aspire Acer Aspire 9810
medion Medion Laptops
medion-md2 Medion MD2
targa-dig Targa/MSI
targa-2ch-dig Targs/MSI with 2-channel
laptop-eapd 3-jack with SPDIF I/O and EAPD (Clevo M540JE, M550JE)
lenovo-101e Lenovo 101E
lenovo-nb0763 Lenovo NB0763
lenovo-ms7195-dig Lenovo MS7195
haier-w66 Haier W66
6stack-hp HP machines with 6stack (Nettle boards)
3stack-hp HP machines with 3stack (Lucknow, Samba boards)
auto auto-config reading BIOS (default)
So you might first try:
options snd-hda-intel model=3stack-dig
then stop/start alsa (or reboot):
/etc/init.d/alsa restart
Haven't checked if the above is right for alsa restart in ubuntu as I'm not in fronthe of the frontend. It should be something "alsa" though. ls -l /etc/init.d/*alsa* will tell you.
See if anything has changed with aplay -l/-L and test playback with mplayer, check alsamixer etc. All the stuff we've done previously.
If there's no joy then try the next in the list:
options snd-hda-intel model=6stack-dig
Only use the first part of the line above, that's the config to try, the "6-jack digital with SPDIF I/O" part are just despcriptions in the file and should not go in /etc/modprobe.d/alsa-base
That's one thing to try. Still looking for the info on removing conflicting intel drivers though I think that might not be 100% accurate. Intel-HDA is the driver for the realtek as far as I know... Will see if I can find the post again and get back to you.
modprobe looks ok but I'l not 100% sure what I'm looking for just yet
Though it was a mini holiday, away just long enough to be completely dark on the fact that I didn't take the whole week off!
