[SOLVED] Weird Boot Problem

I carried out an -Syu on my eeepc a couple of weeks ago. Unusually, this resulted in all kinds of error messages at boot time. most of which I've hunted down and squashed. The machine has functioned correctly throughout.
However, there is one message which I cannot find. When the system boots, the on-screen command line output displayed before the desktop is loaded (lxde) shows a "Login:" prompt, which is followed immediately by the display of an error message
FATAL: Module and not found
I can't find this in any of the logs, so I don't know where to begin. Module "and"??!!
Any advice would be very welcome.
Thanks in advance
Last edited by myrlin (2011-10-28 14:10:21)

I have just discovered that this message is being generated by UFW.
I have it in my Daemons array.
A manual start (or restart) also fails with the same message.
Strangely, when accessing UFW through GUFW, all seems to be normal.
"ufw status" reports "active". Curious!
**EDIT**
I finally solved the problem by completely removing ufw and gufw (including ALL configuration files), then re-installing. I never did find out what had been corrupted, or how, but - hey - life's too short!!
Many thanks to everyone for their help and support
Last edited by myrlin (2011-10-28 14:13:36)

Similar Messages

KT6V Weird boot problems

Hi..
I'm having this weird boot problem (and no it doesn't seem to be the standard one)
OK..
I have the following :
AMD Athlon 2000+
KT6V LSR mainboard
2x 256 Crucial PC2700 memory
IDE Hard Disk (120gb segate)
Creative 5700ultra Graphics card (AGP)
Cd Rom
Chieftec 400w PSU
WinXP Pro
If I set my CPU FSB to 100mhz (everything else on auto).. win Xp pro boots fine and all is pretty good except that my chip is now seen as a lowly 1.25ghz..
If I then set my CPU FSB to 133 or 166 then the machine boots (ie it beeps etc..).. starts to load windows xp (I get the logo and that's when the problem happens) and either black screens (ie.. nothing and the monitor turns off) or blue screens with the windows message saying that windows has detected a hardware fault and has halted the system..
I know my memory, chip, heatsink etc all work because just over an hour ago they all worked fine in my KT3 ultra.
What is going on as I've tried almost everything to try and solve this, with the only option to set the FSb to 100mhz which is incorrect for my CPU.
How do I fix this.
I've looked through the forum but this is not the same problem as simple reboots.. this is weird.
If I can't fix this then I guess it'll be send it back.. which is a shame because I like MSi motherboards.
Thanks
Slippery

Hi..
I've checked the CPU heatsink.. and nothings wrong !
(Can't check the voltage but I know the PSU is Ok as I did run it in a custom case with 4 Cd writters, 4 HDs, loads of lights etc.. before I moved to this new plain case tonight)
What's weird is that set at 100FSb it's fine but at 133 or 166 it just crashes after the loading XP logo is displayed. Up until that point it's all fine.
But why does it run Ok at 100mhz and not 133mhz ?
Please help.. before I end up fixing this with a hammer !
Thanks
Slippery

[SOLVED] DBUS boot problems - Mounting system devices as a normal user

I have the [testing] and [community-testing] repositories enabled. A few days ago, probably due to an update, I started having trouble mounting devices and the shutdown/reboot options don't show up anymore on the LXDE exit menu.
I use gvfs for mounting devices as a normal user with PCManFM or Thunar. The error message is "Authentication is required".
After some testing, I found out that by restarting dbus, I could start mounting devices again:
/etc/rc.d/dbus restart
So my guess is that there's some problem with dbus startup. I have it in DAEMONS of rc.conf, as well as .xinitrc, the daemon seems to start correctly on boot, and it worked previously, so I have no idea of what could be wrong.
My ~/.xinitrc:
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
eval 'dbus-launch --sh-syntax --exit-with-session'
fi
numlockx && exec ck-launch-session dbus-launch startlxde
My /etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# DAEMON_LOCALE: If set to 'yes', use $LOCALE as the locale during daemon
# startup and during the boot process. If set to 'no', the C locale is used.
# HARDWARECLOCK: set to "", "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# Note: Using "localtime" is discouraged, using "" makes hwclock fall back
# to the value in /var/lib/hwclock/adjfile
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# Note: if unset, the value in /etc/localtime is used unchanged
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="ca_AD.UTF-8"
DAEMON_LOCALE="no"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Andorra"
KEYMAP="es"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
# Replace every !module by an entry as on the following line in a file in
# /etc/modprobe.d:
# blacklist module
# See "man modprobe.conf" for details.
MODULES=()
# Udev settle timeout (default to 30)
UDEV_TIMEOUT=30
# Scan for FakeRAID (dmraid) Volumes at startup
USEDMRAID="no"
# Scan for BTRFS volumes at startup
USEBTRFS="no"
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="localhost"
# Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
# Wired network setup
# - interface: name of device (required)
# - address: IP address (leave blank for DHCP)
# - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
# - broadcast: broadcast address (ignored for DHCP) (optional)
# - gateway: default route (ignored for DHCP)
# Static IP example
# interface=eth0
# address=192.168.0.2
# netmask=255.255.255.0
# broadcast=192.168.0.255
# gateway=192.168.0.1
# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=
interface=eth0
address=
netmask=
broadcast=
gateway=
# Setting this to "yes" will skip network shutdown.
# This is required if your root device is on NFS.
NETWORK_PERSIST="no"
# Enable these netcfg profiles at boot-up. These are useful if you happen to
# need more advanced network features than the simple network service
# supports, such as multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
# If you are sure nothing else touches your hardware clock (such as ntpd or
# a dual-boot), you might want to enable 'hwclock'. Note that this will only
# make a difference if the hwclock program has been calibrated correctly.
# If you use a network filesystem you should enable 'netfs'.
DAEMONS=(hwclock syslog-ng network crond alsa dbus cupsd)
Thanks!
Last edited by gamezelda (2011-11-08 19:28:04)

I solved it.
The Wiki page for Mounting for normal users with PCManFM tells to create a "/etc/polkit-1/localauthority/50-local.d/55-myconf.pkla" file specifying the privileges to grant to the user. The problem is that it does not include the privilege needed to mount internal drives (which was what I was trying to mount). To fix it, I added:
;org.freedesktop.udisks.filesystem-mount-system-internal
To the "Action=..." line.
(Though I have no idea why it worked before it broke, or why restarting dbus after initializing my WM fixed it.)
As for the power issues, I've concluded that it was working, but restarting dbus after initializing my WM broke it (my bad for not checking it before restaring dbus). So it all works now.

How to solve a boot problem

I was working on my Mac and it was very slow, so i turned it off (it was like quarter and hour while shutdown). After, i tried to boot it again, but didn't boot, so i entered Verbose mode. Error was "disk0s2: media is not present". I entered sigle user mode and i did "fsck -fy". It did the check and it was "The volume Macintosh HD appears to be OK. FILE SYSTEM WAS MODIFIED. I did fsck -fy again (i read on a forum that is necessary to do this till it doesn't appear FILE SYSTEM WAS MODIFIED) and it didn't appeared, only appered again "The volume Macintosh HD appears to be OK", so i logged out, but the disk0s2: media is not present was on screen another time. I booted from Mac OS X installation DVD, and i opened Disk Utility. It appeared the wait cursor and freezed. I held the Power button for shutdown and booted again from same DVD. I selected the installation program and when it checked the HDs for install it appeared Macintosh HD with 159'7 GB and 31'97 GB free, but when HD check finished, it disappeared. After doing that like 5 times, Macintosh HD didn't appear anymore when checking. From the single user mode i can enter to HD directories, like /Applications/Parallels or /Applications/ToySight etc. I need help for how to boot again my Mac or how to reinstall Mac OS without losing anything, or how to do a backup. Thanks.

CAH4E3 wrote:
Got my new customized iMac 27' yeasterday. After installing some soft, I decided to install Windows 7 as second OS on Boot Camp. After clicking the Boot Camp Assistant icon, programm opens, and immediately it shows error "Boot Camp Assistaint does not support Windows installation on this iMac 3TB" or something like that (I have a russian version of dashboard/OS). Only option available at that moment - button "OK", which exits Boot Camp A|ssistant.
So... Any suggestions on how to solve the problem? I really need Windows as second OS, and don't want to install it like a virtual/emulator machine.
My customized iMac "loadout" is Core i7 3.4, 16Gb DDR, Nvidia GeForce 680MX 2Gb, 3TB Hard Drive.
P.S. I thought this may be solved by separating Hard Drive into partitions (main, which is for Mac OS, and little tome for Windows, formated into MS DOS FAT system), still - this has not helped me.
There is a thread covering this subject here. I would advise you to read the whole thread before trying the 'solution'.

Macbook Pro weird boot problems

Hello!
I have a macbook Pro (late 2012) with OS X Yosemite (latest update) and I have some weird stuff going on in it...
2 days ago, I was using normally it, as I use it for work, when it suddenly freezes (never happened before). when i turn it on again, a empty symbol shows instead of the grey apple until i turn it off.
then, when i opened the recovery mode to see if my HD was damaged or something, it just do not shows my HDD at all to verify for integrity. I trun it off and let it be.
After several hours later, i decided to try to boot it again, and, for my surprise, it boots normally and all my files are normal. But after 10-15 minutes backing up all my important files to cloud services, it begins to be really slow. The spinning disk is shown even when i tried to close a finder window, move simple pages files or even to open the top menu to shut it down. The weird part is going even crazier: when i put a freezing gel (a gel packet that freezes and thaw without water is involved) under the macbook, the slowness is off and it works almost at normal speed. when the freezing effect is off, the slowleness is back
All this parts repeats very often.. sometimes the empty symbol appears when booting, sometimes it boots normally and after several minutes it becomes really slow. I tried to diagnose if a hardware problem was involved (pressing "D" after pushing the power button), but no problems were found at all.
what is going on? do you guys even had this? I hope it´s not the logic board!
(Sorry for my bad english)

The startup drive is failing, or there is some other internal hardware fault.
Back up all data on the drive immediately if you don't already have a current backup. There are ways to back up a computer that isn't fully functional—ask if you need guidance.
Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.
If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.
Keeping your confidential data secure during hardware repair
Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.
*An SSD doesn't need to be zeroed.

Spin the wheel of weird boot problems!

Hey! First time Mac owner here.
So, I bought this poor little 13" white Macbook off a guy who had clearly abused it and I'm trying to nurse it back to health. I'm trying to fix it, and then wipe the hard drive and install a fresh copy of the best OS I can get for it. It's gradually getting better, but I'm still having some problems, so I figured I'd ask you guys for help.
_Here's what I'm working with:_
- 13" white macbook
- OSX 10.4.11
- 60GB HD
- 2GB RAM
_Here's what I've done so far:_
- FIRST I took the giant "Valvoline" sticker off the back.
- Then I replaced the broken left display hinge.
- Now I'm trying to get it to WORK properly.
_Here's what it WAS doing / not doing:_
- Not booting or, booting without the screen turning on.
OR
- Not booting and just repeatedly checking disk drive.
I reset the SMC and got the screen back (sometimes). Then after multiple attempts, I got the thing to boot and I tried to update the SMC firmware (which it told me was already updated), then I uninstalled all the crap-tacular software the guy had put on it. Then I downloaded a program called "MainMenu", and ran all the Mac maintenance processes it had.
_Here's what it's doing / not doing now:_
- Sometimes it boots without the screen coming on. (At least that's what I assume it's doing.)
- Sometimes it boots ok, and I can use it as normal, but only for UP TO 30 minutes or so before the screen goes black and it checks the disk drive and then does nothing.
- Sometimes it doesn't wait for the OS loading status bar to finish before displaying the desktop and letting me use the computer, but sometimes it does. Is that normal?
Next I'm going to do some research and make sure I've got the right RAM in there and make sure it's properly installed and seated. Maybe it's a bad logic board, maybe its just a bad SMC chip, maybe it's a problem with the magnetic switch, maybe I just have it sitting to close to my Dell laptop and it's angry. I'm not sure. Any advice you guys have for me would be great.
Also, can anybody tell me what is the recommended best OS for this model?
Thanks!
~Dave

Actually, I think this MIGHT just be a problem with the magnetic switch that puts it to sleep when the thing closes. The "crashing" that I'm experiencing is actually just the screen going black and not coming back on, and I've actually got it to come back on today by closing the lid and opening it back up. Hmmmm...

Weird booting problems since 10.7.4 update

I have a 2006 MBP 2,2 which is now taking over 10 minutes to boot since updating to 10.7.4.
When it boots the Apple logo does come up almost straight away, it then stays for 5-6 minutes, before disappearing to the 'linen' for another 5 minutes, then the login screen comes up. From there it enters the desktop normally and afterwards the computer is as responsive as it ever was under Lion (ie not very!).
I have repaired permissions and I have verified the disk (which reports no errors).
I cannot reboot from DVD as the superdrive is toast. However, I cannot reboot in Target Disk mode either. Holding down T when the computer boots up leads to nothing happening, no Apple Logo, just a grey screen. Going into Startup Disk and telling it to reboot in target disk mode caused me no end of stress! When it rebooted nothing happened again. Eventually, after hard restarting it several times, I left it. No less than 25 minutes later, 25 minutes!, the Apple logo appeared and it booted normally (ie its 10+ minute boot into the OS).
Holding down shift, C, D, Command-V, Command-S leads to nothing happening at restart (or maybe it is just that I get bored of holding them down after about 5 minutes), however resetting the PRAM/NVRAM with Command-Option-P-R worked in a few seconds as I would expect.
Any ideas ?? (At nearly 6 years old it will not be going to be repaired by Apple.)
Cheers.

See if this is the explanation to your problem:
http://reviews.cnet.com/8301-13727_7-57451440-263/thunderbolt-update-plaguing-ma cbook-pros-with-kernel-panics/
Ciao.

[SOLVED]Dual boot problem with an Asus UX31A (EFI)

I never did an EFI install before and I still don't understand how it works however following the Zenbook wiki, I have successfully installed Arch. Now I can't boot Windows 7 anymore. I am using grub2, have installed os-prober. Grub menu has windows 7 entry but when used prompts a wrong EFI file path error.
My partition table is:
[root@zenbook sonay]# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 238.5G 0 disk
├─sda1 8:1 0 200M 0 disk
├─sda2 8:2 0 128M 0 disk
├─sda3 8:3 0 98.6G 0 disk
├─sda4 8:4 0 4G 0 disk
├─sda5 8:5 0 90.7G 0 disk
├─sda6 8:6 0 512M 0 disk /boot/efi
├─sda7 8:7 0 3.9G 0 disk
├─sda8 8:8 0 10G 0 disk
├─sda9 8:9 0 200M 0 disk /boot
└─sda10 8:10 0 30.3G 0 disk /
sdc 8:32 0 931.5G 0 disk
└─sdc1 8:33 0 931.5G 0 disk /run/media/sonay/My Passport
/dev/sda1 used to be Windows 7 EFI partition. Gparted says it is flagged as boot.
What I did to install arch:
Partitioned /dev/sda5 with windows disk manager to create linux partitions and formatted the new partitions with gparted as the noob I am.
created /dev/sda6 for EFI boot
created /dev/sda9 for boot partition
created /dev/sda10 as root.
Did not touch
/dev/sda1 which was the EFI partition named SYSTEM
/dev/sda2 which was windows boot partition
/dev/sda3 which was windows C:,
/dev/sda4 and /dev/sda7 which I don't know what they used to be (possible for Asus fast wake up or swap whatever)
/dev/sda8 which is recovery partition.
I did not touch any grub files, except /etc/default/grub
[sonay@zenbook ~]$ cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
Finally my /boot/grub/grub.cfg is:
[sonay@zenbook ~]$ cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=1
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0"
GRUB_CMDLINE_LINUX=""
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
[sonay@zenbook ~]$ cat /boot/grub/grub.cfg
cat: /boot/grub/grub.cfg: Permission denied
[sonay@zenbook ~]$ su
Password:
[root@zenbook sonay]# cat /boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_gpt
insmod ext2
set root='hd0,gpt10'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt10 --hint-efi=hd0,gpt10 --hint-baremetal=ahci0,gpt10 cf66f05a-418c-4517-a0e0-af01b3be4a67
else
search --no-floppy --fs-uuid --set=root cf66f05a-418c-4517-a0e0-af01b3be4a67
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=1
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-cf66f05a-418c-4517-a0e0-af01b3be4a67' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 42d2ba69-758d-4a54-9482-ae5d60866a52
else
search --no-floppy --fs-uuid --set=root 42d2ba69-758d-4a54-9482-ae5d60866a52
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=cf66f05a-418c-4517-a0e0-af01b3be4a67 ro quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-cf66f05a-418c-4517-a0e0-af01b3be4a67' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt9 --hint-efi=hd0,gpt9 --hint-baremetal=ahci0,gpt9 42d2ba69-758d-4a54-9482-ae5d60866a52
else
search --no-floppy --fs-uuid --set=root 42d2ba69-758d-4a54-9482-ae5d60866a52
fi
echo 'Loading Linux core repo kernel ...'
linux /vmlinuz-linux root=UUID=cf66f05a-418c-4517-a0e0-af01b3be4a67 ro quiet init=/bin/systemd add_efi_memmap elevator=noop i915.i915_enable_rc6=1 pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nmi_watchdog=0
echo 'Loading initial ramdisk ...'
initrd /initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-5246C0D846C0BE4B' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt3'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 5246C0D846C0BE4B
else
search --no-floppy --fs-uuid --set=root 5246C0D846C0BE4B
fi
chainloader +1
menuentry 'Windows Recovery Environment (loader) (on /dev/sda8)' --class windows --class os $menuentry_id_option 'osprober-chain-3C98C9B298C96B4A' {
insmod part_gpt
insmod ntfs
set root='hd0,gpt8'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt8 --hint-efi=hd0,gpt8 --hint-baremetal=ahci0,gpt8 3C98C9B298C96B4A
else
search --no-floppy --fs-uuid --set=root 3C98C9B298C96B4A
fi
drivemap -s (hd0) ${root}
chainloader +1
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
SOLUTION:
first I needed to mount Windows EFI partition which was /dev/sda1, so :
mount /dev/sda1 /mnt
Then issue the following commands and take note of the outputs:
grub-probe --target=fs_uuid /mnt/EFI/Microsoft/Boot/bootmgfw.efi
which outputs: 18DF-E58E and
grub-probe --target=hints_string /mnt/EFI/Microsoft/Boot/bootmgfw.efi
which outputs: --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
Finally edit the os-prober entry to the following in /boot/grub/grub.cfg
menuentry 'Windows 7 (loader) (on /dev/sda3)' --class windows --class os $menuentry_id_option 'osprober-chain-5246C0D846C0BE4B' {
insmod part_gpt
insmod fat
insmod search_fs_uuid
insmod chain
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1 18DF-E58E
chainloader /EFI/Microsoft/Boot/bootmgfw.efi
Last edited by sonay (2012-10-07 18:20:20)

grub-probe --target=hints_string /boot/efi/EFI/Microsoft/Boot/bootmgfw.efi
--hint-bios=hd0,gpt1 --hint-efi=hd0,gpt1 --hint-baremetal=ahci0,gpt1
Sorry, no need to anymore. Thanks anyways.
Last edited by sonay (2012-10-07 18:08:39)

K8MM3 (MS-7181) weird boot issue

Hello,
I have bought a K8MM3 (not V) MB and I have a weird boot problem.
I am using a 40 gig NON SATA drive, I installed XP, all went fine, on the final reboot once all is done I get a message saying "non system disk...".
I went to the BIOS, deactivated the SATA section since I'm not using it and the problem remains.
The ONLY way to make my computer boot is as follows :
BIOS boot order is set as HDD, nothing else and "try other boot devices" is enabled.
If I have a bootable CD in the drive (XP or anything else) after the POST I get the update escd AND DMI messages, then nothing for 10-15 seconds, then a message "BOOT FROM CD :" then the CD spins and I get the boot message "press any key to boot from CD" and if I let this message go away the computer boots normally on the standard NON SATA drive....
SO it seems the BIOS is all screwed up and wants to boot on SATA drive no matter waht and tests normal IDE drives only if everyhting else fails.
The BIOS I have on this board is 1.5 but I didn't see anything newer on the sites, how can i solve this ANNOYING problem ?
Thanks

What brand drive is this?
As it looks a jumper problem to me.
If it's a WD drive, then the jumpers are different then other brands:
Standalone: Jumperless
Master with slave: Jumpered master
Slave with master: Jumpered slave

K8N Neo2 Windows XP Boot problems

I've recently built a new machine based on the K8N Neo 2 & Athlon 64 3500 and am having intermittant problems during boot into Windows XP.
Basically the machine seems to hang just as it gets to the 'Windows XP' logo. The screen looks blank, but if you look very carefully the logo is displayed very faintly. I have tried connecting the startup disk to both SATA1 and SATA3 with the same results as at first I thought it may be some kind of driver problem. I didn't have to install any SATA drivers during the XP install which surprised me.
I have also run Memtest86 on the two sticks of 512Mb PC3200 Geil Ram which seemed to test OK.
Once running the machine is stable, its just annoying that it may take 2 or 3 tries to get it up and running.
Any help or suggestions would be very much appreciated.
The full spec of the machine is as follows:
K8N Neo 2
Athlon 64 3500
Geil Value PC3200 512Mb x2
Maxtor Diamond Max 9 80Gb (Boot Disk)
Maxtor Diamond Max 10 200Gb
Sapphire ATI Radeon 9600XT
Andi

I will not install the nForce IDE drivers on the (I guess soon) reinstall. I've read that the PS/2 keyboard also could be the badguy in this weird boot problem but I cant understand why and how the keyboard could add time to the bootup sequence only sometimes, I guess that it has something to do with the XP keyboard driver ??..
Anyone with any other tips is welcome. Other than this weird problem my system runs perfect. MSI Core Center now tells me that my CPU temp is 45% (CPU speed 1004) (Downloading stuff but not doing anything else), CPU speed is according to XP 1.79Ghz and I use the Cool 'n' Quiet function, On what temp should I start to become alarmed and is there some way to setup something in the bios to shut down or warn me when and if the CPU gets to hot ?..
Thanks for helping a new MSI user out

Weird booting issue.

Hello,
I built my first computer in December, and the PSU fan was making some noise so I RMA'd it. When I put in the new PSU, the fan noise disappeared but now something weird is happening.
My scenario is the following. When I'm in Windows and choose to shut down my PC, and then I push the power button on my case (say within a second after the computer powers off), my PC does not turn on again right away. Instead, I have to wait several seconds (maybe 5-7 seconds or so) and then the PC turns itself on (without me pushing the power button again). If I RESTART the PC from within Windows, everything is fine (it shuts down and turns itself on right away no problem). One more clarification: if I shut down my computer and let a safe amount of time pass after everything powers down (say 10 seconds), pushing the power button on the case turns the computer on right away.
Any idea what this could be? Is this normal behavior? It didn't used to happen with my old PSU, but I tried putting the old PSU back in and the same problem is happening (it still makes the old fan noise and it has the same weird booting problem now that I took it out and put it back in).
Specs:
Core i5 3570K
Hyper 212+
GTX 660 FTW Signature 2
Corsair TX650m PSU
G.Skill 8 GB Ripjaws
Intel 330 180 GB SSD
WD 1 TB Black hard drive
MSI z77a-G45 motherboard

Not if that is the only issue. However there have been allot of improvements in the latest bios's so the choice is yours. I have posted the latest official bios here:>>Beta BIOSes<< If you wish to flash, use that archive and forum flash tool.
It could be that the prior psu was broken (as it was)
When you hit the power button, a signal is sent to the psu then the psu sends a "ready" signal back. Then the board proceeds though post. Same thing happens in reverse when you shut down. As I said before I have tested this when a prior user asked this question and all of my computers have a similar delay.

Boot problems with K8N NEO Platinum(no video). SOLVED

I have this board for a few months now, but this week, when powering the system, it gave me no video.
It reads the HD and after a little while all the lights in the D-Bracket go green. But still no video.
There are other simptoms that can help the diagnosis: sometimes i do get video, the system powers up perfectly. This happens when I repeatedly press the reset button, or try powering on and off, on and off...
I don't think it is cold boot problem, since when I successfully turn on the system and then turn it off, the same boot problem occurs I I try turning it on again.
Another thing is that when I turn it off through Windows, it doesnt actually turn off: the screen ges black, but the HD leds still blink for a looong time. I have to turn it off manually, then. Sometimes it actually turns off, but turn itself on again after 1 second.
So if the D-Bracket sais its all good, then what is bad?
My System specs are
Athlon 64 Venice 3000
1 Gb Corsair DDR
Leadtek Geforce 6600GT

Quote from: cyberoll on 19-April-06, 19:18:18
Its solved now. There was a short circuit. The rouded isolators were placed in the upside of the board, and they should have been under the board. I changed it and all the problems are gone.
Such a little thing... :D
What is a "rouded isolator" and where is it located. I would like to see if this will fix my problem. The same thing is happening to me.
Thanks

1st series iMac G5: Booting problems, kernel panics, waking from sleep...

Specifications of the iMac described: 1.8 Ghz, 1GB, 80GB, 64 Mb Nvidia VRAM, Airport, 10.5.5
Back in August 2004 my dad bought us kids an iMac G5 for ‘family use’. It had a fresh install of 10.3.5 on it and compared to the (1999) iMac G3 it replaced it was amazingly fast.
The iMac never showed any signs of probable issues, until we decided to upgrade to Leopard in January 2008. Initially, this upgrade was only meant to be able to sync with the latest iPod nano (who demanded a newer version of iTunes).
After the installation the first thing I noticed was a high CPU usage, the machine seemed slower than ever and that with 1 Gb of RAM (the minimum sys. req. for Leopard are 512 Mb of RAM). Anyway, then the real thing started, it wouldn’t turn on anymore. We brought it to an Authorized Apple Reseller, the Tech department said the Logic board had failed. The costs of the fix weren’t the worth the computer anymore, so...end of story. The iMac was indeed one of the bad series, although it hadn’t any swollen capacitors.
My dad already made up his mind and bought himself a Macbook. He then told me that if I was able to get the broken iMac fixed, I could keep it. And so, I bought an ‘as-is’ logic board on Ebay. Last weekend I installed it, and it actually seemed to work! Yet, the problems are during the startup: the first thing I see is a screen full with horizontal lines flickering all the time, like an old TV with bad signal. Mostly it won’t boot and I get the message to restart the computer (kernel panic, I got dozens of logs already!). Sometimes it got stuck during booting (grey apple screen with gear in the middle) making the fans go crazy (after a while) and sounding what others describe as a ‘jetliner taking off’ sound. Sometimes the screen remains black. Generally it takes me 5 to 10 minutes to start up properly. Maybe it’s just me but it seems like when the computer has warmed up a little (by turning on and off on and on) starting up gets smoother. I mean the startup screen suffers from less horizontal flickering lines.
During the use of Leopard, I again get high CPU usage, especially when I use multiple programs at the same time, or when starting multiple programs. My iStat Pro said once that the fans were running at 4700 rpm and the heat of the CPU was about 70 Celsius. If I really want to **** my iMac off I should play a racing game. That just totally freaks him out! These problems could probably be solved by adding more RAM. Right?
The iMac also has a sleep problem. Sometimes after lets say an hour or so, you can’t get it out of sleep mode (by manipulating keyboard and/or mouse, the sleep light stops, but the screen stays off --> only solution is to restart). What happened to me once was that it slept so long that it just got into a deep sleep by turning itself off completely!
Here’s a list of what I tried so far:
- Disk Utility: Resetting the permissions, no problems were found.
- Resetting the SMU, both on the logic board itself as by pressing the power button 5 - 8 seconds, no improvements.
- Resetting the PRAM, no improvements.
- Did the Hardware test of the original install CD, nothing was found, all good.
- Did Archive and Instal, this actually messed my system entirely, cause it wouldn't boot at all and when starting up from the Leopard installation DVD it wouldn't recognize the Macintosh HD.
- Did Archive and Instal with the original disks, this disk did recognize Macintosh HD and so I installed the original system, 10.3. Booting problems and those flickering lines are still there though.
Next phase will be erase and install, but first I want to know what you guys think about all this.
Oh eh, One more thing; The guys at Applecare (phone support) told me that the replaced logic board was also out of warranty and so they couldn’t help me. But as the man on the phone was kind, he told me to go look for a special ‘driver’ on the net. He said that the driver should be able to resolve some of the issues described. He said that I had to give in the name of the LB on google and look for results. Is this bogus? Because I haven’t found anything useful on google so far. What’s the name (rather than a number) of the LB in the first place?
I hope you guys can give me some answers. I'm kinda desperate. But I still feel there's hope...

The symptoms of a flakey power supply are sleep problems and you have done all the right things as far as resetting the SMU and PRAM. Your CPU usage can be tracked by going to Utilities>Activity Monitor - look and see what is hogging the memory. The flickering lines could also be an optical system going south.
The other thing you can do is run DiskWarrior or TechToolPro to see if you have corrupted directories. Preferential Treatment will let you check for corrupted preferences.

I have an early 2008 Mac Pro, which has re-booting problems. Also what does the spinning beach-ball indicate?

Hi, I have an early 2008 Mac Pro which has re-booting problems.
Processor speed is: 2.8
Memory: 2GB 800 MHz DDR2 FB-DIMM
2 x 28GHz Quad Core Intel Xeon
I am running OSX Yosemite Version 10.10
My Mac Pro keeps re-booting. Last year I had to replace my graphics card. My original card was the ATI Radeon HD 2600 XT 255MB, and that is what I have now. At this precise moment my Mac Pro is running perfectly, except that it is slow and the spinning beach-ball keeps appearing. I have managed to do some work with the disk utilities, verifying, cleaning and partitioning. Some errors were found and when it was cleaned this seemed to help my Mac Pro to function properly. Although I am able to use my Mac Pro now, from day to day I still experience re-boot problems. Also quite unexpectedly my mac dictionary has an error, it closed itself down and will not open at all, I had the message to say that a report will be sent to Apple.
I have tried starting my computer with an external hard drive fitted via a USB cable, I use for back-ups. This worked and I was able to wipe my hard drive clear and replace all info from the back up I had done only a few days ago.
This worked for a few days and then the same problem started again.
I am beginning to wonder if I need to buy a new hard drive.
If there is anyone who has some answers to help me solve my problem, I would be most grateful.
Robert

When you have the beachball activity, note the exact time: hour, minute, second.
These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad and start typing the name.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
Each message in the log begins with the date and time when it was entered. Scroll back to the time you noted above.
Select the messages entered from then until the end of the episode, or until they start to repeat, whichever comes first.
Copy the messages to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
The log contains a vast amount of information, almost all of it useless for solving any particular problem. When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Some private information, such as your name, may appear in the log. Anonymize before posting.

Windows 8.1 pro boot problems

I upgraded my OS on a hp pavilion g6-1d73us from windows 7 home premium to windows 8.1 pro and ever since I have had boot problems. I took all the software off since I thought that might be the problem but the boot problems persist. The computer's self diagnosis helps but I still have problems. Is my laptop incompatible with windows 8.1? Windows 8.1 was a download and I still have recovery disks for windows 7. I originally thought the problem was incompatible software but now I am not sure.

Hi @hifive11 ,
Thank you for visiting the HP Support Forums and Welcome. I am glad you have recovery disks for windows 7, smart thinking. I have looked into your issue about your HP Pavilion g6-1d73us Notebook and having issues with the Windows upgrade to 8.1. Here is a link to the drivers page for your product. I do notice there are drivers for Windows 8.The Updates you need for the system are the Chipset. These are located on the driver page link above.
One of the things that can cause an issue is things connected USB. The computer can not load the drivers so it causes an issue. Once the machine is up to date then return the USB devices.
Then I recommended to restore the BIOS to factory defaults.Here is a link to restore the BIOS.
You can do a system restore. System restore will help if something automatically updated and did not go well on the Notebook.
Please note remove any and all USB devices. Disconnect all non-essential devices.
Hope this helps.
Thanks.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

[SOLVED] Weird Boot Problem

Similar Messages

Maybe you are looking for