Oss-v4.0-1015 installation crashes on SXDE snv_87

OSS specific Solaris discussion (x86/SPARC)

Moderators: hannu, dev, kodachi, cesium

Oss-v4.0-1015 installation crashes on SXDE snv_87

Postby l33tmmx » Fri May 16, 2008 1:27 pm

I tried to install OSS drivers (v4.0-1015) to my HP Omnibook XE4100 laptop, running Solaris Express Developer Edition snv_87 (Solaris 11), but the installation crashed, and almost trashed my whole system (Similar type of error as here:, in other thread.

After some difficulties, I managed to boot the system, with some error messages about network/rpc-bind and network/security/ktkt_warn. CDE login starts, but I'm unable to log in to the graphical desktop, so I'm now stuck on command line console.

I managed to save some of the oss installation output before the whole machine froze:

/usr/sbin/osslic
/usr/sbin/ossupdate
/usr/sbin/savemixer
[ verifying class <none> ]
[ verifying class <drvcfg> ]
## Executing postinstall script.
Setting up Open Sound System....please wait
add_drv -m '* 0666 root sys' osscore
add_drv -m '* 0666 root sys' -i '"pci1106,3058"' via97

(At this point the installation froze for several minutes, until I pressed Ctrl-C)

^Cadd_drv -m '* 0666 root sys' -i '"pci1106,3058"' via97
Installing OSS (via97) failed
rm: Cannot map /lib/ld.so.1

Installation of <oss> was terminated due to user request.
pkgadm: Cannot map /lib/ld.so.1
pkgadd: ERROR: ERROR: Unable to release package administration lock for this system; try again later
rm: Cannot map /lib/ld.so.1
pkgadm: Cannot map /lib/ld.so.1
pkgadd: ERROR: ERROR: Unable to release package administration lock for this system; try again later
BASH-3.2# pkgrm oss

(And here the whole computer froze, so I had to forcibly power it off)

The sound chip is, according to scanpci:
pci bus 0x0000 cardnum 0x11 function 0x05: vendor 0x1106 device 0x3058 VIA Technologies, Inc. VT82C686 AC97 Audio Controller

I removed the package adm. lock mentioned above, tried to reinstall, which failed with some error message I was unable to see, because the output on console went by so fast... Of course, pkgrm oss doesn't work, because the package wasn't installed properly in the first place.

I now need someone to guide me through the steps to
1) remove the cruft the failed install left on my system
2) restore my system to a working state

I REALLY, REALLY hope that I don't need to resort to reinstalling everything, as the person in the mentioned other thread...
l33tmmx
 
Posts: 3
Joined: Fri May 16, 2008 4:09 am
Location: Finland

Removing cruft

Postby dhollister » Sat May 17, 2008 2:45 am

I wish I had an answer about why the install was failing, but there's not much info to go on. If you had some /var/adm/messages output, that might help.

Anyway, here's what you can do to get your system back to where it was.

First off, you'll want to remove the drivers that got installed. It looks like the only ones may have been osscore and via97... So, as root:

# rem_drv via97
# rem_drv osscore

Now, make sure all the files in the package are removed. I'm not sure of an easy way to know what files are in the package if it's not installed, but here's the list from my system (build 1015):

