Re: WEIRD BIOS-related error...
Gil Stendig <[email protected]> Wed, 16 Nov 2005 14:36:17 -0800 (PST)
| Newsgroups | gmane.linux.pxes.devel |
|---|---|
| Message-ID | <[email protected]> |
--0-2118257324-1132180577=:93765 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable So the second DHCP request fixes/resolves the issue? Could you by any cha= nce post the snippet of code you added (and which file you added it to - = although, I assume it's the "rcS" file)? =20 Thank you SO much for your help - I was going nuts trying to troubleshoo= t this issue! =20 Thanks, Gil Chris Gianelloni <[email protected]> wrote: On Wed, 2005-11-16 at 09:29= -0800, Gil Stendig wrote: > Hey guys, > So while trying to run a PXES configuration on some old Dell Optiplex > GX-150s here at work, with their 3Com 3c920 integrated NICs, I run > into the following error: upon a cold-boot/power-up, I (without fail) > get a "DHCP Error: Network Failed to Initialize (eth0)" error. > HOWEVER, if upon bootup I hit F2 to enter BIOS and then exit > immediately (without even changing anything) and then continue to boot > normally, PXES detects the networking card and everything then works > fine! >=20 > (NOTE: I'm using the built-in 2.4.20-12 kernel, and the built-in 3c59x > driver, since there isn't a specific 3c920 driver - and as I mentioned > before, when it works, it works, so I don't think it's a driver/module > problem, per se). >=20 > (Even rebooting, via "reboot" from the command prompt, at that point > works fine. Powering down and then turning back on, though, still > doesn't work, and I have to resort to entering/exiting BIOS again to > get things to work). >=20 > Oddly enough, this happens on all the GX-150s we have here at the > office, without fail. So far, I've tried updating the BIOS to the > latest version (A11 from version A09), but that doesn't seem to help. > Does anyone have any ideas about what's wrong or how to fix it? Any > help would be GREATLY appreciated. I have the same issue on the GX-110. I simply added a second DHCP request to PXES' init scripts, and only have it fail with an error if the second one fails. I would definitely say it is related to the Dell systems. I also found that this does not occur nearly as much with portfast enabled on the port that the machine is plugged into on our Cisco switches. --=20 Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux =09 --------------------------------- Yahoo! FareChase - Search multiple travel sites in one click. =20 --0-2118257324-1132180577=:93765 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable <div id=3D"RTEContent">So the second DHCP request fixes/resolves the issu= e? Could you by any chance post the snippet of code you added (and which = file you added it to - although, I assume it's the "rcS" file)?<br> <br> = Thank you SO much for your help - I was going nuts trying to troubleshoot= this issue!<br> <br> Thanks,<br> Gil<br><br><b><i>Chris Gianelloni <w= [email protected]></i></b> wrote:<blockquote class=3D"replbq" style=3D= "border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left:= 5px;"> On Wed, 2005-11-16 at 09:29 -0800, Gil Stendig wrote:<br>> Hey= guys,<br>> So while trying to run a PXES configuration on some old De= ll Optiplex<br>> GX-150s here at work, with their 3Com 3c920 integrate= d NICs, I run<br>> into the following error: upon a cold-boot/power-up= , I (without fail)<br>> get a "DHCP Error: Network Failed to Initializ= e (eth0)" error.<br>> HOWEVER, if upon bootup I hit F2 to enter BIOS a= nd then exit<br>> immediately (without even changing anything) and then continue to boot<br>> normally, PXES dete= cts the networking card and everything then works<br>> fine!<br>> <= br>> (NOTE: I'm using the built-in 2.4.20-12 kernel, and the built-in = 3c59x<br>> driver, since there isn't a specific 3c920 driver - and as = I mentioned<br>> before, when it works, it works, so I don't think it'= s a driver/module<br>> problem, per se).<br>> <br>> (Even reboot= ing, via "reboot" from the command prompt, at that point<br>> works fi= ne. Powering down and then turning back on, though, still<br>> doesn't= work, and I have to resort to entering/exiting BIOS again to<br>> get= things to work).<br>> <br>> Oddly enough, this happens on all the = GX-150s we have here at the<br>> office, without fail. So far, I've tr= ied updating the BIOS to the<br>> latest version (A11 from version A09= ), but that doesn't seem to help.<br>> Does anyone have any ideas abou= t what's wrong or how to fix it? Any<br>> help would be GREATLY appreciated.<br><br>I have the same issue on the GX-110= . I simply added a second DHCP<br>request to PXES' init scripts, and onl= y have it fail with an error if<br>the second one fails. I would definit= ely say it is related to the Dell<br>systems. I also found that this doe= s not occur nearly as much with<br>portfast enabled on the port that the = machine is plugged into on our<br>Cisco switches.<br><br>-- <br>Chris Gia= nelloni<br>Release Engineering - Strategic Lead<br>x86 Architecture Team<= br>Games - Developer<br>Gentoo Linux<br></blockquote><br></div><p> <hr size=3D1> <a href=3D"http://us.lrd.yahoo.com/_ylc=3DX3oDMTFqODRtdXQ= 4BF9TAzMyOTc1MDIEX3MDOTY2ODgxNjkEcG9zAzEEc2VjA21haWwtZm9vdGVyBHNsawNmYw--= /SIG=3D110oav78o/**http%3a//farechase.yahoo.com/">Yahoo! FareChase - Sear= ch multiple travel sites in one click.</a> =20 =20 --0-2118257324-1132180577=:93765-- ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click