[ipxe-devel] ipxe-devel Digest, Vol 28, Issue 7
Michael Zhou
michael.zhou.sh at gmail.com
Fri Sep 28 12:01:08 UTC 2012
Hi,
When booting with ipxe.usb on gigabit network, i found that:
Client PC can not get IP address by "dhcp net0", but if set IP address to
net0 by "config net0", and ping the IP address, i got response.
I tried ping the IP address by format of "ping xxx.xxx.xxx.xxx -l N", with
size N, when N is bigger than 210, no response from client.
Hope this is helpful for fix the issue.
Michael
On Sat, Sep 8, 2012 at 7:00 PM, <ipxe-devel-request at lists.ipxe.org> wrote:
> Send ipxe-devel mailing list submissions to
> ipxe-devel at lists.ipxe.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
> or, via email, send a message with subject or body 'help' to
> ipxe-devel-request at lists.ipxe.org
>
> You can reach the person managing the list at
> ipxe-devel-owner at lists.ipxe.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ipxe-devel digest..."
>
>
> Today's Topics:
>
> 1. IPXE question: iPXE.efi can't detect network device
> (=?gb18030?B?u6/Krw==?=)
> 2. Re: Transform syslinux menu.c32/menu.cfg to ipxe menu
> (Thomas Glanzmann)
> 3. Recent tg3 driver commits still fail on gigabit (me too)
> (Wes Hardin)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 7 Sep 2012 21:37:02 +0800
> From: "=?gb18030?B?u6/Krw==?=" <354225989 at qq.com>
> To: "=?gb18030?B?aXB4ZS1kZXZlbA==?=" <ipxe-devel at lists.ipxe.org>
> Subject: [ipxe-devel] IPXE question: iPXE.efi can't detect network
> device
> Message-ID: <tencent_153984982058C99F1A0F4D1F at qq.com>
> Content-Type: text/plain; charset="gb18030"
>
> Dear IPXE owner,
> Thanks for ipxe develop team hard work,after read ipxe code ,i found that
> ipxe code is very classic and helpful to me.
> Our product will import ipxe,but efi file can't found network device,I
> built efi file according to the below steps.
> 1.I have undef PXE_STACK and PXE_MENU in src\config\general.h.
> 2.Built EFI version as vendor/product specific:
> $ make bin-x86-64/10222000.efi bin-x86-64/10222001.efi
> bin-x86-64/10222625.efi.(computer vendor is 1022 ,device id is 2001).
> $make bin-x86-64-efi/80861502(computer vendor is 8086,device id is 1502).
> 3.insert usb drive and enter uefi shell.
> 4.fs0:
> 5.run above efi file.
> 6.All commands are Show the tip "No more network devices".
>
>
> My built enviroment like following:
> OS:ubuntu 12
> GCC:4.6
>
>
>
>
>
>
> ------------------ ???? ------------------
> ???: "Anton D. Kachalov"<mouse at yandex-team.ru>;
> ????: 2012?9?6?(???) ??10:18
> ???: "??"<354225989 at qq.com>; "ipxe-devel"<ipxe-devel at lists.ipxe.org>;
>
> ??: Re: PXE question: iPXE.efi can't detect network device
>
>
>
> Hello.
>
> It's better to address this question directly to the
> ipxe-devel at lists.ipxe.org mailing list. Michael Brown should be right
> person.
>
> BTW, ipxe.iso is legacy bootable ISO image and it contains all supported
> network drivers including pcnet32.
>
> Try to build EFI version as vendor/product specific:
>
> $ make bin-x86-64/10222000.efi bin-x86-64/10222001.efi
> bin-x86-64/10222625.efi
>
> One of them should work.
>
> Please pay attention that EFI environment doesn't support PXE stack. You
> have to disable PXE_STACK and PXE_MENU in the config file.
> 06.09.2012, 17:32, "??" <354225989 at qq.com>:
> Dear Anton,
> I have built ipxe.efi 64 bit,my network device card is pcnet32,but
> ipxe.efi can't attach network card,i only get the log "No more network
> devices".but if boot to ipxe via ipxe.iso,ipxe can detected the network
> device card.
> We will add ipxe to our project,so I hurry to solve this problem.
>
> BTW,
> After debug ipxe.efi,i found that only call
> efi_pci.c\efipci_driver_startup but not call efi_pci.c\efipci_start,so i
> think pci device not been attach,do you know that what time to call
> function efipci_start().
>
> Although I have read a topic about "Using iPXE with UNDI driver",but i
> can't find the root cause,Do you know the root cause?
>
> Thank you very much.
> I have built via run command "make bin-x86-64/ipxe.efi DEBUG:efi_pci
> device,pci" and then run ipxe.efi,
> unfortunately,the result like following figure,it means can't attach any
> pci device,do you know why?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20120907/2abcf368/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Fri, 7 Sep 2012 19:41:17 +0200
> From: Thomas Glanzmann <thomas at glanzmann.de>
> To: ipxe-devel at lists.ipxe.org
> Subject: Re: [ipxe-devel] Transform syslinux menu.c32/menu.cfg to ipxe
> menu
> Message-ID: <20120907174117.GB12312 at glanzmann.de>
> Content-Type: text/plain; charset=us-ascii
>
> Robin,
>
> > https://gist.github.com/2234639
>
> thank you for this very versatile and extensive example. I got
> everything up and running now in matter of minutes. For the people
> googling for this:
>
> set menu-timeout 50
>
> :start
> menu Boot menu
> item disk Boot from disk
> item preseed_squeeze_64 Preseed Squeeze 64 installation
>
> choose --default disk --timeout ${menu-timeout} selected || goto cancel
>
> goto ${selected}
>
> :cancel
> echo Type exit to get the back to the menu
> shell
> goto start
>
> :disk
> exit
>
> :preseed_squeeze_64
> kernel http://10.10.10.1/ipxe/squeezex64/debian-installer/amd64/linuxvga=788 interface=auto auto=true netcfg/dhcp_timeout=60 preseed/url=
> http://10.10.10.1/preseed.cfg hostname=debian domain=gmvl.de
> initrd http://10.10.10.1/ipxe/squeezex64/debian-installer/amd64/initrd.gz
> boot
>
> Cheers,
> Thomas
>
>
> ------------------------------
>
> Message: 3
> Date: Fri, 7 Sep 2012 13:47:39 -0500
> From: Wes Hardin <wes.hardin at maximintegrated.com>
> To: <ipxe-devel at lists.ipxe.org>
> Subject: [ipxe-devel] Recent tg3 driver commits still fail on gigabit
> (me too)
> Message-ID: <504A414B.9000509 at maximintegrated.com>
> Content-Type: text/plain; charset="UTF-8"
>
> This is in response to:
> http://lists.ipxe.org/pipermail/ipxe-devel/2012-August/001752.html
>
> I couldn't reply to the original thread because I just signed up for
> mailing
> list today. I've been troubleshooting this issue myself for the past few
> days
> and found this thread today. I would really like to be able to lend my
> assistance in troubleshooting as I can.
>
> For me, the affected BCM5764M is in a HP Z600 Workstation. I have other
> (supposedly identical) Z600s that do not seem to be affected.
>
> I can be found on IRC as Authority, although I'm only around during normal
> US
> business hours during the week.
> --
> /* Wes Hardin */
> UNIX/Linux Systems Administrator, IT Engineering Support
> Maxim Integrated | www.maximintegrated.com
>
>
> ------------------------------
>
> _______________________________________________
> ipxe-devel mailing list
> ipxe-devel at lists.ipxe.org
> https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel
>
>
> End of ipxe-devel Digest, Vol 28, Issue 7
> *****************************************
>
--
Thanks & Best Regards.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20120928/288de0e7/attachment.htm>
More information about the ipxe-devel
mailing list