PXE-Boot with Linux

I have an IBM Machine (8193-75G) with Intel 10/100/1000 LAN. Is it
possible to do an PXE-Boot with Linux? Do I need a special driver?
Thanx

[email protected]
> I have an IBM Machine (8193-75G) with Intel 10/100/1000 LAN. Is it > possible to do an PXE-Boot with Linux? Do I need a special driver?
> Thanx
You might get an answer in the imaging forum
Jared L Jennings, CNE
Novell Support Forums SysOp.
http://support.novell.com/forums/faq_nntp.html
Posting with XanaNews Reader 1.15.7.4
Geek by Nature, NetWare by Choice.

Similar Messages

PXE Boot With intel Based IMAC

Hello,
I am trying to boot my IMAC from the network with PXE Boot with no success.
I found some documents (very little) about how to boot mac from network using diffrent mac with app called netboot, but i assume that because my imac is intel based it should be able to boot from PXE.
Are there any documents information you could point me to ?
Thanks.

U.S. websites for those companies don't show those models on their product lists or at support. If your iMac recognizes your printer, don't worry about the driver, it's there.

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

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

T400s Linux/Windows dual boot with Linux from Esata Flash Drive

This project is about a dual boot Windows/Linux system without using the normal dual boot changes in the bootloader of the windows hard drive. When I started this I found bits and pieces of information on the web but no complete description so I wrote this post.
I have done a dual boot system on my previous Thinkpad where I had partitioned the hard drive between Linux and windows. For this project I wanted to leave the windows hard drive absolutely intact and unaltered, and boot Linux from a flash drive in the esata port on the back of the T400s. Obviously this uses the F12 boot list function key to boot from the flash. The advantage of this is that Windows is totally unaltered and when I need Linux, I plug in the esata flash drive, hit F12 during the boot cycle and select booting from the esata flash drive. The reason for Esata rather than USB is simply speed. I have a nice fast Linux installation.
I used the OCZ esata flash drive but suspect any of the alternatives will work. It did not need the accessory usb cable because the Thinkpad powered the esata flash directly.
To boot from the esata drive I had to make the following changes in the bios
    I left the esata flash plugged in as I went into the bios
    Bios>config>Serial ATA and changed the Sata controller mode option to compatibility
    Restart and back into the Bios
    Bios>startup>boot - in my case the esata flash drive showed up as ATA HDD2 and was excluded from the boot order so I had to un-exclude it and move it to the point in the boot order that I wanted.
Next I downloaded a linux installation iso and put it on a CD - in my case opensuse. Then booted from the CD
From now on this instructions are specific to opensuse and yast but can be generalized to whatever Linux is being used.
In my case yast came up with a good set of suggestions for automatically partitioning the flash drive but then crashed during the partitioning itself. So I rebooted and specified the partitions manually.
    A fat32 partition left as a partition which both windows and Linux could see (in my case about 20% of the drive) (/dev/sdb1)
    An extended partition with the remainder of the drive (/dev/sdb2) which contains the following logical partitions
    A linux Swap partition of 2GB (/dev/sdb5)
    A linux /home partition –the remainder of the drive (/dev/sdb6)
    A linux /root partition of 8GB (/dev/sdb7)
Yast automatically suggested mount points of C,D,E for the windows partitions. Unfortunately because of the way the Thinkpad hard drive was laid out Yast had C assigned the ThinkPad Service partition and D assigned to the SW_Preload (or main windows partition). However there was an edit function that allows for the reversal of those mount points so that the windows C drive is mounted in Linux as Windows/C thereby avoiding confusion. I had already backed up and removed the Thinkpad factory install data so I did not have to deal with that. Yast suggested Windows/E for the mount point of the FAT32 partition on the flash drive, which I accepted.
The yast install configurator made all this manual selection easy, and after the manual configuration the partitioning worked perfectly.
Next step was Linux user configuration which went fine
Next was booting.
In the section management tab
    delete the windows 1 and 2 options (since we are not dual booting directly)
