Thanks Warner...
On Tue, Mar 19, 2019 at 05:14:15PM -0600, Warner Losh wrote:
> You need to set the NFS mount point properly.
I think I have? The 12.0 environment was basically a copy of a
functioning 11.0 PXE environment, and 12 worked fine with 11's pxeboot.
Regardless, turns out ne
On Tue, Mar 19, 2019 at 4:53 PM James Snow wrote:
> Hello -stable,
>
> We have a PXE environemt that builds FreeBSD-11 boxes. We've started
> to dip our toes into the 12.x waters, but have had trouble getting
> FreeBSD-12 to pxeboot. It would crash and burn like so:
>
Hello -stable,
We have a PXE environemt that builds FreeBSD-11 boxes. We've started
to dip our toes into the 12.x waters, but have had trouble getting
FreeBSD-12 to pxeboot. It would crash and burn like so:
Startup error in /boot/lua/loader.lua:
LUA ERROR: cannot open /boo
Hi,
today’s latest 11.2 rev 341671, when booting off local disk all is fine, but
pxeboot gets stuck after printing
FreeBSD/x86 bootstrap loader. Revision 1.1
(Fri Dec 7 09:45:34 IST 2018 danny-pe-44)
-
older pxeboot get slightly further, but hang too.
older root images
On 7/24/12 6:07 AM, Robert Blayzor wrote:
On Jul 23, 2012, at 1:58 PM, Bob Healey wrote:
I know I have this working, however I don't remember what I did. I know I can
pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp server/NAT
gateway. I do know the first thing in my
On Jul 23, 2012, at 1:58 PM, Bob Healey wrote:
> I know I have this working, however I don't remember what I did. I know I
> can pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp
> server/NAT gateway. I do know the first thing in my RHEL install script is
>
I know I have this working, however I don't remember what I did. I know
I can pxeboot and install RHEL on a 9K frame network from a FreeBSD tftp
server/NAT gateway. I do know the first thing in my RHEL install script
is to set the MTU to 9K.
If I have a chance later today, I'll di
Is it possible to PXEboot a diskless client with an MTU higher than 1500 (Ie:
9k) ?
The network we currently boot several diskless machines from has a lot of NFS
traffic and we'd like to enable them all for larger MTU's however the one thing
stopping us is the issue with initial boot
On Tue, Dec 02, 2008 at 01:48:17PM +0200, Danny Braniss wrote:
> latest pxeboot (7.1):
> mother-boardNIC/LOM CPU
> - --- ---
> Intel SWV25 em xeonworks fine
> SUN X2200bgeamd works fine
> DELL PE 29
latest pxeboot (7.1):
mother-boardNIC/LOM CPU
- --- ---
Intel SWV25 em xeonworks fine
SUN X2200bgeamd works fine
DELL PE 2950 bcexeonfailes 95% of the times
Hi,
Hmm for what's worth: I just upgraded a 6.2 pxe box using cvs to 7.0
release and it boots and runs fine, it seems. The server (still) runs 6.2
.
Cheers,
Robert
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
On Thu, Mar 27, 2008 at 05:17:23AM -0700, Jeremy Chadwick wrote:
> On Thu, Mar 27, 2008 at 12:44:25PM +0100, don Juan wrote:
> > On Client screen it can be seen:
> >
> > Loading /boot/defaults/loader.conf
> > /boot/kernel/kernel text=0x6fd45c ...
> >
> > and after that, server reboots.
>
> Pleas
On Thu, Mar 27, 2008 at 12:44:25PM +0100, don Juan wrote:
> On Client screen it can be seen:
>
> Loading /boot/defaults/loader.conf
> /boot/kernel/kernel text=0x6fd45c ...
>
> and after that, server reboots.
Please see this documentation, particularly step #10.
http://jdc.parodius.com/freebsd/p
I wander if pxeboot setup for FreeBSD 7.0 is different from pxeboot with 6.2?
I did sucessfully network pxeboot setup of Freebsd 6.2 using following
DHCP configuration, based mostly on this how to:
http://networking.ringofsaturn.com/Unix/pxeboot.php,
host host1
{
hardware ethernet 00:0c:29:1f
On Mon, Mar 26, 2007 at 03:16:15PM -0400, Ryan J. Taylor wrote:
> I compiled pxeboot with TFTP support by doing:
> cd /usr/src/sys/boot
> make -DLOADER_TFTP_SUPPORT
>
> I have clients booting via PXE and grabbing their root filesystem from a
> memory disk. However, there was a
Hi all,
I compiled pxeboot with TFTP support by doing:
cd /usr/src/sys/boot
make -DLOADER_TFTP_SUPPORT
I have clients booting via PXE and grabbing their root filesystem from a
memory disk. However, there was a long delay in the boot sequence.
tcpdump revealed that after downloading pxeboot
Hi all,
I can't emphasise enough how useful running a TCPDUMP on the server
in question is to find out what subtle thing it is that I missed.
Generally speaking a quick-crash like that is a file not being found like
the modules directory or something silly like that. If you dump the NFS
traffic
etails with the bare eye. I recorded it
> with a digital camera and a snapshot of it is here:
> http://www.lahaye.dds.nl/pxeboot/crash.jpg
> The whole boot process in plain text goes as
> follows:
> --
> Attempting Boot From Intel(R
w.lahaye.dds.nl/pxeboot/crash.jpg
The whole boot process in plain text goes as
follows:
--
Attempting Boot From Intel(R) Boot Agent Version
3.0.05 (PnP Device)
Initializing Intel(R) Boot Agent Version 3.0.05
PXE 2.0 Build 078 (WfM 2.0), RPL V2.73
Inte
Rob wrote:
Is it OK to have a double kernel read at the last
two lines?
Any idea what's wrong here or what I could do to
further test what the actual problem is?
Argh. I had this same problem as recently as October, but I can't
remember exactly what caused this. When I went back and re-did thin
On Sun, 11 Feb 2007 17:22:22 -0800 (PST) Rob wrote:
> I have a FreeBSD 6.1 PC as the server to a PXE boot
> of another Compaq Deskpro EN PC.
> The Compaq PC has the option of a "Network Service
> Boot" with the F12-key during BIOS boot up. On the
> server, tftpd, bootpd and dhcpd are all working
this:
read request for //pxeboot: success
read request for /boot/loader.rc: success
read request for /boot/loader.4th: success
read request for /boot/support.4th: success
read request for /boot/beastie.4th: success
read request for /boot/screen.4th: success
read request for /boot/frames.4th:
On Thu, 18 May 2006, Danny Braniss wrote:
DB> > DB> > At that point, lsdev shows the disk devices, but not the pxeboot
"disk", which
DB> > DB> > leaves me without a kernel, etc. So something is different between
the i386
DB> > DB> > and amd64
> On Thu, 18 May 2006, Danny Braniss wrote:
>
> DB> > At that point, lsdev shows the disk devices, but not the pxeboot
> "disk", which
> DB> > leaves me without a kernel, etc. So something is different between the
> i386
> DB> > and amd64 d
On Thu, 18 May 2006, Danny Braniss wrote:
DB> > At that point, lsdev shows the disk devices, but not the pxeboot "disk",
which
DB> > leaves me without a kernel, etc. So something is different between the
i386
DB> > and amd64 disks, or maybe there's a proble
llows: if I insert the 6.1
> i386 release CD, it all works great. If I insert the amd64 CD, then I get
> the
> following after pxeboot has been going for a bit:
>
> ([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006)
> Can't work out which disk we are booting from.Guess
book. All good so far. The problem is as follows: if I insert the 6.1
RW> i386 release CD, it all works great. If I insert the amd64 CD, then I get
RW> the following after pxeboot has been going for a bit:
RW>
RW> ([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006)
RW> Can't
i386 release CD, it all works great. If I insert the amd64 CD, then I get the
following after pxeboot has been going for a bit:
([EMAIL PROTECTED], Sun May 7 02:16:38 UTC 2006)
Can't work out which disk we are booting from.Guessed BIOS device 0x not found by probes, defaulting to
roblem was. Hardware is
> > exactly the same.
> > What have I missed?
>
> Maybe you had a corrupted pxeboot binary somehow?
I'm quiet sure that this can't be. I played arround with several CFLAG
options (-Os, -marchi486 etc.) and with several -DPXELDR_ALWAYS_SERIAL
etc. so I&#x
changed recently, and I had net4501
> > > boxes pxebooting fine with FreeBSD 5.3.
> >
> > Hmm. Int 6 is an invalid opcode exception:
>
> I have no ideay why, but over night I recompiled my PXEROOT system (BETA3
> now) and the problem vanished. I can't see any ch
ook up that eip address. In the loader here on my laptop
> it's in the write function:
>
> % nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort
> ...
> 00023b9c T readdirfd
> 00023c14 T write
> 00023d18 T lseek
>
> If you want to be able to use gdb, then rebuild libstand with debugging
> (make DEBUG_FLAGS=-g) and rebuild all of /sys/boot with debugging (make
> DEBUG_FLAGS=-g). You can then
> use /usr/obj/usr/src/sys/boot/i386/pxeldr/pxeboot for your pxeboot and
> you can run gdb on /usr/obj/usr/src/sys/boot/i386/loader/loader.sym and
> you can do listings of the addresses for eip, etc.
pgpj0zK68sjPU.pgp
Description: PGP signature
pop ebp
>
> I'm guessing that there's been a stack overflow or some such. Your eip
> is in the loader. You can try using the loader.sym from your loader
> binary to look up that eip address. In the loader here on my laptop
> it's in the write function:
Thanks for y
at eip address. In the loader here on my laptop it's in the write
function:
% nm /usr/obj/usr/src/sys/boot/i386/loader/loader.sym | sort
...
00023b9c T readdirfd
00023c14 T write
00023d18 T lseek
If you want to be able to use gdb, then rebuild libstand with debugging (make
DEBUG_FLAGS=-g)
Am Dienstag, 16. August 2005 19:52 CEST schrieb Brooks Davis:
> On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote:
> > Hello,
> >
> > I just wanted to ask if somebody had success with providing pxe boot
> > service under 6-BETA2.
> > I have two clients, one NET4501 wich just reboots af
a net4501 and BIOS versions higher than 1.24? Like
mentioned, the box gets DHCP info, loads pxeboot and after this message
immediately reboots:
CLIENT MAC ADDR: 00 00 24 C0 33 70
CLIENT IP: 172.21.1.248 MASK: 255.255.0.0 DHCP IP: 172.21.0.1
GATEWAY IP: 172.21.0.1
PXE Loader 1.00
Building th
On Tue, Aug 16, 2005 at 02:05:08PM +0200, Emanuel Strobl wrote:
> Hello,
>
> I just wanted to ask if somebody had success with providing pxe boot
> service under 6-BETA2.
> I have two clients, one NET4501 wich just reboots after fetching pxeldr via
> TFTP and a Laptop which just hangs when NFS-l
Hello,
I just wanted to ask if somebody had success with providing pxe boot
service under 6-BETA2.
I have two clients, one NET4501 wich just reboots after fetching pxeldr via
TFTP and a Laptop which just hangs when NFS-loading kernel.
I'm about to investigate further, but maybe someone can conf
On Fri, Jun 24, 2005 at 01:50:37PM -0400, John Baldwin wrote:
> It uses TFTP to fetch the pxeboot binary itself. After that, it uses either
> NFS or TFTP. By default it uses NFS to access /boot/loader and friends. If
> you want it to just use TFTP and not use NFS at all, you need to
On Friday 24 June 2005 01:03 pm, Brian Candler wrote:
> I have been setting up a pxeboot "jumpstart" environment for FreeBSD 4.11,
> following the instructions at
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/
>
> Rather than build pxeboot like this:
> # r
I have been setting up a pxeboot "jumpstart" environment for FreeBSD 4.11,
following the instructions at
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/
Rather than build pxeboot like this:
# rm -rf /usr/obj/*
# cd /usr/src/sys/boot
# make
# cp /usr/src/sys/boot/i386/pxel
> I'm trying to make very big MD_ROOT (300MB) sent using
> PXEBOOT+TFTPBOOT. No NFS. It's a sort of diskless machine with all the
> system on ram. There is a problem when the preloaded image is >~32MB.
> Kernel loads but it does not seem to find the files. It seems
> Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
>
> > Hi,
> >
> > I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT.
> No
> > NFS. It's a sort of diskless machine with all the system on ram. There
> is a
> > problem
On Tue, Apr 19, 2005 at 04:18:17PM -0700, David G. Lawrence wrote:
>
>I assume you saw this in the tftpd manual page?
>
> BUGS
> Files larger than 33488896 octets (65535 blocks) cannot be transferred
> without client and server supporting blocksize negotiation (RFC1783).
>
> M
> Hi,
>
> I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No
> NFS. It's a sort of diskless machine with all the system on ram. There is a
> problem when the preloaded image is >~32MB. Kernel loads but it does not
> seem to find the files.
> Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
>
> Marc Olzheim wrote:
>
> >On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote:
> >
> >
> >>Hi,
> >>
> >>I'm trying to make very big MD_ROOT (300MB) sent using PXEBOO
> Objet : Re: PXEBOOT/TFTPBOOT + big MD_ROOT problem
>
> On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote:
> > This is roughly how it works under our linux servers, webservers, etc...
> I
> > was hoping to avoid that approach (less work.. less maintenance..
On Tue, Apr 19, 2005 at 09:31:10PM +0200, Emmanuel Chriqui wrote:
> This is roughly how it works under our linux servers, webservers, etc... I
> was hoping to avoid that approach (less work.. less maintenance..).
>
> Am I the only one on earth to need a big MFSROOT ???
> :)
Hmm, I guess so. :-P
> -Message d'origine-
> De : [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] De la part de Marc Olzheim
> Envoyé : mardi 19 avril 2005 21:06
> À : Emmanuel Chriqui
> Cc : freebsd-hackers@freebsd.org; freebsd-stable@freebsd.org
> Objet : Re: PXEB
Marc Olzheim wrote:
On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote:
Hi,
I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No
NFS.
Any reasons for not using NFS ?
I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT .
(same pb with a 5.3).
Am I mi
On Tue, Apr 19, 2005 at 09:52:07AM +0200, Emmanuel Chriqui wrote:
> Hi,
>
> I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No
> NFS.
Any reasons for not using NFS ?
> I use i386/5.4RC2/TFTPD/PXEBOOT+TFTPBOOT .
> (same pb with a 5.3).
>
Hi,
I'm trying to make very big MD_ROOT (300MB) sent using PXEBOOT+TFTPBOOT. No
NFS. It's a sort of diskless machine with all the system on ram. There is a
problem when the preloaded image is >~32MB. Kernel loads but it does not
seem to find the files. It seems as if only part of
On Wed, Apr 13, 2005 at 07:06:32PM +0200, Helmut Allwang wrote:
> Hello,
>
> it was possible for me, to boot a bootable floppy-image over pxeboot.
>
> Is it possible to boot a CD-image over pxeboot?
You mount the image (mdconfig + mount_cd9660) on your tftp server and
off you
Hello,
it was possible for me, to boot a bootable floppy-image over pxeboot.
Is it possible to boot a CD-image over pxeboot?
Please cc me your answers.
Thank you all,
Helmut
__
Verschicken Sie romantische, coole und witzige Bilder
attached to the very same
controller I wanted to give 5.x a try, and this is what I get from an
attempt to boot 5.3-RELEASE floppies with 5.3-p5 pxeboot compiled with
tftp support. Can anyone tell me what I'm doing wrong? I can provide
part numbers, exact BIOS versions, whatever is deemed relevant.
T
On Wed, 23 Jan 2002, Michael Smith wrote:
> You can rebuild and reinstall just libstand; it is self-contained and has
> no particularly special issues.
Thanks for the tip. I recompiled libstand and loader picked it up out of
the /usr/src tree, so I didn't even need to install it.
> Glad to have
and the Intel PRO/100 S NIC. There are no hard drives or floppy drives
> in the system. This machine used to be my server until I replaced it a few
> months ago with a new machine.
ok, so till someone can shed some light from the BTX dump (hint hint), check
1) if the pxeboot is ok
2) try tc
On Tue, 22 Jan 2002, Danny Braniss wrote:
> im no expert in reading btx dump, but from past experience, upgrading the
> firmware of the BIOS/NIC solved the problem.
Before I posted my first message, I flashed the last Boot Agent onto the
NIC, and after seeing your message, I hunted down and flash
> On Mon, 21 Jan 2002, Ladislav Kostal wrote:
> > On Sun, 20 Jan 2002, Jason K. Fritcher wrote:
> > > I'm trying to get a machine to netboot with the pxeboot loader and a Intel
> > > PRO/100 S network card. I built pxeboot with tftp instead of nfs support,
>
On Sun, Aug 05, 2001 at 08:39:56PM +0200, Hartmann, O. wrote:
[...]
> But pxeboot in /boot/ seems still broken! We cn not boot any diskless
> station (AMD based systems) here with the most recent image of pxeboot.
> To make the stations working we have to use a backuped imag from the 31
Gerhard Sittig <[EMAIL PROTECTED]> probably said:
> > Listening on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0
> > Sending on BPF/fxp1/00:50:8b:d3:0b:ba/10.25.1.0
> > Sending on Socket/fallback/fallback-net
>
> I would expect the daemon to listen on and to send to a "real"
Sorry. Too many versions. It's PXE-2.0 build 078 but
Intel Boot Agent 3.0.03.
Doug White wrote:
>
> On Wed, 5 Jul 2000, Alan Edmonds wrote:
>
> >
> > Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM
> > (3.0.03)? I'm getting
build version (07X).
Build 079 is the latest build from Intel and it is the only PXE 2.0 rom
that I know of which has no known bugs.
Anything newer than 079, I have not tested myself..
paul
Alan Edmonds ([EMAIL PROTECTED]) wrote:
>
> Is anyone using pxeboot from 4.0-STABLE with the latest
On Wed, 5 Jul 2000, Alan Edmonds wrote:
>
> Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM
> (3.0.03)? I'm getting a register dump when it's loading the kernel.
Where did you get this version? The new machines we have are all 0.X or
2.X, but
-0500, Alan Edmonds wrote:
>
> > Is anyone using pxeboot from 4.0-STABLE with the latest Intel PXE ROM
> > (3.0.03)? I'm getting a register dump when it's loading the kernel.
>
> Speaking only as someone who saw what the people who wrote this used
> to debug it, you&
64 matches
Mail list logo
