PXE Boot Problem

Hello everyone!
I've got a PXE boot server running and I can boot my EEE 701 from it without issue, it gets to the installer but then I get asked for the source of the packages. Now, I don't have an Internet connection to the boot server, so that's not an option. I know I can mount something to /src to have the packages show up, but what am I supposed to mount, and where?
Thanks in advance!
P.S: If you're considering "rtfm" or "Google" as a response as some did on the IRC, don't bother wasting your time to type
I mounted a USB stick with all the packages on to /src (I knew that had to be done) but I thought perhaps the installer would have mounted the packages from the tftp server to /src automatically. So now I don't understand the point of the separate installer CD?
Last edited by scottuss (2009-12-17 12:44:55)

hokasch wrote:
Hmm, do you mean the one from here? If so, it says "ftp-installation only", but I maybe should have made that more clear. I planned support for mounting packages from the tftp-server later (you need to set up nfs for that), but never picked it up again.
It is stitched together rather imperfectly, I just made it because there was no other way of getting an install on an old laptop.
I've totally gone around the houses
yeah, you could just have booted from an usb-stick, right?
Actually no! I had problems with that (although I've done it before) I got an error: "Boot device didn't show up after 30 seconds" and the workaround(s) at http://bbs.archlinux.org/viewtopic.php?id=77815 didn't help, so I figured I'd try the PXE boot.
Look, I'll be straight, I use Arch on an old box as a testing / development server for odd jobs. I left Arch as a desktop user a long time ago for Ubuntu where things "just work" - I don't have time to fix things constantly breaking on my main desktop. I thought I'd give Arch another go as a desktop OS on my EEE but I don't have the time (or inclination) to mess around with it anymore.
Ubuntu is installing from a USB stick as we speak.
Don't get me wrong: I LOVE Arch, as a headless, non-important playing around OS, I don't think I'll be using it as a desktop
P.S: Using Ubuntu has NOTHING to do with the skill level of anyone who chooses to use it. I HATE elitism! (rant over!)
Last edited by scottuss (2009-12-17 15:08:40)

Similar Messages

W530/T530 PXE boot problem again

Our latest W530s and T530s won't load the OS off the PXE server
Previously, we only had to set the bios as discussed here
http://forums.lenovo.com/t5/X-Series-Tablet-ThinkPad-Laptops/Can-t-PXE-boot-Windows-8-models/td-p/98...
Under Security, we turrn Secure Boot off
Under Startup, we st UEFI/Legacy Boot to both with legacy first and CSM on
Under restart, we turn the OS Optimized defaults off
That's been working for months.
Now, the W530 (and T530) find the PXE server, we select the remote boot options, and it just hangs before (or as) it loads the boot.wim
No error message, it just sits there.
Has anyone else experienced this? Is there some sort of bios upgrade that caused this?
Thanks.
Solved!
Go to Solution.

We are aware of the problem with LANDesk but I don't have any fix outlook. You can get previous BIOS versions from the download page:
http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS029170
Scroll to the bottom and you'll see all the previous versions. Note that to downgrade to a previous version you need to disable rollback prevention which is an option in BIOS Setup (look in the Security -> UEFI BIOS Update Option menu)

PXE boot problem: guest VM DHCP request packets not able to reach DHCP server

Hi Gurus,
I'm wondering if anyone could help me with this problem. I wanted to install Linux on Oracle VMs using PXE. I set up a DHCP server and the OVM running RHEL6.4 box. The DHCP server worked fine since other PHYSICAL servers could get IPs from this DHCP server. However, DHCP requests from Oracle VMs was not able to reach the DHCP server. So I suspect this is a VM-specific issue.
If I type in "dhcp net0" on gPXE prompt on the OVS machine(sappire), I can see the requests were being sent from the OVS server (sapphire):
gPXE> dhcp net0
DHCP (net0 00:21:f6:00:00:00) .............................................Connection time out (0x4c106035)
Could not configure net0: Connection time out (0x4c106035)
gPXE>
[root@sapphire ~]# tcpdump -i any -n udp dst portrange 67-68
tcpdump: WARNING: Promiscuous mode not supported on the "any" device
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
20:47:25.606400 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
20:47:25.606549 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
20:47:25.606559 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:21:f6:00:00:00, length: 387
^C
12 packets captured
14 packets received by filter
0 packets dropped by kernel
But if I snoop the same on the RHEL6.4 server running DHCP server and OVM, no request can be seen:
[root@bluestone Desktop]# tcpdump -i any -n udp dst portrange 67-68
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 bytes
^C
0 packets captured
0 packets received by filter
0 packets dropped by kernel
OVS(sapphire) and OVM(bluestone) are located in the same subnet:
[root@bluestone network-scripts]# ifconfig -a
eth0      Link encap:Ethernet HWaddr 00:14:22:72:7C:27
          inet addr:192.168.2.48 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::214:22ff:fe72:7c27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:106795 errors:0 dropped:0 overruns:0 frame:0
          TX packets:122056 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:59173975 (56.4 MiB) TX bytes:25362955 (24.1 MiB)
[root@sapphire ~]# ifconfig -a
10049df2fc Link encap:Ethernet HWaddr 8A:C5:05:83:AF:C9
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:80 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33200 (32.4 KiB) TX bytes:0 (0.0 b)
eth0      Link encap:Ethernet HWaddr 00:1A:64:64:DA:64
          inet addr:192.168.2.202 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:37664 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38939 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4537897 (4.3 MiB) TX bytes:23127790 (22.0 MiB)
eth0:0    Link encap:Ethernet HWaddr 00:1A:64:64:DA:64
          inet addr:192.168.2.212 Bcast:192.168.2.255 Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[root@sapphire ~]# brctl show
bridge name    bridge id        STP enabled    interfaces
10049df2fc        8000.8ac50583afc9    yes        tap7.0
                            tap7.1
                            vif7.0
                            vif7.1
I turned off iptables and SELinux on the DHCP server, the issue still remained.
Any help will be highly appriciaited.
Thanks in advance,
Alex

Hi,
- Do you install Oracle VM Server (OVS) on an emulated environment like Oracle VM VirtualBox ? if yes so you can't do it.
- Don't forget to configure the Virtual Machines Network and also to add this network to this Virtual Machine.
I hope this can help you
Best Regards

Wds pxe boot problem

I tried to deploy remote os installation from wds on intel D915GAV board which has no builtin NIC, so first i install TP-Link Nic on one of PCI slot and add this NIC driver to Boot.wim on wds but still no booting from wds ............ pls help me anyone
thanks

yes already checked that firmware upgrade and PXE has enabled.............. i also try TP Link NIC in Intel DG41RQ board but same no booting from wds and error appear for media failure check cable etc. while on DG41RQ builtin NIC it boot from same wds

E540 PXE Boot problem

Hi ;
I just buy lenovo E540 and when I try to upgrad windows 7 to windows 8 which on cds that i get with the lap
i get this error message when i turn my laptop on intel
UNDI PXE-2.1 (build 083) Copyright (C) 1997-2000 This product is covered by one or more of the following patents:US5, 307, 434, 872, US5, 732, 094, US6, 570, 884, US6, 15, 776 AND US6, 327, 625 Realtek PCle FE Family Controller Series v1.23 (07/28/10) PXE-MOF: EXITING PXE ROM.
and plz I need contect number of custermer server in Egypt ..
plz I need help as fast as possible casue I have an assigmet to deliver plz
Moderator Note; subject edited

If you received the Windows 8 discs with the system from Lenovo there will be some instructions included on how to use thos discs and and changes which you may be required to make in BIOS before using them. The same or similar to these;
http://download.lenovo.com/pccbbs/options/en_sp40e37996.pdf
How to contact support; http://support.lenovo.com/en_GB/feedback/detail.page?LegacyDocID=MIGR-76613
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

Problems PXE booting Gen 2 Virtual Machines after Upgrading to Windows Server 2012 R2

My Current Setup:
I have two virtual machines set up with Hyper V on my Windows Server 2012 Server.
VM1: Configured to boot from an ISO file and runs Clonezilla server.
VM2: Configured to PXE boot using a legacy network adapter, and with a passthrough 250Gb hard disk.
These two VMs are connected to an external Virtual Switch, which allows physical machines to PXE boot to the Clonezilla server.
For the past few months I have been using this setup for two purposes:
1. To clone physical machines to the Clonezilla virtual server (as a backup).
2. To restore those image to the second VM if I find that need to get access to the files on the original image..
This has worked perfectly, except for the fact that the speed of the legacy network adapter on the second VM (which is required to PXE boot) is very slow. But I know this is because of the limitations in how the legacy adapter works...
Now my problem:
I found out that Gen 2 VMs allow you to PXE boot without having use a legacy network adapter, allowing me to image back to the VM faster. So I upgraded the Server to Server 2012 R2 . I then created the same two virtual machines on the R2 server. I can still
PXE boot the Gen 1 VM to the Clonezilla Server but I cannot get the Gen 2 VMs to PXE boot properly. They get an IP address from the Clonezilla Server but then just stop with the following screen. (note: I have disabled the Secure Boot).
Are Gen 2 VMs unable to pull down images from anything other than a WDS Server?

Hi J,
>>Unfortunately WDS is not a solution for us as it is dependent on the PC being part of a domain
If you would like to make the client not join to the domain, please check the box before “Do not join the client to a domain after an installation.” In addition, make sure not to set the client to the domain in the unattend file and do not prestage
the computer in AD. "
It is quoted from following thread :
https://social.technet.microsoft.com/Forums/windowsserver/en-US/1026c3a9-0a10-4a58-a48f-5391659a96c8/wds-set-unattend-file-for-workgroup?forum=winserversetup
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Problems using PXE boot to jumpstart an HP client

Hello folks,
I have a Sparc jumpstart server that I am trying to use to jumpstart an HP with Solaris x86. I have gotten the x86 installation stuff installed by mounting the DVD on an x86 system and NFS exporting it to the jumpstart server. This seemed to work just fine.
My problem is PXE boot and DHCP. I have exported the appropriate directories, I have set up the DHCP service, and I can see on the client machine's console that it receives its IP address, but then I get the message "No filename or root path specified." I have a macro defined that points to the pxegrub file, and everything seems to be set up correctly. Does anyone have any thoughts on what I am missing?
Edited by: user13373794 on Feb 10, 2011 11:24 AM

Well, we managed to solve the problem with DHCP and PXE boot on the HP Proliant, at least the problem I first posted above. We have run into another problem. Apparently, the problem we had was twofold. First there is some sort of bug in the HP that if there is an LOM on the system you can't use the first network interface to PXE boot, it produces the error message about not finding the filename or root path. So the solution to that was to switch to the second network interface and change the DHCP server to answer that MAC address.
Making changes to the DHCP config on the Solaris jumpstart server somehow made it stop serving IP addresses to the client. As a last ditch attempt we shut down DHCP with the svcadm command and restarted it. This fixed that problem and now the PXE boot finds the pxegrub files and the installation starts up.
Now there is a new problem. We want to do a hands-off jumpstart, but the system pops up an X window and asks for keyboard type and some network and timezone info, and a root password. Then the install seems to proceed to use the profiles listed in the rules.ok file on the jumpstart server. So it does seem to be getting some config options from the jumpstart server, but not enough to be completly hands-off. Is there something we can add to the rules file or beginning script or something to fix this? Anyone have experience or even just a good guess?

T61s, T60s & older model unable to PXE boot to SCCM (MAC address problem)

Hi,
We have a series of T60, T61 & older machines that are unable to PXE boot to SCCM. The T400 & X series & other newer models can boot just fine.
After checking further, we realised that only a certain range of MAC addresses are unable to pxe boot i.e
00-1A-XXXXXXX
00-1C-XXXXXXX
range.. all the other range of MAC addresses are fine to boot via network.
The error when doing network boot is "bad or missing discovery server list"
Also, we are running on SCCM 2012 at the moment. Our branch office who is running SCCM 2008 can have all the machines - regardless of models & brand boot just fine.
Any ideas? Much appreciated.

did it obtain IP address from DHCP server? is DNS server address is configured in DHCP scope? can you ping using IP address?
if drivers are proper will suggest to update it in boot media & enable command line support to make it easy for deployment & troubleshooting.
Prashant Patil

Problems with PXE boot for clients

Hi,
I have an environment where I have clients on av VLAN connected to a Cisco 2960X (WS-C2960X-48LPD-L ) with layer 3 configuration. The clients do a PXE boot to get configuration. The thing is that this does not work on all switches. The switches have the exact same configuration, the only thing that differs is Hardware Board Revision Number. (That I can find..) The ones that works has 0x05 and the ones that doesn´t work has 0x12. The PXE server is connected on a different VLAN in the same switch.
I have configured spanning-tree portfast on the interfaces. I have ip-helper on the VLAN. The PXE server is also the DHCP server.
Any suggestions?
Regards,
Carina

It seems NIC teaming was configured really incorrectly in this case. Different switches require different configuration with specific settings on the Windows Server side. Sometimes incorrect configurations work when network traffic is low but start behaving
funny when it increases. The reason behind this is Windows hosts sending back answers to its peers via different physical links, and the switch doesn't expect it and drops "incorrect" frames.
You can find detailed description of different teaming modes here:
http://www.aidanfinn.com/?p=14004
If you use LACP, be sure to set up port channel on Cisco switches or LACP trunk on HP switches. Otherwise you might want to use the Switch Independent mode.
Evgeniy Lotosh
MCSE: Server infractructire, MCSE: Messaging

Yoga 2 Pro PXE boot?

Looking to PXE boot a Yoga 2 Pro so I can create/restore images with Microsoft WDS. Since Yoga 2 Pro does not have a built-in Ethernet jack, does anyone know if it's possible to do this with a USB Ethernet adapter?
Would it have to be a Lenovo-branded apdater, or can any brand Belkin, TP-Link, etc) work?