etc/oss/devices.list
etc/oss/forceload.conf
etc/oss/userdefs
etc/oss/version.dat
kernel/drv/ali5455
kernel/drv/ali5455.conf
kernel/drv/allegro
kernel/drv/allegro.conf
kernel/drv/als300
kernel/drv/als300.conf
kernel/drv/als4000
kernel/drv/als4000.conf
kernel/drv/amd64/ali5455
kernel/drv/amd64/allegro
kernel/drv/amd64/als300
kernel/drv/amd64/als4000
kernel/drv/amd64/apci97
kernel/drv/amd64/atiaudio
kernel/drv/amd64/audigyls
kernel/drv/amd64/audioloop
kernel/drv/amd64/audiopci
kernel/drv/amd64/cmi8788
kernel/drv/amd64/cmpci
kernel/drv/amd64/cs4280
kernel/drv/amd64/cs4281
kernel/drv/amd64/digi32
kernel/drv/amd64/digi96
kernel/drv/amd64/emu10k1x
kernel/drv/amd64/envy24
kernel/drv/amd64/envy24ht
kernel/drv/amd64/fm801
kernel/drv/amd64/geode
kernel/drv/amd64/hdaudio
kernel/drv/amd64/ich
kernel/drv/amd64/imux
kernel/drv/amd64/lynxtwo
kernel/drv/amd64/maestro
kernel/drv/amd64/neomagic
kernel/drv/amd64/osscore
kernel/drv/amd64/ossusb
kernel/drv/amd64/riptide
kernel/drv/amd64/s3vibes
kernel/drv/amd64/sadasupport
kernel/drv/amd64/sblive
kernel/drv/amd64/sbxfi
kernel/drv/amd64/softoss
kernel/drv/amd64/solo
kernel/drv/amd64/sonorus
kernel/drv/amd64/trident
kernel/drv/amd64/via8233
kernel/drv/amd64/via97
kernel/drv/amd64/vmix
kernel/drv/amd64/vortex
kernel/drv/amd64/ymf7xx
kernel/drv/apci97
kernel/drv/apci97.conf
kernel/drv/atiaudio
kernel/drv/atiaudio.conf
kernel/drv/audigyls
kernel/drv/audigyls.conf
kernel/drv/audioloop
kernel/drv/audioloop.conf
kernel/drv/audiopci
kernel/drv/audiopci.conf
kernel/drv/cmi8788
kernel/drv/cmi8788.conf
kernel/drv/cmpci
kernel/drv/cmpci.conf
kernel/drv/cs4280
kernel/drv/cs4280.conf
kernel/drv/cs4281
kernel/drv/cs4281.conf
kernel/drv/digi32
kernel/drv/digi32.conf
kernel/drv/digi96
kernel/drv/digi96.conf
kernel/drv/emu10k1x
kernel/drv/emu10k1x.conf
kernel/drv/envy24
kernel/drv/envy24.conf
kernel/drv/envy24ht
kernel/drv/envy24ht.conf
kernel/drv/fm801
kernel/drv/fm801.conf
kernel/drv/geode
kernel/drv/geode.conf
kernel/drv/hdaudio
kernel/drv/hdaudio.conf
kernel/drv/ich
kernel/drv/ich.conf
kernel/drv/imux
kernel/drv/imux.conf
kernel/drv/lynxone.conf
kernel/drv/lynxtwo
kernel/drv/lynxtwo.conf
kernel/drv/maestro
kernel/drv/maestro.conf
kernel/drv/neomagic
kernel/drv/neomagic.conf
kernel/drv/osscore
kernel/drv/osscore.conf
kernel/drv/ossusb
kernel/drv/ossusb.conf
kernel/drv/riptide
kernel/drv/riptide.conf
kernel/drv/s3vibes
kernel/drv/s3vibes.conf
kernel/drv/sadasupport
kernel/drv/sadasupport.conf
kernel/drv/sblive
kernel/drv/sblive.conf
kernel/drv/sbxfi
kernel/drv/softoss
kernel/drv/softoss.conf
kernel/drv/solo
kernel/drv/solo.conf
kernel/drv/sonorus
kernel/drv/sonorus.conf
kernel/drv/trident
kernel/drv/trident.conf
kernel/drv/via8233
kernel/drv/via8233.conf
kernel/drv/via97
kernel/drv/via97.conf
kernel/drv/vmix
kernel/drv/vmix.conf
kernel/drv/vortex
kernel/drv/vortex.conf
kernel/drv/ymf7xx
kernel/drv/ymf7xx.conf
kernel/misc/amd64/osscommon
kernel/misc/osscommon
usr/bin/ossinfo
usr/bin/ossmix
usr/bin/ossplay
usr/bin/ossrecord
usr/bin/osstest
usr/bin/ossxmix
usr/include/sys/soundcard.h
usr/man/man1/ossinfo.1
usr/man/man1/ossmix.1
usr/man/man1/ossplay.1
usr/man/man1/ossrecord.1
usr/man/man1/osstest.1
usr/man/man1/ossxmix.1
usr/man/man1m/ossdetect.1m
usr/man/man1m/ossdevlinks.1m
usr/man/man1m/savemixer.1m
usr/man/man1m/soundoff.1m
usr/man/man1m/soundon.1m
usr/man/man7d/ali5455.7d
usr/man/man7d/allegro.7d
usr/man/man7d/als300.7d
usr/man/man7d/als4000.7d
usr/man/man7d/apci97.7d
usr/man/man7d/atiaudio.7d
usr/man/man7d/audigyls.7d
usr/man/man7d/audioloop.7d
usr/man/man7d/audiopci.7d
usr/man/man7d/cmi8788.7d
usr/man/man7d/cmpci.7d
usr/man/man7d/cs4280.7d
usr/man/man7d/cs4281.7d
usr/man/man7d/digi32.7d
usr/man/man7d/digi96.7d
usr/man/man7d/dsp.7d
usr/man/man7d/emu10k1x.7d
usr/man/man7d/envy24.7d
usr/man/man7d/envy24ht.7d
usr/man/man7d/fm801.7d
usr/man/man7d/geode.7d
usr/man/man7d/hdaudio.7d
usr/man/man7d/ich.7d
usr/man/man7d/imux.7d
usr/man/man7d/lynxone.7d
usr/man/man7d/lynxtwo.7d
usr/man/man7d/maestro.7d
usr/man/man7d/midi.7d
usr/man/man7d/mixer.7d
usr/man/man7d/neomagic.7d
usr/man/man7d/osscore.7d
usr/man/man7d/ossusb.7d
usr/man/man7d/riptide.7d
usr/man/man7d/s3vibes.7d
usr/man/man7d/sadasupport.7d
usr/man/man7d/sblive.7d
usr/man/man7d/sndstat.7d
usr/man/man7d/softoss.7d
usr/man/man7d/solo.7d
usr/man/man7d/sonorus.7d
usr/man/man7d/trident.7d
usr/man/man7d/via8233.7d
usr/man/man7d/via97.7d
usr/man/man7d/vmix.7d
usr/man/man7d/vortex.7d
usr/man/man7d/ymf7xx.7d
usr/sbin/ossdetect
usr/sbin/ossdevlinks
usr/sbin/osslic
usr/sbin/ossupdate
usr/sbin/savemixer

