etherboot-developers — Discussion of developer issues

[Etherboot-developers] 3Com MBA+nbi image support patch

[Michael G. <mge...@so...>]

So, this patch adds support for booting linux kernel images with a 3Com
MBA + NBI header.  Non NBI 3Com MBA headers are aborted.

diff -Nur etherboot-5.1.5/src/Config etherboot-5.1.5-mba/src/Config
--- etherboot-5.1.5/src/Config	Fri Jan 10 10:20:05 2003
+++ etherboot-5.1.5-mba/src/Config	Tue Jan 21 19:39:50 2003
@@ -122,6 +122,8 @@
 #
 #	Boot image options:
 #
+#	-DMBA_IMAGE
+#			Add 3Com MBA+nbi image kernel boot support.
 #	-DTAGGED_IMAGE
 #			Add tagged image kernel boot support (recommended).
 #	-DAOUT_IMAGE
diff -Nur etherboot-5.1.5/src/arch/i386/core/mba_loader.c etherboot-5.1.5-mba/src/arch/i386/core/mba_loader.c
--- etherboot-5.1.5/src/arch/i386/core/mba_loader.c	Wed Dec 31 19:00:00 1969
+++ etherboot-5.1.5-mba/src/arch/i386/core/mba_loader.c	Tue Jan 21 19:36:01 2003
@@ -0,0 +1,143 @@
+static int	mba_curpos;
+static int	mba_oldpos;
+static int	mba_headersize;
+static char	mba_nbi_header[512];
+
+static sector_t mba_tagged_download(unsigned char *data, unsigned int len, int eof);
+static inline os_download_t mba_tagged_probe(unsigned char *data, unsigned int len)
+{
+	struct segheader	*sh;
+	unsigned long loc;
+	char	mbasig[] = "TCPIP";
+	int i;
+	if (memcmp(data + 2, mbasig, strlen("TCPIP")) != 0) {
+		return 0;
+	}
+	mba_headersize = *(data + 10) + (*(data + 11) << 8);
+	printf("(MBA %d)",mba_headersize);
+
+	mba_curpos = 0;
+	mba_oldpos = 0;
+	
+	return mba_tagged_download;
+
+}
+static sector_t mba_tagged_download(unsigned char *data, unsigned int len, int eof)
+{
+	int	i;
+
+	mba_oldpos = mba_curpos;
+	mba_curpos += len;
+
+#ifdef DEBUG
+	printf ("curpos:%d oldpos:%d\n",
+			mba_curpos,
+			mba_oldpos);
+#endif
+	
+	/* If we're already past the headers, then we're in the middle of
+	* loading the kernel and we should proceed as normal */
+	if (mba_oldpos > mba_headersize+512)
+	{
+		return tagged_download(data,len,eof);
+	}
+	/* If not then we're still in the middle of mangling the MBA and nbi
+	* headers. */
+	else if (mba_curpos > mba_headersize)
+	{
+		int nbi_start;
+		int nbi_len;
+		/* Case where packet holds first portion of nbi header:
+		* put first portion into the nbi buffer and continue */
+		if ((mba_oldpos <= mba_headersize) &&
+		    (mba_curpos < (mba_headersize+512)))
+		{
+			nbi_start = mba_headersize - mba_oldpos;
+			nbi_len = len - nbi_start;
+#ifdef DEBUG
+			printf ("First fraction bytes %d to %d (%d bytes)\n", 
+					0,
+					nbi_len-1,
+					nbi_len);
+#endif
+			memcpy (mba_nbi_header, 
+				data+nbi_start,
+				nbi_len);
+		}
+		
+		/* Case where packet holds entire nbi header:
+		* don't even bother with the nbi buffer, just adjust the
+		* len dohickey to point to the start of the nbi header, 
+		* pass it to the probe function, then proceed as normal */
+		if ((mba_oldpos <= mba_headersize) &&
+		    (mba_curpos >= (mba_headersize+512)))
+		{
+			nbi_start = mba_headersize + len - mba_curpos;
+			len -= nbi_start;
+			data += nbi_start;
+			if (!tagged_probe(data,len))
+			{
+				printf ("(!NBI)");
+				longjmp(restart_etherboot, -2);
+			}
+		}
+		
+		/* Case where packet holds last portion of nbi header:
+		* save the last portion to the nbi buffer, pass the addr
+		* of the nbi buffer to probe, run the tagged_loader with 
+		* twiddled len and tctx.first values. */
+		if ((mba_oldpos > mba_headersize) &&
+		    (mba_curpos >= (mba_headersize+512)))
+		{
+			nbi_start = mba_oldpos - mba_headersize;
+			nbi_len = 512 - nbi_start;
+#ifdef DEBUG
+			printf ("Last fraction bytes %d to %d (%d bytes)\n", 
+					nbi_start,
+					nbi_start+nbi_len,
+					nbi_len);
+#endif
+			memcpy (mba_nbi_header+nbi_start,
+				data,
+				nbi_len);
+			if (!tagged_probe(mba_nbi_header,512))
+			{
+				printf ("(!NBI)");
+				longjmp(restart_etherboot, -2);
+			}
+			tctx.first = 0;
+			len -= nbi_len;
+			data += nbi_len;
+		}
+		
+		/* Case where packet holds sub portion of nbi header:
+		* probably never happen, but better save than sorry, place sub
+		* portion into the nbi buffer, proceed as normal */
+		if ((mba_oldpos > mba_headersize) &&
+		    (mba_curpos < (mba_headersize+512)))
+		{
+			nbi_start = mba_oldpos - mba_headersize;
+			nbi_len = len;
+#ifdef DEBUG
+			printf ("Last fraction bytes %d to %d (%d bytes)\n", 
+					nbi_start,
+					nbi_start+nbi_len,
+					nbi_len);
+#endif
+			memcpy (mba_nbi_header+nbi_start,
+				data,
+				nbi_len);
+		}
+		
+		/* Since we're past the end of the headers, we know it's time 
+		* to do the first tagged_download call.  We assume that
+		* anything that needs to be jiggered to make this work has
+		* been above. */
+		if (mba_curpos >= (mba_headersize + 512))
+		{
+			return tagged_download(data,len,eof);
+		}
+	}
+	
+	return 0;
+}
diff -Nur etherboot-5.1.5/src/core/osloader.c etherboot-5.1.5-mba/src/core/osloader.c
--- etherboot-5.1.5/src/core/osloader.c	Fri Dec 13 04:53:59 2002
+++ etherboot-5.1.5-mba/src/core/osloader.c	Tue Jan 21 18:38:55 2003
@@ -80,10 +80,14 @@
 #include "../arch/i386/core/aout_loader.c"
 #endif
 
