From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] PXE tftpload: file does not exist
Date: Mon, 17 Jul 2023 19:47:12 +0100 [thread overview]
Message-ID: <7D0CCBF2-C182-4740-B381-9D3ADCBF85F7@quintile.net> (raw)
In-Reply-To: <A46F574D-76BB-48D4-B6AC-F113145DC588@germteig.com>
are you running the tftp server?
> On 17 Jul 2023, at 4:38 pm, Marco Feichtinger <marco@germteig.com> wrote:
>
> I have a standalone file server, and a separate standalone auth server.
>
> I tried to pxe boot a cpu server.
> It gets the /386/9boot to load fine, but then it seems, that it can’t retrieve the file /cfg/pxe/<mac address> from my file server.
>
> here is the screen output during bootup:
> 9boot gz…starting protected-mode loader at 0x900020
>
> Plan 9 from Bell Labs PXE boot loader
> cpu0: 1800MHz GenuineIntel Atom (cpuid: AX 0x106CA DX 0xBFEBFBFF)
> ELCR: CC80
> #l0: i82598: 10Gbps port 0XFE980000 irq 11: <mac address>
> #l0: i82598: 10Gbps port 0XFE980000 irq 10: <mac address>
> 498M memory: 498M kernel data, 0M user, 18M swap
> pxe on ether0 .
> <sysname> (10.0.10.1!69): /cfg/pxe/<mac address> .T.T.T.T.T.T.T.T.T.Ttftpread1st: failed to connect to server (10.0.10.1!69)
>
> failed.
> tftpload: file does not exist
>
> Which is strange, because I did create the file on my file server.
> It looks like following:
> bootfile=ether0!/386/9pccpuf
> nobootprompt=tcp
> readparts=1
> mouseport=2
> monitor=vesa
> vgasize=1024x768x8
> user=bootes
> sysname=<sysname>
>
> Does anyone know what might be the problem?
> Thanks.
>
> -marco
>
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T8484142ec51acbb7-M0ce607b1428412813c3c3de5
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2023-07-17 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 15:37 Marco Feichtinger
2023-07-17 18:47 ` Steve Simon [this message]
2023-07-17 20:25 ` Marco Feichtinger
2023-07-22 6:21 ` Marco Feichtinger
2023-07-22 23:12 ` vic.thacker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7D0CCBF2-C182-4740-B381-9D3ADCBF85F7@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).