How did you get this to work sir?? I have been trying for a solid week and it never see the Lenovo ethernet dongle as a boot option no matter what I choose in the BIOS. I have the X1 Carbon and it works as you would expect it to. But it NEVER works on the YOGA 2 PRO. CAn anyone help me?? The BIOS clearly has an option to boot the dongle thats made by LENOVO but the dongle never ever shows any lights no matter what port its in or regardless of the settings vchanged in the very small bios. I have wasted atleast 60 hrs + trying to figure out how to boot with it and it doesnt work at all. I had to end up making a bootable discover USB to help it find my wds server. Altough now when ever I attempt to drop an image to it it fails right at FINISHING up and finishes with a "corrupt installation file" error message. To make things more confusing is I can drop this same "Corrupt" image to our X1 carbons without a problem. Can anyone guess why??

PXE boot issue with DHCP and SCCM server on different subnets

I'm working with a client on the operating system deployment module of SCCM.
Their network configuration currently has a single large subnet for client
computers with a DHCP server on the same subnet. The SCCM subnet is
configured on a seperate subnet with no DHCP server on the subnet. We want to
configure client computers to be able to boot using the PXE client to deploy
OS images to the machines but can not get PXE-boot to work correctly.
Also, the client does not want to make changes to their network
infrastructure routers or switches to remedy this problem. Are there settings
on the DHCP or SCCM servers we can implement to make this work? If so, what
needs to be installed or configured on each server. We currently already have
WDS installed on the SCCM server and the SCCM server is configured as a PXE
Service Point within SCCM. Both WDS and the PXE Service Point seem to be working fine.
Any help would be appreciated.
Thanks,
Gary

