Change History (11)
by , 18 years ago
Attachment: | blfs-bootscripts-20060910-alsapatch added |
---|
comment:1 by , 18 years ago
whoops, sorry for the double-attachment, I obviously don't have kde fully under control yet.
The patch changes the text on shutdown (all we do is save the volume), that's a question of taste. It also restores volume (using -F to help when alsa changes its controls on a kernel upgrade), which is the important thing. I've also added a link to start this from rcsysinit - maybe it would be better in only specific runlevels. At this stage, the patch deliberately doesn't alter the last-revised-by comment.
comment:2 by , 18 years ago
NAK. We are supposed to restore the volume from udev rules. Doesn't that work for you?
comment:3 by , 18 years ago
Type: | task → defect |
---|
comment:4 by , 18 years ago
This has either to be closed as invalid (because alsa bootscript isn't supposed to restore volume, it is the task for udev rules), or to be retitled to a more appropriate description of the problem.
comment:5 by , 18 years ago
Owner: | changed from | to
---|
I have a feeling that what is left of this one is a direct result of Ticket #2125. Ken, if you are still watching BLFS, can you comment on this? Thanks.
comment:6 by , 18 years ago
Status: | new → assigned |
---|
comment:7 by , 18 years ago
So, the only difference I see here from the udev rule is that Ken's change calls alsactl with -F and the udev rules call the particular device with %n.
Ken, I'm gonna leave this open until you comment. The udev rules have always done the right thing for me.
comment:8 by , 18 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Closing invalid. The alsa boot script should not restore volume. #2125 fixed volume restoration on boot by use of correct udev rules.
comment:9 by , 18 years ago
Sorry, I intended to look at this last weekend for my current build, but I forgot it. If your current udev rules restore the volume, the problem is solved, just not how I expected.
what I'm using