Thread: [Etherboot-developers] Driver probing twice in latest 5.1 cvs
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers
|
From: Timothy L. <tim...@us...> - 2003-01-17 00:39:09
|
Hi I was fooling around with the sundance driver once again after a cvs update an hour ago. It seems that the driver is being probed twice. Any thoughts? Tim |
|
From: <ebi...@ln...> - 2003-01-17 00:45:11
|
"Timothy Legge" <tim...@us...> writes: > Hi > > I was fooling around with the sundance driver once again after a cvs > update an hour ago. It seems that the driver is being probed twice. > Any thoughts? Not enough detail. What when is it getting probed? Eric |
|
From: Timothy L. <tim...@us...> - 2003-01-17 01:10:36
|
> Not enough detail. What when is it getting probed? Sorry. I had boot from the floppy and hit the N for Network. (Also happened when I didn't hit N). I noticed right away, that the screen looked weird. The PC bios dump/info was not in the screen and there was no way the driver should spew enough info to get rid of it. I thought first that the sundance_reset was getting called twice, but when I looked at the messages closely, it seems that the code is probing the nic twice. 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. Tim |
|
From: <ebi...@ln...> - 2003-01-17 01:25:50
|
"Timothy Legge" <tim...@us...> writes: > > Not enough detail. What when is it getting probed? > > Sorry. I had boot from the floppy and hit the N for Network. (Also > happened when I didn't hit N). I noticed right away, that the screen > looked weird. The PC bios dump/info was not in the screen and there was > no way the driver should spew enough info to get rid of it. Ah. So it would take a serial console to capture everything, and understand what is going on... > I thought first that the sundance_reset was getting called twice, but > when I looked at the messages closely, it seems that the code is probing > the nic twice. Hmm. I can't think of a normal case without errors where that should happen. When ever it retries it reprobes as to be as safe as possible. And having a boot menu will get a reprobe to reinitialize the card. > 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: probe DHCP TFTP (get an error) reset <abort> (and sleep one second) (restart or give up depending on the compile options). Eric |
|
From: Timothy L. <tim...@us...> - 2003-01-17 01:43:45
|
> > 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). |
|
From: <ebi...@ln...> - 2003-01-17 01:57:20
|
"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... |
|
From: Timothy L. <tim...@us...> - 2003-01-17 02:42:40
|
> 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) |
|
From: <ebi...@ln...> - 2003-01-17 02:57:47
|
"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 |
|
From: <ebi...@ln...> - 2003-01-17 17:51:04
|
"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 |
|
From: Timothy L. <tim...@us...> - 2003-01-18 20:43:22
|
> 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... |
