Solaris

Thanks very much for the reply. All excellent suggestions. Unfortunately, the drivers are nowhere to be found on my system. However, in a stroke of amazing luck, I just got a very nice reply to the email I sent from a gentleman at techsource who said they removed the drivers from their web site due to lack of interest. He put them back up temporarily just for me, so now I've finally got the official files I need to do this install.

I have some other stuff to do today but I'll report back with the reaults once I get going on it.

Good news Michele. It's like they always say "Where there's a shell there's a way"

Well looks like I spoke too soon. This is going from bad to worse. I installed the drivers from Techsource and now I can't even start the gnome windowing system. If I let the machine boot, I end up at a blank X-windows screen with an "X" cursor. If I login with root, stop the gui login with ^C and do a gfcconfig -i, it says "No valid TSI devices found! Exiting".

I may have brought this on myself because during the driver install it complained about some other mystery package I don't have called "SUNWowrqd " being required.

So now I have a real mess on my hands. How do I get back to just being able to login to the Sun Java desktop?

The easiest way to go back is to boot from cd and restore the filesystem from backup but, before you do that, let's try and move forward.

Firstly, after putting the driver on, did you tell the kernel to reconfigure?

Code:

 
boot -r

Previous discussions on the web indicate that the new graphics adapter won't be seen until the kernel reconfigures.

( you could also add the 'verbose' switch to the boot command to see if it tells you anything you didn't already know as it boots.

Code:

 
boot -rv

)

I assume that you now have two graphics adapters in the system? Are you saying that, if you connect monitors to both adapters, that you don't get the GUI on either?

One of the links I provided previously explained how to tell the service processor about the new adapter and switch off the old one. (I assume the old one is on-board so can't be taken out?)

Remember to try kernel reconfigure after each of these (no harm in repeatedly telling Solaris to reconfigure).

Try installing the missing package from the distribution CD/DVD. It might just be on the media. If not Google for it. Post if you can't find it.

Good suggestions. Here's the details - this install was apparently doomed form the start because while executing the GFX install_all script I got this message:

Code:

Installing Raptor GFX-C System Software/Device Driver v1.4 as <TSIgfc>

## Installing part 1 of 1.
/a/platform/sun4u/kernel/drv/gfxc
[ verifying class <none> ]
## Executing postinstall script.
No such file or directory
Cnnot access file (/a/etc/minor_perm).

Failed add_drv!

pkginstall: ERROR: postinstall script did not complete successfully

Installation of <TSIgfc> on zone <bristol-jes> failed.
## Restoring state of global zone <bristol-jes>

I continued on anyway in the hope that everything would somehow magically sort itself otu but of course it didn't. I did a boot -r but that didn't matter since the new device didn't get installed. A check of fbconfig -prconf confirmed that my only driver is the built-in 8 bit one.

So next I tried to address the missing SUNWowrqd package. I did find one on an old Solaris 2.3 CD I had lying around but when I went to do the pkginstall, it said all the files it was wanting to install were already in the system. So I aborted that. But what's odd is if I do a pkginfo | grep SUNWow, it does not find SUNWowrqd.

Anyway I then uninstalled the GFX drivers, rebooted again and at least now I can log back in to my Sun Java desktop.

So now I think the problem becomes why am I getting this "No such file or directory" error. I looked that up in Google and didn't find any answers. I'm getting ready to chuck this whole machine out the window.

"One of the links I provided previously explained how to tell the service processor about the new adapter and switch off the old one. (I assume the old one is on-board so can't be taken out?"

That's right - the PGX device is right on the mobo and the PGX32 occupies a PCI slot. The hardware knows it's there because


# prtdiag -v

Shows Bus# PCI-2 , slot 1, Name=TSI,gfxp, Model=GFXP

I'm sorry, I must have missed that link, but I think we need to get the new driver at least installed before going any further.

Please post what your system comprises in the way of zones.

Your post shows there are zones. Global + non-global?

Which zone(s) are you trying to install this driver on???

If you pkgadd from the global zone without the -G switch, it will try and install onto all zones. I think this might be your problem.

You may be on to something here. I had never even heard of "zones" until I tried doing this installation. The system I have was configured by the prvious owner, so I've got whatever he set up.

"Which zone(s) are you trying to install this driver on???"

That's a very good question. I have no idea. I just typed "./install_all". How do I know what zone I'm in? Right now I think I'm in the Twilight Zone.

"If you pkgadd from the global zone without the -G switch, it will try and install onto all zones. I think this might be your problem. "

Well yes, there's no -G switch in the script. I'm doing it from the console logged in as root, if that makes any difference. You think I should try it again but with -G?