[SOLVED] Missing mixer device in /dev/snd??

I'm trying to get the gkrellm volume plugin working. When I try to configure it, the plugin can't find any mixer devices. My next step was to check the plugin source which notes that "enable_alsa=1" should be an argument to make. Since this wasn't in the PKGBUILD script, I added it and rebuilt the package. After updating and installing, I restarted gkrellm, but was still unable to locate a mixer. Since sound is working just fine, i started digging deeper.
8< Here's the output of several diagnostic commands... >8
$ cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe7f0000 irq 16
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfe8e8000 irq 19
$ cat /proc/asound/devices
1: : sequencer
2: [ 0- 1]: digital audio playback
3: [ 0- 0]: digital audio playback
4: [ 0- 0]: digital audio capture
5: [ 0- 0]: hardware dependent
6: [ 0] : control
7: [ 1- 3]: digital audio playback
8: [ 1- 0]: hardware dependent
9: [ 1] : control
33: : timer
$ l /dev/snd
total 0
drwxr-xr-x 2 root root 80 Jul 25 10:44 by-path/
crw-rw----+ 1 root audio 116, 6 Jul 25 10:44 controlC0
crw-rw----+ 1 root audio 116, 9 Jul 25 10:44 controlC1
crw-rw----+ 1 root audio 116, 5 Jul 25 10:44 hwC0D0
crw-rw----+ 1 root audio 116, 8 Jul 25 10:44 hwC1D0
crw-rw----+ 1 root audio 116, 4 Jul 25 10:44 pcmC0D0c
crw-rw----+ 1 root audio 116, 3 Jul 26 03:36 pcmC0D0p
crw-rw----+ 1 root audio 116, 2 Jul 25 10:44 pcmC0D1p
crw-rw----+ 1 root audio 116, 7 Jul 25 10:44 pcmC1D3p
crw-rw----+ 1 root audio 116, 1 Jul 27 03:44 seq
crw-rw----+ 1 root audio 116, 33 Jul 25 10:44 timer
# lsmod |grep snd
snd_seq 50785 0
snd_seq_device 5372 1 snd_seq
snd_hda_codec_hdmi 22784 1
snd_hda_codec_realtek 297871 1
snd_hda_intel 22186 1
snd_hda_codec 77543 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6342 1 snd_hda_codec
snd_pcm 73736 3 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 19488 2 snd_seq,snd_pcm
snd 57256 11 snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6178 1 snd
snd_page_alloc 7161 2 snd_hda_intel,snd_pcm
$ pacman -Qs alsa
local/alsa-lib 1.0.24.1-1
An alternative implementation of Linux sound support
local/alsa-plugins 1.0.24-2
Extra alsa plugins
local/alsa-utils 1.0.24.2-1
An alternative implementation of Linux sound support
8< end of command output >8
I've been unable to locate a snd_mixer module for the kernel and there is no /dev/snd/mixerC?D?
I thought that the ALSA interface had changed since I last compiled from scrath (I was a Slacker from kernel 1.2 until I migrated to Ubuntu, and now to Arch), but according to http://www.alsa-project.org/main/index. … ibrary_API, /dev/snd/mixerCXDX is still part of the interface specification.
Did I miss an ALSA pacakage that's required to get /dev/snd/mixerCXDX?
Or has the ALSA implementation changed (/dev/snd/mixerCXDX deperecated), in which case the gkrellm plugin needs to be updated? Google didn't turn up anything definitive and the alsa-driver-1.0.2 source tarball doesn't include a changelog.
Thanks!
Last edited by barthel (2011-07-29 03:07:07)

That's what I was afraid of. I switched to Ubuntu at Dapper Drake, so I've not been up to speed with the details of program changes the way I was with Slackware. I don't want to install the OSS layer only for the sake of a volume widget.
Thanks for the reply. I'm taking a look at Conky now as a potential replacement for gkrellm, since it hasn't been updated in years.

Similar Messages

