Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- From: "den" <dchang.04@xxxxxxxxx>
- Date: 28 Mar 2007 13:39:20 -0700
On Mar 27, 12:20 pm, Darren Dunham <ddun...@xxxxxxxxxxxxxxxx> wrote:
den <dchang...@xxxxxxxxx> wrote:
Solaris 8. Is driver required for booting or only for access after theI think the problem is more severe than what I explained.
system is up?
For Intel based systems Solaris requires a DCA (Disk Configuration
Assistant).
That was why I asked the question above. DCA is required for devices
that you need to access before Solaris is running (usually boot
devices).
And I don't know of anyway to provide this DCA except through floppy.
There are probably some ways because the boot environment is exported
after Solaris is running, but I don't have a pre-GRUB system running any
longer to test on.
I seem to remember being able to shove an ITU into the right directory
or something similar....
In other words I can't install Solaris without floppy access.
So you answered one question: I can install a driver with pkgadd.
Second question then is: do you think I can add a driver to one
system (like a transplant if you will) and move the disks to the
other?
It's possible. As long as all the drivers are in the system, you might
be able to rescan the hardware at boot and have it come up. However,
it's not guaranteed.
I've actually got another problem. The good Compaq is now not so
good.
I installed a Patch cluster the other day and one of the patches wrote
over
my Hardware configuration section (I believe it's the eeprom
settings).
So when I boot it jumps into a kernel debugger. I tried booting from
the
cdrom but it still goes into the debugger. Is there anyway I can
recover
that section? Or do I have to do everything from scratch again?
Hmm. The "eeprom" is just some files in the boot area (usually mounted
as /boot). I think it's in the bootenv.rc file. Does that file have a
'boot-file' set?
--
Darren Dunham ddun...@xxxxxxxx
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
I'm new to Solaris system administration. I've been playing
with the system off and on for 2 years now. So I'm alittle
confused by your question. If bootenv.rc file is sitting within
the filesystem and I can't access the filesystem without
booting then how can I access the file to check that
setting? Can you suggest any other way?
I tried booting off the cdrom. Just like on the SPARC I was
hoping to do a:
ok> boot cdrom -s
so that I could see what I could do. But when booting from
the cdrom it goes into the Hardware configuration routine
and after pressing F2 it jumps straight into the boot
debugger (my error ... it wasn't a kernel debugger .. sorry).
The prompt is:
[c000:2dd7]
So in both booting options (hard drive and cdrom) it kicks
me into a boot debugger. That is why I assume it's that
section that requires hardware configuration data.
So do you think I can modify it without hosing my system?
Thanks for your replies Darren,
Dennis.
.
- Follow-Ups:
- Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- From: Darren Dunham
- Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- References:
- Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- From: den
- Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- From: Darren Dunham
- Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- From: den
- Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- From: Darren Dunham
- Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- Prev by Date: T1000 vs T2000
- Next by Date: RAM options for Sun Blade 150?
- Previous by thread: Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- Next by thread: Re: Add new hardware driver to Solaris 8 on a Compaq Proliant 1600
- Index(es):
Relevant Pages
|
|