etherboot-users — Discussion of user issues

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971 - SOLVED

[Krzysztof L. <krz...@li...>]

Krzysztof Lichota wrote:
> Krzysztof Lichota wrote:
> 
>> Timothy Legge wrote:
>>
>>> I don't have time tonight to look, but some additional details 
>>> regarding the hardware that you have would help.  The issue you 
>>> reference below was only seen on one model of HP Vectra.
>>
>> Exactly. It is HP Vectra VL5/200 MMX.
> 
> 
> I attach more hardware details from Linux proc.
> 
> I can see that in RPL boot, ethernet controller is assigned IRQ 2 while 
> later on it has IRQ 9. Maybe it is a problem?

Victory! :)
I suspected a problem with interrupts and it was it!
I looked into AMD specs for the chip, added code to disable interrupts 
and it worked :) I am able to boot into LTSP up to XDM login screen :)

Patch attached. It is a bit verbose, but probably it has to be changed 
anyway as I don't know if it does not spoil something for other chips.

Regards

	Krzysztof Lichota

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

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

On Jun 17, 2005, at 2:10 PM, Michael Brown wrote:
> On Fri, 17 Jun 2005, Krzysztof Lichota wrote:
>>> Are you sure you're using Etherboot?  We don't have any code that
>>> supports RPL, nor do we use NDIS drivers.  Is it possible that you're
>>> using a different product?
>> I am loading Etherboot ROM using RPL.
> Out of curiosity, how?  We have no rplprefix.S; does RPL allow you to
> download and execute a PCI/ISA option ROM image (.rom), or are you 
> using a
> ..dsk image with floppy drive emulation, etc.?
> Michael

This sounded familiar somehow, so I did some searching and found the 
message below.  There are probably other ways to do it, but I remember 
thinking this was a neat hack.

Marty

> From: 	  val...@no...
> Subject: 	Re: [Etherboot-users] load an etherboot-rom by ethernet
> Date: 	August 17, 2004 12:21:10 PM EDT
> To: 	  eth...@li...
> Cc: 	  da...@ix...
>
> Hi,
>
> At Mon, Aug 16, 2004 at 02:08:27PM -0700, Mike Castle wrote:
>> Out of curiosity, how are you serving up RPL?  I have an machine that
>> supports RPL but not PXE, and if I could get an RPL -> etherboot 
>> solution
>> going, that would be way cool.  :->
>
> Hee, I got it to work. Here's how.
>
> - get rpld http://gimel.esc.cam.ac.uk/james/rpld/index.html version 
> 1.7 (1.8
> crashes for me)
> - make; make
> - set rpld.conf to the following:
> HOST {
> 	ethernet = 00:de:ad:be:ef:01;
> 	FILE {
> 	path="/tmp/rom.iso";
> 	load=0x1000;
> 	};
> 	execute=0x1000;
> };
>
> start rpld with  ./rpld -C ./rpld.conf -f (or something alike)
>
> Then download the http://rom-o-matic.net/5.3.8/ rom image. For some 
> reason,
> the "binary rom image" wouldn't work here (it started but hung when
> detecting the ethernet card), even if I chose "execute=0x1006" (as 
> someone
> suggested on this list). The 5.2.5 would work with a ROM image, but 
> those
> don't support PXEboot which is what I want, so I went for 5.3.8 and 
> chose
> the "isolinux without floppy" option.
>
> That worked nicely. The 5.3.8 rom would load our pxelinux stuff and in 
> turn
> a kernel would load.
>
> The only thing I'm fighting now is that, for some obscure reason, the 
> NIC of
> the RPL server needs to be in promiscuous mode. This is probably due to
> protocol incompatibilities in IBM/ Novell implementation or so.
> Communications now go like this:
> RPLclient->broadcast: hello, anyone there?
>
> RPLserver->client: hello, I'm here to serve you
>
> RPLclient->some mac address that I don't recognize: well, send me the 
> files
> RPLclient->some mac address that I don't recognize: well, send me the 
> files
> RPLclient->some mac address that I don't recognize: well, send me the 
> files
> RPLclient->some mac address that I don't recognize: well, send me the 
> files
> [ad nauseam]
>
> Why it would have this Mac address is a mistery to me, but a hacking
> workaround is to use promisc in the mean time.
>
> We still have some issues with the kernel that's being loaded: the 
> first one
> we tried kept crashing and rebooting after the "unloading NIC" 
> message. This
> might be due to a wrong processor or kernel size or other unknown 
> things.
> We chose another, simpler kernel (the generic Debian boot kernel) and 
> this
> made our first RPLbooted workstation (sorta) functioning this 
> afternoon.
>
> Thanks everyone so far!
>
> V.
> -- 
> http://www.openoffice.nl/   Open Office - Linux Office Solutions
> Valentijn Sessink  val...@no...

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Krzysztof L. <krz...@li...>]

Michael Brown wrote:
> On Fri, 17 Jun 2005, Krzysztof Lichota wrote:
> 
>>>Are you sure you're using Etherboot?  We don't have any code that
>>>supports RPL, nor do we use NDIS drivers.  Is it possible that you're
>>>using a different product?
>>
>>I am loading Etherboot ROM using RPL.
> 
> 
> Out of curiosity, how?  We have no rplprefix.S; does RPL allow you to
> download and execute a PCI/ISA option ROM image (.rom), or are you using a
> .dsk image with floppy drive emulation, etc.?