-#ifdef TAGGED_IMAGE
+#if defined(TAGGED_IMAGE) || defined(MBA_IMAGE)
 #include "../arch/i386/core/tagged_loader.c"
 #endif
 
+#ifdef MBA_IMAGE
+#include "../arch/i386/core/mba_loader.c"
+#endif
+
 #if defined(ELF_IMAGE) || defined(ELF64_IMAGE)
 #include "elf_loader.c"
 #endif
@@ -233,6 +237,9 @@
 #endif
 #ifdef WINCE_IMAGE
 	if (!os_download) os_download = wince_probe(data, len);
+#endif
+#ifdef MBA_IMAGE
+	if (!os_download) os_download = mba_tagged_probe(data, len);
 #endif
 #ifdef TAGGED_IMAGE
 	if (!os_download) os_download = tagged_probe(data, len);

[Etherboot-developers] PCI_CONFIG patch

[Timothy L. <tim...@us...>]

Hi

Looking for the "486 R" problem, I decided to disable PCI by removeing
-DCONFIG_PCI from the Config file.  As a result, I received errors
trying to compile pci_io.c.  I did the following, but since I don't know
if this is the best way to handle it, I did not cvs it.  With the patch
in place, everything seemed to compile correctly.

Tim

*** arch/i386/core/pci_io.c	Tue Jan 21 19:59:32 2003
--- arch/i386/core/pci_io.c-new	Tue Jan 21 20:01:49 2003
***************
*** 12,17 ****
--- 12,18 ----
  */
  #include "etherboot.h"
  #include "pci.h"
