Cannot boot with PXE on new Intel I217-LM nic card

I imaged a new Dell 5540 with nic I-218LM perfectly by inserting the driver.
After that I did the same with the Lenovo T540p with nic I-217LM which is the same driver "E1D6232.inf" and when I boot into PXE (after changing bios to UEFI network to both or legacy) it finds the SCCM/WDS server and finds the advertisement.
It asks me to press F12, I press it but it doesn't react and the following line is: "PXE-MOF: Exiting Intel Boot Agent". So I find this weird, it's like the key F12 doesn't work. Is there a way to see if this key works?
Does anybody know why it's not going furthur? The correct driver seems to be injected into the boot image. I am using the driver from the lenovo website in the Windows OS after Winpe stage.

After much frustration trying to get the drivers to install for a winpe boot image I found that the issue was it couldn't find the files to copy.  The inf file does not tell the install where to find the driver files. Instead it was trying to find them
in x:\windows\inf\   not where they are installed in the pe image simple fix was to copy the files into the windows inf folder and now the drivers install correctly.
I found this by hitting shift-F10 and the running notepad and opened the x:\windows\inf\setupapi.dev.log file, the source path for the driver points to x:\windows\inf (see below)
\machine.inf_amd64_neutral_9e6bb86c3b39a3e9\machine.inf' ([strings])
!    sto:           Skipping missing driver package file 'e1d62x64.sys'.
!    sto:           Skipping missing driver package file 'e1d62x64.din'.
!    sto:           Skipping missing driver package file 'NicCo36.dll'.
!    sto:           Skipping missing driver package file 'NicInstD.dll'.
!    sto:           Skipping missing driver package file 'e1dmsg.dll'.
      flq:           {FILE_QUEUE_COPY}
     flq:                CopyStyle      - 0x00000000
     flq:                SourceRootPath - 'x:\windows\inf'
Good luck
L

