Package Details: oss-nonfree 4.2_2020-1

Git Clone URL: (read-only, click to copy)
Package Base: oss-nonfree
Description: Open Sound System UNIX audio architecture (including nonfree drivers)
Upstream URL:
Keywords: oss
Licenses: custom:4Front Commercial License
Conflicts: libflashsupport-oss, libflashsupport-oss-git, oss, oss-git
Provides: oss
Submitter: alexdw
Maintainer: alexdw
Last Packager: alexdw
Votes: 15
Popularity: 0.000001
First Submitted: 2013-06-23 13:17 (UTC)
Last Updated: 2020-12-29 17:36 (UTC)

Latest Comments

alexdw commented on 2020-12-29 17:38 (UTC)

@seawright Thanks! Updated (4.2_2020-1) for this new release - OSS v4.2 build 2020.

seawright commented on 2020-12-28 21:26 (UTC)

@alexdw New packages uploaded to: PKGBUILD requires updating. sha512sum oss-linux-v4.2-2020* 3161f86a85c5eb1d30400a11351ff8e88defd65a1f6eab6e7b0f63fa6efe8f66f641239df681de6430e83aea901cd2b6c1c1d887fb5073838662875431f06aab oss-linux-v4.2-2020-amd64.tar.bz2 0f649e8851ec12b3cde4dc65ebf593dcdeba724356c5eac1f96cbb52713db2e9574efb9c3ac843514e3b6754c94a2b139b9d07cb4aefb4acf78646fb77616cde oss-linux-v4.2-2020-i386.tar.bz2

alexdw commented on 2019-10-27 20:23 (UTC)

@seawright: I'm not sure it actually makes any difference in Arch Linux since around 2013:'s_Filesystem_Hierarchy_Standard_(FHS)?

seawright commented on 2019-10-27 10:30 (UTC) (edited on 2019-10-27 10:31 (UTC) by seawright)

@alexdw I am new to Arch Linux but have quickly realised that its ethos is different to that of other distributions. I am however perplexed that someone (or a general consensus) has deemed it necessary to move system programmes (as indicated by their appearance in section 8 of the man database) such as ossdetect and ossdevlinks from /usr/sbin to /usr/bin and wondered if you (or someone else) could explain the rationale behind that decision and whether it should still apply.

seawright commented on 2019-10-10 22:39 (UTC)

See my reply to Mowgli's post on Open Sound System forum:

alexdw commented on 2019-08-31 21:23 (UTC)

This suggests another upstream patch/release will be required to make oss work with 5.2+ kernels:

Midna commented on 2019-08-27 01:34 (UTC)

Please note that the current build of OSS v4 (OSS v4.2 build 2019) does not appear to function for 5.2+ kernels.

For oss-nonfree, the error happens during soundon. See error details at: The log actually lists every kernel module as being "invalid ELF objects", although this might not be the main culprit.

However, the package still works for the linux-lts kernel (currently 4.19.68-lts) up to 5.1+ kernels (tested for 5.1.19).

alexdw commented on 2019-04-22 17:54 (UTC)

Updated (4.2_2019-1) for new release - OSS v4.2 build 2019:

Now working again with Arch (kernel 5.0.8).

tedbell commented on 2018-02-26 09:30 (UTC)

Hi! I'm a novice to PKGBUILD. What I did was extract the source and replace the file in the source tarball. Then I updated the sums with makepkg -g >> PKGBUILD because updpkgsums didn't work. I tried doing it your way and the patch seemed to apply ok but I guess it didn't get packaged.

alexdw commented on 2018-02-25 16:16 (UTC)

I'll have a look, though generally I wouldn't want to modify the sources but instead include the patch itself and have the PKGBUILD apply that.

alexdw commented on 2018-02-25 16:14 (UTC)

@tedbell: Thanks! There should be information here on uploading to AUR: But if you prefer to email for me to do it, then I think my address is at the top of the PKGBUILD files (as Maintainer).

tedbell commented on 2018-02-25 16:13 (UTC)

I have the updated oss-linux-v4.2-2017-amd64.tar.bz2 with the patched osscore.c and a PKGBUILD with updated sums.

tedbell commented on 2018-02-25 16:07 (UTC)

I'm not set up for that and not sure how to do it. Can I email you the files somehow? I've compiled this one and I will do the same for oss and oss-git

alexdw commented on 2018-02-25 12:52 (UTC)

@tedbell: That would be great. Or if you're set up for AUR contributions you could commit it directly? In fact, I could add you as a Co-Maintainer if you want? I don't actively use these OSS packages since I switched to a sound card that had native ALSA support.

