<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><div id="yiv1564245935"><table id="yiv1564245935bodyDrftID" class="yiv1564245935" border="0" cellpadding="0" cellspacing="0"><tbody><tr><td id="yiv1564245935drftMsgContent" style="font-style: inherit; font-variant: inherit; font-weight: inherit; line-height: inherit; font-size-adjust: inherit; font-stretch: inherit; font-family: arial; font-size: 10pt;">Hi there,<br><br>rom-o-matic.net is still down on 01/27/2011 at 11h54 PM (GMT+1)<br><br>I can ping the server but a port scan shows no open ports not even 80 (maybe a firewall) <br>but it can't load in FireFox 3.6.13 on Linux.<br><br>by running "ping rom-o-matic.net" I get:<br><br><span style="font-style: italic; font-weight: bold;">"10 packets transmitted, 9 received, 10% packet loss, time 9756ms</span><br style="font-style: italic; font-weight: bold;"><span style="font-style: italic; font-weight:
bold;">rtt min/avg/max/mdev = 232.616/234.264/235.062/0.907 ms"</span><br><br>Is it just me ? (my cache is flushed & I reloaded with Ctrl+F5)<br><br>Thanks !<br>TheMadOne.<br><br>--- En date de : <b>Mer 26.1.11, gpxe-request@etherboot.org <i><gpxe-request@etherboot.org></i></b> a écrit :<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>De:
gpxe-request@etherboot.org <gpxe-request@etherboot.org><br>Objet: gPXE Digest, Vol 16, Issue 13<br>À: gpxe@etherboot.org<br>Date: Mercredi 26 janvier 2011, 18h00<br><br><div class="yiv1564245935plainMail">Send gPXE mailing list submissions to<br> <a rel="nofollow">gpxe@etherboot.org</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br> <a rel="nofollow" target="_blank" href="http://etherboot.org/mailman/listinfo/gpxe">http://etherboot.org/mailman/listinfo/gpxe</a><br>or, via email, send a message with subject or body 'help' to<br> <a rel="nofollow">gpxe-request@etherboot.org</a><br><br>You can reach the person managing the list at<br> <a rel="nofollow">gpxe-owner@etherboot.org</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of gPXE digest..."<br><br><br>Today's Topics:<br><br> 1.
rom-o-matic.net offline? (Guilherme Benkenstein)<br> 2. Re: rom-o-matic.net offline? (Miller, Shao)<br> 3. Re: iSCSI boot works sometimes (Chad Voelker)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 25 Jan 2011 14:45:34 -0200<br>From: Guilherme Benkenstein <<a rel="nofollow">gb@gbti.com.br</a>><br>Subject: [gPXE] rom-o-matic.net offline?<br>To: <a rel="nofollow">gpxe@etherboot.org</a><br>Message-ID:<br> <AANLkTi=<a rel="nofollow">96gSdB5P0gi5f6n29XT2ztE-4ZnjhTOGp1m9V@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>Hi all<br><br>Does rom-o-matic.net offline?<br><br>Thanks<br><br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 25 Jan 2011 17:25:00 -0500<br>From: "Miller, Shao" <<a rel="nofollow">shao.miller@yrdsb.edu.on.ca</a>><br>Subject: Re: [gPXE] rom-o-matic.net
offline?<br>To: "Guilherme Benkenstein" <<a rel="nofollow">gb@gbti.com.br</a>><br>Cc: <a rel="nofollow">gpxe@etherboot.org</a><br>Message-ID:<br> <<a rel="nofollow">F0E5F8699DE1364584CDB894E997135520E25FA1@YRDSB5.YRDSB.YRDSB.NET</a>><br>Content-Type: text/plain; charset="us-ascii"<br><br>Good day, Guilherme.<br><br>I believe that Marty Connor just ensured that Etherboot Project servers<br>are back online. Please do try again. :)<br><br>- Shao Miller<br><br><br>------------------------------<br><br>Message: 3<br>Date: Tue, 25 Jan 2011 20:21:30 -0600<br>From: Chad Voelker <<a rel="nofollow">chad.voelker@gmail.com</a>><br>Subject: Re: [gPXE] iSCSI boot works sometimes<br>To: <a rel="nofollow">gpxe@etherboot.org</a><br>Message-ID: <<a rel="nofollow">4D3F852A.1010908@gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>To update the list on what I've done. I
tried Andrew's suggestions <br>below, but entries in the blacklist file don't seem to make a <br>difference. I believe that this is either because a) the initramfs <br>process does not look at the /etc/modules directory or b) The scripts <br>mentioned in the link here: <br><a rel="nofollow" target="_blank" href="http://etherboot.org/wiki/sanboot/ubuntu_iscsi2">http://etherboot.org/wiki/sanboot/ubuntu_iscsi2</a> do the loading of the <br>drivers explicitly. Though, if "b" was the explanation, I would expect <br>them to be loaded in the same order each time.<br><br>What I ended up doing was adjust this portion of the <br>/etc/initramfs-tools/scripts/local-top/iscsi file (hopefully, the <br>formatting comes across ok):<br> until ifconfig
${netdev}|grep -q "inet addr"; do<br> for netdev in `ifconfig -a|grep Ethernet|cut -d' ' -f1`; do <br> # Do a round-robin search for dhcp servers<br> ip link set ${netdev} up <br> # try to bring up the interface<br> ipconfig -t 2 -c dhcp -d ${netdev} <br> # Get an IP<br> if ifconfig -a|grep -q "inet addr"; then break 2; fi <br> # If we have got an address, stop searching.<br># If we are here, then we have a problem, remove and re-add the
NIC<br> rmmod forcedeth <br> # <--- Remove the NIC driver<br> sleep 1 <br> # <--- Give it some time<br> modprobe forcedeth # <--- Re-add the NIC driver<br> sleep 2 # <--- Give it some time<br> done # end of netdev probing<br> CNT=$((${CNT} - 1))<br> if [ ${CNT} = 0 ];
then<br> echo "No dhcp servers found!"<br> exit 0<br> fi<br> echo "Tries left: ${CNT}"<br> done # end of until<br><br>I added the four lines below "If we are here, then we have a problem..." <br>Not the cleanest solution, but it has been reliable.<br><br>Thanks again Andrew for your help. If nothing else, you helped confirm <br>that I was looking in the right direction.<br><br>-Chad<br><br><br><br>On 01/19/2011 08:23 AM, Andrew Bobulsky wrote:<br>> Hello Chad,<br>><br>> As a disclaimer, I've got next to no idea how device drivers on Linux<br>> work, so I've only got some guesses for you ;)<br>> I suspect you might be right about driver load order having something<br>> to do with it. Specifically, in your non-working example's
dmesg<br>> output:<br>><br>> <br>>> [ 1.249252] forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20<br>>> [ 1.249350] forcedeth 0000:00:0a.0: setting latency timer to 64<br>>> [ 1.302279] Loading iSCSI transport class v2.0-870.<br>>> [ 1.315354] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 90:fb:a6:2b:ee:ff<br>>> [ 1.315450] forcedeth 0000:00:0a.0: highdma csum pwrctl gbit lnktim msi desc-v3<br>>> <br>> I'm unsure as to whether the iSCSI driver used here cares whether or<br>> not a NIC is available before it goes hunting for the iBFT, but it<br>> could be possible. It looks like Linux kernels are designed to not<br>> care a whole lot about device driver load order... which seems odd to<br>> me, but I'm sure there's a
reason for it.<br>><br>> While the blog post I found is a little dated, the technique (though a<br>> little convoluted!) may likely still apply. Take a look here:<br>> <a rel="nofollow" target="_blank" href="http://rackerhacker.com/2009/01/26/linux-adjust-storage-kernel-module-load-order/">http://rackerhacker.com/2009/01/26/linux-adjust-storage-kernel-module-load-order/</a><br>><br>> Doubling down on that disclaimer again, the following suggestion is a<br>> complete guess:<br>><br>> First, open your /etc/modprobe.d/blacklist file and add iscsi on to<br>> the end of it.<br>> Then, open your /etc/modules file and specify the forcedeth driver<br>> followed by the iscsi driver.<br>><br>> Might work :P<br>><br>> Best regards,<br>> Andrew Bobulsky<br>><br>><br>> On Wed, Jan 19, 2011 at 8:35 AM, Chad Voelker<<a rel="nofollow">chad.voelker@gmail.com</a>> wrote:<br>>
<br>>> Hello,<br>>><br>>> I apologize for being slightly off-topic...<br>>><br>>> I have a Ubuntu 10.04 Myth frontend that I'm trying to get booting with iSCSI. gPXE is working, and attaching the iSCSI drive and initiating the boot sequence on the iSCSI drive. Following the guide here: <a rel="nofollow" target="_blank" href="http://etherboot.org/wiki/sanboot/ubuntu_iscsi2">http://etherboot.org/wiki/sanboot/ubuntu_iscsi2</a>, it sometimes fails on the file /etc/initramfs-tools/scripts/local-top/iscsi where it tries to call ipconfig to get DHCP info (even though the server is there and fine, otherwise we wouldn't have gotten this far).<br>>><br>>> This works somewhere around 1 out of 3 boots. What I've noticed in dmesg is that when working, the iSCSI driver is loaded near the end of the process. I've listed (trimmed)
versions of the dmesg output below, if you need the complete output let me know.<br>>><br>>> Is there somewhere that I can dictate the order that things are loaded? Any other ideas?<br>>><br>>> Thanks.<br>>> -Chad<br>>><br>>> dmesg (entries that are repeated / unimportant are shortened with a "...")<br>>><br>>> Working...<br>>><br>>> [ 0.947158] udev: starting version 151<br>>> [ 1.115166] ahci ...<br>>> [ 1.132935] scsi0 : ahci...<br>>> [ 1.252750] ata1: SATA max UDMA/133 ...<br>>> [ 1.253462] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.<br>>> [ 1.254782] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 23<br>>> [ 1.254869] forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 23 (level, low) -> IRQ 23<br>>>
[ 1.254965] forcedeth 0000:00:0a.0: setting latency timer to 64<br>>> [ 1.318176] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 90:fb:a6:2b:ee:ff<br>>> [ 1.318264] forcedeth 0000:00:0a.0: highdma csum pwrctl gbit lnktim msi desc-v3<br>>> [ 1.348043] usb 2-3: ...<br>>> [ 1.572051] ata1: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.572193] ata2: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.600025] ata6: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.600139] ata3: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.600146] ata4: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.600202] ata5: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.619530] Loading iSCSI transport class v2.0-870.<br>>> [ 1.667310] iscsi:
registered transport (tcp)<br>>> [ 1.678221] iBFT detected at 0x93350.<br>>><br>>> Not Working...<br>>><br>>> [ 0.947224] udev: starting version 151<br>>> [ 1.247791] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.<br>>> [ 1.249164] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 20<br>>> [ 1.249252] forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20<br>>> [ 1.249350] forcedeth 0000:00:0a.0: setting latency timer to 64<br>>> [ 1.302279] Loading iSCSI transport class v2.0-870.<br>>> [ 1.315354] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 90:fb:a6:2b:ee:ff<br>>> [ 1.315450] forcedeth 0000:00:0a.0: highdma csum pwrctl gbit lnktim msi desc-v3<br>>> [ 1.325446]
ahci ...<br>>> [ 1.327784] scsi0 : ahci...<br>>> [ 1.330959] ata1: SATA max UDMA/133 ...<br>>> [ 1.352040] usb 2-3: ...<br>>> [ 1.648030] ata2: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.648131] ata1: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.652029] ata4: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.652122] ata5: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.652132] ata3: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.656026] ata6: SATA link down (SStatus 0 SControl 300)<br>>> [ 1.672896] iscsi: registered transport (tcp)<br>>> [ 1.683754] iBFT detected at 0x93350.<br>>><br>>><br>>> _______________________________________________<br>>> gPXE mailing list<br>>> <a
rel="nofollow">gPXE@etherboot.org</a><br>>> <a rel="nofollow" target="_blank" href="http://etherboot.org/mailman/listinfo/gpxe">http://etherboot.org/mailman/listinfo/gpxe</a><br>>><br>>> <br>> <br><br><br>------------------------------<br><br>_______________________________________________<br>gPXE mailing list<br><a rel="nofollow">gPXE@etherboot.org</a><br><a rel="nofollow" target="_blank" href="http://etherboot.org/mailman/listinfo/gpxe">http://etherboot.org/mailman/listinfo/gpxe</a><br><br><br>End of gPXE Digest, Vol 16, Issue 13<br>************************************<br></div></blockquote></td></tr></tbody></table></div></td></tr></table><br>