Similar Messages

  • M83 and M93p ipv6 storms intel i217-LM NIC

    The Intel i217-LM NIC in some new lenovo devices will create massive IPv6 listener discovery spam when the machine sleeps, hibernates, or is turned off.  This can be resolved by using the 19.0 or later driver from intel (currently 19.1).  The officially supported driver provided by Lenovo is older than 19.0 and causes network storms.  Highly recommend that Lenovo bump up their supported version and anyone using this NIC on a production network update their driver from Intel's website.
    This problem only seems to occur if there are 2 or more machines with this NIC on the same network that are in a sleep, hibernate, or off state (off but plugged in).
    This is also a problem for T440 machines, probably others as well.

    It's connected IPV4 but because of the faulty NIC driver it starts broadcasting IPV6 when in sleep/hibernate mode.
    https://supportforums.cisco.com/discussion/12291431/ipv6-broadcast-storm-caused-hp-eliteone-800-intel-i217-lm-nic-how-find-hosts
    https://forums.lenovo.com/t5/A-M-and-Edge-Series-ThinkCentre/M83-and-M93p-ipv6-storms-intel-i217-LM-NIC/td-p/1600686

  • Intel i217-LM NIC Causes Broadcast storm and High CPU

    Wanted to post this here to help others that may be experiencing issues with broadcasts.   
    If you have PC's with the Intel i217-LM NIC if you don't have the latest driver from Intel the NIC will cause an IPV6 broadcast storm when the computer goes into sleep/hibernate.  You have to have at least two PC's on your network in sleep/hibernate mode.  It causes the same affect as a network loop.  In my network it would cause the MDF CPU to go to 100% and basically shut the network down.  
    We have Lenovo M93 desktops that have this NIC and I know that there are other PC's that have his same NIC and experience the same problem.
    When the broadcast storm is happening you can issue the command 
    show interfaces | include is up|line|broadcast on your MDF switch to find which interfaces have high broadcasts.  You may have to trace it through your uplinks to your IDF's.  You can then shut those interfaces to stop the broadcast storm.
    Your long term solution will be to get the latest NIC driver from Intel and update your PC's.

    It's connected IPV4 but because of the faulty NIC driver it starts broadcasting IPV6 when in sleep/hibernate mode.
    https://supportforums.cisco.com/discussion/12291431/ipv6-broadcast-storm-caused-hp-eliteone-800-intel-i217-lm-nic-how-find-hosts
    https://forums.lenovo.com/t5/A-M-and-Edge-Series-ThinkCentre/M83-and-M93p-ipv6-storms-intel-i217-LM-NIC/td-p/1600686

  • Cannot boot with new SSD

    Installed new OWC 240G SSD in 2007 iMac. Started up with old HD in external case running OS 10.10.2.  Initialized SSD with Disk Utilities, and it mounted on the desktop.  Transferred contents from old HD to new SSD. Computer boots fine from old HD in external case, but does not boot with internal SSD.  After displaying Apple symbol for a few seconds of the startup process, computer goes to a kernel panic and gets into a loop of retry message-Apple symbol-message-etc.  The SSD shows on the desktop, but does not show as a startup disk in System Preferences pane.  Disk Utilities shows drive is fine, but repair of permissions is grayed out.  Window says permissions repair is only permitted on OS installed with an Apple installer.  System folder on the SSD does not show the "blessed" symbol.  Have tried recloning using Time Machine backup - same result.  Installed eDrive on SSD with TechToolsPro, and can start up in eDrive thru TTP window, thus verifying all cabling.  After booting with original internal HD installed in external case, SSD will show on desktop, but will disappear in a few minutes after a message says it was improperly ejected.  Suggestions?  Is there a way to access OS 10 software purchased and downloaded from Apple site?

    Many possibilities here. Maybe a bad connection when you installed the drive. Maybe a bad drive. Maybe a bad SATA cable.
    How did you format the drive? Should be Mac OS Extended Journaled. When you boot into the recovery drive, access disk utility from there and see if you can access the drive.
    I have the same drive as you. What I did is use Disk Utility from the recovery drive of TM. I first re-formatted the SSD drive. Then I used Disk Utility to restore the whole drive of my original to the new SSD drive.
    You can still download the Yosemite installer from the App Store in your purchases providing you downloaded it from the App Store already.

  • T440p exactly once per two power ups cannot boot with USB mouse receiver insterted.

    With inserted nano Logitech mouse receiver my Lenovo cannot boot once per two power ups.
    Let say that I power off laptop. Power on, it just powers down itself after 3-4 seconds. I power up it again and everything is OK. It allways behave the same way: NOTOK >> OK.

    engywook wrote:Erm, I dunno, I'd guess input-mouse. I have no idea what evdev is.
    evdev is a generic input driver (you can use it for both your mouse and keyboard). If you do not know what the evdev driver is, you most likely are using the xf86-input-mouse driver.
    To be sure you can use a
    pacman -Q | grep xf86-input
    from the command line and see which one comes up. Try switching to the other (you need to install it first of course). This gentoo wiki page may help you a bit how to configure your xorg.conf for an evdev driver: http://gentoo-wiki.com/HOWTO_Advanced_M … d_USB_Mice (note that you do not need most parts that are written there)
    Does this solve your problem? If not, try using the vesa video driver temporarily to see if the problem is with your video card driver.
    engywook wrote:Do I need to do something with pacman to get all the packages at the mirror? all I've really done so far is pacman -Sy or -Su whatever updates it.
    No normally that should work. You don't get any results when doing 
    pacman -Ss pidgin
    If so try to use another mirror and see if that helps.

  • Cannot boot with Perc /2 raid controller

    I have just built a system with K7D + 2 2400 MP, and the system hangs when I try to boot with my Perc/2 raid controller in. I have stripped down to just the following components;
    2 2400 MP
    Perc 2
    1GB ECC ram
    Sapphire ATI Radeon 9000
    When I try to boot the machine it gets as far as trying to load the Perc /2 Bios and hangs.
    The Perc works fine in my old system Tyan Tiger 133 with dual 733 PIII, it also seems to boot up fine in a Tyan Tiger S2460.
    Any ideas on the cause or a work around?
    Thanks.

    Yeah, all the firmware & bios is up to date, have stripped things down to just the motherboard, graphics card & Perc. Tried PCI graphics to elliminate any conflicts there. I have disabled all the on-board controllers too.

  • [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)

  • Cannot Print with HP L7680 (new) printer

    Hi there,
    I printed fine for the past several months with Tiger, but with Leopard I cannot access my printer and this is urgent. I see many similar posts here. This printer was purchased new at Best Buy only a few months ago and works great, until now. I was able print 1-2 pages here are there after hitting numerous buttons, but it just doesn't work at all anymore. I have no idea why. A friend with Leopard used to come to my place and print and she can't access it anymore either.
    Thanks for any tips.

    That's correct, I did the normal install of Leopard and never installed any HP drivers. Actually I never installed any HP drivers with Tiger either and it has been working fine until I put Leopard in. Not sure what to do, but I have never put a driver in for my HP printer....its not even connected, it just worked with my wireless network perfectly from day one....until now.

  • Cannot boot from installed disk on Intel Xserve

    I have an Intel Xserve.
    I have had it for some months,it has been working fine, it is a standby backup machine to others and is used as a testbed.
    I have just installed from the supplied DVD 10.4.8.
    The installation goes smoothly, however after the first reboot. The system is trying to install from dvd again.
    I have tried installing a known working Intel boot disk, and this just gives a folder with the flashing question mark.
    I have tried formatting the disk and partitioning making sure to use GUID partition and it doesn't boot.
    I can however boot from a external FW drive with 10.4.10 installed.
    I can then go into Startup disk and set the boot disk as on of the installed drives, but this has No effect.
    I am currently trying to Clone from the FW drive to an installed drive.
    Has anyone seen this behaviour?
    Can someone tell me what I can try to resolve this.
    All I have read regarding Flashing Question Marks is to ensure disks are using GUID partion and when booting from another disk to set the boot disk in the System Prefences.

    Welcome to the forum!
    You're missing the first disk which is "Rescue and Recovery", followed by CDs 1-7.
    Make sure to re-align the partitions before or after OS installation in order to get the proper utilization of that SSD.
    Good luck.
    Cheers,
    George
    In daily use: R60F, R500F, T61, T410
    Collecting dust: T60
    Enjoying retirement: A31p, T42p,
    Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
    Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

  • Cannot boot with graphics card installed

    Specs:
    MSI R9 280 TWIN FROZR
    ASRock H97M
    Core i5 4750
    Corsair 750W
    8GB g.skills
    First time builder. Build was turning on (CPU/case/GPU fans running) but going to a black screen with no bios or POST. No mobo beep codes because somehow it doesn't have speaker bumpers. With the R9 unplugged, it gets to bios fine. I triple checked the power cables and seating of the card. Made sure in the BIOS it was set to PCI-E as the default graphics source. Looked on ASRock's site but couldn't find compatibility info.
    Is the card a dud, or is there anything else I should try?
    Thanks so much

    CPU socket was fine. I switched the bios to internal graphics and kept the GPU installed, BIOS could see the card in the slot fine.. which at first I thought meant the gpu was definitely busted. But then, I switched the PCI-E Speed from "auto" to "Gen2" and default GPU back to the PCI-E slot and lo, it worked and booted. Tried "gen3", didn't work. Switched the switch at the top and tried Gen3, and it worked!
    Weirdly, messing around again I un-switched the switch and put it back to "Auto", and it still boots fine now..
    EDIT: Never mind, still need gen3/switched to the left

  • I cannot install iTunes on a new Intel i3 core windows 7 computer

    After I download the iTunes setup file, it starts installing the software and comes to a point in which there is a problem with the 64bit program loading

    Hello there, jag123059.
    The following Knowledge Base article offers up some great steps to follow for resolving issues with installing iTunes:
    Issues installing iTunes or QuickTime for Windows
    http://support.apple.com/kb/ht1926
    Thanks for reaching out to Apple Support Communities.
    Cheers,
    Pedro.

  • My Iphone 4 appears this massage "this accessory may not be supported" and then cannot charging with apple (old & new also) genuine cable

    Since updating to iOS 7.0.4 I've getting a prompt "this accessory may not be supported" after a few minutes charging.
    Charging then stops and I've unplug the cable and reconnect, then hopefully get another 5 minutes before the message appears again. The phone is pretty much unusable now as I can't get it charged. Only using genuine apple cables (have tried 3 seperate cables) and have tried charging both via the wall and the laptop, but the result is the same.

    Yes Doctor9fan. All Accessories are genuine.

  • PXE-Boot with Hyper-V based on W2K12 R2 with Gen2-VMs

    Dear Community,
    as you probably know the new R2-Version was advertised with the ability of PxE-booting with the synthetic instead of the legacy-nic which works with poor 100 mbit/s.
    Here´s the problem:
    When I create a new virtual machine with Gen2 without the option "Secure Boot" and PxE-boot it, I get the following error:
    Boot failed. EFI Network.
    Boot failed. EFI SCSI Device.
    No Operating System was Loaded. Press a key to retry the boot sequence
    When I create another new virtual machine with Gen2 but with the option "Secure Boot" and PxE-boot it, I get this error:
    Station IP address is x.x.x.x
    Server IP address is x.x.x.x
    NBP filename is pxelinux.0
    NBP filesize is 15888 Bytes
    Downloading NBP file...
    Successfully downloaded NBP file.
    Boot Failed. EFI Network. Failed Secure Boot Verification.
    Boot Failed. EFI SCSI Device
    No Operating System was Loaded. Press a key to retry the boot sequence
    When taking a look at the log of the TFTP-Server (TFTPD32) I get the same information regardless which way I do it. The only interesting thing it says is:
    "Peer returns ERROR <User aborted the transfer> ->aborting transfer"
    I have also tried to use another tool called Serva as TFTP/PXE-Server -> The error still occurs.
    Before anybody wants me to try to do it as Gen1 -> I know that this works, but I want to get it running under Gen2 since the synthetic one works (should work) much faster than the legacy-one.
    Really looking forward to get some useful information here.
    Thanks in advance !

    This question was completely answered by Andy here:
    http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/4098e57f-c6da-493a-a772-87d60ee1d0a1/#b2808adb-a79e-49e6-8a00-2c324c3e41d1
    He wrote:
    "Apparently, there is an issue in WDS that causes it to use legacy NetBIOS name resolution instead of DNS to find a domain controller, and it impedes domain controller connectivity. The solution is simple - go to TCP advanced properties on WDS server,
    and on WINS tab disable NetBIOS over TCP/IP. This forces WDS to use the right name resolution, and everything works perfectly."
    I can confirm it. Works perfectly! Thanks to Andy!
    Vadim

  • Kernel Panic / G4 dp500 / Cannot boot currently

    Machine Config:
    10.4.8
    G4 DP500
    1.5 gigs ram.
    Internal ATA133 PCI controller card (Sonnet)
    Four internal hard drives. My current 4-drive configuration:
    Three 200 gig drives are connected to the internal ATA133 sonnet card, and out of those three, just one was made to be bootable with 10.4.8.
    The fourth drive (160gig) is connected to the on-board ata33 connector, and is bootable with 10.3.9 on it. Presently I cannot boot from either drive
    I installed the Sonnet ata133 card three months ago to expand the drive capacity. I wanted to "see" hard drives larger than 127 gigs, which is the limit if using the onboard ata33.
    Everything has been working fine for 3 to 4 months after I installed the Sonnet card, and three internal drives. But about three days ago, my computer was hard-frozen when I went to use it. No mouse movement etc. When I rebooted, I received the Kernel panic black screen with its resulting verbosity.
    I had a spare internal drive laying around that was preconfigured with an OS on it. So fearing the Kernel panic was from the Sonnet controller card, I installed my spare drive to connect from the mother board ata33 connector. I was then able to boot from my spare. after that I was able to repair my boot drive that was attached to my Sonnet card. The one that was initially corrupted by the Kernel panic.
    After rebooting successfully to m, I decided to leave my spare boot drive attached the on-board ata33 connecter (just in case the kernel panic happened again)
    Well, it did happen again. And now I can't even boot from my spare now. Its as if the kernel panic is destroying the directories of my boot drives!
    Specifically the volume header wraps.
    In addition, I can't even boot from Disk Warrior or my OSX install disk. The screen just hangs at grey. So, I have no more spare boot drives available, and I cannot boot from cd/dvd. The cd/dvd drive is attached to the internal on-board ata33 like my spare is.
    I know that heat will often cause a hard freeze. But will it also cause kernel panics upon reboot?
    As it stands now:
    When ever I try to reboot, a black screen will display unix command line text describing kernel panic and the last line is"
    "Panic: we are hanging here."
    This seems like a hardware issue. But why are my boot directories becoming corrupted? At this point, maybe its over heating. I have four drives now stuffed into the G4 with ribbon cables all over the place and a vent fan installed into one of the unused PCI slots.
    I haven't installed any new hardware lately.
    I upgraded to 10.4.8 and the panic still happens.
    I have 30gigs of itunes, 20gigs of iphotos, 40gigs of imovies, 10 gigs of mail, etc. My back up system was using SuperDuper to copy my USER folder to another internal drive, so I know I have a backup, It's just that I cannot access it. If I can recover my data, I'm going to go out and buy a G5, transfer my data, and be done with it. If I can't recover my data, then I will be forced to live a life of quiet desperation. My wife will leave me if I've lost her itunes collection
    BTW, what is a good program to back up to 8.5 gig DVD's? Can I make large 20gig .DMG files and segment then into 8.5 gig portions? I no longer want to rely on internal backup. I would feel better knowing that my back were on dvd's locked in my fire safe. When did I become so dependant on computers?!
    Losing sleep.
    Haifarmer

    It may not help, but it's worth a try to reset the PMU. See Mac PRAM, NVRAM, CUDA/PMU & Battery Tutorial
    When trying to troubleshoot problems, disconnect all external devices except your monitor, kbd & mouse. Do you experience the same problems?
    May be a solution on one of these links.
    Troubleshooting
    The X Lab (Troubleshooting & Maintenance of OS X)
    OS X Routine Maintenance & Generic Troubleshooting
    Prevent Mac Disasters
    Kernel Panic
    Mac OS X Kernel Panic FAQ
    Mac OS X Kernel Panic FAQ
    Resolving Kernel Panics
    12-Step Program to Isolate Freezes and/or Kernel Panics
     Cheers, Tom

  • Using External Boot Drive with New Intel Mac Mini

    I have a 1st Gen MacMini and use an external 7200 RPM Lacie drive as the system boot drive along with all the applications.
    If I were to purchase a new Intel Mac Mini, is it possible to use the current external drive as the system drive or is there some conversion steps that would be necessary ?
    Thank you.

    You can use the hardware, but will have to repartition and reinstall the OS from the disk shipped with the new Mac Mini.
    http://docs.info.apple.com/article.html?artnum=303220
    If you create a disk image of the Lacie on your Mini, you can later use setup assistant to restore users and applications from that image.

Maybe you are looking for