Mika Tiainen | 9 Feb 21:38 2016
Picon
Picon

[PATCH] [intel] Add INTEL_NO_PHY_RST for another I218-LM variant

Fixed booting on HP EliteBook 820 G2 laptop
---
 src/drivers/net/intel.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/drivers/net/intel.c b/src/drivers/net/intel.c
index cdfac15..dc06466 100644
--- a/src/drivers/net/intel.c
+++ b/src/drivers/net/intel.c
 <at>  <at>  -1065,7 +1065,7  <at>  <at>  static struct pci_device_id intel_nics[] = {
 	PCI_ROM ( 0x8086, 0x157b, "i210-2", "I210", 0 ),
 	PCI_ROM ( 0x8086, 0x15a0, "i218lm-2", "I218-LM", INTEL_NO_PHY_RST ),
 	PCI_ROM ( 0x8086, 0x15a1, "i218v-2", "I218-V", 0 ),
-	PCI_ROM ( 0x8086, 0x15a2, "i218lm-3", "I218-LM", 0 ),
+	PCI_ROM ( 0x8086, 0x15a2, "i218lm-3", "I218-LM", INTEL_NO_PHY_RST ),
 	PCI_ROM ( 0x8086, 0x15a3, "i218v-3", "I218-V", INTEL_NO_PHY_RST ),
 	PCI_ROM ( 0x8086, 0x294c, "82566dc-2", "82566DC-2", 0 ),
 	PCI_ROM ( 0x8086, 0x2e6e, "cemedia", "CE Media Processor", 0 ),
--

-- 
2.7.0

Sean m | 5 Feb 21:29 2016
Picon
Gravatar

DEBUG http

Hi all,

It seems like in newer versions of iPXE the DEBUG=http option during the make of undionly.kpxe does not do anything. Versions that were older than ipxe-15a8800 actually provided output when that option was set, but it seems like anything newer than that does not.

Is there something I'm missing?

-- 
Thanks,
Sean
<div><div dir="ltr">Hi all,<div><br></div>
<div>It seems like in newer versions of iPXE the DEBUG=http option during the make of undionly.kpxe does not do anything. Versions that were older than ipxe-15a8800 actually provided output when that option was set, but it seems like anything newer than that does not.</div>
<div><br></div>
<div>Is there something I'm missing?<br clear="all"><div><br></div>--&nbsp;
</div>
<div>Thanks,</div>
<div>Sean</div>
</div></div>
Christian Nilsson | 3 Feb 20:49 2016
Picon
Gravatar

Re: Request for Network support for HP Elitebook 745 G3 (Broadcom NetXtreme Gigabit Ethernet Plus)

On Wed, Feb 3, 2016 at 8:34 PM, Krizak, Paul <pkrizak <at> qualcomm.com> wrote:
> I am fairly certain I'm using the latest version:
>
> --- /usr2/pkrizak/git/ipxe
> [pkrizak <at> melchior]$ git remote -v show
> origin  git://git.ipxe.org/ipxe.git (fetch)
> origin  git://git.ipxe.org/ipxe.git (push)
>
> --- /usr2/pkrizak/git/ipxe
> [pkrizak <at> melchior]$ git pull
> Already up-to-date.
>
> --- /usr2/pkrizak/git/ipxe
> [pkrizak <at> melchior]$ git rev-parse HEAD
> d0bfd830e4e5ddd1015dda66833a99b068b6a519

Yes that's the latest one, goodie ;)

>
> If you're referring to the build number in some of the screenshots earlier in this thread -- you're right,
that was the older build.  We actually did build with the newer version and got the same results (but did not
post newer screencaps that show the newer build version).
>
>>> Why kkpxe?
>
> We have a standard infrastructure based on pxelinux, so we are chain-loading iPXE specifically for
Windows installs.  Linux and ESX installs go through our standard pxelinux stuff.  But it all has to live on
the same network, so pxelinux is the "primary" bootloader.
>
> I did not develop the ipxe setup for Windows -- it was handed to me in this state.  I don't know why we use kkpxe
versus other types of bootloaders, except for "that's how it was set up".  Is there a better way to get
HTTP-based image downloads to work without needing kkpxe?

Ok yes, use undionly.kpxe (single k) that should work for all nics
that are chained (unless The underlaying UNDI implementation is buggy)

Having pxelinux in the boot path is sometimes causing an issue so you
should try without it, for example by building the .usb version
instead and booting directly from a usb stick.

http://forum.ipxe.org/showthread.php?tid=6989
I'm guessing here, but kkpxe might actually be part of your issue.

>
> The key feature of ipxe that we're taking advantage of is its ability to use HTTP to retrieve a disk image,
rather than TFTP.  With Windows installs, we have to download a multi-hundred-MB image, which takes
FOREVER over TFTP. Over HTTP it is much faster and more reliable (since it uses TCP instead of UDP).
>
>>> I'm quite sure I have added that to a build myself.
>
> Maybe it's still sitting in a feature branch and needs to be merged to master?  It's definitely not in the
code at the master branch.

It was a one time build and was never sent upstream. (I'm just a iPXE
user like yourself)

>
> I edited tg3.c and added the PCI_ROM macro, then recompiled.  Same behavior as before.  And I
double-checked the build number, and it's the newest one (d0bf...)
>
>

What did you build? please try: make bin/14e41687.pxe DEBUG=tg3
Or if you chain from pxelinux you might want make bin/14e41687.lkrn
DEBUG=tg3 instead

undionly versions will never include specific nic versions, so it
won't make any difference.

> ----
> Paul Krizak              office: AF-250D
> Staff IT Engineer, UCM   desk: 858-651-2467
> Qualcomm, Inc            cell: 512-791-0686
>
>
> -----Original Message-----
> From: Christian Nilsson [mailto:nikize <at> gmail.com]
> Sent: Wednesday, February 03, 2016 11:07 AM
> To: Doose, Michael; Krizak, Paul
> Cc: ipxe-devel <at> lists.ipxe.org
> Subject: Re: [ipxe-devel] Request for Network support for HP Elitebook 745 G3 (Broadcom NetXtreme
Gigabit Ethernet Plus)
>
>  Hi,
> Sorry about 14e4-1687 not being included, let me return to that further down...
>
> On Tue, Feb 2, 2016 at 10:07 PM, Doose, Michael <mdoose <at> qualcomm.com> wrote:
>> Christian,
>>
>> Thanks so much for the response, I apologize for not better explaining our situation. I hope the
information below helps make things more clear. I work on the Windows side and have a Unix engineer helping
with the updates on the pxe/ipxe side.
>>
>> We are now using iPXE 1.0.0+ (8f01). I have reached out to have the unit folks check the niclist.pl for the
Broadcom NIC.
>
> That is very old!
> commit 8f0173b5c8ac6de9e9fa8115e37357c2aeb88101
> Date:   Mon Dec 9 15:32:42 2013 +0000
>
> Please use latest git master, cloning from
> https://git.ipxe.org/ipxe.git is recommended
>
>>
>> The error warning received was the following which referenced Legacy: "iPXE initializing
devices...WARNING: Using legacy NIC wrapper on 00:00:00:00:00:00"
>>
>> On all our other systems we see: "iPXE initializing devices...ok"
>>
>> We are using .kkpxe with WIMBOOT and BOOTMGR.EXE, no EFI stuff. We are also chain loading from SYSLINUX
PXE to iPXE
>
> Why kkpxe?, and what's your boot path/steps up to the above "Using
> legacy NIC wrapper" message?
> For example is it loaded from USB or is pxelinux involved somewhere etc.
> Are you using ipxe.* or undionly.*
> if you use undionly.kpxe (note not kkpxe) then ipxe will use the
> BIOS/Firmware drivers, you could in that case try to upgrade BIOS.
> if you use ipxe.pxe (don't use kpxe when using this variant) then it
> will only use ipxes native drivers, since none exist that won't work,
> but it shouldn't try to detect a non existing nic.
> Or build bin/14e41687.pxe (see below for info about adding support)
> Another alternative would be to test with .usb version on a USB stick:
> http://ipxe.org/download#using_a_boot_cd-rom_or_usb_key
>
>
>>
>> In BIOS we have configured legacy mode:
>> Configure Legacy Support and Secure boot : "Legacy Support Enable and Secure Boot Disable"
>>
>> -Mike
>
> Now about The missing 14e4-1687, I'm quite sure I have added that to a
> build myself.
> You could try to add it to tg3.c and see if it works
>
> PCI_ROM(0x14e4, 0x1687, "14e4-1687", "14e4-1687", 0),
> or patch at: http://ur1.ca/oh6r6
>
> If it does not work then build with debugging enabled and see if that
> gives anything:
> make bin/14e41687.pxe DEBUG=tg3
> This will enable the DBG statements in the tg3.c file
> for even more debug output use DEBUG=tg3,tg3_hw,tg3_phy
>
> If it works, it would be appriciated if you could run thru the
> testlist at http://ipxe.org/dev/driver
> If everything passes then we can add it to the main repo (it will
> probably be added if it works to boot with since it's better then
> nothing, but the more tested the better)
>
> /Christian
>
>
>>
>> -----Original Message-----
>> From: Christian Nilsson [mailto:nikize <at> gmail.com]
>> Sent: Tuesday, February 02, 2016 11:17 AM
>> To: Doose, Michael <mdoose <at> qualcomm.com>
>> Cc: ipxe-devel <at> lists.ipxe.org
>> Subject: Re: [ipxe-devel] Request for Network support for HP Elitebook 745 G3 (Broadcom NetXtreme
Gigabit Ethernet Plus)
>>
>> On Tue, Feb 2, 2016 at 7:48 PM, Doose, Michael <mdoose <at> qualcomm.com> wrote:
>>> Hey team,
>>>
>>> I pulled down the latest build this morning to try and add support for
>>> the new HP Elitebook 745 G3 (AMD) based notebook, but it is still
>>> defaulting to the Legacy and failing with all zeroes as the Mac Address.
>>>
>>> This unit runs a “Broadcom NetXtreme Gigabit Ethernet Plus” LAN
>>> Adapter. Is there anything you can suggest to try and add support for this unit?
>>>
>>> Thank you!
>>>
>>> Misc Hardware Info:
>>>
>>> Hardware IDs:
>>> PCI\VEN_14E4&DEV_1687
>>
>> Hi,
>>
>> The 14e4-1687 have native supported in ipxe and should work, the first thing to check in cases like this is
the niclist that can be generated by niclist.pl in the util directory.
>>
>> What do you mean by Legacy? Assuming you are using the latest git master, what are your build command and
which ipxe file are you using?
>> legacy might mean undionly.kpxe which do not have any native drivers in it. you need ipxe.pxe or ipxe.efi
depending on platform, you could also build 14e41687.pxe/.efi to only support the specific nic.
>>
>> Your issues might also be related to buggy HP firmware:
>> http://lists.ipxe.org/pipermail/ipxe-devel/2015-November/004476.html
>>
>> Hope it helps, otherwise you can follow some of the steps described in the above email thread and see if
that gets you any further.
>>
>> /Christian
_______________________________________________
ipxe-devel mailing list
ipxe-devel <at> lists.ipxe.org
https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
Tellenbach Daniel | 3 Feb 15:43 2016
Picon

Problem with DHCP

Hi
I’am using ipxe to boot my old PC-Hardware via USB-Stick. The reason why I need the USB stick is that the old PC does not support pxe boot via Network. So I have setup a TFTP server holding a pxelinux.0 binary. But my problem starts when I use the dhcp command to get the ip address. As soon as I call the DHCP command, the PC hangs an I have to manually restart it. Here the output of the dmidecode command of my Hardware.
 
Here the script I am using
 
#!ipxe
 
# Get ip address
dhcp
 
# Override dhcp settings
echo Override current dhcp settings next-server=${next-server} and filename=${filename}
set next-server 192.168.201.24
set filename pxelinux.0
 
# Boot
echo Booting ${filename} on server ${next-server}
chain tftp://${next-server}/${filename}
 
I also compiled the latest  version of pxe.
 
 
Any idea what is the problem? Please let me know if you need more information.
 
Thanks in advanced
Dani
 
P.S The pxe boot in general is working because on newer Hardware it works.
 
Daniel Tellenbach
Senior Solution Architect
 
Wincor Nixdorf AG
Stationsstrasse 5
8306 Brüttisellen, Switzerland
 
Office: +41 44 835 34 69
Mobile: +41 79 233 42 69
daniel.tellenbach <at> wincor-nixdorf.ch
 
 
 
# dmidecode 2.12
SMBIOS 2.2 present.
34 structures occupying 870 bytes.
Table at 0x000F0800.

Handle 0x0000, DMI type 0, 19 bytes
BIOS Information
	Vendor: Phoenix Technologies, LTD
	Version: 6.00 PG
	Release Date: 12/19/2012
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 512 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		AGP is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
	Manufacturer:  
	Product Name:  
	Version:  
	Serial Number:  
	UUID: Not Present
	Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer:  
	Product Name: i845-C8736XP
	Version:  
	Serial Number:  

Handle 0x0003, DMI type 3, 13 bytes
Chassis Information
	Manufacturer:  
	Type: Desktop
	Lock: Not Present
	Version:  
	Serial Number:  
	Asset Tag:  
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown

Handle 0x0004, DMI type 4, 32 bytes
Processor Information
	Socket Designation: Socket 478
	Type: Central Processor
	Family: Pentium 4
	Manufacturer: Intel
	ID: 29 0F 00 00 FF FB EB BF
	Signature: Type 0, Family 15, Model 2, Stepping 9
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Pentium(R) 4 CPU
	Voltage: 0.0 V
	External Clock: 100 MHz
	Max Speed: 3066 MHz
	Current Speed: 2000 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x0008
	L2 Cache Handle: 0x0009
	L3 Cache Handle: No L3 Cache

Handle 0x0005, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: 8-bit Parity
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 1024 MB
	Maximum Total Memory Size: 2048 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		Other
	Memory Module Voltage: 5.0 V
	Associated Memory Slots: 2
		0x0006
		0x0007
	Enabled Error Correcting Capabilities:
		None

Handle 0x0006, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A0
	Bank Connections: 0 1
	Current Speed: Unknown
	Type: Other
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A1
	Bank Connections: 2 3
	Current Speed: Unknown
	Type: Other
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0008, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 20 kB
	Maximum Size: 20 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0009, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 512 kB
	Maximum Size: 512 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PRIMARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: SECONDARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: FDD
	Internal Connector Type: On Board Floppy
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: 8251 FIFO Compatible

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM1
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM2
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: LPT1
	Internal Connector Type: DB-25 female
	External Reference Designator:  
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Keyboard
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Keyboard Port

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PS/2 Mouse
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Mouse Port

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB0
	External Connector Type: Other
	Port Type: USB

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB1
	External Connector Type: Other
	Port Type: USB

Handle 0x0014, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI0
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 1
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0015, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 2
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0016, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI2
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 3
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0017, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI3
	Type: 32-bit PCI
	Current Usage: In Use
	Length: Long
	ID: 4
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0018, DMI type 9, 13 bytes
System Slot Information
	Designation: AGP
	Type: 32-bit AGP
	Current Usage: Available
	Length: Long
	ID: 8
	Characteristics:
		5.0 V is provided

Handle 0x0019, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 3
		n|US|iso8859-1
		n|US|iso8859-1
		r|CA|iso8859-1
	Currently Installed Language: n|US|iso8859-1

Handle 0x001A, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 2 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x001B, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A0
	Bank Locator: Bank0/1
	Type: SDRAM
	Type Detail: Synchronous

Handle 0x001C, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A1
	Bank Locator: Bank2/3
	Type: SDRAM
	Type Detail: Synchronous

Handle 0x001D, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Array Handle: 0x001A
	Partition Width: 1

Handle 0x001E, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x001B
	Memory Array Mapped Address Handle: 0x001D
	Partition Row Position: 1

Handle 0x001F, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00040000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x001C
	Memory Array Mapped Address Handle: 0x001D
	Partition Row Position: 1

Handle 0x0020, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0021, DMI type 127, 4 bytes
End Of Table

Attachment (ipxe.iso): application/octet-stream, 1383 KiB
# dmidecode 2.12
SMBIOS 2.2 present.
34 structures occupying 870 bytes.
Table at 0x000F0800.

Handle 0x0000, DMI type 0, 19 bytes
BIOS Information
	Vendor: Phoenix Technologies, LTD
	Version: 6.00 PG
	Release Date: 12/19/2012
	Address: 0xE0000
	Runtime Size: 128 kB
	ROM Size: 512 kB
	Characteristics:
		ISA is supported
		PCI is supported
		PNP is supported
		APM is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		ESCD support is available
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		5.25"/360 kB floppy services are supported (int 13h)
		5.25"/1.2 MB floppy services are supported (int 13h)
		3.5"/720 kB floppy services are supported (int 13h)
		3.5"/2.88 MB floppy services are supported (int 13h)
		Print screen service is supported (int 5h)
		8042 keyboard services are supported (int 9h)
		Serial services are supported (int 14h)
		Printer services are supported (int 17h)
		CGA/mono video services are supported (int 10h)
		ACPI is supported
		USB legacy is supported
		AGP is supported

Handle 0x0001, DMI type 1, 25 bytes
System Information
	Manufacturer:  
	Product Name:  
	Version:  
	Serial Number:  
	UUID: Not Present
	Wake-up Type: Power Switch

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
	Manufacturer:  
	Product Name: i845-C8736XP
	Version:  
	Serial Number:  

Handle 0x0003, DMI type 3, 13 bytes
Chassis Information
	Manufacturer:  
	Type: Desktop
	Lock: Not Present
	Version:  
	Serial Number:  
	Asset Tag:  
	Boot-up State: Unknown
	Power Supply State: Unknown
	Thermal State: Unknown
	Security Status: Unknown

Handle 0x0004, DMI type 4, 32 bytes
Processor Information
	Socket Designation: Socket 478
	Type: Central Processor
	Family: Pentium 4
	Manufacturer: Intel
	ID: 29 0F 00 00 FF FB EB BF
	Signature: Type 0, Family 15, Model 2, Stepping 9
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: Intel(R) Pentium(R) 4 CPU
	Voltage: 0.0 V
	External Clock: 100 MHz
	Max Speed: 3066 MHz
	Current Speed: 2000 MHz
	Status: Populated, Enabled
	Upgrade: ZIF Socket
	L1 Cache Handle: 0x0008
	L2 Cache Handle: 0x0009
	L3 Cache Handle: No L3 Cache

Handle 0x0005, DMI type 5, 20 bytes
Memory Controller Information
	Error Detecting Method: 8-bit Parity
	Error Correcting Capabilities:
		None
	Supported Interleave: One-way Interleave
	Current Interleave: One-way Interleave
	Maximum Memory Module Size: 1024 MB
	Maximum Total Memory Size: 2048 MB
	Supported Speeds:
		Other
	Supported Memory Types:
		Other
	Memory Module Voltage: 5.0 V
	Associated Memory Slots: 2
		0x0006
		0x0007
	Enabled Error Correcting Capabilities:
		None

Handle 0x0006, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A0
	Bank Connections: 0 1
	Current Speed: Unknown
	Type: Other
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0007, DMI type 6, 12 bytes
Memory Module Information
	Socket Designation: A1
	Bank Connections: 2 3
	Current Speed: Unknown
	Type: Other
	Installed Size: 1024 MB (Double-bank Connection)
	Enabled Size: 1024 MB (Double-bank Connection)
	Error Status: OK

Handle 0x0008, DMI type 7, 19 bytes
Cache Information
	Socket Designation: Internal Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 20 kB
	Maximum Size: 20 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x0009, DMI type 7, 19 bytes
Cache Information
	Socket Designation: External Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: External
	Installed Size: 512 kB
	Maximum Size: 512 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Unknown
	System Type: Unknown
	Associativity: Unknown

Handle 0x000A, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PRIMARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000B, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: SECONDARY IDE
	Internal Connector Type: On Board IDE
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: Other

Handle 0x000C, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: FDD
	Internal Connector Type: On Board Floppy
	External Reference Designator: Not Specified
	External Connector Type: None
	Port Type: 8251 FIFO Compatible

Handle 0x000D, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM1
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x000E, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: COM2
	Internal Connector Type: 9 Pin Dual Inline (pin 10 cut)
	External Reference Designator:  
	External Connector Type: DB-9 male
	Port Type: Serial Port 16450 Compatible

Handle 0x000F, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: LPT1
	Internal Connector Type: DB-25 female
	External Reference Designator:  
	External Connector Type: DB-25 female
	Port Type: Parallel Port ECP/EPP

Handle 0x0010, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Keyboard
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Keyboard Port

Handle 0x0011, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: PS/2 Mouse
	Internal Connector Type: PS/2
	External Reference Designator:  
	External Connector Type: PS/2
	Port Type: Mouse Port

Handle 0x0012, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB0
	External Connector Type: Other
	Port Type: USB

Handle 0x0013, DMI type 8, 9 bytes
Port Connector Information
	Internal Reference Designator: Not Specified
	Internal Connector Type: None
	External Reference Designator: USB1
	External Connector Type: Other
	Port Type: USB

Handle 0x0014, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI0
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 1
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0015, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI1
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 2
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0016, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI2
	Type: 32-bit PCI
	Current Usage: Available
	Length: Long
	ID: 3
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0017, DMI type 9, 13 bytes
System Slot Information
	Designation: PCI3
	Type: 32-bit PCI
	Current Usage: In Use
	Length: Long
	ID: 4
	Characteristics:
		5.0 V is provided
		PME signal is supported

Handle 0x0018, DMI type 9, 13 bytes
System Slot Information
	Designation: AGP
	Type: 32-bit AGP
	Current Usage: Available
	Length: Long
	ID: 8
	Characteristics:
		5.0 V is provided

Handle 0x0019, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 3
		n|US|iso8859-1
		n|US|iso8859-1
		r|CA|iso8859-1
	Currently Installed Language: n|US|iso8859-1

Handle 0x001A, DMI type 16, 15 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 2 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x001B, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A0
	Bank Locator: Bank0/1
	Type: SDRAM
	Type Detail: Synchronous

Handle 0x001C, DMI type 17, 21 bytes
Memory Device
	Array Handle: 0x001A
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 1024 MB
	Form Factor: DIMM
	Set: None
	Locator: A1
	Bank Locator: Bank2/3
	Type: SDRAM
	Type Detail: Synchronous

Handle 0x001D, DMI type 19, 15 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 2 GB
	Physical Array Handle: 0x001A
	Partition Width: 1

Handle 0x001E, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x0003FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x001B
	Memory Array Mapped Address Handle: 0x001D
	Partition Row Position: 1

Handle 0x001F, DMI type 20, 19 bytes
Memory Device Mapped Address
	Starting Address: 0x00040000000
	Ending Address: 0x0007FFFFFFF
	Range Size: 1 GB
	Physical Device Handle: 0x001C
	Memory Array Mapped Address Handle: 0x001D
	Partition Row Position: 1

Handle 0x0020, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0021, DMI type 127, 4 bytes
End Of Table

Thomas Bächler | 3 Feb 20:12 2016

[RFC 0/3] Implement IPv6 source address selection


When I tried using ipxe with IPv6, I realized that I was unable to reach any hosts
outside my own network. The reason was that ipxe used my ULA address instead of my
globally routable address. This patchset implements ipv6 source address selection
according to RFC 6724.
Capriccio, Peter | 3 Feb 09:49 2016

Best practices for troubleshooting UEFI General Protection Exceptions when booting iPXE?

I was recently working on a ProLiant DL380 Gen9 system (which, unfortunately, I no longer have access to)
where booting an iPXE "snponly.efi" image from a certain interface would fail with a General Protection Exception.

This system had the onboard 1Gb Ethernet, 4-port "331i" adapter (Broadcom-based), plus an add-on
InfiniBand QDR/Ethernet 10Gb 2-port "544+FLR-QSFP" adapter (Mellanox ConnectX-3 Pro-based) running
in 10Gb Ethernet mode. The system was running in its UEFI mode (it also supports running in a Legacy BIOS
mode). I was able to boot iPXE successfully from the 331i adapter but not from the 544+FLR-QSFP adapter --
the latter throwing the exception. However, I was able to boot to elilo 3.16 and SYSLINUX 6.03 (EFI) from
the 544+FLR-QSFP adapter.

I was using iPXE build "d0bfd83" from:

  https://git.ipxe.org/ipxe.git/snapshot/d0bfd830e4e5ddd1015dda66833a99b068b6a519.tar.gz

- made no config file changes

- built using:

  # make bin-x86_64-efi/snponly.efi EMBED=/root/foo.ipxe

- where "/root/foo.ipxe" contained only:

  #!ipxe
  dhcp
  shell

Here is what the console output looked like (with a lot of blank lines removed) when booting from the
544+FLR-QSFP adapter:

>> Booting Embedded FlexibleLOM 1 Port 1 : HP InfiniBand QDR/Ethernet 10Gb 2-port 544+FLR-QSFP Adapter -
NIC (PXE IPv4)

>> Booting PXE over IPv4.
  Station IP address is 10.7.161.131

  Server IP address is 10.7.170.254
  NBP filename is snponly.efi
  NBP filesize is 147616 Bytes
Downloading NBP file...

  NBP file downloaded successfully.
iPXE initialising devices...

X64 Exception Type 0D - General Protection Exception

RCX=000000007744D978 DX=0000000070DFE000 R8=0000000000500000 R9=0000000000000000
RSP=000000006BA23108 BP=000000006BA2D971 AX=0000000000000038 BX=000000007744D978
R10=0000000000000000 11=000000006BA23130 12=000000000000001A 13=000000006BA233B0
R14=0000000000000000 15=0000000000000006 SI=0000000000000001 DI=000000006BA232D0
CR2=0000000000000000 CR3=000000006B983000 CR0=80000013 CR4=00000668 CR8=00000000
CS=0038 DS=0038 SS=0030 ES=0038 RFLAGS=00010203 MSR1D9=4801 345=32C4 1C9=000F

LBRs From      To       From      To       From      To       From      To
01h  00093009->74407191 78464454->0005E11A 7846443A->78464454 78466365->78464432
05h  74407BEB->78466340 0005E11A->74407BE0 778F2F27->00000000 778F1F89->778F2ED7
09h  778F0B34->778F1EEF 778F0A94->778F0AAF 778F0A61->778F0A7C 778F0A37->778F0A52
0Dh  778F1B08->778F09FA 778F1ACC->778F1AF5 778F1AA8->778F1AC0 7440719C->78466340
Null Caller: ImageBase=00000000778EB000 CALL ImageBase        ImageName+Offset
00h  0000000000000000 No Image Information

CALL ImageBase        ImageName+Offset

STACK   00h      04h      08h      0Ch      10h      14h      18h      1Ch
RSP+00h 778F2F2A 00000004 6BA3A81C 000025EE 779059D1 778F1F8B 712FDFFF 72372398
RSP+20h 00000001 72371018 72372398 778F0B36 00000008 72371018 6BA23306 778F1B0B
RSP+40h 71487068 6BA2B776 71487018 6BA232B0 778F18FA 70DFD000 6BA232B0 6BA232B0
RSP+60h 77445439 00000000 6BA2B7D4 6BA23306 C0000000 7744D978 7744554C 00009CC0
RSP+80h 000070DF 00000000 7744D978 77445D88 7744D788 72372398 00000002 72372398
RSP+A0h 6BA233B0 71487538 72F72CA8 774453AD 00000000 00400100 7744D978 72372398
RSP+C0h 00000002 7744D688 7744C3D8 7744C438 77441C64 72372398 7744D6D8 00000002
RSP+E0h 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Just something to note (not sure if it matters), the 544+FLR-QSFP adapter has its own iPXE stack in its
firmware, although I only see output from it when the system is in Legacy BIOS mode.

Now, if you've made it this far :), my questions are these:

- What is the best method, in general terms, for troubleshooting a problem such as this?

- What debug flags (or breakpoints maybe?) would produce the most fruitful data?

- What other information needs to be gathered?

Sorry for the noob questions, but as a non-developer, there is not a lot for me to go on when running into these
kinds of problems, so the next time I come across this, I want to be better prepared.

Thanks for any feedback,

Pete C. (employed by, but not speaking for, HPE Financial Services)

Doose, Michael | 2 Feb 19:48 2016

Request for Network support for HP Elitebook 745 G3 (Broadcom NetXtreme Gigabit Ethernet Plus)

Hey team,

 

I pulled down the latest build this morning to try and add support for the new HP Elitebook 745 G3 (AMD) based notebook, but it is still defaulting to the Legacy and failing with all zeroes as the Mac Address.

 

This unit runs a “Broadcom NetXtreme Gigabit Ethernet Plus” LAN Adapter. Is there anything you can suggest to try and add support for this unit?

 

Thank you!

 

 

Misc Hardware Info:

 

Hardware IDs:

 

PCI\VEN_14E4&DEV_1687&SUBSYS_807E103C&REV_10

PCI\VEN_14E4&DEV_1687&SUBSYS_807E103C

PCI\VEN_14E4&DEV_1687&CC_020000

PCI\VEN_14E4&DEV_1687&CC_0200

 

Compatible IDs:

 

PCI\VEN_14E4&DEV_1687&REV_10

PCI\VEN_14E4&DEV_1687

PCI\VEN_14E4&CC_020000

PCI\VEN_14E4&CC_0200

PCI\VEN_14E4

PCI\CC_020000&DT_0

PCI\CC_020000

PCI\CC_0200&DT_0

PCI\CC_0200

 

Service: b57nd60a

 

Device Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}

Driver Key: {4d36e972-e325-11ce-bfc1-08002be10318}\0007

 

Physical Device Object Name: \Device\NTPNP_PCI0023

 

 

Driver Location:

http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=7815280&swItemId=ob_154953_1&swEnvOid=4060

 

 

-Mike

 

<div>
<div class="WordSection1">
<p class="MsoNormal">Hey team,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I pulled down the latest build this morning to try and add support for the new HP Elitebook 745 G3 (AMD) based notebook, but it is still defaulting to the Legacy and failing with all zeroes as the Mac Address.
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">This unit runs a &ldquo;Broadcom NetXtreme Gigabit Ethernet Plus&rdquo; LAN Adapter. Is there anything you can suggest to try and add support for this unit?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thank you!<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Misc Hardware Info:<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Hardware IDs:<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;DEV_1687&amp;SUBSYS_807E103C&amp;REV_10<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;DEV_1687&amp;SUBSYS_807E103C<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;DEV_1687&amp;CC_020000<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;DEV_1687&amp;CC_0200<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Compatible IDs:<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;DEV_1687&amp;REV_10<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;DEV_1687<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;CC_020000<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4&amp;CC_0200<p></p></p>
<p class="MsoNormal">PCI\VEN_14E4<p></p></p>
<p class="MsoNormal">PCI\CC_020000&amp;DT_0<p></p></p>
<p class="MsoNormal">PCI\CC_020000<p></p></p>
<p class="MsoNormal">PCI\CC_0200&amp;DT_0<p></p></p>
<p class="MsoNormal">PCI\CC_0200<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Service: b57nd60a<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Device Class GUID: {4d36e972-e325-11ce-bfc1-08002be10318}<p></p></p>
<p class="MsoNormal">Driver Key: {4d36e972-e325-11ce-bfc1-08002be10318}\0007<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Physical Device Object Name: \Device\NTPNP_PCI0023<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Driver Location:<p></p></p>
<p class="MsoNormal"><a href="http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=7815280&amp;swItemId=ob_154953_1&amp;swEnvOid=4060">http://h20564.www2.hp.com/hpsc/swd/public/detail?sp4ts.oid=7815280&amp;swItemId=ob_154953_1&amp;swEnvOid=4060</a><p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">-Mike<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
perlsite | 30 Jan 23:14 2016
Picon

Bug report: missing or invalid displacement expression `private_key_len <at> GOTOFF'

Hello,
I'm trying to build the following:

git clone git://git.ipxe.org/ipxe.git
$ cd ipxe/src

make

And I get the following error:
...
...
  [BUILD] bin/privkey.o

/tmp/cc89fEkd.s: Assembler messages:

/tmp/cc89fEkd.s:36: Error: missing or invalid displacement expression `private_key_len <at> GOTOFF'

Makefile.housekeeping:850: recipe for target 'bin/privkey.o' failed

make: *** [bin/privkey.o] Error 1

My build env is:

nasm -v

NASM version 2.11.08 compiled on Mar 24 2015


gcc -v

Using built-in specs.

COLLECT_GCC=/usr/bin/gcc

COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/lto-wrapper

Target: x86_64-unknown-linux-gnu

Configured with: /build/gcc-multilib/src/gcc-5.3.0/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release

Thread model: posix

gcc version 5.3.0 (GCC)

make -v

GNU Make 4.1

Built for x86_64-unknown-linux-gnu


$ uname -a

Linux stoffle 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux

I'm running Arch Linux, so all the tools are the latest versions of respective tools.

Let me know if need more information!

Regards,
Julian



-------------------------------------
P.S. Може да стартираш собствен онлайн магазин с Shopiko от СуперХостинг.БГ. СуперЛесно е, а и има безплатен тестов период!
<div>
<p valid="true">Hello,<br>I'm trying to build the following:<br><br>$&nbsp;<span valid="true">git clone git://git.ipxe.org/ipxe.git</span><br>$ <span valid="true">cd&nbsp;ipxe/src</span></p>
<p valid="true">$&nbsp;<span valid="true">make</span></p>
<p valid="true">And I get the following error:<br>...<br>...<br>&nbsp; [BUILD] bin/privkey.o</p>
<p valid="true">/tmp/cc89fEkd.s: Assembler messages:</p>
<p valid="true">/tmp/cc89fEkd.s:36: Error: missing or invalid displacement expression `private_key_len <at> GOTOFF'</p>
<p valid="true">Makefile.housekeeping:850: recipe for target 'bin/privkey.o' failed</p>
<p valid="true">make: *** [bin/privkey.o] Error 1<br><br></p>
<p valid="true"><span valid="true">My build env is:</span><br><br></p>
<p valid="true">$&nbsp;<span valid="true">nasm -v</span></p>
<p valid="true">NASM version 2.11.08 compiled on Mar 24 2015<br><br><br></p>
<p valid="true">$&nbsp;<span valid="true">gcc -v</span></p>
<p valid="true">Using built-in specs.</p>
<p valid="true">COLLECT_GCC=/usr/bin/gcc</p>
<p valid="true">COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/lto-wrapper</p>
<p valid="true">Target: x86_64-unknown-linux-gnu</p>
<p valid="true">Configured with: /build/gcc-multilib/src/gcc-5.3.0/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release</p>
<p valid="true">Thread model: posix</p>
<p valid="true"></p>
<p valid="true">gcc version 5.3.0 (GCC)<br><br></p>
<p valid="true">$&nbsp;<span valid="true">make -v</span></p>
<p valid="true">GNU Make 4.1</p>
<p valid="true">Built for x86_64-unknown-linux-gnu</p>
<p valid="true"><br>$ <span valid="true">uname -a</span></p>
<p valid="true">Linux stoffle 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux<br><br>I'm running Arch Linux, so all the tools are the latest versions of respective tools.<br><br>Let me know if need more information!<br><br>Regards,<br>Julian</p>
<br><br>-------------------------------------<br><a href="http://ads.mail.bg/delivery/ck.php?oaparams=2__bannerid=4129__zoneid=35__OXLCA=1__cb=9e84404517__oadest=https%3A%2F%2Fwww.superhosting.bg%2Fweb-hosting-compare-shop-plans.php%3Futm_source%3DFooter1%26utm_medium%3Dt1%26utm_campaign%3DShopiko16-MailBG" target="_blank">
P.S. &#1052;&#1086;&#1078;&#1077; &#1076;&#1072; &#1089;&#1090;&#1072;&#1088;&#1090;&#1080;&#1088;&#1072;&#1096; &#1089;&#1086;&#1073;&#1089;&#1090;&#1074;&#1077;&#1085; &#1086;&#1085;&#1083;&#1072;&#1081;&#1085; &#1084;&#1072;&#1075;&#1072;&#1079;&#1080;&#1085; &#1089; Shopiko &#1086;&#1090; &#1057;&#1091;&#1087;&#1077;&#1088;&#1061;&#1086;&#1089;&#1090;&#1080;&#1085;&#1075;.&#1041;&#1043;. &#1057;&#1091;&#1087;&#1077;&#1088;&#1051;&#1077;&#1089;&#1085;&#1086; &#1077;, &#1072; &#1080; &#1080;&#1084;&#1072; &#1073;&#1077;&#1079;&#1087;&#1083;&#1072;&#1090;&#1077;&#1085; &#1090;&#1077;&#1089;&#1090;&#1086;&#1074; &#1087;&#1077;&#1088;&#1080;&#1086;&#1076;!<br></a>
</div>
Никита Илюшкин | 26 Jan 17:36 2016
Picon

Extracting ipxe script from compiled image

Hello list,

As I can found in the web:
http://ipxe-devel.ipxe.narkive.com/Lg8lM179/re-extract-ipxe-script-from-image-possible

year ago this script extracting can be done "not easily". Is it some 
progress in that direction? And could you please describe how "Not 
easily" way can be performed? This can be very helpful in situation of 
source code loss or in case of supporting somebody else's code (like mine).

Thank you.

--
Nikita Ilyushkin
김병욱 | 25 Jan 04:15 2016

ipxe wasn't compiled.

Hello ipxe developer or contributors.

I can compile pxe-boot to use usb. but it wasn't run. 

My notebook(real machine) is rebooted infinite.

I still don't understand, why wasn't run.

 

[build machine information]

$ uname -a

Linux bw-VirtualBox 4.2.0-25-generic #30-Ubuntu SMP Mon Jan 18 12:31:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

 

$ ll /dev/disk/by-id/

Totals 0

drwxr-xr-x 2 root root 200  1월 25 12:02 ./

drwxr-xr-x 5 root root 100  1월 25 12:02 ../

lrwxrwxrwx 1 root root   9  1월 25 10:27 ata-VBOX_CD-ROM_VB2-01700376 -> ../../sr0

lrwxrwxrwx 1 root root   9  1월 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf -> ../../sda

lrwxrwxrwx 1 root root  10  1월 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf-part1 -> ../../sda1

lrwxrwxrwx 1 root root  10  1월 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf-part2 -> ../../sda2

lrwxrwxrwx 1 root root  10  1월 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf-part5 -> ../../sda5

lrwxrwxrwx 1 root root   9  1월 25 12:02 usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0 -> ../../sdb

lrwxrwxrwx 1 root root  10  1월 25 12:02 usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0-part3 -> ../../sdb3

lrwxrwxrwx 1 root root  10  1월 25 12:02 usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0-part4 -> ../../sdb4


$ git clone http://github.com/ipxe/ipxe ipxe-src
$ cd ipxe-src/src
$ make
$ make bin/ipxe.usb
$ sudo dd if=bin/ipxe.usb of=/dev/disk/by-id/usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0
$ qemu-system-i386 /dev/sdb -boot n <--- success

[target machine information]

$ lscpi -s 02:00.0 -nnn 

Network Controller [0200] : Qualcomm Atheros AR92856 Wireless Network Adapter (PCI-Express) [168C:002B] (rev 01)

 

Why wasn't it booted in real machine?

 

Regards,

ByeoungWook.

<div>
<div>
<p>Hello&nbsp;ipxe&nbsp;developer or&nbsp;contributors.</p>
<p>I can compile pxe-boot to use usb. but it wasn't run.&nbsp;</p>
<p>My notebook(real machine) is rebooted infinite.</p>
<p>I still don't understand, why wasn't run.</p>
<p>&nbsp;</p>
<p>[build machine information]</p>
<p>$ uname -a</p>
<p>Linux bw-VirtualBox 4.2.0-25-generic #30-Ubuntu SMP Mon Jan 18 12:31:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux</p>
<p><span>&nbsp;</span></p>
<p>$ ll /dev/disk/by-id/</p>
<p>Totals 0</p>
<p>drwxr-xr-x 2 root root 200 &nbsp;1&#50900; 25 12:02 ./</p>
<p>drwxr-xr-x 5 root root 100 &nbsp;1&#50900; 25 12:02 ../</p>
<p>lrwxrwxrwx 1 root root &nbsp; 9 &nbsp;1&#50900; 25 10:27 ata-VBOX_CD-ROM_VB2-01700376 -&gt; ../../sr0</p>
<p>lrwxrwxrwx 1 root root &nbsp; 9 &nbsp;1&#50900; 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf -&gt; ../../sda</p>
<p>lrwxrwxrwx 1 root root &nbsp;10 &nbsp;1&#50900; 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf-part1 -&gt; ../../sda1</p>
<p>lrwxrwxrwx 1 root root &nbsp;10 &nbsp;1&#50900; 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf-part2 -&gt; ../../sda2</p>
<p>lrwxrwxrwx 1 root root &nbsp;10 &nbsp;1&#50900; 25 10:27 ata-VBOX_HARDDISK_VB444533e4-25a6cacf-part5 -&gt; ../../sda5</p>
<p>lrwxrwxrwx 1 root root &nbsp; 9 &nbsp;1&#50900; 25 12:02 usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0 -&gt; ../../sdb</p>
<p>lrwxrwxrwx 1 root root &nbsp;10 &nbsp;1&#50900; 25 12:02 usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0-part3 -&gt; ../../sdb3</p>
<p>lrwxrwxrwx 1 root root &nbsp;10 &nbsp;1&#50900; 25 12:02 usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0-part4 -&gt; ../../sdb4</p>
<div><br></div>
<div>$ git clone <a href="http://github.com/ipxe/ipxe">http://github.com/ipxe/ipxe</a> ipxe-src</div>
<div>$ cd ipxe-src/src</div>
<div>$ make</div>
<div>$ make bin/ipxe.usb</div>
<div>$ sudo dd if=bin/ipxe.usb of=/dev/disk/by-id/<span>usb-Sandisk_USB_Ultra_VC0482150712210757000233-0:0</span>
</div>
<div><span>$ qemu-system-i386 /dev/sdb -boot n<span> &lt;--- success</span></span></div>
<div><br></div>
<p><span>[target machine information]</span></p>
<p><span>$ lscpi -s 02:00.0 -nnn</span>&nbsp;</p>
<p>Network Controller [0200] : Qualcomm Atheros AR92856 Wireless Network Adapter (PCI-Express) [168C:002B] (rev 01)</p>
<p>&nbsp;</p>
<p>Why wasn't it booted in real machine?</p>
<p>&nbsp;</p>
<p>Regards,</p>
<p>ByeoungWook.</p>
</div>
<table><tr><td></td></tr></table>
</div>
Ben Hildred | 27 Jan 17:05 2016
Picon

bug report: 3c900b-fl freezes

I have been going through a stack of ethernet cards  getting them ready to be setup for iPXE boot, collecting pci ids and mac addresses, checking basic functionality, and making a list of eproms to order and I hit a snag when a 3c900b-fl is present and a driver for it is compiled into iPXE the system freezes. I believe the problem is the connector type forcing,as this is a 10 base fiber card and does not have other connectors. serial capture follows. mac addresses have been removed.

iPXE initialising devices...no connectors!warning: strange connector type in EEPROM.
selected utp. (forced)
WARNING: Using legacy NIC wrapper on xxxxxxxx
ok


iPXE 1.0.0+ (e55ec8) -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI NFS TFTP SRP AoE ELF MBOOT PXE bzImage COMBOOT Menu PXEXT

net0: xxxxxxxxx using 3c900b-fl on PCI00:08.0 (open)
  [Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 xxxxxxxxx)...

--
--
Ben Hildred
Automation Support Services
303 815 6721
<div><div dir="ltr">I have been going through a stack of ethernet cards &nbsp;getting them ready to be setup for iPXE boot, collecting pci ids and mac addresses, checking basic functionality, and making a list of eproms to order and I hit a snag when a 3c900b-fl is present and a driver for it is compiled into iPXE the system freezes. I believe the problem is the connector type forcing,as this is a 10 base fiber card and does not have other connectors. serial capture follows. mac addresses have been removed.<div><br></div>
<div>
<div>iPXE initialising devices...no connectors!warning: strange connector type in EEPROM.</div>
<div>selected utp. (forced)</div>
<div>WARNING: Using legacy NIC wrapper on xxxxxxxx</div>
<div>ok</div>
<div><br></div>
<div><br></div>
<div>iPXE 1.0.0+ (e55ec8) -- Open Source Network Boot Firmware -- <a href="http://ipxe.org">http://ipxe.org</a>
</div>
<div>Features: DNS HTTP iSCSI NFS TFTP SRP AoE ELF MBOOT PXE bzImage COMBOOT Menu PXEXT</div>
<div><br></div>
<div>net0: xxxxxxxxx using 3c900b-fl on PCI00:08.0 (open)</div>
<div>&nbsp; [Link:up, TX:0 TXE:0 RX:0 RXE:0]</div>
<div>Configuring (net0 xxxxxxxxx)...</div>
<div><br></div>-- <br><div class="gmail_signature">
<div>--</div>
<div>
<div>Ben Hildred</div>
<div>Automation Support Services</div>
</div>
<div>303 815 6721</div>
</div>
</div>
</div></div>

Gmane