12-12-2006
Also, one can use a
boot floppy to PXE boot when your card/BIOS doesn't directly support it.
9 More Discussions You Might Find Interesting
1. Red Hat
my redhat 9 will not boot. We had a power failure and when the power came back, my redhat linux will not boot.
The machine come up to grub prompt.
I tried the following from grub prompt
root (hd0, then press tab key
partition num:0 filesystem type unknown, partition type 0x83... (7 Replies)
Discussion started by: hassan2
7 Replies
2. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
3. 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
4. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
5. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
6. SCO
hi
SCO Unix 5.0.6 doesn't boot due to this problem:
not a directory
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
Knows someone howto solve it? (16 Replies)
Discussion started by: ccc
16 Replies
7. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 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. Red Hat
Hi guys,
I've been trying to set up a server for disk-less booting of remote machines on a network. The server host OS is RHEL6 and I have configured dhcp, tftp and nfs services which are proven to be working since I am able to install RHEL6 through pxe boot. Now I want it to serve for disk-less... (0 Replies)
Discussion started by: aninmuk
0 Replies
LEARN ABOUT OSF1
sys_attrs_bparm
sys_attrs_bparm(5) File Formats Manual sys_attrs_bparm(5)
NAME
sys_attrs_bparm - bparm subsystem attributes
DESCRIPTION
This reference page lists and describes attributes for the Boot Parameters (bparm) kernel subsystem. Refer to the sys_attrs(5) reference
page for an introduction to the topic of kernel subsystem attributes.
Identifies the device from which the system was last booted. This attribute corresponds to the console firmware environment vari-
able with the same name. Do not modify this value, which is set when the system boots.
A combination of flags that controls the boot loader and kernel. This attribute corresponds to the console firmware environment
variable with the same name. Values for the variable are: Boot to multiuser mode. By default, the kernel boots to single-user mode.
Enable the kdebug debugger to debug the kernel. By default, kdebug is not enabled in the kernel. Produce full dumps when the system
crashes. By default, partial dumps are produced. Prompt for an alternate kernel and special arguments when the system is booted. By
default, no questions are asked.
Set boot_osflags only at the console prompt or by using the consvar utility.
Identifies the boot device to be used when one is not included in the boot command line. This attribute corresponds to the console
firmware environment variable with the same name. Set bootdef_dev only at the console prompt or by using the consvar utility.
SEE ALSO
Commands: consvar(8)
Others: sys_attrs(5)
System Administration
sys_attrs_bparm(5)