[Solved] Missing /sys/devices/system/cpu/sched_mc_power_savings

I'm missing two files that are quite desirable on laptop /sys/devices/system/cpu/sched_mc_power_savings and /sys/devices/system/cpu/sched_smt_power_savings. I'm running standard arch 2.6.34 kernel.
Anything I can do to correct that?[wiki][/wiki]
Last edited by magillos (2010-07-11 18:35:51)

I compiled my own kernel and it seems that setting processor_type_and_featured->processor_family:core_2 was necessary instead of default Arch's processor_type_and_featured->processor_family'pentium-pro.

[SOLVED]ALSA sequencer(/dev/snd/seq) missing = broken midi

I get this error when attempting to start qsynth (frontend for fluidsynth)
fluidsynth: warning: Failed to pin the sample data to RAM; swapping is possible.
fluidsynth: warning: Requested a period size of 1024, got 940 instead
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
fluidsynth: error: Error opening ALSA sequencer
It's right, /dev/snd/seq really does not exist on my system. I have the midi driver set to alsa_seq in the qsynth settings, and it's been working just fine up until now. I haven't tinkered with anything related to alsa, so I'm not sure how it disappeared. The only possible cause I can think of is that today I installed kernel26-lts and have been using it for a few hours. However, rebooting and switching to the standard kernel doesn't solve the problem, as /dev/snd/seq is still missing and I get an identical error message. Any ideas/suggestions/wild guesses?
Last edited by splittercode (2010-08-25 15:14:54)

Maybe you have blacklisted some module in rc.conf?
[karol@black ~]$ lsmod | grep -i seq
snd_seq_dummy 1071 0
snd_seq_oss 25016 0
snd_seq_midi_event 4488 1 snd_seq_oss
snd_seq 41656 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 4353 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_timer 15601 2 snd_seq,snd_pcm
snd 42602 11 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
[karol@black ~]$ l /dev/snd/seq
crw-rw---- 1 116, 3 2010-08-25 13:56 /dev/snd/seq

Tvtime has no sound: no 'mixer' device in /etc? [~SOLVED]

Hi everybody
Every audio app were workin fine in this location up to 1 or 2 days ago.
Got latest Alsa & edited /etc/modprobe.conf accordingly to alsa wikki a long time ago, removing anything but those lines:
alias snd-card-0 snd-intel8x0
alias sound-slot-0 snd-intel8x0
As of today, bmp, amarok, opera, mplayer have sound as allways, but tvtime has none (and that came out just in time for my single favorite tv show, you know that :cry: ) :
Running tvtime 1.0.1.
Reading configuration from /etc/tvtime/tvtime.xml
Reading configuration from /home/kozaki/.tvtime/tvtime.xml
mixer: Can't open device /dev/mixer, mixer volume and mute unavailable.
tvtime uses '/dev/mixer:line' by default:
option name="MixerDevice" value="/dev/mixer:line"/
And may use some others like 'pcm', 'vol', etc.
But it worked fine until 1 or 2 days ago, & I did not edit tvtime conf file since months !?
What I found is there's no 'mixer' device in /etc :
[root@llewellyn kozaki]# find /etc -name "mixer*"
[root@llewellyn kozaki]#
any clue about that pliz ?

unmuted 'Line' in alsamixer and TV sound is back ...even if tvtime shows same warning message
mixer: Can't open device /dev/mixer, mixer volume and mute unavailable.
OK i get it clearer now : sound comes directly to/from the 'In' jack on my mobo integrated sound chip, so I have no control on it (like with an audio CD plugged directly to the sound card I guess).
That was most probably /me having played with alsamixer #-|
Uh, what is that still absent 'mixer' device supposed to do anyway ?

Couldn't open mixer device /dev/audioctl

