Diskless PXE and hal

I am booting 9.0-RELEASE-p4 i386 over PXE with read-only root. I need hal in order to autoprobe video cards, mouses, keyboards etc. due to different hardware of clients, but it does not work. Invoking it from command line gives me error: # hald --daemon=no --verbose=yes 15:00:11.984 [I] hald.c

Re: pxe + nfs + microsoft dhcp

> > --=-etjkwQYOTmf8U9KY0eW8 > Content-Type: text/plain; charset="us-ascii" > Content-Transfer-Encoding: 7bit > > > > pacija wrote: > > > > > > - Original Message - > > > > Dear list readers, > > > > &

Re: pxe + nfs + microsoft dhcp

> > pacija wrote: > > > > - Original Message - > > > Dear list readers, > > > > > > I am having a problem with pxe loader on FreeBSD 9.0 i386 release. No > > > matter what value I put for DHCP option 017 (Root Path) in

Re: pxe + nfs + microsoft dhcp

> pacija wrote: > > - Original Message - > > Dear list readers, > > > > I am having a problem with pxe loader on FreeBSD 9.0 i386 release. No > > matter what value I put for DHCP option 017 (Root Path) in Microsoft > > DHCP server, pxe always se

Re: pxe + nfs + microsoft dhcp

pacija wrote: - Original Message - > Dear list readers, > > I am having a problem with pxe loader on FreeBSD 9.0 i386 release. No > matter what value I put for DHCP option 017 (Root Path) in Microsoft > DHCP server, pxe always sets root path: > pxe_open: server path: /

pxe + nfs + microsoft dhcp

Dear list readers, I am having a problem with pxe loader on FreeBSD 9.0 i386 release. No matter what value I put for DHCP option 017 (Root Path) in Microsoft DHCP server, pxe always sets root path: pxe_open: server path: / I've read src/sys/boot/i386/libi386/pxe.c as instructed in handbook

Re: PXE on 7.0 problem and solution

On Thu, Feb 28, 2008 at 12:30:26PM -0800, Tim Clewlow wrote: > Hi there, > > Installing 7.0 via PXE has a slight problem that is easily worked around. The > file /boot/mfsroot.gz on the installation media needs to be unzipped to make > PXE boot via tftp/nfs work. Otherwise the lo

Re: PXE on 7.0 problem and solution

Tim Clewlow wrote: Hi there, Installing 7.0 via PXE has a slight problem that is easily worked around. The file /boot/mfsroot.gz on the installation media needs to be unzipped to make PXE boot via tftp/nfs work. Otherwise the loader ultimately complains that it cant find the device to boot from

PXE on 7.0 problem and solution

Hi there, Installing 7.0 via PXE has a slight problem that is easily worked around. The file /boot/mfsroot.gz on the installation media needs to be unzipped to make PXE boot via tftp/nfs work. Otherwise the loader ultimately complains that it cant find the device to boot from. For example, if you

6.2/pxe blues, was Re: pxe boot size limit?