I am using .zlilo binary - Linux kernel-compatible binary can be 
downloaded and executed. I am using rpld daemon to do that, with example 
configuration for memtest86, modified to point to etherboot rom, instead 
of memtest86.
Client (Vectra) must be set in BIOS to RPL/Microsoft in order for that 
to work.

Hope this explains everything :)

Regards

	Krzysztof Lichota

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Michael B. <mb...@fe...>]

On Fri, 17 Jun 2005, Krzysztof Lichota wrote:
> > Are you sure you're using Etherboot?  We don't have any code that
> > supports RPL, nor do we use NDIS drivers.  Is it possible that you're
> > using a different product?
> I am loading Etherboot ROM using RPL.

Out of curiosity, how?  We have no rplprefix.S; does RPL allow you to
download and execute a PCI/ISA option ROM image (.rom), or are you using a
.dsk image with floppy drive emulation, etc.?

Michael

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Krzysztof L. <krz...@li...>]

Michael Brown wrote:
> On Fri, 17 Jun 2005, Krzysztof Lichota wrote:
> 
>>Etherboot ROM is loaded using RPL (remote boot protocol). It prints the 
>>following settings:
>>RPL-ROM-ADR: 0060 B0C1 3893
>>RPL-ROM-DMA: 5
>>RPL-ROM-IRQ: 2
>>RPL-ROM-PIO: FCE0
>>
>>I have also tried creating Netboot boot rom with NDIS driver (from AMD 
>>site) and it does not work. I cannot create rom with packet driver, it 
>>says something about executable using too much memory.
> 
> 
> Are you sure you're using Etherboot?  We don't have any code that supports 
> RPL, nor do we use NDIS drivers.  Is it possible that you're using a 
> different product?

I am loading Etherboot ROM using RPL.
I mentioned NDIS driver (wrapped using netboot) just to confirm that it 
is not working either.

Regards

	Krzysztof Lichota

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Michael B. <mb...@fe...>]

On Fri, 17 Jun 2005, Krzysztof Lichota wrote:
> Etherboot ROM is loaded using RPL (remote boot protocol). It prints the 
> following settings:
> RPL-ROM-ADR: 0060 B0C1 3893
> RPL-ROM-DMA: 5
> RPL-ROM-IRQ: 2
> RPL-ROM-PIO: FCE0
> 
> I have also tried creating Netboot boot rom with NDIS driver (from AMD 
> site) and it does not work. I cannot create rom with packet driver, it 
> says something about executable using too much memory.

Are you sure you're using Etherboot?  We don't have any code that supports 
RPL, nor do we use NDIS drivers.  Is it possible that you're using a 
different product?

Michael

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Krzysztof L. <krz...@li...>]

Krzysztof Lichota wrote:
> I attach more hardware details from Linux proc.

> ==> /proc/pci <==
> PCI devices found:
>   Bus  0, device  11, function  0:
>     Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 37).
>       IRQ 9.
>       Master Capable.  Latency=64.  Min Gnt=6.Max Lat=255.
>       I/O at 0xfce0 [0xfcff].
>       Non-prefetchable 32 bit memory at 0xfedffc00 [0xfedffc1f].
> ==> /proc/ioports <==
> fce0-fcff : Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]
>   fce0-fcff : pcnet32_probe_pci
> 
> ==> /proc/iomem <==
> fedffc00-fedffc1f : Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE]

Strange - PCI reports it as 79c970 while driver detects it as 79c971.

	Krzysztof Lichota

Re: [Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Krzysztof L. <krz...@li...>]

Krzysztof Lichota wrote:
> Timothy Legge wrote:
>> I don't have time tonight to look, but some additional details 
>> regarding the hardware that you have would help.  The issue you 
>> reference below was only seen on one model of HP Vectra.
> 
> 
> Exactly. It is HP Vectra VL5/200 MMX.

I attach more hardware details from Linux proc.

I can see that in RPL boot, ethernet controller is assigned IRQ 2 while 
later on it has IRQ 9. Maybe it is a problem?

Regards

	Krzysztof Lichota

[Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

[Krzysztof L. <krz...@li...>]

Timothy Legge wrote:
> Hi
> 
> If you are not subscribed to the etherboot-users list please do so.  I 
> always get the messages to the list but sometimes my inbox gets full or 
> worse (your email was marked as spam for instance)

OK. I am sending my reply here.

> I don't have time tonight to look, but some additional details regarding 
> the hardware that you have would help.  The issue you reference below 
> was only seen on one model of HP Vectra.

Exactly. It is HP Vectra VL5/200 MMX.

According to BIOS, the following devices are on:
Parallel port - IRQ 7
Serial port 1 - IRQ 4
Serial port 2 - IRQ 3
IDE Adapters - IRQ 14 and 15
Integrated ethernet interface (PCNet/Fast) - ?
USB interface - ?
Modem - IRQ 3 or IRQ 4 (there is no modem, so I guess it does not matter)

According to power-on setting, there should also be assigned IRQ 12 to 
PS/2 mouse.

All PCI IRQ lines in BIOS are set to "Auto".

Etherboot ROM is loaded using RPL (remote boot protocol). It prints the 
following settings:
RPL-ROM-ADR: 0060 B0C1 3893
RPL-ROM-DMA: 5
RPL-ROM-IRQ: 2
RPL-ROM-PIO: FCE0

I have also tried creating Netboot boot rom with NDIS driver (from AMD 
site) and it does not work. I cannot create rom with packet driver, it 
says something about executable using too much memory.

Hope this helps.

Regards

	Krzysztof Lichota

[Etherboot-users] Re: Problem with Etherboot driver for PCnet/FAST 79C971

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

Hi

If you are not subscribed to the etherboot-users list please do so.  I 
always get the messages to the list but sometimes my inbox gets full or 
worse (your email was marked as spam for instance)

I don't have time tonight to look, but some additional details regarding 
the hardware that you have would help.  The issue you reference below 
was only seen on one model of HP Vectra.

Tim

Krzysztof Lichota wrote:
> Hello!
> I see in driver source code that you are the author of driver, so I hope 
> you can help me.
> I have got some computers with PCnet/FAST 79C971 ethernet controllers. 
> Unfortunately, they are not working with etherboot driver pcnet32 even 
> in latest release 5.4.0.
> Using standard etherboot driver, loading hangs right after printing "at 
> ioaddr FCE0,". I have seen an e-mail thread on etherboot-developers 
> list, but it ended without conclusion.
> 
> I have tried to fix it myself and here are the results of my experiments:
> I have verified that standard Linux driver works (linux kernel 2.4.27), 
> you can see dmesg output attached.
> 
> I have added tracing messages to locate place where it hangs and the 
> first place was "Trigger initialization just for the interrupt". I have 
> disabled this code and this went through.
> I have looked into Linux driver code and it seems that this code is not 
> executed in my case, so I think it is OK to disable it.
> 
> Next it stuck in "We used to clear InitDone bit". I have added setting 
> this bit and it went further. This is not compatible with what Linux 
> driver does.
> 
> With these two changes, booting with etherboot is going up to the point 
> where DHCP requests are sent. I am getting DHCP request (DHCPDISCOVER) 
> on server and it sends back DHCPOFFER, but client is hanging.
> 
> I have added more tracing to see where it hangs and it seems it is 
> hanging some time after triggering send poll in pcnet32_transmit(). I 
> suspect so, because if some tracing messages are printed, if there are a 
> few of them (commented out in attached patch), client hangs in the 
> middle of printing message to console, before finishing function 
> pcnet32_transmit(). If there is only message at the end of function, it 
> is printed OK.
> 
> I suspect a problem with interrupts, but I do not have expertise in 
> network drivers :(
> I have tried adding changes based on changes in Linux driver from base 
> version of your driver (1.27a) up to Linux kernel version 2.4.27, but 
> with no luck. I have also experimented with some other options 
> (disabling/enabling DXSUFLO), but it didn't help.
> 
> I would appreciate any help. I have working environment for compiling 
> etherboot set up, so I can test any patches you send. If you need any 
> further information, I will be happy to provide it.
> 
> TIA
> 
> Kind regards
> 
>     Krzysztof Lichota
> 
> 
> ------------------------------------------------------------------------
> 
> Linux version 2.4.27 (ar...@re...) (gcc version 3.3.4 (PLD Linux)) #1 Thu Jul 15 21:46:57 CEST 2004
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
>  BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
>  BIOS-e820: 00000000000f1c24 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 0000000002000000 (usable)
>  BIOS-e820: 00000000fffe0000 - 0000000100000000 (reserved)
> 0MB HIGHMEM available.
> 32MB LOWMEM available.
> On node 0 totalpages: 8192
> zone(0): 4096 pages.
> zone(1): 4096 pages.
> zone(2): 0 pages.
> DMI not present.
> ACPI: Unable to locate RSDP
> Kernel command line: initrd=initrd.ide root=/dev/ram0 init=/linuxrc CONF="`/dev/fd0:/rescue`;;;;;;;;;;;" BOOT_IMAGE=vmlinuz 
> No local APIC present or hardware disabled
> Initializing CPU#0
> Detected 199.435 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 398.13 BogoMIPS
> Memory: 29352k/32768k available (1136k kernel code, 3028k reserved, 483k data, 120k init, 0k highmem)
> Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
> Inode cache hash table entries: 2048 (order: 2, 16384 bytes)
> Mount cache hash table entries: 512 (order: 0, 4096 bytes)
> Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Intel Pentium with F0 0F bug - workaround enabled.
> CPU:     After generic, caps: 008001bf 00000000 00000000 00000000
> CPU:             Common caps: 008001bf 00000000 00000000 00000000
> CPU: Intel Pentium MMX stepping 03
> Checking 'hlt' instruction... OK.
> POSIX conformance testing by UNIFIX
> mtrr: v1.40 (20010327) Richard Gooch (rg...@at...)
> mtrr: detected mtrr type: none
> ACPI: Subsystem revision 20040326
> ACPI: Interpreter disabled.
> PCI: PCI BIOS revision 2.10 entry at 0xf7142, last bus=0
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: Probing PCI hardware (bus 00)
> Limiting direct PCI/PCI transfers.
> Activating ISA DMA hang workarounds.
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Initializing RT netlink socket
> Starting kswapd
> kinoded started
> devfs: v1.12c (20020818) Richard Gooch (rg...@at...)
> devfs: boot_options: 0x0
> Detected PS/2 Mouse Port.
> pty: 256 Unix98 ptys configured
> Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16550A
> ttyS01 at 0x02f8 (irq = 3) is a 16550A
> Real Time Clock Driver v1.10f
> floppy0: no floppy controllers found
> NET4: Frame Diverter 0.46
> COMX: driver version 0.85 (C) 1995-1999 ITConsult-Pro Co. <in...@it...>
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> loop: loaded (max 8 devices)
> Initializing Cryptographic API
> IEEE 802.2 LLC for Linux 2.1 (c) 1996 Tim Alpaerts
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> IP: routing cache hash table of 512 buckets, 4Kbytes
> TCP: Hash tables configured (established 2048 bind 4096)
> Linux IP multicast router 0.06 plus PIM-SM
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 541k freed
> FAT: bogus logical sector size 49488
> VFS: Mounted root (romfs filesystem) readonly.
> Freeing unused kernel memory: 120k freed
> Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PIIX3: IDE controller at PCI slot 00:0f.1
> PIIX3: chipset revision 0
> PIIX3: not 100% native mode: will probe irqs later
>     ide0: BM-DMA at 0xfcb0-0xfcb7, BIOS settings: hda:pio, hdb:pio
>     ide1: BM-DMA at 0xfcb8-0xfcbf, BIOS settings: hdc:pio, hdd:pio
> hda: LG DVD-ROM DRD-8120B, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> hda: attached ide-cdrom driver.
> hda: ATAPI 40X DVD-ROM drive, 512kB Cache
> Uniform CD-ROM driver Revision: 3.12
> ISO 9660 Extensions: Microsoft Joliet Level 3
> ISO 9660 Extensions: RRIP_1991A
> usb.c: registered new driver usbdevfs
> usb.c: registered new driver hub
> uhci.c: USB Universal Host Controller Interface driver v1.1
> uhci.c: USB UHCI at I/O 0xfcc0, IRQ 11
> usb.c: new USB bus registered, assigned bus number 1
> hub.c: USB hub found
> hub.c: 2 ports detected
> usb.c: registered new driver hiddev
> usb.c: registered new driver hid
> hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <vo...@su...>
> hid-core.c: USB HID support drivers
> mice: PS/2 mouse device common for all mice
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> pcnet32.c:v1.30c 05.25.2004 tsb...@al...
> pcnet32: PCnet/FAST 79C971 at 0xfce0, 00 60 b0 c1 38 93
>     tx_start_pt(0x0c00):~220 bytes, BCR18(9861):BurstWrEn BurstRdEn NoUFlow 
>     SRAMSIZE=0x7f00, SRAM_BND=0x3f00, assigned IRQ 9.
> divert: allocating divert_blk for eth0
> eth0: registered as PCnet/FAST 79C971
> pcnet32: 1 cards_found.
> eth0: link down
> IPv6 v0.8 for NET4.0
> IPv6 over IPv4 tunneling driver
> divert: not allocating divert_blk for non-ethernet device sit0
> eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
> eth0: no IPv6 routers present
> 
> 
> ------------------------------------------------------------------------
> 
> --- drivers/net/pcnet32.c.orig	2004-06-01 17:55:01.000000000 +0200
> +++ drivers/net/pcnet32.c	2005-06-16 08:13:25.550372056 +0200
> @@ -521,18 +521,19 @@
>  	lp->a.write_csr(ioaddr, 4, 0x0915);
>  	lp->a.write_csr(ioaddr, 0, 0x0001);
>  
>  
>  	i = 0;
> -	while (i++ < 100)
> +	while (i++ < 1000)
>  		if (lp->a.read_csr(ioaddr, 0) & 0x0100)
>  			break;
>  	/* 
>  	 * We used to clear the InitDone bit, 0x0100, here but Mark Stockton
>  	 * reports that doing so triggers a bug in the '974.
>  	 */
> -	lp->a.write_csr(ioaddr, 0, 0x0042);
> +//KLOLD:	lp->a.write_csr(ioaddr, 0, 0x0042);
> +	lp->a.write_csr(ioaddr, 0, 0x0042 | 0x0100);
>  
>  	dprintf(("pcnet32 open, csr0 %hX.\n", lp->a.read_csr(ioaddr, 0)));
>  
>  }
>  
> @@ -552,10 +553,11 @@
>  	status = ((short) le16_to_cpu(rx_ring[entry].status) >> 8);
>  
>  	if (status < 0)
>  		return 0;
>  
> +	dprintf(("pcnet32_poll received something\n"));
>  	if ( ! retrieve ) return 1;
>  
>  	if (status == 0x03) {
>  		nic->packetlen =
>  		    (le32_to_cpu(rx_ring[entry].msg_length) & 0xfff) - 4;
> @@ -582,10 +584,11 @@
>  			     unsigned int t,	/* Type */
>  			     unsigned int s,	/* size */
>  			     const char *p)
>  {				/* Packet */
>  	/* send the packet to destination */
> +	dprintf(("pcnet32_transmit start\n"));
>  	unsigned long time;
>  	u8 *ptxb;
>  	u16 nstype;
>  	u16 status;
>  	int entry = 0;		/*lp->cur_tx & TX_RING_MOD_MASK; */
> @@ -611,25 +614,29 @@
>  
>  	/* we set the top byte as the very last thing */
>  	tx_ring[entry].status = le16_to_cpu(status);
>  
>  
> +//	dprintf(("pcnet32_transmit before send poll\n"));
>  	/* Trigger an immediate send poll */
>  	lp->a.write_csr(ioaddr, 0, 0x0048);
> +//	dprintf(("pcnet32_transmit after send poll\n"));
>  
>  	/* wait for transmit complete */
>  	lp->cur_tx = 0;		/* (lp->cur_tx + 1); */
>  	time = currticks() + TICKS_PER_SEC;	/* wait one second */
>  	while (currticks() < time &&
>  	       ((short) le16_to_cpu(tx_ring[entry].status) < 0));
>  
>  	if ((short) le16_to_cpu(tx_ring[entry].status) < 0)
>  		printf("PCNET32 timed out on transmit\n");
>  
> +//	dprintf(("pcnet32_transmit before stop pointing\n"));
>  	/* Stop pointing at the current txb
>  	 * otherwise the card continues to send the packet */
>  	tx_ring[entry].base = 0;
> +	dprintf(("pcnet32_transmit end\n"));
>  
>  }
>  
>  /**************************************************************************
>  DISABLE - Turn off ethernet interface
> @@ -896,12 +903,12 @@
>  	 * interrupts. For ISA boards we get a DMA error, but VLB and PCI
>  	 * boards will work.
>  	 */
>  	/* Trigger an initialization just for the interrupt. */
>  
> -	a->write_csr(ioaddr, 0, 0x41);
> -	mdelay(1);
> +//KL:	a->write_csr(ioaddr, 0, 0x41);
> +//KL:	mdelay(1);
>  
>  	cards_found++;
>  
>  	/* point to NIC specific routines */
>  	pcnet32_reset(nic);

[Etherboot-users] Re: etherboot pci wifi

[<fel...@gm...>]

Hi,

>>I do not have the hardware yet.  I looked into the source and it seems as I
>>should buy a card mentioned at the beginning of  drivers/net/prism2_plx.c. 
>>I started looking on ebay, but didn't find the right card yet.

> fortunatly i own such a card ;-)

>>As I do not have the hardware yet I'd be happy about someone else testing
>>the prism support, but if nobody is able to I will try it in the next weeks
>>myself.

> i tried with an old tekram tc-400 .... wow what an old card ;-)

> maybe my card is not working correctly, never get it to work
> with linux directly .. and the original M$ drivers are a P.I.T.A!! :-o

As I am kind of interested in this project I bought a card for myself it is a 
3com AirConnect 3CRWE777A. [1]

I did not receive the card yet, but as soon as I have it, I will try etherboot 
with it and report back.

MfG
Felix

[1] http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=5779358226

Re: [Etherboot-users] Re: [Thinstation-general] Boot Error RX Overrun (0001)

[Jacky <jac...@gm...>]

Hi,=20
this happened sometime if using hub and if using switching it's ok.
maybe network busy or corrupt.


On 6/10/05, Trevor Batley <tre...@us...> wrote:
> Quoting Jacky <jac...@gm...>:
>=20
> > Hi all,
> > I have a problem  when booting thinstation 2.0.2 and error message RX
> > Overrun(0001)  I use 3c905-tx and rom AT29c512 (etherboot 5.2.5)
> > What's mean RX Overrun (0001) and what's cause "RX Overrun", how to
> > solved this problem
>=20
> etherboot 5.2.5 was released in 1998. Any reason you are using such an ol=
d
> version. Try with the 'Universal boot floppy' or a newly built etherboot =
floppy
> from rom-o-matic (http://rom-o-matic.net). If that still fails, then we m=
ay
> need to look at something else (possibly a corrupt thinstation.zpxe file,=
 or
> irq conflicts, etc.)
>=20
> Trevor B
> >
> > Searching for Server (DHCP)
> > Me : 172.16.184.174 Server 172.16.184.20 Gateway 172.16.184.254
> > Triming .ZPXE extention
> > loading 172.16.184.20:thinstation.nbi(NBI) 3c90x : RX Overrun(0001)
> > 3c90x:RX Overrun(0001)
> > 3c90x:RX Overrun(0001)
> > 3c90x:RX Overrun(0001)
> > 3c90x:RX Overrun(0001)
> > 3c90x:RX Overrun(0001)
> >
> > thanks
> > --
> > Regards,
> >
> > Jacky
> >
> >
> > -------------------------------------------------------
> > This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you s=
hotput
> > a projector? How fast can you ride your desk chair down the office luge
> > track?
> > If you want to score the big prize, get to know the little guy.
> > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
> > _______________________________________________
> > Thinstation-general mailing list
> > Thi...@li...
> > https://lists.sourceforge.net/lists/listinfo/thinstation-general
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you sho=
tput
> a projector? How fast can you ride your desk chair down the office luge t=
rack?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you sho=
tput
> a projector? How fast can you ride your desk chair down the office luge t=
rack?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
> _______________________________________________
> Thinstation-general mailing list
> Thi...@li...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general
>=20


--=20
Regards,

Jacky

Re: [Etherboot-users] Boot Error RX Overrun (0001)

[Michael B. <mb...@fe...>]

On Fri, 10 Jun 2005, Jacky wrote:
> I have a problem  when booting thinstation 2.0.2 and error message RX
> Overrun(0001)  I use 3c905-tx and rom AT29c512 (etherboot 5.2.5)
> What's mean RX Overrun (0001) and what's cause "RX Overrun", how to
> solved this problem
> 
> Searching for Server (DHCP)
> Me : 172.16.184.174 Server 172.16.184.20 Gateway 172.16.184.254
> Triming .ZPXE extention
> loading 172.16.184.20:thinstation.nbi(NBI) 3c90x : RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)

