Booting kernel from UEFI Shell - no console?

Hello ALL,
I'm trying to boot kernel from uefi shell w/o a bootloader like this:
fs1:> \efi\arch\vmlinuz-linux.efi root=/dev/sdc3 initrd=\efi\arch\initramfs-linux.img
All goes well, I see all the usual boot messages until at some point my screen turns black.
I saw this warning in the kernel.log: Warning: unable to open an initial console.
Do I need to use some special console=... or video=... parameter to get the console? If so which one?
Thanks for your help.

Fixed this following begginer guide with reFINd, keypont was to check efibootmgr output before writing efibootmgr -c -g -d ... command. then run it again and check for the added option.

Similar Messages

[SOLVED-in-PART] recompiling kernel images, boot diferent from chroot

Hi, I got into an dead end. Two days ago I was trying to solve some small annoying problems (ethernet driver, dkms not compiling automatically and difference in time hwclock and software clock) with my recent arch installation. I started with the time difference problem, for which I followed some solutions which I found in the internet, but all for no avail. So I postponed this for later and started to tackle the ethernet driver problem (Atheros AR8161) [https://wiki.archlinux.org/index.php/Ne … ros_AR8161]. I followed all described steps, I also did the mentioned hack. After all, I turned my note at work off and at home on and surprise it found the GRUB menu, I started the option for the system, the disk was checked but, no system came up. It even messed up my window8 system as well. But that is now up and working. After windows came back GRUB was loading and I can start it from GRUB, but not Arch.
I looked at the grub menu and as far as I could see and understand everything was pointing and the right direction. So I supposed that during the network driver compilation and module load, something went wrong with the images or images source (if they are important for booting). So reading around I got pointed to how to rebuild the kernel images (http://riskofruin.markmccracken.net/201 … image.html). I know the blog title is kreepy... but the procedure sounds very logic, correct and quite strait forward. So I got the latest Arch image, put it on an usb stick and chroot into my installed system.
When I started the /sbin/depmod I immediately got an error saying that two files where missing for the kernels 3.7.9-2-ARCH. Well as far as I remember my installed system has the latest kernel (3.7.10-1-ARCH). So I though to update my pendrive system and so restart an both kernels would be equal. After restarting, I repeated al chroot protocol and then I saw that I still had the wrong kernel images. I suspect why, but I am not sure, may be the system is all memory loaded when it is booted up? Also, if I saw right, even the images are quite different (pendrive and harddrive). I surfed around to see how can I, in an chroot environment, where the hardrive installed system has an different kernel from the booted system, generate new kernel images for the hardrive system, soin a hope that I can initialize my hardrive installed system? Is there someone that could guide me through this?
PS.: Remember I suppose the problem is in the kernel, I do not not how to check for sure.
Last edited by camarao (2013-03-10 03:10:56)

Hi Trilby,
No, just the initramfs. Because I think when I tryed to install my Atheros AR8161 drive I guess that something went wrong with the image or it could be something else.
Do you think the vmlinuz-linux should also be reconstructed?
Yesterday at night I found in the internet, someone using the "-k" option, of mkinitcpio, and pointing to the /boot/vmlinuz.linux directory. So if I understood well mkinitcpio using the options "-k", "-c" and "-g" you can point where to put the reconstructed images, vmlinuz and the initramfs, according to the "-c" pointed mkinitcpio.conf. This would allow me to reconstruct both images for the broken system which are from a different kernel version, than the one used to boot up and repair the broken system.
Two last questions:
1. Is it necessary to run /sbin/depmod before reconstructiong the images, as mentioned in the link (http://riskofruin.markmccracken.net/201 … image.html)?
2. Will the two new images be automatically replaced in /boot?
Sorry for asking this, but IT is just an hobby for me, and my IT knowledge is limited to what I read and understand. I like adventures and sometime dangerous one as well, I learn a lot. But if sometimes I can get a small help I like.
Well thanks for everything

Boot process freezes when booting from UEFI

Subject says it all. I followed the grub2/uefi wiki to configure Arch to work with my new motherboard's EFI. I can boot into grub okay and I can select the entry that boots Arch, but the boot hangs indefinably at the 'loading udev uevents [BUSY]' prompt. By contrast, if I boot using a 2nd HDD which has grub-bios on it, Arch comes up without a hitch. I must conclude that booting from UEFI is the problem and would like to fix it.
I moved all logs from /var/log so that the dir is empty hoping to catch something that would give a clue but after a failed boot attempt, mounting the root partition and inspecting /var/log gave no files.

Please check this Install Ubuntu without a CD using UNetbootin.
Also I think this thread is better safed in Linux section of this forum.
Try a look there, also.
Message Edited by Agotthelf on 15-11-2008 12:22 PM
Follow @LenovoForums on Twitter! Try the forum search, before first posting: Forum Search Option
Please insert your type, model (not S/N) number and used OS in your posts.
I´m a volunteer here using New X1 Carbon, ThinkPad Yoga, Yoga 11s, Yoga 13, T430s,T510, X220t, IdeaCentre B540.
TIP: If your computer runs satisfactorily now, it may not be necessary to update the system.
English Community Deutsche Community Comunidad en Español

[SOLVED] Booting a luks encrypted system directly from UEFI firmware

I've been struggling somewhat with my first UEFI machine (a Toshiba laptop).
The wiki got me to a basic four-partition install okay, and then after a small amount of pain I managed to get a build booted okay from gummiboot and with with root, swap and home luks-encrypted.
What I'm trying to do now is boot directly from the UEFI using an appropriate firmware entry, ie with something like what's described in the EFISTUB Wiki page:
# efibootmgr -d /dev/sdX -p Y -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sda2 rw initrd=/initramfs-linux.img"
...but I've been unable to achieve this with luks-encrypted partitions. Has anyone here had any success? Is there a "-u" parameter in the above command that will achieve this? I've certainly not found anything online explaining how this can be done, so maybe I'm being unrealistic and expecting too much.
Last edited by bananabrain (2015-06-18 14:45:56)

Head_on_a_Stick wrote:
Try this (untested -- I don't use encryption):
# efibootmgr -d /dev/sdX -p Y -c -L "Arch Linux" -l /vmlinuz-linux -u "cryptdevice=UUID=<UUID>:<mapped-name> root=UUID=<luks-UUID> rw initrd=/initramfs-linux.img"
You're a star - that works perfectly.
I wondered about lifting that syntax from "$esp/loader/entries/arch-encrypted.conf" in my last instalation but stupidly thought it was gummiboot-specific.
I'm as surprised that I couldn't find your solution on the web as I am that so few people seem interested in using UEFI firmware in this way. It seems like PC hardware has at last "grown up", with a versatile firmware that must have been a long time in collaborative development - something akin to Sun's OpenBoot - but the community's response has been to create another raft of boot loaders to sit on top of it. Maybe I'm missing something.
Thanks very much for your help.

Unable to boot kernel 3.9.x on Toshiba NB510 Netbook

Hi,
I'm going to start with a quick question first not related to the title:
what is the difference between the modesetting package in the official repos and the one in the AUR (git) version?
It looks as though the AUR version hasn't been updated since 2012 so I'm just wondering if for HD playback it's worth installing that over the official version?
Will that give me 1920x1080 resolution on external HDMI screen?? My Lenovo X220 with supported hardware has no issues at all with HD playback or HD res on external screens using up to date Arch stock components; so is this just a simple case of gma500 HELL??
Now for the issue that I'm having, as these things are all related to HD playback using the gma500 driver, which I'm currently going through this to help:
https://wiki.archlinux.org/index.php/Poulsbo
For some reason I'm unable to boot the 3.9.x kernel.... I've updated to all of the patch varients in the official repos and per the link above tried to build the lqx version...
I ran:
makepkg -s
pacman -U linux-lqx....tar.xz
grub-mkconfig -o /boot/grub/grub.cfg
to build and install the 64bit version. All went fine but when booting it as per all the stock kernels I get the same error:
echo 'Loading Linux lqx kernel ...'
linux /boot/vmlinuz-linux-lqx root=UUID=65811fe0-5600-4ad8-8a53-f43c89af0fad ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-lqx-fallback.img
the system hangs right at the above....
Loading initial ramdisk ...
section.
Using kernel 3.8.11-1 64bit I'm up and running and using X11 with no problem but the newer kernels don't do anything??
This is strange as my other machine running Arch x64 also works fine with stock kernels and latest patch revision 3.9.4.
Could anyone suggest anything to resolve the issue or will I need to wait until the next generation kernel 3.10 or 4.0??
Thanks

med1972 wrote:
Same problem here. Running on a Dell E6320, UEFI boot with rEFInd. Ran my updates, copied vmlinuz and the initramfs files from /boot to /boot/efi/EFI/arch. Rebooted and I get the same error. I am pulling down a copy of the systemrescuecd now.
::running early hook [udev]
::running hook [udev]
::Triggering uevents...
Waiting 10 seconds for device /dev/sda3
ERROR: device '/dev/sda3' not found. Skipping fsck.
ERROR: Unable to find root device '/dev/sda3'.
and then it drops me into the recovery shell. There are no /dev/sd* devices. I am guessing I need to refer to the partitions by UUID instead but /dev/sda3 was working before. Actually, I don't see any disk devices under /dev at all (no /dev/disk).
- Mark
Looking through the threads, I would venture to guess that this might actually be an issue that has been discussed where recent kernels (efistub) in various combinations with rEFInd/UEFI Shell v1/UEFI Shell v2 are sometimes unbootable. Search the threads for these issues... maybe you can participate in debugging, and find a workaround along the way.

REFInd stuck but works using UEFI Shell v1 (but not v2) [FIXED]

Hi,
First ArchLinux install and it gets problematic. I've followed the Beginner's guide and am now in the following situation.
rEFInd get stuck on:
rEFInd - Booting OS
Starting vmlinuz-arch.efi
Using load options 'root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap initrd=\EFI\arch\initramfs-arch.img'
The \EFI\arch\refind_linux.conf contains the following line:
"Boot" "root=/dev/sda5 ro rootfstype=ext4 add_efi_memmap initrd=\EFI\arch\initramfs-arch.img"
Interestingly, when I start it from the UEFI shell (from the arch installation cd) it works with the v1 but not the v2 !?
What did I overlook?
edit: initrt was a typo… sorry.
Last edited by greut (2013-03-27 18:10:53)

greut wrote:
srs5694 wrote:Second, try simplifying your command line. The "rootfstype=ext4 add_efi_memmap" options are probably unnecessary, so removing them (at least for testing) is desirable.
Yep, I can boot using only:
vmlinuz-arch.efi root=/dev/sda5 ro initrd=\EFI\arch\initramfs-arch.img
But still, it works with the UEFI Shell v1 from the liveUSB but not using the shell v2 or via rEFInd directly.
Is there any particular reason you need those options? If not, just leave them out and call it fixed. If you care to do more investigation, though, I'd be interested in knowing which of those two options is causing problems -- or perhaps if only the combination of both of them is causing problems. If either alone works but not both, then I'm inclined to suspect there's a problem with the length of the options line, although that seems odd, since I'm pretty sure I've tested with long options lines in the past with no sign of trouble.
I also can't help but wonder if this might somehow be related to the problem being discussed in this thread, which also has a bug report here. That seems to be a problem with specific kernels, but it's conceivable that there's an interaction between kernels and some other unknown factor.
FWIW, I just did a quick scan of the most relevant section of the rEFInd code and I didn't spot anything suspicious about how it's handling those strings. In fact, it's using allocated memory rather than fixed character arrays, so a hard limit caused by a string of length x seems to be unlikely as a cause unless it were in the kernel's EFI stub loader -- and then you wouldn't see the difference based on the boot manager type (EFI shell v.1 vs. EFI shell v.2 vs. rEFInd).

[SOLVED] Wiki page for GPT disks and booting arch using UEFI

Hi guys, I am new to archlinux. I installed archlinux x86_64 just yesterday and I like its customisability. I also like arch wiki. Nowhere else have I seen such extensive documentation, especially about things like HAL, UDEV etc. with proper instructions. Thanks to all archers.
I have installed Archlinux x86_64 in my Dell India Studio 1537 laptop along with Windows 7 Professional x64. Both the OSes boot in UEFI-GPT setup (my UEFI is tianocore.sourceforge.net EDK DUET UEFI64 firmware booting from USB). I boot Archlinux using my own compiled grub2-bzr compiled for both BIOS and UEFI-x64. I have a 1 MB BIOS Boot Partition as required by grub2 for BIOS-GPT booting. My Archlinux system can boot both from bios and from uefi, while Windows can boot only using UEFI.
The official Archlinux installation guide talks about only MBR (or msdos disklabel) partitions and booting from BIOS based systems. With 2TB drives becoming common place and UEFI being implemented (search for Phoenix SecureCore Tiano's 1 second POST operation), I think a proper wiki page describing differences between MBR and GPT, why GPT is better, how to setup arch to boot from GPT. Another page describing steps to setup arch to boot from UEFI (either as a separate page or as an extension of GRUB2 wiki page) is also needed.
Some details regarding Pure GPT (not a Hybrid GPT/MBR setup) and/or UEFI setups :-
Partitioning tools -
GNU Parted for filesystem related tasks
GPT fdisk tool - http://rodsbooks.com/gdisk/ , http://sourceforge.net/projects/gptfdisk/ , pacman -S gdisk (in extra repo) - for non-filesystem related tasks
util-linux-ng fdisk does not support GPT disks
Bootloader - GRUB2 - vanilla grub-legacy does not support GPT and does not support UEFI (Fedora's patched grub-legacy does support both GPT and UEFI) and syslinux does not support GPT (I may be wrong here - seems a gptmbr of syslinux does help in booting from gpt but not sure).
For GRUB2 - Need BIOS Boot Partition to embed GRUB2's core.img in GPT disks - size about 1 MB max - no filesystem
In GPT fdisk partition type code - EF02
In GNU Parted or GParted - bios_grub flag on
For UEFI-GPT booting this special partition is not needed as no embedding takes place. This is needed only in case of BIOS-GPT booting.
Incase of custom kernel configuration - enable CONFIG_EFI_PARTITION for GPT support
CONFIG_EFI for UEFI support (for UEFI even above option required)
CONFIG_EFI_VARS for UEFI Runtime Variables support (optional)
Note: Although GPT is part of UEFI specification, a UEFI system is not needed to boot from/use GPT. BIOS based GPT booting is possible with GRUB2 or Fedora's patched grub-legacy (but not vanilla grub-legacy provided by archlinux). It is also possible to boot Linux in UEFI-MBR setup (again using grub2) but I have not tried it.
Even without UEFI and less than 2TB harddrives, GPT based partitioning has many advantages - secondary GPT header and Partition table, CRC32 checksums. Unique Disk GUID and Filesystem-independent Unique Partition GUIDs, multiple primary partitions (default is 128 partitions, but it can be changed). The only problamatic OS is Windows which does not allow GPT booing unless one has UEFI based system. It allows only UEFI-GPT or BIOS-MBR setups. In linux it just depends on how the bootloader is configured - not a problem with grub2.
I also propose that incase of Auto-prepare Hard Drive, the installer default to GPT for "archlinux only" installs ( ie no dual-boot or triple-boot etc.).
I did not use the official archlinux iso but used archboot 2010.04 R3 as it gave an option of installing to GPT and also provided GRUB2 during bootloader install. I have never edited any wiki page before, thats why I request some one else to start a wiki page with the information given above.
I don't know whether this is the right place, but any Windows (Vista or 7 x64 versions) and Linux dual-boot user who has UEFI-based system with GPT partitioning and wants to get rid of Hybrid MBR setup (to boot Windows) can follow this post http://www.insanelymac.com/forum/lofive … hp/t186440 (outside this forum) - this link describes the way to make Windows boot natively in UEFI-GPT setup. After doing this one can install arch using GRUB2 compiled for UEFI x86_64, and Windows will also see
Last edited by skodabenz (2011-01-30 19:32:48)

Welcome to arch, skodabenz! Offering documentation on third post - all thumbs up
You could start the wiki page in your user-space with what you have, and then invite others to join working on it. Just register a wiki account, navigate to the page you want to start, for example:
http://wiki.archlinux.org/index.php/User:skodabenz/GPT
and click on "edit this page".
As noted in the other thread, arch's legacy grub is patched for gpt support. I don't know about UEFI, but you can always open a bug report asking for the patches from fedora to be included.
edit: the page from Rod Smith is a great resource. I was absolutely terrified at first by all this screwed up GPT/MBR stuff when I tried triple-booting Arch, Win and OS x, but he really does a great job explaining what it is all about.
Last edited by hokasch (2010-05-21 15:44:08)

Settting boot kernel architecture with Apple Script

Ok, so on three different sites, I've got a total of about fifty Macs, the majority of which run 10.6.8. I need to install a remote monitoring application on the machines, but the application only runs on the 64 bit kernel. I'd really like to set the kernel to 64 from Remote Desktop's send unix command feature, but it looks like it can't run with sudo. So after some poking around, I've come up with the following Applescript:
property myUserName : "<admin login>"
property myPassword : "<admin pass>"
do shell script "sudo systemsetup -setbootkernelarchitecture x86_64" user name myUserName password myPassword with administrator privileges
My goal here would be to run the script remotely with ARD. It copmpiles and runs fine, but doesn't acually change the boot kernel. I don't get any errors, so I've got nothign to go on here as to why it's not working.
Can anyone offer some insight on this? Would a different approach work better? I really don't want to go sit at each desktop and set the kernel manually.

I'd really like to set the kernel to 64 from Remote Desktop's send unix command feature, but it looks like it can't run with sudo
You don't need to use sudo with Remote Desktop's 'send UNIX' command.
When you choose to send a command you get to nominate what user it should run as - either root or the current logged-in user. Just set it to run as root and omit the sudo prefix and you should be fine.

[SOLVED] Kernels from the AUR not compiling properly

Hiya everyone,
I've got a bit of a problem, I think. Early this evening I tried downloading and making the Linux-lqx kernel from the AUR. Largely because why not.
After the tarball downloaded, I ran tar -xvf on it like I always do, ran namcap on the PKGBUILD (it came up with a few superfluous errors), and ran makepkg -s on the PKGBUILD. It downloaded the relevant source, then immediately failed the PGP signature check. I was like, "Oh you AUR!" and ran makepkg -s --skippgpcheck. It did it's thing until it was applying patches, at which point it just failed at a certain point with "ERROR: A failure occured in prepare()", and aborted. I reported the error and the lines that preceded it in the package's page in the AUR.
I got suspicious, and tried the Linux-lbre-xen kernel to test the building of it. Same issue: a prepare() error. Baffled, I thought maybe my building system was broken. I recompiled a few packages I had already built and installed successfully, and they were fine. I grabbed a few more tarballs from the AUR: adobe-air, I think jre, and something else. They all compiled great and installed just fine. Confused, I then tried building Linux-ck. Another prepare() error!
Then I noticed the line that preceded the error, "patching file virt/kvm/kvm_main.c", then the error. Going back to lqx and libre-xen, I tried compiling them again, and sure enough "patching file virt/kvm/kvm_main.c" directly preceded the prepare() error.
What's going on here? Strangely, every kernel I try from the AUR fails the PGP signature check, too. Just the kernels - everything else works as expected. Am I missing something?
Last edited by MrEvilBreakfast (2015-05-24 18:59:02)

The build goes fine until:
==> Starting prepare()...
The next patch would create the file Documentation/ABI/testing/debugfs-aufs,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/ABI/testing/sysfs-aufs,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file Documentation/devicetree/bindings/dma/fsl-mxs-dma.txt
The next patch would create the file Documentation/filesystems/aufs/README,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/01intro.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/02struct.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/03atomic_open.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/03lookup.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/04branch.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/05wbr_policy.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/06fhsm.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/06mmap.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/06xattr.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/07export.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/08shwh.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/10dynop.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file Documentation/filesystems/aufs/design/99plan.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file Documentation/kernel-parameters.txt
patching file Documentation/networking/scaling.txt
The next patch would create the file Documentation/scheduler/sched-BFS.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file Documentation/scsi/link_power_management_policy.txt
patching file Documentation/sysctl/kernel.txt
The next patch would create the file Documentation/tp_smapi.txt,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file Documentation/virtual/kvm/devices/s390_flic.txt
patching file MAINTAINERS
patching file Makefile
patching file arch/arm/boot/dts/armada-xp-openblocks-ax3-4.dts
patching file arch/arm/boot/dts/at91-sama5d3_xplained.dts
patching file arch/arm/boot/dts/dove.dtsi
patching file arch/arm/boot/dts/exynos5250-spring.dts
patching file arch/arm/boot/dts/imx23-olinuxino.dts
patching file arch/arm/boot/dts/imx25.dtsi
patching file arch/arm/boot/dts/imx28.dtsi
patching file arch/arm/boot/dts/imx6qdl-phytec-pfla02.dtsi
patching file arch/arm/boot/dts/omap3-n900.dts
patching file arch/arm/boot/dts/ste-dbx5x0.dtsi
patching file arch/arm/boot/dts/ste-href.dtsi
patching file arch/arm/boot/dts/ste-snowball.dts
patching file arch/arm/include/asm/elf.h
patching file arch/arm/include/uapi/asm/kvm.h
patching file arch/arm/kernel/Makefile
patching file arch/arm/kernel/hibernate.c
patching file arch/arm/kernel/process.c
The next patch would create the file arch/arm/kernel/psci-call.S,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file arch/arm/kernel/psci.c
The next patch would create the file arch/arm/kernel/reboot.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file arch/arm/kvm/arm.c
patching file arch/arm/mach-mvebu/pmsu.c
patching file arch/arm/mach-omap2/prm-regbits-34xx.h
patching file arch/arm/mach-omap2/prm-regbits-44xx.h
patching file arch/arm/mach-omap2/vc.c
patching file arch/arm/mach-omap2/vc.h
patching file arch/arm/mach-omap2/vc3xxx_data.c
patching file arch/arm/mach-omap2/vc44xx_data.c
patching file arch/arm/mach-s3c64xx/crag6410.h
patching file arch/arm/mach-s3c64xx/mach-crag6410.c
patching file arch/arm/net/bpf_jit_32.c
patching file arch/arm64/Kconfig
patching file arch/arm64/Makefile
patching file arch/arm64/include/asm/cpufeature.h
patching file arch/arm64/include/asm/smp_plat.h
patching file arch/arm64/include/uapi/asm/kvm.h
patching file arch/arm64/kernel/cpu_errata.c
patching file arch/arm64/kernel/entry.S
patching file arch/arm64/kernel/head.S
patching file arch/arm64/kernel/setup.c
patching file arch/arm64/kernel/smp.c
patching file arch/arm64/mm/dma-mapping.c
patching file arch/c6x/kernel/time.c
patching file arch/mips/Kconfig
patching file arch/mips/Makefile
patching file arch/mips/bcm47xx/board.c
patching file arch/mips/bcm63xx/prom.c
patching file arch/mips/bcm63xx/setup.c
patching file arch/mips/cavium-octeon/dma-octeon.c
patching file arch/mips/cavium-octeon/setup.c
patching file arch/mips/include/asm/asm-eva.h
patching file arch/mips/include/asm/cacheflush.h
patching file arch/mips/include/asm/cpu-features.h
patching file arch/mips/include/asm/elf.h
patching file arch/mips/include/asm/fpu.h
patching file arch/mips/include/asm/kvm_host.h
patching file arch/mips/include/asm/mach-cavium-octeon/cpu-feature-overrides.h
patching file arch/mips/include/asm/octeon/cvmx.h
patching file arch/mips/include/asm/octeon/pci-octeon.h
patching file arch/mips/include/asm/pgtable.h
patching file arch/mips/include/asm/r4kcache.h
patching file arch/mips/include/asm/spinlock.h
patching file arch/mips/kernel/entry.S
patching file arch/mips/kernel/smp-cps.c
patching file arch/mips/kernel/unaligned.c
patching file arch/mips/kvm/emulate.c
patching file arch/mips/kvm/mips.c
patching file arch/mips/kvm/trap_emul.c
patching file arch/mips/loongson/loongson-3/irq.c
patching file arch/mips/mm/cache.c
patching file arch/mips/mm/tlbex.c
patching file arch/mips/mti-malta/malta-memory.c
patching file arch/mips/netlogic/xlp/ahci-init-xlp2.c
patching file arch/mips/pci/Makefile
patching file arch/mips/pci/pci-octeon.c
patching file arch/mips/pci/pcie-octeon.c
patching file arch/mips/power/hibernate.S
patching file arch/mips/ralink/Kconfig
patching file arch/powerpc/kernel/cacheinfo.c
patching file arch/powerpc/mm/hugetlbpage.c
patching file arch/powerpc/perf/callchain.c
patching file arch/powerpc/platforms/cell/interrupt.c
patching file arch/powerpc/platforms/cell/iommu.c
patching file arch/powerpc/platforms/cell/spufs/sched.c
patching file arch/powerpc/platforms/powernv/pci-ioda.c
patching file arch/s390/kernel/suspend.c
patching file arch/s390/kvm/interrupt.c
patching file arch/s390/kvm/kvm-s390.h
patching file arch/s390/kvm/priv.c
patching file arch/x86/Kconfig
patching file arch/x86/Kconfig.cpu
patching file arch/x86/Makefile_32.cpu
patching file arch/x86/include/asm/insn.h
patching file arch/x86/include/asm/mwait.h
patching file arch/x86/include/asm/pvclock.h
patching file arch/x86/include/asm/spinlock.h
patching file arch/x86/kernel/acpi/boot.c
patching file arch/x86/kernel/apic/io_apic.c
patching file arch/x86/kernel/cpu/intel.c
patching file arch/x86/kernel/cpu/perf_event_intel_ds.c
patching file arch/x86/kernel/early_printk.c
patching file arch/x86/kernel/ioport.c
patching file arch/x86/kernel/process.c
patching file arch/x86/kernel/pvclock.c
patching file arch/x86/kvm/vmx.c
patching file arch/x86/kvm/x86.c
patching file arch/x86/lib/insn.c
patching file arch/x86/lib/usercopy_64.c
patching file arch/x86/pci/acpi.c
patching file arch/x86/platform/efi/early_printk.c
patching file arch/x86/tools/test_get_len
patching file arch/x86/vdso/vclock_gettime.c
patching file arch/xtensa/Kconfig
patching file arch/xtensa/include/uapi/asm/unistd.h
patching file arch/xtensa/platforms/iss/network.c
patching file arch/xtensa/platforms/xtfpga/Makefile
patching file arch/xtensa/platforms/xtfpga/include/platform/hardware.h
patching file arch/xtensa/platforms/xtfpga/include/platform/lcd.h
patching file arch/xtensa/platforms/xtfpga/lcd.c
patching file block/Kconfig.iosched
patching file block/Makefile
The next patch would create the file block/bfq-cgroup.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file block/bfq-ioc.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file block/bfq-iosched.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file block/bfq-sched.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file block/bfq.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file block/blk-core.c
patching file block/blk-mq.c
patching file block/blk-sysfs.c
patching file drivers/accessibility/braille/braille_console.c
patching file drivers/acpi/acpi_pnp.c
patching file drivers/acpi/acpica/acmacros.h
patching file drivers/acpi/acpica/dsopcode.c
patching file drivers/acpi/acpica/evgpe.c
patching file drivers/acpi/acpica/evregion.c
patching file drivers/acpi/acpica/exdump.c
patching file drivers/acpi/acpica/exfldio.c
patching file drivers/acpi/acpica/exregion.c
patching file drivers/acpi/acpica/hwgpe.c
patching file drivers/acpi/acpica/hwvalid.c
patching file drivers/acpi/acpica/nsdump.c
patching file drivers/acpi/acpica/tbdata.c
patching file drivers/acpi/acpica/tbinstal.c
patching file drivers/acpi/acpica/tbprint.c
patching file drivers/acpi/acpica/tbxfroot.c
patching file drivers/acpi/acpica/utaddress.c
patching file drivers/acpi/blacklist.c
patching file drivers/acpi/resource.c
patching file drivers/acpi/sbs.c
patching file drivers/acpi/sbshc.c
patching file drivers/acpi/scan.c
patching file drivers/ata/acard-ahci.c
patching file drivers/ata/ahci.c
patching file drivers/ata/ahci.h
patching file drivers/ata/libahci.c
patching file drivers/ata/libahci_platform.c
patching file drivers/ata/libata-core.c
patching file drivers/ata/libata-eh.c
patching file drivers/ata/libata-pmp.c
patching file drivers/ata/libata-scsi.c
patching file drivers/ata/libata.h
patching file drivers/ata/sata_highbank.c
patching file drivers/base/bus.c
patching file drivers/base/cacheinfo.c
patching file drivers/base/platform.c
patching file drivers/block/loop.c
patching file drivers/block/rbd.c
patching file drivers/bluetooth/ath3k.c
patching file drivers/bluetooth/btusb.c
patching file drivers/char/tpm/tpm-chip.c
patching file drivers/clk/at91/clk-usb.c
patching file drivers/clk/qcom/clk-rcg.c
patching file drivers/clk/qcom/clk-rcg.h
patching file drivers/clk/qcom/clk-rcg2.c
patching file drivers/clk/qcom/gcc-ipq806x.c
patching file drivers/clk/qcom/lcc-ipq806x.c
patching file drivers/clk/samsung/clk-exynos4.c
patching file drivers/clk/tegra/clk-tegra124.c
patching file drivers/clk/tegra/clk.c
patching file drivers/cpufreq/cpufreq.c
patching file drivers/cpufreq/cpufreq_conservative.c
patching file drivers/cpufreq/cpufreq_ondemand.c
patching file drivers/cpufreq/intel_pstate.c
patching file drivers/crypto/omap-aes.c
patching file drivers/gpio/gpio-mvebu.c
patching file drivers/gpio/gpiolib-sysfs.c
patching file drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c
patching file drivers/gpu/drm/drm_irq.c
patching file drivers/gpu/drm/exynos/exynos_dp_core.c
patching file drivers/gpu/drm/exynos/exynos_drm_fimd.c
The next patch would create the file drivers/gpu/drm/exynos/exynos_drm_fimd.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file drivers/gpu/drm/i2c/adv7511.c
patching file drivers/gpu/drm/i915/i915_drv.c
patching file drivers/gpu/drm/i915/i915_irq.c
patching file drivers/gpu/drm/i915/i915_reg.h
patching file drivers/gpu/drm/i915/intel_display.c
patching file drivers/gpu/drm/i915/intel_dp.c
patching file drivers/gpu/drm/i915/intel_i2c.c
patching file drivers/gpu/drm/i915/intel_lvds.c
patching file drivers/gpu/drm/radeon/atombios_crtc.c
patching file drivers/gpu/drm/radeon/atombios_encoders.c
patching file drivers/gpu/drm/radeon/dce6_afmt.c
patching file drivers/gpu/drm/radeon/evergreen_hdmi.c
patching file drivers/gpu/drm/radeon/r600_hdmi.c
patching file drivers/gpu/drm/radeon/radeon_asic.c
patching file drivers/gpu/drm/radeon/radeon_asic.h
patching file drivers/gpu/drm/radeon/radeon_audio.c
patching file drivers/gpu/drm/radeon/radeon_connectors.c
patching file drivers/gpu/drm/radeon/radeon_cs.c
patching file drivers/gpu/drm/radeon/radeon_ttm.c
patching file drivers/gpu/drm/radeon/radeon_uvd.c
patching file drivers/gpu/drm/radeon/radeon_vce.c
patching file drivers/gpu/drm/radeon/radeon_vm.c
patching file drivers/gpu/drm/radeon/rv770d.h
patching file drivers/gpu/drm/radeon/si_dpm.c
patching file drivers/gpu/drm/radeon/uvd_v1_0.c
patching file drivers/gpu/drm/radeon/uvd_v2_2.c
patching file drivers/hid/Kconfig
patching file drivers/hid/Makefile
patching file drivers/hid/hid-ids.h
patching file drivers/hid/hid-multitouch.c
The next patch would create the file drivers/hid/huiontablet.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file drivers/hid/usbhid/hid-quirks.c
patching file drivers/hv/channel.c
patching file drivers/hv/channel_mgmt.c
patching file drivers/i2c/busses/i2c-rk3x.c
patching file drivers/i2c/i2c-core.c
patching file drivers/i2c/i2c-mux.c
patching file drivers/idle/intel_idle.c
patching file drivers/infiniband/core/cma.c
patching file drivers/infiniband/core/umem.c
patching file drivers/infiniband/hw/mlx4/qp.c
patching file drivers/infiniband/ulp/iser/iser_initiator.c
patching file drivers/infiniband/ulp/isert/ib_isert.c
patching file drivers/input/input-mt.c
patching file drivers/input/joydev.c
patching file drivers/input/mouse/alps.c
patching file drivers/input/mouse/elantech.c
patching file drivers/input/mouse/elantech.h
patching file drivers/input/mouse/synaptics.c
patching file drivers/input/mouse/synaptics.h
patching file drivers/macintosh/Kconfig
patching file drivers/macintosh/adbhid.c
patching file drivers/md/md.c
patching file drivers/md/raid0.c
patching file drivers/media/platform/marvell-ccic/mcam-core.c
patching file drivers/media/platform/marvell-ccic/mcam-core.h
patching file drivers/media/rc/img-ir/img-ir-core.c
patching file drivers/media/usb/stk1160/stk1160-v4l.c
patching file drivers/memstick/core/mspro_block.c
patching file drivers/mfd/mfd-core.c
patching file drivers/mmc/card/block.c
patching file drivers/mmc/card/queue.c
patching file drivers/mmc/card/queue.h
patching file drivers/mmc/core/core.c
patching file drivers/mmc/host/sh_mmcif.c
patching file drivers/mmc/host/sunxi-mmc.c
patching file drivers/mmc/host/tmio_mmc_pio.c
patching file drivers/mtd/ubi/attach.c
patching file drivers/mtd/ubi/cdev.c
patching file drivers/mtd/ubi/eba.c
patching file drivers/mtd/ubi/wl.c
patching file drivers/net/ethernet/broadcom/bnx2x/bnx2x.h
patching file drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c
patching file drivers/net/ethernet/cadence/macb.c
patching file drivers/net/ethernet/chelsio/cxgb4/t4_hw.c
patching file drivers/net/ethernet/intel/e1000/e1000_main.c
patching file drivers/net/ethernet/marvell/pxa168_eth.c
patching file drivers/net/ethernet/mellanox/mlx4/en_ethtool.c
patching file drivers/net/ethernet/mellanox/mlx4/en_netdev.c
patching file drivers/net/ethernet/mellanox/mlx4/en_rx.c
patching file drivers/net/ethernet/mellanox/mlx4/en_tx.c
patching file drivers/net/ethernet/mellanox/mlx4/mlx4_en.h
patching file drivers/net/netconsole.c
patching file drivers/net/ppp/ppp_generic.c
patching file drivers/net/vxlan.c
patching file drivers/net/wireless/hostap/hostap.h
patching file drivers/net/wireless/hostap/hostap_ap.c
patching file drivers/net/wireless/hostap/hostap_config.h
patching file drivers/net/wireless/hostap/hostap_hw.c
patching file drivers/net/wireless/hostap/hostap_info.c
patching file drivers/net/wireless/hostap/hostap_ioctl.c
patching file drivers/net/wireless/rtlwifi/rtl8192cu/sw.c
patching file drivers/net/wireless/ti/wl18xx/debugfs.c
patching file drivers/net/wireless/ti/wlcore/debugfs.h
patching file drivers/nfc/st21nfcb/i2c.c
patching file drivers/pinctrl/core.c
patching file drivers/pinctrl/core.h
patching file drivers/pinctrl/devicetree.c
patching file drivers/platform/x86/Kconfig
patching file drivers/platform/x86/Makefile
patching file drivers/platform/x86/compal-laptop.c
patching file drivers/platform/x86/hdaps.c
The next patch would create the file drivers/platform/x86/thinkpad_ec.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/platform/x86/tp_smapi.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file drivers/power/ipaq_micro_battery.c
patching file drivers/power/lp8788-charger.c
patching file drivers/power/twl4030_madc_battery.c
patching file drivers/rtc/rtc-armada38x.c
patching file drivers/scsi/3w-9xxx.c
patching file drivers/scsi/3w-9xxx.h
patching file drivers/scsi/3w-sas.c
patching file drivers/scsi/3w-sas.h
patching file drivers/scsi/3w-xxxx.c
patching file drivers/scsi/3w-xxxx.h
patching file drivers/scsi/megaraid/megaraid_sas_fusion.c
patching file drivers/scsi/mvsas/mv_sas.c
patching file drivers/scsi/scsi_devinfo.c
patching file drivers/scsi/scsi_scan.c
patching file drivers/scsi/sd.c
patching file drivers/scsi/sd_dif.c
patching file drivers/scsi/storvsc_drv.c
patching file drivers/spi/spi-imx.c
patching file drivers/spi/spidev.c
patching file drivers/ssb/Kconfig
patching file drivers/staging/Kconfig
patching file drivers/staging/Makefile
patching file drivers/staging/android/sync.c
patching file drivers/staging/panel/panel.c
The next patch would create the file drivers/staging/vhba/Kconfig,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/staging/vhba/Makefile,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/staging/vhba/vhba.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file drivers/staging/vt6655/rxtx.c
patching file drivers/target/iscsi/iscsi_target.c
patching file drivers/target/iscsi/iscsi_target_erl0.c
patching file drivers/target/iscsi/iscsi_target_login.c
patching file drivers/target/target_core_file.c
patching file drivers/target/target_core_sbc.c
patching file drivers/target/target_core_transport.c
patching file drivers/tty/Kconfig
patching file drivers/tty/hvc/hvc_xen.c
patching file drivers/tty/serial/8250/8250_core.c
patching file drivers/tty/serial/8250/8250_dw.c
patching file drivers/tty/serial/8250/8250_early.c
patching file drivers/tty/serial/atmel_serial.c
patching file drivers/tty/serial/imx.c
patching file drivers/tty/serial/of_serial.c
patching file drivers/tty/serial/uartlite.c
patching file drivers/tty/serial/xilinx_uartps.c
patching file drivers/tty/vt/vt.c
patching file drivers/usb/chipidea/otg_fsm.c
patching file drivers/usb/class/cdc-acm.c
patching file drivers/usb/class/cdc-wdm.c
patching file drivers/usb/core/hub.c
patching file drivers/usb/dwc2/hcd.c
patching file drivers/usb/gadget/legacy/printer.c
patching file drivers/usb/host/ehci-hcd.c
patching file drivers/usb/host/ehci-hub.c
patching file drivers/usb/host/fotg210-hcd.c
patching file drivers/usb/host/fusbh200-hcd.c
patching file drivers/usb/host/isp116x-hcd.c
patching file drivers/usb/host/oxu210hp-hcd.c
patching file drivers/usb/host/r8a66597-hcd.c
patching file drivers/usb/host/sl811-hcd.c
patching file drivers/usb/host/uhci-hub.c
patching file drivers/usb/host/xhci-ring.c
patching file drivers/usb/isp1760/isp1760-hcd.c
patching file drivers/usb/musb/musb_core.c
patching file drivers/usb/musb/musb_virthub.c
patching file drivers/usb/phy/phy.c
patching file drivers/usb/storage/uas-detect.h
patching file drivers/usb/storage/uas.c
patching file drivers/usb/storage/usb.c
patching file drivers/vfio/vfio.c
patching file drivers/video/logo/Kconfig
patching file drivers/video/logo/Makefile
patching file drivers/video/logo/logo.c
The next patch would create the file drivers/video/logo/logo_arch_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_bsd_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_debian_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_exherbo_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_fbsd_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_fedoraglossy_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_fedorasimple_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_gentoo_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_oldzen_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_slackware_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_tits_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file drivers/video/logo/logo_zen_clut224.ppm,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file drivers/xen/events/events_2l.c
patching file drivers/xen/events/events_base.c
patching file drivers/xen/xen-pciback/conf_space.c
patching file drivers/xen/xen-pciback/conf_space.h
patching file drivers/xen/xen-pciback/conf_space_header.c
patching file drivers/xen/xenbus/xenbus_probe.c
patching file fs/Kconfig
patching file fs/Makefile
The next patch would create the file fs/aufs/Kconfig,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/Makefile,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/aufs.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/branch.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/branch.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/cpup.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/cpup.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dbgaufs.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dbgaufs.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dcsub.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dcsub.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/debug.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/debug.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dentry.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dentry.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dinfo.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dir.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dir.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dynop.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/dynop.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/export.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/f_op.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/fhsm.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/file.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/file.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/finfo.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/fstype.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/hfsnotify.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/hfsplus.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/hnotify.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/i_op.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/i_op_add.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/i_op_del.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/i_op_ren.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/iinfo.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/inode.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/inode.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/ioctl.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/loop.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/loop.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/magic.mk,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/module.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/module.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/mvdown.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/opts.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/opts.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/plink.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/poll.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/posix_acl.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/procfs.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/rdu.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/rwsem.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/sbinfo.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/spl.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/super.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/super.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/sysaufs.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/sysaufs.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/sysfs.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/sysrq.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/vdir.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/vfsub.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/vfsub.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/wbr_policy.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/whout.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/whout.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/wkq.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/wkq.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/xattr.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file fs/aufs/xino.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file fs/binfmt_elf.c
patching file fs/btrfs/extent-tree.c
patching file fs/btrfs/ioctl.c
patching file fs/btrfs/send.c
patching file fs/btrfs/xattr.c
patching file fs/buffer.c
patching file fs/coredump.c
patching file fs/dcache.c
patching file fs/exec.c
patching file fs/ext4/extents.c
patching file fs/ext4/extents_status.c
patching file fs/ext4/inode.c
patching file fs/ext4/namei.c
patching file fs/file_table.c
patching file fs/hfsplus/xattr.c
patching file fs/inode.c
patching file fs/lockd/svcsubs.c
patching file fs/namei.c
patching file fs/namespace.c
patching file fs/nfs/callback.c
patching file fs/nfs/direct.c
patching file fs/nfs/nfs4xdr.c
patching file fs/nfs/read.c
patching file fs/nfs/write.c
patching file fs/nfsd/nfs4proc.c
patching file fs/nfsd/nfs4state.c
patching file fs/nfsd/nfs4xdr.c
patching file fs/nfsd/nfsctl.c
patching file fs/nfsd/nfsd.h
patching file fs/nilfs2/btree.c
patching file fs/notify/group.c
patching file fs/notify/mark.c
patching file fs/ocfs2/dlm/dlmmaster.c
patching file fs/open.c
patching file fs/pnode.c
patching file fs/pnode.h
patching file fs/proc/base.c
patching file fs/proc/nommu.c
patching file fs/proc/task_mmu.c
patching file fs/proc/task_nommu.c
patching file fs/splice.c
patching file fs/xattr.c
patching file include/acpi/acconfig.h
patching file include/acpi/acpixf.h
patching file include/acpi/actypes.h
patching file include/acpi/platform/acenv.h
patching file include/dt-bindings/clock/tegra124-car-common.h
patching file include/linux/bpf.h
patching file include/linux/cgroup_subsys.h
patching file include/linux/console.h
patching file include/linux/file.h
patching file include/linux/init_task.h
patching file include/linux/ioprio.h
patching file include/linux/jiffies.h
patching file include/linux/libata.h
patching file include/linux/linux_logo.h
patching file include/linux/mm.h
patching file include/linux/mm_types.h
patching file include/linux/mount.h
patching file include/linux/nilfs2_fs.h
patching file include/linux/sched.h
patching file include/linux/sched/prio.h
patching file include/linux/skbuff.h
patching file include/linux/splice.h
The next patch would create the file include/linux/thinkpad_ec.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file include/linux/usb.h
patching file include/linux/usb_usual.h
patching file include/scsi/scsi_devinfo.h
patching file include/sound/emu10k1.h
patching file include/sound/soc-dapm.h
patching file include/target/iscsi/iscsi_target_core.h
patching file include/target/target_core_base.h
The next patch would create the file include/trace/events/fs.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file include/uapi/linux/Kbuild
The next patch would create the file include/uapi/linux/aufs_type.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file include/uapi/linux/nfsd/debug.h
patching file include/uapi/linux/sched.h
patching file include/uapi/linux/vt.h
patching file include/video/samsung_fimd.h
patching file init/Kconfig
patching file init/main.c
patching file kernel/bpf/core.c
patching file kernel/bpf/verifier.c
patching file kernel/debug/kdb/kdb_io.c
patching file kernel/delayacct.c
patching file kernel/exit.c
patching file kernel/fork.c
patching file kernel/printk/printk.c
patching file kernel/ptrace.c
patching file kernel/sched/Makefile
The next patch would create the file kernel/sched/bfs.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
The next patch would create the file kernel/sched/bfs_sched.h,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file kernel/sched/core.c
patching file kernel/sched/deadline.c
patching file kernel/sched/fair.c
patching file kernel/sched/idle.c
patching file kernel/sched/stats.c
patching file kernel/stop_machine.c
patching file kernel/sysctl.c
patching file kernel/time/Kconfig
patching file kernel/time/posix-cpu-timers.c
patching file kernel/trace/ring_buffer.c
patching file kernel/trace/trace_events.c
patching file kernel/trace/trace_functions_graph.c
patching file kernel/trace/trace_selftest.c
patching file lib/Kconfig.debug
patching file lib/string.c
patching file mm/Makefile
patching file mm/filemap.c
patching file mm/huge_memory.c
patching file mm/hugetlb.c
patching file mm/madvise.c
patching file mm/memory-failure.c
patching file mm/memory.c
patching file mm/mempolicy.c
patching file mm/mmap.c
patching file mm/msync.c
patching file mm/nommu.c
patching file mm/page-writeback.c
The next patch would create the file mm/prfile.c,
which already exists! Skipping patch.
1 out of 1 hunk ignored
patching file net/bridge/br_netfilter.c
patching file net/core/dev.c
patching file net/core/skbuff.c
patching file net/ethernet/eth.c
patching file net/ipv4/Kconfig
patching file net/ipv4/geneve.c
patching file net/ipv4/ip_forward.c
patching file net/ipv4/ping.c
patching file net/ipv4/route.c
patching file net/ipv4/tcp_output.c
patching file net/mac80211/mlme.c
patching file net/netlink/af_netlink.c
patching file scripts/mkcompile_h
patching file security/commoncap.c
patching file security/device_cgroup.c
patching file security/security.c
patching file sound/oss/sequencer.c
patching file sound/pci/emu10k1/emu10k1.c
patching file sound/pci/emu10k1/emu10k1_callback.c
patching file sound/pci/emu10k1/emu10k1_main.c
patching file sound/pci/emu10k1/emupcm.c
patching file sound/pci/emu10k1/emuproc.c
patching file sound/pci/emu10k1/memory.c
patching file sound/pci/hda/hda_codec.c
patching file sound/pci/hda/patch_realtek.c
patching file sound/pci/hda/thinkpad_helper.c
patching file sound/soc/codecs/cs4271.c
patching file sound/soc/codecs/pcm512x.c
patching file sound/soc/codecs/rt5677.c
patching file sound/soc/codecs/tfa9879.c
patching file sound/soc/codecs/wm8741.c
patching file sound/soc/davinci/davinci-evm.c
patching file sound/soc/samsung/s3c24xx-i2s.c
patching file sound/synth/emux/emux_oss.c
patching file sound/synth/emux/emux_seq.c
patching file sound/usb/quirks.c
patching file tools/lib/traceevent/kbuffer-parse.c
patching file tools/perf/config/Makefile
patching file tools/perf/tests/make
patching file tools/perf/util/cloexec.c
patching file tools/perf/util/cloexec.h
patching file tools/perf/util/symbol-elf.c
patching file tools/power/x86/turbostat/Makefile
patching file virt/kvm/arm/vgic.c
patching file virt/kvm/kvm_main.c
==> ERROR: A failure occurred in prepare().
Aborting...
Last edited by MrEvilBreakfast (2015-05-24 17:08:08)

[SOLVED] UEFI shell won't work on Thinkpad Edge E520

Hi there,
I have installed the x86_64 UEFI Shell 2.0 on my Thinkpad Edge E520 which is already booting in UEFI mode using refind-efi for some time now. The same shell is running just fine on my desktop system.
But - on the Thinkpad it doesn't run. The shell is installed as /boot/efi/shellx64.efi and when I start the laptop, refind appears and shows me the shell icon (amoung others). But when I choose the shell from refind I get a black screen with this writing:
Starting shellx64.efi
Using load options ' '
ASSERT_EFI_ERROR (Status = Device Error)
ASSERT c:\dev\edk2tip\Build\Shell\RELEASE_VS2005\X64\ShellPkg\Application\Shell\Shell\DEBUG\AutoGen.c (431): !EFI_ERROR (Status)_
I don't know if the text is going on after the last underline. If yes I cannot see it because the text is running out of the screen.
The funny thing is - exactly the same setup is working pretty nice on my Asrock ITX board but not on the Lenovo Thinkpad Edge E520.
Any ideas? Just say, if you need further information.
Last edited by swordfish (2013-02-10 11:44:27)

Okay, found the - somewhat obvious - solution myself. The UEFI Bios on my Thinkpad is an "old" UEFI 2.0. So, Shell 2.0 won't work on this system (as I could have read in the wiki ).
Now, I have installed Shell 1.0 and I can enter the shell from refind .
Last edited by swordfish (2013-02-10 11:45:03)

Problem booting Linux from JTAG on PicoZed

Forums:
General Questions
I'm trying to boot my PicoZed board to Linux from JTAG. It's close, but I'm missing something.
I can successfully boot from SD Card with these same files, so it seems the problem lies elsewhere.
Here are the steps, I'm following:
* Set SW1 to JTAG boot mode.
* XMD Console commands
- connect arm hw
- dow zynq_fsbl.elf
- run
- fpga –f fpgabits.bit
- dow u-boot.elf
- run
* Stop u-boot from auto-booting in terminal
* XMD Console command
- stop
- dow –data image.ub 0x1000000
- con
* From u-boot type
- bootm 0x1000000
* Linux boot hangs with last lines
- [drm] Initialized drm 1.1.0 20060810
- brd: module loaded
- loop: module loaded
The next lines that Linux is supposed to print has to do with the QSPI, but I'm not sure what else to do.
When successfully booting from the SD Card, I'm using BOOT.BIN with the same FSBL, FPGA Bits and u-boot.
I'm also using the same image.ub file.
Any suggestions on what to try next?
--Jeff

The DTS is in the image.ub file. I will try the steps in the pdf and let you know if it helps.
Here is the boot information from when u-boot loads/runs the image.ub file:
reading image.ub
8639064 bytes read in 749 ms (11 MiB/s)
## Loading kernel from FIT Image at 01000000 ...
Using 'conf@1' configuration
Trying 'kernel@1' kernel subimage
Description: PetaLinux Kernel
Type: Kernel Image
Compression: gzip compressed
Data Start: 0x010000f0
Data Size: 8620511 Bytes = 8.2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x00008000
Entry Point: 0x00008000
Hash algo: crc32
Hash value: 9a258a1a
Verifying Hash Integrity ... crc32+ OK
## Loading fdt from FIT Image at 01000000 ...
Using 'conf@1' configuration
Trying 'fdt@1' fdt subimage
Description: Flattened Device Tree blob
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x01838bb4
Data Size: 17256 Bytes = 16.9 KiB
Architecture: ARM
Hash algo: crc32
Hash value: a1140b0d
Verifying Hash Integrity ... crc32+ OK
Booting using the fdt blob at 0x1838bb4
Uncompressing Kernel Image ... OK
Loading Device Tree to 07ff8000, end 07fff367 ... OK
--Jeff

[WORKAROUND] Can only boot after exiting EFI Shell

Hello there, What happens is when I boot, this is an EFI, if I boot directly to GRUB I get the menu then the messages:
Loading Linux core repo kernel ...
Loading initial ramdisk ...
Then is just stops. There are no more messages or any thing. The only way I have found is to boot into EFI Shell then exit the shell which drops into grub which will then boot all the way.
I have efibootmgr set to boot into EFI Shell. The startup.nsh just runs 'exit'.
grub2-common 1:2.00beta2-3
grub2-efi-x86_64 1:2.00beta2-2
Linux 3.2.13-1
root/boot are a single partition. Filestsyem is btrfs compressed zlib on an SSD.
I hope this is clear enough.
Last edited by tweezerhead (2012-04-06 00:13:34)

I ran into very similar problem today, except that I'm using grub-bios.
Booting 3.2.13-1 fails at "loading initial ramdisk...", with no error message or whatsoever. The lts kernel also fails.
It turns out the downgrading the kernel from 3.2.13-1 to 3.2.11-1 fixes the problem.

Error on install, CDROM not booting Kernel, unable to mount CDRM, what now?

Please help. I am new to this, so as many options as possible would be a help.
So far here are the steps I've taken to install Solaris 8 (Intel):
1. Checked HCL - I have two CD ROM's I've tried, both are on the list. (Mitsumi FX140S and Sony DVD DDU220E)
2. Set BIOS to boot CDROM - Boot failure..., I have set and changed jumpers back and forth from Master to Slave. I have moved CDROM drive from primary Slave to secondary Master and secondary Slave.
3. I have downloaded and used the Device Config Assistant boot floppy. It boots and checks devices. It also recognizes the CDROMs I have (both CDROMs are not have installed at the same time).
4. I have selected whichever CDROM I have installed as the default boot device (*) using F4_Boot Tasks. I have also adjusted timeouts from 0,1,2 and 3 seconds and have had autoboot ON/OFF.
5. I have entered F2 to continue and I receive this error:
Unable to mount a Solaris root file system from the device:
CD : (*) Target 1, MITSUMI CD-ROM FX140S !B e12 on Bus Mastering IDE controller on Board PCI bus 0, at Dev 4, Func 1
Error message from mount:
/pci@0,0/pci-ide@4,1/ide@0/sd@1,0:a: can't open - no hsfs VTOC
Press Enter to Continue.
I have inserted all 3 CD I have created with the same results from each. The CDs have the .iso extention and were created using Easy CD Creator.
Please, Please, Please, ANY suggestions!!
LL

First off you don't need to set your CDROM as the default boot device to install Solaris, that's why we have the Solaris DCA boot diskette. And also only the Solaris Installation CD and Software 1 of 2 are bootable CDs, the software 2 of 2 is NOT.
Once you finish downloading the images from Sun's website you need to not only add the .iso extension to the ending of each image file but use the option "Burn using CD image" under the File menu in Easy CD creator.
If you try and view the burned CD under Windows you will only see a small number of the actual files that are on the CD. And NO you will not see the .vtoc file and will not be able make one yourself.
My suggestion would be to try and burn a new CD with the above instructions and boot with the Solaris DCA and continue pressing F2 until you get to the point where it asks you select where you want to boot the kernel from. At that point put with ther Installation CD or Software 1 of 2 in your drive and attempt to boot from it.
Keep us updated on your progress.
Allen
Sun Develeper Technical Support

MacBook Pro doesn't boot (Kernel Panic), even CD/DVD doesn't work anymore

It is a very long story how I came to the point I am at right now, so I'll try to keep it really short:
My MPR stops booting and shows that Kernel Panic message (30s after starting the boot procedure with the grey screen and Apple logo), telling me to reboot. It even does not boot from CD/DVD anymore. Zapping PRAM doesn't help. Booting into Safe Mode doesnt work. Booting into Single User Mode and repairing the drive (/sbin/fsck -fy) did help a couple of times; scanning the system with Onyx and removing faulty preferences even helped a lot as well, everything seemed to work fine. But after the next system crash (happened during memtest procedure), I had the same problem again, this time even Single User Mode doesnt help. Booting from external FW-drive doesnt work. Every time: Kernel Panic.
Since I put in 4GB RAM four weeks ago (without any problems until last week), I replaced the new RAM with the old RAM. Still: Kernel Panic.
How I ran into the whole trouble? I replaced the original internal drive with a new 500GB WD drive. Now problems, until I accidently wiped the whole drive with BootCamp assistant.
At some point, I managed to boot from CD/DVD and (deep-)clean / format the whole internal disk, reinstalled 10.5.4, imported the settings and software from my old internal disk, and maybe f*ed everything up again by doing so. ONYX helped me to isolate a couple of preferences that went bad after that import, and after deleting them, everything seemed to be alright, especially after updating to 10.5.6. Until the system crashed next time, during a memtest. Memory seems to be ok though; as I already said, swapping it against the old RAM doesnt change anything, and TechTool didnt find anything. HD seems to be ok as well, neither Disk Utility nor ONYX nor TechTool did find any hardware fault.
After every crash so far, pcscd.pub was corrupted, with 17 instead of 16 blocks (Single User Mode fsck -fy fixed that), which is more than strange since I don't use any smart card stuff which that file is used for.
Now, even fixing that file doesnt help anymore.
Verbose mode shows that the boot process stops right after
Feb 15 18:00:43 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow[57]: Login Window Application Started -- Threaded auth
Feb 15 18:0046 localhost mDNSResponder-176.3 (Sep 30 2008 16:59:38)[56]: starting
AirPort: Link Down on en1
It could be interesting to put back in the old internal drive, but I'd like to avoid that at almost any cost since putting back the cases lid was such a p. i. t. a. It doesnt seem to be necessary as the drive itself seems to be ok technically.
The thing that amazes me most is the fact that I can't boot neither from CD/DVD nor from external FW-drive(s) anymore.
Now I'm sitting here with a beautiful 2,5k$ brick and I'm wondering if anybody has a clue what I could do or who to ask (Apple Care won't be available before tomorrow). Thanks a lot in advance!

Alright, "Signal 4" means "illegal instruction", as "info signal" shows.
Rebooting in Single User Mode and doing another fsck -fy shows that everything is as before: a damaged pcscd.pub (incorrect block count) and a "succesful repair" with "FILESYSTEM MODIFIED". Exiting Single User Mode and continuing boot up works this time . Very strange. Verifying the volume using Disk Utility: everything is ok; some of the rights were corrupted though (in detail:
Die Zugriffsrechte unterscheiden sich für Library/Application Support/Apple/ParentalControls/ALRHelperJobs, Soll-Wert: drwxrwxr-x , Ist-Wert: drwxr-xr-x .
Die Zugriffsrechte unterscheiden sich für System/Library/LaunchDaemons/com.apple.usbmuxd.plist, Soll-Wert: -rw-r--r-- , Ist-Wert: -rwxr-xr-x .
Die Zugriffsrechte unterscheiden sich für Library/Application Support/Apple/ParentalControls/ContentFiltering, Soll-Wert: drwxrwxr-x , Ist-Wert: drwxr-xr-x .
Die Zugriffsrechte unterscheiden sich für Library/Application Support/Apple/ParentalControls, Soll-Wert: drwxrwxr-x , Ist-Wert: drwxr-xr-x .),
but repaired without problems. BTW, "Die Zugriffsrechte unterscheiden sich für..." means "Access rights differ...", "Soll-Wert" means "reference value", "Ist-Wert" means "actual value".
Testing CPU, RAM, video RAM and USB using TechTool Deluxe: everything is ok.
The crash log read as follows:
System Configuration:
Model: MacBookPro3,1, BootROM MBP31.0070.B07, 2 processors, Intel Core
2 Duo, 2.4 GHz, 4 GB
Graphics: GeForce 8600M GT, GeForce 8600M GT, spdisplayspciedevice,
256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 2 GB, DDR2 SDRAM, 667 MHz
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x87),
1.4.8.0
Network Service: AirPort, AirPort, en1
Network Service: Parallels Shared Networking Adapter, Ethernet, en2
Network Service: Parallels Host-Only Networking Adapter, Ethernet, en3
PCI Card: pci168c,24, sppci_othernetwork, PCI Slot 5
Serial ATA Device: WDC WD5000BEVT-00ZAT0, 465,76 GB
Parallel ATA Device: MATSHITADVD-R UJ-857E
USB Device: Built-in iSight, (null) mA
USB Device: Apple Internal Keyboard / Trackpad, (null) mA
USB Device: IR Receiver, (null) mA
USB Device: composite_device, (null) mA
Problem Details
Sun Feb 15 15:18:32 2009
panic(cpu 0 caller 0x001A8CD4): Kernel trap at 0x640e50b7, type
14=page fault, registers:
CR0: 0x8001003b, CR2: 0x000000bc, CR3: 0x00e8f000, CR4: 0x00000660
EAX: 0x54d91630, EBX: 0x06884c04, ECX: 0x06725800, EDX: 0x00000000
CR2: 0x000000bc, EBP: 0x54d91668, ESI: 0x00000000, EDI: 0xffffffff
EFL: 0x00010246, EIP: 0x640e50b7, CS: 0x00000008, DS: 0x06720010
Error code: 0x00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x54d91408 : 0x12b0fa (0x4592a4 0x54d9143c 0x133243 0x0)
0x54d91458 : 0x1a8cd4 (0x46280c 0x640e50b7 0xe 0x461fbc)
0x54d91538 : 0x19ede5 (0x54d91550 0x9 0x54d91668 0x640e50b7)
0x54d91548 : 0x640e50b7 (0xe 0x48 0x54d90010 0x64110010)
0x54d91668 : 0x640ecea0 (0xc1d00001 0x1000000 0x1000003 0x40)
0x54d916c8 : 0x640e1e2b (0x54d91858 0x6 0x0 0x0)
0x54d91828 : 0x640d4f12 (0x0 0x600d600d 0x7027 0x54d91858)
0x54d918e8 : 0x642a8942 (0xc1d00001 0x1000000 0x1000003 0x40)
0x54d91918 : 0x642b1d86 (0x46536000 0x1000000 0x88100090 0x3e)
0x54d938a8 : 0x64296056 (0x46536000 0x1000000 0x15 0x4653601c)
0x54d939a8 : 0x640cf572 (0x46536000 0x0 0x54d93ab2 0x80)
0x54d93a08 : 0x54f675a5 (0x6702800 0x0 0x54d93ab2 0x80)
0x54d93b38 : 0x54f68d74 (0x6702800 0x54f6c358 0x54d93bec 0x4)
0x54d93c08 : 0x54f54133 (0x6702800 0x1 0x0 0x13)
0x54d93c68 : 0x54f4d93a (0x6702800 0x2507 0x54d93d2c 0x65dfbe4)
0x54d93c98 : 0x40fc65 (0x6702800 0x65dfbe4 0x65dfbe4 0x0)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.2.8)@0x640ce000->0x6430dfff
dependency: com.apple.iokit.IONDRVSupport(1.5.2)@0x54f61000
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x54e54000
dependency:
com.apple.iokit.IOGraphicsFamily(1.5.2)@0x54f45000
com.apple.iokit.IONDRVSupport(1.5.2)@0x54f61000->0x54f6efff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x54e54000
dependency:
com.apple.iokit.IOGraphicsFamily(1.5.2)@0x54f45000
com.apple.iokit.IOGraphicsFamily(1.5.2)@0x54f45000->0x54f60fff
dependency: com.apple.iokit.IOPCIFamily(2.4.1)@0x54e54000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
9E25
Kernel version:
Darwin Kernel Version 9.4.0: Mon Jun 9 19:30:53 PDT 2008;
root:xnu-1228.5.20~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
Interestingly the Kernel version mentioned in the crash log is 9.4.0, while ONYX states it is 9.6.0.
Trying a reboot from CD and new clean install, then I'm planning to make extensive hardware tests.

HP pavilion g6 do not boot nothing from any media

Hi, I have this notebook (HP Pavilion g6-1010sc) and one day it do not boot nothing from any media.
I tried to boot linux, winxp, original win7-x64 from internal and external USB disks, but unfortunatelly.
Notebook restarts or freezes after i tried to boot OS. Start of booting OS is correct, in original win7 it asked to run system normally or launch system repair. After i choose normal startup, its normally starting and only one point of WIN7 loading logo is shown and after this freezes.
When I run win7 installation from USB HDD or launch system repair, windows loaded files correctly, but after this, system restarts and capslocks LED blink two or three times and notebook startup again.
I have on second USB HDD linux ubuntu, which work on every computer correctly, but on this computer it freezes after small time.
I tested Back Track5 from DVD and during boot notebook restarts after one minute too.
I have tried to remove original HDD and try boot other USB HDD/DVD too, but no change. I tried other memory modules, but no change too.
System diagnostics of RAM and HDD is correct and no problem found.
Original bios on this notebook was F6.A and I tried older version F53 and only one change is, that in booting is shown more piece of WIN7 boot logo, and again freezes.
I tried disable automatic restart after system failure, but notebook it does not react on this, when it want to restart or freeze, it does it
Sorry for my english

No, i do not think, that I have UEFI bios. After I pres ESC and after F2 or directly after turn on press F2, my diagnostic menu looks as this:
This diagnostic tool is stored on HDD, when I removed HDD, this tool can not to run.
(By the way, tests will be passed.)
And original system is WIN7x64 and on support page is only this system and cannot be selected other operating systems, e.g. WIN8, which fully supports UEFI.
This reply is no solution for me. I tested internal HDD in different computer and it is 100% correct, and RAM i tried to change with other 100% correct modules as I wrote on last post and no change.
This means, that RAM and HDD is correct. I want to know, whether is error in notebook's mainboard or bios or some different.
I think, I am not first with such problem, and I do not want know solution only, but I want also know reason.
Thanks for reply, but it is no solution for this problem, and is outside.

Booting kernel from UEFI Shell - no console?

Similar Messages

Maybe you are looking for