Hi,
I'm new to Coreboot, but I've been able to get a BIOS burned and sort of working. I'm working with a Capio II 320 (see specs below) and I've tried using the "Axus TC320" and "ASI MB-5BLMP" build tutorials since the CPU and chipsets are so similar. I've also tried using Etherboot and FILO as the payloads with the same results. The ASI tutorial starts up and initializes the network interface, but I never get any video. With the Axus TC320 tutorial, I get video, the network interface is initialized, and I get a splash screen, but that's where it stops. When using Etherboot I can see that the Capio starts to boot from my network boot server and then stops. Is there a way I can get console output with the Axus TC320 setup? If I could see what's going on I might be able to fix it.
Any help will be greatly appreciated.
Boundless (Neoware) Capio II 320 Cyrix MediaGXm 233MHz Geode CS5530 companion device Intel 82559ER Network Interface 48MB DiskOnChip 32MB SDRAM DIMM
Thanks,
Jeremy
Have you set up serial console? Or is that your question?
ron
No, I haven't set up serial console. Is there documentation on how to do that? I wasn't sure what the next step should be since I'm so unfamiliar with Coreboot.
Thanks.
On Feb 1, 2008 6:59 PM, ron minnich rminnich@gmail.com wrote:
Have you set up serial console? Or is that your question?
ron
I am pretty sure one or both of those targets has serial console enabled. The next thing to do is boot standard bios on that board, with linux, hook up serial to a box you know works, run minicom on each end, and just verify that serial works at all.
Then we can talk about coreboot serial :-)
ron
I can't run Linux on the Capios because they don't have any external drive access, and the only thing that they will boot off of is the DiskOnChip which has Windows CE on it (which wants to see a Windows Terminal Server). One of the reasons that I am trying Coreboot is to get to where I can reprogram the DOC to put Linux on it. So, I'm stuck on testing serial communications with minicom on the Capio end.
Any ideas?
Thanks.
On Feb 1, 2008 7:15 PM, ron minnich rminnich@gmail.com wrote:
I am pretty sure one or both of those targets has serial console enabled. The next thing to do is boot standard bios on that board, with linux, hook up serial to a box you know works, run minicom on each end, and just verify that serial works at all.
Then we can talk about coreboot serial :-)
ron
can you get kermit or some other terminal emulator for windows CE?
just to test?
ron
I'll try to set up a termporary terminal server with Windows XP and see if I can get to the point where I can try kermit or something similar.
On Feb 1, 2008 7:35 PM, ron minnich rminnich@gmail.com wrote:
can you get kermit or some other terminal emulator for windows CE?
just to test?
ron
I got a Windows terminal server set up, but I can't execute the terminal emulator locally. It just runs on the server. The way that Windows CE is set up on the DOC, I can't install (or run) anything locally. It's a remote desktop only client. The best that I can do is "reset it to factory condition" which doesn't give me any more control.
Is there any way I can try serial console without testing the serial communications first?
On Feb 1, 2008 7:39 PM, Jeremy Wright wrightjmf@gmail.com wrote:
I'll try to set up a termporary terminal server with Windows XP and see if I can get to the point where I can try kermit or something similar.
On Feb 1, 2008 7:35 PM, ron minnich rminnich@gmail.com wrote:
can you get kermit or some other terminal emulator for windows CE?
just to test?
ron
On 01.02.2008 20:32, Jeremy Wright wrote:
I can't run Linux on the Capios because they don't have any external drive access, and the only thing that they will boot off of is the DiskOnChip which has Windows CE on it (which wants to see a Windows Terminal Server).
http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=26;t=1216... has some interesting info about Damn Small Linux on the Capio II.
One of the reasons that I am trying Coreboot is to get to where I can reprogram the DOC to put Linux on it. So, I'm stuck on testing serial communications with minicom on the Capio end.
I think that if you manage to reprogram the DOC outside the Capio, you can run Linux and use that to further debug Coreboot.
Regards, Carl-Daniel
http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=26;t=1216...http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=26;t=12165 has some interesting info about Damn Small Linux on the Capio II.
Yeah, I've seen that before, but I'm having a hard time finding a TC325. I'll keep my eyes out for one though. Thanks.
On Feb 2, 2008 4:25 PM, Carl-Daniel Hailfinger < c-d.hailfinger.devel.2006@gmx.net> wrote:
On 01.02.2008 20:32, Jeremy Wright wrote:
I can't run Linux on the Capios because they don't have any external
drive
access, and the only thing that they will boot off of is the DiskOnChip which has Windows CE on it (which wants to see a Windows Terminal
Server).
http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=26;t=1216... has some interesting info about Damn Small Linux on the Capio II.
One of the reasons that I am trying Coreboot is to get to where I can reprogram the DOC to put Linux on it. So, I'm stuck on testing serial communications with minicom on the Capio end.
I think that if you manage to reprogram the DOC outside the Capio, you can run Linux and use that to further debug Coreboot.
Regards, Carl-Daniel
On 03.02.2008 05:09, Jeremy Wright wrote:
http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=26;t=1216... has some interesting info about Damn Small Linux on the Capio II.
Yeah, I've seen that before, but I'm having a hard time finding a TC325. I'll keep my eyes out for one though. Thanks.
In theory, someone who already has DSL on the Capio II should be able to run some diagnostic tools (flashrom, superiotool, lspci -nnvvvxxx, dmidecode, dmesg). The contents of /proc/iomem, /proc/ioports, /proc/interrupts would also be interesting. Maybe that gives us enough information about memory ranges that should be avoided etc.
Regards, Carl-Daniel
Well, I wasn't able to get the output of any commands from a Capio running DSL, but I tried hooking the first serial port up to a laptop and I got some data when the Capio is powered on and the splash screen comes up (it's not much though). I assume that means there is some data exchange going on, but I'm not sure where to go next. The program I used was not a terminal emulator, it was just a serial program that captured all the hex output from the serial port. Is there any way to set up a serial console now so that I can see what FILO/Etherboot are doing?
Thanks,
Jeremy
On Feb 3, 2008 10:30 PM, Carl-Daniel Hailfinger < c-d.hailfinger.devel.2006@gmx.net> wrote:
On 03.02.2008 05:09, Jeremy Wright wrote:
http://damnsmalllinux.org/cgi-bin/forums/ikonboard.cgi?act=Print;f=26;t=1216...
has some interesting info about Damn Small Linux on the Capio II.
Yeah, I've seen that before, but I'm having a hard time finding a TC325. I'll keep my eyes out for one though. Thanks.
In theory, someone who already has DSL on the Capio II should be able to run some diagnostic tools (flashrom, superiotool, lspci -nnvvvxxx, dmidecode, dmesg). The contents of /proc/iomem, /proc/ioports, /proc/interrupts would also be interesting. Maybe that gives us enough information about memory ranges that should be avoided etc.
Regards, Carl-Daniel
On Friday 01 February 2008 19:47, Jeremy Wright wrote:
Hi,
I'm new to Coreboot, but I've been able to get a BIOS burned and sort of working. I'm working with a Capio II 320 (see specs below) and I've tried using the "Axus TC320" and "ASI MB-5BLMP" build tutorials since the CPU and chipsets are so similar. I've also tried using Etherboot and FILO as the payloads with the same results. The ASI tutorial starts up and initializes the network interface, but I never get any video. With the Axus TC320 tutorial, I get video, the network interface is initialized, and I get a splash screen, but that's where it stops. When using Etherboot I can see that the Capio starts to boot from my network boot server and then stops. Is there a way I can get console output with the Axus TC320 setup? If I could see what's going on I might be able to fix it.
Any help will be greatly appreciated.
Boundless (Neoware) Capio II 320 Cyrix MediaGXm 233MHz Geode CS5530 companion device Intel 82559ER Network Interface 48MB DiskOnChip 32MB SDRAM DIMM
Sounds like my CAPIO Boundless II. I also tried this to boot via coreboot, but without success. There is no serial device available on this target for debugging purposes and the 82559 seems special as the standard etherboot for this device fails also.
Getting a console with coreboot might help for coreboot, but etherboot for example cannot use it. So if etherboot fails you will stick at the same point.
Juergen
Hi Juergen,
Is it that you don't have the superio (or whatever it's called) parallel/serial card for the Capio, or does Coreboot not recognize it? I have the card, I just need to know how to use it for debugging, or even if I can.
Have you tried FILO with your Capio? I got the same result with it which makes me wonder if the problem is something other than the 82559.
On Feb 1, 2008 9:30 PM, Juergen Beisert juergen127@kreuzholzen.de wrote:
On Friday 01 February 2008 19:47, Jeremy Wright wrote:
Hi,
I'm new to Coreboot, but I've been able to get a BIOS burned and sort of working. I'm working with a Capio II 320 (see specs below) and I've
tried
using the "Axus TC320" and "ASI MB-5BLMP" build tutorials since the CPU
and
chipsets are so similar. I've also tried using Etherboot and FILO as the payloads with the same results. The ASI tutorial starts up and
initializes
the network interface, but I never get any video. With the Axus TC320 tutorial, I get video, the network interface is initialized, and I get a splash screen, but that's where it stops. When using Etherboot I can see that the Capio starts to boot from my network boot server and then
stops.
Is there a way I can get console output with the Axus TC320 setup? If I could see what's going on I might be able to fix it.
Any help will be greatly appreciated.
Boundless (Neoware) Capio II 320 Cyrix MediaGXm 233MHz Geode CS5530 companion device Intel 82559ER Network Interface 48MB DiskOnChip 32MB SDRAM DIMM
Sounds like my CAPIO Boundless II. I also tried this to boot via coreboot, but without success. There is no serial device available on this target for debugging purposes and the 82559 seems special as the standard etherboot for this device fails also.
Getting a console with coreboot might help for coreboot, but etherboot for example cannot use it. So if etherboot fails you will stick at the same point.
Juergen
On Feb 1, 2008 1:47 PM, Jeremy Wright wrightjmf@gmail.com wrote:
Hi Juergen,
Is it that you don't have the superio (or whatever it's called) parallel/serial card for the Capio, or does Coreboot not recognize it? I have the card, I just need to know how to use it for debugging, or even if I can.
can you run any programs on this node at all? Can you assemble a program? How does this thing boot anyway.
ron
I can't run any programs on the node or assemble anything.
The Capio BIOS boots a DiskOnChip (48 meg Flash drive) just like it would a hard drive. The DOC contains a pre-burned copy of Windows CE that is preconfigured to only give you the remote desktop connection dialog. I can bring up the standard Windows CE F2 menu, but it doesn't have any options to give me local access. So, the options that I've come up with so far are Coreboot, and buying/building an adapter card for the DOC. I would rather have the flexibility of Coreboot if at all possible though.
On Feb 1, 2008 9:52 PM, ron minnich rminnich@gmail.com wrote:
On Feb 1, 2008 1:47 PM, Jeremy Wright wrightjmf@gmail.com wrote:
Hi Juergen,
Is it that you don't have the superio (or whatever it's called) parallel/serial card for the Capio, or does Coreboot not recognize it? I have the card, I just need to know how to use it for debugging, or even
if I
can.
can you run any programs on this node at all? Can you assemble a program? How does this thing boot anyway.
ron
Hi Jeremy,
On Friday 01 February 2008 22:47, Jeremy Wright wrote:
Is it that you don't have the superio (or whatever it's called) parallel/serial card for the Capio, or does Coreboot not recognize it?
This box has a superio, but the serial lines are not physically available.
I have the card, I just need to know how to use it for debugging, or even if I can.
Hmm, I have to reopen the box to see what's in it.
Have you tried FILO with your Capio? I got the same result with it which makes me wonder if the problem is something other than the 82559.
I tried with etherboot only. But it failed, and without a serial console no chance to discover why.
Juergen
Hi Jeremy,
On Saturday 02 February 2008 10:04, Juergen Beisert wrote:
On Friday 01 February 2008 22:47, Jeremy Wright wrote:
Is it that you don't have the superio (or whatever it's called) parallel/serial card for the Capio, or does Coreboot not recognize it?
This box has a superio, but the serial lines are not physically available.
Ups, sorry. A few minutes ago I opened the box again and: There is no SuperIO! At least in this box are no serial lines available, no LPT aso. Only a very small device for PS/2 keyboard and mouse support.
Juergen
Thanks for checking Juergen. I'm hoping that having the SuperIO card will help me figure out what's going on. I did find out through ethereal that Etherboot is communicating with the server, it's just not loading the image correctly.
I'll let you know what I find out.
Thanks again.
On Feb 2, 2008 11:08 AM, Juergen Beisert juergen127@kreuzholzen.de wrote:
Hi Jeremy,
On Saturday 02 February 2008 10:04, Juergen Beisert wrote:
On Friday 01 February 2008 22:47, Jeremy Wright wrote:
Is it that you don't have the superio (or whatever it's called) parallel/serial card for the Capio, or does Coreboot not recognize it?
This box has a superio, but the serial lines are not physically
available.
Ups, sorry. A few minutes ago I opened the box again and: There is no SuperIO! At least in this box are no serial lines available, no LPT aso. Only a very small device for PS/2 keyboard and mouse support.
Juergen
On 01.02.2008 19:47, Jeremy Wright wrote:
I'm new to Coreboot, but I've been able to get a BIOS burned and sort of working. I'm working with a Capio II 320 (see specs below) and I've tried using the "Axus TC320" and "ASI MB-5BLMP" build tutorials since the CPU and chipsets are so similar. I've also tried using Etherboot and FILO as the payloads with the same results. The ASI tutorial starts up and initializes the network interface, but I never get any video. With the Axus TC320 tutorial, I get video, the network interface is initialized, and I get a splash screen, but that's where it stops. When using Etherboot I can see that the Capio starts to boot from my network boot server and then stops.
Does that mean etherboot manages to load something over the network for both the Axus and the ASI target?
Is there a way I can get console output with the Axus TC320 setup? If I could see what's going on I might be able to fix it.
Since you got as far as having etherboot retrieve something over the network, the obvious next step would be to: - control etherboot over the network (no idea if that is possible) or - have etherboot load a payload which communicates over the network.
Once you establish interaction over the network, a serial console is still desirable, but you can control the hardware and make the serial console work.
Regards, Carl-Daniel
According to the logs on my LTSP server (using TFTP), it's the Capio is getting an IP address and then not requesting anything. Am I confused about how Etherboot works?
Can Etherboot load a secondary payload like that?
On Feb 1, 2008 10:01 PM, Carl-Daniel Hailfinger < c-d.hailfinger.devel.2006@gmx.net> wrote:
On 01.02.2008 19:47, Jeremy Wright wrote:
I'm new to Coreboot, but I've been able to get a BIOS burned and sort of working. I'm working with a Capio II 320 (see specs below) and I've
tried
using the "Axus TC320" and "ASI MB-5BLMP" build tutorials since the CPU
and
chipsets are so similar. I've also tried using Etherboot and FILO as the payloads with the same results. The ASI tutorial starts up and
initializes
the network interface, but I never get any video. With the Axus TC320 tutorial, I get video, the network interface is initialized, and I get a splash screen, but that's where it stops. When using Etherboot I can see that the Capio starts to boot from my network boot server and then
stops.
Does that mean etherboot manages to load something over the network for both the Axus and the ASI target?
Is there a way I can get console output with the Axus TC320 setup? If I
could
see what's going on I might be able to fix it.
Since you got as far as having etherboot retrieve something over the network, the obvious next step would be to:
- control etherboot over the network (no idea if that is possible) or
- have etherboot load a payload which communicates over the network.
Once you establish interaction over the network, a serial console is still desirable, but you can control the hardware and make the serial console work.
Regards, Carl-Daniel
On 01.02.2008 23:05, Jeremy Wright wrote:
According to the logs on my LTSP server (using TFTP), it's the Capio is getting an IP address and then not requesting anything. Am I confused about how Etherboot works?
Does the DHCP server ever get a DHCPREQUEST response to its DHCPOFFER packet? If you're not sure, a pcap log (via ethereal or tcpdump) as attachment to the list should help us diagnose whether the Capio really receives packets from the server. Note: The pcap log should have 4 packets and be reasonably small (~300-2000 bytes).
Can Etherboot load a secondary payload like that?
Well, it can load a payload, so it should be able to load a payload which interacts over the network.
Regards, Carl-Daniel
On Feb 1, 2008 2:42 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 01.02.2008 23:05, Jeremy Wright wrote:
Can Etherboot load a secondary payload like that?
Sure. I've loaded filo and etherboot with etherboot.
ron
Yes, the server gets a DHCPREQUEST response to its DHCPOFFER. I took the ethereal advice and found that not only is DHCP working, but TFTP is working as well. I noticed it was loading the nbi.img image (sucessfully), so I switched it to pxelinux.0 and got a different response. The client starts to load the pxelinux.0 image, gets to block 2, and then resets, asks for an address via DHCP again, and starts trying to download the image again until it gets to block 2. It will keep going in this loop forever unless I stop it. When it loads the nbi.img file, it doesn't have the looping problem.
I have included the output from ethereal below hoping that it will shed some light on the situation.
I'm a little puzzled. Should I try another version of Etherboot? I'm using version 5.2.6.
Thanks,
Jeremy
No. Time Source Destination Protocol Info 1 0.000000 0.0.0.0 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe16c0e9 2 0.028507 Cisco-Li_0b:4f:e7 Broadcast ARP Who has 192.168.0.247? Tell 192.168.0.1 3 0.704732 192.168.0.1 192.168.0.247 DHCP DHCP Offer - Transaction ID 0xe16c0e9 4 0.705118 192.168.0.247 255.255.255.255 DHCP DHCP Request - Transaction ID 0xe16c0e9 5 0.737300 192.168.0.1 192.168.0.247 DHCP DHCP ACK - Transaction ID 0xe16c0e9 6 0.737626 Ncr_16:c0:5e Broadcast ARP Who has 192.168.0.1? Tell 192.168.0.247 7 0.737660 192.168.0.1 192.168.0.247 ICMP Echo (ping) request 8 0.737669 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP 192.168.0.1 is at 00:18:f8:0b:4f:e7 9 0.737757 192.168.0.247 192.168.0.1 TFTP Read Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, blksize=1432 10 0.739513 192.168.0.1 192.168.0.247 TFTP Option Acknowledgement, blksize=1432 11 0.739640 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 0 12 0.739770 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 1 13 0.740292 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 1 14 0.740343 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 15 1.740598 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 16 3.776443 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 17 5.736343 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 18 6.736318 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 19 7.736294 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 20 7.812340 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 21 7.981137 192.168.0.247 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe16c176 22 7.981593 192.168.0.1 192.168.0.247 DHCP DHCP Offer - Transaction ID 0xe16c176 23 7.981976 192.168.0.247 255.255.255.255 DHCP DHCP Request - Transaction ID 0xe16c176 24 7.985617 192.168.0.1 192.168.0.247 DHCP DHCP ACK - Transaction ID 0xe16c176 25 7.985927 Ncr_16:c0:5e Broadcast ARP Who has 192.168.0.1? Tell 192.168.0.247 26 7.985959 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP 192.168.0.1 is at 00:18:f8:0b:4f:e7 27 7.986042 192.168.0.247 192.168.0.1 TFTP Read Request, File: /ltsp/i386/pxelinux.0, Transfer type: octet, blksize=1432 28 7.987704 192.168.0.1 192.168.0.247 TFTP Option Acknowledgement, blksize=1432 29 7.987824 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 0 30 7.987947 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 1 31 7.988477 192.168.0.247 192.168.0.1 TFTP Acknowledgement, Block: 1 32 7.988554 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 33 8.988357 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 34 11.024306 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 35 12.988160 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 36 13.988134 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 37 14.988108 Cisco-Li_0b:4f:e7 Ncr_16:c0:5e ARP Who has 192.168.0.247? Tell 192.168.0.1 38 15.060153 192.168.0.1 192.168.0.247 TFTP Data Packet, Block: 2 39 15.226659 192.168.0.247 255.255.255.255 DHCP DHCP Discover - Transaction ID 0xe16c1f6
...and so on and so on
On Feb 1, 2008 10:43 PM, ron minnich rminnich@gmail.com wrote:
On Feb 1, 2008 2:42 PM, Carl-Daniel Hailfinger c-d.hailfinger.devel.2006@gmx.net wrote:
On 01.02.2008 23:05, Jeremy Wright wrote:
Can Etherboot load a secondary payload like that?
Sure. I've loaded filo and etherboot with etherboot.
ron
On 02.02.2008 02:46, Jeremy Wright wrote:
Yes, the server gets a DHCPREQUEST response to its DHCPOFFER. I took the ethereal advice and found that not only is DHCP working, but TFTP is working as well. I noticed it was loading the nbi.img image (sucessfully), so I
Good. How big is nbi.img?
switched it to pxelinux.0 and got a different response. The client starts to load the pxelinux.0 image, gets to block 2, and then resets, asks for an address via DHCP again, and starts trying to download the image again until it gets to block 2. It will keep going in this loop forever unless I stop it. When it loads the nbi.img file, it doesn't have the looping problem.
That looks a lot like memory problems, but it is only a gut feeling. (One image is loaded completely , another image with a possibly different load address causes a crash.) A size comparison and load address comparison could help debug the issue.
I'm a little puzzled. Should I try another version of Etherboot? I'm using version 5.2.6.
There is a small chance that the behaviour of Etherboot 5.4.3 is different. Please try it.
Is there any chance you can try to have etherboot load etherboot? The problem with that is of course that the second etherboot has to send a different ID string for its DHCP requests, otherwise you can't find out whether the new DHCP request is from the flashed etherboot after the machine resets itself or from the etherboot loaded over the network.
However, my experience with etherboot is very limited, but Ron and others know a LOT about it.
Regards, Carl-Daniel
Good. How big is nbi.img?
nbi.img is 5.6 MB and pxelinux.0 is 12.8 kB.
That looks a lot like memory problems, but it is only a gut feeling. (One image is loaded completely , another image with a possibly different load address causes a crash.) A size comparison and load address comparison could help debug the issue.
I tried switching out the SDRAM and it didn't make any difference. Is that what you meant or should I try a different ROM chip? Is there documentation on how to do size and load address comparisons?
There is a small chance that the behaviour of Etherboot 5.4.3 is different. Please try it.
I'll do that.
Is there any chance you can try to have etherboot load etherboot?
Is there any documentation on how to load etherboot with etherboot?
Thanks.
On Feb 2, 2008 2:22 AM, Carl-Daniel Hailfinger < c-d.hailfinger.devel.2006@gmx.net> wrote:
On 02.02.2008 02:46, Jeremy Wright wrote:
Yes, the server gets a DHCPREQUEST response to its DHCPOFFER. I took the ethereal advice and found that not only is DHCP working, but TFTP is
working
as well. I noticed it was loading the nbi.img image (sucessfully), so I
Good. How big is nbi.img?
switched it to pxelinux.0 and got a different response. The client
starts to
load the pxelinux.0 image, gets to block 2, and then resets, asks for an address via DHCP again, and starts trying to download the image again
until
it gets to block 2. It will keep going in this loop forever unless I
stop
it. When it loads the nbi.img file, it doesn't have the looping problem.
That looks a lot like memory problems, but it is only a gut feeling. (One image is loaded completely , another image with a possibly different load address causes a crash.) A size comparison and load address comparison could help debug the issue.
I'm a little puzzled. Should I try another version of Etherboot? I'm
using
version 5.2.6.
There is a small chance that the behaviour of Etherboot 5.4.3 is different. Please try it.
Is there any chance you can try to have etherboot load etherboot? The problem with that is of course that the second etherboot has to send a different ID string for its DHCP requests, otherwise you can't find out whether the new DHCP request is from the flashed etherboot after the machine resets itself or from the etherboot loaded over the network.
However, my experience with etherboot is very limited, but Ron and others know a LOT about it.
Regards, Carl-Daniel
where does nbi.img load and where does etherboot load?
ron
I'm not sure where either of the images load since I can't run any applications locally on the client. Is there a way to see where applications load from there server side? Sorry if that's a naive question, but I'm pretty new to this.
On Feb 2, 2008 3:21 AM, ron minnich rminnich@gmail.com wrote:
where does nbi.img load and where does etherboot load?
ron
-
Carl-Daniel Hailfinger -
Jeremy Wright -
Juergen Beisert -
ron minnich