Oss-v4.0-1015 installation crashes on SXDE snv_87
Posted: 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...
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...