I have just installed Solaris10 x86 OS on my Toshiba Satellite Laptop, everything seesm to work fine but I have no audio. The volume control icon on the panel says > no audio device and when I click on it I get an error dialog saying> Couldn't open mixer device /dev/audioctl
I have downloaded the Solaris Audio Drivers 1.0, audio810 and audiovia823x from the Sun website and installed them but no use, I also installed the audio drivers from the http://www.tools.de/solaris/audio/ website > audio1371, audioemu, audioi810, audiovia8233 but nothing.
Could anyone please advise me how I can get the audio working.
Thanks,
Suraj

HI thankx,
I tried your solution but>
devfsadm: driver failed to attach: audio810
Warning: Driver (audio810) successfully added to system but failed to attach

[SOLVED] ALSA and intel soundcard - not detected, /dev/snd is empty

Hi, there was some topics mounths ago about this but I still can't figure out how to get my sound to work.
The main problem is that my soundcard is not detected and /dev/snd seems a little empty. I can't find the controlc0,1 files either....
Here is some useful info.
root@red red]# ls -l /sys/module/snd/holders/
total 0
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_hda_codec -> ../../snd_hda_codec
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_hda_intel -> ../../snd_hda_intel
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_hwdep -> ../../snd_hwdep
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_mixer_oss -> ../../snd_mixer_oss
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_pcm -> ../../snd_pcm
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_pcm_oss -> ../../snd_pcm_oss
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_seq -> ../../snd_seq
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_seq_device -> ../../snd_seq_device
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_seq_oss -> ../../snd_seq_oss
lrwxrwxrwx 1 root root 0 Jun 15 17:09 snd_timer -> ../../snd_timer
[root@red red]# lsmod | grep '^snd' | column -t
snd_seq_dummy 1439 0
snd_seq_oss 28928 0
snd_seq_midi_event 5412 1 snd_seq_oss
snd_seq 50530 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 5233 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_hda_intel 22514 0
snd_pcm_oss 39096 0
snd_hda_codec 68863 1 snd_hda_intel
snd_hwdep 6150 1 snd_hda_codec
snd_mixer_oss 16956 1 snd_pcm_oss
snd_pcm 70924 3 snd_hda_intel,snd_pcm_oss,snd_hda_codec
snd_timer 19684 2 snd_seq,snd_pcm
snd 57209 10 snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm_oss,snd_hda_codec,snd_hwdep,snd_mixer_oss,snd_pcm,snd_timer
snd_page_alloc 7161 2 snd_hda_intel,snd_pcm
[root@red red]# ls -l /dev/snd/
total 0
crw-rw---- 1 root audio 116, 3 Jun 15 17:00 seq
crw-rw---- 1 root audio 116, 2 Jun 15 17:00 timer
Souncard : Don't know the exact name, the "intel hd" one with an ICH7 bridge
Mobo : intel d945gclf (little atom board, not the newer ones)
Notice that line : snd_hda_intel 22514 0
Seems to me that the module is loaded, am I right?
EDIT: Sorry, maybe I am in the wrong section...
Last edited by Lrouge (2010-06-18 18:33:54)