So, you could probably just do something like this, where "filename" is a file you created with that list of files up above.

#!/bin/bash
for file in `cat filename`
rm -f ${file}
done

Then reboot. Hopefully, that will do it.
dhollister
 
Posts: 9
Joined: Wed May 14, 2008 1:59 pm

Postby l33tmmx » Sat May 17, 2008 11:27 am

Strange, I don't have any of the mentioned files on my system... Maybe pkgadd removed the files it had installed when I interrupted the installation? (No, I don't really know how pkgadd works, I'm just guessing. I have used Solaris for about 3 months now, but have about 8 years of Linux experience)

The whole /var/adm/messages file is too long to be included here, but the relevant part can be read here, starting from when I inserted the USB stick where I copied the installation file from, to when I finally closed the machine down and went to sleep ;). I hope someone finds something useful there.

Well, I still get the rpcbind failure messages, the gui doesn't start, so I'm afraid that the only real option is to reinstall... unless any of you have a better idea?

One more question: if I compile the oss drivers from sources, does it use the same install script as the package?; I mean, is there a possibility that it could freeze my system similar way as when installing the package?
l33tmmx
 
Posts: 3
Joined: Fri May 16, 2008 4:09 am
Location: Finland

Postby cesium » Sat May 17, 2008 11:37 am

The source install doesn't look the same as the package install, but since we don't know what crashed the system, it may still crash it.
cesium
 
Posts: 903
Joined: Sun Aug 12, 2007 12:51 am

Install trouble

Postby dhollister » Sat May 17, 2008 3:21 pm

First off, there should be no reason to reinstall, unless you enjoy the process ;-)

I didn't see anything in the messages file that would indicate that your trouble has anything to do with oss.

There were several warnings in the messages file about driver names with no aliases. I'd check the associated line numbers in /etc/driver_aliases.

If you'd like, you can point me to your /etc/driver_aliases and the /var/svc/log/... files as provided in the "svcs -xv" output and I'll have a look.


l33tmmx wrote:Strange, I don't have any of the mentioned files on my system... Maybe pkgadd removed the files it had installed when I interrupted the installation? (No, I don't really know how pkgadd works, I'm just guessing. I have used Solaris for about 3 months now, but have about 8 years of Linux experience)

The whole /var/adm/messages file is too long to be included here, but the relevant part can be read here, starting from when I inserted the USB stick where I copied the installation file from, to when I finally closed the machine down and went to sleep ;). I hope someone finds something useful there.

Well, I still get the rpcbind failure messages, the gui doesn't start, so I'm afraid that the only real option is to reinstall... unless any of you have a better idea?

One more question: if I compile the oss drivers from sources, does it use the same install script as the package?; I mean, is there a possibility that it could freeze my system similar way as when installing the package?
dhollister
 
Posts: 9
Joined: Wed May 14, 2008 1:59 pm


Return to Solaris

Who is online

Users browsing this forum: No registered users and 1 guest