Solaris 10 boot oddity

I'm pretty new to Solaris, but I have a pretty solid background in unixy/linuxy type OSes. I've been getting into Java lately so I figured I might as well install Solaris just cuz'. So I have my root account, and my "poweruser" account that's simply a non-root admin type account. The thing is, when it boots up Solaris insists on setting the login screen to the world's biggest possible resolution, which in VMware is more of an irritation than anything else because both accounts of the system run in 1280x800. How on earth do I get the login screen to load up into 1280x800 and not....what appears to be 1600x1200?
Thanks

I think you are right about doing the "exclude", but I couldn't decipher the information from that link... Notebook in question is a "Dell Latitude E6410" if that helps.
I got a bit more information from logging Re: Boot hang - Can I stop it looking for the wireless lan? but missed the line that probably contains the driver name!

Similar Messages

Solaris boot sequence

Hi - is there a document which describes the Solaris boot sequence? I'm looking for stuff like 'when do device drivers get loaded', 'when do device drivers initialise, and in what sequence', 'when does /etc/system get read, and which statements are acted upon first'. Stuff like that.
thanks

Hi
You may find this information usefull.
In a Sun Box with Solaris 2.x the booting sequence is as shown below.
1.On powering the system , the Boot PROM in Sun hardware runs a series of self tests, displays banner , keyboard type information etc.
2. It then reads the Disk label at Sector 0 of the boot drive.
3. It reads the Primary Boot program called "bootblk" from the 1-15 sectors in the Boot drive and loads it in to system memory.
4. The "bootblk" program is a UFS file system reader. Using this "bootblk" program , the boot PROM reads the secondary boot program called "ufsboot" which is located at "/platform/`uname-i` " directory in the boot drive. The ufsboot program is loaded on to the memory.
5. The boot PROM then loads the two part static Solaris kernel onto the memory. The two kernels are /platform/`uname -m/kernel/unix ( which is a platform dependant kernel ) and /kernel/unix (which is a platform independent kernel which is same across all Solaris systems irrespective of their architectures).
6.From here on , the newly loaded Kernel takes over and loads the different kernel modules present in the directory /kernel/drv using the "ufsboot" program.
7.Kernel modules are pieces of the OS that can be installed separately.Kernel modules eliminate the need to rebuild the Unix kernel.Device drivers are also a type of these kernel modules.
8.The kernel modules needed to boot the OS are stored in /kernel/drv. Any module that can wait until after the kernel is booted is put into /usr/kernel.
9.The /etc/system which is a kernel patch file is read at this time and you can define a variable called "moddir" that establishes a search path for these modules.By default, this is set to search /kernel and /usr/kernel directories.
10. The kernel will then initialize itself and spawn the init process.The init will read the /etc/nittab and normal booting continues from there.
11. The kernel modules can be loaded and unloaded dynamically using the commands "modload" and modunload". You can see a list of the modules currently loaded in the memory using the command "modinfo".

Solaric boot up problem after poweroff

Hi Everybody,
I have a solaris 10 8/07 installation on X86. I have problem regarding boot up after power off. Its not booting in multiuser mode and hangs up at the blue screen. Could we do something in the single user mode to rectify the problem, because its possible to boot in single user mode?
Thanks.

Please include your full model number when posting problems on the forums. It can be found on the bottom of your laptop.
If it's now working perfectly, then I wouldn't worry about it if I were you. However, I can say that it's best to do a system recovery with the exact media designed for your notebook and then upgrade if you wish.
- Peter

How to mount USB & CDROM drives from single user mode - Solaris boot disk?

Hi All,
I need to carry out ufsrestore on a single newly replaced system disk (no redundancy / mirroring) from either USB or CDROM drives from the following steps:
( i ) GRUB => e, e, cdrom –s, Enter, b (boot from Solaris 10 x86 media).
( ii ) Choose menu 1 for Install Solaris Interactive Mode to reach single user mode.Below are the commands that I have tried in single user mode without success:
mount –r –F pcfs /dev/dsk/c1t0d0p0 /cdrom (after unmount Solaris CD)
mount: /dev/dsk/c1t0d0p0 is not a DOS filesystem.
svcadm –v enable smserver
svcadm: Pattern ‘smserver’ doesn’t match any instances
svcadm enable autofs
svcadm: Pattern ‘autofs’ doesn’t match any instances
devfsadm
devfsadm: mkdir failed for /dev 0s1ed: Read-only file system
mkdir /mnt
mkdir: Failed to make directory “/mnt”; Read-only file systemPart of the problem is due to the current READ ONLY filesystems which does not allow the creation of mount point such as /mnt.
I have been able to create both / root (/dev/dsk/c1t0d0s0) and /export/home (/dev/dsk/c1t0d0s0) filesystems with newfs that are awaiting for restore using ufsrestore.
The only option I am left with is to attach a secondary disk to install Solaris 10 on either of them before bring the system to multi-user mode so that service such as volmgt, autofs, volfs are available to access USB & CDROM drives.
Any suggestion on how to resolve this issue?
Many thanks,
Jack

Hi JKGN,
Is the directory a located under the root filesystem. ie /a? Are there any other mount point for say USB drive as well? I am not in a position to try it out right now but will get back
to you soon on whether /a exist or not.
Btw, the last thing I managed to do on this system at the time was added a secondary 1TB internal disk with the intention to restore both / and /export/home data onto this disk while
making use of all the disk device management services such as the following services only available in a fully installed Solaris system (both single & multi-user modes) installed on the
primary disk:
# svcs smserver
STATE          STIME    FMRI
online         Jun_08   svc:/network/rpc/smserver:default
# svcs autofs
STATE          STIME    FMRI
online         Jun_08   svc:/system/filesystem/autofs:default
# devfsadm
# iostat -En
c1t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: ATA      Product: SAMSUNG HD321KJ Revision: 0-11 Serial No:
Size: 320.07GB <320072932864 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 41 Predictive Failure Analysis: 0
c0t0d0           Soft Errors: 0 Hard Errors: 5 Transport Errors: 0
Vendor: PHILIPS Product: DVD+-RW DVD8801 Revision: AD21 Serial
Size: 17.54GB <17538875392 bytes>
Media Error: 0 Device Not Ready: 5 No Device: 0 Recoverable: 0
Illegal Request: 10 Predictive Failure Analysis: 0
c2t0d0           Soft Errors: 0 Hard Errors: 0 Transport Errors: 0
Vendor: JetFlash Product: Transcend 16GB   Revision: 1100 Serial No:
Size: 0.00GB <0 bytes>
Media Error: 0 Device Not Ready: 0 No Device: 0 Recoverable: 0
Illegal Request: 7 Predictive Failure Analysis: 0
# rmformat
Looking for devices...
     1. Volmgt Node: /vol/dev/aliases/cdrom0
        Logical Node: /dev/rdsk/c0t0d0s2
        Physical Node: /pci@0,0/pci-ide@1f,1/ide@0/sd@0,0
        Connected Device: PHILIPS DVD+-RW DVD8801 AD21
        Device Type: DVD Reader/WriterHowever, I was disappointed that "iostat -En" has not found the secondary disk (1 TB) even though it was available earlier, for Solaris installation as the only disk on the same system.
As a result, I am left with no option but the need to rebuild this system with only a single primary disk while in single user mode. However, the single user mode that I am in is the
one from Solaris installation disk with restrictive (_cannot create folder for mount point or running disk management utilities_) capability such as those services just covered, compared to one from a completed Solaris installation system with full access to all filesystems and utilities / commands in general.
I would very much value your assistance on how to mount both CD & USB in this restrictive limited Read Only OS (assume that it is running from memory) in order to get complete access to
the blank primary disk so that full restore with ufsrestore could take place.
Thanks in advance,
Jack
Edited by: 797805 on 9/06/2012 04:15

Solaris boot problem after Patch cluster install

just wondering if anyone can assist. i have just installed solaris 10 x86 recommended patches on a 16 disks server. where first 2 disks are mirrored called rpool, and remaining 14 disks are raid z called spool. upon installing the patches successfully and rebooting server, i am coming up with the following error:
NOTICE: Can not read the pool label from '/pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a'
NOTICE: spa_import_rootpool: error 5, Inc. All rights reserved.
Cannot mount root on /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@0,0:a /pci@0,0/pci8086,25f8@4/pci111d,801c@0/pci111d,801c@4/pci108e,286@0/disk@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
skipping system dump - no dump device configured
rebooting...
It looks like the solaris 10 os cannot find zfs filesystem and keeps on rebooting in normal solaris os mode, but when I go to safe mode and type: zfs list, I can see zfs rpool (mirrored) file system and cannot see the zfs spool (raid z) file system, any ideas on how i can fix the boot problem and get zfs spool back in the safest way possible?...

Same problem here with actual recomended patch set.
NOTICE: Can not read the pool label from '/pci@0,0/pci10de,375@f/pci1000,3150@0/sd@0,0:a /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@1,0:a'
NOTICE: spa_import_rootpool: error 5
Cannot mount root on /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@0,0:a /pci@0,0/pci10de,375@f/pci1000,3150@0/sd@1,0:a fstype zfs
panic[cpu0]/thread=fffffffffbc28820: vfs_mountroot: cannot mount root
fffffffffbc4b190 genunix:vfs_mountroot+323 ()
fffffffffbc4b1d0 genunix:main+a9 ()
fffffffffbc4b1e0 unix:_start+95 ()
What the hell happened to the bootsektor or the pool or what ever?

Solaris boot images fail with bad magic number

hi guys, have had Solaris on boxes for allmost 10 years. I have never installed sol10, and I have a problem
1. I download the zip file, then use winrar to unzip them..
2. burt the image with nero 7
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt
I do boot cdrom
this fails with "bad magic number" I have redown loaded it and reburnt it with nero reinstalled
and also changed out the DVD on SunBlade
3 I found a copy of Solaris 8 and the I got back a 'bitch' where is Solaris 9 so, most likely the drive is OK
HELP
Cris Harrison

Hello Cris,
unfortunately I don't understand your last sentence !
I found a copy of Solaris 8 and the I got back a '*****' where is Solaris 9 so, most likely the drive is OK
If this was a Solaris 8 (7/01 or later) DVD that did successfully boot, your DVD drive firmware (assuming that this is the Sun Toshiba SD-M1401) is up-to-date. If the DVD drive has firmware 1007, an update to 1009 is required to boot from DVD. otherwise you won't be able to boot from DVD (boot from CD works and a DVD can be automounted/mounted).
Partial output of probe-scsi
Before update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011007
After update:
Unit 0 Removable Read Only device TOSHIBA DVD-ROM SD-M14011009
[*Patch 111649-04 - Toshiba DVD 1401 firmware update*|http://sunsolve.sun.com/search/advsearch.do?collection=PATCH&type=collections&queryKey5=111649&toDocument=yes]
when my SunBlade 1000 comes up I do the Stop-A, and from the Ok promt ...
Instead of trying to directly boot, disable auto-boot and retry after a clean power-on.
Break with Stop-A
setenv auto-boot? false
reset-all
boot cdrom
Michael

Error message on Solaris booting

It was troubled, I have a Question.
When starting Solaris2.5.1(x86), the following error message is always displayed.
In order not to display this message, what should it carry out?
Moreover, what is a cause to display?
Cause is Hardware? or software?
-------boot message-----
Hostname : TEST01
The file system (/dev/rdsk/c1d0s0) is being checked.
/dev/rdsk/c1d0s0: INCORRECT BLOCK COUNT I=1053783 (2 should be 0) (CORRECTED)
/dev/rdsk/c1d0s0: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED)
/dev/rdsk/c1d0s0: 25250 files, 419799 used, 1833112 free
/dev/rdsk/c1d0s0: (3424 frags, 228711 blocks, 0.1% fragmentation)
The system is coming up. please wait.
-----end----------------
Usually, "init 0" (or "shutdown -y -g0 -i0") is used when shutting off a power supply.
In this case, an error message(incorrect block ,,,,,) is displayed.
But often, when I use "halt" , an error message may not be displayed
It cannot repair even if it uses the "fsck" command.
(Ex. fsck -F ufs -o b=32 /dev/rdsk/c1d0s0)
I have no idea about a cause.
please let me know If there are informations.
----system environment----
Solaris 2.5.1 (for Intel)
Pentium MMX 233MHz, 64MB memory, NIC:3C509B,
SCSI:AHA-1510B, Serial Multiport:aurora 8000P,
HDD: WD200BB (20GB, IDE)

Most likely, this is nothing to worry about. The message is fairly normal. There were some problems with sync'ing disks when such old Solaris x86 systems shut down, but it gets cleaned up when the system boots (which is what the message is telling you).
If reliability is important to you, upgrade to a modern version of Solaris and turn on file system logging.
Richard

Command-r boot oddity

Hey Folks,
Im just about to install a second SSD in my mini and testing a few of my software options for re-installing OSX after creating a RAID. My problem is that when I hold command-r to boot into recovery the entire software language is Chinese characters!?!?!?!?! Which, unfortunately, I don't read.
Is there a way to change this language to English so I can navigate the menus to perform back-ups etc.
This may or may not be releveant but my Mac was a custom build shipped to me from China.
Thanks,
Kyle

To see if there is atleast a Recovery HD partition
execute the following command in terminal:
diskutil list
If the Recovery HD is present, it should list something
like this (the underlined one):
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS Server HD               249.6 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
   4:                  Apple_HFS Mountain Lion           249.5 GB   disk0s4
(I don't actually have Mountain Lion Installed, just a partition
set up for it when it is released)
If it does, try booting with the option key held down and
see if it shows up as a selection.

Dual Booting Windows and Solaris

Hi
how do i dual boot windows and solaris
Do i install windows first and then solaris or do it the other way around..?
how do i make sure that Windows and Solaris appear in my boot options..?
Is their a guide on doing this...?
Thanks
Liam

Hey I did a quick google search for you. So I havent tried this method myself but it sounds reasonable.
The text below is from the following link:
http://www.hccfl.edu/pollock/AUnix1/DualBoot.htm
"Solaris boot loader
Partition the drive to leave at least 2GB of space available for Solaris;
more drive space is desirable.
As with Linux, install Windows first then Solaris.
Do not use the Installation CD but boot and install
from Software CD 1.
If you accept the default partitioning scheme which
the installer provides you will soon run out of space in
your / and /usr partitions since only enough space is
allocated to install the system.
All extra space is allocated to /export/home.
A typical installation on a 4.5GB partition might look
something like this:
Filesystem Size Used Avail Use% Mounted on
/dev/dsk/c0d0s0 900M 536M 310M 64% /
/dev/dsk/c0d0s1 334M 109M 192M 36% /var
swap 671M 8.0k 671M 1% /var/run
swap 671M 8.0k 671M 1% /tmp
/dev/dsk/c0d0s5 845M 222M 565M 29% /opt
# (FAT32 partition):
/dev/dsk/c0d0p0:1 5.0G 3.3G 1.6G 66% /c
/dev/dsk/c0d0s7 1.1G 92M 954M 9% /export/home
/dev/dsk/c0d0s4 752M 225M 474M 33% /usr/local
The Solaris boot selector enables you to choose either
Solaris or Windows with Solaris as the default.
(I prefer grub or lilo!)
To mount FAT under Solaris:
# mount -F pcfs /dev/dsk/c0d0p0:c /dos (or �:1�?)
And the vfstab file:
/dev/dsk/c0d0p0:c - /dos pcfs - yes -
To create a GRUB boot floppy, follow these steps:
$ mkfs -t ext2 /dev/fd0
$ mount /dev/fd0 /mnt/fd0
$ mkdir /mnt/fd0/boot /mnt/fd0/boot/grub
$ cp /boot/grub/stage[12] /boot/grub/grub.conf \
> /mnt/fd0/boot/grub
$ /sbin/grub --batch <
Hope this helps!
/Oscar

Xp/solaris dual boot bug

Hello
I have a 80gb hard disk set up with win xp pro along
with a 25gb unformated partition. Recently I installed
solaris 10 x86 to the 25gb partition from sun's
website. the installation setup automatically selected
the 25 gb space. all seemed to be working fine. the
only problem was after installation solaris boot
manager selected solaris automatically if no selection
of win xp was made within 30 seconds. since i needed
xp pro as a default i used the utility OSBS (boot.exe
and osbs135). as instructed i have entered the saved
solaris.bin from mbr to xp root and have entered
corresponding entry in win.ini file. the new boot
manager enables xp selection by default, xp pro boots
all fine but if i select solaris nothing happens
except a blinking cursor.
It seems to me that solaris partition is all fine and
healthy as I added few packages from solaris
installation cd few days back. Only problem is i m
unable to boot from it with the OSBS boot manager.
Is this a known problem?? or is there any better boot
manager?
Any advice/suggestion will be highly appreciated.
Many thanks

Hi, I am not sure if this would work but it might. First of all do you know if you delete the solaris partition then wouldn't it go back to booting to Windows? Just wondering about that. Well anyways here is my proposed solution that enables booting Solaris from Windows XP boot menu. Actually wait do you have a floppy drive on your laptop or a portable one. Because this solution requires that. Reply if you have one.

Solaris 10 x86 b72 "Cannot find boot.bin" booting from SCSI.

Hello,
After several gyrations of installation attempts and dealing with early BIOS PnP issues, I've finally managed to get Solaris 10 x86 installed on an old dual P2 333Mhz system. So far the system is running flawlessly, but I'm still not able to boot directly off the SCSI disk. The primary boot handler is erroring out that it cannot find boot.bin.
I can boot fine off of the IDE CD drive and the floppy (currently pointed to autoboot into the SCSI disk as a workaround). But when I try to boot directly off the SCSI drive, I get the error from the Solaris boot manager that it "Cannot find boot.bin".
I have booted off the CD & Floppy and compared the /boot files from both the CD & floppy, but I cannot find any difference that would prevent the primary boot loader from finding boot.bin. I've even compared files to make sure they were not corrupt, and even force re-installed the boot handlers, and manually partioning, always with the same results. I've also tried both enabling and disabling the DOS >1G translation of the Adaptec SCSI BIOS with no change. I can't find any reason that the boot loader is not seeing boot.bin, or that the file is corrupt in any way (even after several wipe and install attempts).
My System is:
Supermicro P6DLS dual Pentium II 333MHz & 512MB RAM, w/ Adaptec 7880 SCSI-UW and IDE (whopping UltraDMA 33) interfaces.
CD/DVD reader is configured as the secondary master (moved from primary master in an attempt to fix boot problem)
HD is a 16GB UW SCSI disk.
(Other particulars ommited unless someone feels they are relevant to the boot process).
The system came to me with Windows 2000 installed and functioning. I also had Fedora Core 3 installed, both with no boot problems of the SCSI disk. (Although FC3 would not see the second processor even with the canned SMP kernel).
This system is intended to replace a Fedora Core 3 system to be a multi-purpose firewall gateway & proxy server and I'm really liking the performance I'm seeing with Solaris 10 on this system but would like it to be able to go through a normal boot process and not have to depend on a floppy as a boot device to get started.
Anyone have any ideas why the Solaris x86 boot loaders think that they cannot find boot.bin when the full /boot partion is intact?
TIA,
-Troy

I'm getting the same problem trying to install
Solaris 10 in VMware from DVD.
It brings up the Solaris Primary Boot Subsystem, so
it appears to be reading fine, but the only thing
that happens is I get the Cannot find boot.bin
error.Hmm, the "Cannot find boot.bin." message comes from the
CD/DVD's boot code, which is contained in the first 16 sectors
of the media.
The boot.bin file is supposed to be read from the Solaris UFS
slice, which starts at 512 byte block #5151360 (or 2048 byte
dvd sector #1287840). This a byte offset of ~2.6 GBytes.
Maybe an issue with your system's bios not being able to read
DVD media > 2GB, during DVD boot?
Or a problem with burning the DVD media? Maybe some
"smart" PC DVD burning software has decided only to record
the 2.6 GB ISO filesystem, and the 100 MB Solaris UFS
filesystem that follows the ISO filesystem is missing on the DVD?
Or a 2GB filesize issue while burning the DVD?
Do you have a pc / windows utility that can print some information
about the S10 DVD media, especially the size of that DVD?
Maybe your CD/DVD recording software?
The original S10 GA x86 DVD image has a size of 2732195840
bytes, or 1334080 2K DVD blocks.

Dual boot of Solaris 10

Hi,
I am new to Unix world , Can I install Solaris 10 with Dual boot support. I have to keep Windows XP as well as Solaris.
And my second question is that Solaris 10 is the Desktop OS or Server OS ? And what is the difference between SunOS 5.2 and Solaris 10.
Amir Hussain
Thanx in Advance.

Yes, I have Solaris 10 x86 (03/05) running along with
Windows XP on a Dell Optiplex GX280. I loaded XP
first, created a partition for the Solaris install
and then loaded Solaris. The Solaris boot loader
comes up at power up so that you can select Solaris
or XP. I am using Solaris 10 on both servers and
destops. I am not experienced enough to tell you the
difference between SunOS 5.2 and Solaris 10. Sorry.Thanks Daniel,
Its mean First of all I have to install xp, then create a partition for solaris 10. Then install solaris 10.
I have IBM compatible PC.
I

Installed Solaris, No OS-boot sector is recognized.

Hello,
I just installed Solaris 10 11/06 version on x86 Intel pentium. I followed through every steps, ejected the DVD and upon restart ,nothing happens, it mentions press a key to continue and restarts and comes back to the same point.
My assumption is that the menu.lst is not updated or not sure. There is no operating system boot happening,How do you set the bootloader to pick the Solairs Operating System from disk partition C0D0S0, what are the main entries in the menu.lst, is this what i should be doing. I logged via the DVD boot and get a prompt, i tried bootadm and other utilities, any help.
Basically the Solaris is installed but just need to configure the bootloader or bios to recognize Solaris OS is installed. My bios setting points to HDD.
Any help would be great
Thanks
MJ

A couple things you can I'd look at or do. First I'd make sure that your ribbon connected to your hdd is not loose. A bad ribbon, or intermitten one will cause your hdd not being recognized. If you're sure it good then try booting from the installation DVD and at the prompt type the following command:
installgrub
That should reinstall grub for you.
You can also try booting in safe mode and run the following command:
- bootadm update-archive -f -R /a.
That should update your boot archive.
More good grub info is located at:
http://www.sun.com/bigadmin/features/articles/grub_boot_faq.html#q19
Also, if you want to try editing you're copy of /boot/grub/menu.1st. Here's a copy of what mine looks like:
# default menu entry to boot
default 0
# menu timeout in second before default OS is booted
# set to -1 to wait for user input
timeout 10
# To enable grub serial console to ttya uncomment the following lines
# and comment out the splashimage line below
# WARNING: don't enable grub serial console when BIOS console serial
#     redirection is active!!!
# serial unit=0 speed=9600
# terminal serial
# Uncomment the following line to enable GRUB splashimage on console
splashimage /boot/grub/splash.xpm.gz
# To chainload another OS
# title Another OS
#     root (hd<disk no>,<partition no>)
#     chainloader +1
# To chainload a Solaris release not based on grub
# title Solaris 9
#     root (hd<disk no>,<partition no>)
#     chainloader +1
#     makeactive
# To load a Solaris instance based on grub
# title Solaris <version>
#     root (hd<disk no>,<partition no>,x)     --x = Solaris root slice
#     kernel /platform/i86pc/multiboot
#     module /platform/i86pc/boot_archive
# To override Solaris boot args (see kernel(1M)), console device and
# properties set via eeprom(1M) edit the "kernel" line to:
# kernel /platform/i86pc/multiboot <boot-args> -B prop1=val1,prop2=val2,...
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
title Solaris 10 11/06 s10x_u3wos_10 X86
root (hd0,0,a)
kernel /platform/i86pc/multiboot
module /platform/i86pc/boot_archive
#---------------------END BOOTADM--------------------
#---------- ADDED BY BOOTADM - DO NOT EDIT ----------
Message was edited by:
mrmdls
Added a copy of /boot/grub/menu.1st

Solaris 11 enable default splash screen boot-up

After playing around with 'bootadm' due to some reasons, I restored the original menu like 'bootadm generate-menu' and everything runs just perfect.
But the original Solaris boot splash screen dismissed.
I know many people around want to disable it while running virtually on e.g. vmware.
I am running on a physical machine and want the default splash back!
How to restore it, please?

I don't have a system to check on this myself but you might look in /boot/grub to see if the default
splash screen file is included. The file name should be apparent. If it is included, then the bootadm
syntax (from the bootadm.1m man page) looks something like this:
# bootadm set-menu splashimage=/boot/grub/splash.xpm.gz
Thanks, Cindy

Re: Installing Solaris 11.1 and multi-boot manager

Hi,
I have several problems too (I'm newbie on solaris) installing Solaris in multiboot environment ( I have 3 hard disks on this pc)
Does the grub2 of solaris 11.1 boot linux or not ? if the grub2 of solaris 11.1 can boot linux I think I will install the grub2 of solaris in MBR, I have already triyed this with bootadm install-bootloader -M but there was already a grub2-pc of linux installed and it did'nt
delete the grub2 of linux, so I think I must use bootadm install-bootloader -fM to install the grub2 of solaris
if the grub2 of solaris 11.1 doesn't boot linux I will do as you said with the chainload of solaris (how can I chainload solaris in a recent grub2 ?
in menu entry :
insmod part_msdos
insmod part_sunpc
insmod part_gpt
insmod zfs
set root='(hd2,gpt1)'
chainload +1
(this last point is not important because I have other ways to boot linux and Iprefer to install the grub2 of solaris)
I cannot retrieve my root pool when I boot from the text install CD ROM, zpool import -f rpool doesn't succeed, must I do something after an installation (is it possible to save the root pool on a big usb key ?),(I think I will post another thread for that...)
thanks for your answers
Edited by: stephane_l on May 16, 2013 5:59 AM

Hi,
I have severals problems too installing soalris 11.1 in multiboot environment(3 hard disks on pc)
Can the grub2 of solaris boot linux?
I tried to install the grub2 of solaris after an installation but it doesn't delete the grub2-pc of linux, I think I should have use bootadm install-bootloader -fM to force the instalaltion in MBR
After that (it was my second unsuccessful installation) I have booted with the text install cdrom but the zpool import -f rpool didn't work, must I do something after an installation ? (should I save the root pool after my installation ? can I save the root pool on a big usb key?) I must perhaps post a new thread for this..
thanks for your answers

Solaris 10 boot oddity

Similar Messages

Maybe you are looking for