Jumpstarting x86 with a specific network driver...

unix

    Next

  • 1. clone VM disk
    Hi all, I have one disk in server A and one disk in server B. The server A's disk is running VM 4.0. How can I clone the server A's disk to server B's disk? Thanks
  • 2. two questions about solaris installation
    1. When first install Solaris 9, i didn't assign a seperate partition for /usr. Later on I moved /usr to a slice on another internal disk(not the root disk). NOw each time when reboot the machine, it always has a messaging saying that /usr is busy.... My question is does /usr have to be on boot disk? 2. When install Solair 9 using DVD, I usually get slice 1(swap) started at cylinder 0. How to make slice 0 starting with cylinder 0? also how to keep one slice as unassigned during customise the file system layout when installing with DVD? Thanks for advice
  • 3. A1000, Ultra 10, & drive size compatibility
    Can a Sun A1000 RAID array, linked to an Ultra 10 with Solaris 2.6 by a differential scsi controller, be loaded with 36Gb of 70+Gb Sun drives? I ask since there are sometimes issues with older OS vs newer (ie larger capacity) drives.
  • 4. Restricting a Solaris User to one directory
    Hi, I've created a new user named "test" in my Solaris 8. What I need when ever this user log in, he will directly(automatically) go to some directory say /fsh/xyz. And this user will have all the permission for all the stuff but only within this directory and this user can not cd to any other directory except this specific one. Can any one please guide me how can I do that? Thanks ank

Jumpstarting x86 with a specific network driver...

Postby te » Wed, 15 Feb 2006 14:26:41 GMT

I have gotten my Linux server to act as a jumpstart server for both the
SPARC and x86 Solaris verions, which is quite nice.

However, I have one x86 box that does not have a network driver in the
base x86 set.

