Sponsored Content
Operating Systems Solaris I can't boot my Sun T5220 server from cdrom. Post 303031693 by rbatte1 on Monday 4th of March 2019 12:04:09 PM
Old 03-04-2019
Can you tell us what you actually downloaded? Perhaps the link would be useful here too so we can cross check.

The CD will need to have a boot-block written and enough to get it started. Perhaps an ISO image of an install CD will be enough, but the hardware would need to be supported.




Robin
This User Gave Thanks to rbatte1 For This Post:
 

9 More Discussions You Might Find Interesting

1. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

2. Solaris

Sun T5210 & T5220

Hi! Does anybody got some experiences with the Sun Server T5210 or T5220? -> especially in network configuration! Thanks... BYE (2 Replies)
Discussion started by: kaufmoa
2 Replies

3. UNIX for Dummies Questions & Answers

How-to boot server with no CDROM via serial connection to laptop

I have an x86 Sun server, with no CDROM drive and no OS currently loaded on it. I need to install CentOS on it... trying to figure out how to do that. I've heard there are ways to connect to the serial management port, and mount a laptop's CDROM drive as a drive the server will recognize to... (0 Replies)
Discussion started by: Mariognarly
0 Replies

4. Solaris

Error while trying to boot from cdrom on Sun Fire T2000

Hi Guyz, I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso. When trying to boot at the ok> boot cdrom i get the following error: ----------------------------------------------------------------------- Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies

5. Solaris

Sun Blade 150 wont boot off cdrom

Hello, Ive just aquired a blade 150 off ebay.Im new to suns and are having a problem getting it to boot off the cdrom.Openboot continuously tries to do a network boot and I cant enter any commands.Im using an average pc keyboard and it definetly works.Thanks for any help.:wall: (3 Replies)
Discussion started by: chucky
3 Replies

6. Solaris

How to boot a sun Solaris server?

Hi everyone, I have searched on google and sun documentation but it's still not clear for me; how do we boot a sun Solaris server? I know what to do but only from this step: 1- start /SYS 2- start /SP/console The system go to to the prompt OK, then we use the BOOT command. My... (9 Replies)
Discussion started by: adilyos
9 Replies

7. Solaris

T5220 fails to boot

One of our T5220 servers fail to boot due to following error: ERROR: The following devices are disabled: XAUI1 XAUI0 I can't see any disabled components in SP console, any idea what is the problem? (1 Reply)
Discussion started by: belalr
1 Replies

8. Solaris

Trying to boot Solaris without hard drives in T5220

I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode. I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management. Tinkering around I... (4 Replies)
Discussion started by: nerdboy
4 Replies

9. Solaris

T5220 not able to boot from USB

Hi, I want to install Solaris-11 on T5220. I created USB from sol-11_4-text-sparc.usb by usbcopy on another Solaris-11 servers, which looks like a good one. I tried did "reset-all" and still same issue. Can I get some help on this. {0} ok reset-all Sun Netra T5220, No Keyboard Copyright... (8 Replies)
Discussion started by: solaris_1977
8 Replies
EMBUILDDEPS(1)						User Contributed Perl Documentation					    EMBUILDDEPS(1)

NAME
embuilddeps - handle native and cross build-dependency installation. Usage embuilddeps [-a|--arch] [--use-sudo] embuilddeps -?|-h|--help|--version Options -a|--arch: Install cross packages for the specified arch. -d|--dir DIR: Location of the unpacked source (./debian/control) --dsc DSCFILE: Path to a .dsc file for the package. -m|--multiarch: Make dpkg-cross convert Multi-Arch packages. -k|--preserve: Pass the -k option down to xapt. -v|--verbose: Make the output more verbose -q|--quiet: Make the output less verbose -n|--dry-run: Only output the commands which would be used. --use-sudo: Call apt-get using sudo. Description "embuilddeps" is a simple build dependency checker for cross-building. Native build dependencies are checked using the debian/control file in the source package being built and installed with "apt-get". Cross build dependencies are checked using a debian/xcontrol file or the debian/control file if no xcontrol file exists. "embuilddeps" uses "xapt" to install cross build dependencies. Output To see more about what is going on (and to check the results of parsing the dependencies and architecture limits. See also Term::ANSIColor (3) for information on ANSI_COLORS_DISABLED. pbuilder "embuilddeps" can be used as a native and cross-dependency resolver in a pbuilder chroot using "pbuilder", "pdebuild" or "pdebuild-cross" and supports pbuilder options to locate the chroot and execute calls within the chroot. --control indicates the location of the .dsc file --internal-chrootexec indicates the command to execute inside the chroot --chroot indicates the location of the chroot --binary-all is supported as a no-op by C<embuilddeps>. If other build tools need particular options to be supported, please file a wishlist bug against "xapt" and describe the exact options which are necessary. "embuilddeps" does require that "xapt" is installed inside the chroot - it will try to install it for you but it is much easier if you install it once and for all. "pdebuild-cross" will add "xapt" when creating a new chroot. See pdebuild-cross (1) for more information on how to manipulate a pdebuild-cross chroot after creation. Source packages and dsc files "embuilddeps" can also parse the build dependencies of a package via the .dsc file. The rest of the source package (the files listed in the .dsc) do not need to exist and the source does not need to have been unpacked. Use the "embuilddeps --dsc FILE" option. The alternative method is to parse the ./debian/control file at the location specified by the "--dir" option which defaults to the current working directory. Multi-Arch transition Some packages already have multi-arch paths which dpkg-cross does not normally convert. This can cause missing dependencies when trying to install the converted packages. Use the "--multiarch" option to "embuilddeps" to pass this down to "xapt" and hence to "dpkg-cross". Retaining downloaded binaries "embuilddeps" can pass the "-k" option to "xapt" to retain the foreign architecture packages downloaded by "xapt" and the packages built using "dpkg-cross". Note that "xapt" should be asked to clean up the downloaded files once these lists have been handled by calling the "xapt -c" option which removes the contents of /var/lib/xapt/*. perl v5.14.2 2012-09-26 EMBUILDDEPS(1)
All times are GMT -4. The time now is 01:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy