HDD boot broken, Linux usb works

<center>
Windows 7 won't boot on HDD
</center><n><p2> When I start it up on HDD, nothing runs. I cant see what's happened because NTFS isn't viewable on Linux. I installed Ubuntu on a hard drive partition and acer boot didn't recognize it as a different device. Pleaseeee
help me!</p2></n>

For problems caused by installing Ubuntu Linux you need to go to the Ubuntu forums. Linux usually installs the Linux utility called GRUB and you must follow the instructions posted by the Linux community when installing Linux to avoid problems with
your installed Windows system.
Start @ www.ubuntu.com and find the Ubuntu forums for assistance with your Ubuntu Linux problems resulting from installing Ubuntu Linux on your system.
It is highly recommended you read the Ubuntu Linux installation carefully before you attempt the installation.
Neither Linux nor GRUB are Microsoft products and they are not a part of the Windows 7 operating system.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Similar Messages

Can all macbooks boot from usb(stick,hdd) and firewire(hdd) an os: linux, win, mac os x, opensolaris, etc

Subject: BOOT FROM EXTERNAL STORAGE DEVICE - After this setup properly
Can all macbooks boot from usb(stick,hdd) and firewire(hdd) an os: linux, win, mac os x, opensolaris, etc?
what about:
Apple MacBook Pro MB133LL/A 15.4-inch Laptop(OLD VERSION) (4GB RAM 120G HD 2.33 GHz Core 2 Duo processor, 15.4" Matte Screen, 4GB memory, 120 GB 7200 rpm hard drive) White

Yes,
Disconnect everything hooked up to the PC except the keyboard, mouse and monitor.
Then use this method to flash the BIOS. It is the safest way to go.
USB Device BIOS Flashing in DOS
DOS Flash (DOSFlash.exe, FlshUefi.cpu) is the DOS-compatible System BIOS flash utility that can be used from a DOS bootable storage device (where "DOS" refers to any of a number of compatible operating systems such as FreeDOS, MS-DOS or DR-DOS). FlshUefi.cpu is the required driver for DOSFlash.exe. To flash the System BIOS from a bootable USB storage device, you will need to copy the contents of the DOS Flash folder to the USB device, boot the PC from the USB device, and execute the DOSFlash application. To see a more complete description of the DOS flash utilities, view DOSFlash.txt located in the DOS Flash folder. This folder also contains the required binary image of the BIOS. The binary image file is named xxx_MMmm.bin where "xxx" is the BIOS family, "MM" is the major version number, and "mm" is the minor version number. This file can be copied to the root directory of any USB removable medium for use with the F10 setup "Flash System ROM" option
View Contents of DOS Flash Folder
The links on this post don't work. I copied the section from the BIOS flashing instructions for the specific section you need.
Paul

LINUX USB install (NOT LIVE) that works on a Mac and PC

I've installed linux on a USB and I can use it on any pc I want. I just change the boot device and I'm in my private linux os with all my stuff. But if I buy a macbook can I use it on a mac, how?
There are planty tutorials how to make a LIVE USB (boots using ram - like a LVIE CD), but nowhere I can find how to but an actuall install of linux from USB on a mac that also works on a PC, is that possible, it's just a key combination or a boot order in bios or is not posible at all?
I never had a mac in my life, forgive me if this is a simple "Just hit F2, stupid!" question.
Again no ISO, no LIVE, I want the install to have my stuff, I don't want to install flash and my stuff everytime I boot.
Thanks in advance.

You can use a Linux Live USB or CD on any PC is because the hardware drivers are freely availalbe.
On Mac's that's just not the case, until later on someone who gives a ratts behind and runs Linux on a Mac, and is a command line guru can get them and publish them for others to use.
Also Mac's have all sorts of other drivers to control the fans, etc., that if one tries to boot off Linux causes issues.
Installing Linux on a Mac is a big no no, unless your a computer science graduate, because Linux installs it's Swap folder into the hidden EFI partition and reformats the Macintosh HD partiiton with OS X on it and other horrors as it's not a generic PC like people think it is.
You can install Linux into a virtual machine like virtualbox, then OS X is still controling the hardware and virtualbox is taking care of the under the hood things
Want to try Linux?, read this

Installation of Windows 7 via USB External HDD (Boot Camp Assistant)

How do I mount Windows 7 Ultimate disk image (.iso) onto my USB external HDD so that I can boot using that USB external HDD? I have tried reEFIt, but it doesn't work for me. It may be because I did something wrong. I would appreciate a comprehensive guide. Thanks.

i suspect you haven't prepared the USB drive as a boot volume.
You can absolutely do this. It is detailed on CNET in the following article: http://reviews.cnet.com/8301-31012_7-20020513-10355804.html

[SOLVED] Booting Arch off USB HDD fails - can't mount real root device

I've installed Arch on the internal HDD (sda) of my laptop, and I attempted to install a second copy of Arch on partition sdb3 of an external USB HDD. sdb3 is a primary partition that I had prepared beforehand with gparted and outfitted with the reiserfs filesystem. I skipped section 3.2 (manually prepare hard drives) of the Arch installer. There was no problem with section 3.3 (manually configure filesystems and mountpoints); I put all of / in sdb3. Installing packages and configuring the system also went without a hitch.
I wanted to boot this new install of Arch via the boot menu of GRUB that was installed in the MBR of sda with my primary install of Arch. On the new install, I first did go through section 7 (install bootloader), thinking I would want to install GRUB in the root sector of partition sdb3 (not in the MBR of sdb where the GRUB of MintKDE resides, a boot menu that I want to keep) but that failed, so I then picked "no bootloader to be installed". With that I exited the new install, since it appeared to have gone to completion.
I then copied the appropriate stanza in the /boot/grub/menu.lst of this new Arch install to the /boot/grub/menu.lst of my primary Arch install on the internal HDD of my laptop.
This stanza reads as follows:
# (3) Arch Linux on WDPP60 blue (sdb3)
title Arch Linux on WDPP60 blue (sdb3)
root (hd1,2)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/191cc027-43ce-443b-8846-f265d60555ec ro
initrd /boot/kernel26.img
However, I'm not able to boot the new Arch install when I pick this entry from the GRUB menu list. The new install starts booting, finds sda but not sdb and stops with the following errors, dropping me to a recovery shell:
Root device /dev/disk/by-uuid... doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid...'
mounting /dev/disk/by-uuid... on /new_root failed: No such file ...
ERROR: Failed to mount the real root device.
Running "mount -t reiserfs /dev/sdb3 /new_root" at the ramfs prompt also fails.
I've tried a number of edits of the menu.lst stanza from the grub> command prompt, such as adding rootfstype=reiserfs, replacing root=/dev/disk/by-uuid..etc. with root=/dev/sdb3 (booting then fails with "/dev/sdb3 No such file"), using "initrd /boot/kernel26-fallback.img" etc., but booting always fails at the same stage with equivalent error messages.
I have no trouble booting half a dozen other Linux/BSD distros that reside on two different external USB HDD's by the same method, i.e. choosing an entry from the GRUB boot menu of my primary Arch install, after I placed the appropriate stanza in its /boot/grub/menu.lst.
How can I get this new Arch install to boot?
Last edited by RobF (2010-05-17 23:03:27)

Yes, this was in fact the solution. I stumbled upon it in this thread:
http://bbs.archlinux.org/viewtopic.php?id=65844
When one wants to boot from a USB mass storage device, the initrd needs to include the modules for accessing USB devices, and in Arch this is accomplished by adding "usb" to the HOOKS array. I simply reinstalled Arch to the USB HDD and in the system configuration step now edited /etc/mkinitcpio.conf by adding the "usb" item. Adding "rootdelay=10" and/or "rootfstype=reiserfs" to the kernel line in the appropriate stanza in Arch's /boot/grub/menu.lst wasn't necessary in this case. I left the stanza exactly as I posted it above.
Thanks for your input.

[solved] Thinkpad x61 w/ /boot on external USB can't see internal hdd

Hi all,
EDIT: Fixed it. I had to boot the install media and re-run mkinitcpio -p linux. Not sure if I forgot to do that the first time or if something changed...
I have my /boot partition on an external USB key. I installed grub on that key. My main disk is supposed to be encrypted, and is internal in my Thinkpad x61. When I boot with this setup, grub can't find the system disk. I get dumped to a recovery console, and lsblk just shows the USB key.
If I plug the internal drive in via a USB-SATA converter, everything works as it is supposed to.
It seems like when the thinkpad boots from the USB key it isn't turning on the internal drive or making it available to linux. Has anyone seen something like this?
When I boot the arch installation media from USB I can see the internal drive right away. Is there a way to figure out what the installation boot is doing that I'm not on my regular system?
Thanks in advance,
Lefty
Last edited by LeftyAce (2014-01-05 05:06:43)

Yup, sudo makes all the difference.
[warnec@chakra-desktop ~]$ sudo lsusb
Hasło:
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 003: ID 1532:0109 Razer USA, Ltd Lycosa Keyboard
Bus 007 Device 002: ID 046d:c049 Logitech, Inc. G5 Laser Mouse
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 005: ID 03f0:2904 Hewlett-Packard
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[warnec@chakra-desktop ~]$
My /etc/group:
root::0:root
bin::1:root,bin,daemon
daemon::2:root,bin,daemon
sys::3:root,bin
adm::4:root,daemon
tty::5:
disk::6:root
lp::7:daemon
mem::8:
kmem::9:
wheel::10:root
ftp::11:
mail::12:
uucp::14:
log::19:root,warnec
locate::21:warnec
smmsp::25:
http::33:
games::50:
network:x:90:warnec
video:x:91:warnec
audio::92:warnec
optical::93:hal,warnec
floppy:x:94:hal,warnec
storage:x:95:hal,warnec
scanner:x:96:warnec
power:x:98:warnec
nobody::99:
users::100:warnec
dbus:x:81:
hal:x:82:
policykit:x:102:
camera:x:97:warnec
avahi:x:84:
cdemu:x:103:
mysql:x:89:
I guess I should add "warnec" after "daemon"?

A40: Booting from external USB HDD

Hi guys.
Who could help me? The problem: I've recently bought USB 2.0 HDD case, the device is working properly and everything is OK, but I can't boot from it.
The model is A40 and USB FDD boot option is available, how could I go around it and make my laptop boot from USB HDD?
Thanks in advance.

Hello
There is no problem at all because this possibility is absolutely not possible. There is no way to do this.
Dont compare external FDD and HDD. They are two different external devices.
Bye

Windows 7.5 phone not recognized. Charges but no usb connection. USB works with HDD, Flash, 3G modem, Iphone, just no the Win 7.5 phone. Using 27" IMac with Lion.

When I connect windows Phone (HT7 using Windows Phone 7.5 (tried 2 phones) usb wont recognise it. Charges but no usb connection. USB works with HDD, Flash, 3G modem, Iphone, just no the Win 7.5 phone. Using 27" IMac with Lion.
I am running VMWare fusion when I connect any USB device Lion prompts to connect Windows or MAC. Both work for many devices. When I plug in the phone Lion simply does not respond.
Peter

Also.... my phone works and can do everything fine when not plugged in.. I just can't get my computer or others to recognize the darn thing when plugged in!

How to boot Linux USB Hard Disk from Windows Machine?

*Dears,,*
I have XP windows Machine . . .
My laptop is Qosmio F20 155
I need to boot Linux USB Hard Disk .
I tried to enter setup menu to arrange the boot perority to make The USB Hard Disk FIRST but i cannot enter setup menu
Please, help me ASAP
*Many Thanks & Regards,,*
Message was edited by: eng_mohammedmostafa

*Dear,,*
FYI , , ,
We have another laptop (VAIO) and we can enter BIOS and edit the priority boot and it run successfully . . .
But in laptop (Toshiba) We can't make it.
*Thanks & Regards,,*
*Eng Mohammed Mostafa*

Tecra M2: Can I Boot from External USB/Firewire-HDD ???

Hi All,
how can I boot from an external USB Drive ?
The Bios 1.20, 03/15/2004 doesn't seem to support this on my Tecra M2.
I have an Maxtor 300Gig external HDD which can be connected via Firewire or USB. Usually I am using an Firewire PCMCIA-Card to connect this HDD, which has 3 partitions on it.
Would it also be possible, to Boot via PCMCIA-Firewire ?
Many thanks in advance.
Lembong

Hi
As far as I know its not possible to boot from a USB HDD. I know that in some cases its possible to boot from compatible USB FDD and CD/DVD drives but note from HDD.
This theme was disused a lot of time here in the forum.
Please check this other posting:
http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=4534&messageID=14824#14824
http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=8963&messageID=31325#31325
Regards

Failed booting from external usb hdd

Hey Community!
I struggle at backing up my arch linux operation system. I found this instruction but for newbies as me it seems to be a little bit hard to follow:
Full_System_Backup_with_rsync
The backup itself with rsync and the installation of GRUB bootloader seemed to be successful, but if I plug in the external hdd in another PC and boot from it, GRUB fails with ERROR 21.
I think, that my menu.lst is somehow incorrect. What I did:
full rsync to /mnt/usbHDD (mounted from /dev/sdb1)
my external hard disk is partitioned like that:
|| 160 gb ext4, sdb1 | UNUSED rest ||
blkid gives me that:
/dev/sda1: UUID="8f7f3e77-8acb-4724-862a-6c9678cadd29" TYPE="ext2"
/dev/sda2: UUID="c21b9563-ebf9-4b28-882d-fd8322693627" TYPE="swap"
/dev/sda3: UUID="78aad592-62d5-4752-8e04-50f17ff19705" TYPE="ext4"
/dev/sda4: UUID="b5cba3a9-5009-485f-b53c-6be526b51f55" TYPE="ext4"
/dev/sdc1: LABEL="storageHDD" UUID="49afd07d-1c11-448f-9b06-f7477cbe1b7c" TYPE="ext4"
The /etc/fstab of the original OS is:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=78aad592-62d5-4752-8e04-50f17ff19705 / ext4 defaults 0 1
UUID=8f7f3e77-8acb-4724-862a-6c9678cadd29 /boot ext2 defaults 0 1
UUID=b5cba3a9-5009-485f-b53c-6be526b51f55 /home ext4 defaults 0 1
UUID=c21b9563-ebf9-4b28-882d-fd8322693627 swap swap defaults 0 0
The /boot/grub/menu.lst of the original OS is:
# general configuration:
timeout 5
default 0
color light-blue/black light-cyan/blue
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/78aad592-62d5-4752-8e04-50f17ff19705 ro
initrd /initramfs-linux.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz-linux root=/dev/disk/by-uuid/78aad592-62d5-4752-8e04-50f17ff19705 ro
initrd /initramfs-linux-fallback.img
The /etc/fstab of the backed up (on hdd) OS is:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
UUID=78aad592-62d5-4752-8e04-50f17ff19705 / ext4 defaults 0 1
UUID=8f7f3e77-8acb-4724-862a-6c9678cadd29 /boot ext2 defaults 0 1
UUID=b5cba3a9-5009-485f-b53c-6be526b51f55 /home ext4 defaults 0 1
UUID=c21b9563-ebf9-4b28-882d-fd8322693627 swap swap defaults 0 0
The /boot/grub/menu.lst of the backed up (on hdd) OS is:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz-linux root=/dev/sdb1 ro
initrd /initramfs-linux.img
# (1) Arch Linux
title Arch Linux Fallback
root (hd0,0)
kernel /vmlinuz-linux root=/dev/sdb1 ro
initrd /initramfs-linux-fallback.img
I don't have a clue what to change, since it is not clearly specified in the wiki...I followed exactly the instructions in the wiki, besides the include and excludes for rsync but that doesnt really matter
Appreciate your help
Last edited by athal (2012-06-25 21:09:16)

You should adapt the menu.lst of the backed up OS like this:
# (0) Arch Linux
title Arch Linux
root (hd1,0)
kernel /boot/vmlinuz-linux root=/dev/sdb1 ro
initrd /boot/initramfs-linux.img
explanation:
- Your root should be (hd1,0) because the external disc is the second hard disc (assuming root=/dev/sdb1 is correct).
- The kernel and initrd line should have /boot, because you don't have a seperate boot partition.
Also, you didn't adapt your fstab of the backed up hard disk. In particular, you have to remove the entries for /boot, /home and swap. The entry of root file system is also wrong, because you still have the old UUID in it:
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sdb1 / ext4 defaults 0 1
Finally, I think not following the excludes in the wiki will also cause problems.

Tutorial - How to triple boot OSX, Linux and Windows 8.1 with a shared Data Partition without any third party Win / OSX softwares

This is not a question, but rather a personal guide that has proved to be running successfully.
I would like to thank numerous sources, including Christopher Murphy's suggestions at:
Re: Repairing Boot Camp after creating new partition
Before proceeding, there are certain concepts needs to know:
Why Boot Camp does NOT allow further partitioning of drives after Windows has installed?
Answer: Because the way Apple configures the Mac to be recognized as non UEFI capable system on Windows.
Quote from Christopher Murphy based on the above line:
However, Windows on Macs right now use CSM-BIOS mode in Mac firmware that presents BIOS to Windows rather than EFI. Windows thinks it's on a BIOS computer, and therefore mandates the use of MBR for boot disks, rather than GPT. So that's why we have this hybrid MBR+GPT approach on Mac with Windows on it. You inherit the limitations of MBR, which is four primary partitions.
So what does it means?
It means that OSX + EFI + Recovery HD + Boot Camp partition = 4 primary partitions and thus any attempt to modify the disk will render booting issues of either system.
For more info on GPT (GUID Partition Table disks VS Master Boot Record or MBR in short, you may visit: http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx)
So, how to overcome it?
The general guideline is to install ALL GPT ready OS first then create a Data partition, before installing Windows (Which is again, NOT supported GPT due to EFI configuration by Apple where end-users are not able to modify it).
Interestingly, since Mac Pro 2013 Late supports only Windows 8 and above, thus it is not known if this CSM-BIOS applies to it or not.
Do take note that GPT disks in Windows can only be booted when the system meets the 2 requirements:
http://msdn.microsoft.com/en-us/library/windows/hardware/dn640535%28v=vs.85%29.a spx#gpt_faq_win7_boot
1) Windows x64 version (Which is a must for newer Macs. If you cannot go to Boot Camp 5, then you need Windows 7 x86 or 32bit version)
2) UEFI system. However, Windows sees all Macs (With the possibility of Mac Pro 2013 Late is an exception. To be determined) as BIOS, or rather NON-UEFI system.
In short, booting on GPT disks is not possible for Mac in Windows.
Summary,
It is tested that a combination of the following will not work:
- OSX + Windows + Linux
- Windows + OSX + Linux
- Windows + Linux + OSX
Usually it can create the system un-bootable or OSX refused to install due to the system does not recognize such partitions and / or Disk Utility refused to format a free space. An example screen-shot is provided below:
The error message is shown as
Title: "Failed to erase volume" Message: "Failed to wipe volume, as an error occurred: MediaKit has reported that the device does not have enough free space to execute the requested operations."
The second thing is about the preparations we need.
1) 1X Windows 7 or 8 DVD or USB thumbdrive
1A) If you uses a DVD to install, you will need another thumbdrive to load the BootCamp drivers for Windows as well as may requires an external DVD drive for newer Macs
2) 1X Linux DVD of your choice. Personally I choose Fedora 20.
So ready? Let's go.
1. Using Disk Utility, shrink the OSX's partition size to what is needed. For me, I give OSX 150GB. Do NOT create any new partition.
Disk Utility should see something like below whereby only OSX partition is left with desired disk space. The remaining space are to be unused disk space for the moment.
Note: Click on the top most item that should start with the size of your HDD / SSD. Then clicked on "Partition" and specify the desired OSX size. Hit "Apply" after that.
2: Download Boot Camp drivers only via Boot Camp Assistant. The USB thumbdrive shall be used later after Linux's installation.
Boot Camp Assistant should see this:
I have only selected "Download latest Windows Support Files from Apple"
3. Insert Linux DVD, reboot Mac into EFI mode (The left most first "EFI mode").
Note 1: Before rebooting, please plugged in an Ethernet adapter because Wi-Fi drivers is not installed.
Note 2: For Thunderbolt adapters, it must be plugged in before reboot as hot-swapping is not supported under Linux. More on the tips at the end of this article.
Note 3: Press and hold "Option" after the screen turns black. Release Option key after you see the image as below:

For the unfortunate part that did not make it on time to edit the images:
9. Install the Windows Support software from your CD/USB drive to gain full functionality of your computer. Reboot and go to Windows again.
Note 1: You may choose to eject disc at this point of time. For Apple SuperDrive users, you will need to wait until the drivers (i.e. Boot Camp support files) is installed and rebooted before ejecting is reasonably possible (As I failed to figured out how to right click without the drivers)
Note 2: Unlike Windows 7 on KBase article TS4599 Keyboard/trackpad inoperative, black screen, or alert messages when installing Windows 7, USB stick can be plugged in after the Windows installation is done. This is because Windows 7 (And probably Windows 7 with SP1 DVD) does not have a built in USB 3 drivers when it was released back in 2009 where USB3 has not arrived then.
Note 3: Due to TPM, Bitlocker is not supported without the use of thumbdrives.
10. Using Disk Management to determine the given drive letter for the DATA partition (DO NOT DELETE and RECREATE partition or else you can goodbye to booting Linux and OSX). Disk Management will not allow you to format it as exFAT / FAT32 in graphical way.
Note: You may remove or modify some of the disk letters in Disk Management. However, do NOT remove / modfify the drive letter for the partition with 200MB size in HFS. This is because it will disallow booting of Linux and neither could Windows nor OSX can do anything EXCEPT to reinstall Linux only.
11. Open Command Prompt in Administrator Mode (Important!!), and key in the following command:
format F: /FS:exFAT
Give this volume a label after it has successfully formatted before hitting "Enter" again.
Note: Mine Data partition was assigned as F drive. Please make necessary adjustment to "F:" should your Data partition is assigned to other letters.
12. After that, Setup your Data partition structure as you like.
Tip: Minimally create the important folders such as:
- Music
- Documents
- Movie (Videos)
- Downloads
- Pictures
All these folders are commonly used by the 3 OSes. I do NOT recommend changing of /home (OSX and / or Linux) and / or user home directory (Windows) either partially or as a whole.
This is because of compatibility issue.
On a side note, iTunes Media Library used in OSX and Windows are NOT able to be use interchangably due to hard-coded path used.
13. Useful troubleshooting in Fedora / Linux:
With references to these:
http://chaidarun.com/fedora-mbp
http://anderson.the-silvas.com/2014/02/14/fedora-20-on-a-macbook-pro-13-late-201 3-retina-display/
http://unencumberedbyfacts.com/2013/08/16/linux-on-a-macbook-pro-101/
I would like to highlight a few important points:
1) Wi-Fi driver:
http://rpmfusion.org/Configuration
Note 1: The sound driver should be installed at Out of Box Experience. However, the Wi-Fi is not.
Note 2: Install both free and non-free repository. By the way, some other software like VLC can only be found after the Free Repository is installed.
Search for "akmod-wl" in Gnome-Package-Installer in order to install Wi-Fi drivers
Note 3: For those who do not have Ethernet adapters and their Mac does NOT have a built-in Ethernet port, it is recommended to get one. This is because Fedora 20 does not have a good support for iPhone USB tethering. Unsure for Andriod / Blackberry / Windows Phone users.
2) Grub Menu:
It will show several options to boot into OSX, even of the capability to boot into x86 or x64 mode. However, neither of them is bootable except Linux and the rescue.
Hence, it is recommended to remove the items by hand in this file:
/boot/efi/EFI/fedora/grub.cfg
Command to be used:
"sudo gedit /boot/efi/EFI/fedora/grub.cfg"
Parts to be removed:
- For any extra kernels, delete the target entry by locating the line "menuentry" under "/etc/grub.d/10_linux" sector to one line above the next "menuentry".
It is recommended to keep one main kernel, and one recovery at the minimal.
- For other OS, delete all the entry (Since neither it can works) under "/etc/grub.d/30_os-prober" sector without removing the lines starts with ###.
Auto Mount exFAT partition:
- After installing extra packages for exFAT support (Since it is not supported by Fedora 20 from a default installation), you may wish to edit "/etc/fstab" in order to mount the exFAT partition during boot time.
Command to be used:
"sudo gedit /etc/fstab"
Add the following line in gedit:
UUID=702D-912D /run/media/Samuel/DATA exfat defaults 1 2
Note 1: For DATA partition, OSX & Boot Camp partition, Fedora defaults mounts under: "/run/medua/<Username with case sensitive>/<Partition Label Name>"
Note 2: UUID is unique ID. You can find out the UUID by:
Step 1: First determine the DATA partition number:
"sudo gdisk /dev/sda"
Step 2: Determine the UUID of this partition number:
"sudo blkid /dev/sda8"
Reference 1: http://manpages.courier-mta.org/htmlman5/fstab.5.html
Reference 2: http://liquidat.wordpress.com/2007/10/15/short-tip-get-uuid-of-hard-disks/
3) Overheating CPU
Solution is to issue the following command in Linux terminal: su -c "echo -n 1 > /sys/devices/system/cpu/intel_pstate/no_turbo"
4) System resumes immediately after suspend
Solution is to issue the following command in Linux terminal: su -c "echo XHC1 > /proc/acpi/wakeup"
5) What does not works well out of box:
- Both GNOME and KDE's fonts are too small to be readable for out of box experience. Additional configuration is a need. (Some of the info can be found on "More Tips" later)
- Thunderbolt hotplugging is NOT supported under Windows and Linux so far. Neither FaceTime HD camera works as well.
- The red light in Headphone jack is always on. I do not have luck in switching off the light without losing the sound.
Note 1: It is determined that the module "snd_hda_intel" is used by both cards (HDMI and normal output)
Note 2: It is also known that blacklisting it can switch off the redlight at the price of muting the system.
Note: Based on this article, http://support.apple.com/kb/TS1574
A Mac (Except Mac Pro) needs servicing when there is a red light while the system fails to detect internal speakers. However, this article does NOT applies to this issue.
5A) More Tips:
Install gnome-tweak-tool for more customization
Search for: "gnome-package" to install:
Install Gnome Package Installer for advanced package repository
Install Gnome Package Updater for advanced updates to be install (Whereby Fedora's App Store alike might not show the relevant updates)
14. Verify if disk is still GPT:
Use Gdisk to determine if the disk is pure GPT:
http://ubuntuforums.org/showthread.php?t=1742682
Command: sudo gdisk -l /dev/sda (The entire hard drive)
You should see the MBR is "Protective" instead of anything else.
15. Congrats, the system is ready for triple boot. (I forgot to eject my Windows DVD when the photo was taken)
Note 1: You cannot set the default startup disk in Linux due to the lack of Boot Camp Control Panel in Linux.
Neither is changing startup disk recommended in Windows due to the inability to display correctly.
For me, I click "Cancel" whenever I am on this tab (Feel free to make other Boot Camp adjustments in other tabs).
Only OSX I know that can show the startup disk options correctly.
Note 2: For some reason, OSX likes to auto mount the EFI partition everytime it boots up. It is not known to have any issue for ejecting other disks or mounting disks via Disk Utility.
Note 3: It is not determined if any Firmware or System upgrades will cause issues. It is only known that all 3 OS's regular updates should not be an issue.
System Updates excludes Mac OSX 10.9.3 updates to OSX 10.9.4 type as I had done it on a OSX 10.9.4 Mac or Windows 8.1 to Windows 8.1 Update 1 since my Windows DVD comes with Update 1.
System Upgrades refers to OSX Mavericks to Yosemite, Fedora 20 to Fedora 21, Windows 8.1 Update 1 to Windows 8.2 / Windows 9 for that matter.
Note 4: Reset SMC and / or PRAM will NOT affect your ability to boot any of the OS (OSX, Recovery HD, Fedora & Windows 8)
Yup, that is it!

Unable to boot new Linux installation on Lenovo G400

I am having problems installing Linux Mint 16 to a Lenovo G400 that I recently purchased here in China. I have an older Lenovo that I have had for several years, and have been quite pleased with it so I thought I would get another. I gave up on Windows several years ago, and have been running exclusively Linux, mostly Ubuntu or Mint, ever since. I have heard and read things about how Microsoft seems to be fighting back to restrict the spread of Linux, so I took a Live USB stick of Linux Mint 16 so I could see if start it with any machine that I was interested in.
The machine I tested my USB stick on worked fine, so I sent them to the warehouse to get a fresh one in a box. My problems started when they came back from the warehouse with another model, newer, with a faster processor, and pre-installed Linux. I entered the data required to complete the setup, and played around with the Linpus OS a bit before deciding to take that machine instead of the other. My thinking was that I could replace Linpus with Mint later. I did not try booting from my USB stick before agreeing to take this machine.
Later, after trying out Linpus and deciding I had a strong preference for a Debian derivative, I had trouble setting the boot order, but resolved that by finding a copy of the user guide in English. When I tried to boot from the USB, the first thing I noticed was that anything I tried to run from a Live USB stick would not function in standard or default mode. The menu would come up, I would select the default or standard mode, and the system would start to load but a few seconds later the screen would go black. The USB continued to flash for a while but the screen stays black.
At first I noticed this problem with Gparted, which would not run in default or failsafe mode, but does run in safe graphic mode. Similarly, with Mint 16, the live USB will only start in compatibility mode. Later there were several other live systems that I have tried with similar results. Almost all of the live systems I tried ran in their equivalent of the compatibility mode. The one exception to that was Boot-Repair-Disk, which I could not get to work at all in the 64-Bit edition. The 32-Bit edition did work, in their equivalent of compatibility mode, but it told me I needed the 64-Bit Edition because EFI was detected.
When I succeeded in getting the Gparted and Mint 16 live USBs to function in non-default modes I decided to go ahead with my repartitioning and installation plans. This may have been my second mistake. Maybe I should have taken this machine back, but I didn't.
With my Live USB of Gparted running in Safe Graphic mode, I found 6 partitions on the HDD: sda1 is FAT 32 and labeled boot; sda2 is an unknown file system and labeled bios_grub. Both of these partitions are 500 Mb, and I left them alone. I also left sda3 untouched, which is labeled linux-swap. Sda4, sda5 and sda6 I re-sized and re-formated to use as two / partitions and a shared /home.
I then installed Mint 16 in sda4 with sda6 as home. I left the GRUB intallation in the default setting, sda. The installation seemed to go alright, but when I try to boot I just see Lenovo and then the screen goes black. It does seem like the system may be loading and I just can't see it, but that is only a guess. I don't see anything that looks like the GRUB screen and so there is no way to use compatibility mode. Using Gparted from a Live USB suggests that the installation worked and there are files there.
I have searched on the web and have been unable to find anything that helps. Obviously, I am not an expert, but I have installed Linux quite a few times and never experienced anything like this. But then I am used to starting from a clean disk.
I am very tempted to delete the two partitions that I left in place and try an installation like I am used to doing. But I do not know anything about EFI, and my hard drive is listed in BIOS setup as an EFI HDD Device, so I don't know if my machine would still work if I delete these partitions.
So I am very much in need of some advice on this and I wonder if anyone can please offer me some guidance. And perhaps I should add a few more details, such as: USB Legacy is enabled; Boot Mode is set at Legacy Support ; Boot Priority is Legacy First ; USB Boot is Enabled; and my BIOS Version is 78CN25WW(V2.03).
I am sorry to go on so long, but I have tried to be thorough, thank you.

Hi, the W520 has ACPI and powermanegement issues on kernels < 2.6.39 without specific patches. Two questions:
What version of (K)Ubuntu are you trying to run?
What is the setting of your graphics system in the BIOS? Most of the time, setting it to Integrated just works fine, the open source Intel driver is quite good. When setting it to Discrete, you can either use the open source Nouveau drivers for the Nvidia card or the Nvidia proprietary binary drivers, all with varying success. At the moment I would not recommend setting it to Optimus, since support with Bumblebee is work in progress and quite tricky to handle. I am not sure what the Live CD is trying to do, but test it with graphics set to integrated first. Because of all the manual tweaking necessary two month ago I switched from Ubuntu to Gentoo, rolled a new kernel and never looked back. See my thread about HowTo Running Linux on the W520:
http://forums.lenovo.com/t5/Linux-Discussion/HowTo-Running-Linux-on-W520/td-p/453327
W520|4282-W16|2720QM|16GB|Q1000M|FHD|500GB|UMTS|BIOS 1.26|Gentoo Linux/2.6.39-r3|Win7-64-Prof|

Strange screen colors while booting Arch Linux (i686)

I'm trying to install Arch on an old computer via usb live,
when I start the first option "Boot Arch Linux i686" at the beginning seems to work then stops and appears:
Arch Linux 3.17.6-1-arch (tty1)
archiso login: root (automatic login)
at this point the pixels begin to change from black to white. until the monitor becomes completely white and black horizontal line appears at the center.
you have any idea what could be the problem?
Thanks for help
Last edited by Enrico87 (2015-01-28 19:06:27)

Enrico87 wrote:actually i have installed Debian
What?? The first post clearly said archlinux, but if this is debian, you are asking in the wrong place. Did you just use debian because the arch iso was unusable? Did these visual distrubances completely prevent login?
can you link me the article?
Not likely. Is your google broken?
EDIT: in hindsight this post was more abrupt than needed for a new-comer to the forums. Please pardon the tone - but the content was exactly as intended. We are happy to help when it is needed, but archlinux users are expected to be able to do some of their own research. If you really need the wiki link provided to you, you most likely would never be happy with archlinux.
Last edited by Trilby (2015-01-28 20:12:45)

[SOLVED] Cannot boot with linux-3.5.3

Edit: Solved, as explained here.
Hello,
after upgrading to linux-3.5.3-1 my boot stopped at
:: running early hook [udev]
I tried upgrading to grub-bios-2.00, removing any customization I had in modprobe.conf and /etc/modules-load.d as well as removing the only module (radeon) from /etc/mkinitcpio.conf (obviously followed by mkinitcpio -p linux), which made me go on to
:: waiting for udev uevents to be processed [BUSY]
I'm not sure it's an actual progress.
My /etc/udev/rules.d is empty and /usr/lib/udev/rules.d only contains pacman-tracked stuff.
I enabled some debugging as described here but couldn't get anything useful - is there any way for such messages to be logged somewhere, so they can be pasted here?
I ended up downgrading to linux-3.4.9, which boots fine.
Any idea to troubleshoot this?
cat /etc/rc.conf
# /etc/rc.conf - configuration file for initscripts
# Most of rc.conf has been replaced by various other configuration
# files. See archlinux(7) for details.
# For more details on rc.conf see rc.conf(5).
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond dbus @networkmanager kdm @cpufreq sshd @cups @supervisor)
# Storage
# USEDMRAID="no"
# USELVM="no"
# Network
# interface=
# address=
# netmask=
# gateway=
cat /etc/mkinitcpio.conf
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES=""
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options
# like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## This is identical to the above, except the old ide subsystem is
## used for IDE devices instead of the new pata subsystem.
# HOOKS="base udev autodetect ide scsi sata filesystems"
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev pata scsi sata usb filesystems"
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev pata mdadm encrypt filesystems"
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev usb lvm2 filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect pata scsi sata resume filesystems usbinput fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
pacman -Qo /usr/lib/udev/rules.d/*
/usr/lib/udev/rules.d/10-dm.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/10-vboxdrv.rules is owned by virtualbox 4.1.20-2
/usr/lib/udev/rules.d/11-dm-lvm.rules is owned by lvm2 2.02.97-1
/usr/lib/udev/rules.d/13-dm-disk.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/40-gphoto.rules is owned by libgphoto2 2.4.14-1
/usr/lib/udev/rules.d/40-hpet-permissions.rules is owned by jack2 1.9.8-2
/usr/lib/udev/rules.d/40-usb-media-players.rules is owned by media-player-info 17-1
/usr/lib/udev/rules.d/42-usb-hid-pm.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/50-udev-default.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/53-sane.rules is owned by sane 1.0.23-1
/usr/lib/udev/rules.d/60-cdrom_id.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-pcmcia.rules is owned by pcmciautils 018-4
/usr/lib/udev/rules.d/60-persistent-alsa.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-input.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-serial.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage-tape.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-storage.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-persistent-v4l.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/60-rfkill.rules is owned by rfkill 0.4-5
/usr/lib/udev/rules.d/61-accelerometer.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/61-gnome-bluetooth-rfkill.rules is owned by gnome-bluetooth 3.4.2-1
/usr/lib/udev/rules.d/64-md-raid.rules is owned by mdadm 3.2.5-2
/usr/lib/udev/rules.d/65-kvm.rules is owned by qemu 1.1.1-1
/usr/lib/udev/rules.d/69-cd-sensors.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/69-libmtp.rules is owned by libmtp 1.1.4-1
/usr/lib/udev/rules.d/70-infrared.rules is owned by v4l-utils 0.8.8-1
/usr/lib/udev/rules.d/70-power-switch.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-uaccess.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/70-udev-acl.rules is owned by consolekit 0.4.6-4
/usr/lib/udev/rules.d/71-seat.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/73-seat-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-net-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-probe_mtd.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/75-tty-description.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/77-nm-olpc-mesh.rules is owned by networkmanager 0.9.4.0-6
/usr/lib/udev/rules.d/78-sound-card.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-drivers.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/80-udisks.rules is owned by udisks 1.0.4-5
/usr/lib/udev/rules.d/80-udisks2.rules is owned by udisks2 1.94.0-2
/usr/lib/udev/rules.d/85-usbmuxd.rules is owned by usbmuxd 1.0.8-1
/usr/lib/udev/rules.d/90-alsa-restore.rules is owned by alsa-utils 1.0.25-3
/usr/lib/udev/rules.d/90-libgpod.rules is owned by libgpod 0.8.2-6
/usr/lib/udev/rules.d/90-pulseaudio.rules is owned by pulseaudio 2.1-1
/usr/lib/udev/rules.d/95-cd-devices.rules is owned by colord 0.1.21-2
/usr/lib/udev/rules.d/95-dm-notify.rules is owned by device-mapper 2.02.97-1
/usr/lib/udev/rules.d/95-keyboard-force-release.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-keymap.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-udev-late.rules is owned by systemd-tools 188-2
/usr/lib/udev/rules.d/95-upower-battery-recall-dell.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-fujitsu.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-gateway.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-ibm.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-lenovo.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-battery-recall-toshiba.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-csr.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-hid.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/95-upower-wup.rules is owned by upower 0.9.17-2
/usr/lib/udev/rules.d/97-bluetooth-hid2hci.rules is owned by bluez 4.101-1
/usr/lib/udev/rules.d/99-systemd.rules is owned by systemd-tools 188-2
cat /var/log/pacman.log
[2012-08-28 12:27] Running 'pacman -Sy'
[2012-08-28 12:27] synchronizing package lists
[2012-08-28 14:51] Running 'pacman -S -u'
[2012-08-28 14:51] starting full system upgrade
[2012-08-28 14:53] upgraded gc (7.2.c-1 -> 7.2.d-1)
[2012-08-28 14:53] >>> Updating module dependencies. Please wait ...
[2012-08-28 14:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-28 14:53] ==> Building image from preset: 'default'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [autodetect]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] ==> Building image from preset: 'fallback'
[2012-08-28 14:53] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-28 14:53] ==> Starting build: 3.5.3-1-ARCH
[2012-08-28 14:53] -> Running build hook: [base]
[2012-08-28 14:53] -> Running build hook: [udev]
[2012-08-28 14:53] -> Running build hook: [pata]
[2012-08-28 14:53] -> Running build hook: [scsi]
[2012-08-28 14:53] -> Running build hook: [sata]
[2012-08-28 14:53] -> Running build hook: [resume]
[2012-08-28 14:53] -> Running build hook: [filesystems]
[2012-08-28 14:53] -> Running build hook: [usbinput]
[2012-08-28 14:53] -> Running build hook: [fsck]
[2012-08-28 14:53] ==> Generating module dependencies
[2012-08-28 14:53] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-28 14:53] ==> Image generation successful
[2012-08-28 14:53] upgraded linux (3.4.9-1 -> 3.5.3-1)
[2012-08-28 14:53] upgraded lirc-utils (1:0.9.0-22 -> 1:0.9.0-26)
[2012-08-28 14:53] In order to use the new version, reload all virtualbox modules manually.
[2012-08-28 14:53] upgraded virtualbox-modules (4.1.20-1 -> 4.1.20-3)
[2012-08-28 14:59] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.3fb/google-chrome-21.0.1180.81-1-x86_64.pkg.tar.xz'
[2012-08-28 14:59] upgraded google-chrome (21.0.1180.57-1 -> 21.0.1180.81-1)
[2012-08-28 15:00] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.MgI/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:00] Running 'pacman -Sy'
[2012-08-28 15:00] synchronizing package lists
[2012-08-28 15:01] Running 'pacman -U /tmp/yaourt-tmp-dp/PKGDEST.Vic/tunlr-0.1.5-1-any.pkg.tar.xz'
[2012-08-28 15:01] upgraded tunlr (0.1.4-1 -> 0.1.5-1)
[2012-08-28 17:34] Running 'pacman -S extra/kdeedu-kmplot'
[2012-08-28 17:34] installed kdeedu-kmplot (4.9.0-1)
[2012-08-29 10:20] Running 'pacman -Syu'
[2012-08-29 10:20] synchronizing package lists
[2012-08-29 10:20] starting full system upgrade
[2012-08-29 11:07] Running 'pacman -S grub-bios'
[2012-08-29 11:07] removed grub (0.97-21)
[2012-08-29 11:07] Generating grub.cfg.example config file...
[2012-08-29 11:07] This may fail on some machines running a custom kernel.
[2012-08-29 11:08] done.
[2012-08-29 11:08] installed grub-common (2.00-1)
[2012-08-29 11:08] installed grub-bios (2.00-1)
[2012-08-29 11:48] Running 'pacman -Sy'
[2012-08-29 11:48] synchronizing package lists
[2012-08-29 11:48] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -Sy'
[2012-08-29 12:11] synchronizing package lists
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:11] Running 'pacman -S -u'
[2012-08-29 12:11] starting full system upgrade
[2012-08-29 12:15] upgraded firefox (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded firefox-i18n-it (14.0.1-1 -> 15.0-1)
[2012-08-29 12:15] upgraded gsmartcontrol (0.8.7-1 -> 0.8.7-2)
[2012-08-29 12:15] upgraded libwbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded smbclient (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded samba (3.6.7-1 -> 3.6.7-2)
[2012-08-29 12:15] upgraded sane (1.0.22-9 -> 1.0.23-1)
[2012-08-29 12:15] upgraded syslinux (4.05-6 -> 4.05-7)
[2012-08-29 12:15] upgraded thunderbird (14.0-1 -> 15.0-1)
[2012-08-29 12:15] upgraded thunderbird-i18n-it (14.0-1 -> 15.0-1)
[2012-08-29 12:15] -> You can now set custom file descriptor ulimits for Tor in
[2012-08-29 12:15] -> "/etc/conf.d/tor" using the "TOR_MAX_FD" variable.
[2012-08-29 12:15] upgraded tor (0.2.2.37-1 -> 0.2.2.38-1)
[2012-08-29 12:56] Running 'pacman -U /tmp/yaourt-tmp-root/PKGDEST.K10/downgrade-3.0-1-any.pkg.tar.xz'
[2012-08-29 12:56] installed downgrade (3.0-1)
[2012-08-29 12:57] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:04] Running 'pacman -U /var/cache/pacman/pkg/virtualbox-modules-4.1.20-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:05] Running 'pacman -R virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rd virtualbox-modules'
[2012-08-29 13:05] Running 'pacman -Rdd virtualbox-modules'
[2012-08-29 13:06] removed virtualbox-modules (4.1.20-3)
[2012-08-29 13:06] Running 'pacman -U /var/cache/pacman/pkg/linux-3.4.9-1-x86_64.pkg.tar.xz'
[2012-08-29 13:06] >>> Updating module dependencies. Please wait ...
[2012-08-29 13:06] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2012-08-29 13:06] ==> Building image from preset: 'default'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [autodetect]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:06] -> Running build hook: [sata]
[2012-08-29 13:06] -> Running build hook: [resume]
[2012-08-29 13:06] -> Running build hook: [filesystems]
[2012-08-29 13:06] -> Running build hook: [usbinput]
[2012-08-29 13:06] -> Running build hook: [fsck]
[2012-08-29 13:06] ==> Generating module dependencies
[2012-08-29 13:06] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2012-08-29 13:06] ==> Image generation successful
[2012-08-29 13:06] ==> Building image from preset: 'fallback'
[2012-08-29 13:06] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2012-08-29 13:06] ==> Starting build: 3.4.9-1-ARCH
[2012-08-29 13:06] -> Running build hook: [base]
[2012-08-29 13:06] -> Running build hook: [udev]
[2012-08-29 13:06] -> Running build hook: [pata]
[2012-08-29 13:06] -> Running build hook: [scsi]
[2012-08-29 13:07] -> Running build hook: [sata]
[2012-08-29 13:07] -> Running build hook: [resume]
[2012-08-29 13:07] -> Running build hook: [filesystems]
[2012-08-29 13:07] -> Running build hook: [usbinput]
[2012-08-29 13:07] -> Running build hook: [fsck]
[2012-08-29 13:07] ==> Generating module dependencies
[2012-08-29 13:07] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2012-08-29 13:07] ==> Image generation successful
[2012-08-29 13:07] upgraded linux (3.5.3-1 -> 3.4.9-1)
[2012-08-29 14:47] Running 'pacman -Sy'
[2012-08-29 14:47] synchronizing package lists
[2012-08-29 14:49] Running 'pacman -S -u'
[2012-08-29 14:49] starting full system upgrade
Last edited by thujone (2012-09-19 12:18:51)

because the report opener said that those freezes fixed with the 'futex' patch (included in 3.14-5).
As he says:
for those who have again problems despite the patch it means probably that there are another bugs further in the source code of kernel 3.14, bugs who are not necessarily related to the "futex problem"
i will try a clean profile, thanks.
Last edited by tritonas00 (2014-04-16 13:22:51)

HDD boot broken, Linux usb works

Similar Messages

Maybe you are looking for