OSS v4.2 build 2004 - looking GOOD!

OSS specific Solaris discussion (x86/SPARC)

Moderators: hannu, dev, cesium, kodachi

OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Fri Jan 07, 2011 12:27 am

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 Sound!

Thank you!
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Tue Jan 11, 2011 4:21 pm

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 that when boot archive is updated upon reboot, oss attaches normally. A reconfigure reboot (boot -r or reboot -- -r) often gets oss to attach properly. Without attachment, osstest will still work, but other sounds will not play, as has been the case for years. "ossdetect" placed at the end of /etc/profile does not solve the problem. If ossdetect is run as root, then oss will attach for subsequent logins by any user. How can I get ossdetect to be run automatically by the system after each reboot?

Other times, oss behaves perfectly after reboot. :?
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby dev » Wed Jan 12, 2011 10:36 pm

rasta wrote: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 that when boot archive is updated upon reboot, oss attaches normally. A reconfigure reboot (boot -r or reboot -- -r) often gets oss to attach properly. Without attachment, osstest will still work, but other sounds will not play, as has been the case for years. "ossdetect" placed at the end of /etc/profile does not solve the problem. If ossdetect is run as root, then oss will attach for subsequent logins by any user. How can I get ossdetect to be run automatically by the system after each reboot?

Other times, oss behaves perfectly after reboot. :?



Hi,


Try this: edit /etc/init.d/oss and add sleep 10 before the soundon command in the start) section. What happens after reboot is Solaris calls modunload -i 0 and this unloads all modules not currently in use. The problem with oss is that it's the framework (osscore/sadasupport/etc) that creates all the device nodes - not the driver - and if the framework gets loaded after the driver then no device nodes get reattached.



regards
Dev
dev
 
Posts: 577
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Thu Jan 13, 2011 9:26 pm

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!
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Tue Jan 18, 2011 7:19 pm

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/oss.conf
else
OSSLIBDIR=/usr/lib/oss
fi

##########
#
# The first argument tells what to do.
##########

state=$1

if test -f /etc/oss.conf
then
. /etc/oss.conf
else
OSSLIBDIR=$OSSLIBDIR
fi

case $state in

'start')
soundoff
sleep 10
soundon
exit 0
;;
'stop')
/usr/sbin/savemixer > /dev/null 2>&1
exit 0
;;
esac

exit 1
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Mon Jan 24, 2011 4:33 pm

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 will not
prevent intentional unloads of modules by an end-user, but it will
prevent automatic unloads of modules that are not in use.

-- Garrett"

I hope this helps.

********************************

Did you try that? It appears that you and the oss team knows what the problem is with the modules unloading, but are either uninterested, incapable, or too busy to fix it. Please prove me wrong.
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby dev » Wed Jan 26, 2011 11:50 pm

rasta wrote: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 will not
prevent intentional unloads of modules by an end-user, but it will
prevent automatic unloads of modules that are not in use.

-- Garrett"

I hope this helps.

********************************

Did you try that? It appears that you and the oss team knows what the problem is with the modules unloading, but are either uninterested, incapable, or too busy to fix it. Please prove me wrong.



the problem is that osscore handles the device creation and it's a "framework" pseudo driver - hence ddi-no-autodetach will not work for osscore. - it only works for actual drivers - in OSS - drivers do not create the device nodes - they simply attach/detach the physical device.


The only real way is for solaris to implement nodetach to pseudo drivers.


(look at osscore.conf - it's parent is "pseudo". while any othe driver eg sblive.conf has the parent as pci.)


this problem has been solved by boomer in Solaris 11.

regards
Dev
dev
 
Posts: 577
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Fri Jan 28, 2011 3:57 pm

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 independent from Oracle?
Last edited by rasta on Thu Feb 17, 2011 5:41 pm, edited 1 time in total.
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Wed Feb 02, 2011 5:59 pm

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 (meaning for Solaris 10, too)? Or maybe this property is exported elsewhere under Solaris 10?

Hope this helps. Please pass this info no to the oss developers, who may not read this forum.
Last edited by rasta on Thu Feb 17, 2011 5:40 pm, edited 1 time in total.
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby dev » Mon Feb 14, 2011 9:59 pm

rasta wrote: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 autodetech is run regardless of OS (meaning for Solaris 10, too)? Or maybe this property is exported elsewhere under Solaris 10?

Hope this helps. Please pass this info no to the oss developers, who may not read this forum.



Hi,


I've added the patch to the latest sources - I tested this on Solaris 10 sparc and it seemed to work.
dev
 
Posts: 577
Joined: Fri Sep 12, 2003 6:08 am
Location: Culver City, CA

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Thu Feb 17, 2011 5:39 pm

GREAT!!!!!!!!!!!!!!!! Thank you very much for making the change. :D
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby Egorio » Thu Sep 01, 2011 2:51 pm

dev wrote:I've added the patch to the latest sources - I tested this on Solaris 10 sparc and it seemed to work.

gsm signal booster for home review at wiki.
Looking for gsm repeater. Check it
Last edited by Egorio on Mon Mar 10, 2014 9:37 am, edited 3 times in total.
Egorio
 
Posts: 1
Joined: Thu Sep 01, 2011 2:44 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby rasta » Mon Sep 19, 2011 5:07 pm

So far, it looks like v4.2 build 2005 solves all problems related to attaching on Solaris 10 x86! Good job, 4front!!! :D
rasta
 
Posts: 33
Joined: Mon Oct 19, 2009 9:17 pm

Re: OSS v4.2 build 2004 - looking GOOD!

Postby vixcin » Fri Dec 02, 2011 4:27 am

From what I could understand, the main issue here that you are experiencing is nothing other than the fact that ossscores are handling the device creation apparently. And since it is a framework pseudo driver, only drivers which are actual can work. Audiodetach won’t work in this case, I’m afraid.
“Read Today, Lead Tomorrow”
vixcin
 
Posts: 4
Joined: Mon Nov 28, 2011 5:35 am

Re: OSS v4.2 build 2004 - looking GOOD!

Postby ColoWin » Fri Dec 23, 2011 4:39 pm

vixcin wrote:From what I could understand, the main issue here that you are experiencing is nothing other than the fact that ossscores are handling the device creation apparently. And since it is a framework pseudo driver, only drivers which are actual can work. Audiodetach won’t work in this case, I’m afraid.

Looks like you're right
____________________
watch video about 3g booster
http://www.artwiki.fr/wakka.php?wiki=GSMSignalBooster
ColoWin
 
Posts: 1
Joined: Fri Dec 23, 2011 4:38 pm


Return to Solaris

Who is online

Users browsing this forum: No registered users and 2 guests