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:

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...

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?

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?