02-13-2003
Quote:
Originally posted by Perderabo
Regarding the first question, you need to do a reset or a power cycle to make the change take effect. From the ok prompt, just type "reset".
I never heard of creator3d or elitem6, so I'll pass on question 2.
i did the power cycling. when i doa printenv, it shows that the boot setting is disk0:3... which is even more frustating because it still tries to boot from the net.
seriously... you've never heard of Creator3D or EliteM3/M6 cards? do you do most of your work on server class machines?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
hardware on my first FreeBSD server has crashed. i was planning on
swapping the HD into another machine, booting the generic kernel and then
custom tailoring it to the new machine specs.
however, i'm having a problem.
the new machine is using a promise ultra100 card. i don't have any... (2 Replies)
Discussion started by: xyyz
2 Replies
2. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
3. Solaris
I have a client with a V1280 onsite and it is having boot problems. Below is the message it is returning when trying to boot. Is this something that anybody has run into, or that you might be able to shed some light on?
{0} ok boot
/ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:f
SunOS Release 5.9... (3 Replies)
Discussion started by: xcwhitex
3 Replies
4. SCO
Hello those more knowledgeable than I:
I have been trying to get xp and SCO to coexist on the same system. I have tried several different ways to make both work, here's the list:
-install xp, image it, move the partition to the end of drive, verify it boots, image again,
-boot off of SCO... (6 Replies)
Discussion started by: stay0ut
6 Replies
5. Solaris
I have a pentium IV with 512 MB ram and 80 GB HDD.
I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies
6. Solaris
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies
7. Solaris
I 'm trying to configure a WAN boot server on Solaris10 x86 for sparc clients ..
when i try to set up the server m getting following error
./setup_install_server -w /var/apache2/htdocs/wanboot10/wpath /var/apache2/htdocs/wanboot10/ipath
ERROR: Cannot make WAN boot Image file on this... (6 Replies)
Discussion started by: fugitive
6 Replies
8. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
9. Solaris
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
10. Red Hat
I am installing Red Hat Linux 6.9 as a VM in Hyper-V on an HP laptop running Windows 10. After the install completes and the VM reboots, it gives me the message, "Detected CPU Family 6 model 142; Warning: Intel CPU model - this hardware has not undergone testing by Red Hat and might not be... (1 Reply)
Discussion started by: tigers580307
1 Replies
HY(4) Kernel Interfaces Manual HY(4)
NAME
hy - Network Systems Hyperchannel interface
SYNOPSIS
/sys/conf/SYSTEM:
NHY hy_controllers # Hyperchannel
DESCRIPTION
The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.
The network to which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl. The host's address is discovered by
reading the adapter status register. The interface will not transmit or receive packets until the network number is known.
DIAGNOSTICS
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies the device during autoconfiguration.
hy%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
hy%d: can't initialize. The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
an 11/750 where there are only 3 buffered data paths.
hy%d: NEX - Non Existent Memory. Non existent memory error returned from hardware.
hy%d: BAR overflow. Bus address register overflow error returned from hardware.
hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.
hy%d: Power Off Error, network shutdown. Power was really off in the adapter, network connections are dropped. Software does not shut
down the network unless power has been off for a while.
hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too big. Probable a driver bug. Shouldn't happen.
hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error. Shouldn't happen.
hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a non-existent state. Definite driver bug.
hy%d: watchdog timer expired. A command in the adapter has taken too long to complete. Driver will abort and retry the command.
hy%d: adapter power restored. Software was able to reset the power off bit, indicating that the power has been restored.
SEE ALSO
intro(4N), inet(4F)
BUGS
If the adapter does not respond to the status command issued during autoconfigure, the adapter is assumed down. A reboot is required to
recognize it.
The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed. The driver will believe that power has
failed only if it can not reset the power fail latch after a ``reasonable'' time interval. These seem to appear about 2-4 times a day on
some machines. There seems to be no correlation with adapter rev level, number of ports used etc. and whether a machine will get these
``bogus powerfails''. They don't seem to cause any real problems so they have been ignored.
3rd Berkeley Distribution August 20, 1987 HY(4)