Sponsored Content
Operating Systems Solaris Solaris 8 booting from wrong device Post 302206458 by sparcguy on Tuesday 17th of June 2008 10:36:26 PM
Old 06-17-2008
go to your ok prompt do a devalias
and compares if any boot device alias has /pci@1f,0/pci@1/scsi@8/sd@0,0 in it.

If there isnt. Do a nvalias and map a new alias boot3(whatever) to /pci@1f,0/pci@1/scsi@8/sd@0,0

do a man on devalias
do a man on nvalias
 

4 More Discussions You Might Find Interesting

1. Solaris

What's wrong with my system? Solaris not booting.

Booting the 32-bit OS ... SunOS Release 5.7 Version Generic_106541-31 Copyright (c) 1983-2002, Sun Microsystems, Inc. configuring network interfaces: le0. Hostname: wz-ultra1 metainit: wz-ultra1: there are no existing databases The system is coming up. Please wait. checking ufs... (2 Replies)
Discussion started by: CollenM
2 Replies

2. Solaris

Booting from wrong SCSI-disk. Error -256 Stack Underflow

Hi. I need to boot on Sun Blade 150 from scsi-disk, that ran on old Sun Ultra 10. It is necessary to take some the information from an old disk and something to study. The workstation is booted and I receive the following issue::mad: Sun Blade 150 (UltraSPARC-IIe 650MHz), No Keyboard (tip... (3 Replies)
Discussion started by: wolfgang
3 Replies

3. Red Hat

This doesn't look like a partition table Probably you selected the wrong device.

Hi, I need to mount the device from this device # fdisk -l . . . Disk /dev/sdas: 2000.4 GB, 2000365289472 bytes 255 heads, 63 sectors/track, 243197 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size... (0 Replies)
Discussion started by: justbow
0 Replies

4. Red Hat

Device-mapper behaviour booting on init=bin/bash

Good morning Recently we needed to change the password from a redhat 6.5 system that no one knew the root password. Starting the system with the init=/bin/bash method took us to the following scenario: system_vg active with only root_lv and tmpfs mounted. our entries at fstab are like... (1 Reply)
Discussion started by: Ikaro0
1 Replies
GENFB(4)						   BSD Kernel Interfaces Manual 						  GENFB(4)

NAME
genfb -- generic framebuffer console driver SYNOPSIS
genfb* at pci? genfb* at sbus? wsdisplay* at genfb? DESCRIPTION
The genfb driver provides support for generic framebuffers that have no native driver. All it needs are some parameters to describe the framebuffer and an address. PCI When attaching to a pci(4) bus the driver is configured via device properties: width (uint32) Width in pixels. height (uint32) Height in pixels. stride (uint32) Line size in bytes. depth (uint32) Bits per pixel. is_console (bool) If true, genfb will try to become the system console. address (uint32) Bus address of the framebuffer. SBus When attaching to sbus(4) all those parameters are retrieved from the firmware. SEE ALSO
pci(4), sbus(4), wscons(4), wsdisplay(4) BUGS
There is no way to change the color map even when the firmware supports it. The pci(4) bus frontend has only been tested on macppc, i386, and amd64 and requires machine dependent code to pass the properties mentioned above. So far only macppc, i386, and amd64 provides them. BSD
August 23, 2009 BSD
All times are GMT -4. The time now is 09:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy