Problems booting RH 8

10 More Discussions You Might Find Interesting

1. Solaris

solaris booting problems

hi am trying to get some knowledge on Solaris common trouble shooting problems.. can some one help me in getting most common issues.. and how to solve those issues. thanks in advance

2. UNIX and Linux Applications

Hi, I've just installed Centos 5.3 x86_64 into a CPU. I've done a yum update to update the version to Centos 5.4. I then installed mysql, php, apache and phpmyadmin into the system. After the installation of phpmyadmin the screen suddenly goes blank, but the monitor is still on, and the cpu...

3. Linux

Damn Small Linux Booting Problems

I recently downloaded a DSL iso file. I loaded the iso in VirtualBox and it worked perfectly, but when I wrote the iso to a CD using k3b and I tried booting it, I got an error. I tried booting from the disk in VirtualBox and got the same error. "FATAL: Could not read from the boot medium! System...

4. Solaris

Solaris 10: Problems booting off mirror drive -- Error 22: No such partition

Solaris 10 5/08 on Ultra 40 M2 It boots fine off primary disk but having issues booting off the mirror disk. I get this error when booting off mirror disk: Booting 'Solaris 10 ... Mirror disk' root (hd1,0,a) Error 22: No such partition Press any key to continue... Any...

5. Solaris

Problems during booting from mirror disk

Hi All, I have detached a mirror and primary disk from my Solaris box. On trying to boot from Primary disk, It boots up good. But from my mirror disk, it is not booting and giving me the login prompt Instead it goes to maintenance state by issuing a coredump. Can you explain why...

6. Solaris

booting from CD

Hello.. I am Still Learing Solaris .. when i try to Install Solaris 8 from its CD...i pressed STOP + A and i get a OK prompt screen. I then typed, "boot cdrom" and i am getting this error message. " FATAL: system is not bootable, boot command is disabled." How do we enable the boot...

7. UNIX for Dummies Questions & Answers

Having booting problems

I booted up my SUSE ver 10.1 linux box today. Went to the DOS-type login. Failed to display KDE. I understand this has something to do with levels. But how do I change the default? I know zero about Vi (and don't need to learn it). How do I get the system to boot to KDE again? Best...

8. UNIX for Dummies Questions & Answers

Unix 5.0.7 problems Booting

Hello there guys , I have a unix box that i just install on a HP VL400 , installation went all the way no problem. I get the BOOT: Hit enter and it goes to the point that you can see the all the hardware info. the problem is that freeses when gets to this point H oeminit Note: I put...

9. UNIX for Dummies Questions & Answers

Booting

Hi all, I've managed to get Mandrake 9 installed by disconnecting my 2 windows' drives. When I reconnect them Mandrake wants to take over. I figure it's time for the BootManager, or should I use a Linux specific one like Lilo? Or have I already stuffed up by not running Lilo at time of...

10. UNIX for Advanced & Expert Users

booting problems on solaris

When i try to boot my solaris 2.6 E220R server, i get this error message > INIT: cannot create /var/adm/utmp or /var/adm/utmpx >INIT: failed write of utmpx entry:" " >INIT: failed write of utmpx entry:" " INIT Single User Mode Press Ctrl-d for normal boot process or enter roots password...

LEARN ABOUT NETBSD

pciback

PCIBACK(4)						 BSD/xen Kernel Interfaces Manual						PCIBACK(4)

NAME

     pciback -- Xen backend paravirtualized PCI pass-through driver

SYNOPSIS

     pciback* at pci?

DESCRIPTION

     The pciback driver is the backend part of the PCI pass-through functionality that can be used by the Xen dom0 to export pci(4) devices to a
     guest domain.  To export a PCI device to a guest domain, the device has to be attached to pciback in the dom0.

     When the guest domain is NetBSD, the device attached to the pciback driver will attach to a xpci(4) bus inside the guest domain.

EXAMPLES

     To attach a device to the pciback driver, follow these steps:
	   1.	look for the device PCI ID, via pcictl(8).
	   2.	edit boot.cfg(5) and add the PCI ID to the list of PCI IDs that you want to attach to pciback, in bus:device.function notation.
		The list is passed to dom0 module via the pciback.hide parameter:
		      pciback.hide=(bus:dev.fun)(bus:dev.func)(...)
		See also boot(8).
	   3.	reboot dom0.
	   4.	add the PCI ID to the list of PCI devices in the domain configuration file:
		      pci = ['bus:dev.fun', '...']
	   5.	start the guest domain.

SEE ALSO

     pci(4), xpci(4), boot(8), pcictl(8)

HISTORY

     The pciback driver first appeared in NetBSD 5.1.

AUTHORS

     The pciback driver was written by Manuel Bouyer <bouyer@NetBSD.org>.

CAVEATS

     Currently, to attach a device to the pciback backend, this procedure has to be performed at boot(8) time.	In the future, it will be possible
     to do it without requiring a dom0 reboot.

SECURITY CONSIDERATIONS

     As PCI passthrough offers the possibility for guest domains to send arbitrary PCI commands to a physical device, this has direct impact on
     the overall stability and security of the system.	For example, in case of erroneous or malicious commands, the device could overwrite physi-
     cal memory portions, via DMA.

BSD
								  January 8, 2011							       BSD

Linux