07-10-2017
Looks like a botched kernel upgrade. Your modules do not match the kernel you are booting with.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I'm not sure if this is the right forum to post.
I had following setup before installing SUSE Linux:
Windows 98 installed on Primary partition
Windows XP installed on Extended Partition
When I installed SUSE, it shared space from primary partition and shrunk the size of Windows... (4 Replies)
Discussion started by: patras
4 Replies
2. Solaris
I had installed solaris 10 on 440 on disk 0. I had done ufsrestore on disk1 from tape and then rebooted
Rebooting with command: boot disk1
Boot device: /pci@1f,700000/scsi@2/disk@1,0 File and args:
SunOS Release 5.10 Version Generic_118833-24 64-bit
Copyright 1983-2006 Sun Microsystems,... (3 Replies)
Discussion started by: vr76413
3 Replies
3. OS X (Apple)
Hi friends I am newbiee to MACOS ,the thing is that i installed MAC OS X86 10.5.6 into my VAIO-VGN-CR343N series without any problem and after rebooting I was unable to boot into macos and tried options like -v -f but no progress..can somebody help me (1 Reply)
Discussion started by: srinivas2828
1 Replies
4. Hardware
I have a problem with one of my Sun 280R servers.
I'm unable to boot it. I've managed to get to the {ok} prompt from the RSC card.
Please see output below
ok show-devs
/virtual-memory
/memory
/aliases
/options
/openprom
/chosen
/packages
/openprom/client-services... (2 Replies)
Discussion started by: soliberus
2 Replies
5. Red Hat
Hello,
I have a test PC running Fedora 10. Friday evening it was working fine, I have some perl scripts which are scheduled to run every morning.
But when I started work this morning, I found I cannot ping the machine. When I switched on the monitor, I saw the GRUB promt :(. I am not sure... (10 Replies)
Discussion started by: SivaramaRaju
10 Replies
6. Ubuntu
I am not able to boot into my ubuntu. Grub gives me this message
How do I boot linux? (6 Replies)
Discussion started by: locoroco
6 Replies
7. Solaris
This is what is displayed on the screen as the system tries to boot and then hangs:
0>Test CPU(s)....Done
0>Interrupt Crosscall....|
SC Alert: DHCP negotiation failed, perhaps misconfigured or no DHCP server avail
able
Done
0>Init Memory....|
SC Alert: Host System has Reset
'Done
0>PLL... (2 Replies)
Discussion started by: kenosongo
2 Replies
8. Red Hat
hi guys,
I was using kernel-3.1.2-1 in fedora 16. then updated to kernel-3.1.4-1. after reboot now grub shows command prompt instead of boot menu. i tried to load manually with:
set root=(hd0,msdos3)
linux /vmlinuz-3.1.4-1.fc16.x86_64
initrd /initramfs-3.1.4-1.fc16.x86_64.imgbut in the middle... (0 Replies)
Discussion started by: majid.merkava
0 Replies
9. Solaris
Update:
The / file system (/dev/rdsk/c1t0d0s0) is being checked
fsck unable to stat
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0).
Root password for system maintenance (control-d to bypass):
I am unable to hit control-d to by pass.
I... (50 Replies)
Discussion started by: br1an
50 Replies
10. Ubuntu
Hi;
I had Windows Server 2003 and performed a fresh Ubuntu Server 15 installation.
After installation, Ubuntu server not booting
I guess there is boot problem conflicting with my old Windows Server.
This is my pastebin:
http://paste.ubuntu.com/13851828/
Any help to start my new... (1 Reply)
Discussion started by: gc_sw
1 Replies
LEARN ABOUT FREEBSD
boot.config
BOOT.CONFIG(5) BSD File Formats Manual BOOT.CONFIG(5)
NAME
boot.config -- Configuration file for the boot blocks
DESCRIPTION
The boot.config file contains options for the FreeBSD boot block code.
When the FreeBSD boot loader runs, it searches the ``a'' slice of the boot partition for a boot.config file (as a result, slices which are
missing an ``a'' partition require user intervention during the boot process). If the boot.config file is found, its contents are used as
the default configuration options for the boot block code and are echoed to the system console.
A valid format of this file is to put BIOS drive number, a controller type, a unit number, a partition, a kernel file name, and any other
valid boot(8) option on a single line, as it is done at the ``boot:'' prompt.
The options related to the boot image selection described below and all the other options available for boot.config are documented in detail
in the boot(8) manual page.
FILES
/boot.config parameters for the boot blocks (optional)
EXAMPLES
The command:
# echo "-P" > /boot.config
will activate the serial console of FreeBSD.
The command:
# echo "1:ad(1,a)/boot/loader" > /boot.config
will instruct the second stage of boot(8) on the first disk to boot with the third boot(8) stage from the second disk.
The command:
# echo "1:ad(1,a)/boot/loader -P" > /boot.config
will do both of the above.
SEE ALSO
boot(8), loader(8)
AUTHORS
This manual page was written by Daniel Gerzo <danger@FreeBSD.org>.
BSD
May 13, 2007 BSD