+ #ifdef CONFIG_PCI
  #ifdef	CONFIG_PCI_DIRECT
  #define  PCIBIOS_SUCCESSFUL                0x00
  
*************** void find_pci(int type, struct pci_devic
*** 332,334 ****
--- 333,336 ----
  #endif
  	return scan_pci_bus(type, dev);
  }
+ #endif

RE: [Etherboot-developers] 3Com MBA image support...

[Timothy L. <tim...@us...>]

Hi

If you are a developer, you could cvs it.  If not, send it to the list
for review.  

Ken is on vacation I believe and a number of others are at the Linux
conference.  If you don't get much response this week, resubmit it again
next week...

Tim

> -----Original Message-----
> From: eth...@li...
[mailto:etherboot-
> dev...@li...] On Behalf Of Michael Gentili
> Sent: Tuesday, January 21, 2003 8:16 PM
> To: eth...@li...
> Subject: [Etherboot-developers] 3Com MBA image support...
> 
> 
> So I've glued in support for recognising and booting 3Com MBA+nbi
> linux kernel images.  What would be the best way to submit a patch?
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!
> Can't afford IT training? All 2003 ictp students receive scholarships.
> Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
> www.ictp.com/training/sourceforge.asp
> _______________________________________________
> Etherboot-developers mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-developers

[Etherboot-developers] 3Com MBA image support...

[Michael G. <mge...@so...>]

So I've glued in support for recognising and booting 3Com MBA+nbi
linux kernel images.  What would be the best way to submit a patch?

[Etherboot-developers] About tulip

[deng z. <dz...@ho...>]

I have a ADMtek an983 chip,I can download a win98 image and start it;But 
when I restart from windows and reboot the pc, the etherboot report "The 
Tulip chip at %X is not functioning"; then I debug it at :
   if (inl(ioaddr + CSR5) == 0xFFFFFFFF) {
        printf("%s: The Tulip chip at %X is not functioning.\n",
               tp->nic_name, ioaddr);
        return 0;
    }
then I power off and power on ,it can go correctly; But when I restart from 
windows,problem again!



_________________________________________________________________
与联机的朋友进行交流，请使用 MSN Messenger: http://messenger.msn.com/cn 

RE: [Etherboot-developers] 5.1 will not boot on 486 was Serial Port Debugging

[Timothy L. <tim...@us...>]

> 2) Seeing if just using the serial port would allow your 486 to work,
>    you could at least see if it could get more than one character
printed.

Well, I have more information on the 486 issue.  I compiled a driver
(gcc 2.95.3) and booted the system.  It displayed:

.000041.0000 done
R

At this point, nothing was shown in minicom.  Then, I accidentally hit
some miscellaneous keys on the client keyboard.  The result was that it
started to display the rest of the information on the screen (and in
minicom) as follows:

.000041.0000 done
ROM segment 0x0800 length 0x8000 reloc 0x00020000

I was able to observe the following:

1) Even the non-serial debugging version displayed this behavior.
2) If I hit the (return) enter key it displayed the text 2 letters at a
time.
3) If I hit the number keypad enter key it displayed the text 4 letters
at a time.
4) It would start to beep after hitting the key a number of times.
5) It froze after it finished displaying that first line. (Or at least
did not display anything else in either minicom of on the screen.

I am not sure if any of this information is useful, but I guess it is
more than we knew earlier.

Tim

Re: [Etherboot-developers] Serial Port Debugging

[<ebi...@ln...>]

"Timothy Legge" <tl...@ro...> writes:

> So after spending more money than I want to think about and making
> beginner level mistakes I have finally gotten serial debugging working.
> Now what was it I needed it for??

There are 2 cases I remember.
1) confirming the double probe. (already confirmed...)
2) Seeing if just using the serial port would allow your 486 to work,
   you could at least see if it could get more than one character printed.

Eric

RE: [Etherboot-developers] Serial Port Debugging

[Vasil V. <va...@sy...>]