If I install off the DVD, I just do a pkgadd for the network driver
(It's a YUKON gigabit) and everything works like a champ.

When I boot off the jumpstart server I get the following error:

Custom Jumpstart
No driver (or driver binding) was found for the interface used to boot.
A driver (or driver binding) may be available in an update or patch
from Sun, or from the interface vendor.

Is there a way that I can patch the DVD image copied to the
distribution point so I can finish the jumpstart?

Thanks!


Re: Jumpstarting x86 with a specific network driver...

Postby Michael Vilain » Wed, 15 Feb 2006 15:39:15 GMT

In article < XXXX@XXXXX.COM >,




I don't know if Jumpstart is any different from when I set it up, but 
unless you can boot from the Jumpstart image, you're more or less stuck 
here.  I don't know of a way to "patch" the jumpstart image with the 
driver you need to boot the machine.  But you could install via DVD, 
then do a flarcreate to image the base system with this type of HW, then 
you'd be able to reinstall it later (supposedly you'd be able to boot 
with the base system that's loaded over the network).  Or does the flar 
system also require a working network with a base Solaris install in 
order to work as well?

-- 
DeeDee, don't press that button!  DeeDee!  NO!  Dee...




Re: Jumpstarting x86 with a specific network driver...

Postby Casper H.S. Dik » Wed, 15 Feb 2006 18:10:51 GMT

 XXXX@XXXXX.COM  writes:



Solaris 10 or Solaris 10 update 1?


If this is S10 update 1 you will need to build a miniroot with the
appropriate device installed.  This requires unpacking the miniroot
on a Solaris x86 system (it's a gzip'ed file), mounting it with lofi
adding the device and then  recompressing it.

Casper
-- 
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Re: Jumpstarting x86 with a specific network driver...

Postby te » Thu, 16 Feb 2006 01:08:13 GMT

Casper,
Yes, it's is the 01/06 release of Solaris 10 x86.

Ok, I have the miniroot mounted and have added the extra lines into the
devalias file, which is what I have read that needed to be done.  I'm
about ready to umount/recompress/ and copy the image back over.

I do have one question though, is the /etc/devalias the only file that
needs to be added?  I would think I would need to add a specific driver
or such..... Wait, I just found a couple files in the /kernel/drv
directory (yukonx.conf and yukonx) and , so I now have copied those
into the miniroot too.

Are there any other files that I should add to the miniroot?

BTW: Casper, I have watched you be an active participant in these and
other forums for many years.  Your knowledge transfer has always been
greatly appreciated.

Keep up the great work and long live Sun!


Re: Jumpstarting x86 with a specific network driver...

Postby Casper H.S. Dik » Thu, 16 Feb 2006 04:11:09 GMT

 XXXX@XXXXX.COM  writes:



You need to:

    - copy the 32 bit driver to:
	    $miniroot/kernel/drv/yourge
	    $miniroot/kernel/drv/yourge

    - then run:

	    add_drv -b $miniroot -i '"pciXXXX,YYYY" "pciXXXX,ZZZZ"' yourge

this will add the driver aliases, assign a major number, etc.

Or, if it's in pkgadd format, it's probably easier to:

	pkgadd -R $miniroot YOURge


No; see above.




Thanks.

Casper
-- 
Expressed in this posting are my opinions.  They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.

Similar Threads:

1.jumpstarting x86

i thought i had this working at one point, i guess not.

i've been through the advanced installation guide.  it doesn't
mention the acpi-user-options bit, so i'm wondering what else
there is to read, for one thing....

well, anyway.

i put together a boot floppy, from a downloaded d1_image.  on close
inspection, it looks like it's missing a number of things, namely
the solaris/bootenv.rc file, the whole drivers directory, on
and on.  the boot floppy does have:

rules
rules.ok
the machine's profile file

i boot; it turns the screen black, i think it says
solaris boot environment                  page 1

at the top, and that's all that happens.

is there something wrong with d1_image?  and consequently
my floppy?  can you tell enough from what i've said already
to answer that?  (bootenv.rc isn't there, the solaris
dir is empty, but maybe it should be?)


i notice /tftpboot
does not have a pointer to an inetboot.* file, and that the
rm.<IP> is a trivial shell script--does nothing.  maybe /tftpboot
is okay.  in.tftpd is in inetd.conf; this server serves my
sparc boxes, too, and that's worked for a long time.  so we
should feel pretty good about tftp.

the partition is shared
202 > showmount -e
export list for csdsun2.arlut.utexas.edu:
/VOLUMES/arch/sparc/jumpstart (everyone)
/VOLUMES/arch/ia/jumpstart    (everyone)

the target machine is on the same subnet as the server; as are
all the sparcs i've successfully jumpstarted.

bootparams; i'm going to pretty-ize this, but it was all one
line, trust me.

203 > ypcat -k bootparams |grep smudged
smudged.arlut.utexas.edu
root=csdsun2.arlut.utexas.edu:/VOLUMES/arch/ia/jumpstart/OS/Solaris_9_2003-08/Solaris_9/Tools/Boot
install=csdsun2:/VOLUMES/arch/ia/jumpstart/OS/Solaris_9_2003-08
boottype=:in
sysid_config=csdsun2:/VOLUMES/arch/ia/jumpstart/Sysidcfg/smudged
install_config=csdsun2:/VOLUMES/arch/ia/jumpstart
rootopts=:rsize=8192

at this point, i'm perfectly prepared to believe i've overlooked anything.
so if you think i need to check tftp, say so.  that goes
for everything.

it's probably not the profile, right?  i know what the profile would
do on the sparc side, and there's no evidence that i get that
far along on the intel side.  then again, maybe it wouldn't look
the same.  but it never says it's making file systems, installing
packages, anything like that.  the profile might be messed up, but
it's not the problem at this stage, is it?

if you've got a way for me to test the tftp, lemme hear it;
just because i say it's okay, doesn't mean it is.  i don't have a
way to check it, that i know of, other than to test-boot a sparc.
if you've got another way, to check any or all of this, bring it
on.

i'll be grateful for anything you want to suggest.  i'm befuddled...

j.

-- 
Jay Scott		512-835-3553		 XXXX@XXXXX.COM 
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div.                   S224
University of Texas at Austin

2.jumpstarting x86; /a/etc/.UNCONFIGURED not removed


i jumpstart an x86 box to solaris 10.  when it reboots, is have to tell it:

terminal is a vt100
ipv6,
default route
kerberos
time zone
root password
and NFS 4, which is also probably legit.

my issue is that my sysidcfg file DEFINITELY HAS the answers
for ipv6 through the root password.

ahh, yes....  if if remove /a/etc/.UNCONFIGURED then
the only question is asks is about NFS 4.  why isn't .UNCONFIGURED
getting zapped?

as best i can remember, here's what /a/etc/.sysIDtool.state
looked like:  (the comments on right are the fuzzy part)
1	previoiusly configured
1	bootparams succeeded
1	on netowkr
1	extended network info
1	autobinder
1	subnets
1	root password
1	locale and terminal
1	security policy
vt100

j.


-- 
Jay Scott		512-835-3553		 XXXX@XXXXX.COM 
Head of Sun Support, Sr. Operating Systems Specialist
Applied Research Labs, Computer Science Div.                   S224
University of Texas at Austin

3.Unattented jumpstarting of X86 servers

G'day!

Jumpstarting a X86 server cannot be done completely unattented because 
you need a bootdisk now that you don't have a ok prompt to enter "boot 
net - install" from (if I understand correctly).

Is that also the case with the new V20z/V40z servers?

Thanks in advance!
- Morten Green Hermansen, Fanitas

4.jumpstarting x86?


Uwe Wolfram wrote:
> Seems my original posting did not get through...
> 
> My boss is thinking about purchasing an x86 cluster, arghhh.
> At least I can hope to persuade him of running Solaris instead of Linux.
> 
> My question is: Is it possible to jumpstart Solaris on Sun's x86 machines
> just like I'm able to do for Sparc?
> 
> Uwe
> 
> --
> anti-spam: Remove "dummy." from address above to obtain correct one

Yes, You can Jumpstart X86 machine as you Jumpstart Sparc.
A Sparc server can provide JumpStart files for both Sparc & X86 systems.

Shivakanth

5.Jumpstarting with multiple network interfaces

Hello!

When I jumpstart my V240 I want to configure all my 4 network interfaces and
not just only the primary device.
I have tried to have multiple network_interface statements in my sysidcfg
file but it does not seem to work.
Anybody tried this?

Thanks in advance,
- Morten Green Hermansen, Fanitas



6. Jumpstarting over 2 networks

7. [RFC][PATCH 11/12] generic timeofday i386/x86-64 specific clocksources

8. [PATCH 6/9] x86: add moorestown specific setup code



Return to unix

 

Who is online

Users browsing this forum: No registered users and 14 guest