| 00:30.46 | *** join/##pxe jtg23 (n=jtg23@unaffiliated/jtg23) |
| 00:32.06 | jtg23 | hey i have a pxe setup that was working with one client but now it's not with a new one; it says "can't open /tmp/net-eth0.conf"--is anyone familiar with this? |
| 02:20.14 | *** join/##pxe jtg23 (n=jtg23@c-67-160-86-42.hsd1.wa.comcast.net) |
| 05:26.11 | *** join/##pxe jtg23 (n=jtg23@c-67-160-86-42.hsd1.wa.comcast.net) |
| 08:56.32 | *** join/##pxe Norky (n=dan@milton.ocsl.co.uk) |
| 10:14.53 | Nirkus | which computer at which point in the boot process fails with this messsage? |
| 10:59.08 | *** join/##pxe jbot (i=ibot@pdpc/supporter/active/TimRiker/bot/apt) |
| 10:59.08 | *** topic/##pxe is PXE HOWTO at: http://pxe.dev.aboveaverageurl.com/index.php/PXE_Index | Also see http://en.wikipedia.org/wiki/Preboot_Execution_Environment (also at de.wiki) | Need help? Stick around (for about 8 hours, we're probably sleeping or at school)! | Want logs? http://tinyurl.com/2ja6hn |
| 12:00.34 | *** join/##pxe mqueiros_ (n=mqueiros@c-217-70-70-6.bragatel.pt) |
| 13:40.44 | *** join/##pxe frederico (n=ibm@189-29-96-13-tb.cpe.vivax.com.br) |
| 19:50.35 | *** join/##pxe mqueiros_ (n=mqueiros@c-217-70-69-72.bragatel.pt) |
| 20:14.29 | *** join/##pxe jtg23 (n=jtg23@75-165-101-117.tukw.qwest.net) |
| 20:15.44 | jtg23 | hey all, i'm having ubuntu pxe issues; would anybody like to help me decipher SIOCGIFINDEX ... can't open /tmp/eth0.conf |
| 20:16.03 | jtg23 | i have outlined the issue here http://ubuntuforums.org/showthread.php?t=714080&highlight=pxe |
| 20:18.50 | ScytheBlade1 | Sounds like a general misconfiguration to me |
| 20:18.57 | ScytheBlade1 | ie, passing bad parameters to ifconfig |
| 20:19.03 | jtg23 | such as? |
| 20:19.17 | ScytheBlade1 | I have no idea, as I can't see all of your config :) |
| 20:19.20 | jtg23 | thing i don't understand is i had another client working with no issues |
| 20:19.49 | jtg23 | and the research i've done pointed to a driver issue, but i don't seem to have any special drivers |
| 20:20.25 | ScytheBlade1 | Actually yeah, it's not finding your eth0 at all |
| 20:20.52 | jtg23 | ok, if i want to hardcode eth0 settings, where do i do that? |
| 20:21.06 | ScytheBlade1 | You need to find the correct driver for it, and then either a) build it into your kernel, or b) make it a module, throw into your initrd and modify it |
| 20:21.23 | ScytheBlade1 | Um, in any one of fifteen billion places - you can "hardcode eth0 settings" almost anywhere you please |
| 20:21.34 | ScytheBlade1 | "No such device" means that the kernel is not seeing your NIC |
| 20:21.58 | jtg23 | ok now when i boot regularly w the hd, it seems as though it comes up and then goes down and then comes up again |
| 20:22.02 | ScytheBlade1 | You're probably looking at modifying your kernel or your initrd at a minimum |
| 20:22.20 | ScytheBlade1 | Meaningless, as when you boot from the HD, you're using a different boot path completely |
| 20:22.20 | jtg23 | ok, i'll look into this |
| 20:22.37 | ScytheBlade1 | It might be the same kernel, it might not be! It might be in the initrd, it might not be! |
| 20:22.37 | jtg23 | i gotcha, but the fact that the pxe starts indicates my nic gets recognized at some point, no? |
| 20:22.53 | ScytheBlade1 | Yes, because your NIC hooks into the BIOS and says "hey I'm a boot device" |
| 20:23.03 | ScytheBlade1 | The BIOS in turn uses a generalized interface to the NIC to make it go |
| 20:23.07 | jtg23 | ahhhh |
| 20:23.14 | ScytheBlade1 | That's the "pre boot stage" so to speak |
| 20:23.26 | jtg23 | i follow; and then when it passes off my actual driver, it's absent |
| 20:23.29 | *** join/##pxe winksaville (n=chatzill@70.91.206.233) |
| 20:23.31 | ScytheBlade1 | After that, your NIC loads the kernel - and then PXE is *100% not even relevant* |
| 20:23.37 | ScytheBlade1 | Yup |
| 20:23.48 | ScytheBlade1 | PXE loads a binary, and that binary takes it and runs with it |
| 20:24.10 | jtg23 | ok well thank you for the info; this sheds light on a confusing area |
| 20:24.14 | ScytheBlade1 | Your distro not finding your NIC isn't even related to the fact that you can PXE boot :) |
| 20:24.17 | ScytheBlade1 | Good :) |
| 20:25.42 | ScytheBlade1 | Once the boot process is passed on, the PXE stack is (typically) unloaded from memory, and whatever binary it was passed takes full and complete control |
| 20:25.54 | ScytheBlade1 | In your case, that binary is a linux kernel, and also in your case, your kernel isn't seeing your NIC |
| 20:26.33 | jtg23 | so i need to look at my /nfsroot/etc/initrd ? |
| 20:30.03 | ScytheBlade1 | Or your kernel |
| 20:30.26 | ScytheBlade1 | Actually no |
| 20:30.40 | ScytheBlade1 | Your nfsroot only comes into play once you have network access |
| 20:31.00 | jtg23 | ohh right, so i'm hitting the tftp server and then not mounting the nfs |
| 20:31.06 | jtg23 | i'm starting to see the err of my ways, FINALLY |
| 20:31.35 | ScytheBlade1 | Your problem lies inbetween your PXE stack and your init scripts |
| 20:32.13 | jtg23 | right, see here's what i don't understand--why doesn't the driver get built properly when i do mkinitramfs -o blah |
| 20:32.20 | jtg23 | shouldn't that have wrapped up the driver? |
| 20:39.53 | winksaville | Hello, I've got pxelinux.0 running and then have default config setup to run memtest86, I get to "boot: " then the |
| 20:39.55 | winksaville | delay and then a bunch of "8000" one per line forever. Any ideas where the "8000" are coming from? |
| 20:41.25 | jtg23 | um did you output the timeout in the menu.lst file? |
| 20:43.41 | winksaville | Below is my pxelinux.cfg/default, what do you menat menu.lst? |
| 20:43.43 | winksaville | prompt 1 |
| 20:43.44 | winksaville | default memtest |
| 20:43.46 | winksaville | timeout 10 |
| 20:43.47 | winksaville | label memtest |
| 20:43.49 | winksaville | <PROTECTED> |
| 20:44.11 | winksaville | what do you mean(sp) menu.list? |
| 20:45.46 | jtg23 | or menu.c32 |
| 20:46.31 | jtg23 | but it doesn't look like that's your problem |
| 20:46.37 | jtg23 | it sounds like you're outputting text though somewhere |
| 20:49.57 | winksaville | is there a "hello world" that I can execute via pxelinux.0, i.e. a trivial program? |
| 20:50.16 | jtg23 | um, the best luck i've had is testing the nfs |
| 20:50.48 | jtg23 | have you seen this tutorial? http://www.xs4all.nl/~rjb/fatclient.html |
| 20:50.56 | jtg23 | i got my setup running using that |
| 20:51.30 | winksaville | Thanks, I'll take a look |
| 20:51.52 | jtg23 | k, good luck |
| 21:09.41 | *** join/##pxe jtg23 (n=jtg23@75-165-101-117.tukw.qwest.net) |
| 21:22.21 | ScytheBlade1 | winksaville: run `file memtest.bin` and paste what comes out |
| 21:22.40 | ScytheBlade1 | It should be reported as an X86 boot sector |
| 21:51.43 | winksaville | wink@ic2d1:$ file memtest.bin |
| 21:51.45 | winksaville | memtest.bin: x86 boot sector |
| 21:52.01 | ScytheBlade1 | Rename it from .bin (try just 'memtest') |
| 21:53.03 | winksaville | Is this what you mean? |
| 21:53.04 | winksaville | wink@ic2d1:$ sudo mv memtest.bin memtest |
| 21:53.06 | winksaville | wink@ic2d1:$ file memtest |
| 21:53.07 | winksaville | memtest: x86 boot sector |
| 21:53.07 | ScytheBlade1 | Yes |
| 21:53.17 | ScytheBlade1 | Now configure the default file to run that file |
| 21:54.59 | winksaville | My pxelinux.cfg/default is now: |
| 21:55.00 | winksaville | prompt 1 |
| 21:55.02 | winksaville | default memtest |
| 21:55.03 | winksaville | timeout 10 |
| 21:55.05 | winksaville | label memtest |
| 21:55.06 | winksaville | <PROTECTED> |
| 21:56.30 | winksaville | I just rebooted the test machine and I have a nice memtest screen |
| 21:56.31 | winksaville | although the test doesn't seem to be running. What is magical |
| 21:56.32 | winksaville | about ".bin"? |
| 21:57.05 | ScytheBlade1 | pxelinux will do different things based on the file extension |
| 21:57.23 | ScytheBlade1 | (or lack thereof) |
| 21:57.35 | winksaville | good to know:) |
| 21:59.11 | winksaville | it doesn't seem to be running, I'd expect "Test %" to be updating but things |
| 21:59.13 | winksaville | look dead. Seems I've done something else wrong? |
| 21:59.52 | ScytheBlade1 | Try a new version of it? |
| 22:02.27 | winksaville | hoo ya, using memtest86+-2.01 works THANKS! |
| 22:02.41 | ScytheBlade1 | Yup, enjoy |