Looks pretty complete to me. (OK, /dev/snd does look sparse.) What do you see when you run alsamixer and press the F5 key?
$ sudo su -
# pacman -Sy alsa-utils
# alsamixer
Press F5 and check for:
* Master, Speaker, Front, Line, PCM volume down (if any)
* Any MM (bottom of vertical bar, signifies: line is muted) -- mute / un-mute with the 'm' key
Press Esc key to exit alsamixer + save changes.
Also, right after booting, run: dmesg | grep -i codec
Look for something like "Realtek" or "ALC662" or similar.
Manually add codec driver: modprobe snd_hda_codec_realtek
ls -al /dev/snd
drwxr-xr-x 2 root root 60 May 28 19:35 by-path
crw-rw---- 1 root audio 116, 7 May 28 19:35 controlC0
crw-rw---- 1 root audio 116, 6 May 28 19:35 hwC0D2
crw-rw---- 1 root audio 116, 5 May 28 19:35 pcmC0D0c
crw-rw---- 1 root audio 116, 4 May 28 19:35 pcmC0D0p
crw-rw---- 1 root audio 116, 3 May 28 19:35 seq
crw-rw---- 1 root audio 116, 2 May 28 19:35 timer
lsmod | grep snd
snd_hda_codec_realtek 179443 1
snd_seq_dummy 1099 0
snd_seq_oss 25304 0
snd_seq_midi_event 4452 1 snd_seq_oss
snd_hda_intel 18921 0
snd_seq 42628 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 4313 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_hda_codec 56728 2 snd_hda_codec_realtek,snd_hda_intel
snd_pcm_oss 33693 0
snd_hwdep 5102 1 snd_hda_codec
snd_pcm 57479 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_mixer_oss 14810 1 snd_pcm_oss
snd_timer 16117 2 snd_seq,snd_pcm
snd 43847 11 snd_hda_codec_realtek,snd_seq_oss,snd_hda_intel,snd_seq,snd_seq_device,snd_hda_codec,snd_pcm_oss,snd_hwdep,snd_pcm,snd_mixer_oss,snd_timer
soundcore 5007 1 snd
snd_page_alloc 5809 2 snd_hda_intel,snd_pcm

[Solved] Inconsistency in device naming concerning mount/fstab

This is not a problem that needs to be solved, but rather a gap in my understanding of a mechanism.
I have several partitions mounted in my fstab, they are identified by UUID.
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump><pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
UUID=0767c51a-0ba8-405e-ac98-106182fe4d83 /tmp ext4 noexec,rw,noatime,nodiratime 0 2
UUID=0ba14b78-1b36-4857-92ae-8b1ca41264b6 /boot ext2 defaults 0 1
UUID=4eb07abb-25b0-4683-badf-8d556b536d9c / ext4 defaults 0 1
UUID=e3fe5429-379b-4b6d-a01e-e30aa85784e2 /home ext4 defaults 0 1
UUID=e7fda340-ca00-4c4c-b42e-cfba13a3abbe swap swap defaults 0 0
UUID=e3ae11a4-b602-4ea2-bbf7-8c8c9dea52a6 /mnt/Esther ext4 defaults,rw,noatime,nodiratime 0 2
UUID=55525a1b-386b-4390-8f47-b078b0b2c06e /mnt/Ballamb ext4 defaults,rw,noatime,nodiratime 0 2
UUID=b71cfb8d-a4eb-4ded-a65b-fbc2db102332 /mnt/Galbadia ext4 defaults,rw,noatime,nodiratime 0 2
When all drives are mounted, they show up as mounted by device name (/dev/sd*), only / is displayed as mounted by UUID.
$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=386283,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c on / type ext4 (rw,relatime,barrier=1,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,mode=600,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
/dev/sdc2 on /tmp type ext4 (rw,noexec,noatime,nodiratime)
/dev/sda1 on /boot type ext2 (rw)
/dev/sda4 on /home type ext4 (rw)
/dev/sdb1 on /mnt/Esther type ext4 (rw,noatime,nodiratime)
/dev/sdc1 on /mnt/Ballamb type ext4 (rw,noatime,nodiratime)
/dev/sdd1 on /mnt/Galbadia type ext4 (rw,noatime,nodiratime)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/xy/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=xy)
$ df -h
Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
udev 10M 0 10M 0% /dev
run 10M 192K 9,9M 2% /run
/dev/disk/by-uuid/4eb07abb-25b0-4683-badf-8d556b536d9c 68G 8,5G 56G 14% /
shm 1,5G 4,0K 1,5G 1% /dev/shm
/dev/sdc2 289G 194M 274G 1% /tmp
/dev/sda1 251M 17M 222M 7% /boot
/dev/sda4 849G 62G 745G 8% /home
/dev/sdb1 1,8T 1,5T 223G 88% /mnt/Esther
/dev/sdc1 1,1T 223G 810G 22% /mnt/Ballamb
/dev/sdd1 1,8T 390G 1,4T 23% /mnt/Galbadia
Now I feel the urge to know why. Neither the mount nor the fstab manfile gave me insight on this one. So, what's behind this?
Last edited by Awebb (2011-10-08 17:51:26)