I am Brazilian,
sorry for wrong english
My DHCP is on linux,
in my own structure VLANS
The system center is on the network
10.0.4.0/24
The machines on the network 10.0.5.0/24
The problem is that the machines that
are not on the same network system center
can not boot
I tried configuring / etc/dhcp3/dhcpd.conf
follows
option vendor-class-identifier "PXEClient";
option bootfile-name "\
\ SMSBOOT \ \ x86 \
\ wdsnbp.com";
option tftp-server-name
"10.0.4.101"; ---->
IP server
But it did not work, anyone know
how to configure?

Screen resolution when PXE boot from WDS vs Install Windows 8.1 from USB

Hi all
I own a Lenovo ThinkPad T430s, X230 Tablet, and now have my hands on a T440. All three machines have UEFI Secure Boot enabled properly, i.e. Windows boot screen shows Lenovo logo instead of Windows logo.
However, if I do a PXE boot (using Windows Deployment Services from Windows Server 2012, not R2) and boot to the same boot.wim provided on a Windows 8.1 ISO image, the boot screen resolution turns crap, and the WinPE environment runs in 640x480. Also, as opposed
to the Lenovo logo showing on the boot screen, the Windows logo shows up instead, indicating it's not doing a secure boot?
When booting from a USB stick however, using the same Windows 8.1 boot.wim (copied from ISO), the screen resolution in Windows Setup is detected correctly, and the Lenovo logo shows up.
This occurs on all three machines since MDT was upgraded to MDT 2013 or when I replaced Windows 8 boot.wim with Windows 8.1 boot.wim (as the Windows ADK 8 --> ADK 8.1).
Is there a fix for this? Do others have the same problem elsewhere?
Many thanks

