Linux Fails To Boot After Refind Install

I clean installed Antergos 64bit (GNOME 3) on my iMac, and now need to boot the OS X DVD that came with the computer to format and restore. The ultimate goal is to keep this machine for dual-booting (which I can take care of) since there are simply things I need from both operating systems. If only Antergos or GRUB would boot from the DVD to kick-off the process.


What have you done so far?

It made sense to install rEFInd on this machine, since that was the program that helped OS X boot the Antergos image from my USB drive in the first place.

I followed the steps laid out in the Arch Wiki. First, by using the refind-install command Then used the refind-install --usedefault /dev/sda1 command to "also install rEFInd to the default/fallback boot path".
I shutdown, and booted the Mac up in hopes to catch rEFInd's splash screen, but to no avail. Only the Antergos/GRUB screen, and then into Antergos as usual.
(This began a hopeless cycle of re-installing, and rebooting which lasted quite some time.)

Afterwards, I tried manually installing rEFInd using the following commands from the Arch Wiki:
Quote:
cp /usr/share/refind/refind_x64.efi $esp/EFI/refind/
efibootmgr -c -d /dev/sda -p 1 -l /EFI/refind/refind_x64.efi -L "rEFInd Boot Manager"
Also, I installed the mactel-boot utility from the AUR.

And according to the efibootmgr utility, rEFInd was now first in the boot order:

Quote:
BootCurrent: 0002
BootOrder: 0004,0003,0002,0080,0001,0000
Boot0000* ubuntu
Boot0001* rEFInd Boot Manager
Boot0002* antergos_grub
Boot0003* rEFInd Boot Manager
Boot0004* rEFInd Boot Manager
Boot0080* Mac OS X
Boot0081* Recovery OS
BootFFFF*
After shutdown/power-on, the machine displayed alot of white-colored "clearing node" text, before tragically booting once again into Antergos/GRUB.

I've also read How-to Geek's guide on re-installing OS X on Mac, yet the tutorial never mentions how to restore it from Linux.


Conclusion:

What piece of this puzzle am I missing? Would creating a LiveUSB of OS X be an easier route than this DVD? Is there a GRUB command I'm not aware of that can change the boot order?

I'm almost certain rEFInd is not the only way Linux would be able to boot this OS X DVD, it's just the only way I've known how so far.

I can clearly see the Mac OS X boot option in efibootmgr as Boot0080*, so at least it's being recognized. When Antergos boots to the desktop, the OS X DVD is displayed as "WindowsSupport" if that helps.
I'm out of my element and am at an impasse, your help will be appreciated.

PLEASE & THANK YOU

Hi,

Before installing Linux Mint 17 to the entire HDD of my HP p2 1317cb desktop, it was running a preinstalled windows 8 OEM UEFI. After several failed attempts of dual booting(no grub menu and boots directly to the windows 8) i then decided to do a erase all and install Linux option. Now i have Linux Mint 17.1 working flawlessly, so far. What i want to now do is, dual boot a windows 7 installation alongside my Linux. Please advise on the best way to do this.
Thank You.

Note: Before doing a clean install of Linux i disabled secure boot,enabled legacy, and disabled fast boot.

Hello,

I am new to Linux images (pxe, livecd). I would like to add files to a linux image, like something under etc or var, and have the files be available on the client.
The server I am working on was already configured with a pxe image, and only 2 files are present under the pxe client folder: initrd and vmlinuz. So I am wondering if either of these files contain the dirs /etc, /var, etc..., and how I could add files to them.

To give some background, I have done the same thing in Windows. An image in Windows is typically either boot.img or install.img. You can mount either of these to a folder using the Windows SDK tool imagex.exe /mountrw <img file> 1 <mount point>. From here you can add/remove/modify any files you want. Then commit the changes with imagex.exe /unmount <mountpoint> /commit.

Can someone provide insight to the linux image creation process, which of the files (initrd, vmlinuz/vmlinux, etc...) contain what for the client boot, or something similar to the Windows Image editing process?

I know I'm asking for a range of info, but pointers to any material to help my understanding will be greatly appreciated.

Thanks,
Jon

After creating a bootable usb using Universal USB Installer. I booted up the sytstem (Dell Inspiron N4110) F12 boot on usb, did the install, everything went well until after copying files and then the error message that "The grub-pc package failed to install into /target.. So i continued without a boot loader and now am trying to figure out how to get it back.
Previously i did a perfect dual boot of Kali Linux wherein the Grub boot loader was present. I did however uninstall Kali, reclaim HDD space, and even use EasyBCD to remove Grub(i believe).
Also worth noting is that before this dual boot with pignuy and after uninstalling kali linux i did a complete reinstallation of my windows 7 system using the recovery HD.