On Mon, 20 Jan 2003, Timothy Legge wrote:

> > > I had purchased a 9 to 25 pin null modem serial cable, nothing
> seemed to
> > work.
> >
> > Where do you connect the 25 pin end?
>
> Particularly good question.  Here is what I have learned about serial
> debugging:
>
> 1) If you have two 25 pin ports on the back of your computer, ensure
> that you know which one is the printer port.  Yes, even if you think you
> know, open the case and look to be sure.
>
> 2) If you are going to buy a num modem cable or adapter ensure that you
> know how it should be wired.  Do not buy a cable or adapter that does
> not have wiring information unless you verify it with a meter.  In fact,
> insist on it even if it is labeled.
>
> So after spending more money than I want to think about and making
> beginner level mistakes I have finally gotten serial debugging working.
> Now what was it I needed it for??

Good points. I have experienced similar problems about wiring but with RJ45
connectors:

3) There is no standard for converting RJ45 to DB9 or DB25 for serial lines.

-- 
Vasil
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The trouble with eating Italian food is that five or six days later
you're hungry again.
		-- George Miller

RE: [Etherboot-developers] Serial Port Debugging

[Timothy L. <tim...@us...>]

> > I had purchased a 9 to 25 pin null modem serial cable, nothing
seemed to
> work.
> 
> Where do you connect the 25 pin end?

Particularly good question.  Here is what I have learned about serial
debugging:

1) If you have two 25 pin ports on the back of your computer, ensure
that you know which one is the printer port.  Yes, even if you think you
know, open the case and look to be sure.

2) If you are going to buy a num modem cable or adapter ensure that you
know how it should be wired.  Do not buy a cable or adapter that does
not have wiring information unless you verify it with a meter.  In fact,
insist on it even if it is labeled.

So after spending more money than I want to think about and making
beginner level mistakes I have finally gotten serial debugging working.
Now what was it I needed it for??

Tim

RE: [Etherboot-developers] Serial Port Debugging

[Timothy L. <tl...@ro...>]

> > I had purchased a 9 to 25 pin null modem serial cable, nothing
seemed to
> work.
> 
> Where do you connect the 25 pin end?

Particularly good question.  Here is what I have learned about serial
debugging:

1) If you have two 25 pin ports on the back of your computer, ensure
that you know which one is the printer port.  Yes, even if you think you
know, open the case and look to be sure.

2) If you are going to buy a num modem cable or adapter ensure that you
know how it should be wired.  Do not buy a cable or adapter that does
not have wiring information unless you verify it with a meter.  In fact,
insist on it even if it is labeled.

So after spending more money than I want to think about and making
beginner level mistakes I have finally gotten serial debugging working.
Now what was it I needed it for??

Tim

[Etherboot-developers] away for a bit

[<ke...@us...>]

I'm going on holiday. See you guys in a couple of weeks.

Leave some bugs for me. :-)

Re: [Etherboot-developers] Fwd: rom-o-matic error

[<ke...@us...>]

>Do we have a patch for this? I know CVS is quite active lately, and I 
>am thinking I should be patching 5.1.5 on rom-o-matic.net to try to 
>keep up.

No, it's a bug triggered by the use of the DELIMITERLINES feature. I'm
half inclined to drop that feature. Feel free to develop a fix.

[Etherboot-developers] Fwd: rom-o-matic error

[Marty C. <md...@en...>]

Do we have a patch for this? I know CVS is quite active lately, and I 
am thinking I should be patching 5.1.5 on rom-o-matic.net to try to 
keep up.

Thanks,

Marty

Begin forwarded message:

> From: "Steve Flynn" <sf...@tp...>
> Date: Sun Jan 19, 2003  1:38:02  AM US/Eastern
> To: <web...@en...>
> Subject: rom-o-matic error
> Reply-To: "Steve Flynn" <sf...@tp...>
>
>  Build failed. Status = 2.
>
> Following is the output from make:
>
>
> make: Entering directory `/tmp/ROMaiFOkC'
> gcc -DPCBIOS -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC 
> -DBOOT_SECOND=BOOT_FLOPPY -D
> BOOT_THIRD=BOOT_DISK -DBOOT_INDEX=0 -DBAR_PROGRESS -DDELIMITERLINES 
> -DSIZEIN
> DICATOR -DCONGESTED -DBACKOFF_LIMIT=7 -DTRY_FLOPPY_FIRST=0 
> -DTAGGED_IMAGE -D
> ELF_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 
> -DCOMPARM
> =0x03 -DCONFIG_PCI -Os -ffreestanding  -Wall -W -Wno-format 
> -DVERSION_MAJOR=
> 5 -DVERSION_MINOR=1 -DVERSION=\"5.1.5\" -DRELOC=0x20000  -I include -I
> arch/i386/include -DARCH=i386 -DINCLUDE_RTL8139 -o bin/rtl8139.o -c
> drivers/net/rtl8139.c
> In file included from include/string.h:11,
>                  from include/osdep.h:13,
>                  from include/etherboot.h:9,
>                  from drivers/net/rtl8139.c:68:
> arch/i386/include/bits/string.h:254: warning: static declaration for
> `strncmp' follows non-static
> arch/i386/include/bits/string.h:277: warning: static declaration for
> `strlen' follows non-static
> gcc -DPCBIOS -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC 
> -DBOOT_SECOND=BOOT_FLOPPY -D
> BOOT_THIRD=BOOT_DISK -DBOOT_INDEX=0 -DBAR_PROGRESS -DDELIMITERLINES 
> -DSIZEIN
> DICATOR -DCONGESTED -DBACKOFF_LIMIT=7 -DTRY_FLOPPY_FIRST=0 
> -DTAGGED_IMAGE -D
> ELF_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 
> -DCOMPARM
> =0x03 -DCONFIG_PCI -Os -ffreestanding  -Wall -W -Wno-format 
> -DVERSION_MAJOR=
> 5 -DVERSION_MINOR=1 -DVERSION=\"5.1.5\" -DRELOC=0x20000  -I include -I
> arch/i386/include -DARCH=i386 -o bin/linuxbios.o -c
> firmware/linuxbios/linuxbios.c
> gcc -DPCBIOS -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC 
> -DBOOT_SECOND=BOOT_FLOPPY -D
> BOOT_THIRD=BOOT_DISK -DBOOT_INDEX=0 -DBAR_PROGRESS -DDELIMITERLINES 
> -DSIZEIN
> DICATOR -DCONGESTED -DBACKOFF_LIMIT=7 -DTRY_FLOPPY_FIRST=0 
> -DTAGGED_IMAGE -D
> ELF_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 
> -DCOMPARM
> =0x03 -DCONFIG_PCI -Os -ffreestanding  -Wall -W -Wno-format 
> -DVERSION_MAJOR=
> 5 -DVERSION_MINOR=1 -DVERSION=\"5.1.5\" -DRELOC=0x20000  -I include -I
> arch/i386/include -DARCH=i386 -o bin/main.o -c core/main.c
> In file included from include/string.h:11,
>                  from include/osdep.h:13,
>                  from include/etherboot.h:9,
>                  from core/main.c:22:
> arch/i386/include/bits/string.h:254: warning: static declaration for
> `strncmp' follows non-static
> arch/i386/include/bits/string.h:277: warning: static declaration for
> `strlen' follows non-static
> core/main.c: In function `main':
> core/main.c:160: `i' undeclared (first use in this function)
> core/main.c:160: (Each undeclared identifier is reported only once
> core/main.c:160: for each function it appears in.)
> core/main.c:148: warning: unused parameter `ptr'
> core/main.c: In function `main_loop':
> core/main.c:294: warning: comparison between signed and unsigned
> make: *** [bin/main.o] Error 1
> make: Leaving directory `/tmp/ROMaiFOkC'Please let us know that this
> happened.
>
> Cheers, Steve Flynn
> sf...@tp...
>

RE: [Etherboot-developers] Driver probing twice in latest 5.1 cvs

[Timothy L. <tim...@us...>]

> Bah.  I just saw a double probe case.  I forgot to ``initialized=1''
> to main.c  when I put in the fix for the menu code so the NICs were
being
> reinitialized every time through main_loop.