tedbell commented on 2018-02-25 03:09 (UTC)

I made a PKGBUILD and compiled with the patch from the link. Let me know if you want it.

alexdw commented on 2018-02-18 20:30 (UTC)

@tedbell: Thanks for the information. I'll have a look at adding this to the PKGBUILD if it isn't applied upstream soon.

tedbell commented on 2018-02-18 19:51 (UTC)

Will not compile under kernel 4.15

See here for patch:

alexdw commented on 2017-02-13 23:49 (UTC)

Updated (4.2_2017-1) for new release - OSS v4.2 Build 2017: Now working again with Arch kernel 4.8.

alexdw commented on 2016-12-21 23:54 (UTC)

Note: This does not work with Arch kernel 4.8 with default configuration due to new CONFIG_HARDENED_USERCOPY feature being enabled. Workaround would be to compile a custom kernel with CONFIG_HARDENED_USERCOPY disabled or alternately use oss or oss-git, which include a patch to avoid this issue (a similar patch does not appear to be possible for oss-nonfree as that code seems to be precompiled).

alexdw commented on 2016-06-14 23:34 (UTC)

Updated (4.2_2011-3) with a patch to allow compilation with 4.6 kernels.

alexdw commented on 2015-05-07 20:44 (UTC)

Updated (4.2_2011-2) with patch by "oss117" from OSS forums: This should fix the compile error for 4.x kernels (tested as working for 4.0.1).

alexdw commented on 2015-03-01 23:35 (UTC)

Updated (4.2_2011-1) for build 2011.

alexdw commented on 2014-10-05 23:20 (UTC)

I think the libflashsupport-oss issue should be fixed - all three (oss-nonfree, oss, oss-git) now have their own respective libflashsupport packages. I wasn't able to solve the permissions warnings though - seems to be for oss-nonfree only so I'm guessing something to do with the way the source file archive? As mentioned before it seems to work fine for me despite the warnings.

alexdw commented on 2014-09-09 05:30 (UTC)

@nuc: Thanks for checking and posting back. Yes I noticed it was a bit odd now that AUR does not allow all 3 of the base packages to have a "libflashsupport-oss". The reason why I left it as "libflashsupport-oss" in optdepends is I thought this would allow any of the 3 "libflashsupport-oss" to work, though thinking again you probably always want the one associated with the base package so I'll have a look at changing it in the way you suggest. I'm not sure about what is causing those warnings (I get them too but osstest seems to work), whether it's a new feature in AUR/makepkg or a change in file permissions in the OSS source archive. Nor do I know how to resolve them - do I need to change the directory permissions in the package somehow? I'll have a look at this while checking out the "libflashsupport-oss" issue. Again I'm travelling for work so it will be Friday before I can make any of these fixes.

nuc commented on 2014-09-08 23:50 (UTC)

Hi, thanks for the update. Some issues though: libflashsupport-oss is in optdepends but it should be libflashsupport-oss-nonfree. Also I needed to manually remove libflashsupport-oss first because it obviously pulls in oss, which in turn conflicts to oss-nonfree. So maybe oss-nonfree should also conflict to libflashsupport-oss (and oss to libflashsupport-oss-nonfree)? Kind of a mess :/ Also I got those warnings after updating: Warning: directory permissions differ for / usr / lib / oss / build / Filesystem: 755 package: 2755 Warning: directory permissions differ for / usr / lib / oss / lib / Filesystem: 755 package: 2755 Warning: directory permissions differ for / usr / lib / oss / etc / Filesystem: 755 package: 2755 Warning: directory permissions differ for / usr / lib / oss / scripts / Filesystem: 755 package: 2755 Warning: directory permissions differ for / usr / lib / oss / cuckoo / Filesystem: 755 package: 2755 It *think* it installed properly though.

alexdw commented on 2014-09-08 19:44 (UTC)

Updated (4.2_2010-4) for build 2010, some clean-up in the PKGBUILD as suggested by nuc (thank you!), use of mkaurball (for new .AURINFO requirement in AUR) and renaming libflashsupport-oss to not conflict with the other ones (seems to be another new AUR requirement).

nuc commented on 2014-09-03 01:41 (UTC)

@alexdw: Sure np :) About the licensing issue: There appeared to be another bug concerning proper registration, thats why I didn't answer. The dev told me he will probably get it fixed in the next release (build 2010 I guess).

alexdw commented on 2014-09-02 18:04 (UTC)

