UEFI boot problems with Linux 3.7 kernels
According to this thread in the Arch Linux forums, some people are having problems booting some versions of the Linux 3.7 kernel. Here are the numbers:
3.7.3 works for some, but not others
3.7.4 works for some, but not others
3.7.5 works
3.7.6 does not
3.7.7 works
3.7.8 does not
The problem occurs with both the Gummiboot and rEFInd boot managers, and has so far only been reported on Lenovo hardware. I have a ThinkPad W530, and can confirm that on Gummiboot, 3.7.6 does not work, whereas 3.7.5 and 3.7.7 does work. It looks like a Lenovo-related issue to me. It has only been reported on Arch Linux as far as I know. Has anyone else encountered this problem?
Thanks for your reply. Yes, the cursor did blink in the top left corner.
I gather from your comments that, if I install a new HD, I will be able to re-install the Windows 7 32-bit O/S from the Product Recovery DVD GMR410014EN0, which was supplied by Toshiba with the laptop and it would also follow, if that is true, that I would be able to Format (Boot n' Nuke) the existing HD and re-install the O/S onto it before I get my friend to lay out cash for a new HD.
I would appreciate your confirmation that the above conclusions are correct as I was under the, hopefully incorrect, impression that the Recovery Disk could only be used to repair an existing system. I have the Microsoft licence number as it is printed on the bottom of my friends machine.
Thanks for your time and I look forward to hearing from you.
Similar Messages
-
HEAVY Problems with Linux x86_64 on K8T Neo
Hello, Community!
I experience *HEAVY* Problems with Linux on my MSI K8T Neo (FSR). Since the customer support of the german dependancy seems to ignore my call for help I'm in good hope that maybe you can help me out or give me some useful advise.
First some Hardware Specs of my system:
MSI K8T Neo FSR, Rev 1.1, BIOS 1.5
AMD Athlon 64 3000+
3x 512MB Kingston DDR400
Enermax EG365P-VE (350W) PSU (3.3V/5V 185W Combinded)
MSI GeForce FX5200 TDR 128
Adaptec ATA RAID AAR1200A (HPT370A) in PCI Slot 3
Hauppauge WinTV PCI in PCI Slot 5
Maxtor 4K040H2 (40GB) as Primary Master
JLMS XJ-HD166S DVD-ROM as Primary Slave
LiteOn LDW-411S DVD+/-RW as Secondary Master
LiteOn LTR-52327S CD-RW as Secondary Slave
2x Maxtor 6Y060L0 (60GB) on HPT370A as Primary Master/Slave
Seagate ST380020A (80GB) on HPT370A as Secondary Master
Maxtor 32049U3 on HPT370A as Secondary Slave
KeyTronic KT2001 USB Keyboard
Microsoft Optical Wheel Mouse Blue USB
I've downloaded Fedora Core 1 x86_64 as well as the lately released Fedora Core 2 test 3 x86_64 distribution. Both CD sets have been burnt ok.
If I try to install Core 1 x86_64 (Kernel 2.4.22-1.2179) the kernel crashes with a "attempted to kill idle task" panic. As far as I've learned the workaround is to give idle=poll as kernel parameter. This resolves the kernel panic, but the installer randomly crashes with segfaults at a random stage; sometimes while loading anaconda, sometimes during package install.
If I try to install Core2 test 3 x86_64 (Kernel 2.6.5) I get a, completely new, error message while the kernel does the PCI Scan:
******* Your BIOS seems to not contain a fix for K8 errata #93
******* Working around it, but it may cause SEGVs or burn power
******* Please consider a BIOS update
******* Disabling USB legacy in the BIOS may also help
I removed my USB keyboard, connected a PS/2 keyboard, disabled to USB Legacy option (I need it enabled in order to use Ghost) in the BIOS and booted again.
The error message is gone now, but as in Core 1 the installer still crashes randomly with segfaults. I'm still unable to go all the way through the installation routine.
I even tried to install Fedora Core 1 "i386": again there are segfaults during install.
Contrary to the problems I experience while trying to install Linux my Windows XP (32-Bit), as well as a test installation of Windows XP 64-Bit, run like a charm without any problems. Strange but true.
Since I already read trough several posts in this forum I already tried running my system with memory sticks from another manufacturers as well as with a more powerful PSU. I even removed my tv-card and raid-controller.
Nogo - Linux still crashes randomly and Windows still works without any flaws.
Has anyone a clue what I can/must do to successfully install Linux?
Might it be that the BIOS has some flaws that might cause the problems?
Has anyone managed to install Linux (what distribution) on this Mainboard?
I would greatly appreciate any help. If you need to know something I haven't provided here please feel free to ask. I'll answer ASAP.
Thank you in advance.
P.S.: The system is *NOT* overclocked in any way.And now even the last problem is solved ...
Since I was successful in installing a basic Gentoo system but still failed to install Fedora I reflashed BIOS 1.5. This time I cleared the CMOS by unplugging the PSU, setting the jumper and removing the backup battery.
Yesterday I only flashed it with the /a switch, which should have cleared the CMOS as well - so far for the theory. However, it once went fine as I upgraded from BIOS 1.1 to 1.4.
After setting up the BIOS options again I gave it another try and booted from Fedora (Core 2 test 3) install CD: No more complains about the CPU errata, although USB legacy is enabled, and I even went through the installation without any problems.
It seems as I will stick with Gentoo as my primary distribution since the kernel makes a more "mature" impression than the one from Fedora (i.e. the K8 PowerNOW! Driver seems to be missing in Fedora's Kernel 2.6.5).
By using an spare Athlon XP Mainboard I worked out that only one of my three Kingston memory sticks had errors - I'm going to replace the faulty stick tomorrow.
Now for the conclusio:
Thanks, especially you JLP, for helping me with my issue. Without the advise to use Gentoo, and the included MemTest86, I wouldn't have been able to track down the error to a faulty memory stick that fast since Windows always ran fine. -
[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) -
Lenovo laptop u430 Touch - strange UEFI boot problem
Hello!! I'm Javier from Argentina. I'm having a strange boot problem with my Lenovo u430 Touch and Windows 8.1 x64 configured in UEFI.
When I power on o restart the laptop It gets stuck at lenovo logo screen and i have to press a key from the keyboard to continue booting on Windows 8.1 x64. This is really annoying.
No hdd activity.Trying to solve the problem I reset bios to default settings, I updated to last bios available and restored Windows 8.1 with OKR but i have no luck.
To solve this problem I configured the laptop to use legacy support, but I would that someone can help me to use again my laptop with UEFI bios settings.
Thanks, I will appreciate your help.JavierHi Sendhil,
Welcome to Lenovo Community Forums!
I'm sorry to hear about your situation. I have private messaged you the details. Please let me know after checking your PM inbox.
Do post us back for further queries.
Best Regards
Shiva Kumar
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
Poll: Do you have cold boot problem with SB X-FI Fatal1t
Hi guys:
I have post a thread regarding the cold boot problem with SB X-FI Fatalty and OCZ GameXStream 600W SLI power supply combination. Apparently, no one has answer to that . In addition, I have recently RMA'd my psu and received a brand-new unit. The same problem still exists. If the problem is really with the power supply, doesn't matter what kind of the setup I have, I should still have the cold-boot problem. However, it doesn't seem like that. Doesn't matter what kind of cards I put on the motherboard, as long as the SB X-FI Fatalty card is there, there is cold boot problem (even with the setup of cpu, mother, ram, and the sound card only, WITHOUT video card and harddri've). And for other different setup without the SB X-FI Fatalty card, there is no cold boot. The cpu and memory are running at stock speed.
My post regarding the cold boot issue:
http://forums.creative.com/creativelabs/board/message?board.id=soundblaster&message.id=79753
There is one user on the forum saying he has the same problem. Therefore, I think it might be the imcompatibility between the X-FI Fatalty and OCZ GameXStream PSU.
I would like to know how many people that has the same problem that I am having. So I can possibly narrow down the problem and contact OCZ tech support or creative tech support with more information. It would also be benefitical to those who have the same problem as I do.
Please post your system setup as well in the thread.
Greatly appreciate your opinions. Message Edited by White_Hair on 2-02-200604:58 AM
Message Edited by White_Hair on 2-02-200603:22 PMI would venture to say that it isn't your powersupply, but more likely the X-Fi. I had troubles with my system, until I pulled out my X-Fi and replaced it with a non Creative Labs sound card. One of my troubles, which I incorrectly blamed on my powersupply was the ASUS A8R-MVP motherboard I had and the X-Fi XtremeMusic card, was after gaming for 4 hours, was the?sudden reboot of my system. Powersupply before, was an Antec TrueControl 2 550watt PSU. As it stands right now, I no longer have the parts mentioned and have a decent 700watt powersupply in my system, along with an ABIT AT8 32X motherboard. As you have probably seen there are a lot of problems with the X-Fi soundcards, and I in my right mind can't blame the motherboard, powersupply, motherboard chipset, ram, or any other component in ones system, if one is having trouble other than the X-Fi itself. I'll be honest, there is something quite frankly wrong with the X-Fi, and exactly what that is, I'll probably never know like most people.
-
K8N NEO4 Platinum cold boot problem with 165 opteron?
I have this board and have a cold boot problem with my opteron. Is there anything I can do to fix this? Its starting to get very anooying.
K8N NEO4 Platinum
165 opty dual core
2X1GB Ballistix PC4000
160GB sata2
7800GTX
X-Fi platinum
600 watt seasonic PSUWell I am running them at the rated speed of 250 and the rated timings of 3-4-4-10 on the rated 2.8 volts. Ballistix have been known to die quickly when you throw to many volts at them for some reason. I dont get the cold boot problem with the OCZ. Once I finally get it to boot with the Ballistix it works just fine but the next morning I play hell to get it to boot again. I dont even get the main screen to let me get into bios. It just stays black. I have done all kinds of stress testing and ran memtest with no problems. I am really at a loss here.
-
[SOLVED] Using Apple's UEFI boot menu with Arch
Hello,
I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer). From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go. Unfortunately I've tried this a bunch of different ways, to no avail. I think some of my failure is simply because of a misunderstanding of UEFI, here are some questions I (partially) don't understand and my current understanding of them:
1. Do I even need a bootloader on a pure GPT/UEFI system? It seems like the answer is no, and I can just use the UEFI firmware and the linux kernel to load Arch (per: https://wiki.archlinux.org/index.php/UE … ux_Kernel). Note: I'd like to have as little software between the firmware and the os, for speed and simplicity. However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update? I think the answer is yes, which would be motivation (esp when I need to update the kernel) to just use a multibootloader and have it handle arch and the firmware pass control to either that or MacOS
3. Will `efibootmgr` brick my mac? https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ). Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
I've been searching a bunch of different things, output of the `bless` commands I've been running, and have found the following:
* https://bbs.archlinux.org/viewtopic.php?id=148647
* Using OSX to install rEFInd manually (moving the files around and using OSXs `bless` command) http://www.rodsbooks.com/refind/installing.html#osx , I used the rEFInd files from Archs repos: https://www.archlinux.org/packages/extr … efind-efi/ )
* The Wiki docs on rEFInd https://wiki.archlinux.org/index.php/UE … ing_rEFInd
To summarize, I'm trying to set up a dual boot between MacOS (installed) and Arch (also installed, there's just no way to boot it on my system yet) using Apple's built in menu that deals with the EFI partition on /dev/sda1 . Thanks in advance for any help!
end
Last edited by enduser (2013-03-18 12:00:17)enduser wrote:I've successfully installed arch on my mid-2012 (5,1) 11" Macbook Air, and now I'm trying to get an entry in apple's boot menu (the one that shows when you hold 'option' when starting the computer). From the author of rEFInd's install instructions (http://www.rodsbooks.com/refind/installing.html#osx) it sounds like I can just add some files to `/dev/sda1` (a vfat directory that contains the stuff needed to boot macos), and then run apple's `bless` command and we're good to go.
Not quite. That makes a boot loader bootable, but it doesn't add an entry to Apple's boot manager menu. There's a blog post somewhere by Matthew Garrett that describes the steps necessary to add something to Apple's boot manager, but I couldn't find it in a quick Web search. Maybe you'll have better luck, or be able to track down the same information somewhere else. As I recall, it involves using a separate HFS+ volume, creating two or three dummy files, and using "bless" in OS X.
1. Do I even need a bootloader on a pure GPT/UEFI system?
Yes, you do need a boot loader. It's important to distinguish between a boot loader and a boot manager, though. The former is a program that loads a kernel, and perhaps associated data, into memory and transfers control to the kernel. A boot manager presents a user interface that enables you to select which OS (or which boot loader) to launch. A boot manager is not strictly necessary, and Apple's EFI implementation includes its own simple boot manager, which is what you've been unsuccessful in configuring.
Note: I'd like to have as little software between the firmware and the os, for speed and simplicity. However, I'd still like to dual boot, but it sounds like the firmware can handle showing me a menu as long as there are entries pointing to parts of each OS.
Many people make do with the firmware's own boot manager, but this can be rather inflexible. I'm not even sure if Apple's boot manager can handle passing options to Linux kernels' EFI stub loaders. This ability is not absolutely required, but without it you must compile your options into your kernel at compile time, which greatly reduces flexibility since you can't modify the options on a per-boot basis -- say, to boot into single-user mode if this is required.
2. Will grub/rEFInd/syslinux do some of the work for me initially/on a kernel update?
The usual Arch Linux method of handling kernel updates is to overwrite an old kernel with a new one, so no boot loader/boot manager changes are required. If you want to keep numbered kernels around (as most other distributions do), GRUB provides scripts that can help automate changes, but they are required in the grub.cfg file. rEFInd can auto-detect boot loaders, and if you're using the EFI stub loader, that means that the kernel is its own boot loader, and with a proper configuration, rEFInd can detect new kernels without changing its configuration file.
SYSLINUX has some very early and very experimental EFI support. The one and only time I tried it (about a month ago), it wouldn't compile for me. (I don't know of a precompiled binary available on the Web -- the support is that new!) I don't recommend trying it unless somebody who's gotten it to work offers to help you personally.
3. Will `efibootmgr` brick my mac? https://wiki.archlinux.org/index.php/UE … FI_systems says it will, but I think the `grub-install` command uses `efibootmgr`, so should I not try grub on here (this package: https://www.archlinux.org/packages/core … fi-x86_64/ ).
There were reports of efibootmgr damaging Mac firmware several months ago (I believe over a year ago). Since then I've seen claims that this problem has been fixed with recent kernels (3.0 and later, IIRC), but I've seen no substantiation one way or the other. Overall, I recommend caution....
Also some of the other packages (like rEFInd-efi) depend on efibootmgr, so does that mean any kind of an install from them (a command from the package, not the `pacman -S pkg` command) will also brick my system? (see rEFInd-efi dependencies: https://www.archlinux.org/packages/extr … efind-efi/ )
On a Mac, I recommend installing rEFInd (or any other EFI boot loader) from OS X rather than from Linux. (Note that I'm rEFInd's maintainer, so that's an official recommendation from the software's developer.) Offhand, I don't know if the Arch package for rEFInd runs efibootmgr automatically on boot or just has it as a dependency because efibootmgr is the usual way to register a boot loader on UEFI systems. If the latter, it should be safe to install the Arch package for rEFInd, copy its files, and then reboot to OS X to run bless on it. It would be just as easy, if not easier, to install it completely from OS X, though. -
Sound problems with 2.6.18 kernel
hi
i cant play any sound with kernel 2.6.18 PC just hangs and no sound played now i am using beyond version its 2.6.17 kernel version and everything is ok. i have some problems with apic and from 2.4 kernel i must boot with noapic nolapic flags.
M/B DFI AD77 with build in AC97 sound using snd_via82xx modules
arch linux is fresh installed
sorry for my english i am not english speaker
thanx for helpi analyzed dmesg output deeper and found something suspicious
can't register device seq
i unload all sound modules and attempted to load modules, then checked dmesg output and there appears new lines of that error, it seams problem is in seq device. now is question how to fix it.. from there that error appears form kernel, from sound module or from alsa ? ill try other sound system later and will post results. -
Tecra S2: Problems with Linux Live CDs after BIOS upgrade
Hi all,
a short while ago I flashed the BIOS of my Tecra S2. My current BIOS version now is 2.80. Unfortunately no I have got problems with booting Linux Live CDs like Knoppix or Kanotix. The boot process freezes, when the PCMCIA module is tried bo be started.
What i want to do now is to downgrade my BIOS version. Does anyone know how that stuff works and does anyone have an old BIOS version from 2005? I couldn`t found older versions on the Toshiba support sites.
Thanks for all answers!
biberkopfYoure right. On the Toshiba page you will find only the newest version of the BIOS and the older versions are not available on the page.
In my opinion if you want to downgrade the BIOS you have to ask the authorized service provider in your country for the help.
But did you check this useful site:
http://newsletter.toshiba-tro.de/main/
There you can check the area machine installation help
It provides some useful tips with the device configuration -
Problems with TV - Card after Kernel Upgrade
Hi Folks,
since the last Kernel Upgrade I've got problems with my tv tuner card. Since ever I had to set the tuner manually to 38. But now it seems that its not enough just to set this type.
I used this script to set up my card correctly:
modprobe -r cx88-dvb cx88-blackbird cx8802 cx88-alsa cx8800 cx88xx
modprobe cx88xx tuner=38
modprobe cx8800
Now I've got weired sound and only a few stations, with a very poor picture quality. After reloading the modules with the script dmesg says:
tda9887 2-0043: destroying instance
tuner-simple 2-0061: destroying instance
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 16
cx88[0]: subsystem: 0070:3401, board: Hauppauge WinTV 34xxx models [card=1,autodetected]
cx88[0]: TV tuner type 38, Radio tuner type -1
tuner' 2-0043: chip found @ 0x86 (cx88[0])
tda9887 2-0043: creating new instance
tda9887 2-0043: tda988[5/6/7] found
tuner' 2-0061: chip found @ 0xc2 (cx88[0])
tveeprom 2-0050: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom.
cx88[0]: warning: unknown hauppauge model #0
cx88[0]: hauppauge eeprom: model=0
tuner-simple 2-0061: creating new instance
tuner-simple 2-0061: type set to 0 (Temic PAL (4002 FH5))
input: cx88 IR (Hauppauge WinTV 34xxx as /class/input/input8
cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 16, latency: 32, mmio: 0xe6000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
From my (limited) point of view the problem is, that tuner-simple does not loads the correct tuner type? I've looked into modinfo from tuner-simple but there is no parameter for type... What else could be the problem?
Thanks in advance
BadcelHi cjpembo,
my Card looks like:
01:07.0 Multimedia video controller [0400]: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [14f1:8800] (rev 05)
01:07.1 Multimedia controller [0480]: Conexant CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] [14f1:8811] (rev 05)
My card seems to be another version. Regarding to the v4l Wiki: http://linuxtv.org/v4lwiki/index.php/Tu … ted_Tuners
A new Hauppauge WinTV PCI-FM card is here (pci_ids: 14f1:8800, 14f1:8811), using the TCL MFPE05-02 PAL (DK BG I) FM tuner. It just implements mk3 API, you can use philips 1216me mk3 (tuner=38) instead.
If I don't specify any module parameters, the tuner type 0 is selected.
ACPI: PCI interrupt for device 0000:01:07.0 disabled
tda9887 2-0043: destroying instance
tuner-simple 2-0061: destroying instance
Linux video capture interface: v2.00
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
ACPI: PCI Interrupt 0000:01:07.0[A] -> Link [APC1] -> GSI 16 (level, high) -> IRQ 16
cx88[0]: subsystem: 0070:3401, board: Hauppauge WinTV 34xxx models [card=1,autodetected]
cx88[0]: TV tuner type -1, Radio tuner type -1
tuner' 2-0043: chip found @ 0x86 (cx88[0])
tda9887 2-0043: creating new instance
tda9887 2-0043: tda988[5/6/7] found
tuner' 2-0061: chip found @ 0xc2 (cx88[0])
tveeprom 2-0050: Encountered bad packet header [00]. Corrupt or not a Hauppauge eeprom.
cx88[0]: warning: unknown hauppauge model #0
cx88[0]: hauppauge eeprom: model=0
tuner-simple 2-0061: creating new instance
tuner-simple 2-0061: type set to 0 (Temic PAL (4002 FH5))
input: cx88 IR (Hauppauge WinTV 34xxx as /class/input/input8
cx88[0]/0: found at 0000:01:07.0, rev: 5, irq: 16, latency: 32, mmio: 0xe6000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
The card is not listed in my local PCI ID repository. And it seems, that the PCI ID is not known to the PCI ID Repository: http://pci-ids.ucw.cz/iii/?i=0070
Badcel
Last edited by badcel (2008-08-24 09:46:18) -
Strange Boot problem with iMac OSX 10.7.5 (Boot loop, not working safe boot etc.)
Hey guys,
I've got a strange problem with my iMac Late 2009. This morning it didn't want to boot (grey screen with turning wheel). Yesterday when I shut it down everything was fine. Last backup was finished three minutes before. So I was a bit shirty but noch scared of any data loss.
I tried the following things:
1. boot recovery and check hdd (it's a new one, only second day back from apple store for replacing seagate hdd), everythings fine
2. try to boot in safe mode, did not work!
3. try to boot in verbose mode, did work until it stopped. Screenshot of the last lines of log is within this post
4. I used my TM backup and afterwards I could boot! Strange, because as I sad the backup finished a few minutes beforce I left my mac and shut it down
Now I'm a bit scared of shutting it down again But what would be the next step to find the error? My first thought were some third party kernel extensions, but that would not affect a safe mode boot, am I right? I have a Macbook Air here which is setup nearly identical to my mac and it's working. Could it be a hardware fault? Maybe you've got an idea.
Thanks!
Maxat the moment it seems to be a corrupted time machine backup from my old hard drive (new one has a runtime of 27 hours). So I'll will try a clean install of my system at least, when I got the time. sh%&$ !
-
Problem with linux installation on Thinkpad T410i
Hello everyone. I have a problem with an installation of Linux (Debian). Installation ended in my Thinkpad T410i, but when you are starting, the computer constantly restarts. With windows does not happen. What's the problem?
Probe with two versions: one with and one without GUI, and always restarts during startup stage or just finish loading the operating system. If eligo Windows in GRUB, the pc works normally.
I appreciate any help you can give me.Madhukar,
Check the below forums which also discuss about same problem like yours.
Trouble with SAP system installation GUI
error in installation of solution manager
Regards,
Debasis. -
Cd rom boot problems with MEGA 180
I recently recieved my MEGA 180 and have been unable to successfully install an OS because when I boot from CD, the computer freezes at various stages of installation. The point at which it freezes varies between the point at which the CD is initialized to anywhere in the windows xp setup process up untill the drive format. Occassionally the lockup coincides with an error copying a file, but this is not consistent. I have tried two different cd-rom drives as well as three different xp installation cds. Further I have run with 5 different sticks of ram (kingston and corsair). None of these changes have had any obvious effect.
Having read the warning labes regarding non MSI optical devices, I am tempted to think that may be the problem as I am not running on an MSI drive. However, the warning souned like it was about mechanical parts and thus I assume the ability of a drive to fit in the MEGA 180 case while opening and closing correctly.
I would appreciate any input you might have on this matter as I am finding this experience rather frustrating.I had the exact same problem when upgrading from a 2100+ Palamino processor to a 2800+ Thoroghbred one. The screen had already dissappeared due to powering up with no monitor plugged in, so I tried a reinstall of Windows XP. It kept falling over randomly during the install process. I then swapper the CPU back and had no problems at all. I have since lapped the heatsink and reduced the FSB to 157MHz in the BIOS, and have not had a problem with the 2800+ CPU. I have not tried installing windows again, but feel this will be OK too.
My test is to run FujiFilm Snapshot Slideshow, which sends the CPU temp rocketting. I have found that when it goes above 70 C it starts getting unstable. I throttled the FSB back to 157MHz and it does not get to 70 C any more. In normal operation it never gets above 60 C, so I don't know why the slideshow takes so much CPU power -
I have just bought a new HD (WD 120GB SE, ATA100, 8MB CACHE) for my PC. My old HD was a Quantum Fireball Plus AS 20.5GB. I had in mind to remove the old one and copy the 2 partitions from the old one to the new (3 Partitions made by Partition Magic). I used the Norton Ghost 9 to copy the partitions with the "copy one drive to another' option, also select the one partition to be "active" so it can boot the OS and copy the "master boot records" from the old HD. When i restart the PC with the new HD as master after the "veryfing DMI pool data" i should see the windows logo with the loading bar, but the only thing i get is under the "veryfing DMI pool data" the message "error loading operating system"! ! ! The same thing happens if i copy the partition (with the OS) to a dvd again with Norton Ghost and try to recover it. And the strangest thing is that i have the same problem if i try to install (clean) windows to the HD, it copies some files to the HD and when it restarts so it can continue installing windows shows the same message. I have download a diagnostic program from WD and there is no problem with the HD. I have taken the HD to a friend of mine and it works fine. I forgot to mention that both bios and windows detect the HD. When i use the HD as slave, i can copy/cut files/folders with no problem in windows. I have the latest ver. of bios and nForce drivers. PLEASE HELP ME! ! !!
P.S. Sorry for my english. . .If you use Ghost to copy from one disk to another and the geometry is different, it can happen that the result is not readable.
Simple way: plug disk as slave. Boot on the 20GB drive. Partition the new drive in windows. Copy the files.in windows. Activate the new partition as primary and bootable. Swap drives. -
Problems with key shortcuts after kernel update (can't shutdown wifi)
Hi! Sorry for my poor english!
I have 2 problems on my laptop that went out after a kernel update; the first one involves the wireless card (Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01), but I don't think it is important): when I press the key shortcut it switches off only partially, the led remains lighted and with "rfkill list all" i get that is actually only software blocked.
The second problem is about the key shortcut to switch off the screen: even with xev it isn't recognised anymore.
I am pretty sure the 2 problems are related; the latest kernel with they were working is 3.5.6-1, in fact if I downgrade to that version I haven't got any problem.
I have encountered this issue with 3 models of Asus EEEPC: 1015pd (mine), 1215b and 1015cx, (the first two with AR9285, the third with AR9485).
Thanks for the help ;-)Ok, so after removing catalyst-test and trying to install catalyst, I got the following error:
resolving dependencies...
warning: cannot resolve "catalyst-utils", a dependency of "catalyst"
:: The following package cannot be upgraded due to unresolvable dependencies:
catalyst
Proceeding to try installing catalyst-utils...
Maybe you are looking for
-
I don't know if this is a bug, but I'm running Lion.
-
Problem with Iplanet/JWS 6.1 connecting to Weblogic on Solaris
We have an application which runs JSPs and Servlets on SJSWS/Iplanet 6.1 and uses EJBs on Weblogic 8.1 for database access. When the Weblogic server is running on a Windows box, there is no problem accessing the EJBs. But we have not been able to get
-
Fields mandatory on contract...
Hello all, how to make these fields mandatory on contract-plant, shipping point, contract start & end dates . what would be best way- user exit or transaction variant. as our requirement is when ever we trying to save the contract system should not a
-
Important question! need help please
I was wandering if the Cmos battery is dead or not working, does that mean the whole motherboard including the PSU and NB will not work or boot???
-
As a baseball coach how can I view Ubersense on a monitor?
How do I view Ubersense on a monitor from my iPad?