Now i would like to know how i could get grub boot loader back onto my system so that i can boot up Pinguy OS. Thanks

Ubuntu 12.04

I installed updates, which included a new kernel. I went to remove one of the older kernels and got:

Code:

jnojr@DEV:~$ sudo apt-get purge linux-image-3.13.0-46-generic
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-3.13.0-46-generic gir1.2-ubuntuoneui-3.0 wireless-regdb iw
  linux-headers-3.13.0-46 crda linux-headers-3.5.0-23-generic lesstif2
  linux-headers-3.5.0-23 libubuntuoneui-3.0-1 thunderbird-globalmenu
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
  linux-image-3.13.0-46-generic*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 197 MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 340656 files and directories currently installed.)
Removing linux-image-3.13.0-46-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
update-initramfs: Deleting /boot/initrd.img-3.13.0-46-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found Windows Vista (loader) on /dev/sda1
Found CentOS release 6.6 (Final) on /dev/sdb1
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found Windows Vista (loader) on /dev/sda1
Found CentOS release 6.6 (Final) on /dev/sdb1
Found memtest86+ image: /boot/memtest86+.bin
error: syntax error.
error: Incorrect command.
error: syntax error.
error: Incorrect command.
error: syntax error.
error: line no: 146
Syntax errors are detected in generated GRUB config file.
Ensure that there are no errors in /etc/default/grub
and /etc/grub.d/* files or please file a bug report with
/boot/grub/grub.cfg.new file attached.
done
Purging configuration files for linux-image-3.13.0-46-generic ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.13.0-46-generic /boot/vmlinuz-3.13.0-46-generic

I have no idea how I'd "ensure there are no errors" in the /etc/grub related files... I have no idea what's supposed to be there. Looking at the line it's complaining about in /boot/grub/grub.cfg.new doesn't tell me anything. How do i find out what it's unhappy about?

The installation of the latest stable on my Lenovo G505s went just fine in UEFI mode but when the installation finished I never reach grub during the bootup process. I put Refind media onto a usb stick and boot into my computer using it after that I tried to follow this guide https://wiki.debian.org/GrubEFIReinstall but I'm having some trouble.

When I start the computer with the "Refind media" it gives me 3 options where the first is

"Boot EFI\debian\grubx64.efi from 510 Mib Fat Volume" If I choose this option it takes me to grub via eufi(?) and then I can get into my computer as usual.

How can I make my computer understand that it should recognize and boot from EFI\debian\grubx64.efi, 510 Mib Fat Volume?

I found https://wiki.debian.org/EFIStub and since my
/boot/efi/EFI/debian looks like; grubx64.efi initrd.img-3.16.0-4-amd64 vmlinuz-3.16.0-4-amd64
I tried the following
Code:

# efibootmgr -c -g -L "Debian (EFI stub)" -l '\EFI\debian\grubx64.efi' -u 'root=UUID=$UUID ro quiet rootfstype=ext4 add_efi_memmap initrd=\\EFI\\debian\\initrd.img-3.16.0-4-amd-64'
efibootmgr: Could not set variable Boot0005: No such file or directory
efibootmgr: Could not prepare boot variable: No such file or directory

Code:

    [ -d /sys/firmware/efi ] && echo "EFI boot on HDD" || echo "Legacy boot on HDD"
    EFI boot on HDD


     apt-get install --reinstall grub-efi

went just fine and I have /dev/sda1 mounted on /boot/efi
but when I try grub-install I get

Code:

grub-install /dev/sda
Installing for x86_64-efi platform.
efibootmgr: Could not set variable Boot0005: No such file or directory
efibootmgr: Could not prepare boot variable: No such file or directory
Installation finished. No error reported.

What is going wrong here?

Code:

    update-grub
    Generating grub configuration file ...
    Found background image: .background_cache.png
    Found linux image: /boot/vmlinuz-3.16.0-4-amd64
    Found initrd image: /boot/initrd.img-3.16.0-4-amd64
    Adding boot menu entry for EFI firmware configuration
    done

Code:

file /boot/efi/EFI/debian/grubx64.efi
/boot/efi/EFI/debian/grubx64.efi: PE32+ executable (EFI application) x86-64 (stripped to external PDB), for MS Windows

but efibootmgr --verbose | grep debian gives me nothing. If I run efibootmgr without grep I get:

Code:

    efibootmgr --verbose
    BootCurrent: 0002
    Timeout: 0 seconds
    BootOrder: 2001,0003,0004,0001,0000,2002,2003
    Boot0000* USB HDD     : SanDisk U3 Cruzer Micro    BIOS(2,500,00)..................3.......1...5........................................
    Boot0001* USB ODD     : SanDisk U3 Cruzer Micro    BIOS(3,500,00)..................;.......9...=........................................
    Boot0002* EFI USB Device   ACPI(a0341d0,0)PCI(10,0)USB(2,0)0311050000HD(1,800,2d5f,55fc859c-5227-4cd5-bd64-a4fd678ba8b6)RC
    Boot0003* SATA HDD    : ST1000LM014-1EJ164                         BIOS(2,0,00).......................................................................
    Boot0004* SATA ODD    : MATSHITADVD-RAM UJ8C2                      BIOS(3,0,00).......................................................................
    Boot2001* EFI USB Device   RC
    Boot2002* EFI DVD/CDROM   RC
    Boot2003* EFI Network   RC

Here is some additonial information which might be relevant.

Code:

    # df -h
    Filesystem                 Size  Used Avail Use% Mounted on
    /dev/dm-1                  9.1G  2.5G  6.2G  29% /
    udev                        10M     0   10M   0% /dev
    tmpfs                      1.4G  9.1M  1.4G   1% /run
    tmpfs                      3.5G   68K  3.5G   1% /dev/shm
    tmpfs                      5.0M  4.0K  5.0M   1% /run/lock
    tmpfs                      3.5G     0  3.5G   0% /sys/fs/cgroup
    /dev/sda2                  237M   35M  190M  16% /boot
    /dev/sda1                  511M  132K  511M   1% /boot/efi
    /dev/mapper/ludo--vg-home  893G  103M  848G   1% /home
    tmpfs                      713M  4.0K  713M   1% /run/user/117
    tmpfs                      713M  8.0K  713M   1% /run/user/1000

Code:

fdisk -l

Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0080BBEA-1B46-4EAE-9471-CC523BFCAD44

Device       Start        End    Sectors   Size Type
/dev/sda1     2048    1050623    1048576   512M EFI System
/dev/sda2  1050624    1550335     499712   244M Linux filesystem
/dev/sda3  1550336 1953523711 1951973376 930.8G Linux filesystem

GPT PMBR size mismatch (13695 != 2009726) will be corrected by w(rite).

Disk /dev/sdb: 981.3 MiB, 1028980224 bytes, 2009727 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: E4A93BB9-2F9C-4487-B090-91B620879E4C

Device     Start   End Sectors  Size Type
/dev/sdb1   2048 13662   11615  5.7M EFI System

Disk /dev/mapper/sda3_crypt: 930.8 GiB, 999408271360 bytes, 1951969280 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/ludo--vg-root: 9.3 GiB, 9999220736 bytes, 19529728 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/ludo--vg-swap_1: 14.4 GiB, 15439233024 bytes, 30154752 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/mapper/ludo--vg-home: 907.1 GiB, 973967720448 bytes, 1902280704 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Hi, I'm pretty new to Linux.

I'm currently working on a project in my Linux Administration class, but have run into a bit of a bump.

I'm tasked with booting Linux (currently using CentOS 7) through the GRUB prompt. I've loaded the kernel, but I'm having an issue with the initrd.

I've tried both of these commands:
"linux /boot/initrd-plymouth.img"
"linux /boot/initramfs-3.10.0-123.el7.x86_64.img"

Neither of these commands have worked. It only returns the message "invalid magic number" for both of the commands. Any ideas on how I can fix this?

Thanks for any help in advance. It should help me understand Linux better!

Hi guys,

For my dual boot system, I first installed window XP followed by Linux fedora 19 and the system has been booting and working fine without
problem.

Now, I would like to remove window XP and install Window 7,
so, I need to remove the partition window XP is on, and then
do a fresh window 7 install. Is there is simple and easy way
of doing this ?

I have window XP, a window 7 and a linux fedora installation disk.

Thanks.

User 247

Hello,

for the reason my PC hangs a long time at the boot line
initrd /boot/initrd.img-3.7.10-antix.7-486-smp
I decided to uopdate it with
update-initramfs -u
but the error
"cryptsetup: WARNING: failed to detect canonical device of /dev/sda2" appear.

I have few questions now:
- how to create a quick initrd
- how to avoid that error?

Your help will be much appreciated.

Just did an update via terminal:

Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
linux-headers-3.13.0-49 linux-headers-3.13.0-49-generic
linux-image-3.13.0-49-generic linux-image-extra-3.13.0-49-generic
Use 'apt-get autoremove' to remove them.
The following NEW packages will be installed:
fglrx-core linux-headers-3.13.0-53 linux-headers-3.13.0-53-generic
linux-image-3.13.0-53-generic linux-image-extra-3.13.0-53-generic
The following packages will be upgraded:
accountsservice apport apport-gtk fglrx fglrx-amdcccle fuse
libaccountsservice0 libfuse2 liboxideqt-qmlplugin liboxideqtcore0
liboxideqtquick0 libspice-server1 linux-firmware linux-headers-generic
linux-image-generic linux-libc-dev oxideqt-codecs-extra python3-apport
python3-problem-report
19 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 227 MB of archives.
After this operation, 490 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y

It downloaded and unpacked files, everything was automated until it asked for my input before replacing the following files:
I backed them up then chose to replace them:

DKMS: install completed.
update-initramfs: deferring update (trigger activated)
Setting up fglrx (2:15.200-0ubuntu0.3) ...

Configuration file '/etc/ati/amdpcsdb.default'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** amdpcsdb.default (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/amdpcsdb.default ...

Configuration file '/etc/ati/atiapfxx'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** atiapfxx (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/atiapfxx ...

Configuration file '/etc/ati/control'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** control (Y/I/N/O/D/Z) [default=N] ? ^[Y

Configuration file '/etc/ati/control'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** control (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/control ...

Configuration file '/etc/ati/signature'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** signature (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/signature ...

Configuration file '/etc/ati/atiapfxx.log'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** atiapfxx.log (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/atiapfxx.log ...

Configuration file '/etc/ati/atiapfxx.blb'
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options a
Y or I : install the package maintainer's version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** atiapfxx.blb (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/ati/atiapfxx.blb ...
Creating backups for the fglrx-core transition
update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken
Restoring backups for the fglrx-core transition
Setting up fglrx-amdcccle (2:15.200-0ubuntu0.3) ...
Setting up linux-firmware (1.127.12) ...
Setting up linux-headers-3.13.0-53 (3.13.0-53.89) ...
Setting up linux-headers-3.13.0-53-generic (3.13.0-53.89) ...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic

Good news! Module version for fglrx.ko
exactly matches what is already found in kernel 3.13.0-53-generic.
DKMS will not replace this module.
You may override by specifying --force.
Setting up linux-headers-generic (3.13.0.53.60) ...
Setting up linux-image-extra-3.13.0-53-generic (3.13.0-53.89) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
update-initramfs: Generating /boot/initrd.img-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.13.0-53-generic /boot/vmlinuz-3.13.0-53-generic
Generating grub configuration file ...
Found theme: /boot/grub/themes/Zorin/theme.txt
Found linux image: /boot/vmlinuz-3.13.0-53-generic
Found initrd image: /boot/initrd.img-3.13.0-53-generic
Found linux image: /boot/vmlinuz-3.13.0-52-generic
Found initrd image: /boot/initrd.img-3.13.0-52-generic
Found linux image: /boot/vmlinuz-3.13.0-51-generic
Found initrd image: /boot/initrd.img-3.13.0-51-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found linux image: /boot/vmlinuz-3.13.0-46-generic
Found initrd image: /boot/initrd.img-3.13.0-46-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
No volume groups found
Found Windows XP Professional x64 Edition on /dev/sda1
done
Setting up linux-image-generic (3.13.0.53.60) ...
Setting up oxideqt-codecs-extra:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Setting up liboxideqtcore0:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Setting up liboxideqtquick0:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Setting up liboxideqt-qmlplugin:amd64 (1.7.8-0ubuntu0.14.04.1) ...
Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
Processing triggers for initramfs-tools (0.103ubuntu4.2) ...
update-initramfs: Generating /boot/initrd.img-3.13.0-53-generic
W: Operation was interrupted before it could finish

Finally the error in red immediately above pops up.
I searched the net and found a site with an article dated back in 2010 that said to fix the error before rebooting or I'd probably not be able to boot to Linux.
Which I'm doing right now, I've not yet rebooted.

How should I recover from such an error before I reboot.

The site had several solutions depending upon other variables, one of which was to delete and/or re-run something. But none of the solutions seemed to fit my case.

I'm running the Zorin OS 9 Theme on top of Ubuntu 14.04 LTS, an AMD PhenomII 64bit 4 core processor on an ASUS MB. The video card is also an AMD/ATI, hence the need for the fglrx drivers listed above.

I'm not sure if the overwriting of the ATI/AMD driver config files shown above are responsible for the error or not. I did nothing that I was aware of that might have caused it, except close another instance of terminal that was runnning, and a libre office writer window.

Any ideas on how to solve this before I reboot would be greatly appreciated.

TIA