Now I feel stupid for not searching properly. Solved. Thanks, karol.
EDIT: So, in other words, if the UUID is passed by Grub, it shows as UUID in the system,
http://projects.archlinux.org/mkinitcpi … 3afd7e0001
So it was solved about a year ago? Well...
Last edited by Awebb (2011-05-29 14:12:06)

Bluetooth is missing from device manager

As you can see that bluetooth is missing from device manager.I have also installed energy management but only wireless tab apppears.I m using windwos 8 pro 64 bit..
i have also tried to install windwos 7 bluetooth driver in compatabilty but it doesnt appear in device manager but after installing in compatability mode bluetooth appeared in PC SETTINGS-->>DEVICES.But it was grayed.
Please help me.

Amanat,
you need to post your model number which can be found on the system itself, please see following link, or post the Lenovo part number. This will enable Shiva to check that your system should have Bluetooth; not all G470s have Bluetooth.
http://support.lenovo.com/en_GB/basic.page?DocID=HF003001
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Udev: /dev/snd - /dev/sound

*[root@Asteraceae snd]# ls -la
total 0
drwxr-xr-x 2 root root 0 2004-11-07 02:26 .
drwxr-xr-x 21 root root 0 2004-11-07 03:25 ..
crw-rw---- 1 root audio 116, 0 2004-11-07 02:26 controlC0
crw-rw---- 1 root audio 116, 24 2004-11-07 02:26 pcmC0D0c
crw-rw---- 1 root audio 116, 16 2004-11-07 02:26 pcmC0D0p
crw-rw---- 1 root audio 116, 25 2004-11-07 02:26 pcmC0D1c
crw-rw---- 1 root audio 116, 33 2004-11-07 02:26 timer
*[root@Asteraceae sound]# ls -la
total 0
drwxr-xr-x 2 root root 0 2004-11-07 02:26 .
drwxr-xr-x 21 root root 0 2004-11-07 03:25 ..
crw-rw---- 1 root audio 14, 4 2004-11-07 02:26 audio
crw-rw-rw- 1 root audio 14, 3 2004-11-07 02:26 dsp
crw-rw-rw- 1 root audio 14, 0 2004-11-07 02:26 mixer
why are the inodes in /dev/snd only crw-rw---- and in /dev/sound crw-rw-rw-? (i don't really understand the concept having a /dev/snd AND a /dev/sound ... or is it simply legacy-reasons to keep older software working?)

phrakture wrote:my dirs are the same permission-wise...
thanx for confirming that i'm not crazy or having paranoia ;-)
phrakture wrote:you may have an extra 6 in your /etc/udev/permissions.d/udev.permissions...
yes, indeed i have
phrakture wrote:I think that /dev/sound is legacy (if I rmmod snd-pcm-oss this /dev/sound is empty).
oh ... didn't think at that ... exactly! if oss-legacy is removed, the duplica /dev/sound disappears - and now the world is a little bit more logical to me
thanx

After partition using fdisk, i can not see the new device file (/dev/sdd1)

I used fdisk -l to partition /dev/sdd, use the entire disk as partition 1. it looks successful:
# fdisk -l /dev/sdd
Disk /dev/sdd: 10.7 GB, 10737418240 bytes
64 heads, 32 sectors/track, 10240 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x35e3e2c4
Device Boot Start End Blocks Id System
/dev/sdd1 1 10240 10485744 83 Linux
the problem: i don't see the device file /dev/sdd1. tried to delete it and partition again, the same.
also tried
- mknod b 8 70 /dev/sdd1, to manually create it, but when i use oracleasm createdisk DISK2 /dev/sdd1, the command won't recognize manually crated /dev/sdd1.
- reboot the server,
- "partprobe" command, no luck.
in addition, cat /proc/partitions seems including /dev/sdd1:
cat /proc/partitions
major minor #blocks name
8 16 292935982 sdb
8 0 143338560 sda
8 1 512000 sda1
8 2 142825472 sda2
252 0 25608192 dm-0
252 1 25608192 dm-1
252 2 62423040 dm-2
252 3 35012608 dm-3
252 4 20480000 dm-4
252 5 10240000 dm-5
252 6 4096000 dm-6
8 32 10485760 sdc
8 33 10484736 sdc1
8 48 20971520 sdd
8 49 20971504 sdd1
8 64 10485760 sde
8 65 10485744 sde1
any advice?
Thanks as alwasy!
Edited by: 943714 on Apr 25, 2013 10:55 AM

After you create a new partition, always verify it:
# fdisk -l /path/to/diskOnce that confirms the new partition, you must tell the kernel to re-read the partition table. Several ways to do this, depending on what your storage connection is. This often works:
# partprobe /path/to/mydiskThen check if the kernel sees the partition:
# grep /proc/partitions mydiskIf it does, you are done.

Sound card has no Mix device. Can alsa simmulate one?

Hey,
As the subject says, my sound card
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
doesn't have a "Mix" device from which to record "what-you-hear" sound. I've read into the subject, and keep seeing Pulse mentioned. However, I'd like to avoid switching to Pulse, if at all possible. Is alsa capable of creating a "virtual mix device" or some such contraption?

After spending a whole bunch of time, I was able to create a hardware loopback using ALSA that allows recording all of "what-you-hear".
Like most modern motherboards, mine also had a "HDA Intel" audio controller, but that's only half the hardware. You should also have a "codec" chip that the HDA Intel chip controls.
My codec chip is a Realtek ALC662. So it all started by using some google-fu to download the PDF datasheet for this chip. Looking at the block diagram in that document showed that there were indeed "virtual wires" that connected the audio outputs (play) back to the audio inputs (capture).
Downloading, compiling, and firing up the "hda-analyzer" program showed that those "virtual wires" simply were not turned on. So I used that same program to "connect" the wires, unmute some of the newly connected nodes, then messed with alsamixer until it all worked.
The "hda-analyzer" program has a great feature that can create a Python script of the changes you've made. This is super because your changes will disappear on a reboot (unless you jump through even more hoops).
I found that sometimes if I left the hardware loopback device connected for a somewhat long period of time, a minor "hummmm..." could be heard from my speakers when no music was playing. So I'm totally guessing this is the reason why the ALSA developers don't have this loopback "wired" by default. So I simply created one Python script that turns on the loopback, and then another that turns it off.
Anyway, it works great, and if you're lucky (your codec chip has virtual "loopback" wires), and you roll up your sleeves and get really, really "dirty" in the ALSA and audio hardware mud, you just may be able to do the same thing on your system.
Last edited by pigiron (2012-04-17 23:26:45)

How can i get on my iMAC read access to BPF devices in /dev/bpf*

Ls.
How can i get/change on my iMAC read access to BPF devices in /dev/bpf*
I want to use Wireshark.
Thanks in advance.
Loekie.

...any app launched from /Applications holds only the permissions of the user launching the app, regardless of the owner (presumably because anyone, including "root" can install applications into /Applications).
It has nothing to do with where the application is installed. Any executable runs with the permissions of the user who runs it. The only exception is a binary executable with the SUID or SGID bit set, and then only if it's on the root device, and only if it's not an Aqua application. The SG/UID bits are ignored otherwise.
So, anyone who has installed Wireshark from the "native .dmg" by drag-and-dropping won't be able to use the suid trick because the OS will ignore the suid permissions.
Sorry, I don't understand this at all. Wireshark invokes dumpcap as a child process to capture packets. If dumpcap is installed anywhere on the root device as SUID root, then it will run as root regardless of who invokes it.
The suid method will only work for Macports and Fink installations...
That's not correct. There are many SUID or SGID executables in a default installation of the Mac OS, and none of them comes from MacPorts or Fink.

Could not open the device file /dev/nvidia0

and yet:
[root@mythfe01 dev]# ls -alh nvid*
crw-rw-rw- 1 root root 195, 0 Mar 26 16:06 nvidia0
crw-rw-rw- 1 root root 195, 255 Mar 26 16:06 nvidiactl
and:
[root@mythfe01 dev]# lsmod | grep nv
nvidia 4083280 0
agpgart 28872 1 nvidia
but:
NVIDIA: could not open the device file /dev/nvidia0 (Input/output error).
(EE) NVIDIA(0): Failed to initialize the NVIDIA graphics device!
(EE) NVIDIA(0): *** Aborting ***
I am using a homemade kernel, but i can't think of a reason why that would prevent things from working properly considering the module loaded ok.
Any thoughts?

Moo-Crumpus wrote:Do you use udev? Have a look if there is a ruleset for nvidia, I remember there was one. Afaik, nvidia should be owned by the video group - well, once it was, I am not up to date and have no arch machine with nvidia right now.
Could anyone specify how to do that? I have the exact same problem, although I use the default kernel that came with Arch.
NVIDIA: could not open the device file /dev/nvidia0 (Permission denied).
NVIDIA: Direct rendering failed; attempting indirect rendering.
[kristjans@myhost ~]$ cat /proc/driver/nvidia/cards/0
Model: GeForce 6200 TurboCache(TM)
IRQ: 22
Video BIOS: 05.44.02.52.00
Card Type: PCI-E
DMA Size: 39 bits
DMA Mask: 0x7fffffffff
[kristjans@myhost dev]$ ls -alh nvid*
crw-rw---- 1 root 27 195, 0 2007-10-06 19:10 nvidia0
crw-rw-rw- 1 root 27 195, 255 2007-10-06 19:10 nvidiactl
[kristjans@myhost dev]$ lsmod | grep nv
nvidia 6829684 40
i2c_core 20352 2 nvidia,i2c_piix4
agpgart 27224 2 nvidia,ati_agp
Last edited by KSiimson (2007-10-11 04:23:18)

Udev doesn't create sd* devices in /dev

Today I updated udev package and after it I can't start my system. The booting stops with the message about check filesystem manually. When I tried to do this I couldn't find any sd* devices in /dev. Kernel detects all drives and correspond files presents in /sys/block directory. I can make device files with mknod command using information from /sys.
How do I make udev to create device files in /dev?
Sorry for bad English.

I just found one more interesting thing. When I test udev rules by "udevadm test /block/sdb/sdb2" udev creates correct device files - /dev/disk/ dev/block and /dev/sd*. But at daemon mode - udevd --daemon it doesn't do anything!
Does anybody know how to fix this?

Nvidia Input/Output error. Could not open the device file /dev/nvidia0

Hello, I finally have Arch running on my MacBook pro 3,1 (mid 2007) but when I startx after installing Nvidia drivers it gives the Input/Output error and states "could not open device file /dev/nvidia0." I tried everything from the Nvidia wiki, and nothing seems to work. Does anyone please have any other ideas or things to try? My Nvidia card is 8600M GT and I have installed xorg-server, xorg-apps and Nvidia-utils already. Also is it possible my graphics card is not compatiable with this new kernel? Thank you for your time.

You know that this posts a huge list - and I couldnt remember how to trim for certain keywords (which one would you be interested in?).
So here the last few things regarding Video: from dmesg:
[..] nvidia: module license "NVIDIA" taints kernel.
[..] Disabling lock debugging due to kernel taint.
[..] nvidia 0000:01:00.0: enabling device (0002 -> 0003)
[..] vgaarb device changed decodes: PCI:0000:01:00.0,oldcodes=io+mem,decodes=none:owns=none
[..] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 304.37 Wed Aug 8 19:52:48 PDT 2012
then comes Swap, wlan, eth0 etc..

[SOLVED] Missing mixer device in /dev/snd??

Similar Messages

Maybe you are looking for