|
osdir.com mailing list archive F.A.Q. -since 2001! |
|
|
|
Subject: Re: PXE-on-a-disk Intel EM64T reboot - msg#00028List: network.etherboot.user
by Date: Prev Next Date Index by Thread: Prev Next Thread Index
Hi Josh,
[ I added Etherboot-Users to the list for wider distribution. ] This looks like a great tool! ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html A Universal PXE-on-a-disk floppy is a really neat thing. I have read the thread on the SYSLINUX list, and see how it differs from: http://etherboot.anadex.de/ Which is another neat tool. Thanks so much for doing this. I would like to continue discussion of the outstanding issues that you mention, and maybe we can make it even better. I think that there are a few people on the lists that may be able to help debug the EM64T issue. Is there any chance of a hardware donation we can offer to someone who is willing to figure it out? We can also offer a small cash reward (although Eternal Glory may be enough ;) In any case, thanks very much for your work! It's a nice tool, and I encourage you to keep polishing it. It might be something to consider putting on the Etherboot web site. Everyone who can, please test this tool, and send your findings to Etherboot-Users. Thanks, Marty On Dec 30, 2005, at 11:16 PM, Josh Lehan wrote: Hello. I've used Etherboot and SYSLINUX to create a "PXE-on-a- disk" implementation: a floppy and CD image that is self-booting. It does what a PXE BIOS would do, and is useful for computers that don't have a built-in PXE BIOS. The disk is full of compiled Etherboot packages, one build for each supported PCI driver. Ethersel (part of SYSLINUX) autodetects the PCI network card, and selects the proper Etherboot package to load. Works fine from there! Here's a simple webpage I made about it, and a download link: ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html The only problem is on the Intel EM64T (Intel's clone of AMD's 64- bit architecture). After the download of the Linux kernel succeeds, something goes wrong, and instead of starting the kernel, the machine reboots. I'm guessing it's some kind of cleanup issue, or something early on in the transition from 16-bit BIOS to 64-bit kernel. I've tested on 32-bit machines, and AMD Opteron 64-bit machines, and it works fine there. It's also not related to any particular brand of network card. On the Intel EM64T machines this problem happens on, I was able to PXE boot just fine from the on-board BIOS, and also from the local hard drive. It worked fine from there, so know it's not a problem with PXELINUX, or the booting process in general, on that particular machine. This is all probably a moot point, since it'd be a fair guess that all Intel EM64T machines ever made have a working PXE BIOS in them, making this "PXE-on-a-disk" unnecessary, but thought I'd mention it, in case anybody else has seen this. Thanks! Josh Lehan jlehan@xxxxxxxxx -- 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: mdc@xxxxxxxxxxxxx Web: http://www.etherboot.org/ ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
Thread at a glance:
Previous Message by Date:Re: Re: Re: Realtek rtl8169 not workingBruno Cesar Ribas wrote: On Fri, Dec 30, 2005 at 02:54:45AM -0200, Bruno Cesar Ribas wrote: Timothy Legge wrote: It looks like there have been some updates to the linux version of the driver that include mac versions. It looks like I will need to pull that in. Give me a few days. I did a diff between the linux 2.4.21 driver and a current 2.6.13 driver and the result is not pretty. The diff is 3 times the size of the driver. ;-) It will take a bit to separate what exactly is needed. Since I don't have a copy of your card, it will take more time. Feel free to contact me off list if you can provide a sample. Hi Tim, Would you like some help to code rtl8169 stuff? I do need it working round here, and i think i might be able to provide some help coding the drive. Bruno Bruno Have you tried the latest update from cvs? I updated the driver about 5 weeks ago to address new linux driver changes. Tim ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click Next Message by Date:Re: Re: Realtek rtl8169 not working>Timothy Legge wrote: >> It looks like there have been some updates to the linux version of the >> driver that include mac versions. It looks like I will need to pull >> that in. Give me a few days. >I did a diff between the linux 2.4.21 driver and a current 2.6.13 driver >and the result is not pretty. The diff is 3 times the size of the >driver. ;-) >It will take a bit to separate what exactly is needed. Since I don't >have a copy of your card, it will take more time. Feel free to contact >me off list if you can provide a sample. Hi Tim, Would you like some help to code rtl8169 stuff? I do need it working round here, and i think i might be able to provide some help coding the drive. Bruno >Tim >> >> Tim >> >> Alexander Martins Silva wrote: >> >>> Hi Tim, >>> >>> I cant to give you this information now because im not at >>> work, but the cards have the same chip realtek. One is a Planet ENW >>> 9605 and the second is Encore *ENL832-GB/ENLGA-1320. >>> >>> Alexander. >>> * >>> Timothy Legge wrote: >>> >>>> Alexander Martins Silva wrote: >>>> >>>>> I've got a serious problem with network cards with the Realtk >>>>> 8169s/8101 chipset. With two differents cards I couldnt etherboot a >>>>> client machine, with the same error message: "Searching server >>>>> (DHCP)...No IP Address", but works when I use a machine with a >>>>> different network card (nvidia2). What's happening? The r8169 drive >>>>> dont work for the rtl8169? Someone got the same problem? >>>>> >>>>> Thanks is advance, >>>> >>>> >>>> >>>> >>>> Hi >>>> >>>> Please provide the PCI ids for the card. >>>> >>>> Tim -- Bruno Ribas - ribas@xxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click Previous Message by Thread:(no subject)hi, I'm having some trouble with recompiling a kernel and using mknbi to get it to boot over network with etherboot diskette...my etherboot works just fine but there is something going wrong after that....I recompiled a linux 2.4 kernel provided with damn small linux distrobution to include support for "root filesystem on NFS" "IP: kernel level autoconfiguration" "enable bootp support" "RARP support" and "DHCP support" and also provided kernel level support for boot clients NIC...I then run the command: "mkelf-linux --ip=192.168.2.1:192.168.2.240:192.168.2.255:255.255.255.0:D1000 bzImage-2.4.31 --output=kernel --rootdir=nfsroot" and place the generated file "kernel" into the "c\tftpd32\knoppix\boot\isolinux" folder of the damn small linux distrobution which I am serving via DHCP to my bootclient off of a windows machine...I also have same folder exported via NFS as "/tftpboot/nfsroot" Upon bootup the kernel begins to load successfully but halts with the following error: Looking up port of RPC 10003/2 on 192.168.2.240 VFS: Mounted root (nfs filesystem). Freeing unused kernel memory: 148k freed Warning: unable to open an initial console. Kernel panic: No init found. Try passing init= option to kernel. aslo, my NFS server displays the following information: Mountd(v1): 192.168.2.1 requests mount of /tftpboot/nfsroot. Mount request accepted. 09:43:16 (nfsv2) getattr(C:\tftpd32\KNOPPIX) ==> 16ms 09:43:16 (nfsv2) statfs(C:\tftpd32\KNOPPIX) ==> 15ms 09:43:16 (nfsv2) getattr(C:\tftpd32\KNOPPIX) ==> 0ms 09:43:16 (nfsv2) getattr(C:\tftpd32\KNOPPIX) ==> 0ms 09:43:16 (nfsv2) lookup(C:\tftpd32\KNOPPIX, dev) => [Not found] 09:43:16 (nfsv2) lookup(C:\tftpd32\KNOPPIX, sbin) => [Not found] 09:43:16 (nfsv2) lookup(C:\tftpd32\KNOPPIX, etc) => [Not found] 09:43:16 (nfsv2) lookup(C:\tftpd32\KNOPPIX, bin) => [Not found] gc: XN-E=89% N=535872 O+=0 I try using the command: "mkelf-linux init=kernel --ip=192.168.2.1:192.168.2.240:192.168.2.255:255.255.255.0:D1000 bzImage-2.4.31 --output=kernel --rootdir=nfsroot" and recieve the error: "init=kernel: file not found" any feedback greatly appreciated. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click Next Message by Thread:Re: Re: Realtek rtl8169 not working>Timothy Legge wrote: >> It looks like there have been some updates to the linux version of the >> driver that include mac versions. It looks like I will need to pull >> that in. Give me a few days. >I did a diff between the linux 2.4.21 driver and a current 2.6.13 driver >and the result is not pretty. The diff is 3 times the size of the >driver. ;-) >It will take a bit to separate what exactly is needed. Since I don't >have a copy of your card, it will take more time. Feel free to contact >me off list if you can provide a sample. Hi Tim, Would you like some help to code rtl8169 stuff? I do need it working round here, and i think i might be able to provide some help coding the drive. Bruno >Tim >> >> Tim >> >> Alexander Martins Silva wrote: >> >>> Hi Tim, >>> >>> I cant to give you this information now because im not at >>> work, but the cards have the same chip realtek. One is a Planet ENW >>> 9605 and the second is Encore *ENL832-GB/ENLGA-1320. >>> >>> Alexander. >>> * >>> Timothy Legge wrote: >>> >>>> Alexander Martins Silva wrote: >>>> >>>>> I've got a serious problem with network cards with the Realtk >>>>> 8169s/8101 chipset. With two differents cards I couldnt etherboot a >>>>> client machine, with the same error message: "Searching server >>>>> (DHCP)...No IP Address", but works when I use a machine with a >>>>> different network card (nvidia2). What's happening? The r8169 drive >>>>> dont work for the rtl8169? Someone got the same problem? >>>>> >>>>> Thanks is advance, >>>> >>>> >>>> >>>> >>>> Hi >>>> >>>> Please provide the PCI ids for the card. >>>> >>>> Tim -- Bruno Ribas - ribas@xxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
blog comments powered by Disqus
|
|