That seems to have fixed my issue.  Of course, my sundance driver seems
to have worked better when the card was probed twice...

[Etherboot-developers] Re: etherboot

[Tom T. <to...@mm...>]

On Sat, Jan 18, 2003 at 10:52:02AM +1100, ke...@us... wrote:
> There has been a one line fix and someone has reported a working tulip.
> You can find the patch at the web site. The bit about hanging at the 'R'
> is not Tulip related. I have not experienced it, only Timothy Legge has.
> It's quite strange, it only happens with his 486 not his Pentium. But
> then you must be running a Pentium too, since the Tulip is a PCI card so
> what gives?  It might be one of those rare compiler bugs. What version
> of gcc are you running? 2.95 and 3.2 seem to work ok for me.

My home development system will soon be 3.2,
right now I use kgcc on a Red Hat system which gives
me egcs-2.91.66 (instead of the buggy 2.96).
I could build the images on another system running gcc 3.2.

Interestingly my test system is a 486 !!  It is a late period
486 with an am486DX4-120 processor, UMC chipset, and 3 pci slots.

So, I have many things to try now, I will do some experimenting.

	Tom

-- 
Tom Trebisky
MMT Observatory
to...@mm...

Re: [Etherboot-developers] Driver probing twice in latest 5.1 cvs

[<ebi...@ln...>]

"Timothy Legge" <tim...@us...> writes:

> > I have a serial console log of etherboot appended so if you can point
> out
> > rough where you think an extra probe may be happening I am willing to
> take
> > a look.
> 
> 
> > Starting: EFI Lanboot
> > ROM segment 0x0000 length 0x0000 reloc 0xbeedd310
> > Etherboot 5.1.5pre2 (GPL) ELF64 for [undi_nii]
> > Relocating _text from: [00000040beedd310,00000040beffa8e0) to
> > [000000003f0f4a30,000000003f212000)
> > ITC 900 Mhz
> > Boot from (N)etwork (D)isk (F)loppy or from (L)ocal?
> > Probing pci nic...
> 
> I think it starts here.  I am trying to setup miniterm, to be able to
> get a dump of the information.  There is a real lack on information on
> how to set up two serial debugging on the Linux side.  I found the
> Etherboot config setting but getting the Linux side configured is a
> pain.

Bah.  I just saw a double probe case.  I forgot to ``initialized=1''
to main.c  when I put in the fix for the menu code so the NICs were being
reinitialized every time through main_loop.  

And while I am thinking about it another way to see messages that are
scrolling to fast is to put a delay into the printf after the messages
is printed, sorry I think in terms of serial console first because you can
let it spew and then look back to see what actually happened.

Eric

Re: [Etherboot-developers] Serial Port Debugging

[Vasil V. <vas...@sy...>]

On Fri, 17 Jan 2003, Timothy Legge wrote:

> Hi
>
> I am getting somewhat fustrated with trying to get the serial port debugging working.  Here what I have done:
>
> 1) Enabled the Serial Console in Config (I assume there is only one spot)

There is an option for CRT Console and Dual Console (CRT and Serial). I am not
sure what the exclusions are.

> 2) Run minicom, with the same speed and the /dev/ttyS0 or /dev/ttyS1 port,
> 8N1 and ANSI.  (The status bar for minicom says Offline, is this normal).

I've seen minicom which says Offline and sending and receiving OK. I think
Offline is to do with the flow control pins, so if they are not connected you
may get Offline in minicom, but otherwise all else is fine.

Check the serial port configuration for etherboot and the ports the BIOS uses
for the serial lines.

> I had purchased a 9 to 25 pin null modem serial cable, nothing seemed to work.

Where do you connect the 25 pin end?

> Today, I purchased a 9 to 9 pin seial cable and a Null Modem adapter, nothing seems to work.
>
> I have deleted /dev/modem and /dev/mouse, so they are not interfering.

Have you tried lilo or booting linux kernel with the console parameter set:

in lilo.conf

serial=s,xxxxxn8

image=.....
	append="console=ttySs,xxxxx"


