>> Last night I ran the text installer and when it finished the built in >> nvida driver worked fine. I was really surprised that the graphical >> installer wouldn't run, but the after text installation it worked >> fine. What you just said explains it. I really hope that the >> installation team updates the driver because the text installer was >> very painful: >> > Well... we can look at this. The miniroot which is what is used to > drive the installation likely doesn't have the updated version of the > driver. We can add this. Albert, is this a different package than open > nv driver? Is there a reason we would need both in the installation > environment? Thank you
>> - At around 15% copying files to disk it completely froze up (samba >> package). After waiting a few minutes I rebooted. >> - This time at around 45% it completely froze up (star office 8 fonts >> package?) Again I rebooted. >> - The third time it went all the way. >> > Well.. this isn't supposed to happen. What do you mean by froze up? No > mouse movement, just hanging, or the appearance of hanging? Since it was a text based installer there was no mouse. There is a progress bar that goes from 0 to 100 as it is installing files. At the end of the progress bar there is an animated slash that spins while I was DVD-ROM light blink and listen to hard drive make sounds. When it froze that animation stopped, DVD rom spun down and stopped, hard drive was not making sounds anymore, caps lock and num locks key on keyboard was unresponsive (didn't make light turn on/off). It was completely locked up. >> - I was unable to log into Gnome until I first went to a console as >> root and configured: >> a) /etc/nodename >> b) /etc/inet/hosts >> c) /etc/auto_home >> d) created /export/home >> e) created a new user and home directory >> >> > that should not be the case. If you set a root password, which I > assume you did, and the other host configuration data you should have > been able to log in. How did you answer the system configuration > questions during the installation? I told it to use DHCP, DNS, configured my ISP's DNS ip address, and for domain I made one up. The text installer did not ask me to enter a host name. During the partitioning it wanted to create an /export/home partition, but I changed it to be an /export partition so that I could put zones and other things on there too, outside of the home folder. >> A lot of that was trial & error, and a lot of googling. Once I was >> in things were working, but none of the developer edition stuff was >> installed, even though I chose the "Development workstation" software >> group during installation. >> > Yes, the developer software only gets installed if you use SXDE. The > SXCE paths, which the text installer is part of, doesn't automatically > install the developer tools. > >> Later I rebooted and chose the "xVM Hipervisor" at grub just to check >> it out. It booted my regular solaris, but network wasn't working. >> After rebooting and choosing the regular Solaris menu item in GRUB I >> find my network card is still not working. I did not have time to >> find out why. I'll have to look at it tonight. >> >> > Sounds like nwam isn't enabled. What does svcs -a > svc:/network/physical:nwam show? I'll have to check when I get home. Networking was working great until I rebooted into xVM. What was xVM supposed to show me? I thought maybe some config or monitoring tool? I was a bit surprised when it booted my normal OS. >> It was a bit disappointing to have to go through so much trouble on >> Sun's own hardware. I bought this hardware so that I wouldn't have >> trouble with Solaris. However it is free software and I do >> appreciate the work everyone has put into it. >> >> >> > I am sorry that this experience was frustrating. Some of the things we > are working on with Indiana are exactly these things. You can download > and try Indiana from > here:http://opensolaris.org/os/project/indiana/resources/getit/ > Thank you, I might give that a try soon. Ryan
