Prev: Package Level Thermal Control and Power Limit Notification: power limit
Next: [PATCH] ips driver: make it less chatty
From: Mario 'BitKoenig' Holbe on 28 Jul 2010 17:30 On Wed, Jul 28, 2010 at 06:03:29PM +0200, Takashi Iwai wrote: > I wrote: > > Mario 'BitKoenig' Holbe wrote: > > > My PC-Speaker Beep control worked in 2.6.34, but is gone in 2.6.35-rc6. > > It's because now the driver checks the SSID your board sets up. > > So, it's actually BIOS that clears it. But the BIOS itself beeps through the sound-card at boot :/ > Or, does the following patch fix? It's already in sound git tree, Nope, unfortunately it doesn't. Still no Beep controls, no beep through sound-card. May I somehow provide any further data? Or am I somehow able to tweak it? Is there a module parameter to set this SSID bit? I mean, it did work before... :) Thanks for you help & regards Mario -- Why did the tachyon cross the road? Because it was on the other side.
From: Mario 'BitKoenig' Holbe on 29 Jul 2010 04:10 On Thu, Jul 29, 2010 at 07:44:38AM +0200, Takashi Iwai wrote: > Mario 'BitKoenig' Holbe wrote: > > But the BIOS itself beeps through the sound-card at boot :/ > But BIOS tells that the HD-audio codec shouldn't use, so the driver > follows it. Even grub's beep (play 480 440 1) goes through the sound-card. So it seems like the BIOS leaves everything set up working as well. Please don't get me wrong. I'm not saying the driver does something wrong, I'm sure it doesn't. I'm just sure that if I could convince it to behave as if it would have detected the Beep pin everything would work fine again because it did before... > Please give alsa-info.sh output instead of codec proc file. It's more > comprehensive. Attached. This is from a kernel with both patches applied you sent me. > With the patch below, you'll likely have back the system beep sound. Nope, no sound. But I guess this wasn't the intention of the patch. Now, no beep input is registered anymore - which was the intention, I guess. > But it doesn't go through codec, thus no volume control. If you mean it should go through the 5V PC Speaker (i.e. pcspkr) - I don't have such a thing connected. I always appreciated having volume- and mute control over the beep at night when you can't get away from work but don't like to wake up anybody just because command completion beeps, because you pasted something in the wrong window, or whatever. regards Mario -- Independence Day: Fortunately, the alien computer operating system works just fine with the laptop. This proves an important point which Apple enthusiasts have known for years. While the evil empire of Microsoft may dominate the computers of Earth people, more advanced life forms clearly prefer Macs.
From: Mario 'BitKoenig' Holbe on 29 Jul 2010 05:20 On Thu, Jul 29, 2010 at 10:52:36AM +0200, Takashi Iwai wrote: > Usually the codec SSID isn't checked in other places, so passing a > bogus value should be OK. Pass a value like 2: Mh, 1 probably :) $ cat /etc/modprobe.d/local-alsa.conf options snd-hda-intel model=asus-p5q install snd-hda-intel /sbin/modprobe --ignore-install snd-hda-intel $CMDLINE_OPTS && { cd /sys/class/sound/hwC0D0; echo -n 1 > subsystem_id; echo -n 1 > reconfig; : ; } Yep, Beep is back :) Btw... On Thu, Jul 29, 2010 at 10:26:22AM +0200, Takashi Iwai wrote: > So, the fix is likely to override SSID value, or create a special > quirk rule to enable PC-beep for known white-list, supposing BIOS > won't be fixed in any future... Well, the Board is from 2007, the last BIOS is from Aug 2009. I don't think Asus will provide an update just for that :) Thanks for your help Mario -- Unfortunately, the chip vendors have delayed the availability of the long-promised crystal-ball peripherals yet again, forcing the governor code to rely on heuristics; once again, software must make up for deficiencies in the hardware. -- Jonathan Corbet, LWN
From: Mario 'BitKoenig' Holbe on 29 Jul 2010 09:30
On Thu, Jul 29, 2010 at 11:42:44AM +0200, Takashi Iwai wrote: > OK, then try the patch below (over my previous two patches). It > enables PC-beep for your device forcibly. Yes, it does and it works. Thank you very much again. I just checked 2 more boards - the P5E-VM HDMI (P5E-V HDMI's little brother) is already covered by the quirk and P5Q-EM (G45) seems to specify it correctly (subsystem_id = 0x104382fe - seems I got the logic wrong before - LSB isn't set here and it works). regards Mario -- This project is so important we can't let things that are more important interfere with it. -- Advertising/Marketing manager, United Parcel Service |