FS#35491 - [oss] vermagic check error when enabling
Attached to Project:
Community Packages
Opened by Chris Shake (cshake) - Monday, 27 May 2013, 01:21 GMT
Last edited by Kyle Keen (keenerd) - Wednesday, 25 September 2013, 11:37 GMT
Opened by Chris Shake (cshake) - Monday, 27 May 2013, 01:21 GMT
Last edited by Kyle Keen (keenerd) - Wednesday, 25 September 2013, 11:37 GMT
|
Details
Description:
When /usr/sbin/soundon is run it calls /usr/sbin/ossvermagic to check that the modules to be loaded were built for the current kernel. This program runs for over a minute, spawning many shell scripts that appear to unzip all sorts of modules and run something on them, then finally returns an empty string. It then runs on the oss modules and also returns an empty string. This means that the it compares the two strings (both empty) and with them equal, no matter what version of modules they will be loaded even if they're not actually the same. It also wastes a lot of cycles every time the sound system turns on. Additional info: * package version(s) oss 4.2_2007-2 for x86-64 (assuming same for i686) * config and/or log files etc. Steps to reproduce: $> soundoff && soundon watch the processor churn for a while, notice that /var/log/soundon.log has lines up through the echo on line 36 of /usr/sbin/soundon, but not line 38, so the command on line 37 must still be running. Manually run that command to verify. Acknowledge that this is probably an upstring bug, but since the upstream version hasn't changed in 6 years... if there is an easy way to check what version the module is built for, the soundon script can be changed to use that instead and just ignore ossvermagic (which is a binary). |
This task depends upon
Closed by Kyle Keen (keenerd)
Wednesday, 25 September 2013, 11:37 GMT
Reason for closing: Won't fix
Additional comments about closing: OSS has been moved to AUR.
Wednesday, 25 September 2013, 11:37 GMT
Reason for closing: Won't fix
Additional comments about closing: OSS has been moved to AUR.
FS#33969was filed; specifically:- https://bugs.archlinux.org/task/33969#comment106309
- https://bugs.archlinux.org/task/33969#comment107176