Hi,
Now that I have recover my gpxe script thanks to Josh, I can test the
latest version of GPXE...
My test environment is like that:
* Virtualbox 3.2.6 with ethernet adapter PCNET-Fast III (Am79C973)
* First PXE boot to a classical PXE server
* Then load a GPXE lkrn image made at the
On 28 July 2010 12:22, Gilles Martin gilles.mar...@psi.ch wrote:
Hi,
Now that I have recover my gpxe script thanks to Josh, I can test the
latest version of GPXE...
My test environment is like that:
* Virtualbox 3.2.6 with ethernet adapter PCNET-Fast III (Am79C973)
* First PXE boot to a
Hi,
Here is the result:
Found pcnet32, vendor = 0x1022, device = 0x2000
Setting driver operations failed
gPXE 1.0.1 -- Open Source Boot Firmware -- http://etherboot.org
Features: AoE HTTP iSCSI DNS TFTP bzImage COMBOOT ELF Multiboot PXE
PXEXT
No more network devices
No a
Hello Gilles
pcnet32_probe() fails at the next possible opportunity after the NIC
reset. As Piotr already pointed out, there is a fix for the reset
routine in git mainline which is likely to resolve your problem.
gPXE mainline is usually very stable and it should be fine to use the
git version
...
With only PCNET32, it doesn't detect the interface with ifopen net0.
That's most likely caused by a bug in probe which is already fixed in
master [1]. We really need to release 1.0.2. In the meantime i would
suggest building from master or 1.0.1 + cherry-pick that commit.
[1] -
Hi,
I tried to use GPXE (1.0.1 and Git version) on a Fujitsu Laptop with a
Broadcom chipset (BCM5751M) and it doesn't detect the interface. ifopen
fails with no such interface. I tried to compile with DEBUG=tg3 but no
more information displayed.
Is this a known issue?
Gilles
Hi again,
Sorry, it's my day of testing for latest GPXE 1.0.1 version so I spam
the list a lot! ;)
I made another test on another Fujitsu Siemens Laptop with the chipset
Marvell 88E8055 and just after the ifopen net0 I have the prompt back
and it crashes (Keyboad is blocked, no message). If I am
2010/7/28 Gilles Martin gilles.mar...@psi.ch:
Ok, here is the information:
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme
BCM5751M Gigabit Ethernet PCI Express [14e4:167d] (rev 11)
You could try adding a PCI_ROM entry for that vendor and device code
at end of
Le mercredi 28 juillet 2010 à 16:27 +0200, Piotr Jaroszyński a écrit :
On 28 July 2010 16:18, Gilles Martin gilles.mar...@psi.ch wrote:
Hi again,
Sorry, it's my day of testing for latest GPXE 1.0.1 version so I spam
the list a lot! ;)
I made another test on another Fujitsu Siemens
Le mercredi 28 juillet 2010 à 16:36 +0200, Piotr Jaroszyński a écrit :
2010/7/28 Gilles Martin gilles.mar...@psi.ch:
Ok, here is the information:
02:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme
BCM5751M Gigabit Ethernet PCI Express [14e4:167d] (rev 11)
You could try
10 matches
Mail list logo