Hi John, I'll try to clarify what was going on (as far as I can guess).
On Sat, 20 Feb 2010 06:04:21 PST, john ingrim <dmparis67 at gmail.com> wrote: > I 'fixed' it by removing and reinstalling the driver pkg, and then with .. > > # update_drv -a -i '"pciex168c,XXXX"' arn > > .. which I found here .. > > http://hub.opensolaris.org/bin/view/Community+Group+laptop/arn > The driver as shipped in OpenSolaris already recognises these two IDs: "pciex168c,2a" "pciex168c,2b" so any update_drv should be superfluous unless you have a different ID; you may have had to modload the driver or reboot though. You reinstalled the driver by using 'pkg remove SUNWarn; pkg install SUNWarn', I hope? The package on the site is almost certainly older than the SUNWarn currently bundled in OpenSolaris. > However, there I was, happy to have WiFi back on my netbook, and was > typing away, when suddenly the 'workspace changer' crashed ... then the > 'network monitor' crashed ... then the bottom 'taskbar' crashed ... > > I selected the OpenSolaris icon to do a reboot, when the entire OS just > died, and I got the 'Toshiba' logo as it rebooted. That's a fairly unusual and catastrophic failure. It's easy to blame hardware for this one (something like your hard disk disappearing out from under you would produce similar symptoms) although a driver could be at fault. Does your /var/adm/messages go back to that incident? > > Then I get the 'opensolaris' logo on blue, and the 'Knight Rider' kind of > thing going from left to right. That lasted for eighteen minutes, and then > the console appears, and I get.. It probably booted immediately, but the console is always hidden until you press a key when in graphical boot mode. > > WARNING: the following files in / differ from the boot archive > changed /etc/driver_aliases > The system hadn't had a chance to update the boot archive after (re)installing the driver before it went kaput. The boot archive is unfortunately a fragile part of the boot process as it must contain consistent copies of certain files on your system to be used early in boot. The entire message is: WARNING: The following files in / differ from the boot archive: ... The recommended action is to reboot to the failsafe archive to correct the above inconsistency. To accomplish this, on a GRUB-based platform, reboot and select the "Solaris failsafe" option from the boot menu. On an OBP-based platform, reboot then type "boot -F failsafe". Then follow the prompts to update the boot archive. Alternately, to continue booting at your own risk, you may clear the service by running: "svcadm clear system/boot-archive" Running the above command would solve your problem. > I logged in as root and did a manual reboot, and things are back to > normal. The command above is now in a script in /root, lest I need to use > it again, but it's quite worrying that this should happen when all I did > was close the lid and move to another room. I installed OpenSolaris 'cos > the second part of that name spoke 'stability', but it looks as if > OpenSolaris is about as 'stable' as was RedHat back in 1992. And that's > disappointing. You said you were "typing away" earlier, not closing the lid, so is this a separate incident? -Albert