@nuc: Thanks for the new version notification. I'll have a look at updating the PKGBUILD to 2010 on Monday - I'm away travelling for work at the moment and won't have access to my primary (Linux) PC until then.

alexdw commented on 2014-05-08 19:42 (UTC)

@nuc: I've commented that line so it should now install to: /lib/modules/$KERNEL/kernel/oss/ instead of: /lib/modules/extramodules-$KERNEL/oss/ Please could you try applying your license with this new version? According to the comments below, this change was for consistency with the old community/oss package. If it works better without this I'll do the same with the oss and oss-git packages for consistency (so all will install to /lib/modules/$KERNEL/kernel/oss as oss seems to expect). Updated (4.2_2009-3) with the above change.

nuc commented on 2014-05-08 18:00 (UTC)

It appears this change makes a problem: # make OSS install its modules to /usr/lib/modules/$KERNEL/extramodules/oss When I tried to apply my bought oss license, there was an error: # osslic /tmp/N12345678.asc /lib/modules/3.13.8-1-ARCH/kernel/oss/osscore.ko: No such file or directory It appears that arch installed the osscore.ko file into /lib/modules/extramodules-3.13-ARCH/oss/osscore.ko Could you please fix this alex? Thanks in Advance!

alexdw commented on 2014-04-06 01:37 (UTC)

Thanks for letting me know seschwar. I had a quick search and found a similar compilation error resolved here: Looks like the issue is caused by this: OSS is expecting uid_t but kernel is returning kuid_t instead. So I've added a very simple patch (linux-3.14.0.patch) to convert the return value back to uid_t. Updated version (4.2_2009-2) works for me now (osstest runs fine) with 3.14.0 kernel in testing repos (3.14.0-3-ARCH).

seschwar commented on 2014-04-02 11:22 (UTC)

Does not work on linux-3.14: # sh /usr/lib/oss/build/ OSS build environment set up for REGPARM kernels Building module osscore Failed to compile OSS make -C /usr/lib/modules/3.14.0-1-ARCH/build M=/usr/lib/oss/build modules make[1]: Entering directory '/usr/lib/modules/3.14.0-1-ARCH/build' CC [M] /usr/lib/oss/build/osscore.o /usr/lib/oss/build/osscore.c: In function ‘oss_get_uid’: /usr/lib/oss/build/osscore.c:476:3: error: incompatible types when returning type ‘kuid_t’ but ‘int’ was expected return current->cred->uid; ^ /usr/lib/oss/build/osscore.c: In function ‘alloc_fop’: /usr/lib/oss/build/osscore.c:1002:14: warning: assignment from incompatible pointer type [enabled by default] fop->fsync = oss_no_fsync; ^ /usr/lib/oss/build/osscore.c: In function ‘oss_pci_read_devpath’: /usr/lib/oss/build/osscore.c:1676:3: warning: return discards ‘const’ qualifier from pointer target type [enabled by default] return dev_name(&dip->pcidev->dev); ^ /usr/lib/oss/build/osscore.c: In function ‘oss_get_uid’: /usr/lib/oss/build/osscore.c:480:1: warning: control reaches end of non-void function [-Wreturn-type] } ^ scripts/ recipe for target '/usr/lib/oss/build/osscore.o' failed make[2]: *** [/usr/lib/oss/build/osscore.o] Error 1 Makefile:1274: recipe for target '_module_/usr/lib/oss/build' failed make[1]: *** [_module_/usr/lib/oss/build] Error 2 make[1]: Leaving directory '/usr/lib/modules/3.14.0-1-ARCH/build' Makefile:16: recipe for target 'default' failed make: *** [default] Error 2

alexdw commented on 2014-03-30 23:09 (UTC)

Updated (4.2_2009-1) for the new version (OSS v4.2 build 2009): The only changes in the PKGBUILD is to link to new file and to remove the kernel version-specific patches (as they all appear to be applied in the new build already).

alexdw commented on 2013-11-05 07:38 (UTC)

Tested as working for me on 3.11.6 (latest kernel version in the main repos as of now).

moscwich commented on 2013-11-04 07:58 (UTC)

Please patch for 3.11

alexdw commented on 2013-09-27 23:29 (UTC)

Thank you again seschwar. Updated (4.2_2008-9) with your latest PKGBUILD.

seschwar commented on 2013-09-26 13:52 (UTC)

I my previous modification of the PKGBUILD I accidentally dropped the change to make OSS install its modules in Arch's correct location. This PKGBUILD fixes that and makes OSS install its modules to /usr/lib/modules/$KERNEL/extramodules/oss, where they belong:

seschwar commented on 2013-08-26 15:01 (UTC)

