Open Sound System

So far, it looks like v4.2 build 2005 solves all problems related to attaching on Solaris 10 x86! Good job, 4front!!!

GREAT!!!!!!!!!!!!!!!! Thank you very much for making the change.

Cesium noticed that the oss source adds a 'ddi-no-autoattach' line under Solaris 9: [code="setup/SunOS/confgen.c"]#ifdef SOL9 fprintf (conf, "ddi-no-autodetach=1 ddi-forceattach=1 \n"); #endif[/code] Would removing the ifdef help so that the autodetach is run regardless of OS (me...

Dev, Thank you for the info. I guess it is just a basic incompatibility between Solaris 10 and oss 4.2. It is still more or less random if oss will attach properly to Solaris, but an ossdetect and a reboot or two usually gets oss working. Is Solaris 11 the same as opensolaris? Is opensolaris indepen...

Dev, I posted this in this forum a while back: ********************* Dev, Here is some info about the unloading from the opensolaris opensound forum: "One way to help reduce the chance of modunload -i 0 from auto-unloading modules is to export a property -- "ddi-no-autodetach". This w...

Dev, The behavior I'm getting now (with "sleep 10" added to /etc/init.d/oss) is that upon first boot, oss will not attach, but if I simply reboot, it will attach. Below is the edited oss script. Did I edit it correctly? > cat /etc/init.d/oss #!/bin/sh if test -f /etc/oss.conf then . /etc/o...

Dev,

Thank you very much for the tip. I've implemented it, and I've had perfect attachment on 2 boots in a row. I'll keep you posted. I'm lovin' build 2004 so far!

Cheers!

Hi, Get OSS 4.2 build 2004 - adding the devfsadm to the soundon scripts helps fix the disappearing devlinks problem. The root cause of the links disappearing is that moduload -i 0 is called at the end of boot up and it knocks out the device links of all device drivers that are not in use. Are you s...

Using Solaris 10 u8 x64 on Intel hardware (using Host Driver: Windows DirectSound, Controller: ICH AC97 for VirtualBox 4.0.0 guest), build 2004 will still attach only intermittently. Workarounds are needed to get oss to function normally. DEFINITIVE step-by-step instructions are needed. It seems tha...

OSS 4.2 build 2004 installed perfectly on Solaris 10 u8 x64. However, adding "ossdetect" without quotes to the end of /etc/profile was necessary to get oss to attach properly. After doing that, oss works great, even after a reboot. I'll post again if I run into any problems. Good job, Open...

This build will not attach to Solaris 10 x86, which was the case with build 2002. OSS is still not properly functional for Solaris 10, as has been documented extensively in the Solaris forums. Please fix.

Dev, Here is some info about the unloading from the opensolaris opensound forum: "One way to help reduce the chance of modunload -i 0 from auto-unloading modules is to export a property -- "ddi-no-autodetach". This will not prevent intentional unloads of modules by an end-user, but it...

Dev, He IS using Solaris 10. OSS 4.2 b2002 will not attach to Solaris 10, as myself and others have documented extensively in this forum and in the thread for the release announcement. Even the install of this oss build will fail unless a directory is manually made by the user prior to install. Your...

Rolf, Thank you for the tip. Making that directory makes the install run smoothly. However, oss 4.2 b2002 still will not attach to Solaris 10 after install, as has been noted by several users in the Solaris forum. Other manual fixes have been suggested by Vitaly, but even with them, oss on Solaris 1...

pkgrm -A was the only way I knew to get oss to uninstall, as pkgrm oss did not work. In the future, how should I uninstall oss if pkgrm (without -A) fails?