No audio devices detected ~(udev/modporbe failure)

[clubex]

After yesterday's du (which included an upgraded kernel) and  rebooting the terminal hung at "waiting for dev to be fully populated..." until it eventually timed out. As the boot continued I saw a brief message something about udev and a modprobe failure. It went too fast for me to get any more data and I have no logs on that early part of the system initiation.

At the desktop the "do you want to permanently remove these devices" dialoge was displayed which indicated that no audio devices had been detected.

The above also happens with older kernels and it doesn't appear to be a hardware problem as the audio devices are all detected by an older version of siduction and also with a live CD.

Anyone have ideas how to get my audio devices detected and any explanation for the udev and the modprobe failure?

Code Select Expand


inxi -F
System:    Host: westfield Kernel: 3.9-6.towo.1-siduction-amd64 x86_64 (64 bit)
          Desktop: KDE 4.10.4 Distro: sidux 2008-04 Πόντος - kde-lite - (200812222256)
Machine:   Mobo: ASUSTeK model: M2N68-AM Plus version: Rev X.0x Bios: American Megatrends version: 1002 date: 11/19/2009
CPU:       Dual core AMD Athlon II X2 240 (-MCP-) cache: 2048 KB flags: (lm nx sse sse2 sse3 sse4a svm)
          Clock Speeds: 1: 2812.641 MHz 2: 2812.641 MHz
Graphics:  Card: NVIDIA GF119 [GeForce GT 520] X.Org: 1.12.4 driver: nvidia Resolution: 1680x1050@59.9hz
          GLX Renderer: GeForce GT 520/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 319.23
Audio:     Card-1: NVIDIA MCP61 High Definition Audio Sound: ALSA ver: k3.9-6.towo.1-siduction-amd64
          Card-2: NVIDIA GF119 HDMI Audio Controller
Network:   Card: NVIDIA MCP61 Ethernet driver: forcedeth
          IF: eth1 state: up speed: 100 Mbps duplex: full mac: e0:cb:4e:3a:d8:e4
Drives:    HDD Total Size: 250.1GB (48.2% used) 1: id: /dev/sda model: WDC_WD2500AAJB size: 250.1GB
Partition: ID: / size: 15G used: 12G (86%) fs: ext3 ID: /home size: 214G used: 101G (50%) fs: ext3
          ID: swap-1 size: 1.05GB used: 0.00GB (0%) fs: swap
Sensors:   System Temperatures: cpu: 36.0C mobo: 32.0C
          Fan Speeds (in rpm): cpu: 3183 sys-1: 1510
Info:      Processes: 139 Uptime: 25 min Memory: 1048.6/3959.8MB Client: Shell inxi: 1.8.4


[hsp]

apt-get purge oss-compat if installed and reboot helps

...

[gcp]

I can confirm this problem described above.
Downgrading initramfs-tools and oss-compat does not help.

In my case, i added snd-hda-intel to /etc/modules and have sound again.

But the ~1min Boot-delay remains. "waiting for dev to be fully populated..."

I am running pure debian sid.

Edit: purging oss-compat solved the problem.

[clubex]

Thanks hsp & gcp:
I tried both your suggestions and happily the audio devices have once again been detected and function correctly. Also the delay at waiting for dev is reduced to about 2 or 3 seconds.

Thanks once again to you both.

ps if a moderator thinks this topic is not an upgrade warning then please feel free to move it to the appropriate section of the forum.

[dibl]

Strange -- after installing the new kernel 3.9-6.towo.1, and rebooting, the system came up with no sound, and no audio devices except the connected USB webcam.  aplay -l showed no sound card.  dmesg showed many many errors of all kinds.

So I rebooted to watch messages, and the second time the system came up perfectly with no errors, and sound is working perfectly.  dmesg shows no errors, and only a couple of old ACPI warnings that don't mean anything.

Poltergeist!

[DeepDayze]

Found a bug report that could be related to the issue

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660803

[Smon]

Same problem here yesterday. I backup up everything in /etc/modprobe.d and then deleted all in there. Now it is working.

[gilpier]

Smon, I follow your suggestion, and now it seems that everything is working. Is there some problem with empty /etc/modprobe.d ?

Thanks,

Gilbert

[gilpier]

I restore everything inside /etc/modprobe.d and remove only alsa-base.conf.
Now it is working well. It seems that the problem is in module alsa-base.conf.

[musca]

Issue is fixed with oss-compat 3 in debian unstable main.

cheers!
musca

[clubex]

Thanks musca

[michaa7]

Are you sure it is solved?

During boot udev is now waiting (half a minute or more, was a fraction of a second before) for being populated. Then an error message appears which I can't read because the boot process is going on rapidly.

I don't know what might not work here and can't investigate further now (as I have to leave for some hours) but something seems still wrong with udev (fully updated half an hour ago).

[DeepDayze]

If you don't have any applications that only recognize OSS or you have a recent sound card you shouldn't need oss-compat, right?

[dibl]

If you don't have any applications that only recognize OSS or you have a recent sound card you shouldn't need oss-compat, right?

Logically, that would seem correct, but do an rdepends on oss-compat and you will be surprised.  I removed it some time ago, but it's back -- obviously it gets pulled in by other packages.

[DeepDayze]

If you don't have any applications that only recognize OSS or you have a recent sound card you shouldn't need oss-compat, right?

Logically, that would seem correct, but do an rdepends on oss-compat and you will be surprised.  I removed it some time ago, but it's back -- obviously it gets pulled in by other packages.

I would think oss-compat should be a recommends not a dependency for such apps. Oss-compat is totally broken on my system as well