Sponsored Content
Full Discussion: Boot question
Operating Systems Solaris Boot question Post 302411941 by jlliagre on Saturday 10th of April 2010 05:19:00 AM
Old 04-10-2010
Quote:
Originally Posted by mghis
Does the version of Solaris that you suggested support:
1- SATA hard drives;
2- Nvidia grafic card and mobo;
3- Intel Core 2 Duo CPU?
Sure, that's pretty standard specs nowadays.

If this is a laptop (and even if it's not), you might want to install an OpenSolaris based distribution instead for a better and simpler support.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Boot question

Hey all, Just wondering about to things with the bootup. First one is. When you boot Solaris, the background is white and text black. Is it possible to change this so that the text it white and background is black? I don't have any idea how to do this one. So if anyone does please let... (2 Replies)
Discussion started by: merlin
2 Replies

2. UNIX for Dummies Questions & Answers

another dual boot question/problem

Well, I formatted my entire harddrive (40gig), partitioned it into three partitions, FAT32 for WindowsXP (30 gig), Linux ext3 (7gig), and Linux swap (about 500mb). All this with PartitionMagic 8.0 and it took hours. After all that, I installed the "publishers version" of Red Hat with ease. I was on... (12 Replies)
Discussion started by: chutt
12 Replies

3. UNIX for Advanced & Expert Users

Cannot boot - Boot : Panic : File size out of range (EWS-UX/V unix)

Hey ! I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range. According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies

4. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies

5. Solaris

question about opb boot device

hi all: I have a sun blade-1000 for labs only, with 73G hd loaded, which boot block installed on slice 0. I'm confused by setting "boot-device" value in obp, which my question as follow: in ok mode, I got device alias like this: disk0: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@2,0 as I know the... (4 Replies)
Discussion started by: netshu
4 Replies

6. Filesystems, Disks and Memory

Question - error during boot

I have an HP NetServer LH3 which is exhibiting an error during the boot process. I am getting the following messages, none of which I've seen before 1. WARNING: SCSI adapter: Cannot install intr vecno=12 type=4 IPL=5 Vector 12 is private 2. WARNING: "TEST_UNIT_READY" Command timed 11 seconds... (0 Replies)
Discussion started by: slant-40
0 Replies

7. Boot Loaders

Reboot and Select Proper Boot device or insert Boot media in select Boot device and press a key

Hello, I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error " reboot and select proper Boot device or insert Boot media in select Boot device and press a key " I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies

8. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies

9. Solaris

Solaris 2.4 boot question

Hi Guy's, Newbee here. I installed Solaris 2.4 in VMWare Fusion 5.0.2 on a MacBook Pro. All went well, but after 'system ready' I get a 'console login' prompt. But I never got to the point where I could set a name and password for that. I can login as root. But that's all. How do I get to... (7 Replies)
Discussion started by: hansolo
7 Replies

10. UNIX for Beginners Questions & Answers

Question about Volume Boot Record

Hello and thanks in advance for any help anyone can offer Hopefully this is a simple question but is the Volume Boot Record (VBR) only used in Windows? I've seen references to it in relationship to Windows & not Linux... but I'm not sure if that means it's unique to Windows or not. If it is... (1 Reply)
Discussion started by: bodisha
1 Replies
sata(7D)							      Devices								  sata(7D)

NAME
sata - Solaris SATA framework DESCRIPTION
Serial ATA is an interconnect technology designed to replace parallel ATA technology. It is used to connect hard drives, optical drives, removable magnetic media devices and other peripherals to the host system. For complete information on Serial ATA technology, visit the Serial ATA web site at http://www.serialata.org. Up to 32 SATA devices may be plugged directly to each SATA HBA supported by the Solaris SATA framework. The actual number of pluggable devices my be lower, and is limited by a number of device ports on the SATA HBA. The maximum data rate is either 1.5Gb/sec. or 3.0Gb/sec., depending on the capability of a SATA device and SATA HBA controller. The Solaris SATA framework adheres to the Serial ATA 1.0a specification and supports SATA-2 signaling speed 3.0Gb/sec. SATA devices that are connected to SATA HBAs controlled by a SATA framework-compliant HBA driver are treated by the system as SCSI devices. The Solaris SCSI disk driver (sd(7D)) is attached as a target driver for each device node created by the SATA framework. You can use the cfgadm(1M) utility to manage hot plugged and unplugged SATA devices. FILES
/kernel/misc/sata 32-bit ELF kernel module (x86). /kernel/misc/amd64/sata 64-bit ELF kernel module (x86). ATTRIBUTES
See attributes(5) for descriptions of the following attribute: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ |Availability |SUNWckr | +-----------------------------+-----------------------------+ SEE ALSO
cfgadm(1M), prtconf(1M), cfgadm_sata(1M), attributes(5), ahci(7D), marvell88sx(7D), nv_sata(7D), sd(7D), si3124(7D) Serial ATA 1.0a Specification -- Serial ATA International Organization. Serial ATA II (Extension to Serial ATA 1.0.a.) -- Serial ATA International Organization. http://www.sun.com/io DIAGNOSTICS
The messages described below may appear on the system console as well as being logged. All messages are presented in one of the following formats and are followed by the diagnostic message: sata: WARNING: <controller/devices/.. path>: or: sata: NOTICE: <controller/devices/.. path>: ...where <controller/devices/.. path> identifies a specific SATA HBA issuing a diagnostic message shown below. SATA port X: link lost. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost. SATA port X: link established. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been established. SATA port X: device reset. The device plugged to the specified SATA device port has been reset. The reset may be due to a communication or command error, command timeout, or an explicit request from the host. SATA port X failed. The specified SATA device port failed and is in an unusable state. You can change the port state by deactivating the port and activat- ing it again using cfgadm SATA hardware-specific commands (see cfgadm_sata(1M)). SATA port X error. An error was detected in specified SATA device port operations. SATA device detached at port X. Communication (via serial link) between the HBA and the device plugged to the specified SATA device port has been lost and could not be re-established. The SATA framework assumes that the device is unplugged from the specified SATA device port. SATA device detected at port X. Communication( via serial link) between the HBA and the device plugged to the specified empty SATA device port has been established. The SATA framework assumes that the new device is plugged to the specified SATA device port. SATA disk device at port X. This message is followed by a disk description specifying the disk vendor, serial number, firmware revision number and the disk capa- bilities. SATA CD/DVD (ATAPI) device at port X. This message is followed by a SATA CD/DVD description specifying the DVD vendor, serial number, firmware revision number and the DVD capabilities. SATA device at port X cannot be configured. Application(s) accessing previously attached device have to release it before newly inserted device can be made accessible. The port cannot be configured because there is application using the previous attached device, so the application must release it, then the newly inserted device can be configured. Application(s) accessing previously attached SATA device have to release it before newly inserted device can be made accessible. The target node remained and it belongs to a previously attached device. This happens when the file was open or the node was waiting for resources at the time the associated device was removed. Instruct event daemon to retry the cleanup later. sata: error recovery request for non-attached device at cport X. When error recovery is requested, the device is not yet attached. SATA device at port X will not be power-managed. When property "pm-capable" on the target device node setting fails, the SATA device won't be power-managed. SATA disk device at port X does not support LBA. The disk device plugged into specified SATA device port does not support LBA addressing and cannot be used. Cannot identify SATA device at port X - device will not be attached. IDENTIFY (PACKET) DEVICE data cannot be retrieved successfully after the device is attached to the SATA port. sata: <HBA driver name><instance number>:hba attached failed. The SATA HBA instance attach operation failed. This HBA instance cannot be configured and is not available. sata: invalid ATAPI cdb length<command cdb length>. The length of the command cdb is greater than that the device can support. sata: invalid sata_hba_tran version X for driver <HBA driver name>. The specified SATA HBA driver and the SATA framework are incompatible. The driver cannot attach and SATA HBAs controlled by this driver (and devices plugged to this SATA HBA ports) are not available. sata_hba_attach: cannot create SATA attachment point for port X. The specified SATA device port cannot be configured in the system and a device plugged to this port could not be not be configured and used. sata_create_target_node: cannot create target node for device at port X. The device target node for the device plugged to the specified SATA device port could not be created. As a result, the device cannot be configured and used. SunOS 5.11 5 Sep 2007 sata(7D)
All times are GMT -4. The time now is 01:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy