etherboot-developers Mailing List for Etherboot (Page 201)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-developers — Discussion of developer issues
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
(10) |
Sep
(3) |
Oct
(10) |
Nov
(47) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(41) |
Feb
(107) |
Mar
(76) |
Apr
(103) |
May
(66) |
Jun
(72) |
Jul
(27) |
Aug
(31) |
Sep
(33) |
Oct
(18) |
Nov
(33) |
Dec
(67) |
| 2002 |
Jan
(25) |
Feb
(62) |
Mar
(79) |
Apr
(74) |
May
(67) |
Jun
(104) |
Jul
(155) |
Aug
(234) |
Sep
(87) |
Oct
(93) |
Nov
(54) |
Dec
(114) |
| 2003 |
Jan
(146) |
Feb
(104) |
Mar
(117) |
Apr
(189) |
May
(96) |
Jun
(40) |
Jul
(133) |
Aug
(136) |
Sep
(113) |
Oct
(142) |
Nov
(99) |
Dec
(185) |
| 2004 |
Jan
(233) |
Feb
(151) |
Mar
(109) |
Apr
(96) |
May
(200) |
Jun
(175) |
Jul
(162) |
Aug
(118) |
Sep
(107) |
Oct
(77) |
Nov
(121) |
Dec
(114) |
| 2005 |
Jan
(201) |
Feb
(271) |
Mar
(113) |
Apr
(119) |
May
(69) |
Jun
(46) |
Jul
(21) |
Aug
(37) |
Sep
(13) |
Oct
(4) |
Nov
(19) |
Dec
(46) |
| 2006 |
Jan
(10) |
Feb
(18) |
Mar
(85) |
Apr
(2) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(10) |
Jul
(20) |
Aug
(9) |
Sep
(11) |
Oct
(4) |
Nov
(1) |
Dec
(40) |
| 2008 |
Jan
(19) |
Feb
(8) |
Mar
(37) |
Apr
(28) |
May
(38) |
Jun
(63) |
Jul
(31) |
Aug
(22) |
Sep
(37) |
Oct
(38) |
Nov
(49) |
Dec
(24) |
| 2009 |
Jan
(48) |
Feb
(51) |
Mar
(80) |
Apr
(55) |
May
(34) |
Jun
(57) |
Jul
(20) |
Aug
(83) |
Sep
(17) |
Oct
(81) |
Nov
(53) |
Dec
(40) |
| 2010 |
Jan
(55) |
Feb
(28) |
Mar
(36) |
Apr
(7) |
May
|
Jun
|
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
(3) |
Dec
|
| 2011 |
Jan
(1) |
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
|
Nov
(10) |
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: <ke...@us...> - 2003-04-16 08:12:25
|
In order to give 5.1.8 (development branch) wider testing, I have uploaded a patch from 5.1.7 to 5.1.8rc1 at this URL: http://sourceforge.net/tracker/index.php?func=detail&aid=722329&group_id=4233&atid=304233 This will make it easier for people to test it without access to CVS. You need compiler tools though. Please report successes and problems to the developers list. Preemptive FAQs: You want to do "make bin/3c509.zdsk" or "make bin/3c509.zfd0" for example, not make bin32/3c509.lzdsk, etc. The EEPRO100 timing patch hasn't been included yet, you can get them from a mail by Georg Baum of about a week ago. You need to retag the kernel with a recent mknbi if you are trying to boot LTSP. Etherboot will not respond to DHCP offers without a filename; this is expected. |
|
From: <ke...@us...> - 2003-04-15 23:46:18
|
>What is a good editor for the doc book format? I would like to add some thin >gs to the developers manual. It's text format (SGML) so any text editor should work. But you have to balance the tags yourself. Apparently OpenOffice 1.1 currently in beta has support for Docbook. |
|
From: <ja...@Mc...> - 2003-04-15 16:40:44
|
On Tue, 15 Apr 2003, Timothy Legge wrote: > Hi Ken > > What is a good editor for the doc book format? I would like to add > some things to the developers manual. My favorite Docbook editor is good old vi Jim McQuillan ja...@Lt... > > Particularly on the process involved in developing card driver based > on a Linux driver. I think I have learned a few things that may be > useful, but I am sure some of it will be misleading and some of it > downright wrong so I will want some vetting of it before it goes in. > > Tim > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Etherboot-developers mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-developers > -- |
|
From: Timothy L. <tl...@ro...> - 2003-04-15 15:59:24
|
Hi Ken What is a good editor for the doc book format? I would like to add some things to the developers manual. Particularly on the process involved in developing card driver based on a Linux driver. I think I have learned a few things that may be useful, but I am sure some of it will be misleading and some of it downright wrong so I will want some vetting of it before it goes in. Tim |
|
From: <ke...@us...> - 2003-04-15 02:16:17
|
>Nevermind, a different (non virtual) pc worked. sundance has now been >back ported to 5.0 and added to the 5.0 cvs. Well done. Thanks! |
|
From: Timothy L. <tl...@ro...> - 2003-04-15 02:04:44
|
> Any idea what could cause that? > Nevermind, a different (non virtual) pc worked. sundance has now been back ported to 5.0 and added to the 5.0 cvs. Tim |
|
From: Timothy L. <tl...@ro...> - 2003-04-15 00:50:14
|
The sooner 5.1 is the production release the better. =A0;-)=A0 =A0I have = spent far too much time hunting through the 5.0 source to add support for the sundance driver.=A0 Now that I think I have found all the places, I am plagued with a screen that goes blank with a cursor moving around it after the driver starts probing. =A0 Any idea what could cause that? =A0 Tim |
|
From: Timothy L. <tl...@ro...> - 2003-04-14 23:39:10
|
> I assume you mean you have two NICs in your machine. Sounds reasonable. > But you should also try to boot the LTSP kernel off a local disk, and > also to boot it on another motherboard to rule out BIOS interactions. Yes, I had both the 3c905 and the sundance card in at the same time. I have booted the 2.4.19 kernel that it is based on, but not the ltsp kernel Jim compiled. I will give it a shot. Tim |
|
From: <ke...@us...> - 2003-04-14 23:04:19
|
>1) Added a 3c905 with 5.0 boot rom to download the ltsp kernel >2) modified the NIC= for the 3c905 to be NIC=sundance >3) the client boots with the 3c905 EB driver and downloads the ltsp >kernel >4) the linux driver loads and it loads the sundance module. >5) The client stops trying to mount the root partition. > >So I am thinking that the problem is in the ltsp initialization of >sundance driver or the linux driver itself. > >What do you think? Is this a valid way to validate that the problem is >probably not in the etherboot driver? I assume you mean you have two NICs in your machine. Sounds reasonable. But you should also try to boot the LTSP kernel off a local disk, and also to boot it on another motherboard to rule out BIOS interactions. |
|
From: Timothy L. <tl...@ro...> - 2003-04-14 22:05:00
|
> The disable routine must be coded to leave the NIC in a clean state. I think the problem may be in the linux driver of the ltsp code. I did the following: 1) Added a 3c905 with 5.0 boot rom to download the ltsp kernel 2) modified the NIC= for the 3c905 to be NIC=sundance 3) the client boots with the 3c905 EB driver and downloads the ltsp kernel 4) the linux driver loads and it loads the sundance module. 5) The client stops trying to mount the root partition. So I am thinking that the problem is in the ltsp initialization of sundance driver or the linux driver itself. What do you think? Is this a valid way to validate that the problem is probably not in the etherboot driver? Tim |
|
From: <ke...@us...> - 2003-04-14 15:22:16
|
>Hi. I had some problems with my laptop's sis900 ethernet interface. I >used the linux kernel source and found out a my revision works a bit >different from the other sis900's. I have merged the changes from the >kernel and made it work. I have attached the diff - feel free... > > >Best regards > >Morten Kristiansen >Denmark Thank you! Applied to 5.0 and 5.1. |
|
From: <ke...@us...> - 2003-04-14 02:41:39
|
>Do you think there is anything in the Etherboot driver that >could be mucking up the card where it doesn't work properly >with the Linux driver ? The disable routine must be coded to leave the NIC in a clean state. |
|
From: <ja...@Mc...> - 2003-04-14 02:35:31
|
On Mon, 14 Apr 2003, Ken Yap wrote: > >I tracked down the multiple transmission error and worked with Jim on > >debugging. The client seems to be getting the correct ip address and > >the sundance driver is loaded. However, it does not have the $ROOT_PATH > >set and cannot mount the nfs partition. > > Did you assign the root path option for that client in your DHCPD config? He mentioned that ROOT_PATH wasn't set, but I don't think that's a problem. It's just an env variable in the /linuxrc script, and I'm not even sure i had him check it properly. What we do see is the client sending an ARP request for the server's IP address. The server sends the response, and then the client sends another arp request. This happens once per second. From what I can tell, it will keep going forever. It's like the driver isn't seeing the reply. It is in the Linux kernel at this point. Do you think there is anything in the Etherboot driver that could be mucking up the card where it doesn't work properly with the Linux driver ? Jim. |
|
From: <ke...@us...> - 2003-04-14 02:16:46
|
>I tracked down the multiple transmission error and worked with Jim on >debugging. The client seems to be getting the correct ip address and >the sundance driver is loaded. However, it does not have the $ROOT_PATH >set and cannot mount the nfs partition. Did you assign the root path option for that client in your DHCPD config? |
|
From: Timothy L. <tl...@ro...> - 2003-04-14 02:10:34
|
The story so far: I tracked down the multiple transmission error and worked with Jim on debugging. The client seems to be getting the correct ip address and the sundance driver is loaded. However, it does not have the $ROOT_PATH set and cannot mount the nfs partition. The only thing I notice is that when Linux booted, the sundance module reported using MII #0 instead of the MII #1 that Etherboot used. The driver is self booting, I let it go for 10 minutes and it had no issues. I assume that the disable routine is working (it is being called). Would self-booting an EB rom react badly if the disable routine was not working? The only other thing I might be able to do is set the PowerMgt state to D0 (Uninitialized) I am sure of the base address though (the data sheet list it as PCI device configuration header start). Any thoughts? Tim |
|
From: Timothy L. <tl...@ro...> - 2003-04-13 23:23:29
|
> Ok, then you have two bugs. The EB driver is transmitting twice but that > didn't stop it from loading and running the kernel. Except for one One bug down, the sundance data sheet says that the address of the next frame should be zero if there is only one frame (I was following the tulip card too closely). > thing, the bugs should be unrelated: Did you also remember to implement > the disable routine and to register it? It is registered by the probe function as: dev->disable = sundance_disable; Is that what you mean by register? Marty, if you are listening, would you mind testing the latest CVS with your card? I would like to rule out something stupid in my configuration. Tim |
|
From: Morten K. <mk...@va...> - 2003-04-13 23:06:03
|
Hi. I had some problems with my laptop's sis900 ethernet interface. I used the linux kernel source and found out a my revision works a bit different from the other sis900's. I have merged the changes from the kernel and made it work. I have attached the diff - feel free... Best regards Morten Kristiansen Denmark |
|
From: <ke...@us...> - 2003-04-13 21:54:24
|
>I have a 3 meg tcp dump file that shows sundance doing everything from >requesting the file to acknologing the receipt of each packet twice. >There is probably another reason why it stops after the Linux driver >loads, but I think I should figure the out the duplicate transmits >first. Ok, then you have two bugs. The EB driver is transmitting twice but that didn't stop it from loading and running the kernel. Except for one thing, the bugs should be unrelated: Did you also remember to implement the disable routine and to register it? |
|
From: Timothy L. <tl...@ro...> - 2003-04-13 16:02:32
|
> It's the Linux driver that dhclient calls. > > But you say it's the EB driver that sends twice. This means that it went > awry earlier than you say. You are aware, I'm sure, that once the kernel > is loaded, EB is out of the picture. Sorry for being unclear. I started drafting the message while I still thought the EB driver had no bugs (silly me). I have a 3 meg tcp dump file that shows sundance doing everything from requesting the file to acknologing the receipt of each packet twice. There is probably another reason why it stops after the Linux driver loads, but I think I should figure the out the duplicate transmits first. I have two hunches, I think I have a bug in the transmit status check and I am wondering whether the card should be set to poll for transmits. Tim |
|
From: <ja...@Mc...> - 2003-04-13 14:31:31
|
On Sun, 13 Apr 2003, Ken Yap wrote: > >Jim McQuillan was good enough to roll a new 2.4.19 ltsp kernel with the > >sundance driver and tagged with the latest mknbi. The sundanc driver > >grabs the kernel just fine, starts it and loads the linux sundance > >driver just fine. However, after ltsp calls the dhclient things go > >awry. > > > >He helped me to review a tcpdump and noticed that the driver was > >acknowledging everything twice (indeed it seems to be transmitting > >everything two times). > > > >I am looking through the code, but so far I can't find the issue. Any > >ideas? > > Since this is the Linux driver, I doubt if it's a gross driver error. > Are you by any chance running 2 copies of dhclient? He's seeing the double packets while it is under Etherboot control. He sent me the packet trace, and I looked at it with ethereal, and for every tftp packet that he receives, he is sending back 2 acks. It does get the entire kernel, but then at the end, it dies with several ARP requests that seem to go un answered. Jim McQuillan ja...@Lt... |
|
From: <ke...@us...> - 2003-04-13 13:17:41
|
>> Since this is the Linux driver, I doubt if it's a gross driver error. >> Are you by any chance running 2 copies of dhclient? > >Not that I know of, but actually the EB driver is the one transmitting >everything twice I quote you: >Jim McQuillan was good enough to roll a new 2.4.19 ltsp kernel with the >sundance driver and tagged with the latest mknbi. The sundanc driver >grabs the kernel just fine, starts it and loads the linux sundance >driver just fine. However, after ltsp calls the dhclient things go >awry. It's the Linux driver that dhclient calls. But you say it's the EB driver that sends twice. This means that it went awry earlier than you say. You are aware, I'm sure, that once the kernel is loaded, EB is out of the picture. |
|
From: Timothy L. <tl...@ro...> - 2003-04-13 13:03:37
|
> Since this is the Linux driver, I doubt if it's a gross driver error. > Are you by any chance running 2 copies of dhclient? Not that I know of, but actually the EB driver is the one transmitting everything twice |
|
From: <ke...@us...> - 2003-04-13 06:25:27
|
>Jim McQuillan was good enough to roll a new 2.4.19 ltsp kernel with the >sundance driver and tagged with the latest mknbi. The sundanc driver >grabs the kernel just fine, starts it and loads the linux sundance >driver just fine. However, after ltsp calls the dhclient things go >awry. > >He helped me to review a tcpdump and noticed that the driver was >acknowledging everything twice (indeed it seems to be transmitting >everything two times). > >I am looking through the code, but so far I can't find the issue. Any >ideas? Since this is the Linux driver, I doubt if it's a gross driver error. Are you by any chance running 2 copies of dhclient? |
|
From: Timothy L. <tl...@ro...> - 2003-04-13 02:55:42
|
Hi Jim McQuillan was good enough to roll a new 2.4.19 ltsp kernel with the sundance driver and tagged with the latest mknbi. The sundanc driver grabs the kernel just fine, starts it and loads the linux sundance driver just fine. However, after ltsp calls the dhclient things go awry. He helped me to review a tcpdump and noticed that the driver was acknowledging everything twice (indeed it seems to be transmitting everything two times). I am looking through the code, but so far I can't find the issue. Any ideas? Tim |
|
From: H. P. A. <hp...@zy...> - 2003-04-12 03:46:30
|
Eric W. Biederman wrote: > > Except when I implement sanity checks there is no parsing with ELF > headers either, the structures area all native endian, and wordsize. > The difference is load this chunk into memory at this address, and > load these other chunks into memory at these other addresses, and > finally jump there. > Right... I have a coarse-grained routine that maps the file at a single address without looking at it at all first. > I get some real portability and prototyping benefits because it is > a standard file format. But when space is at an absolute premium > those aren't the most important things. Right. Note that I usually use standard ELF tools to construct COM32 images, and then just "objcopy -O binary" to finish. Very simple. > > Especially when there is proper tail recursion. :) > > I already use that test path with ELF images. And if the recursion > stops before I tell it to I know there is something wrong! > > And it already exist with the mknbi format as well. > Hmmm.... :/ -hpa |
53 messages has been excluded from this view by a project administrator.