Hi,
When boot UEFI-based computer from PXE you should take more into consideration.
For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode.
Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode.
How to Create a PXE-Initiated Windows 8 Deployment for UEFI-Based or BIOS-Based Computers in Configuration Manager
http://technet.microsoft.com/en-us/library/jj938037.aspx
Especially for “Pre-Deployment Considerations”
If you still cannot find a way to make it boot from UEFI mode, you should contact with manufacture to confirm if PXE-initiated boot is supported.
Hope this helps.

Capturing an image to use for PXE boot

I'm using Windows Deployment Services in conjunction with Windows Deployment Terminal (Windows Server 2008) to capture an image from one of our workstations to use as a PXE boot image for future computers. I've created the capture image and PXE booted
to that image, which brings up the "Image Capture" wizard. After capturing the image, I created an install image in WDS using the same .wim file. After trying to PXE boot, the workstation yet again brings up the "Image Capture" wizard.
I then right clicked the image under Boot Images (in WDS) and selected "Create Discover Boot Image." A loading window pops up, but always ends with an error saying something to the extent of the image doesn't have WDSClient Binaries. Does anyone
know what this is or how to fix this? Or even if I'm going about it the right way? If anyone has any advice, I'd appreciate it.

Hi,
Yes, you can.
Here are the rough steps:
1.
Install and configure the WDS Server.
2.
Add the Windows 7 boot image to WDS.
3.
Create a Capture Boot Image and add it to Boot Image.
4.
Create a reference Windows 7 computer (install Windows 7, Office and other applications as you like)
5.
Sysprep the Windows 7 computer.
6.
PXE boot the reference Windows 7 computer into capture image on the boot screen and then capture the image.
7.
Upload the captured image to WDS server.
8.
PXE boot clients, choose the captured image to install the system.
Please refer to this link
http://social.technet.microsoft.com/Forums/windowsserver/en-US/be3af7db-b71b-4b14-b166-fef83cde0ac6/deploy-windows-7-from-waik-with-some-application-added?forum=winserversetup
I had the similar problem couple of years back
UMESH DEUJA MCP,MCTS,MCSA,CCNA