In the boot loader installation tab
    uncheck boot from mbr ( this stops the install from installing Grub and dual boot on the windows c drive
    check boot from root partition (this installs grub and all associated files in the Linux root partition (/dev/sdb6)
I believe that the correct procedure at this point is to click Boot Loader installation details which will bring up the Grub device map. In the device map there will be a line for the fixed hard drive (aka the windows drive) and a line for the esata flash drive. When the installer started up these were in hard drive and esata drive order. However when we boot directly from the flash the esata drive will be grub drive hd0 and the fixed hard drive will be grub hd1. The device map order needs to be changed to reflect this ie the esata drive should be first not second.
I did not do this and ended up initially doing Grub command line editing to boot and later manually editing the grub files using information I had previously learned the hard way and through google.
At this point let the installer go ahead and install Linux. After doing this it should come back and tell you to reboot. Do not do it yet because we need to install the MBR into the flash drive.
I suspect that there is a way of doing this in Yast running from the Live CD but it was not obvious to me so I used the manual method that I have used before.
Open a root terminal
Mount /dev/sdb6 to /mnt/sdb6 (my linux root)
Touch /mnt/sdb6/boot/grub/flag
The purpose of this is when we go looking later at the grub command prompt we need an easy to find unique file
Start grub and do the following
#grub
            grub> find /boot/grub/flag
                (hd1,5)    -- the result of the find in my example
            grub> root (hd1,5)   -- using the result of the find in my example
            grub> setup (hd1)   -- install mbr -- my example parameters - if you get this wrong you will trash some other drive!!!
                  hopefully grub announces success
            grub> quit
Reboot and select the flash drive. In my case I still had the grub devicemap wrong and had to edit the grub commands during boot to tell grub how to find the correct partition and then edit them again after booting
Typical linux install issues that we all always seem to have and can be solved with a little (or a lot of) google research.
As I said at the beginning I now have an untouched windows installation and a nice fast Linux installation. I hope that this will be of some use to someone.

Hi chrissh
i tried this exact procedure... on the exact same notebook (T400s). However, as soon as I set the
   Bios>config>Serial ATA to "compatibility", I cannot use my default Windows installation! I immediately get the "blue screen of death".
I doubt I did anything differently since this is the first step of your procedure and my laptop is brand new!
any idea?

Type 2 Virtual Machine in Hyper-V will not PXE boot with WDS

Hi
Bit of a wierd scenario this but I'm doing a bit of a lab experiment kind of thing. The setup is as follows:
VMWare Workstation 10 with Windows Server 2012 R2 running as a virtual machine. In VMW10 I have a NAT network interface and a Bridging interface set to load with the virtual machine. These seem to work fine (although the NAT doesn't seem to want to connect
to the internet but that's why the bridging one is there in addition).
Server 2012 is configured with the following roles:
ADDS, DHCP, DNS, Hyper-V, Printer, WDS
I have correctly configured WDS to work on the same machine as DHCP and I can get PXE boot working with WDS on a Type1 Virtual Machine in Hyper-V using the Legacy Network adapter. My problem is when I try and PXE boot on a Type2 Virtual Machine (this type
is new in R2 and should eliminate the need for a legacy network adapter) using the same network interface that I used for the Type1 machine, I get an IP address from DHCP but WDS doesn't seem to respond. Instead I get the "PXE-E16: No Offer Received"
message. I have tried just about everything I can think of and spent the whole day trying to figure out why this is the case but came up with nothing. Has anyone else encountered this or can anyone shed any light on the matter?
Many thanks in advance

"VMWare Workstation 10 with Windows Server 2012 R2"and "Server 2012 is configured with the following roles: ADDS, DHCP, DNS, Hyper-V, Printer, WDS"
Hyper-V is not supported to be run as a VM. It is a Type 1 hypervisor, which means it works on the bare metal. You have it running as a VM on a Type-2 hypervisor, so it has no access to the bare metal. Yes, VMware may have made it so some
things work in that environment, but it is not a supported (or tested) environment for Hyper-V.
.:|:.:|:. tim

GE70 dual booting with linux

Has anyone installed linux as a dual booting OS on their MSI laptop? I've gone through a lot of stuff online to try and install, but the UEFI isn't recognizing anything I have as far as live booting dvd or usb. I've turned off secure boot and fast boot. I can get it to boot off the disk/usb in Legacy mode, but if I install from there it installs as MBR which can cause problems. If anyone's had success, please, let me know.
Thanks!
B

If the laptop came with Win 8 pre installed then bios is set to UEFI, a new measure made by Microsoft to ensure nobody tries to boot other system rather than windows. The only way to boot a linux is to change bios to Legacy and then try to boot, after that, to boot windows you have to change that setting again, so not very efficient really.
My advice is to reinstall windows but in Legacy mode, there is software on the internet to check your windows key and reinstall.
All in all, while you have Windows in UEFI mode forget about dual booting, reinstall windows on Legacy or just erase it and go for linux.

Server 2008 configured for PXE boot with UIU and GhostCast

Right now, I am in the process of switching over from UIU 4, to UIU 5, and the implementation is completely different. We used GhostCast to push images out before, but the new UIU uses WIM files to pull the drivers off the server. I had a few
questions about reconfiguring the new server.
Currently, we have a server 2003 machine running ghost cast. It pulls its images off of a server 2008 machine. The server 2008 machine can be accessed remotely. So my first question is, can this be configured to allow remote connections
with the new setup?
The things I have been reading have said that you need to enable DNS, AD, and DHCP, however if we connect this to a WAN, will it conflict with that? Or can we configure only one of the ethernet ports to see this? Sorry kind of new to this.
I guess my main concern is, can we set up a separate domain for GhostCasting, while still being connected to an external domain?

Hi,
I’m not sure what you really want to do. For PXE boot, I think DHCP is always required just like Microsoft deployment solution WDS and MDT.
The two products are third products, so I don’t know the detail information about how they work. Based on my experience, they should be based on broadcast or multicast.
If so it could be a bad idea if you install it on a server facing the internet.
I think you can also ask in the third party forums that provide the products.
Thanks for understanding.

PXE Boot with UEFI. WDS not sending WinPE wim

I am trying to test PXE booting on devices that only have UEFI and no CSM support.
We are running Windows Server 2008 R2 in our environment.
On the DHCP server, we have option 66 and 67 set. If I change option 67 to SMSBoot\x86\wdsnbp.com and boot a traditional BIOS system (non UEFI) the SCCM server responds and gives me the option to hit F12 and PXE boot. This works without issue and can deploy
images.
I then change option 67 to SMSBoot\x64\wdsmgfw.efi and use a machine that is pure UEFI (meaning UEFI without any legacy support / CSM). The system appears to successfully download the wdsmgfw.efi and font file via TFTP as shown in the WDS logs. However, it
then goes to the next sreen where it is trying to contact the WDS server. AFter retrying for a while it will error out with error 0x102 which I believe translates to ERROR_TIMEOUT
The SMSPXE.log repeats the following:
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="2046820352" ServerName="" ServerRemoteName=""><Machine><ClientID>8908f9c4-c345-49ba-b137-af7b0b983584</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="GAS20043" OfferIDTime="7/24/2013 3:12:00 PM" PkgID="GAS00037" PackageVersion="" PackagePath="<a href="http:///SMS_DP_SMSPKG$/GAS00038">http://<IVE
REMOVED THIS>/SMS_DP_SMSPKG$/GAS00038" BootImageID="GAS00038" Mandatory="0"/></ClientIDReply>
SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
00:50:56:01:00:82, DF6A0C42-F909-B518-7B44-3150B662200B: found optional advertisement GAS20043 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Looking for bootImage GAS00038 SMSPXE 7/24/2013 7:14:58 PM 7724 (0x1E2C)
Any idea what may be going on?

Hey,
I am having the following situation:
DP1 = Windows Server 2008 R2 SP1 (Standalone Primary Site Server SCCM 2012 SP1 CU2)
DP2 = Windows Server 2012
UEFI Client: Microsoft Surface Pro (with Microsoft Surface Network Adapter)
BIOS Client: HyperV Virtual machine with Legacy network adapert
DP1; DP2 and DHCPServer all in Subnet1.
(IP Helper is set for DHCPServer for DHCP and for DP1 & DP2 for DHCP and BootP - I checked serveral times if everything is right here)
UEFI Client and BIOS Client in Subnet2.
Situation1 -- Using no DHCP Options and both DPs(DP1 and DP2) WDS running:
UEFI Client - Boots perfectly (contacting Server DP2)
BIOS Client - Boots perfectly (contacting Server DP2)
Situaion2 -- Using no DHCP Options and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Does not boot (no Bootfilename recieved)
Situation3 -- Using DHCP Options(Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Does not boot (no error information is provided)
BIOS Client - Boots perfectly (contacting Server DP1)
Situation4 -- Using DHCP Options(Option 60="PXEClient" Option 66="IP of DP1" Option 67="SMSBoot\x86\wdsnbp.com") and WDS just running on DP1:
UEFI Client - Boots perfectly (contacting Server DP1)
BIOS Client - Does not boot (taking hours to recieve dhcp options..)
My problem is i am having a lot of location with 2008 R2 SP1 server only (this is why situation 1 is not enough for me :-( ).
Based on this article:
http://ccmexec.com/2013/05/configmgr-2012-uefi-and-pxe-boot-support/
x64 UEFI Devices should work with Server 2008 R2 SP1 (not only Server 2012).
Interesting is I am having ALL files on Server 2008 R2 SP1 like they are on Server 2012 (in SMSBoot\x86 folder, too!)??
Some more ideas?
Thank you for help

PXE booting diskless Linux clients?

I currently have a Linux server that uses a combination of DHCP, TFTP, and PXE to boot a series of Linux clients. I would like to replace the Linux machine with a Leopard Server machine, but I don't see how to configure the Leopard DHCP daemon to send the same information.
For reference, here is a section of the Linux dhcpd.conf file:
host goldchannel {
hardware ethernet 00:50:8d:98:f4:8a;
fixed-address 192.168.0.51;
server-name "ISN";
option host-name "goldchannel";
option root-path "/diskless/goldchannel";
if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
filename "/vmlinuz_arch";
} else if substring (option vendor-class-identifier, 0,9) ="PXEClient" {
filename "/pxelinux.0";
There is also a TFTP server running, but I have seen instructions on how to configure a Leopard server the same way.
Any ideas or pointers would be greatly appreciated.

It looks like you want and need to define extra DHCP option fields.
This is not covered at all in the official Mac OS X Server PDF documentation, but if you open a Terminal window and type *man bootpd* then it will give you some information on this subject. It basically involves manually editing the /etc/bootpd.plist configuration file.
If you look at my previous post here http://discussions.apple.com/click.jspa?searchID=5850185&messageID=6021307 then you will see I am trying to work out how to use this feature as well.
Please let me know by posting a reply here if you get any further than me as I could not get it to work. I have seen a couple of vague comments from other posters suggesting they may have got it working but unfortunately they do not provide details.
Obviously if you do get it working then please post enough of your /etc/bootpd.plist file to be an example.

Windows 8.1 will not boot after setting up dual-boot with Linux Mint 17.1 Cinnamon

In which forum should I ask this question?
After installing Linux Mint onto a partition of my hard drive, Windows 8.1 is listed a choice to boot into after restarting my computer, but will not boot up. It suggests a boot repair and to obtain Windows 8.1 from my distributor. I have seen on other forums
that this has not worked, and I was wondering if anyone here had any suggestions for how to proceed.
Thanks in advance.

You can try them over here.
http://answers.microsoft.com/en-us/windows/forum/windows8_1?tab=Threads
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Question about Portege 2000 boot with Linux

Hi everyone,
My Portege 2000 PIII 750MHz, 512 RAM, 20GB is simply driving me mad. I would like to try to install Linux, and have downloaded some distros to try it. The point is I am using an external CD/DVD reader, with a 16 bit pc card connector cable. Booting starts until the BIOS is involved, but when it gets to OS drivers being involved, booting hangs up, with every distro, except of course win XP, with which it installs perfectly fine.
Anybody got any suggestions on how to proceed? I really would like something lighter than WXP on my machine. Thx!

Hi
I do not have this Portege but I know that Toshiba recovery image (WXP) contains driver for external ODD and the installation can be done without any problem.
Maybe you can find some useful tips under http://newsletter.toshiba-tro.de/main/index.html

[solved] Systemd hangs sometimes on boot with linux-ck

Hi i have linux-ck kernel installes and a Systemd-only init.
Sometimes it hangs on boot and then, instead of starting X / LXDM, drops to a commandline login prompt. It does not happen on every boot and never happend with arch stock kernel so far. I cant't login to search in systemd journal for errors because the keyboard does not work corret, e.g. if I press "o" it writes a "6"
here a shot from last time it happend. In the shot the last messages from Systemd are visible, but sometimes the screen is cleard before the login prompt appears.
Last edited by SiD (2012-09-08 07:51:58)

ok I activated syslog-ng and found this in the logs from last boot that not worked
Xorg log
# grep -e EE -e WW /var/log/Xorg.0.log.old
[ 1.932] Current Operating System: Linux sunny 3.5.3-2-ck #1 SMP PREEMPT Mon Aug 27 15:48:39 EDT 2012 x86_64
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 1.942] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 1.944] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 1.944] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 1.948] (II) Loading extension MIT-SCREEN-SAVER
[ 2.133] (EE) NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the
[ 2.133] (EE) NVIDIA(0): system's kernel log for additional error messages and
[ 2.133] (EE) NVIDIA(0): consult the NVIDIA README for details.
[ 2.133] (EE) NVIDIA(0): *** Aborting ***
[ 2.133] (EE) NVIDIA(0): Failing initialization of X screen 0
[ 2.133] (EE) Screen(s) found, but none have a usable configuration.
lxdm log
# cat /var/log/lxdm.log.old
** Message: find greeter (nil)
** Message: find idle (nil)
** Message: add xserver watch
X.Org X Server 1.12.4
Release Date: 2012-08-27
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.4.8-1-ARCH x86_64
Current Operating System: Linux sunny 3.5.3-2-ck #1 SMP PREEMPT Mon Aug 27 15:48:39 EDT 2012 x86_64
Kernel command line: root=UUID=3e32c396-fffb-4e00-b513-08db5c5da177 i915.i915_enable_rc6=1 ro initrd=../initramfs-linux-ck.img BOOT_IMAGE=../vmlinuz-linux-ck
Build Date: 27 August 2012 08:04:39AM
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Sep 3 18:45:01 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
NVIDIA: could not open the device file /dev/nvidiactl (No such device or address).
Fatal server error:
no screens found
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
Please also check the log file at "/var/log/Xorg.0.log" for additional information.
Server terminated with error (1). Closing log file.
** Message: exit cb
** Message: free session
arc 1
and in everything log
Sep 3 18:45:03 localhost systemd[1]: Startup finished in 1s 157ms 589us (kernel) + 2s 645ms 840us (userspace) = 3s 803ms 429us.
Sep 3 18:45:04 localhost dbus-daemon[317]: dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:04 localhost dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:04 localhost dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 3 18:45:04 localhost dbus-daemon[317]: dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 3 18:45:06 localhost systemd[1]: lxdm.service: main process exited, code=exited, status=1
Sep 3 18:45:06 localhost systemd[1]: Unit lxdm.service entered failed state.
Sep 3 18:45:06 localhost dbus-daemon[317]: dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:06 localhost dbus[317]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Sep 3 18:45:06 localhost dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Sep 3 18:45:06 localhost dbus-daemon[317]: dbus[317]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Seems to me there is a problem loading the Nvidia driver. Don't know if the dbus errors matter ...
EDIT:
Makes sence to me, without a graphics driver loaded X / LXDM can not start.
Last edited by SiD (2012-09-03 17:12:23)

E7250 will not PXE Boot with SCCM 2012 R2

Just received our new version Dell laptop the E7250. We are using SCCM 2012 R2 OSD to build our computers. We currently have 6 Dell computers (2 desktops 7010 and 790 and 4 laptops 6410, 6420, 6430 and 5440) that are using the same WIM file. Never had a problem with the network drivers until now with the E7250. It loads the WIM file but as soon as it says "preparing network connection" it fails. I hit F8 and try an IPCONFIG and I don;t see an IP address. So I'm thinking Network Driver issue, so I add the network driver to the Boot image and still can't get past "Preparing Network Connections". Any ideas?
Thanks

I got the same issue, both the Dell and Intel drivers only have Intel L217-LM drivers, the Latitude E7250s I've got need L218-LM drivers. I've tried older versions of the family driver package from Intel, but no good.
Perhaps its not the driver packages but rather SCCM 2012 R2 that doesn't pick up the 218 drivers in the packages, but I'm stuck.

GE60 2PE dual boot with linux

Hi,
I've little question: How to set up linux next to windows when I've formated Disk with GPT and I'm using UEFI ? Is there any chance that could work or I need to change to Legancy ?
That's all for help and have a nice day

Hello krzysi3qq,
I'm not sure what version of Linux you are using but if it supports GPT, just keep setting to UEFI. Or, you may need to change to Legacy mode and your partitions will need to reset and Windows will also need to be re-installed under Legacy mode.
BTW, MSI laptops doesn't support Linux.

PXE-Boot with Linux

Similar Messages

Maybe you are looking for