RX overrun is when packets are received faster than Etherboot can deal 
with them.  It should only happen on a very busy network, or a very slow 
machine.  Do you have an excess amount of broadcast traffic on your 
network?

Michael

[Etherboot-users] Re: [Thinstation-general] Boot Error RX Overrun (0001)

[Trevor B. <tre...@us...>]

Quoting Jacky <jac...@gm...>:

> Hi all,
> I have a problem  when booting thinstation 2.0.2 and error message RX
> Overrun(0001)  I use 3c905-tx and rom AT29c512 (etherboot 5.2.5)
> What's mean RX Overrun (0001) and what's cause "RX Overrun", how to
> solved this problem

etherboot 5.2.5 was released in 1998. Any reason you are using such an old
version. Try with the 'Universal boot floppy' or a newly built etherboot floppy
from rom-o-matic (http://rom-o-matic.net). If that still fails, then we may
need to look at something else (possibly a corrupt thinstation.zpxe file, or
irq conflicts, etc.)

Trevor B
>
> Searching for Server (DHCP)
> Me : 172.16.184.174 Server 172.16.184.20 Gateway 172.16.184.254
> Triming .ZPXE extention
> loading 172.16.184.20:thinstation.nbi(NBI) 3c90x : RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
> 3c90x:RX Overrun(0001)
>
> thanks
> --
> Regards,
>
> Jacky
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
> a projector? How fast can you ride your desk chair down the office luge
> track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
> _______________________________________________
> Thinstation-general mailing list
> Thi...@li...
> https://lists.sourceforge.net/lists/listinfo/thinstation-general

[Etherboot-users] Boot Error RX Overrun (0001)

[Jacky <jac...@gm...>]

Hi all,
I have a problem  when booting thinstation 2.0.2 and error message RX
Overrun(0001)  I use 3c905-tx and rom AT29c512 (etherboot 5.2.5)
What's mean RX Overrun (0001) and what's cause "RX Overrun", how to
solved this problem

Searching for Server (DHCP)
Me : 172.16.184.174 Server 172.16.184.20 Gateway 172.16.184.254
Triming .ZPXE extention
loading 172.16.184.20:thinstation.nbi(NBI) 3c90x : RX Overrun(0001)
3c90x:RX Overrun(0001)
3c90x:RX Overrun(0001)
3c90x:RX Overrun(0001)
3c90x:RX Overrun(0001)
3c90x:RX Overrun(0001)

thanks
--=20
Regards,

Jacky

Re: flashing custom bios Was: [Etherboot-users] booting diskless

[Carl K. <ca...@pe...>]

> This is similar to using the socket on 3C905B NIC cards to write flash 
> chips for RTL8139 or LINKSYS cards using the bromutil program that comes 
> with Etherboot in the contrib directory.

Does it have to be a 3C905 "B" or will any 3c905 (with a socket) do?

Just to say I have done it, and to add to the database of what has been done, I 
want to burn an e-prom useing a NIC.  I have an e-propm a friend yanked out of a 
P1 box before he threw it out:

586 ami bios, Winbond W29EE011-15, 96241

I have the following nics (all have sockets the eprom will fit in.  I have no idea 
what the pinout is.)

lspci:
0000:00:0d.0 Ethernet controller: 3Com Corporation 3c905 100BaseTX [Boomerang]

isa:
eepro_init_module: Auto-detecting boards (May God protect us...)
  id: 0xb4  io: 0x2c0 eth%d: Intel EtherExpress Pro/10 ISA at 0x2c0, 
00:aa:00:69:ff:2e, IRQ 10, 10BaseT.

eexpress.c: Module autoprobe not recommended, give io=xx.
eth%d: EtherExpress 16 at 0x320 (IRQ 10, RJ45 connector, 16-bit bus, 32k RAM)

The Pro boots with "Boot from Network (y/n)?" but seems to only do novel, so it's 
eprom is proably ready to be upgraded too.

Sooo... will any of these work for me?

[Etherboot-users] LinuxWorld Expo San Francisco, August 2005

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

We're in!!

I just talked to Duncan Newell at IDG, and we've got a .ORG booth at 
LinuxWorld Expo San Francisco, which runs August 8-11, 2005 at the 
Moscone Center!

Here's a URL to the show site:

     http://www.linuxworldexpo.com/live/12/events/12SFO05A/SN131341

This will be our 9th appearance, and I look forward to it. In February 
we had Anselm, Vasil, and Markus in Boston, and hopefully we will have 
even more folks visiting and helping in the booth in San Francisco.

We also had a totally cool "For the Love of Free Software" party that I 
co-sponsored with Google.  I hope we can do another one in San 
Francisco, even better!

I've already started working on logistics, and if anyone wants to help, 
or has suggestions for something interesting for our booth (we do try 
to make it memorable :), please let us know.

For those who have never attended a LinuxWorld Expo, I highly recommend 
it.  It's neat to see so many vendors and users of Free and Open Source 
software.  There are lots of sessions, and just a lot of neat geeks to 
hang out with and get to know.

I can't wait!

Marty

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

[Etherboot-users] PXE-Stack

[Tobias W. <tob...@ma...>]

Hello.

Is it possible to put the etherboot pxe-stack into an eprom/flashrom and 
to use it? Are there any information how to do that? 

TIA,

	Tobias

Re: [Etherboot-users] Fwd: hi thered-link dfe-538tx revised E1

[Carlos P. <cpa...@ci...>]

El Mi=E9 08 Jun 2005 06:58, abhi escribi=F3:
> hi carlos
> is there any i can do this in windows
> cause i would have to install a full fleged linux machine to run lspci
>
> :-S
not exactly in windows, but in the bios, just before booting windows, the B=
IOS=20
shows some information about the PCI devices attached to the system and the=
=20
PCI IDs of them. you need to determine what line corresponds to your=20
ethernet, and then copy the PCI IDs=20

other way can be: inside windows go to system tools>system information and =
in=20
the hardware section look for your ethernet card (i don't know if you has=20
installed it with drivers or no) and find a string PCI_VEN9999&DEV_8888
where 9999 and 8888 are the numbers that i need

thanks

Re: [Etherboot-users] could some one tell me how to find pci id in windows or dos

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

On Jun 8, 2005, at 6:17 AM, abhi wrote:
> hi
>  =A0could some one tell me how to find pci id in windows or dos insted=20=

> of installing a full linux distro 'cause i do not have any disk space=20=

> to install it
>  n then install lscpi

Check out the page:

     http://www.idhw.com/textual/guide/inst_type_known_no.html

Look for the PCI program by Craig Hart.  There is a DOS version and a=20
Windows version.

I use the DOS version, which I believe you can download at:

     http://members.datafast.net.au/dft0802/downloads/pci.zip

It displays PCI IDs, subvendor information, and lots of other=20
information.

It also supports output redirection under DOS, so you can do:

     C:\PCI> PCI > LOG.TXT

and get the output in LOG.TXT.

Here is some sample output:

--------------------

     Craig Hart's PCI+AGP bus sniffer, version 0.41, freeware made in=20
1996-2000.

     PCI BIOS Version 2.10 found!
     Number of PCI Busses : 1
     PCI Characteristics  : Config Mechanism 1 Special Cycle Mechanism 1

     Searching for PCI Devices using the System BIOS

      Vendor 8086h Intel Corporation
      Device 7100h 82439TX 430TX System Controller
      Command 0006h (Memory Access, BusMaster)
      Status 2200h (Received Master Abort, Medium Timing)
      Revision 01h, Header Type 00h, Bus Latency 20h
      Self test 00h (Self test not supported)
      PCI Class Bridge, type PCI to HOST

      Vendor 8086h Intel Corporation
      Device 7110h 82371AB PIIX4 ISA Bridge
      Command 000Fh (I/O Access, Memory Access, BusMaster, Special=20
Cycles)
      Status 0280h (Supports Back-To-Back Trans., Medium Timing)
      Revision 01h, Header Type 80h, Bus Latency 00h
      Self test 00h (Self test not supported)
      PCI Class Bridge, type PCI to ISA

      Vendor 8086h Intel Corporation
      Device 7111h 82371AB/EB/MB PIIX4 EIDE Controller
      Command 0005h (I/O Access, BusMaster)
      Status 0280h (Supports Back-To-Back Trans., Medium Timing)
      Revision 01h, Header Type 00h, Bus Latency 20h
      Self test 00h (Self test not supported)
      PCI Class Storage, type IDE
      PCI EIDE Controller Features :
       BusMaster EIDE is supported
       Primary   Channel is at I/O Port 01F0h and IRQ 14
       Secondary Channel is at I/O Port 0170h and IRQ 15
      Address 4 is an I/O Port : 0000F000h

      Vendor 8086h Intel Corporation
      Device 7112h 82371AB/EB/MB PIIX4 USB Controller
      Command 0005h (I/O Access, BusMaster)
      Status 0280h (Supports Back-To-Back Trans., Medium Timing)
      Revision 01h, Header Type 00h, Bus Latency 20h
      Self test 00h (Self test not supported)
      PCI Class Serial, type USB (UHCI)
      Address 4 is an I/O Port : 00006400h
      System IRQ 11, INT# D

      Vendor 8086h Intel Corporation
      Device 7113h 82371AB PIIX4 Power Management Controller
      Command 0003h (I/O Access, Memory Access)
      Status 0280h (Supports Back-To-Back Trans., Medium Timing)
      Revision 01h, Header Type 00h, Bus Latency 00h
      Self test 00h (Self test not supported)
      PCI Class Bridge, type PCI to Other

      Vendor 1002h ATI Technologies
      Device 4752h Rage XL
      Command 0087h (I/O Access, Memory Access, BusMaster, Wait Cycles)
      Status 0290h (Has Capabilities List, Supports Back-To-Back Trans.,=20=

Medium Timing)
      Revision 27h, Header Type 00h, Bus Latency 20h
      Self test 00h (Self test not supported)
      Cache line size 32 Bytes (8 DWords)
      PCI Class Display, type VGA
      Subsystem ID 80081002h Unknown
      Subsystem Vendor 1002h ATI Technologies
      Address 0 is a Memory Address (anywhere in 0-4Gb) : E0000000h
      Address 1 is an I/O Port : 00006500h
      Address 2 is a Memory Address (anywhere in 0-4Gb) : E1000000h
      System IRQ 10, INT# A
      Expansion ROM of 128Kb decoded by this card
      New Capabilities List Information :
       Power Management Capabilities
         Supports Power state D2
         Supports Power state D1
         Supports reduced clock speed (when idle)
         Current power state : D0

[ Here's what we're looking for ]

      Vendor 10ECh Realtek Semiconductor
      Device 8139h RT8139 (A/B/C/8130) Fast Ethernet Adapter
      Command 0007h (I/O Access, Memory Access, BusMaster)
      Status 0290h (Has Capabilities List, Supports Back-To-Back Trans.,=20=

Medium Timing)
      Revision 10h, Header Type 00h, Bus Latency 20h
      Self test 00h (Self test not supported)
      PCI Class Network, type Ethernet
      Subsystem ID 813911F6h Unknown
      Subsystem Vendor 11F6h Compex / Powermatic Data Systems Ltd
      Address 0 is an I/O Port : 00006600h
      Address 1 is a Memory Address (anywhere in 0-4Gb) : E1001000h
      System IRQ 9, INT# A
      New Capabilities List Information :
       Power Management Capabilities
         Supports Power state D2
         Supports Power state D1
         Supports reduced clock speed (when idle)
         Current power state : D0

     ROM PCI IRQ routing table Windows 9x Compatibility Tests....
     No ROM PCI IRQ routing table found!!!

     IRQ Summary: IRQs 9,10,11,14,15 are used by PCI devices
     Shared IRQs: There are no shared PCI IRQs

------------------

I hope this is helpful.  Please let us know how things go.

Marty

P.S. Wiki material?

--=20
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

Re: [Etherboot-users] could some one tell me how to find pci id in windows or dos

[<di...@ta...>]

On Wed, Jun 08, 2005 at 03:47:31PM +0530, abhi wrote:
> hi
> could some one tell me how to find pci id in windows or dos insted of 
> installing a full linux distro 'cause i do not have any disk space to 
> install it
> n then install lscpi

I don't know about Windows, but many BIOSes show them during boot.
You can also boot some live linux CD (e.g. knoppix) and use it without
installing.
-- 
Didi

[Etherboot-users] could some one tell me how to find pci id in windows or dos

[abhi <ab...@gm...>]

hi
could some one tell me how to find pci id in windows or dos insted of=20
installing a full linux distro 'cause i do not have any disk space to=20
install it
n then install lscpi

Re: [Etherboot-users] Re: etherboot pci wifi

[Michael B. <mb...@fe...>]

On Tue, 7 Jun 2005, Hermann Gausterer wrote:
> > Do you have a known working card that you could test with?
> 
> no, not with a prism 2.5 chip ... :-(
> but maybe i can get it work first with linux .. 
> which are the best drivers for this card? there are so
> many wlan driver packets out there ... and also lots of
> different firmwares too ... :-(

The Etherboot driver is based on the linux-wlan-ng driver.

> i guess that etherboot uses the firmware on the card; 
> maybe that is a problem too; this card is realy from the
> first generation of 802.11b

It uses the firmware only to the same extent as the Linux driver, so this 
shouldn't be a problem.

Michael

Re: [Etherboot-users] Re: etherboot pci wifi

[Hermann G. <eth...@mr...>]

On Tuesday 07 June 2005 18:15, you wrote:
> Do you have a known working card that you could test with?

no, not with a prism 2.5 chip ... :-(
but maybe i can get it work first with linux ..=20
which are the best drivers for this card? there are so
many wlan driver packets out there ... and also lots of
different firmwares too ... :-(

i guess that etherboot uses the firmware on the card;=20
maybe that is a problem too; this card is realy from the
first generation of 802.11b

i will also try to check with a wlan sniffer too; maybe
the cards produces more packets, but the accesspoint=20
ignores them (because of errors ....)

hermann

Re: [Etherboot-users] Re: etherboot pci wifi

[Michael B. <mb...@fe...>]

On Tue, 7 Jun 2005, Hermann Gausterer wrote:
> i tried with an old tekram tc-400 .... wow what an old card ;-)
> 
> i did a to stage loading:
> 
> 3comMBA -> prism2.pxe -> etherboot-prism boot
> 
> the accesspoint has all wep & accesslists and such turned off
> 
> all macs are "anomyzed" ;-)
> 
> output of etherboot:
> ------------------------------------------------
> Etherboot 5.4.0 (GPL) http://etherboot.org
> Drivers: Prism2_PCI   Images: NBI ELF PXE   Exports: PXE
> Protocols: DHCP TFTP
> Relocating _text from: [0007ec10,00090b80) to [07eee090,07f00000)
> Probing pci nic...
> [prism2_pci]Prism2.5 has registers at 0xd9112f70
> MAC address 00:02:DD:XX:XX:XX
> Attempting to autojoin to any available access point (attempt 1)...done
> Link not connected (status 0x0006)
> Attempting to autojoin to any available access point (attempt 2)...done
> Link connected (BSSID 00:80:C8:XX:XX:XX - MAC address 8F:00:00:XX:XX:XX)
> Searching for server (DHCP)...Tx exception occurred with fid 0x01ed
> hfa384x: Tx error occurred (status 0x0001):
>  ...retry error
>
> <snip>
>
> maybe my card is not working correctly, never get it to work
> with linux directly .. and the original M$ drivers are a P.I.T.A!! :-o

The driver is definitely communicating with the card, otherwise you'd 
never get a successful join to the access point.  Do you have a known 
working card that you could test with?

Michael