|
Home > Archive > Unix True 64 > October 2004 > SRM parameters from the OS?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
SRM parameters from the OS?
|
|
| Homonnai Mihaly 2004-10-11, 7:50 am |
| hi,
how can i access the srm parameters from the os level? i used to know it,
but unfortunatelly have forgotten.
thx
| |
| Adam Price 2004-10-15, 9:28 pm |
| On Mon, 11 Oct 2004 11:42:18 +0000 (UTC), Homonnai Mihaly wrote:
> hi,
>
> how can i access the srm parameters from the os level? i used to know it,
> but unfortunatelly have forgotten.
> thx
consvar
Be careful though there are console variables which can crash your system
if changed when Tru64 is booted.
Adam
| |
| Stuart Fuller 2004-10-15, 9:28 pm |
| Adam Price wrote:
> On Mon, 11 Oct 2004 11:42:18 +0000 (UTC), Homonnai Mihaly wrote:
>
>
> consvar
> Be careful though there are console variables which can crash your system
> if changed when Tru64 is booted.
And, those console variables are...?
--
Stu
| |
| Bob Harris 2004-10-15, 9:28 pm |
| In article <40vhkc.b7b.ln@dadsys2.fuller.local>,
Stuart Fuller <stufuller@usa.net> wrote:
> Adam Price wrote:
>
>
> And, those console variables are...?
man consvar
-l List the values of all variables supported by this platform
that are not disabled. This is similar to the show SRM
console command.
/sbin/consvar -l # from my AlphaStation 500au (Miata)
auto_action = BOOT
boot_dev = dsk0
bootdef_dev = dsk0
booted_dev = dsk0
boot_file =
booted_file =
boot_osflags = A
booted_osflags = A
boot_reset = OFF
enable_audit = ON
license = MU
char_set =
language = 0x36
tty_dev = 0
Bob Harris
| |
| Adam Price 2004-10-15, 9:28 pm |
| On Tue, 12 Oct 2004 21:05:08 -0400, Stuart Fuller wrote:
> Adam Price wrote:
>
>
> And, those console variables are...?
The one in particular I was thinking of was to do with the processor
pre-cache. It could be turned on and off with consvar but turning off the
cache on a running system made it crash.
You may be protected from that by the latest flavours of Tru64 but then
again...
Adam
| |
| Homonnai Mihaly 2004-10-15, 9:28 pm |
| Adam Price <adam+usenet@pappnase.co.uk> wrote:
> On Mon, 11 Oct 2004 11:42:18 +0000 (UTC), Homonnai Mihaly wrote:
[vbcol=seagreen]
> consvar
> Be careful though there are console variables which can crash your system
> if changed when Tru64 is booted.
> Adam
thx Adam.
another question 
how can i change the ethernet port parameter (eg. speed, simplex/duplex)
from within os level? or it is possible only from srm? if it is possible
from os, should i reboot the machine?
thx
homer
| |
| Bob Harris 2004-10-15, 9:28 pm |
| In article <ckiqic$cu4$1@analog.eik.bme.hu>,
Homonnai Mihaly <homer@norb.rulez.org> wrote:
> Adam Price <adam+usenet@pappnase.co.uk> wrote:
>
>
>
> thx Adam.
>
> another question
> how can i change the ethernet port parameter (eg. speed, simplex/duplex)
> from within os level? or it is possible only from srm? if it is possible
> from os, should i reboot the machine?
> thx
> homer
ifconfig tu1 down; ifconfig tu1 speed 200; ifconfig tu1 up
See man ifconfig for valid values for the speed option. Use your
ethernet device for tu1 (in my case tu1 happens to be a DE500 card)
You can also use
lan_config -i tu1 -m utp -s 100 -x 1 -a 1
Again see man lan_config for details on the commands usage.
If you do not change the speed at the >>> prompt, then you will need to
rerun one of the above commands each time you reboot. Look at
/etc/inet.local (man inet.local) for a possible place to stick such
commands.
I don't really know what I'm talking about, I just got the information
from an in-house web page at work. Test before you buy :-)
Bob Harris
| |
| Marco Benton 2004-10-15, 9:28 pm |
| Bob Harris wrote:
> In article <ckiqic$cu4$1@analog.eik.bme.hu>,
> Homonnai Mihaly <homer@norb.rulez.org> wrote:
>
>
>
>
> ifconfig tu1 down; ifconfig tu1 speed 200; ifconfig tu1 up
>
> See man ifconfig for valid values for the speed option. Use your
> ethernet device for tu1 (in my case tu1 happens to be a DE500 card)
>
> You can also use
>
> lan_config -i tu1 -m utp -s 100 -x 1 -a 1
>
> Again see man lan_config for details on the commands usage.
>
> If you do not change the speed at the >>> prompt, then you will need to
> rerun one of the above commands each time you reboot. Look at
> /etc/inet.local (man inet.local) for a possible place to stick such
> commands.
>
> I don't really know what I'm talking about, I just got the information
> from an in-house web page at work. Test before you buy :-)
>
> Bob Harris
also... you *must* use lan_config or ifconfig for the DE600 as the SRM
settings dont take. maybe it's fixed in newer SRM versions tho. i dont
have a new Marvel or SC45 to test on. ;-)
|
|
|
|
|