where s is the number of the port, say 0 or 1. xxxxx is the speed, say 9600.

Or even simpler, trying typing into /dev/ttyS0 or /dev/ttyS1 on either machine
and listening on the other.
This would at least establish whether the lines and cables are working without
etherboot.

[Etherboot-developers] Serial Port Debugging

[Timothy L. <tl...@ro...>]

Hi

I am getting somewhat fustrated with trying to get the serial port debugging working.  Here what I have done:

1) Enabled the Serial Console in Config (I assume there is only one spot)
2) Run minicom, with the same speed and the /dev/ttyS0 or /dev/ttyS1 port, 8N1 and ANSI.  (The status bar for minicom says Offline, is this normal).

I had purchased a 9 to 25 pin null modem serial cable, nothing seemed to work.

Today, I purchased a 9 to 9 pin seial cable and a Null Modem adapter, nothing seems to work.

I have deleted /dev/modem and /dev/mouse, so they are not interfering.

Any ideas?

Tim

Re: [Etherboot-developers] Driver probing twice in latest 5.1 cvs

[<ebi...@ln...>]

"Timothy Legge" <tim...@us...> writes:

> > I have a serial console log of etherboot appended so if you can point
> out
> > rough where you think an extra probe may be happening I am willing to
> take
> > a look.
> 
> 
> > Starting: EFI Lanboot
> > ROM segment 0x0000 length 0x0000 reloc 0xbeedd310
> > Etherboot 5.1.5pre2 (GPL) ELF64 for [undi_nii]
> > Relocating _text from: [00000040beedd310,00000040beffa8e0) to
> > [000000003f0f4a30,000000003f212000)
> > ITC 900 Mhz
> > Boot from (N)etwork (D)isk (F)loppy or from (L)ocal?
> > Probing pci nic...
> 
> I think it starts here.  I am trying to setup miniterm, to be able to
> get a dump of the information.  There is a real lack on information on
> how to set up two serial debugging on the Linux side.  I found the
> Etherboot config setting but getting the Linux side configured is a
> pain.

I have been doing it to long :)  Anyway the easy solution should just
be:
connect null modem cable.
run minicom
select your serial port and baud rate.

Watch what is happening...

Eric

RE: [Etherboot-developers] Driver probing twice in latest 5.1 cvs

[Timothy L. <tim...@us...>]

> I have a serial console log of etherboot appended so if you can point
out
> rough where you think an extra probe may be happening I am willing to
take
> a look.


> Starting: EFI Lanboot
> ROM segment 0x0000 length 0x0000 reloc 0xbeedd310
> Etherboot 5.1.5pre2 (GPL) ELF64 for [undi_nii]
> Relocating _text from: [00000040beedd310,00000040beffa8e0) to
> [000000003f0f4a30,000000003f212000)
> ITC 900 Mhz
> Boot from (N)etwork (D)isk (F)loppy or from (L)ocal?
> Probing pci nic...

I think it starts here.  I am trying to setup miniterm, to be able to
get a dump of the information.  There is a real lack on information on
how to set up two serial debugging on the Linux side.  I found the
Etherboot config setting but getting the Linux side configured is a
pain.


> Probing isa nic...
> [undi_nii]Ethernet addr: 00:30:6E:39:96:3A
> Searching for server (DHCP)...
> ..Me: 192.168.0.47, Server: 192.168.0.252, Gateway 192.168.0.252
> Loading 192.168.0.252:dual-ia64-boot.ebi .TFTP error 1 (File not
found)

RE: [Etherboot-developers] for tim: sundance.c

[Timothy L. <tim...@us...>]

> Tim, just looking through your latest sundance driver in CVS. There's
a
> missing virt_to_le32desc at line 323. Possibly another at line 461.

Thanks Ken, I will review

Re: [Etherboot-developers] Driver probing twice in latest 5.1 cvs

[<ebi...@ln...>]

"Timothy Legge" <tim...@us...> writes:

