Re: [arch-general] alsa, hdmi, and the invisible magic output
fa...@alpha : cat /proc/asound/modules
0 snd_hda_intel
fa...@alpha : cat /etc/modprobe.d/*.conf
blacklist kyrofb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist savagefb
blacklist s3fb
blacklist viafb
blacklist vmlfb
blacklist cyber2000fb
blacklist neofb
blacklist rivafb
blacklist uvesafb
blacklist radeonfb
blacklist atyfb
blacklist aty128fb
blacklist cirrusfb
blacklist pm2fb
blacklist vt8623fb
blacklist sstfb
blacklist nvidiafb
blacklist kyrofb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist savagefb
blacklist s3fb
blacklist viafb
blacklist vmlfb
blacklist cyber2000fb
blacklist neofb
blacklist rivafb
blacklist uvesafb
blacklist radeonfb
blacklist atyfb
blacklist aty128fb
blacklist cirrusfb
blacklist pm2fb
blacklist vt8623fb
blacklist sstfb
blacklist nvidiafb
blacklist nouveau
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
ohci_hcd $CMDLINE_OPTS
install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
uhci_hcd $CMDLINE_OPTS
fa...@alpha :
Behold, the invisible sound device!
So? Am I fucked?
Or may one of my modprobe be the cause?
On Fri, Dec 3, 2010 at 4:11 AM, Andy Reindl stykwe...@gmail.com wrote:
cat /proc/asound/modules
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
I just noticed:
I've two pluseaudio items in the startup applications list (from gnome)
first one doing 'start-pulseaudio-x11'
and the other one: 'start-pulseaudio-kde'
What's that? Might it be related?
On Fri, Dec 3, 2010 at 9:12 AM, Samuel Martín Moro faus...@gmail.comwrote:
fa...@alpha : cat /proc/asound/modules
0 snd_hda_intel
fa...@alpha : cat /etc/modprobe.d/*.conf
blacklist kyrofb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist savagefb
blacklist s3fb
blacklist viafb
blacklist vmlfb
blacklist cyber2000fb
blacklist neofb
blacklist rivafb
blacklist uvesafb
blacklist radeonfb
blacklist atyfb
blacklist aty128fb
blacklist cirrusfb
blacklist pm2fb
blacklist vt8623fb
blacklist sstfb
blacklist nvidiafb
blacklist kyrofb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist savagefb
blacklist s3fb
blacklist viafb
blacklist vmlfb
blacklist cyber2000fb
blacklist neofb
blacklist rivafb
blacklist uvesafb
blacklist radeonfb
blacklist atyfb
blacklist aty128fb
blacklist cirrusfb
blacklist pm2fb
blacklist vt8623fb
blacklist sstfb
blacklist nvidiafb
blacklist nouveau
alias snd-card-0 snd-hda-intel
alias sound-slot-0 snd-hda-intel
install ohci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
ohci_hcd $CMDLINE_OPTS
install uhci_hcd /sbin/modprobe ehci_hcd ; /sbin/modprobe --ignore-install
uhci_hcd $CMDLINE_OPTS
fa...@alpha :
Behold, the invisible sound device!
So? Am I fucked?
Or may one of my modprobe be the cause?
On Fri, Dec 3, 2010 at 4:11 AM, Andy Reindl stykwe...@gmail.com wrote:
cat /proc/asound/modules
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
On Fri, Dec 3, 2010 at 10:31 AM, Philipp Überbacher
hollun...@lavabit.comwrote:
Excerpts from Samuel Martín Moro's message of 2010-12-03 01:45:14 +0100:
I added this .asoundrc:
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
It fixed at least a problem: I've no more warning about
snd_pcm_dmix_open.
But, still no sound while banshee's operating...
I don't know the .asoundrc syntax but as far as I can tell you should
tell your programs to use a dmix device instead of hw:something. dmix
means software mixing while hw:something means the program uses the
device exclusively.
If that doesn't work you could try PA.
Good luck.
I have now the following:
pcm.card0 {
type plug
slave.pcm dmix
hint {
show on
description My dmix output
}
}
ctl.mixer0 {
type hw
card 0
}
I also tried replacing slave.pcm dmix of card0 by dmixer, defining the
following:
pcm.dmixer {
type dmix
ipc_key 2048
slave {
pcm hw:0,1
period_time 0
period_size 1024
buffer_size 4096
rate 48000
}
bindings {
0 0
1 1
}
}
None of them fixed the problem.
And I'm still not sure I'm calling the good output (the second test uses
hw0,1, the first one does not specify it)
But there's nothing coming out of my TV anymore.
Also, when trying to open a file with alsaplayer, if vlc or banshee are
already playing something, that error pops out:
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
snd_pcm_open: Device or resource busy (plug:dmix)
[...]
NOTE: THIS IS THE NULL PLUGIN. YOU WILL NOT HEAR SOUND!!
I don't understand.
As far as I remember, I was always able to play a game while watching a
video and/or playing music.
What happends?
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
[arch-general] alsa, hdmi, and the invisible magic output
root 0 Dec 2 23:45 status
-r--r--r-- 1 root root 0 Dec 2 23:45 sw_params
/proc/asound/oss:
total 0
-r--r--r-- 1 root root 0 Dec 2 23:45 devices
-r--r--r-- 1 root root 0 Dec 2 23:45 sndstat
/proc/asound/seq:
total 0
-r--r--r-- 1 root root 0 Dec 2 23:45 clients
-r--r--r-- 1 root root 0 Dec 2 23:45 drivers
-r--r--r-- 1 root root 0 Dec 2 23:45 oss
-r--r--r-- 1 root root 0 Dec 2 23:45 queues
-r--r--r-- 1 root root 0 Dec 2 23:45 timer
fa...@alpha : uname -a
Linux alpha.example.com 2.6.36-ARCH #1 SMP PREEMPT Wed Nov 24 00:39:57 CET
2010 x86_64 Intel(R) Core(TM) i7 920 @ 2.67Ghzs GenuineIntel GNU/Linux
I'm not sure to understand what represent pcm0c, pcm0p and pcm1p...
Launching alsamixer, I only have one device (identified as default and hda
intel)
The last listed output is 'HDMI', and indeed, controls my screen speakers'
sound level.
So, I don't understand.
How is it possible to have only one card recognized, and controlling both of
them through the same alsamixer/gnome-volume-control panel?
What can I do?
Setting HDMI as default (only) output? How to do so?
Wait for a patch? Is it a kernel-related bug? Or with nvidia driver?
Would that even fix the banshee/browser troubles accessing device?
This arch worked for more than a year.
I guess that's the bad side of mainstream distros.
Whatever. I'm still enjoying my stay.
Also, I often get this warn:
*** NSPlugin Viewer *** WARNING: unhandled variable 18 (unknown variable)
in NPN_GetValue()
I'm quite sure it's not related to my problem, but I'm still curious: wtf?
I read on some ubuntu forum it's related to flash, kernel x86_64.
It's seems to be fixed on ubuntu. Did I misunderstood? (When) would it come
to arch?
Thanks for your help, and your time!
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
I've seen that.
But I did not seen anything about using a specific output of the card.
as I only have one detected device, how can I set HDMI as default output?
(or: how can I see my graphic card as a audio device too?)
Is it that 'bindings' keyword, that's not explained on the wiki?
2010/12/3 Cédric Girard girard.ced...@gmail.com
On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro faus...@gmail.com
wrote:
What can I do?
Setting HDMI as default (only) output? How to do so?
Wait for a patch? Is it a kernel-related bug? Or with nvidia driver?
Would that even fix the banshee/browser troubles accessing device?
You can control Alsa routing with the asoundrc [1] config file.
[1] http://alsa.opensrc.org/.asoundrc
--
Cédric Girard
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
Re: [arch-general] alsa, hdmi, and the invisible magic output
I added this .asoundrc:
pcm.!default {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
It fixed at least a problem: I've no more warning about snd_pcm_dmix_open.
But, still no sound while banshee's operating...
On Fri, Dec 3, 2010 at 1:22 AM, Samuel Martín Moro faus...@gmail.comwrote:
I've seen that.
But I did not seen anything about using a specific output of the card.
as I only have one detected device, how can I set HDMI as default output?
(or: how can I see my graphic card as a audio device too?)
Is it that 'bindings' keyword, that's not explained on the wiki?
2010/12/3 Cédric Girard girard.ced...@gmail.com
On Fri, Dec 3, 2010 at 12:06 AM, Samuel Martín Moro faus...@gmail.com
wrote:
What can I do?
Setting HDMI as default (only) output? How to do so?
Wait for a patch? Is it a kernel-related bug? Or with nvidia driver?
Would that even fix the banshee/browser troubles accessing device?
You can control Alsa routing with the asoundrc [1] config file.
[1] http://alsa.opensrc.org/.asoundrc
--
Cédric Girard
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
--
Samuel Martín Moro
{EPITECH.} tek5
CamTrace S.A.S
(+033) 1 41 38 37 60
1 Allée de la Venelle
92150 Suresnes
FRANCE
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
Re: [arch-general] BASH no longer does 'for i in $(ls); do ls $i; done'??
you may want to try
for i in $(`which ls` -d .) ; do `which ls` $(`which pwd`)/$i; done
it does work here
Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
On Tue, May 18, 2010 at 10:58 PM, Aaron Griffin aaronmgrif...@gmail.comwrote:
On Tue, May 18, 2010 at 3:47 PM, Sergey Manucharian
ingeniw...@gmail.com wrote:
Excerpts from Linas's message of Tue, 18 May 2010 22:31 +0200:
David C. Rankin wrote:
Guys,
I'm usually quite good at one-liners, but my simple ones no
longer work in Arch. Same cli works fine in suse. What have I
messed up? To wit:
What could keep the simple cli from working on Arch? I know
this stuff worked before updates this morning... What should I look
at?
Bash was updated from 4.1.5(2) to 4.1.7(2).
I can't reproduce it, though.
I cannot reproduce it either and suspect that your ls under $() is
not the real ls, but an alias. I've played with some, and they indeed
produce bad output.
If this is the case, replace ls with /bin/ls in the above and try again
Re: [arch-general] New Using AUR
you should take a look at packer, or yaourt
both of them are (AUR) package manager, dealing with both pacman *and* AUR
repositories.
packer is not perfect (we can not just do -Sy, but have to -Syu, for
example)
but yaourt is very slow (other programming language, don't know exactly, but
even on a core i7, it's shocking to see how long it took to do simple
things...)
so... make your choice :)
Samuel Martín Moro
{EPITECH.} tek4
CamTrace S.A.S
Nobody wants to say how this works.
Maybe nobody knows ...
Xorg.conf(5)
On Wed, Mar 24, 2010 at 3:24 PM, David Rosenstrauch dar...@darose.netwrote:
re, extra, or community.
