First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 121329
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Gentoo Sound Team <sound@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Dave Andruczyk <djandruczyk@yahoo.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 121329 depends on: Show dependency tree
Bug 121329 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2006-02-02 11:05 0000 
When attempting to emerge alsa driver it complains about the PM_LEGACY feture
being turned off in the kernel (my kernel is 2.6.16_rc1).  According to ALSA's
Changelog for 1.0.11rc3 this kernel feature is no longer required...

Snippet from alsa's site for the 1.0.11_rc3 changelog:
http://alsa-project.org/changes/v1-0-11rc2--v1-0-11rc3.txt
+ ALSA Core
    - Fix compile on 2.6.15 without CONFIG_PM_LEGACY


This also applies to later kernels (tested with 2.6.16_rc1)
Commenting out that section in the ebuild and issuing "emerge
alsa-driver-1.0.11_rc3.ebuild digest" and then emerging alsa-driver installed
without a hitch, and functions fine.  It seems that the PM_LEGACY check  is not
longer necessary and can be removed entirely.

------- Comment #1 From Diego E. 'Flameeyes' Pettenò 2006-02-02 11:16:55 0000 ------- 
Yep sorry I forgot to remove it, I knew it was going to go away. Fixed now.
First Last Prev Next    No search results available      Search page      Enter new bug