> > > Not much more I can tell you on that one.  Try renaming the file you
> are
> > > tftping without updating the dhcpd.conf file and you shoud see two
> lots
> > > of probe/reset messages.
> > 
> > This later case is intended.
> > 
> > The sequence displayed should be:
> 
> I meant that because the file will not start booting, you may have a
> chance to see the two lots of probing messages...  This is before the
> initial looking for dhcp server (I believe).


Removing/Renaming a file on the tftp server will not cause any activity
until a tftp request is attempted.  A tftp request will not be attempted
until after DHCP reports which file to load, and DHCP tells etherboot which
ip address to use.

I have a serial console log of etherboot appended so if you can point out
rough where you think an extra probe may be happening I am willing to take
a look.

There is a little extra probing in this image as it looks for a disk driver
and I have not compiled one in.  And undi_nii while not really an isa devices,
is weird one off so etherboot considers it an isa device...

Eric


Starting: EFI Lanboot
ROM segment 0x0000 length 0x0000 reloc 0xbeedd310
Etherboot 5.1.5pre2 (GPL) ELF64 for [undi_nii]
Relocating _text from: [00000040beedd310,00000040beffa8e0) to [000000003f0f4a30,000000003f212000)
ITC 900 Mhz
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? 
Probing pci nic...
Probing isa nic...
[undi_nii]Ethernet addr: 00:30:6E:39:96:3A
Searching for server (DHCP)...
..Me: 192.168.0.47, Server: 192.168.0.252, Gateway 192.168.0.252
Loading 192.168.0.252:dual-ia64-boot.ebi .TFTP error 1 (File not found)
Unable to load file.
<sleep>
<abort>
Probing isa nic...
Probing pci disk...
Probing isa disk...
<sleep>
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? 
Probing pci nic...
Probing isa nic...
[undi_nii]Ethernet addr: 00:30:6E:39:96:3A
Searching for server (DHCP)...
..Me: 192.168.0.47, Server: 192.168.0.252, Gateway 192.168.0.252
Loading 192.168.0.252:dual-ia64-boot.ebi .TFTP error 1 (File not found)
Unable to load file.
<sleep>
<abort>
Probing isa nic...
Probing pci disk...
Probing isa disk...
<sleep>
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? 
Probing pci nic...
Probing isa nic...
[undi_nii]Ethernet addr: 00:30:6E:39:96:3A
Searching for server (DHCP)...
..Me: 192.168.0.47, Server: 192.168.0.252, Gateway 192.168.0.252
Loading 192.168.0.252:dual-ia64-boot.ebi .TFTP error 1 (File not found)
Unable to load file.
<sleep>
<abort>
Probing isa nic...
Probing pci disk...
Probing isa disk...
<sleep>
Boot from (N)etwork (D)isk (F)loppy or from (L)ocal? 
Probing pci nic...
Probing isa nic...
[undi_nii]Ethernet addr: 00:30:6E:39:96:3A
Searching for server (DHCP)...
..Me: 192.168.0.47, Server: 192.168.0.252, Gateway 192.168.0.252
Loading 192.168.0.252:dual-ia64-boot.ebi .TFTP error 1 (File not found)
Unable to load file.
<sleep>
<abort>
Probing isa nic...
Probing pci disk...

[Etherboot-developers] for tim: sundance.c

[<ke...@us...>]

Tim, just looking through your latest sundance driver in CVS. There's a
missing virt_to_le32desc at line 323. Possibly another at line 461.

RE: [Etherboot-developers] Driver probing twice in latest 5.1 cvs

[Timothy L. <tim...@us...>]

> > Not much more I can tell you on that one.  Try renaming the file you
are
> > tftping without updating the dhcpd.conf file and you shoud see two
lots
> > of probe/reset messages.
> 
> This later case is intended.
> 
> The sequence displayed should be:

I meant that because the file will not start booting, you may have a
chance to see the two lots of probing messages...  This is before the
initial looking for dhcp server (I believe).

[Etherboot-developers] [COMMIT] fa311 ns8390.c compile fixes...

[<ebi...@ln...>]

fa311.c needed a virt_to_le32desc not virt_to_le32.
ns8390.c  needed to cast the result of bus_to_virt to a char*
because it wanted to read a character...

Eric