Yes, it always worked for me. Do you have libflashsupport-oss installed? What is the output of ls -l /usr/lib/ /usr/lib/oss/lib/

dflt commented on 2013-08-26 14:03 (UTC)

Does Flash plugin in Firefox works for anybody? If flash has audio I always get "Pluging crashed" message before any audio starts to play.

seschwar commented on 2013-08-26 13:38 (UTC)

I have to perfect my PKGBUILD a bit: It's probably not a bad idea for the lib/modules sed to be idempotent. You could change the respective line to: grep -IlrZ '\<lib/modules\>' . | xargs -0 sed -i 's,\<\(usr/\)\?lib/modules\>,usr/&,g' -- And FTR, I also noticed that the package installs its modules to /usr/lib/modules/`uname -r`/kernel/oss instead of /usr/lib/modules/extramodules-*-ARCH/kernel/oss, like the community/oss package did. This is not really a big deal. I just had to search a bit, when fiddling with OSS.

alexdw commented on 2013-08-24 15:51 (UTC)

Updated (4.2_2008-8) to apply the latest kernel patch for 3.10.7 and above (instead of just for 3.11 and above):

alexdw commented on 2013-08-24 15:29 (UTC)

Updated (4.2_2008-7) with seschwar's cleaned up PKGBUILD file. Thanks seschwar - it's much improved and easier to understand and maintain.

seschwar commented on 2013-08-24 13:14 (UTC)

I cleaned up the PKGBUILD significantly: - more concise definition of architecture dependent source and md5sums arrays - use build() and package() correctly - remove any comments inherited from original community/oss PKGBUILD - build and install - use noextract and then bsdtar xf the source tarball in package(); bsdtar is in libarchive, which is a dependency of pacman - download linux-3.*.patch from OpenSound forum; they can be dropped from the source tarball - more concise usr-move fixes - build libflashsupport-oss split package, since it doesn't hurt - remove superfluous quoting - remove superfluous curly braces in variable names - add a few comments All this makes for a cleaner and much more readable PKGBUILD, which makes it easier to use.

talonz commented on 2013-08-18 22:26 (UTC)

yeah the ossvermagic fix by DrQwertySilence is a blessing no my mpd daemon starts automatically thanks and thanks for the update alexdw

alexdw commented on 2013-08-17 00:05 (UTC)

Updated (4.2_2008-6) with the patch klothius linked to below found on the OSS forums: This seems to fix the issue with 3.10.7 (at least in my VirtualBox install). Also amended soundon to not use ossvermagic as described by DrQwertySilence (thanks!). This might cause issues if you're using old (i.e. 2.6 or earlier) kernel versions but I've left the replaced line as a comment so it's an easy modification if required. In 3.10.6 and 3.10.7 this has significantly increased the speed of soundon (from around a couple of minutes to less than a couple of seconds).

talonz commented on 2013-08-16 01:42 (UTC)

i think the latest kernel update broke oss again 3.10.7-1-ARCH sudo soundon modprobe: ERROR: could not insert 'osscore': Exec format error Loading the osscore module failed

commented on 2013-08-09 03:04 (UTC)

If 'soundon' is taking more time that the normal (like 20s instead of 0.2s) to run oss, is the fault of 'ossvermagic', this return nothing and take 20s to do this. Replace: KERNEL_VERMAGIC=`/usr/bin/ossvermagic -z -s` With: KERNEL_VERMAGIC="" <- or whatever ossvermagic is returning

alexdw commented on 2013-07-29 22:25 (UTC)

Yeah, I saw this, thanks for reminding me about it. As far as I can tell though, 3.11 is not yet in the Testing repo - I'll have a look at using the patch to fix this once it is.

klothius commented on 2013-07-28 22:36 (UTC)

Well 3.11 brings another breakage, but luckily it seems there's already a patch on oss forums ->

alexdw commented on 2013-07-06 13:50 (UTC)

Updated with the 3.10 kernel patch found on the OSS forums: Tested and working for me with both the (x86_64) 3.10 kernel in the Testing repo and the 3.9.9 kernel in Core.

alexdw commented on 2013-07-04 22:10 (UTC)

Thanks for the heads-up klothius. I will look at updating this to work with the 3.10 kernel over this weekend.

klothius commented on 2013-07-01 15:20 (UTC)

Hi, linux kernel 3.10 changed things again and again oss fails to relink the modules because of it. There is already a patch in oss forum - The patch on the page isn't working properly(malformed patch or whatever), but here is a fixed up one - It now relinks modules properly.