> it seems that pxeboot has a limit with respect to the kernel size, > which prevents the kernel to get loaded, the error printed is > slightly misleading. > > the solution is to make a kernel with loadable modules, instead of > compiled in. not entirely true :-( but changing kernel size has diff

pxe boot size limit?

it seems that pxeboot has a limit with respect to the kernel size, which prevents the kernel to get loaded, the error printed is slightly misleading. the solution is to make a kernel with loadable modules, instead of compiled in. danny ___ freebsd-hac

NFS - MNT_NOEXEC [WAS Re: MNT_NOEXEC on root filesystem with diskless PXE boot?]

rom the rest of your email (quoted below). Colin Percival In this case, / is mounted by the BTX PXE loader over NFS (from a FreeBSD 5.3 server, right now). "mount" does not show the noexec flag. However, with the attached little C program I verified that statfs really returns this flag (0x0

RE: PXE Boot FreeBSD with Etherboot

I've been told that you can do an etherboot via grub. After some googling it seems that this is a solution for Open, but no word about FreeBSD. I don't know if it will work for you.. good luck Ivo ___ freebsd-hackers@freebsd.org mailing list http://lists

Re: PXE Boot FreeBSD with Etherboot

Norbert Koch wrote: It seems there are some problems with using pxeboot in combination with the network boot code from the etherboot project. I have tried many combinations of options with no success. The result is very Last time I looked, etherboot didn't support PXE. In any cas

Re: PXE Boot FreeBSD with Etherboot

Norbert Koch wrote: Just my experience. I never handled to successfully pxeboot FreeBSD. I have been completely successful with 4.8, 4.11, 5.4 and 6.0 using dhcpd and tftp(from inetd) and NFS for exporting the filesystem (i.e. the default setup) I've done it on Intel and IBM motherboards, a

Re: PXE Boot FreeBSD with Etherboot

with the same > > > > result. It seems that somehow etherboot is not setting up the > > > > environment the way pxeboot expects it too. Now the native pxe boot > > > > code in vmware does load pxeboot correctly and I have successfully > > > > booted

Re: PXE Boot FreeBSD with Etherboot

t; > > > http://photos.night-shade.org.uk/photo.php?photo=3D6364 > > > >=20 > > > > I have tried it both on my local machine and in vmware with the same > > > > result. It seems that somehow etherboot is not setting up the > > > > environment

Re: PXE Boot FreeBSD with Etherboot

etherboot is not setting up the > > > environment the way pxeboot expects it too. Now the native pxe boot > > > code in vmware does load pxeboot correctly and I have successfully > > > booted freebsd in vmware, however I can't get the pxe boot code on my > > >

RE: PXE Boot FreeBSD with Etherboot

following photo I found: > > > > > > http://photos.night-shade.org.uk/photo.php?photo=6364 > > > > > > I have tried it both on my local machine and in vmware with the same > > > result. It seems that somehow etherboot is not setting up the > > > env

Re: PXE Boot FreeBSD with Etherboot

> > > http://photos.night-shade.org.uk/photo.php?photo=6364 > > > > I have tried it both on my local machine and in vmware with the same > > result. It seems that somehow etherboot is not setting up the > > environment the way pxeboot expects it too. Now the native pxe bo

RE: PXE Boot FreeBSD with Etherboot

e.org.uk/photo.php?photo=6364 > > I have tried it both on my local machine and in vmware with the same > result. It seems that somehow etherboot is not setting up the > environment the way pxeboot expects it too. Now the native pxe boot > code in vmware does load pxeboot correctly

PXE Boot FreeBSD with Etherboot

I have tried it both on my local machine and in vmware with the same result. It seems that somehow etherboot is not setting up the environment the way pxeboot expects it too. Now the native pxe boot code in vmware does load pxeboot correctly and I have successfully booted freebsd in vmware

pxe boot failure

the board's manufacturer, that linux pxeboot does work fine, which not really helps. They have no newer bios update and know nothing about pxe problems. My environment is FreeBSD 4.11 with latest ISC dhcpd. Here are my settings: /usr/local/dhcpd.conf: default-lease-time 600; max-lease-t

Fwd: Re: MFC pxe fixes

I think this is really a current/hackers thread. -- Mensaje reenviado -- Subject: Re: MFC pxe fixes Date: Miércoles, 4 de Mayo de 2005 10:30 From: Jose M Rodriguez <[EMAIL PROTECTED]> To: Danny Braniss <[EMAIL PROTECTED]> Cc: Jose M Rodriguez <[EMAIL PROT

Re: MNT_NOEXEC on root filesystem with diskless PXE boot?

the rest of your email (quoted below). Colin Percival > In this case, / is mounted by the BTX PXE loader over NFS (from a > FreeBSD 5.3 server, right now). "mount" does not show the noexec > flag. However, with the attached little C program I verified that > statfs really retur

MNT_NOEXEC on root filesystem with diskless PXE boot?

n, as /libexec/ld-elf.so.1 complains: Cannot execute objects on / According to the sources, this was added in 5.4, and will happen if / is mounted noexec. In this case, / is mounted by the BTX PXE loader over NFS (from a FreeBSD 5.3 server, right now). "mount" does not show the noexec flag.

Re: 5.3-R PXE installation

On Sun, 5 Dec 2004, Dmitry Morozovsky wrote: DM> I'm trying to setup PXE istallation for new server. Up to pxeboot everything DM> goes smoothly. pxeboot mounting NFS root successively; however, it DM> immediately whines with DM> DM> Loader version 1.1+ required DM> Abort

5.3-R PXE installation

Dear colleagues, I'm trying to setup PXE istallation for new server. Up to pxeboot everything goes smoothly. pxeboot mounting NFS root successively; however, it immediately whines with Loader version 1.1+ required Aborted! start not found then it loads kernel (which I gunzipped from ke

Re: [PATCH] make BOOTP not panic working PXE configs

On 11/02/2004, at 2:00 AM, Brooks Davis wrote: When using the PXE loader and a stock kernel you can specify the root path as with "option root-path" with a path like "/usr/diskless/5.2-CURRENT". The server is then derived from the value of next-server (the siaddr entry in t

[PATCH] make BOOTP not panic working PXE configs

When using the PXE loader and a stock kernel you can specify the root path as with "option root-path" with a path like "/usr/diskless/5.2-CURRENT". The server is then derived from the value of next-server (the siaddr entry in the dhcp packet). If you add options BOOTP

Re: HOWTO: install without floppy, cdrom, or pxe.

On Monday, 1 December 2003 at 0:18:09 -0800, Alfred Perlstein wrote: > Date: Mon, 1 Dec 2003 00:18:09 -0800 > From: Alfred Perlstein <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: HOWTO: install without floppy, cdrom, or pxe. > > I

Re: HOWTO: install without floppy, cdrom, or pxe.

* Colin Percival <[EMAIL PROTECTED]> [031201 00:27] wrote: > At 00:18 01/12/2003 -0800, Alfred Perlstein wrote: > >Then type these commands into the loader: > >unload kernel > >load /ikernel > >load -t mfs_root /mfsroot > >set vfs.root.mountfrom > >boot ^^ > > Surely that sh

Re: HOWTO: install without floppy, cdrom, or pxe.

At 00:18 01/12/2003 -0800, Alfred Perlstein wrote: Then type these commands into the loader: unload kernel load /ikernel load -t mfs_root /mfsroot set vfs.root.mountfrom boot ^^ Surely that should be vfs.root.mountfrom="ufs:/dev/md0c" ? It should also be possible to put th

HOWTO: install without floppy, cdrom, or pxe.

I have a mini-HOWTO here that possibly be automated. Basically we're going to install FreeBSD over FreeBSD without a floppy, cdrom or pxe. This depends on a loader that's compatible with your kernel so if really weird lockups happen, you might not be compatible. Anyhow, here we go:

Re: Booting a machine over the network without pxe.

my patch, you can help me? Thanks again, sorry about the newbie questions, but i really don't know the procedures. Leal > Date: Sun, 14 Sep 2003 22:55:31 -0700 > From: John-Mark Gurney <[EMAIL PROTECTED]> > To: omestre <[EMAIL PROTECTED]> > Subject: Re: Booting a ma

Re: Booting a machine over the network without pxe.

On Tue, 9 Sep 2003, John-Mark Gurney wrote: > boot.netif.hostname already exists as kern.hostname. Why create yet > another knob for the same value? I have used the structures that already exists.. for bootp or pxe purposes... Maybe you did not understand my patch (terrible english :

Re: Booting a machine over the network without pxe.

omestre wrote this message on Tue, Sep 09, 2003 at 14:22 +: > On Tue, 2 Sep 2003, Josef Karthauser wrote: > > Here is How i have made this task: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=54383 > > I guess that is exactly what you want. I have posted a > PR, and maybe the FreeBSD devel

Re: Booting a machine over the network without pxe.

Sep 2003 21:54:18 +0100 > From: Josef Karthauser <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Booting a machine over the network without pxe. > > Does anyone have any experience of booting a machine over the > network, like pxeboot, but without running PXE on a n

Re: Booting a machine over the network without pxe.

Josef Karthauser wrote: Does anyone have any experience of booting a machine over the network, like pxeboot, but without running PXE on a network card. I imagine that it should be possible to load pxeboot at the boot: prompt and have everything just work. pxeboot requires that you have a PXE BIOS

Re: Booting a machine over the network without pxe.

Josef Karthauser wrote: > On Tue, Sep 02, 2003 at 09:54:18PM +0100, Josef Karthauser wrote: > > Does anyone have any experience of booting a machine over the > > network, like pxeboot, but without running PXE on a network card. > > I imagine that it should be possible to loa

Re: Booting a machine over the network without pxe.

On Tue, 2 Sep 2003, Josef Karthauser wrote: > Does anyone have any experience of booting a machine over the > network, like pxeboot, but without running PXE on a network card. The floppies of etherboot (see ports) work just fine. Or use the bootloader on your IDE dis

Re: Booting a machine over the network without pxe.

On Tue, Sep 02, 2003 at 09:54:18PM +0100, Josef Karthauser wrote: > Does anyone have any experience of booting a machine over the > network, like pxeboot, but without running PXE on a network card. > I imagine that it should be possible to load pxeboot at the boot: > prompt and hav

Booting a machine over the network without pxe.

Does anyone have any experience of booting a machine over the network, like pxeboot, but without running PXE on a network card. I imagine that it should be possible to load pxeboot at the boot: prompt and have everything just work. I could really do with booting my laptop into -stable, where it&#

PXE and ftp install

Hi, I am wondering if anyone has any experience using PXE installs via ftp. The problem encountered is when trying using mediaSetFTP with a valid ftp site, the URL menu window shows up instead. If using NFS as the mediaSet, that works without any problems. Looking at jkh's example in /re

Re: Getting PXE to leave an existing partition alone

On Sat, 2002-06-08 at 06:26, Jason Noble wrote: > /virtual partition line and it will not newfs the drive. The following > line does not work (i.e. all the data on /virtual goes bye bye): > > mlxd0s1-5=ufs 0 /virtual N > > Has anyone used pxe to upgrade a system and leave on

Getting PXE to leave an existing partition alone

I've got a hundred systems that I'm looking at upgrading to 4.4 from 4.1. These systems were originally setup with pxe, with the following partioning scheme (install.cfg format): # Now set the parameters for the partition editor on mlxd0 disk=mlxd0

problems PXE booting with 3C996B-T

Hi, I'm trying to PXE boot a cluster of machines using 3Com 3C996B-T gigabit Ethernet NICs and appear to be running into driver problems specific to PXE booting. Here's what I know: - The system boots just fine off of an Intel card with PXE support. - The 3Com NIC basicly works

Re: pxe booting problem

Le Mercredi 31 Octobre 2001 12:49, vous avez écrit : > Henri, > > FYI - this is my dhcpd.conf. I didn't have to enable > a lot of the options you had in yours: > > My dhcpd.conf is a 'pxe' generic config. I used it with FreBSD pxeboot, pxelinux, pxegrub, bpba

Re: pxe booting problem

wrote: > Le Mardi 30 Octobre 2001 14:30, vous avez écrit : > > I posted some of this info last friday but haven't > had > > any responses. I'm hoping someone out there knows > > what the problem is. Here's the details: > > > > I saw Alfred P

RE: pxe booting problem

nfo last friday but haven't > had > > any responses. I'm hoping someone out there knows > > what the problem is. Here's the details: > > > > I saw Alfred Perlsteins page on how to setup > > FreeBSD installs unsing PXE. > > The problem I&

Re: pxe booting problem

Le Mardi 30 Octobre 2001 17:17, vous avez écrit : > > configuration. I also understand that I have to > > create a subdirectory called 'boot' under the TFTP > > root directory with the file 'loader.rc' in it. Can > > someone verify if this is the case? Sorry. Forget this part. This is the con

Re: pxe booting problem

* Paul Jansen <[EMAIL PROTECTED]> [011030 08:31] wrote: > I posted some of this info last friday but haven't had > any responses. I'm hoping someone out there knows > what the problem is. Here's the details: > > I saw Alfred Perlsteins page on how to

Re: pxe booting problem

Le Mardi 30 Octobre 2001 14:30, vous avez écrit : > I posted some of this info last friday but haven't had > any responses. I'm hoping someone out there knows > what the problem is. Here's the details: > > I saw Alfred Perlsteins page on how to setup > FreeBSD i

RE: pxe booting problem

On 30-Oct-01 Paul Jansen wrote: > I posted some of this info last friday but haven't had > any responses. I'm hoping someone out there knows > what the problem is. Here's the details: > > I saw Alfred Perlsteins page on how to setup > FreeBSD installs unsin

pxe booting problem

I posted some of this info last friday but haven't had any responses. I'm hoping someone out there knows what the problem is. Here's the details: I saw Alfred Perlsteins page on how to setup FreeBSD installs unsing PXE. The problem I'm having now is when I follow Al

diskless-boot/PXE/dhcp

hi all, I've made some changes to libstand/bootp.c and they are available for evaluation/comments/critics at: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/diskless-boot short desc.: o the bootp request now does a vendor-specific-request FreeBSDc instead of

Re: Really odd "BTX halted" problem booting - PXE/diskless

On Fri, Feb 09, 2001 at 12:13:40PM +0200, Danny Braniss wrote: > In message <[EMAIL PROTECTED]>you write: > }It its the bios disk probe that is causing the machine to fault. > > I can now confirm that it's a divide by zero in the Adaptec BIOS GRR. > (in biosdisk, when 'probing' the adaptec) a

Re: Really odd "BTX halted" problem booting - PXE/diskless

In message <[EMAIL PROTECTED]>you write: }It its the bios disk probe that is causing the machine to fault. I can now confirm that it's a divide by zero in the Adaptec BIOS GRR. (in biosdisk, when 'probing' the adaptec) and it happens on a AIC 7899, but works ok on some other ADAPTECs. the pr

Re: Really odd "BTX halted" problem booting - PXE/diskless

gt; on a dell-precision 420, it bombs. > both bioses are configured to boot via the network/pxe. > > im using the same disks for both boxes. > > i labeled the disks with: > dd if=/dev/zero of=/dev/rda0 bs=1k count=1 > disklabel -Brw da0 auto > > i then went ahead an playe

RE: What is the latest "known-good" PXE build ?

On 06-Feb-01 Matt Simerson wrote: > Anyway, that should help you out considerably. If I could legally give away > a floppy with WIN-98 MSDOS installed and the fboot.exe program I would but I > think doing so violates a software license or two. > Have you looked at Free-DOS ?

Re: Help with PXE boot, install and related...

Indispensible URL for this: http://people.freebsd.org/~alfred/pxe/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message

RE: What is the latest "known-good" PXE build ?

On Tue, 6 Feb 2001, Matt Simerson wrote: > Anyway, that should help you out considerably. If I could legally give away > a floppy with WIN-98 MSDOS installed and the fboot.exe program I would but I > think doing so violates a software license or two. > > Matt How about using caldera dr-dos (or

RE: What is the latest "known-good" PXE build ?

I have a "magic floppy" which is nothing more than a DOS boot floppy with the fboot.exe program on it and a BIOS image. This works like a charm for my netbooting purposes: Intel (R) Boot Agent Version 4.0.12 PXE 2.0 Build 082 (Wfm 2.0), RPC v2.7.3 Press Ctrl+S to enter the Setup M

Re: What is the latest "known-good" PXE build ?

Mike Smith ([EMAIL PROTECTED]) wrote: > > > > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other, > > > > perhaps better version of it ? (the on-board NIC on the machine is an fxp) > > > > > > Build 068 is a disaster; you ideally

Re: What is the latest "known-good" PXE build ?

> > > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other, > > > perhaps better version of it ? (the on-board NIC on the machine is an fxp) > > > > Build 068 is a disaster; you ideally want 082 or later. > > is there some standard way

Re: What is the latest "known-good" PXE build ?

> > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other, > > perhaps better version of it ? (the on-board NIC on the machine is an fxp) > > Build 068 is a disaster; you ideally want 082 or later. is there some standard way to upgrade the pxe code on t

Re: What is the latest "known-good" PXE build ?

> I haven't tracked these changes, and am still using some slightly older > rc files. I've updated my rc.diskless stuff to use mdconfig now though; > if there's interest I'll put it up for review. yes please... i'd like to fix things as needed so that diskless scripts work correctly in our ne

Re: What is the latest "known-good" PXE build ?

> > The BIOS trace says the PXE is revision 2.0, build 68 : is there some other, > perhaps better version of it ? (the on-board NIC on the machine is an fxp) Build 068 is a disaster; you ideally want 082 or later. > PS : As I've seen, rc has been modified to get rid of &g

What is the latest "known-good" PXE build ?

diskless machine sometimes can start (it loads pxeboot and the kernel via tftp, and then the rest of the partitions via NFS). The BIOS trace says the PXE is revision 2.0, build 68 : is there some other, perhaps better version of it ? (the on-board NIC on the machine is an fxp) TfH PS : As I&#x

RE: Help with PXE boot, install and related...

minimum network appliance, for > details, see http://www.soekris.com/net4501.html > > > 1) I cannot boot FreeBSD using a PXE boot ROM from a FreeBSD > server. Even worse, if I set up my Win98 box with a tftp > server, I can boot succesfully from that !! > > The pxeboo

Help with PXE boot, install and related...

t4501.html 1) I cannot boot FreeBSD using a PXE boot ROM from a FreeBSD server. Even worse, if I set up my Win98 box with a tftp server, I can boot succesfully from that !! The pxeboot gets loaded, grab the correct info from the dhcp server, but can then not download anything more, the server log

Re: Really odd "BTX halted" problem booting - PXE/diskless

On Thu, 1 Feb 2001, Doug White wrote: > This is a bug in the adaptec BIOS. Don't do this for boot disks. Use > fdisk/real slices instead. Or possibly, dont do this for any disk in the system. Some bioses choke even on non-boot disks with DD partitioning... Fred -- Fred Clift - [EMAIL PROTECT

Re: Really odd "BTX halted" problem booting - PXE/diskless

On Mon, 29 Jan 2001, Danny Braniss wrote: > im now being bitten by this one, but with a twist: > on a compaq deskpro workstation it's ok > on a dell-precision 420, it bombs. > both bioses are configured to boot via the network/pxe. > > im using the same disks for bot

Re: Really odd "BTX halted" problem booting - PXE/diskless

On 29-Jan-01 Danny Braniss wrote: > im now being bitten by this one, but with a twist: > on a compaq deskpro workstation it's ok > on a dell-precision 420, it bombs. > both bioses are configured to boot via the network/pxe. > > im using the same disks for both boxes. &

Re: Really odd "BTX halted" problem booting - PXE/diskless

im now being bitten by this one, but with a twist: on a compaq deskpro workstation it's ok on a dell-precision 420, it bombs. both bioses are configured to boot via the network/pxe. im using the same disks for both boxes. i labeled the disks with: dd if=/dev/zero of=/dev/rda0 bs=1k co

Re: diskless/pxe boot

On Fri, 15 Dec 2000, Danny Braniss wrote: > hi all, > I can't get the pxe/dhcp to work when it's 100Mbit Ethernet, it works > fine when it's 10Mbit. Actually a newer Intel MB just succeeded, but 99% > of the pxe enabled cards fail at 100Mbit. from sniffing t

diskless/pxe boot

hi all, I can't get the pxe/dhcp to work when it's 100Mbit Ethernet, it works fine when it's 10Mbit. Actually a newer Intel MB just succeeded, but 99% of the pxe enabled cards fail at 100Mbit. from sniffing the net the broadcast dhcp request does not make it. it does not

RE: PXE boot problem. - SOLVED

That was it. Updating the flash on the Intel NIC and she booted right up. Thanks, Matt > -Original Message- > From: Mathew KANNER [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 01, 2000 8:54 AM > To: Matt Simerson > Cc: '[EMAIL PROTECTED]' > S

Re: PXE boot problem.

On Nov 30, Matt Simerson wrote: > [...] > >Intel UNDI, PXE-2.0 (build 067) >Copyright (c) 1997, 1998 Intel Corporation > [...] Get the flash upgrade from intel. Mine reads: Intel(R) Boot Agent Version 4.0.14 and it works well.

Re: PXE boot problem.

From: Doug White <[EMAIL PROTECTED]> Subject: Re: PXE boot problem. Date: Thu, 30 Nov 2000 20:18:26 -0800 (PST) > On Thu, 30 Nov 2000, Matt Simerson wrote: > > > Hi Folks, > > > > I've been trying hard to get a FreeBSD system booted via PXE with only > >

Re: PXE boot problem.

On Thu, 30 Nov 2000, Matt Simerson wrote: > Hi Folks, > > I've been trying hard to get a FreeBSD system booted via PXE with only > limited success. Maybe someone can have a look at my configs and shed a > little light on this for me. > > Here's what happens a

PXE boot problem.

Hi Folks, I've been trying hard to get a FreeBSD system booted via PXE with only limited success. Maybe someone can have a look at my configs and shed a little light on this for me. Here's what happens at boot time: Intel UNDI, PXE-2.0 (build 067) Copyright (c) 1997,

pxe

hi all, I'm trying to figure out why in pxe.c (sys/boot/i386/libi386) the ip in ip:path is quietly ignored. there must be a reason, but it escapes me. the problem im having, is that since my nfs-root server is not the dhcpd-server, the only way to give it the root nfs ip, is via the opt

Re: PXE (pxeboot) and serial consoles - force it!

Paul Saab writes: | Doug Ambrisko ([EMAIL PROTECTED]) wrote: | > Paul Saab writes: | > | set console="comconsole" is what you want in /boot/loader.rc | > | > Yep, except that it doesn't initialize the com port, it just starts | > using it so you end up with junk out the port. However, if you hav

Re: PXE (pxeboot) and serial consoles - force it!

o appears to load /pxeboot via tftp and /boot/loader.rc > via NFS. Maybe I just have an ill advised configuration. Ok.. that is true.. (I just dont do it that way) The PXE bootrom downloads via tftp and we set the loader to use NFS by default. The NFS support is much better than tftp, so that is

Re: PXE (pxeboot) and serial consoles - force it!

> pxeboot loads /boot/loader.rc over the network from the same place > the PXE bootrom loaded pxeboot. It is done with either NFS or TFTP > (depending on what you compile). Therefore, if it could load pxeboot, > then it can more than likely load /boot/loader.rc. > > -- > P

Re: PXE (pxeboot) and serial consoles - force it!

that it won't take effect until after loader.rc. >> > I know I can put set console="comconsole" in /boot/loader.rc. >> > Normally, this is set in the boot blocks, but we don't >> > have these in pxeboot. >> >> Actually, you will find that

Re: PXE (pxeboot) and serial consoles - force it!

onsole > like you can with boot[012]. pxeboot loads /boot/loader.rc over the network from the same place the PXE bootrom loaded pxeboot. It is done with either NFS or TFTP (depending on what you compile). Therefore, if it could load pxeboot, then it can more than likely load /boot/loade

Re: PXE (pxeboot) and serial consoles - force it!

Mike Smith wrote: > > > Restating the question. > > > > Is there a way to force PXE to > > I think you have some very serious confusion about what things are and > what they are called, and it is making it impossible for anyone else to > understand what you&

Re: PXE (pxeboot) and serial consoles - force it!

> Restating the question. > > Is there a way to force PXE to I think you have some very serious confusion about what things are and what they are called, and it is making it impossible for anyone else to understand what you're talking about. "PXE" is a specifi

Re: PXE (pxeboot) and serial consoles - force it!

Restating the question. Is there a way to force PXE to 1) not probe for a console 2) use a serial port as the default com port I know I can put set console="comconsole" in /boot/loader.rc. Normally, this is set in the boot blocks, but we don't have these in pxeboot. Thanks, -

Re: PXE (pxeboot) and serial consoles - force it!

Doug Ambrisko ([EMAIL PROTECTED]) wrote: > Paul Saab writes: > | set console="comconsole" is what you want in /boot/loader.rc > > Yep, except that it doesn't initialize the com port, it just starts > using it so you end up with junk out the port. However, if you have a > BIOS that setups the bau

Re: PXE (pxeboot) and serial consoles - force it!

> Paul Saab writes: > | set console="comconsole" is what you want in /boot/loader.rc > > Yep, except that it doesn't initialize the com port, it just starts > using it so you end up with junk out the port. However, if you have a > BIOS that setups the baud rate etc. of the serial port then you w

Re: PXE (pxeboot) and serial consoles - force it!

Paul Saab writes: | set console="comconsole" is what you want in /boot/loader.rc Yep, except that it doesn't initialize the com port, it just starts using it so you end up with junk out the port. However, if you have a BIOS that setups the baud rate etc. of the serial port then you would be okay

Re: PXE (pxeboot) and serial consoles - force it!

Alan Edmonds writes: | | I'm playing with PXE and pxeboot. I have a question about | setting the serial console option. The PC BIOS reports | 'No Keyboard Present', but when PXE boots, BTX reports | console as internal keyboard/video. So, I'm looking at | hard coding a

Re: PXE (pxeboot) and serial consoles - force it!

set console="comconsole" is what you want in /boot/loader.rc paul Alan Edmonds ([EMAIL PROTECTED]) wrote: > > I'm playing with PXE and pxeboot. I have a question about > setting the serial console option. The PC BIOS reports > 'No Keyboard Present&#

PXE (pxeboot) and serial consoles - force it!

I'm playing with PXE and pxeboot. I have a question about setting the serial console option. The PC BIOS reports 'No Keyboard Present', but when PXE boots, BTX reports console as internal keyboard/video. So, I'm looking at hard coding a serial console into BTX. Norm

Re: PXE

Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote in list.freebsd-hackers: > -On [2313 13:55], David Yeske ([EMAIL PROTECTED]) wrote: > >I just got an Intel PRO/100+ Management card for a project I am working on. I have >done a little > >a little research and it looks like it is go

Re: PXE

-On [2313 13:55], David Yeske ([EMAIL PROTECTED]) wrote: >I just got an Intel PRO/100+ Management card for a project I am working on. I have >done a little >a little research and it looks like it is going to be a lot of work to netboot this >thing. Anyone >gotten this to work so far? I ha

PXE

I just got an Intel PRO/100+ Management card for a project I am working on. I have done a little a little research and it looks like it is going to be a lot of work to netboot this thing. Anyone gotten this to work so far? I have tried using bootpd and dhcpd with no luck. Regards, David Yesk

  1   2   >