PXE boot and video mode

Hello all,
I posted about this problem a while ago but now I have more information.
6.5 SP2 IR1.
The problem: Booting from CD results in a video mode with far more lines and
column than booting PXE. PXE is always 80x25, on many different hardware
types. I want it to be like the CD.
Theoretically, the video mode is controlled by the vga= parameter on the
kernel's command line. For PXE, the kernel command line comes from <imaging
server>\sys\tftp\cmds, various files therein. Here are the contents of a
typical file:
KERNEL boot/linux
APPEND initrd=boot/initrd vga=0x314 install=tftp://$TFTPIP/boot
rootimage=/root PROXYADDR=$PROXYADDR TFTPIP=$TFTPIP splash=silent
PXEBOOT=YES mode=5
Notice the vga= parameter.
I can modify this vga parameter any way I like, without effect. I have
tried:
- removing the parameter entirely
- setting it to ask
- setting it to vga_ask
- setting it to single-digit numbers e.g. 1, 2
- setting it to other 0x3nnn options
- setting it to extended
It should be possible for anybody to replicate this simply by changing the
vga parameter in one of your CMD files and booting that particular PXE
option. I suggest using "ask" as it is the one that would give the most
visibly obvious evidence of working or not working.
The boot loader for PXE appears to be linld.com. So, I took my PXE
materials and Novell's linld (to ensure same version) and ran them from DOS.
When I run them from DOS, the vga= parameter DOES have an effect; it behaves
exactly as it should.
So, the situation appears to be that linld launched via PXE ignores the vga
parameter while linld launched manually from DOS does not, on the same
hardware.
Working with linld under DOS yielded some interesting information. The text
files specifying the kernel command line parameters for PXE are not actually
in anything remotely like the format linld requires. Having KERNEL and
APPEND keywords is more characteristic of other boot loaders. If you run
linld without parameters under DOS, it gives you very terse command line
information, which is as follows:
LINLD v0.97
Syntax:
LINLD [image=<file>] [initrd=<file>] [vga=vgamode] [cl=<kernel cmdline>]
vgamode: ask,extended,normal or dec/oct/hex number
Use quotes: "cl=..." if you need spaces in cmdline
Use cl=@filename to take cmdline from file
So compared to the CMD file provided for PXE, what linld would really want
is this:
linld image=boot/linux initrd=boot/initrd vga=0x314 [email protected]
where params.txt would contain:
install=tftp://$TFTPIP/boot
rootimage=/root
PROXYADDR=$PROXYADDR
TFTPIP=$TFTPIP
splash=silent
PXEBOOT=YES
mode=5
(It's worth noting that things are actually even slightly more complicated,
because the variables used in the CMD file (e.g. $PROXYADDR) don't actually
work; I have not found any way to use variables on the command line.)
All this tells me that before Novell launches linld, it is internally
processing the contents of these CMD files and spitting out a command line
that linld can really work with. My experience indicates that the vga
parameter is being incorrectly handled in this process.
I cannot figure out where the DOS environment that must exist during the PXE
boot process is coming from. (There must be a DOS environment, because
linld is a DOS Linux launcher.) It was easy to tell with the old preworx
materials, because you could see the .bin files which were nothing but
images of DOS boot floppies; it was even possible to open them in
third-party PXE utilities. I see no comparable files in the current boot
materials. The only other interesting file is loadlin.dnx, but I suspect it
is not involved because the old preworx process had DNX files as well and
they served a different purpose. Consequently I can't look at what is
happening when linld is launched, so I can't get any further in trying to
figure out the problem.
I would be very interested to know whether anybody out there can get their
PXE materials to respond sensibly to vga=ask.
If you can, I'd be interested to know the dates and times of all the backend
NLMs, in case my problem is due to incorrect updating/version mismatch.
If anybody can shed light on the innards of what happens when linld is
launched during PXE boot, I would love to know.
Thanks,
Lisa.

Lisa,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://support.novell.com/forums/

PXE Boot and RIS not working

I'm trying to boot a toshiba SP6100 from ris but getting
PXE-T01:File not found
PXE-E3B: TFTP error - File not found
PXE-MOF: Exiting Intel PXE ROM.
No problem what so ever when booting other mashies (Other brands).
When trying to boot from a Remote boot disk i get:
Error: Could not found a supported network card.....
PC is running latest bios (1.9)
Any suggestions?

Hi
I have found an interesting Microsoft Knowledge Base Article Q304992.
It deals with the PXE Boot and RIS server method, perhaps it could help you!
Pelox

PXE Boot Problem

Similar Messages

Maybe you are looking for