On 04/ 7/10 07:58 PM, bsd wrote:
Peace pipe accepted. :-)
I set 'console=text' but it still loops. I have also set 'acpi-user-options=2'
because otherwise I get a kernel panic. Anything after b129 is problematic for
some reason.
It's a Toshiba L505D-S5983.
Upgrading from b129 on several of my systems required
applying these two fixes documented in:
http://opensolaris.org/jive/thread.jspa?threadID=125446&tstart=0
The first one fixed the panic reboot loop.
6914346 upgrade from OpenSolaris 2009.06 (111b2) to 130 fails with stale
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6914346
After updating to build 130 or beyond, the system may panic
with messages of the form
/kernel/misc/amd64/pci_autoconfig:
undefined symbol 'pcie_get_rc_dip'
WARNING: mod_load: cannot load module 'pci_autoconfig'
panic[cpu0]/thread=fffffffffbc2e3a0:
failed to load misc/pci_autoconfig
Work-around: Boot the original boot environment (BE) instead
and correct the boot archive as follows
<reboot into the earlier BE>
u...@host$ pfexec beadm mount <name of new BE> /mnt
u...@host$ pfexec bootadm update-archive -F -R /mnt
u...@host$ pfexec beadm unmount <name of new BE>
At this point, the new BE can be booted into.
12380 image-update loses /dev/ptmx from /etc/minor_perm
http://defect.opensolaris.org/bz/show_bug.cgi?id=12380
When using image-update or the Package Manager to update to
build 125 or greater, remote access to the system via ssh(1) or
rlogin(1) may become unavailable. Alternatively, using
terminal programs such as gnome-terminal(1) or xterm(1) may
result in characters not being echoed or commands unable to be
typed.
Work-around: Boot the original boot environment (BE) instead
and correct the /etc/minor_perm file contained within as
follows
<reboot into the earlier BE>
u...@host$ pfexec beadm mount <name of new BE> /mnt
u...@host$ pfexec sh -c \
"grep ^clone: /etc/minor_perm >> /mnt/etc/minor_perm"
u...@host$ pfexec touch /mnt/reconfigure
u...@host$ pfexec bootadm update-archive -R /mnt
u...@host$ pfexec beadm unmount <name of new BE>
At this point, the new BE can be booted into.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
