Screen 'flicker'/artifacts after boot into arch

i experience some sort of flickering/artifacts (dunno how to call it, it's like pixels flying across the screen) after i boot into arch. even when i'm (still) in a tty with no x session running. (before booting into arch, while in the grub menu, it's ok)
it looks pretty much like this.
my gpu is an ati radeon hd4570, i have the free radeon driver (xf86-video-ati) installed.
not sure whether it can be a driver issue though, because it happens even when i'm not in a graphical session?
unfortunately i don't know what to do or what to look at to fix this. investigating this issue i'm led to believe it could have something to do with grub or kernel settings or sth, but i have 0 experience with configuring either.
i'm dualbooting with ubuntu 14.04 btw, which also runs the radeon driver, and i don't have the problem there.
i'd appreciate any sort of help!
(this is my first time posting here, i apologize if i ignored any forum etiquette)
Last edited by weisbrot (2015-02-18 20:49:05)

weisbrot wrote:my gpu is an ati radeon hd4570, i have the free radeon driver (xf86-video-intel) installed.
For Radeon you should use xf86-video-ati, not xf86-video-intel.

Similar Messages

[Solved] Can't boot into Arch after deleting some partitons

About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
I can chroot into Arch and did the following -
grub> find /boot/grub/stage1
(hd0,5)
grub> root (hd0,5)
Filesystem type is ext2fs, partition type 0x83
grub> setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
ed
Done.
grub>
The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
title Arch uuid
#root (hd0,5)
uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
intrd /boot/kernel26.img
title Arch hd
root (hd0,5)
kernel /boot/vmlinuz26 root=/dev/sda6
intrd /boot/kernel26.img
I have a bootinfo script which gives the following (from the chroot environment) -
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> No boot loader is installed in the MBR of /dev/sdb
sda1: _________________________________________________________________________
File system: swap
Boot sector type: -
Boot sector info:
sda2: _________________________________________________________________________
File system: Extended Partition
Boot sector type: -
Boot sector info:
sda5: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
sda6: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: /dev/sda5 already mounted or sda5 busy
mount: /dev/sda6 already mounted or sda6 busy
sda7: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
sda3: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 10.04.1 LTS
Boot files/dirs: /etc/fstab
sda4: _________________________________________________________________________
File system: ext3
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
sdb1: _________________________________________________________________________
File system: xfs
Boot sector type: -
Boot sector info:
Operating System:
Boot files/dirs:
=========================== Drive/Partition Info: =============================
Drive: sda ___________________ _____________________________________________________
Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
Partition Boot Start End Size Id System
/dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
/dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
/dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
/dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
/dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
/dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
/dev/sda4 * 63 417,689 417,627 83 Linux
Drive: sdb ___________________ _____________________________________________________
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
Partition Boot Start End Size Id System
/dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
blkid -c /dev/null: ____________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
/dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
/dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
/dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
/dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
/dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
/dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
/dev/sda: PTTYPE="dos"
/dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
/dev/sdb: PTTYPE="dos"
============================ "mount | grep ^/dev output: ===========================
Device Mount_Point Type Options
/dev/sda12 / ext3 (rw,commit=0)
=============================== sda3/etc/fstab: ===============================
# /etc/fstab: static file system information.
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# /dev/sda1 = swap
/dev/sda1 none swap sw 0 0
# /dev/sda3 = root
#UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
/dev/sda3 / ext3 relatime,errors=remount-ro 0 1
# /dev/sda4 = boot
# UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
/dev/sda4 /boot ext3 relatime 0 2
# /dev/sda5 = home
# UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
/dev/sda5 /home ext3 relatime 0 2
#/dev/sda6
#UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
/dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
# /dev/sda7
# UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
/dev/sda7 /var ext3 relatime 0 2
# /dev/sda8
/dev/sda8 /opt ext3 relatime 0 2
# /dev/sda10 - Arch
/dev/sda10 /mnt/arch ext3 relatime 0 2
# Not sure what this is doing here
# Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
# /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
# /dev/sde1
# uuid appears to be 644406B3570C1846 -> ../../sde1
#/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
#1TB-01
UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-02
UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 1TB-03
UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
d defaults, relatime
# 750GB-02 ext3 Partition
# UUID giving problems, trying with dev
# UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
/dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
============================= sda4/grub/menu.lst: =============================
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 3
## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu
# Pretty colours
#color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
# examples
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,3)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash
## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false
## Xen hypervisor options to use with the default Xen boot option
# xenhopt=
## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## should update-grub adjust the value of the default booted system
## can be true or false
# updatedefaultentry=false
## should update-grub add savedefault to the default options
## can be true or false
# savedefault=false
## ## End Default Options ##
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-26-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-24-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-23-generic
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
quiet
title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
root (hd0,3)
kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
initrd /initrd.img-2.6.32-22-generic
title Ubuntu 10.04.1 LTS, memtest86+
root (hd0,3)
kernel /memtest86+.bin
quiet
### END DEBIAN AUTOMAGIC KERNELS LIST
============================= sda4/grub/grub.cfg: =============================
# DO NOT EDIT THIS FILE
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
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 recordfail {
set recordfail=1
if [ -n ${have_grubenv} ]; then if [ -z ${boot_once} ]; then save_env recordfail; fi; fi
insmod ext2
set root='(hd0,3)'
search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
set locale_dir=($root)/grub/locale
set lang=en
insmod gettext
if [ ${recordfail} = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-26-generic ...'
linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-26-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-24-generic ...'
linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-24-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-23-generic ...'
linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-23-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
initrd /initrd.img-2.6.32-22-generic
menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
-class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
echo 'Loading Linux 2.6.32-22-generic ...'
linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
echo 'Loading initial ramdisk ...'
initrd /initrd.img-2.6.32-22-generic
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
linux16 /memtest86+.bin console=ttyS0,115200n8
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch Linux (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26.img
menuentry "Arch Linux Fallback (on /dev/sda10)" {
insmod ext2
set root='(hd0,10)'
search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
linux /boot/vmlinuz26 root=/dev/sda10 ro
initrd /boot/kernel26-fallback.img
#### 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.
# From Arch grub menu.lst
# (0) Arch Linux
#title Arch Linux [/boot/vmlinuz26]
#root (hd0,0)
#kernel /vmlinuz26 root=/dev/sda3 ro
#initrd /kernel26.img
#Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
(hdX,Y)/grub/linux.mod).
#This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
#An example, booting Arch Linux:
#set root=(hd0,5)
#linux /boot/vmlinuz26 root=/dev/sda5
#initrd /boot/kernel26.img
#boot
###menuentry "Arch1" {
###insmod ext2
###set root='(hd0,10)'
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
ID
###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch2" {
###insmod ext2
###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
###menuentry "Arch3" {
###insmod ext2
###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
PARTITION
#linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
UBUNTU THIS IS THE ROOT PARTITION
#initrd /initrd.img-2.6.32-26-generic
#search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
###initrd /boot/kernel26.img
# /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
### END /etc/grub.d/40_custom ###
=================== sda4: Location of files loaded by Grub: ===================
.0GB: grub/core.img
.0GB: grub/grub.cfg
.0GB: grub/menu.lst
.0GB: grub/stage2
.0GB: initrd.img-2.6.32-22-generic
.0GB: initrd.img-2.6.32-23-generic
.1GB: initrd.img-2.6.32-24-generic
.1GB: initrd.img-2.6.32-26-generic
.0GB: vmlinuz26
.0GB: vmlinuz-2.6.32-22-generic
.0GB: vmlinuz-2.6.32-23-generic
.1GB: vmlinuz-2.6.32-24-generic
.0GB: vmlinuz-2.6.32-26-generic
=============================== StdErr Messages: ===============================
No volume groups found
mdadm: No arrays found in config file or automatically
[/quote]
Output of fdisk -l from chroot is -
[quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0000b084
Device Boot Start End Blocks Id System
/dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
/dev/sda2 25414954 1465144064 719864555+ 5 Extended
/dev/sda3 6554520 25414829 9430155 83 Linux
/dev/sda4 * 63 417689 208813+ 83 Linux
/dev/sda5 25414956 1360287809 667436427 83 Linux
/dev/sda6 1360287873 1423198349 31455238+ 83 Linux
/dev/sda7 1423198413 1465144064 20972826 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00025bd3
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953523711 976760832 83 Linux
I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
List of all partitions:
No filesystem could mount root, tried:
Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
I am really lost as to what is going on, which I'm sure is evident.
Thanks a lot
belbo
Last edited by belbo (2011-08-12 13:31:23)

Hi. Unfortunately that didn't help.
So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
[2011-08-08 23:32] ==> Image generation successful
[2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic.
Pacman.log relating to the new kernel package below -
[2011-08-09 00:22] Running 'pacman -Suy'
[2011-08-09 00:22] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:23] Running 'pacman -Suy'
[2011-08-09 00:23] synchronizing package lists
[2011-08-09 00:23] starting full system upgrade
[2011-08-09 00:26] removed python-mygpoclient (1.5-1)
[2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
[2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
[2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
[2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
[2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
[2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
[2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-09 00:26] ==> Building image from preset: 'default'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [autodetect]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-09 00:26] 7079 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] ==> Building image from preset: 'fallback'
[2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-09 00:26] ==> Starting build: 3.0-ARCH
[2011-08-09 00:26] -> Parsing hook: [base]
[2011-08-09 00:26] -> Parsing hook: [udev]
[2011-08-09 00:26] -> Parsing hook: [pata]
[2011-08-09 00:26] -> Parsing hook: [scsi]
[2011-08-09 00:26] -> Parsing hook: [sata]
[2011-08-09 00:26] -> Parsing hook: [filesystems]
[2011-08-09 00:26] -> Parsing hook: [usbinput]
[2011-08-09 00:26] ==> Generating module dependencies
[2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-09 00:26] 23360 blocks
[2011-08-09 00:26] ==> Image generation successful
[2011-08-09 00:26] installed linux (3.0.1-1)
I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
If anybody has other ideas I'd really appreciate it.
If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
Any assistance greatly appreciated.
Thanks
belbo
Last edited by belbo (2011-08-08 23:17:49)

IMac G5 fan always at maximum speed after booting into si...

IMac G5 fan always at maximum speed after booting into single-user mode in 10.4.3
Model: 1.6GHz iMac G5 with 10.4.3
I updated my iMac to 10.4.3, then booted into single-user mode to do some cleaning at the command-line level. I know, as others have discovered, that in single-user mode, the thermal control is off, so the fan gradually increases up to maximum speed and stays there until you reboot or go into multi-user mode. Well, I have never experienced this one before, and I'm freaking out about it... I went into single-user mood one reboot after upgrading to 10.4.3, and after all the println white text lines ended, the [1] fan shot up to maximum speed in 0.35 seconds (it sounded like a high-pitched DJ record scratch during the time interval), [2] the fan stayed at maximum speed when I left single-user mode, and [3] I cannot get the fan to slow itself! I rebooted, shut down, and even tried booting off the Tiger CD, but the instant I hit the power button to turn on the iMac, the fans blast up to maximum speed. They shut down when I put the iMac to Sleep, but then they blast up again in full when it wakes up. I checked my settings in the Energy Saver preference pane, and I have the performance set to "Reduced," which is the lowest possible.
I searched to see if anyone else had this problem or if the KBase had any info, but I didn't see any. I'm thinking about erasing and installing my stuff on the iMac, even though I just did that today.
Again, this maximum speed fan problem is freaking me out. It just started when I booted into single-user mode in OS X 10.4.3. I have booted into single-user mode before (10.4.2) and have not experienced this fan issue. I repeat, the fans blast up to maximum speed after pressing the power switch to turn on the computer, so they do not even wait for the Apple logo to show up on the screen before blasting away. How can I get these fans to not do this anymore?!

for the last few months my 20" 1.8GHz Imac has been very noisy - fans seem to run constantly and noisily. It might have been when updating to Tiger but I was never sure. Today, on the advice of a chat tech, I opened the case and reset the SMU to hopefully cure another problem. I noticed that all the air vents, intake and expel ones, were all quite heavily clogged up - not blocked but clogged with dust and fluff. I cleared it away mainly by blowing but also with a hand held hoover held close by. The exposed fan still as a lot of muck on it but greatly reduced and all the vents are completely clear. Having put everything back together again the iMac has been runnning quietly all day. May have been the SMU reset but equally might just be that the computer couldn'tdraw in cool air, circulate it or expel it properly and the fans had to work overtime to cope. Worth checking if you have noisy fans running at speed constantly.

[SOLVED]Ubuntu 11.10 broke grub2, can't boot into arch

Hi, I'm having a little issue with grub2 at the moment, I have Arch installed on seperate /home / and /boot partitions, I installed Ubuntu using the "alongside" option in the installer which has added an option to boot into Arch on the grub bootup screen. However when I boot up into arch I get the follow message:
Waiting 10 seconds for device /dev/hda3
[ numbers] usb 1=-4.2: device descriptor read/all, error -3
ERROR: Unable to find root device '/dev/hda3' .
You are being dropped to a recovery shell
Then I am promptly dropped into a recovery shell.
My root device should be at /dev/sda5, not quite sure what's happened there.
Any ideas on how to get this fixed? I think ubuntu has /boot on it's own parition, along with the rest of /.
Last edited by will.price94 (2012-02-26 12:11:04)

DSpider wrote:
hda is an IDE drive.
sda is a SCSI drive (SATA).
Do you have both on your system? Or is Ubuntu getting it wrong?
# sudo fdisk -l
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x568055d5
Device Boot Start End Blocks Id System
/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 146802687 73297920 7 HPFS/NTFS/exFAT
/dev/sda3 146802688 148828159 1012736 83 Linux
/dev/sda4 148830206 1465147391 658158593 f W95 Ext'd (LBA)
/dev/sda5 148830208 344139775 97654784 83 Linux
/dev/sda6 344141824 781250559 218554368 83 Linux
/dev/sda7 781252608 1257244671 237996032 83 Linux
/dev/sda8 1257246720 1456762879 99758080 83 Linux
/dev/sda9 1456764928 1465147391 4191232 82 Linux swap / Solaris
Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930277168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004c41c
Device Boot Start End Blocks Id System
/dev/sdb1 2048 2930276351 1465137152 83 Linux
Disk /dev/sdc: 1500.3 GB, 1500299395072 bytes
255 heads, 63 sectors/track, 182401 cylinders, total 2930272256 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0005d269
Device Boot Start End Blocks Id System
/dev/sdc1 2048 2930272255 1465135104 83 Linux
Ubuntu is getting it wrong, I have 2 SATA drives and an external USB drive.

Blue screen - after booting into Darwin/BSD

Hi,
after I had the problem of my iMac G5 only booting into Darwin/BSD (which I posted here: http://discussions.apple.com/thread.jspa?threadID=1093517&tstart=0), I followed the instructions for recreating the user accounts, as described here: http://discussions.apple.com/thread.jspa?threadID=320663&start=0&tstart=0
Now I'm able to get to the blue screen, and the system doesn't exit into Darwin/BSD any longer. However, the Setup Assistant doesn't start either.
I only see an empty blue screen (I guess it's the GUI base screen) and the menu bar. The menu bar only has to items: one menu 'loginwindow', which doesn't have any entries. And the Apple-logo menu, which has the following menu entries:
- About This Mac
- Software Update...
- Mac OS X Software...
- System Preferences...
- Dock >
- Location >
- Force Quit...
- Sleep
- Restart...
- Shot Down...
- Log Out System Administrator...
The 'Restart...' entry doesn't work. I can, however, launch the System Preferences window.
Tail command of /var/log/System.log shows:
configd[41]: WirelessConfigure: 88001003
kernel[0]: Registering For 802.11 Events
kerner[0]: [HCIController][setupHardware] AFH Is Supported
kernel[0]: ATY,Aphrodite2_A: vram [98000000:08000000]
mDNSResponder: Couldn't read user-specific Computer Name; using default bMacintosh-0014513219B8b instead
kernel[0]: ATY,Aphrodite2_B: vram [98000000:08000000}
mDNSResponder: Couldn't read user-specified local hostname; using default bMacintosh-0014513219B8.localb instead
/System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
loginwindow[141]: [Login.m:1867] Failed to launch /Applications/Server/Server Assistant.app/Contents/MacOS/Server Assistant (error -1)
mDNSResponder: Adding brows domain local.
Any recommendations on what to do next?
Thanks!
Torsten

Apologies, was a little vague. and as far as my profile goes i have loads of mac's here in the studio.
using MBP latest model, Snow Leopard with latest updates.
1. boot up in windows XP SP3 (bootcamp NTFS formatted 32GB partition) - all ok
2. shut down windows and re boot in OSX
3. boots up but fails to complete and hangs on blue screen (just prior to desk top picture loading)
4. press and hold power button to shut down
5. reboot in OSX - boots up fine this time

I can boot into Arch, but not DM or DE [solved]

I just recently installed Arch in VirtualBox. Arch is running on 1GB of RAM (changed from 512MB) and 8GB of storage with dynamic size enabled. I set the specs low as I want this to be portable and load on almost any machine. When it boots up I can access command line, but not DM or DE. If I set it to automatically boot into a DM or DE, it hangs (black screen). I have tried different DMs (GDM, KDM, SDDM) and DEs (Gnome, KDE, Plasma), but I get the same problem. During the boot process I get intel_rapl: no valid rapl domains in package 0 and SMBus base address uninitialized. While researching though, these problems don't appear to be linked to mine. Any advice would be helpful, thanks.
Last edited by flavinator (2015-06-12 04:46:33)

flavinator wrote:Update: So, I'm a little lost. I got all the packages installed. I edited the xinit file the way it says to. I chmod it.
Why did you chmod it? This is not in the instructions.
flavinator wrote:When I startx though, X has no file or directory, and don't see where it says how to create one.
What does this mean? Is this some translation or interpretation of an error message? Post the *actual* output.
flavinator wrote:I thought it would do that when XDM installed.
XDM is also not part of the instructions for testing TWM. If you start doing random other steps, we will not be able to help you as we will not understand what state your machine is in.
flavinator wrote:Update 2: I got startx to run, but then it fails with "Using system config directory "/usr/share/X11/xorg.conf.d" 0x00c00000, type = 1) Invalid argument (22) (II) Server terminated successfully"
Please post the *full* output. The server terminated successfully suggests a problem with your xinitrc, so as ewaller requested, we'll need to see that - after you provided the actual output and error messages you are getting.

Mac OS X drive unbootable after booting from Arch cd

I don't know if you guys can help me with this as its not actually involving Arch, though it was caused by the installer disk. I booted my intel iMac from the arch disk, thinking I could boot into the OS to check it out and see if this is the distro I want. However it seems like you have to install it first, so I shut down the computer(without installing anything), ejected the disk and turned it back on. Then I just get a black screen with a "_" , so I thought it was still trying to boot from the CD drive (though I thought usually if theres no CD then it tries the hard drive). So I put in my Leopard CD and set the boot device back to the hard drive. Now when I start up I get a folder with a ? on it and cannot see any boot devices. I'm sure theres something really stupid that I did wrong, but please any help would be appreciated. I've been doing lots of searches, so if you can't help me with this and there's another forum that might help, please point me in the right direction.

CheesyBeef wrote:
Ok, the "arch menu" you saw was the Grub bootloader. That should do absolutely no harm with picking the first option. After that, it does boot into a command prompt, asking for you to login. After you login, you have to run "/arch/setup" to begin the installer dialog, and from there you can begin installing your new system and are prompted before it does anything potentially harmful.
So my best guesses, based on the information given, are that the boot order is messed up from choosing the CD drive to boot (I don't know if you do this through the bios or by pressing a key during boot and selecting a boot device) or the hard reboot did something to your drive. But still, I am pretty darn sure the Arch setup does not mount any hard drives or partitons unless you really begin the installer, and it doesn't sound like you did.
Ok, so I booted into the command prompt, and yes, I did not begin the installation. However, at this point I simply powered off the computer, then I held down the option key durring startup to bring up a menu which allows me to choose where to boot from. All I saw here was the arch cd, which I then ejected, leaving nothing left. So I inserted my Mac OS 10.5 install disk and ran disk utility to see if there was anything wrong with my drive. Everything seemed fine. So I went into the startup disk selection, and saw the drive, with OS 10.5 on it and selected it as the boot drive, and restarted. But still when I try to boot it goes to a blank screen with a folder that has a ? on it. I know that something is amis here, and I'm really trying to figure it out. It must be some way connected with what I did, and I'm not saying there's anything wrong with arch, from what I've read its a really good distro. I'm just stuck and frustrated is all.

Black screen when trying to boot into Windows 7

Hello everyone.
Today we've encountered an issue with one of our MacBook Pros with Windows 7 installed. The computer was booted into Windows 7 (it's strictly used as a Windows machine by this particular user) and after a time of inactivity it went to sleep. It wouldn't wake up from it's sleep so we tried a hard boot. At that point we would get the grey screen, the Apple tone wouldn't sound off and it would just go to a black screen (by default we have it booting to windows). So then we reset the PRAM. Now, we get the apple tone and we can boot into the Mac side. But when we try and boot into Windows, we get a blank screen.
What's even more interesting, if I try and boot into a Windows install disk to do a boot repair, it gives me a black screen. If I even try to boot from a live Linux cd, I get a blank screen! When important thing I then noticed was that the cd spinned for a couple minutes, then stopped. So I began to wonder if it was still loading the OS like expected, but just wasn't displaying it.
So I booted into Windows, got the blank black screen. Then I went into another computer, fired up remote desktop and voila! I'm in the machine!
So the problem is this: When booting into ANYTHING other than OS X, the display turns off.
What can we do?

Hello there,
I have a similar problem! Windows 7 shutdown unexpectedly and since that I can not reboot in windows anymore only with safe mode where everything is a mess.
Also when it's trying to reboot in windows a blue window appears,says something about drivers and it is counting something (79.78...till100)but I m not able to read it cause it disappears immidiately and then black screen and then it turns to reboot in mac which works fine.
I m sorry if I confused you with my english...
If anyone knows please help!
Thanks

Windows 8.1 Boot Camp Screen is blank after boot

I installed Windows 8.1 Pro on my Macbook Air mid-2012 running 10.9.5 Mavericks and Bootcamp Assistant to create the install usb and download the windows drivers. After booting however, the screen always goes blank after the windows logo. I've tried an external monitor with no luck. I've verified I have the latest SMC and EFI firmware installed. I've tried using external usb keyboard/mouse. I've scoured the web for other things to try, but most people with this problem say you need to update your EFI, but mine is already updated.
I was able to boot into the 8.1 install via VMware fusion. That worked since it was using the VmWare video driver.
I've been unable to get 8.1 to boot into safe mode. Does anyone have an idea of what could be going on?
Jonathan

Are using a USB3 drive? If yes, please find a USB2 drive be able to load the KVM drivers. The Windows installer does not have a USB3 driver.
If you have installed Windows using EFI Boot, you will run into Graphics/Audio issues.

No reboot after booting into safe mode

For a few years I've just ignored the problem but thought I should take time to mention it now.
When I boot into Safe Mode (holding down the shift key during boot up) I can always click on restart when the password screen comes up and the computers will restart.
But if I log in after safe boot and let the system boot up past the login screen THEN try a restart I get hours of beach ball. I've left various computers running over night and it is always the same in the morning, no restart, no beach but lots of beach ball.
So I do a force shutdown (hold the on/off button for 10 seconds) or a forced restart.
This has been the case from Leopard OSX10.5 and up including Snow Leopard. And on five different Intel Core 2 Duo Macs including 2GHz & 2.4 GHz iMacs and Macbooks.
The common theme is that I have migrated my setup through all these Macs so maybe there is some legacy thing in my software.
Suggestions?

Well… some improvement.
Here’s what I did: (note that I did a restart and sometimes safe boot after each and every step.
1 – use FontNuke (free shareware) to blast away font cache files. It found 8 some dating from 2002.
2 – use Apple’s Font Book to reconcile duplicate fonts.
Those two steps fixed my slow down problems with playing movie files in Quicktime and VLC.
But not Skype video. The biggest CPU load with Skype is with the transmitted picture oddly enough.
Then for good measure I zapped the PRAM and PMU. No noticeable improvement from doing those. Obliviously repair permissions and verify disk was done long long ago and redone.
I still have the problem of not being able to reboot from safe mode.
The Startup folders are clean except for Qmaster which I do not believe is the cause of not being able to reboot out of safe mode.
Does anyone know of other files/locations that put 3rd party startup items? I remember finding things from Western Digital and Symantic a few years ago in unexpected places. Symantic was especially hard to track down and eliminate.

[SOLVED] Grub won't boot into Arch...

So, this all started when I got this wacky idea of trying Debian on a separate drive.
Installs great, boots up and get a blank screen with blinky cursor..not in the mood to mess with it since I can't find
a reasonable answer for what is wrong with it sooo I boot back into Arch but now I get Error device not found with a "Grub Rescue>" prompt.
Not sure what to do now. I installed grub to the drive I was installing Debian on but it seemed to screw with my precious Arch too
I looked around the forums for help but couldn't find anything.
Also, it goes from post directly to the Grub Rescue prompt
Last edited by PumpkinJack (2011-08-26 07:59:37)

edit:
ok here it is:
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst
# DEVICE NAME CONVERSIONS
# Linux Grub
# /dev/fd0 (fd0)
# /dev/sda (hd0)
# /dev/sdb2 (hd1,1)
# /dev/sda3 (hd0,2)
# FRAMEBUFFER RESOLUTION SETTINGS
# +-------------------------------------------------+
# | 640x480 800x600 1024x768 1280x1024
# ----+--------------------------------------------
# 256 | 0x301=769 0x303=771 0x305=773 0x307=775
# 32K | 0x310=784 0x313=787 0x316=790 0x319=793
# 64K | 0x311=785 0x314=788 0x317=791 0x31A=794
# 16M | 0x312=786 0x315=789 0x318=792 0x31B=795
# +-------------------------------------------------+
# for more details and different resolutions see
# https://wiki.archlinux.org/index.php/GRUB#Framebuffer_resolution
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/6ab6f3ca-2c64-4264-97aa-10819e4561ed ro
initrd /initramfs-linux.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/6ab6f3ca-2c64-4264-97aa-10819e4561ed ro
initrd /initramfs-linux-fallback.img
# (2) Windows
#title Windows
#rootnoverify (hd0,0)
#makeactive
#chainloader +1
Last edited by PumpkinJack (2011-08-26 02:42:08)

Cannot boot into Arch using Gummiboot and Intel fake RAID

This is my first time installing Arch Linux in a few years. The installation seemed to go fine, but I can't boot into it. At this point, when I try to boot into it this is my console output: http://pastie.org/9389435
First of all, what confuses me about this output are the RAID lines. My system currently has two RAID arrays: My RAID0 array where Windows 7 is installed and my RAID1 array where I'm attempting to install Arch Linux. My fstab nor Gummiboot entry files refer to the RAID0 array at all. Why does it activate the partitions on the RAID0 array but not the RAID1 array?
Second of all, lines 10, 11, 14, and 16 refer to /dev/sdd3. When I mount the partitions on my RAID array using the Arch live CD, I have to refer to them as either /dev/md/RAID1_0p1-4 or /dev/md124p1-4. The /dev/sda-sdd seem to refer to the individual drives. Why is it different when I try to boot into the system?
Here is my current fstab: http://sprunge.us/bQCT
The reason fstab is using labels is because the genfstab command generated an fstab that mounted the partitions on the RAID array with their /dev/md124p1-4 names. I noticed these names sometimes changed if I booted back into the live cd, so at one point I changed those names to the /dev/md/RAID1_0p1-4 names. Then in another attempt to fix the problem I'm currently having, I gave each of the partitions labels and I'm now referring to them by their labels in fstab. I also removed the commented UUID's since a few of them had changed since this fstab was generated. Everything to the right of the labels was kept from the original genfstab command.
Here is my gummiboot arch.conf entry file: http://sprunge.us/HPVb
I'm also referring to my root partition by label in this file, rather than the UUID which seems to be the norm. The reason for this is because I was previously getting an error saying that it couldn't even find the root partition based on that UUID. As you can see, I left the UUID line commented in case I have to use it again later.
Here is my mkinitcpio.conf file, which I'm thinking the problem has something to do with this since it's the part I understand the least: http://sprunge.us/IFDL
The modifications I made to this file were based on what I read in the fake raid article on the Arch wiki. All I did was make sure dm_mod and dm_mirror were added to the MODULES line and dmraid was added to the HOOKS line. At first I also had chipset_module_driver in MODULES, but it just generated warnings when I ran `mkinicpio -p linux` so I took it out. I don't know what that module would be for, since it only says "if necessary" on the wiki.
As for the emergency shell it puts me in when it fails to boot, there's not really much I can do from there. The filesystem it puts me in looks entirely different from the root filesystem I can mount from the live cd.
At this point, I'm stumped and I'm not sure where to go from here.

x:5:respawn:/opt/kde/bin/kdm -nodaemon
This is the line that's causing it. It's probably not because of this line, but because kdm isn't starting properly (possibly erroring) and being re-run because of the respawn option.
Try booting into single user mode, changing the default run level to 3, and debugging it from there (figure out why kdm doesn't want to start right).

Have to restore OS X.9.1 after booting into Windows 7 on Bootcamp

I am having an odd problem--whenever I boot into Windows 7 on bootcamp, when I then boot into Mac OS X.9.1, I have to restore the disk from Time Machine. This has never happened before, but now has happened twice in a row. It takes hours for the Restore function to restore everything. Anyone have any idea as to why this is happening. My MacPro dates to 2010. Thanks.

Windows is a guest on your Mac. If you use Windows tools to change the partition Map, or the size of any partition, all Mac OS X partition information is trashed, and you will need to restore it before proceeding.
Otherwise, you should be able to hold down Alt/Option key at Startup, and select your Mac OS X Volume to boot from (after several minutes of discovering what Volumes are present).

Screen flicker/ strobbing after transfer frm FCE to iDVD

Help!
I'm in need of some advice - after editing a large video project on Final Cut Express, then burning a disc through iDVD there is VERY noticeable screen flicker/ strobing in all shots with movement i.e PANNING & TILTING.
When viewing this material in FCE there is no noticeable issues, but after playing the DVD (and watching on a CRT TV) the problem occurs.
I have tried to fix this by applying the Video/De-Interlace filter, but with no effect....any advice is most welcome
n.d I have created various other DVD's but the issues above were largely unnoticeable
The footage was shot on a Sony V1E 25fps 1080i
Laptop spec is: Mac OS X 10.5.8

The export process to iDVD sounds OK.
Do you know the option for quality iDVD was set to handle?
There are three in later versions.
These options affect quality.
I'd be thinking the size of the Project may be affecting the encoding within iDVD depending on the option used at the time.
Have you tried the Professional quality option in iDVD?
Ask in the iDVD forum for detaIls.
Al

Login screen comes up repeatedly, booting into safe mode by default

Good Morning,
I have an iMac (Lion 10.8) that is having a lot of trouble. I manage an Elementary School's IT fleet. At the end of last year, the computer was booting into Safe Mode by default. Once the system came up, the teacher could use it - but it took so long to boot that she chose not to. The teacher left the school, and I was planning to just format it and reimage. Here is what I have happening.
Boots into safe mode on it's own
Once it's done booting, the login screen shows up - but entering any credentials just gets a grey screen, and the login screen comes right back. Even root. Which means I can't get logged into the computer at all.
Recovery mode will not allow me to erase the drive, says failed and not able to access the drive.
Target mode will also not allow me to erase the drive, nor will it allow me to push over an image. Scanning the drive failed, busy.
Disk repair says unable to repair disk - please format.
These are the things I have tried.
Reset PRAM (three times over the course of troubleshooting)
Replaced the RAM completely
Unplugged 15 seconds trick
Accessing via Target mode - Drive is greyed out, but shows up
Ran FSCK manually, and it completed
Tried to do a netinstall, but the disk does not show up in netboot as an option.
I thought maybe the drive was bad, but considering that it will boot into safe mode eventually (although you can't login), and FSCK completed successfully - I'm just not sure! I just thought I'd pick your brains. I'm usually a Windows \ Linux Administrator, so this Apple business is new to me I'm learning! Although I find them frustrating. Any help would be greatly appreciated!
Thank you

I thought maybe the drive was bad, but considering that it will boot into safe mode eventually (although you can't login),
Some part of the disk may be bad while others are good. i/o could be trying multiple times and eventually succeeding.
Ran FSCK manually, and it completed
You run FSCK in single user mode? This is very surprising. FSCK verifies the filesystem is in order. Actual data blocks could be bad. Would be a surprise if no file system blocks were not also bad.
Except for this fact, it seems like a hd problem. Intermediate problem. Heat problem, etc.
Time to try a different hd. See if that works. Could be some other hardware problem. Try external drive/flash drive, etc.
Mac OS X is BSD Unix.

Screen 'flicker'/artifacts after boot into arch

Similar Messages

Maybe you are looking for