Prev: fsck error: "BAD STATE 0x52 TO BLKERR"
Next: fsck -n
From: Scott Howard on 7 Aug 2006 09:25
social <mail4ashok(a)gmail.com> wrote:
> Is there a way to disable a NIC from OK/ALOM on a t2000. I looked
> at disablecomponent, but that disbales a whole slot? OK prompt did not
> recognize asr-disable*

There is, but it's ugly...

Presuming you only want to hide them once...

set auto-boot? to false, and type "reset-all". Once you can get back to
the OK prompt you can set auto-boot? back to true if you want (we need
to make sure that when you type "boot" in a few steps it doesn't
reset first).

Run "show-nets" and get the path for the device you want to hide. I don't
have a T2000 handy, but lets say the path is /pci(a)1f,0/pci@1,1/network@1,1

Type the following at the OK prompt :
" /pci(a)1f,0/pci@1,1/network@1,1" $delete-device drop

So that's
<quote><space><device_path><quote><space> $delete-device <space> drop
^---- Don't forget this space.

Once you've done that, the next time you type "boot" the devices will
not exist.

If you want to do it permanently you need to put it in the nvram.
Type "nvedit" and then enter the following :
0: probe-all install-console banner
1: " /pci(a)1f,0/pci@1,1/network@1,1" $delete-device drop
2: " /pci(a)1f,0/pci@1,1/network@1,2" $delete-device drop
3:
^C

(one for each device, Ctrl-C to exit)

Once you've done that, type "nvstore" to save it, and then make sure
that this will be used by typing "setenv use-nvramrc? true"

After that you'll need a reset-all, and the devices will be permanently
remove - or at least until you remove the above with nvedit.

Scott
From: social on 7 Aug 2006 13:06
Scott Howard wrote:

> After that you'll need a reset-all, and the devices will be permanently
> remove - or at least until you remove the above with nvedit.
>
> Scott

great tip

Thanks
Ashok

First  |  Prev  | 
Pages: 1 2
Prev: fsck error: "BAD STATE 0x52 TO BLKERR"
Next: fsck -n