Hang at boot with rEFInd
After last kernel update (using all testing repos) I rebooted my notebook and -> CRACK... rEFInd let me choose between windows 8 and Arch as usual but if I choose Arch it will display only kernel boot line and then it hangs... why that happens?
my configuration has refind 0.6.7-1 so I haven't created arch folder in /boot/efi/EFI/ but left kernel and initramfs in /boot and I put refind_linux.conf in /boot.. in /boot/efi/EFI I copied tools/drivers_x64 folder from /usr/lib/refind for ext4 driver...
some configs file:
/boot/refind_linux.conf
"Boot with defaults" "root=PARTUUID=d464040b-4ac6-458e-bcd4-245d05944d47 rootfstype=ext4 ro add_efi_memmap systemd.unit=graphical.target"
"Boot to terminal" "root=PARTUUID=d464040b-4ac6-458e-bcd4-245d05944d47 rootfstype=ext4 ro add_efi_memmap systemd.unit=multi-user.target"
/boot/efi/EFI/refind/refind.conf (without comments)
timeout 5
scan_driver_dirs EFI/tools/drivers_x64,drivers_x64
scan_all_linux_kernels
if other informations are needed tell me, I will add them
ps: I mount /dev/sda1 (UEFI partition) in /boot/efi... in your opinion is it better if I mount it in /boot ???
My full steps were:
mkdir -p /boot/efi/EFI/refind/
cp /usr/lib/refind/refind_x64.efi /boot/efi/EFI/refind/
cp /usr/lib/refind/config/refind.conf /boot/efi/EFI/refind/
cp -r /usr/share/refind/icons /boot/efi/EFI/refind/
cp /usr/lib/refind/config/refind_linux.conf /boot/
mkdir -p /boot/efi/EFI/tools/
cp -r /usr/lib/refind/drivers_x64 /boot/efi/EFI/tools/
Edited refind_linux.conf only by adding partuuid and rootfstype.
Edited refind.conf whith scan_driver_dirs EFI/tools/drivers_x64
Similar Messages
-
Hangs on boot with Logitech wireless keyboard
I am running Windows 7 on a Thinkpad W510 and just bought a Logitech S520 wireless keyboard and mouse.
When I try to boot, the system hangs at the Thinkpad splash screen.
I updated the BIOS to the latest version but it had no effect. I also changed the boot sequence so that USB boot was after HD boot.
This had no effect and the system still hangs on boot.
If I remove the USB receiver the system boots fine and I can then insert the USB receiver and everything works propely.
Is there anything that I am missing? This just doesn't make sense.
Thanks for any further suggestions.I have the newer port replicator (issued July ?? 2010) and it is always plugged in to USB 2 port. From the port replicator I go to a powered USB hub. In the later I have the transmitter for my Logitech mouse. I have never tried the Logitech transmitter directly in my laptop so can indicate whether that would hang my system and at least right now I'm not interesting in trying it.
-
Mac Mini hangs on boot with grey Screen. No response to Keyboard
Hello,
yesterday my Mac Mini (C2Duo, fifth generation unibody) startet to behave strangely. First thing was that it was not responding to the mouse(connected throught the keyboard)
I replaced the mouse and everything seemed to be ok.
I then did the latest update available on Mountain Lion and went home.
When I came back this morning, the Mac Mini hang with grey screen. I restarted. Again grey screen.
Chime comes. Then nothing.
Tried everything from http://support.apple.com/kb/ts2570 but nothing worked. The Mac Mini does not seem to be responding
to any keyboard command to enter safe mode, select boot device etc. No firmware password has been set.
Any help/ suggestions would be appreciated.
Yours,
AndreasHave you reset the SMC, then held down the mouse button while restarting to get the CD out?
Reset SMC:
Shut down the computer.
Unplug the computer's power cord.
Wait fifteen seconds.
Attach the computer's power cord.
Wait five seconds, then press the power button to turn on the computer. -
MBP hangs when booting with network plugged in
My macbook pro (just got it last week) seems to be hanging whenever the wired network is plugged in.
as soon as i pull the network jack out, the MBP finishes booting into OSX. any ideas? is the network controller busted maybe?Hi brinox;
May I welcome you to the Apple Discussion Forums.
Before jumping to that drastic of a solution for your problem, I would like to ask if you have go into System Preferences and made sure the hard drive is your boot device in Startup Disk. It is possible it is pointing at the network and with nothing plugged in that fails. Please give that a try and let us know the results.
Allan -
Dell xps hangs on boot with GPIB card
After installation of the NI GPIB card the computer fails to find a boot device. It boots fine if the card is removed. The BIOS was updated with the latest version, but it made no difference. The computer is a Dell XPSB800 running Windows 98 2nd ed. The card works fine in a Dell Optiplex. Help.
I have the same issue as AH.
After installation of the PCI-GPIB card the computer reports "No Boot Devices Found - System Halted". It boots fine if the card is removed. As in the previous message, the BIOS was updated with the latest version, but it made no difference. The computer is a Dell XPSB1000 running Windows 2000. Removing all other PCI cards (network, sound, parallel port) and relocating the card did not solve the problem. -
Kernels 3.10.6 and 3.10.7 fail to boot with EFI stub
Been using rEFInd for some time now. Current installed version is 0.7.1. Kernels 3.10.5 and earlier would boot without incident. Yesterday I upgraded to 3.10.6 and boot failed. As a workaround, I copied the Liquorix kernel and initramfs from my Kubuntu partition; to my mild surprise, this worked. My next test was to install the 3.10.7 Zen kernel from heftig's repository. This kernel boots fine (I added a version number string to the name of the kernel image and the initramfs so that rEFInd would automatically match them). After that, I enabled Arch testing and updated the Arch kernel to 3.10.7; this also fails to boot just like the 3.10.6 kernel did.
I'm a fan of boot text, so I've configured rEFInd in text mode only. Here's my refind.conf, with almost no changes from defaults:
timeout 20
textonly 1
use_graphics_for
scan_all_linux_kernels
And my /boot/refind_linux.conf:
"Boot to X" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=graphical.target"
"Boot to single user" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=multi-user.target"
# "Boot to recovery" "ro root=/dev/sda3 nox2apic nomodeset systemd.unit=rescue.target"
Finally, details abot my laptop -- a ThinkPad T520:
steve@t520 ~ $ inxi -xxSMCGDp
System: Host: t520 Kernel: 3.10.7-1-zen x86_64 (64 bit, gcc: 4.8.1)
Desktop: KDE 4.11.00 (Qt 4.8.5) dm: kdm Distro: Arch Linux
Machine: System: LENOVO product: 423926U version: ThinkPad T520 Chassis: type: 10
Mobo: LENOVO model: 423926U Bios: LENOVO version: 8AET63WW (1.43 ) date: 05/08/2013
CPU: Dual core Intel Core i7-2620M CPU (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10769.3
Clock Speeds: 1: 1188.00 MHz 2: 1809.00 MHz 3: 1809.00 MHz 4: 1080.00 MHz
Graphics: Card: NVIDIA GF119M [Quadro NVS 4200M] bus-ID: 01:00.0 chip-ID: 10de:1057
X.Org: 1.14.2 driver: nvidia Resolution: [email protected]
GLX Renderer: NVS 4200M/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 325.15 Direct Rendering: Yes
Drives: HDD Total Size: 1256.3GB (8.2% used)
1: id: /dev/sda model: M4 size: 256.1GB serial: 000000001140031E608A temp: 0C
2: id: /dev/sdb model: HGST_HTS721010A9 size: 1000.2GB serial: JG40006PG61HKC temp: 43C
Partition: ID: / size: 108G used: 37G (37%) fs: ext4
ID: /boot/efi size: 511M used: 3.1M (1%) fs: vfat
ID: /mnt/kubuntu size: 118G used: 59G (53%) fs: ext4
ID: swap-1 size: 9.64GB used: 0.00GB (0%) fs: swap
Last edited by steveriley (2013-08-19 05:27:15)Steve, your picture is far too large for these forums. You are going to want to put it in some kind of a picture sharing/hosting site and link back to it. Otherwise it will end up disappeared (likely via black magic) from your post. I don't think that it provides any useful information anyway. If you want to post your kernel command line that is great. But posting a picture of a frozen screen with no output... doesn't really do much good.
Efistub has been a bit shaky since 3.6 actually. There is a monster thread about this already, the title of which references 3.6, but the content continues on through several kernel releases. Still people continually report this as being an issue. What I do is I keep a normal efi bootloader (one that doesn't rely on efistub) at the ready all the time. My choice was elilo, but since [testing] started including syslinux-efi in the syslinxu package, I have started using that... though I still have elilo set up.
Can you boot with efistub from the UEFI Shell or gummiboot? I prefer gummiboot, but I have had this problem in the past, and when I did, I was able to boot with rEFInd... which was strange. Some people even report that simply having a direct efibootmgr entry in their firmware causes it to magically work. Though there should be to reasonable explanation for this, it was confirmed by several people in the mentioned thread. -
W701 Won't boot with USB dongle attached
W701 with current BIOS (6KET46WW v1.12) will hang if there is a USB dongle for a Microsoft Explorer Mouse USB dongle in the upper left USB (2.0) socket on boot. Works fine if you put the USB dongle in the lower USB/eSata socket. Note that the upper socket on this 2541-W1Z is NOT a USB 3.0 port (silver, not blue). Course I don't want to put it in that socket since I like to use that for eSata... Apparently the same problem exists in the W5XX laptops as well, but I don't see a post discussing the issue on the W701.
Have you seen the thread
Hangs on boot with Logitech wireless keyboard
Yours may be a similar problem.
I'm about to get a W701 in a day or 2 and will be in the same situation. I'll check it out and report back when I can.
ThinkPad W701 25002LG, i7 2Ghz,FX 3800M, 4Gb,16GB, SSD 320GB, DVDRW, RGB WUXGA, Wacom, Col Sensor, Fingerprint reader, Mini Dock -
[SOLVED] Advice for Arch install with rEFInd dual boot Lenovo laptop?
I am trying to plan an Arch install on a new laptop for dual boot with Windows 8.1, but I know there is a potential to cause huge problems so I have been trying to read and learn about the hard disk partition structure and how I might install the rEFInd boot files so that I am still able to boot Windows once Arch is installed. (Unfortunately for some tasks such as updating the maps on my satnav box Windows is essential). However I am really quite unsure if I am doing the right thing in the way I am thinking about the Arch install so I would appreciate any help from experts on the forum.
The laptop is a Lenovo IdeaPad Y510p which came with Windows 8 pre-installed, with the option to upgrade to Windows 8.1. The upgrade was completed without issue and I then looked into the question of hard drive partitions and boot. I had read posts on the Ubuntu forums about users who had installed Ubuntu on this same laptop and ended up being unable to boot Windows afterwards so I wanted to tread very carefully before executing anything which might cause really major damage. I had also read on the Lenovo forums replies about people who had replaced the hard drive and installed linux only to find that they could not boot to the recovery partitions, with replies from Lenovo moderators saying that if the partition structure had been changed then the laptop would have to be sent back to Lenovo for a factory repair.
On this laptop to get into the bios or boot options you do not just press the power button and hit an F key, but instead there is a special small "OneKey Recovery" button next to the power jack, which opens up with options for BIOS setup and boot options as well as normal boot or recovery. This OneKey Recovery button is therefore needed to boot a usbkey - the power button only allows it to boot to windows presumably until/unless a different bootloader and NVRAM entry is amended.
I have done all the initial ( safe!)changes necessary to move to the point at which I can execute the Arch install. From within Windows (switched off fastboot, and shrunk the "C:" drive to make space for linux partitions). I have also switched off Secure Boot from the BIOS, and made sure that Windows still boots up fine.
The current arch install iso (February 2014) boots under uefi just fine - and of course once booted I have access to the gdisk programme. That certainly showed the pre-existing partitions on the drive (8 partitions with partition number 2 being the EFI partition, and three recovery partitions!) with a GPT partition table, and it should therefore be possible to make the necessary new linux partitions in the now unallocated space on the disk that was freed up with the internal disk management facility within Windows 8.1. So at that point I created three partitions for a root partition (type 8300), a swap partition (type 8200) and another type 8300 partition which will become /opt in the installed Arch system.
In order to try and not make any changes to the partition structure I let the three new linux partitions be number 9, 10 and 11.
I am told that for a GPT disk it is a definite no-no to try to create more than one EFI partition. So I will need to use the existing EFI partition to place the rEFInd files and the kernel once I install Arch.
In this (Y510p) laptop the EFI partition contains the following structure:
BOOT/ - containing only boot.sdi
BOOTSECT.BAK
EFI/ which contains two directories Boot/ and Microsoft/
so EFI/Boot/ contains only Boot64.efi which is likely a fallback copy of the Windows 8.1 bootloader
and EFI/Microsoft/ contains a Boot/ directory - so
EFI/Microsoft/Boot/ contains loads of language specific directories like en-GB/
plus bootmgfw.efi (which I believe is the Windows main efi loader file)
bootmgr.efi
memtest.efi
The scheme that I am planning to use which I have previously used in pure Arch uefi machines, is that /boot is a directory in the root partition, /. That way /boot is an ext4 directory and will contain the kernel and initramfs plus the rEFInd linux config file.
Then I can mount the EFI (vfat) partition as /boot/efi and so I can then make a /boot partition under /. Then the EFI /BOOT/ directory would be seen in Linux as /boot/efi/BOOT/ and the Windows efi stuff would be in /boot/efi/EFI/Boot/Microsoft/Boot/ in which case I would presume that I have to make a new directory in /boot/efi/EFI/refind/ and put the refind stuff including the filesystem drivers there, and let the kernel go into the (ext4) /boot/ directory which would be preferred! However I am not 100% confident that this is what will work and I need to read more before trying to do the install. The thing that concerns me is how the system will handle the uefi boot process, and whether it would auto-detect the Windows efi file as well as the Arch refind efi file once the system has started up?
... and then there is the issue of the NVRAM entries and I am no longer confident that if I use the usual tools to create an entry (efiboomgr or bcfg), that I will get a successful dual boot system!
There is still a chance that I would irrevocably damage being able to boot to the Windows and Recovery partition boot options by messing up the EFI and/or the NVRAM so I have to tread very very carefully with this.
If anyone has gone through this kind of dual boot install with a Windows 8 or 8.1 machine using rEFInd for the bootloader, and can offer advice or help here I would very much appreciate it. I have another pure Arch system which uses rEFInd that works extremely well, but it seems that dual boot with uefi is a rather more complex animal than a pure linux system!
Last edited by mcloaked (2014-02-22 10:06:03)vipin wrote:I have recently bought the y510p , im planning to install Arch , this is my 4th laptop , i had installed Arch in all the other 3 with no problems, but im a bit worried with the installation as this is the first laptop which has EFI , im a linux user for the past 6 years , i started with fedora , now i like Arch , mike documentation is excellent, i just had one question when i had grub , it automatically finds the new kernel when i update (grub.conf/menu.lst gets updated), does rEFInd also do that.
When there is an update to the rEFInd package you need to copy the files across to your ESP from the files contained in /usr/share/refind/ usually you need to copy the refind_x64.efi binary as well as the icons, fonts, and drivers directories. Since there is flexibility in how you configure the kernel and initrd files in terms of where they are located whether you need to do anything else when a new kernel update arrives depends on how you set your system up. If you have the /boot directory as your ESP partition which will then have the kernel and initrd files updated by default then there no need to do anything else when there is a kernel update. If the ESP is then at /boot/EFI and within that is your refind/ directory then that is where the replacement files go if refind-efi gets a pacman update. So it is actually fairly straight forward. If you configure rEFInd to look for kernels in some other directory than /boot/ then you may need to copy the files there after a kernel update but there is more information in the arch wiki about this.
During a refind-efi package update there are helpful files in the pacman output (and log) reminding you of what you need to do. eg for the latest refind-efi update you get:
[2014-06-18 18:48] [PACMAN] upgraded radvd (1.12-1 -> 1.13-1)
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd UEFI application has been installed at /usr/share/refind/refind_*.efi
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] Other UEFI applications have been installed at /usr/share/refind/tools_*/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] UEFI drivers have been installed at /usr/share/refind/drivers_*/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] Copy the efi application (according to your UEFI ARCH)
[2014-06-18 18:48] [ALPM-SCRIPTLET] and /usr/share/refind/refind.conf-sample to a sub-directory of <EFISYS>/EFI/
[2014-06-18 18:48] [ALPM-SCRIPTLET] as refind.conf and add an entry to firmware boot menu using efibootmgr
[2014-06-18 18:48] [ALPM-SCRIPTLET] or mactel-boot (for Macs)
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd Icons have been installed at /usr/share/refind/icons/
[2014-06-18 18:48] [ALPM-SCRIPTLET] rEFInd Fonts have been installed at /usr/share/refind/fonts/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] HTML Documentation is available at /usr/share/refind/docs/html/
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [ALPM-SCRIPTLET] More info: [url]https://wiki.archlinux.org/index.php/UEFI_Bootloaders#Using_rEFInd[/url]
[2014-06-18 18:48] [ALPM-SCRIPTLET]
[2014-06-18 18:48] [PACMAN] upgraded refind-efi (0.8.1-1 -> 0.8.2-1)
I hope that helps.
By the way you can also boot uefi using grub and in fact you can get rEFInd to chainload grub as a backup bootloader as an added safety factor and have both rEFInd as well as grub installed simultaneously. How that can be done is explained in the thread at https://bbs.archlinux.org/viewtopic.php?id=181906
Last edited by mcloaked (2014-06-25 17:41:12) -
[SOLVED] Need help with rEFInd boot entry for rsync backup
I made a successful backup my arch install to an other internal SSD disk (from my HDD).
But now I can't figure out how to make a boot entry for this drive. The wiki only mentions GRUB, which I do not use.
This is the fstab for my HDD:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda5
UUID=c1822e3c-e037-4445-bdd8-b71778237dee / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
And this is the fstab on my SSD which I edited:
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sdb1
UUID=c61a1301-4728-465d-b40b-bde5e084eb50 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda2 LABEL=SYSTEM_DRV
UUID=D2DF-9F74 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
But I'm not sure about the /boot entry, do I need something else here?
Afterward I tried updating rEFInd by reinstalling using refind-install, but that did not work.
ps. I dual boot with Windows.
Last edited by Devenda (2014-08-18 07:58:07)I also tried adding the menu entry manually by editing refind.conf but that didn't work. I got:
Invalid loader file!
Error: Not Found while loading vmlinuz-linux
Here is some additional info:
refind.conf:
menuentry "SSD Arch Linux" {
icon /EFI/refind/icons/os_arch.png
volume "ArchSSD"
loader /boot/vmlinuz-linux
initrd /boot/initramfs-linux.img
options "root=/dev/sdb1 ro"
I hope this helps.
blkid
/dev/sda1: LABEL="WINRE_DRV" UUID="7C2ADD1D2ADCD4EC" TYPE="ntfs" PARTUUID="b7137819-2ca6-40fb-9167-b73ac37d8d96"
/dev/sda2: LABEL="SYSTEM_DRV" UUID="D2DF-9F74" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="9c77b526-730f-42f9-9904-f9a31b205687"
/dev/sda3: PARTLABEL="Microsoft reserved partition" PARTUUID="f4d5275b-24c1-4847-b937-345bc23bec89"
/dev/sda4: LABEL="Windows 8" UUID="38D6E449D6E408C8" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d777a359-f42c-4629-a07c-cc55316352fe"
/dev/sda5: UUID="c1822e3c-e037-4445-bdd8-b71778237dee" TYPE="ext4" PARTUUID="3d282004-2515-4630-b82e-35ed7f707b89"
/dev/sda6: UUID="F80680CC06808D76" TYPE="ntfs" PARTUUID="575bc623-c7f1-44da-a79e-220ce3c98d9b"
/dev/sda7: LABEL="Lenovo_Recovery" UUID="0898D76B98D75632" TYPE="ntfs" PARTUUID="99bfc6d6-1b71-46d1-887e-2f7e65e3eab1"
/dev/sdb1: LABEL="ArchSSD" UUID="c61a1301-4728-465d-b40b-bde5e084eb50" TYPE="ext4" PARTUUID="e87704a5-01"
lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 ntfs WINRE_DRV 7C2ADD1D2ADCD4EC
├─sda2 vfat SYSTEM_DRV D2DF-9F74 /boot
├─sda3
├─sda4 ntfs Windows 8 38D6E449D6E408C8
├─sda5 ext4 c1822e3c-e037-4445-bdd8-b71778237dee /
├─sda6 ntfs F80680CC06808D76
└─sda7 ntfs Lenovo_Recovery 0898D76B98D75632
sdb
└─sdb1 ext4 ArchSSD c61a1301-4728-465d-b40b-bde5e084eb50
sr0
boot tree
/boot
├── BOOT
│ └── boot.sdi
├── BOOTSECT.BAK
├── EFI
│ ├── Boot
│ │ ├── bootx64.efi
│ │ ├── LenovoBT.EFI
│ │ ├── License.txt
│ │ └── ReadMe.txt
│ ├── gummiboot
│ │ └── gummibootx64.efi
│ ├── Lenovo
│ │ └── Boot
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ ├── BCD.LOG2
│ │ ├── bg-BG
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── bootmgfw.efi
│ │ ├── bootmgr.efi
│ │ ├── BOOTSTAT.DAT
│ │ ├── boot.stl
│ │ ├── cs-CZ
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── da-DK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── de-DE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── el-GR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── en-GB
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── en-US
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── es-ES
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── et-EE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── fi-FI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Fonts
│ │ │ ├── chs_boot.ttf
│ │ │ ├── cht_boot.ttf
│ │ │ ├── jpn_boot.ttf
│ │ │ ├── kor_boot.ttf
│ │ │ ├── malgun_boot.ttf
│ │ │ ├── malgunn_boot.ttf
│ │ │ ├── meiryo_boot.ttf
│ │ │ ├── meiryon_boot.ttf
│ │ │ ├── msjh_boot.ttf
│ │ │ ├── msjhn_boot.ttf
│ │ │ ├── msyh_boot.ttf
│ │ │ ├── msyhn_boot.ttf
│ │ │ ├── segmono_boot.ttf
│ │ │ ├── segoen_slboot.ttf
│ │ │ ├── segoe_slboot.ttf
│ │ │ └── wgl4_boot.ttf
│ │ ├── fr-FR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── hr-HR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── hu-HU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── it-IT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ja-JP
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ko-KR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── lt-LT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── lv-LV
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── memtest.efi
│ │ ├── nb-NO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── nl-NL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pl-PL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-BR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-PT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── qps-ploc
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Resources
│ │ │ ├── bootres.dll
│ │ │ └── en-US
│ │ │ └── bootres.dll.mui
│ │ ├── ro-RO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── ru-RU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── sk-SK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sl-SI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-CS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sv-SE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── tr-TR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── uk-UA
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── zh-CN
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── zh-HK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── zh-TW
│ │ ├── bootmgfw.efi.mui
│ │ ├── bootmgr.efi.mui
│ │ └── memtest.efi.mui
│ ├── Microsoft
│ │ └── Boot
│ │ ├── BCD
│ │ ├── BCD.LOG
│ │ ├── BCD.LOG1
│ │ ├── BCD.LOG2
│ │ ├── bg-BG
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── bootmgfw.efi
│ │ ├── bootmgr.efi
│ │ ├── BOOTSTAT.DAT
│ │ ├── boot.stl
│ │ ├── cs-CZ
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── da-DK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── de-DE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── el-GR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── en-GB
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── en-US
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── es-ES
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── et-EE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── fi-FI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Fonts
│ │ │ ├── chs_boot.ttf
│ │ │ ├── cht_boot.ttf
│ │ │ ├── jpn_boot.ttf
│ │ │ ├── kor_boot.ttf
│ │ │ ├── malgun_boot.ttf
│ │ │ ├── malgunn_boot.ttf
│ │ │ ├── meiryo_boot.ttf
│ │ │ ├── meiryon_boot.ttf
│ │ │ ├── msjh_boot.ttf
│ │ │ ├── msjhn_boot.ttf
│ │ │ ├── msyh_boot.ttf
│ │ │ ├── msyhn_boot.ttf
│ │ │ ├── segmono_boot.ttf
│ │ │ ├── segoen_slboot.ttf
│ │ │ ├── segoe_slboot.ttf
│ │ │ └── wgl4_boot.ttf
│ │ ├── fr-FR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── hr-HR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── hu-HU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── it-IT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ja-JP
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── ko-KR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── lt-LT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── lv-LV
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── memtest.efi
│ │ ├── nb-NO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── nl-NL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pl-PL
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-BR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── pt-PT
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── qps-ploc
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── Resources
│ │ │ ├── bootres.dll
│ │ │ ├── en-US
│ │ │ │ └── bootres.dll.mui
│ │ │ └── nl-NL
│ │ │ └── bootres.dll.mui
│ │ ├── ro-RO
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── ru-RU
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── sk-SK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sl-SI
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-CS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sr-Latn-RS
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── sv-SE
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── tr-TR
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── uk-UA
│ │ │ ├── bootmgfw.efi.mui
│ │ │ └── bootmgr.efi.mui
│ │ ├── zh-CN
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ ├── zh-HK
│ │ │ ├── bootmgfw.efi.mui
│ │ │ ├── bootmgr.efi.mui
│ │ │ └── memtest.efi.mui
│ │ └── zh-TW
│ │ ├── bootmgfw.efi.mui
│ │ ├── bootmgr.efi.mui
│ │ └── memtest.efi.mui
│ ├── refind
│ │ ├── icons
│ │ │ ├── arrow_left.png
│ │ │ ├── arrow_right.png
│ │ │ ├── boot_linux.png
│ │ │ ├── boot_win.png
│ │ │ ├── func_about.png
│ │ │ ├── func_exit.png
│ │ │ ├── func_firmware.png
│ │ │ ├── func_reset.png
│ │ │ ├── func_shutdown.png
│ │ │ ├── os_altlinux.png
│ │ │ ├── os_arch.png
│ │ │ ├── os_centos.png
│ │ │ ├── os_chrome.png
│ │ │ ├── os_clover.png
│ │ │ ├── os_debian.png
│ │ │ ├── os_ecomstation.png
│ │ │ ├── os_fatdog.png
│ │ │ ├── os_fedora.png
│ │ │ ├── os_freebsd.png
│ │ │ ├── os_freedos.png
│ │ │ ├── os_funtoo.png
│ │ │ ├── os_gentoo.png
│ │ │ ├── os_gummiboot.png
│ │ │ ├── os_haiku.png
│ │ │ ├── os_hwtest.png
│ │ │ ├── os_kubuntu.png
│ │ │ ├── os_legacy.png
│ │ │ ├── os_linuxmint.png
│ │ │ ├── os_linux.png
│ │ │ ├── os_lubuntu.png
│ │ │ ├── os_mac.png
│ │ │ ├── os_mageia.png
│ │ │ ├── os_mandriva.png
│ │ │ ├── os_manjaro.png
│ │ │ ├── os_mythbuntu.png
│ │ │ ├── os_netbsd.png
│ │ │ ├── os_openbsd.png
│ │ │ ├── os_opensuse.png
│ │ │ ├── os_redhat.png
│ │ │ ├── os_refind.png
│ │ │ ├── os_refit.png
│ │ │ ├── os_slackware.png
│ │ │ ├── os_suse.png
│ │ │ ├── os_ubuntu.png
│ │ │ ├── os_unknown.png
│ │ │ ├── os_win.png
│ │ │ ├── tool_apple_rescue.png
│ │ │ ├── tool_memtest.png
│ │ │ ├── tool_mok_tool.png
│ │ │ ├── tool_part.png
│ │ │ ├── tool_shell.png
│ │ │ ├── tool_windows_rescue.png
│ │ │ ├── transparent.png
│ │ │ ├── vol_external.png
│ │ │ ├── vol_internal.png
│ │ │ └── vol_optical.png
│ │ ├── icons-backup
│ │ │ ├── arrow_left.png
│ │ │ ├── arrow_right.png
│ │ │ ├── boot_linux.png
│ │ │ ├── boot_win.png
│ │ │ ├── func_about.png
│ │ │ ├── func_exit.png
│ │ │ ├── func_firmware.png
│ │ │ ├── func_reset.png
│ │ │ ├── func_shutdown.png
│ │ │ ├── os_altlinux.png
│ │ │ ├── os_arch.png
│ │ │ ├── os_centos.png
│ │ │ ├── os_chrome.png
│ │ │ ├── os_clover.png
│ │ │ ├── os_debian.png
│ │ │ ├── os_ecomstation.png
│ │ │ ├── os_fatdog.png
│ │ │ ├── os_fedora.png
│ │ │ ├── os_freebsd.png
│ │ │ ├── os_freedos.png
│ │ │ ├── os_funtoo.png
│ │ │ ├── os_gentoo.png
│ │ │ ├── os_gummiboot.png
│ │ │ ├── os_haiku.png
│ │ │ ├── os_hwtest.png
│ │ │ ├── os_kubuntu.png
│ │ │ ├── os_legacy.png
│ │ │ ├── os_linuxmint.png
│ │ │ ├── os_linux.png
│ │ │ ├── os_lubuntu.png
│ │ │ ├── os_mac.png
│ │ │ ├── os_mageia.png
│ │ │ ├── os_mandriva.png
│ │ │ ├── os_manjaro.png
│ │ │ ├── os_mythbuntu.png
│ │ │ ├── os_netbsd.png
│ │ │ ├── os_openbsd.png
│ │ │ ├── os_opensuse.png
│ │ │ ├── os_redhat.png
│ │ │ ├── os_refind.png
│ │ │ ├── os_refit.png
│ │ │ ├── os_slackware.png
│ │ │ ├── os_suse.png
│ │ │ ├── os_ubuntu.png
│ │ │ ├── os_unknown.png
│ │ │ ├── os_win.png
│ │ │ ├── tool_apple_rescue.png
│ │ │ ├── tool_memtest.png
│ │ │ ├── tool_mok_tool.png
│ │ │ ├── tool_part.png
│ │ │ ├── tool_shell.png
│ │ │ ├── tool_windows_rescue.png
│ │ │ ├── transparent.png
│ │ │ ├── vol_external.png
│ │ │ ├── vol_internal.png
│ │ │ └── vol_optical.png
│ │ ├── keys
│ │ │ ├── altlinux.cer
│ │ │ ├── canonical-uefi-ca.der
│ │ │ ├── fedora-ca.cer
│ │ │ ├── openSUSE-UEFI-CA-Certificate.cer
│ │ │ ├── refind.cer
│ │ │ └── SLES-UEFI-CA-Certificate.cer
│ │ ├── refind.conf
│ │ ├── refind.conf.old
│ │ ├── refind.conf-sample
│ │ └── refind_x64.efi
│ └── tools
├── grub
│ ├── grub.cfg
│ └── grub.cfg.example
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── loader
│ ├── entries
│ │ └── arch.conf
│ └── loader.conf
├── refind_linux.conf
└── vmlinuz-linux
refind_linux.conf
"Boot with standard options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet "
"Boot to single-user mode" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee quiet single"
"Boot with minimal options" "ro root=UUID=c1822e3c-e037-4445-bdd8-b71778237dee" -
IMac with 10.4.8 hangs on boot
My wife runs a non-profit parenting organization using an iMac (700 MHz, G4, flat panel) with OS 10.4.8. Last Friday on startup, it hung within a few seconds of starting to startup. Kernel panic text covered the screen. Retry to startup gave same result. But will start and run ok in Safe Boot mode although the bootup take very, very long --and can't use search to find files and can't print --maybe other limitations with Safe Boot mode will showup. This past weekend, while running in Safe Boot mode, I was able to backup all of her files onto 8 CDs. I could just reinstall everything beginning with the OS and continue through the various applications (MSOffice, Appleworks, Photoshop Elements, etc.) but I would like to find something that wasn't so drastic to try first. Also I would like to have some idea of what happened so that this would not (hopefully) re-occur. Note --no new software or hardware has been installed in many months except for every Apple update that comes along. It does not have an AirPort card and can access the Internet using ethernet and a DSL connection. Since it started into Safe Boot, I understand that some level of disk repair has taken place. What things should I try before I wipe and reinstall?
iMac G4 700 MHz Flat Screen Mac OS X (10.4.8)Hello --
Thanks for the suggestions. I repaired the disk. I repaired the permissions. And I ran the Apple Hardware Test Disk. The disk was fine. Many, many permissions were repaired. And the Hardware Test Disk found nothing. But, at that point, the "Hang on Boot kernel panic" continued. I then went to the suggestions in Dr. Smokes "Resolving Kernel Panics" article. Using "Cocktail" to flush the caches did the trick. The computer is booting fine again and running faster that before. As an added plus, several other annoying problems and issues have gone away. It seems clear to me that there was a problem in one or more of the caches (I have no clue as to which one) and, therefore, very early in the boot sequence, bad data was drawn upon or an attempt to find data was not possible because of damage to one of the caches. At any rate, Thank you for the suggestions --the computer is fine. (And my wife, on behalf of her non-profit parenting support program, sends you many thanks as well. She also swears that she will now carefully backup her files AT LEAST once a week.) -
[solved] Systemd hangs sometimes on boot with linux-ck
Hi i have linux-ck kernel installes and a Systemd-only init.
Sometimes it hangs on boot and then, instead of starting X / LXDM, drops to a commandline login prompt. It does not happen on every boot and never happend with arch stock kernel so far. I cant't login to search in systemd journal for errors because the keyboard does not work corret, e.g. if I press "o" it writes a "6"
here a shot from last time it happend. In the shot the last messages from Systemd are visible, but sometimes the screen is cleard before the login prompt appears.
Last edited by SiD (2012-09-08 07:51:58)ok I activated syslog-ng and found this in the logs from last boot that not worked
Xorg log
# grep -e EE -e WW /var/log/Xorg.0.log.old
[ 1.932] Current Operating System: Linux sunny 3.5.3-2-ck #1 SMP PREEMPT Mon Aug 27 15:48:39 EDT 2012 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1.942] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1.944] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1.944] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1.948] (II) Loading extension MIT-SCREEN-SAVER
[ 2.133] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
[ 2.133] (EE) NVIDIA(0): system's kernel log for additional error messages and
[ 2.133] (EE) NVIDIA(0): consult the NVIDIA README for details.
[ 2.133] (EE) NVIDIA(0): *** Aborting ***
[ 2.133] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 2.133] (EE) Screen(s) found, but none have a usable configuration.
lxdm log
# cat /var/log/lxdm.log.old
** Message: find greeter (nil)
** Message: find idle (nil)
** Message: add xserver watch
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.4.8-1-ARCH x86_64
Current Operating System: Linux sunny 3.5.3-2-ck #1 SMP PREEMPT Mon Aug 27 15:48:39 EDT 2012 x86_64
Kernel command line: root=UUID=3e32c396-fffb-4e00-b513-08db5c5da177 i915.i915_enable_rc6=1 ro initrd=../initramfs-linux-ck.img BOOT_IMAGE=../vmlinuz-linux-ck
Build Date: 27 August 2012 08:04:39AM
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 3 18:45:01 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
NVIDIA: could not open the device file /dev/nvidiactl (No such device or address).
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Server terminated with error (1). Closing log file.
** Message: exit cb
** Message: free session
arc 1
and in everything log
Sep 3 18:45:03 localhost systemd[1]: Startup finished in 1s 157ms 589us (kernel) + 2s 645ms 840us (userspace) = 3s 803ms 429us.
Sep 3 18:45:04 localhost dbus-daemon[317]: dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:04 localhost dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:04 localhost dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 3 18:45:04 localhost dbus-daemon[317]: dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 3 18:45:06 localhost systemd[1]: lxdm.service: main process exited, code=exited, status=1
Sep 3 18:45:06 localhost systemd[1]: Unit lxdm.service entered failed state.
Sep 3 18:45:06 localhost dbus-daemon[317]: dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:06 localhost dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:06 localhost dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 3 18:45:06 localhost dbus-daemon[317]: dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Seems to me there is a problem loading the Nvidia driver. Don't know if the dbus errors matter ...
EDIT:
Makes sence to me, without a graphics driver loaded X / LXDM can not start.
Last edited by SiD (2012-09-03 17:12:23) -
Refind-efi 0.8.1-1 doesn't boot with custom refind.conf
Recently upgraded to refind-efi 0.8.1-1 and manually ran refind-install.
I usually have the option ¨default_selection "bzImage,vmlinuz"¨ enabled in refind.conf but after some trial and error I found refind wont load the default boot entry with this enabled any more.
I moved
/boot/refind_linux.conf
and
/boot/efi/EFI/refind/refind.conf
and performed a ¨clean¨ refind-install.
If I select the default boot entry, with ¨default_selection "bzImage,vmlinuz"¨ enabled, refind shows the normal boot screen with standard options, but doesn't load the kernel. If I press F2 and select the boot with minimal options (in this case the same as standard options) the kernel boots instantly as expected.
If I use the standard refind.conf-file w/o ¨default_selection "bzImage,vmlinuz"¨ the default boot-entry with standard options works fine.
Anybody able to reproduce?\hbar wrote:Strange... A rEFInd bug perhaps?
I suspect so, but would like to see it reproduced before I file a bug towards rEFInd.
\hbar wrote:When you select the arch entry, is the line that specifies the kernel and its version the same whether the default_selection is set or not?
Yep, the commandline options "ro root=UUID=836e34d6-bc33-4044-a337-372a3d240f49 quiet" plus initrd are the same in the "Booting OS"-screen, whether I select the default "Logo"-entry, or specify which options to boot with via F2.
\hbar wrote:What if you set 'default_selection arch'?
Don't think that's supported, and it doesn't work .
I've also tried "bzImage", "vmlinuz", and "vmlinuz-linux" seperately with the same result.
Should I file a bug now or wait until somebody experiences the same problem? -
[SOLVED] efibootmgr not generating boot loader (rEFInd, etc.) entry.
Hello,
The following command runs without problem or any output. It wouldn't create any entry. Also my refind.conf is not being followed. rEFInd is able to detect kernels and boot fine from /boot
efibootmgr -c -g -d /dev/sda -p 1 -w -L "rEFInd" -l '\EFI\refind\refind_x64.efi'
Information
efibootmgr 0.6.0-1
refind-efi 0.6.8-1
Linux 3.8.4-1-ARCH
sudo efibootmgr
BootCurrent: 000A
Timeout: 0 seconds
BootOrder: 0006,0007,0008,0009,000A,000B,000C,000D,000E,000F,0010,0011,0012,0013
Boot0000 Setup
Boot0001 Boot Menu
Boot0002 Diagnostic Splash Screen
Boot0003 Startup Interrupt Menu
Boot0004 ME Configuration Menu
Boot0005 Rescue and Recovery
Boot0006* USB CD
Boot0007* USB FDD
Boot0008* ATAPI CD0
Boot0009* ATA HDD2
Boot000A* ATA HDD0
Boot000B* ATA HDD1
Boot000C* USB HDD
Boot000D* PCI LAN
Boot000E* ATAPI CD1
Boot000F* ATAPI CD2
Boot0010 Other CD
Boot0011* ATA HDD3
Boot0012* ATA HDD4
Boot0013 Other HDD
Boot0014* IDER BOOT CDROM
Boot0015* IDER BOOT Floppy
Boot0016* ATA HDD
Boot0017* ATAPI CD:
Boot0018* PCI LAN
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
boot refind tools
/boot/EFI/boot:
bootx64.efi icons refind.conf
/boot/EFI/boot/icons:
*** Icons
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
*** icons
/boot/EFI/tools:
drivers shells
/boot/EFI/tools/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/tools/shells:
Shell.efi Shell_Full.efi
cat /boot/refind_linux.conf
"Boot to X" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=graphical.target"
"Boot to Console" "root=PARTUUID=5416f920-35fc-42a8-8a34-564c8c332bfe ro rootfstype=ext4 add_efi_memmap systemd.unit=multi-user.target"
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 3
resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
showtools shell, mok_tool, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
scan_driver_dirs /boot/EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
default_selection "vmlinuz-linux"
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
cat /etc/fstab
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2
UUID=7b92a840-4747-43b7-b2cf-02cbf92afce7 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=72f64fd4-a3f1-424c-8fe3-cdf7751a84e0 /home ext4 rw,relatime,data=ordered 0 2
# /dev/sda1
# UUID=5447-7409 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
UUID=5447-7409 /boot vfat noatime 0 2
# /dev/sda3
UUID=1e11bea5-41db-4969-a8fa-a461734b71ac none swap defaults 0 0
This is a clean install using April 01 ISO with minimal or no modifications. I have tried to follow wiki as precisely as possible. I am not sure what I am missing. Thanks.
EDIT1: Updated and cleaned the post to better reflect current structure and added /etc/fstab.
EDIT2: @swordfish Removed /boot/EFI/arch.
Last edited by donniezazen (2013-04-04 06:37:07)I used March ISO instead of April ISO and it worked flawlessly. There is some problem with April ISO where efibootmgr and UEFI Shell1/2 fail with ASSERT_EFI_ERROR (status = device error).
I have removed both /boot/EFI/boot and /boot/EFI/arch. I now have two entries one on vmlinuz-linux on 1024 Fat 32 partition which works and second one boot/vmlinuz-linux on 20G / partition which fails and takes me to rootfs. Also refind isn't showing UEFI shells that I have in /boot/EFI/tools/Shells.
ls -R /boot
/boot:
EFI initramfs-linux-fallback.img initramfs-linux.img refind_linux.conf vmlinuz-linux
/boot/EFI:
drivers refind tools
/boot/EFI/drivers:
ext2_x64.efi ext4_x64.efi hfs_x64.efi iso9660_x64.efi reiserfs_x64.efi
/boot/EFI/refind:
icons refind.conf refind_x64.efi
/boot/EFI/refind/icons:
### Icons
/boot/EFI/tools:
Shell.efi
# refind.conf
# Configuration file for the rEFInd boot menu
# Timeout in seconds for the main menu screen. Setting the timeout to 0
# disables automatic booting (i.e., no timeout).
timeout 5
# Hide user interface elements for personal preference or to increase
# security:
# banner - the rEFInd title banner (built-in or loaded via "banner")
# label - boot option text label in the menu
# singleuser - remove the submenu options to boot Mac OS X in single-user
# or verbose modes; affects ONLY MacOS X
# safemode - remove the submenu option to boot Mac OS X in "safe mode"
# hwtest - the submenu option to run Apple's hardware test
# arrows - scroll arrows on the OS selection tag line
# hints - brief command summary in the menu
# editor - the options editor (+, F2, or Insert on boot options menu)
# all - all of the above
# Default is none of these (all elements active)
#hideui singleuser
#hideui all
# Set the name of a subdirectory in which icons are stored. Icons must
# have the same names they have in the standard directory. The directory
# name is specified relative to the main rEFInd binary's directory. If
# an icon can't be found in the specified directory, an attempt is made
# to load it from the default directory; thus, you can replace just some
# icons in your own directory and rely on the default for others.
# Default is "icons".
#icons_dir myicons
# Use a custom title banner instead of the rEFInd icon and name. The file
# path is relative to the directory where refind.efi is located. The color
# in the top left corner of the image is used as the background color
# for the menu screens. Currently uncompressed BMP images with color
# depths of 24, 8, 4 or 1 bits are supported, as well as PNG images.
#banner hostname.bmp
#banner mybanner.png
# Custom images for the selection background. There is a big one (144 x 144)
# for the OS icons, and a small one (64 x 64) for the function icons in the
# second row. If only a small image is given, that one is also used for
# the big icons by stretching it in the middle. If only a big one is given,
# the built-in default will be used for the small icons.
# Like the banner option above, these options take a filename of an
# uncompressed BMP image file with a color depth of 24, 8, 4, or 1 bits,
# or a PNG image. The PNG format is required if you need transparency
# support (to let you "see through" to a full-screen banner).
#selection_big selection-big.bmp
#selection_small selection-small.bmp
# Set the font to be used for all textual displays in graphics mode.
# The font must be a PNG file with alpha channel transparency. It must
# contain ASCII characters 32-126 (space through tilde), inclusive, plus
# a glyph to be displayed in place of characters outside of this range,
# for a total of 96 glyphs. Only monospaced fonts are supported. Fonts
# may be of any size, although large fonts can produce display
# irregularities.
# The default is rEFInd's built-in font, Luxi Mono Regular 12 point.
#font myfont.png
# Use text mode only. When enabled, this option forces rEFInd into text mode.
# Passing this option a "0" value causes graphics mode to be used. Pasing
# it no value or any non-0 value causes text mode to be used.
# Default is to use graphics mode.
#textonly
textonly
# Set the EFI text mode to be used for textual displays. This option
# takes a single digit that refers to a mode number. Mode 0 is normally
# 80x25, 1 is sometimes 80x50, and higher numbers are system-specific
# modes. Mode 1024 is a special code that tells rEFInd to not set the
# text mode; it uses whatever was in use when the program was launched.
# If you specify an invalid mode, rEFInd pauses during boot to inform
# you of valid modes.
# CAUTION: On VirtualBox, and perhaps on some real computers, specifying
# a text mode and uncommenting the "textonly" option while NOT specifying
# a resolution can result in an unusable display in the booted OS.
# Default is 1024 (no change)
#textmode 2
textmode 1024
# Set the screen's video resolution. Pass this option either:
# * two values, corresponding to the X and Y resolutions
# * one value, corresponding to a GOP (UEFI) video mode
# Note that not all resolutions are supported. On UEFI systems, passing
# an incorrect value results in a message being shown on the screen to
# that effect, along with a list of supported modes. On EFI 1.x systems
# (e.g., Macintoshes), setting an incorrect mode silently fails. On both
# types of systems, setting an incorrect resolution results in the default
# resolution being used. A resolution of 1024x768 usually works, but higher
# values often don't.
# Default is "0 0" (use the system default resolution, usually 800x600).
#resolution 1024 768
#resolution 3
resolution 1024 768
# Launch specified OSes in graphics mode. By default, rEFInd switches
# to text mode and displays basic pre-launch information when launching
# all OSes except OS X. Using graphics mode can produce a more seamless
# transition, but displays no information, which can make matters
# difficult if you must debug a problem. Also, on at least one known
# computer, using graphics mode prevents a crash when using the Linux
# kernel's EFI stub loader. You can specify an empty list to boot all
# OSes in text mode.
# Valid options:
# osx - Mac OS X
# linux - A Linux kernel with EFI stub loader
# elilo - The ELILO boot loader
# grub - The GRUB (Legacy or 2) boot loader
# windows - Microsoft Windows
# Default value: osx
#use_graphics_for osx,linux
# Which non-bootloader tools to show on the tools line, and in what
# order to display them:
# shell - the EFI shell (requires external program; see rEFInd
# documentation for details)
# gptsync - the (dangerous) gptsync.efi utility (requires external
# program; see rEFInd documentation for details)
# apple_recovery - boots the Apple Recovery HD partition, if present
# mok_tool - makes available the Machine Owner Key (MOK) maintenance
# tool, MokManager.efi, used on Secure Boot systems
# about - an "about this program" option
# exit - a tag to exit from rEFInd
# shutdown - shuts down the computer (a bug causes this to reboot
# EFI systems)
# reboot - a tag to reboot the computer
# Default is shell,apple_recovery,mok_tool,about,shutdown,reboot
#showtools shell, mok_tool, about, reboot, exit
showtools shell, about, reboot, exit
# Directories in which to search for EFI drivers. These drivers can
# provide filesystem support, give access to hard disks on plug-in
# controllers, etc. In most cases none are needed, but if you add
# EFI drivers and you want rEFInd to automatically load them, you
# should specify one or more paths here. rEFInd always scans the
# "drivers" and "drivers_{arch}" subdirectories of its own installation
# directory (where "{arch}" is your architecture code); this option
# specifies ADDITIONAL directories to scan.
# Default is to scan no additional directories for EFI drivers
#scan_driver_dirs EFI/tools/drivers,drivers
scan_driver_dirs EFI/tools/drivers,drivers
# Which types of boot loaders to search, and in what order to display them:
# internal - internal EFI disk-based boot loaders
# external - external EFI disk-based boot loaders
# optical - EFI optical discs (CD, DVD, etc.)
# hdbios - BIOS disk-based boot loaders
# biosexternal - BIOS external boot loaders (USB, eSATA, etc.)
# cd - BIOS optical-disc boot loaders
# manual - use stanzas later in this configuration file
# Note that the legacy BIOS options require firmware support, which is
# not present on all computers.
# On UEFI PCs, default is internal,external,optical,manual
# On Macs, default is internal,hdbios,external,biosexternal,optical,cd,manual
#scanfor internal,external,optical,manual
scanfor internal,external,optical,manual
# Delay for the specified number of seconds before scanning disks.
# This can help some users who find that some of their disks
# (usually external or optical discs) aren't detected initially,
# but are detected after pressing Esc.
# The default is 0.
#scan_delay 5
# When scanning volumes for EFI boot loaders, rEFInd always looks for
# Mac OS X's and Microsoft Windows' boot loaders in their normal locations,
# and scans the root directory and every subdirectory of the /EFI directory
# for additional boot loaders, but it doesn't recurse into these directories.
# The also_scan_dirs token adds more directories to the scan list.
# Directories are specified relative to the volume's root directory. This
# option applies to ALL the volumes that rEFInd scans UNLESS you include
# a volume name and colon before the directory name, as in "myvol:/somedir"
# to scan the somedir directory only on the filesystem named myvol. If a
# specified directory doesn't exist, it's ignored (no error condition
# results). The default is to scan the "boot" directory in addition to
# various hard-coded directories.
#also_scan_dirs boot,ESP2:EFI/linux/kernels
# Partitions to omit from scans. You must specify a volume by its
# label, which you can obtain in an EFI shell by typing "vol", from
# Linux by typing "blkid /dev/{devicename}", or by examining the
# disk's label in various OSes' file browsers.
# The default is "Recovery HD".
#dont_scan_volumes "Recovery HD"
# Directories that should NOT be scanned for boot loaders. By default,
# rEFInd doesn't scan its own directory or the EFI/tools directory.
# You can "blacklist" additional directories with this option, which
# takes a list of directory names as options. You might do this to
# keep EFI/boot/bootx64.efi out of the menu if that's a duplicate of
# another boot loader or to exclude a directory that holds drivers
# or non-bootloader utilities provided by a hardware manufacturer. If
# a directory is listed both here and in also_scan_dirs, dont_scan_dirs
# takes precedence. Note that this blacklist applies to ALL the
# filesystems that rEFInd scans, not just the ESP, unless you precede
# the directory name by a filesystem name, as in "myvol:EFI/somedir"
# to exclude EFI/somedir from the scan on the myvol volume but not on
# other volumes.
#dont_scan_dirs ESP:/EFI/boot,EFI/Dell
# Files that should NOT be included as EFI boot loaders (on the
# first line of the display). If you're using a boot loader that
# relies on support programs or drivers that are installed alongside
# the main binary or if you want to "blacklist" certain loaders by
# name rather than location, use this option. Note that this will
# NOT prevent certain binaries from showing up in the second-row
# set of tools. Most notably, MokManager.efi is in this blacklist,
# but will show up as a tool if present in certain directories. You
# can control the tools row with the showtools token.
# The default is shim.efi,TextMode.efi,ebounce.efi,GraphicsConsole.efi,MokManager.efi,HashTool.efi,HashTool-signed.efi
#dont_scan_files shim.efi,MokManager.efi
# Scan for Linux kernels that lack a ".efi" filename extension. This is
# useful for better integration with Linux distributions that provide
# kernels with EFI stub loaders but that don't give those kernels filenames
# that end in ".efi", particularly if the kernels are stored on a
# filesystem that the EFI can read. When uncommented, this option causes
# all files in scanned directories with names that begin with "vmlinuz"
# or "bzImage" to be included as loaders, even if they lack ".efi"
# extensions. The drawback to this option is that it can pick up kernels
# that lack EFI stub loader support and other files. Passing this option
# a "0" value causes kernels without ".efi" extensions to NOT be scanned;
# passing it alone or with any other value causes all kernels to be scanned.
# Default is to NOT scan for kernels without ".efi" extensions.
scan_all_linux_kernels
# Set the maximum number of tags that can be displayed on the screen at
# any time. If more loaders are discovered than this value, rEFInd shows
# a subset in a scrolling list. If this value is set too high for the
# screen to handle, it's reduced to the value that the screen can manage.
# If this value is set to 0 (the default), it's adjusted to the number
# that the screen can handle.
#max_tags 0
# Set the default menu selection. The available arguments match the
# keyboard accelerators available within rEFInd. You may select the
# default loader using:
# - A digit between 1 and 9, in which case the Nth loader in the menu
# will be the default.
# - Any substring that corresponds to a portion of the loader's title
# (usually the OS's name or boot loader's path).
#default_selection 1
# Include a secondary configuration file within this one. This secondary
# file is loaded as if its options appeared at the point of the "include"
# token itself, so if you want to override a setting in the main file,
# the secondary file must be referenced AFTER the setting you want to
# override. Note that the secondary file may NOT load a tertiary file.
#include manual.conf
# Sample manual configuration stanzas. Each begins with the "menuentry"
# keyword followed by a name that's to appear in the menu (use quotes
# if you want the name to contain a space) and an open curly brace
# ("{"). Each entry ends with a close curly brace ("}"). Common
# keywords within each stanza include:
# volume - identifies the filesystem from which subsequent files
# are loaded. You can specify the volume by label or by
# a number followed by a colon (as in "0:" for the first
# filesystem or "1:" for the second).
# loader - identifies the boot loader file
# initrd - Specifies an initial RAM disk file
# icon - specifies a custom boot loader icon
# ostype - OS type code to determine boot options available by
# pressing Insert. Valid values are "MacOS", "Linux",
# "Windows", and "XOM". Case-sensitive.
# graphics - set to "on" to enable graphics-mode boot (useful
# mainly for MacOS) or "off" for text-mode boot.
# Default is auto-detected from loader filename.
# options - sets options to be passed to the boot loader; use
# quotes if more than one option should be passed or
# if any options use characters that might be changed
# by rEFInd parsing procedures (=, /, #, or tab).
# disabled - use alone or set to "yes" to disable this entry.
# Note that you can use either DOS/Windows/EFI-style backslashes (\)
# or Unix-style forward slashes (/) as directory separators. Either
# way, all file references are on the ESP from which rEFInd was
# launched.
# Use of quotes around parameters causes them to be interpreted as
# one keyword, and for parsing of special characters (spaces, =, /,
# and #) to be disabled. This is useful mainly with the "options"
# keyword. Use of quotes around parameters that specify filenames is
# permissible, but you must then use backslashes instead of slashes,
# except when you must pass a forward slash to the loader, as when
# passing a root= option to a Linux kernel.
# Below are several sample boot stanzas. All are disabled by default.
# Find one similar to what you need, copy it, remove the "disabled" line,
# and adjust the entries to suit your needs.
# A sample entry for a Linux 3.3 kernel with its new EFI boot stub
# support on a filesystem called "KERNELS". This entry includes
# Linux-specific boot options and specification of an initial RAM disk.
# Note uses of Linux-style forward slashes, even in the initrd
# specification. Also note that a leading slash is optional in file
# specifications.
menuentry Linux {
icon EFI/refind/icons/os_linux.icns
volume KERNELS
loader bzImage-3.3.0-rc7
initrd initrd-3.3.0.img
options "ro root=UUID=5f96cafa-e0a7-4057-b18f-fa709db5b837"
disabled
# A sample entry for loading Ubuntu using its standard name for
# its GRUB 2 boot loader. Note uses of Linux-style forward slashes
menuentry Ubuntu {
loader /EFI/ubuntu/grubx64.efi
icon /EFI/refined/icons/os_linux.icns
disabled
# A minimal ELILO entry, which probably offers nothing that
# auto-detection can't accomplish.
menuentry "ELILO" {
loader \EFI\elilo\elilo.efi
disabled
# Like the ELILO entry, this one offers nothing that auto-detection
# can't do; but you might use it if you want to disable auto-detection
# but still boot Windows....
menuentry "Windows 7" {
loader \EFI\Microsoft\Boot\bootmgfw.efi
disabled
# EFI shells are programs just like boot loaders, and can be
# launched in the same way. You can pass a shell the name of a
# script that it's to run on the "options" line. The script
# could initialize hardware and then launch an OS, or it could
# do something entirely different.
menuentry "Windows via shell script" {
icon \EFI\refind\icons\os_win.icns
loader \EFI\tools\shell.efi
options "fs0:\EFI\tools\launch_windows.nsh"
disabled
# Mac OS is normally detected and run automatically; however,
# if you want to do something unusual, a manual boot stanza may
# be the way to do it. This one does nothing very unusual, but
# it may serve as a starting point. Note that you'll almost
# certainly need to change the "volume" line for this example
# to work.
menuentry "My Mac OS X" {
icon \EFI\refind\icons\os_mac.icns
volume "OS X boot"
loader \System\Library\CoreServices\boot.efi
disabled
Thanks for suggesting to try older ISO.
UPDATE:- Most recent ls -R /boot and my refind.conf. Reading over Rod Smith's rEFInd documentation has helped me clean up a little more and set up a good boot manager with automatic kernel detection and shell. I do want to get rid of drivers list that shows itself up along with kernel. Next is to tackle menu entry. Thanks.
Last edited by donniezazen (2013-04-04 06:43:16) -
Macbook Pro 8,2 EFI_STUB loading with rEFInd Failing
Hello fellow Arch users, I've been struggling with trying to get Arch running on my Macbook Pro 8,2 (Early 2011) for the past couple of days and I was hoping that the collective intelligence of the community might be able to help me. I feel that the combination of recent changes in the installation medium, using a Macbook, and my hardware modifications have all converged to make it hard to diagnose what is wrong. First off for hardware I have:
Processor: Core i7 (I7-2820QM)
Integrated Graphics: Intel HD Graphics 3000
Dedicated Graphics: AMD Radeon HD 6750M 1024 MB
Ram: 16G (8Gx2) 1333 MHz
Internal Harddrive: 1Tb WDC WD10TPVT-00HT5T1
Internal Harddrive (in optical drive spot with an OWC Data Doubler): 128Gb APPLE SSD TS128C
I have the SSD setup with only OSX and I planned on installing Arch to the HHD and using rEFInd to boot everything with EFI_STUB. Initially started by trying to install from an external source, but was unable to do so. In the past I had attempted to install windows 7 from an external CD drive only to learn that it is essentially imposible (it would appear to firmware constraint as the Macbook Airs and rMacbook Pros as able to) and I wonder if the same constraint applies for linux live CDs. I tried the "Remove UEFI boot support from ISO" from the UEFI page as well and that did not help. Oddly enough I also was unable to get any usb medium to work as well (both the regular install disk and Archboot, the "Create UEFI bootable USB from ISO" method of the UEFI page) even though it seems that many others have successfully gotten this to work and it should not be affected by my modifications.
At this point I removed the SSD from inside and replaced it with the original super drive. rEFInd will not boot it through efi, but will boot it through BIOS emulation (the partition is listed as windows in rEFInd). From there I followed the standard insertion procedure to get Arch installed (following UEFI_Bootloaders#Linux_Kernel_EFISTUB, Unified_Extensible_Firmware_Interface#Create_an_UEFI_System_Partition_in_Linux and MacBook_Pro_8,1_/_8,2_/_8,3_(2011_Macbook_Pro):
$ cgdisk /dev/sda
512M partition of type EF00, name efi
the rest default type (linux), name root
$ mkfs.vfat -F32 /dev/sda1
$ mkfs.ext4 /dev/sda2
$ mount /dev/sda2 /mnt
$ mkdir /mnt/boot/efi
$ mount /dev/sda1 /mnt/boot/efi
$ mkdir /mnt/boot/efi/EFI/arch/
$ pacstrap /mnt base{,-devel}
$ genfstab -p /mnt >> /mnt/etc/fstab
$ arch-chroot /mnt
$ nano /etc/mkinitcpio.conf
MODULES="..ahci libahci.." #The Macbook page recommends this and I tried it with sd_mod as well based off some previous forum posts.
$ mkinitcpio -p linux
$ cp /boot/vmlinuz-linux /boot/efi/EFI/arch/vmlinuz-arch.efi
$ cp /boot/initramfs-linux.img /boot/efi/EFI/arch/initramfs-arch.img
$ cp /boot/initramfs-linux-fallback.img to /boot/efi/EFI/arch/initramfs-arch-fallback.img
# create /boot/efi/EFI/arch/refind_linux.conf as instructed with the UUID of sda2
$ echo “archy” >> /etc/hostname
$ ln -s /usr/share/zoneinfo/America/New_York /etc/localtime
$ echo “America/New_York” >> /etc/timezone
$ vi /etc/locale.gen
/#en_US and uncomment
$ locale-gen
$ hwclock --systohc --utc
$ echo “KEYMAP=us” >> /etc/vconsole.conf
$ passwd root
$ exit
$ umount /mnt/boot/efi
$ umount /mnt
$ reboot
When I reboot rEFInd does not show the arch partition, but if I boot holding option to bring up the built in partition selection and select the efi partition, rEFInd loads showing the arch linux partition. At this point it loads and gets stuck displaying:
Error: device '' not found. Skipping fsck
Error: Unable to find root device ''.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: cant access tty; job control turned off
[rootfs /]#
I've tried mounting /dev/sda and I simply presents the same error again.
I can confirm the default kernel has EFI_STUB enable as:
$ zcat /proc/config.gz | grep EFI_STUB
displays:
CONFIG_EFI_STUB=y
Any help would be greatly appreciated. I have refined installed on the SSD with OSX and most guides have it installed on the EFI partition with Arch. Is there a different approach I should be taking to set this up with two disks? Thanks.So, I really don't want to hijack this thread, but seeing that I've now 'repaired' my system from the damage mentioned before, I feel I should.
@WonderWoofy:
Well, I very much doubt that this was an issue with my firmware, my reasoning being that it quite simply did not change, the arch-packages however did, quite invasively I may add.
To clarify,
linux (3.6.2-1 -> 3.6.4-1) was the update that broke my systen boot for me.
linux (3.6.4-1 -> 3.6.6-1) since today has again fixed it.
My custom kernel was just vanilla 3.6.0.
So what I did to repair, was to boot up using a live-cd and after discovering I still had my custom-built kernel I copied it back to my EFI-partition, and guess what, it no longer booted!!
to be more precise, it booted, but no display, and after my hdd seemed to have settled, unresponsive/frozen system, hard-reset the only option. The stock kernel(3.6.4-1) never did boot, just froze immediately on load(I could still see the efi-shell).
So, I figured it must be systemd`s fault (because its responsible for loading my system and it was probably no longer working properly with the older kernel version + udev).
My solution was to boot using an older arch-installation cd (in bios-mode!!! again efimode broken) and chroot, update the system, and for now it seems to work again.
So I restate, that arch+efi can be quite unstable at times, even though it could well be my 'luck' to have multiple issues all at once.
To round this off, and maybe benefit the OP, I thought I'd clarify my setup.
I have a single disk, gpt formatted. It holds 7 partitions:
/dev/sda1 -> EFI
/dev/sda2 -> MSRESERVE
/dev/sda3 -> WINDOWS
/dev/sda4 -> DATA
/dev/sda5 -> LINUX
/dev/sda6 -> HOME
/dev/sda7 -> SWAP
Note, I do not have a separate boot partition.
My LINUX partition is laid out in the following way:
/boot -> contains the stock vmlinuz-linux and initramfs-linux.img
/boot/efi -> mountpoint for the EFI partition
fstab entry:
/dev/sda1 /boot/efi vfat rw,noexec,fmask=0113,dmask=0022 0 0
When mounted in such a way, /boot/efi contains:
ls -l /boot/efi/ ->
drwxr-xr-x 8 root root 2.0K Nov 20 14:29 EFI/
ls -l /boot/efi/EFI/ ->
drwxr-xr-x 2 root root 2.0K Nov 20 14:30 arch/
drwxr-xr-x 2 root root 2.0K Nov 20 14:30 archmy/
drwxr-xr-x 2 root root 2.0K Jun 15 19:41 Boot/
drwxr-xr-x 3 root root 2.0K Jun 15 19:25 Microsoft/
drwxr-xr-x 4 root root 2.0K Aug 9 14:48 refind/
drwxr-xr-x 2 root root 2.0K Aug 9 15:09 tools/
Now of interest are the /boot/efi/EFI/refind/ and /boot/efi/EFI/arch folders.
Notice the /boot/efi/EFI/archmy folder is for my custom kernel mentioned above.
Separate folders are one way to use refind's auto-detection mechanism (hence no need to mess with manual boot stanzas) and not have the arch-specific problem of unversioned kernel files.
So /boot/efi/EFI/arch contains:
-rw-rw-r-- 1 root root 13M Nov 21 13:08 initramfs-linux-fallback.img
-rw-rw-r-- 1 root root 4.0M Nov 21 13:08 initramfs-linux.img
-rw-rw-r-- 1 root root 200 Nov 20 14:14 refind_linux.conf
-rw-rw-r-- 1 root root 3.4M Nov 21 13:08 vmlinuz-linux.efi
and /boot/efi/EFI/refind contains:
drwxr-xr-x 2 root root 2.0K Aug 9 14:48 drivers_x64/
drwxr-xr-x 2 root root 4.0K Aug 9 14:48 icons/
-rw-rw-r-- 1 root root 12K Nov 20 14:14 refind.conf
-rw-rw-r-- 1 root root 137K Jun 23 23:26 refind_x64.efi
The two important configuration files are /boot/efi/EFI/arch/refind_linux.conf:
"Boot with Default Options" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap"
"Boot with More Options" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap radeon.modeset=1 iommu=pt radeon.pcie_gen2=1"
In this case I have two seperate kernel-cmd lines, each with different options. I can select which to use, by selecting the 'kernel-entry' I want when refind loads up(each directory, arch/ and archmy/ are a seperate icon)
and pressing'+'. A menu will appear which will show both those lines and I can choose the one I want. This can also be handy when wanting to boot with debugging options.
For instance, the 'radeon-options' are specific to my hw-setup.
Notice that there is no mention of which initramfs file to use, this is handled by refind automatically, BUT can be wonky if not separating kernel versions properly!!!
The only required option is 'root=/dev/sda5' which obviously points at my root partition. (in this case /dev/sda5 -> LINUX)
And /boot/efi/EFI/refind/refind.conf:
timeout 7
hideui banner,label
#icons_dir myicons
#banner hostname.bmp
#selection_big selection-big.bmp
#selection_small selection-small.bmp
#textonly
#resolution 1024 768
use_graphics_for osx,windows
#showtools shell, about, reboot
#scan_driver_dirs EFI/tools/drivers,drivers
#scanfor internal,external,optical
#also_scan_dirs boot,EFI/linux/kernels
dont_scan_dirs EFI/boot
#scan_all_linux_kernels
#max_tags 0
#default_selection 1
These are just the configuration options I have set/unset. Note that some of the commented-out options are still in use, they are just the defaults.
This gives me automatic kernel detection (as long as properly separating things!) and at least when the image itself is working, results in a boot-able system -
Tecra S1 doesn't boot and hangs at (boot) splash screen
Tecra S1 Model PT831E-107EQ-GR
Problems started a month ago. It randomly didn't booted. After some power off/on tries it finally booted and worked properly. Because it happened more often I've bought a new hard drive (Toshiba 40 GB). I've had Acronis True Image and planned to make a disk clone to the new drive. The problem is that a notebook now doesn't boot anymore so I cannot boot it from A CD nor hard drive. It stops at "In Touch..." logo with "Press [F12] for the boot device selection menu" text and doesn't react any key. I tried to boot with no CD, no hard drive - the same. I also connected internal HD using ATA-To-USB adapter - the same. Does it mean that's not a disk problem but motherboard or other components? Is it possible to enter BIOS before boot selection screen?
Regards,
JacekProblem solved. There was a broken PCB under the CPU socket. I've found that pressing with my finger and holding CPU while booting allowed to startup the system while releasing the finger caused system hanging and its total crash. Our local service tried to repair it but with no success. Finally two days ago we've found a working motherboard (a used one) for about 200 USD and now I'm waiting for installing it in the laptop. Th regular price for a new one (about 400 Euro) is too much, but 200 USD is OK. I do like the laptop because of its ports (LPT, RS232). It's used for programming and controlling some older devices. Newer laptops have no LPTs nor RS232s and it's not easy to find a working USB adapter because the software we're using is even from DOS times and has hard-coded IRQs for those ports.
Anyway, I hope it'll back from the service fresh and new, and of course working ;)
Thank you for your tips.
Regards,
Jacek
Maybe you are looking for
-
I am trying to Upgrade to Mavericks but the download never starts.
The upgrade went fine on my 2007 Macbook Pro, but it goes nowhere on my 2007 iMac. The download appears in the dock but the progress bar doesn't fill in and the hover text is "OS X Mavericks – Waiting-" What gives? iMac 7,1 Core 2 Duo 2 GB RAM
-
Sounds weird... but can I import a folder without actually importing?
So I've been used to using Picasa on my PC but recently bought a MacBook Pro and wanted to start using iPhoto. When I selected to import one of the directories of family photos the size of my iPhoto library quickly jumped to over 40gb (about 10,000 p
-
Issue in me9f transaction po printing.
Hi in me9f when try to print a po, there was a z program ZPOPRINT which prints it, i think it is a routine. it is giving a dump. i want information on routines regarding this. Thanks & Regards, Abhimanyu.L
-
hi when I pressed the RESULTS button in PR05 tcode I am getting one error i.e; "ERROR WHILE INITIALIZING TRAVEL FORM". CAN ANY ONE HELP ME TO COME OUT OF THIS ERROR.
-
I have an issue with volfs. volfs is all the time in maintenance state ( I have had no chance yet to reboot system). I tried to use "clear" but it didnt help Hera are some details: # svcs -a /system/filesystem/volfs svcs: -a ignored when used with ar