| 03:43.35 | *** join/##pxe spQ (i=spq@bouncer.by.my-ct.de) |
| 04:06.37 | *** join/##pxe SirFunk (n=Sir@206-159-155-246.netsync.net) |
| 10:44.20 | *** join/##pxe namit (n=test_acc@83-70-235-113.b-ras1.prp.dublin.eircom.net) |
| 11:17.39 | *** join/##pxe namit (n=test_acc@83-70-235-113.b-ras1.prp.dublin.eircom.net) |
| 14:24.16 | *** join/##pxe nami1 (n=test_acc@83-70-235-113.b-ras1.prp.dublin.eircom.net) |
| 17:39.19 | *** join/##pxe _spQ (i=spq@bouncer.by.my-ct.de) |
| 18:33.04 | Nirkus | spq: you might try the 3com card on another computer that has booted fine to confirm its the NIC |
| 18:58.36 | *** join/##pxe muh2000 (n=muh2000@unaffiliated/muh2000) |
| 19:19.47 | *** join/##pxe Xires (n=Xires@66-189-226-159.dhcp.wrbg.mo.charter.com) |
| 19:50.19 | *** join/##pxe whizter (i=whizter@dslb-088-077-020-033.pools.arcor-ip.net) |
| 19:50.22 | whizter | hi |
| 19:53.11 | whizter | how can i boot a memtest86+ image from network? got intel pxe 2.0 on my motherboard, a dhcp and tftp server |
| 19:54.24 | ScytheBlade1 | Read the wiki |
| 19:54.32 | ScytheBlade1 | It sets up PXE and uses memtest as the demo |
| 19:54.38 | ScytheBlade1 | Said wiki is linked in the topic |
| 19:54.49 | whizter | ok thx |
| 20:20.27 | *** join/##pxe copilot (i=copilot@70.142.205.16) |
| 20:29.59 | *** join/##pxe whizter_ (i=whizter@dslb-088-076-202-174.pools.arcor-ip.net) |
| 20:37.35 | *** join/##pxe muh2000_ (n=muh2000@unaffiliated/muh2000) |
| 20:47.27 | *** join/##pxe whizter_ (i=whizter@dslb-088-076-195-211.pools.arcor-ip.net) |
| 20:50.25 | whizter_ | I can't get it to work. if I try to boot from network, it says "TFTP Open Timeout", dhcp works fine. I'm using the haneWIN dhcp server (tftp also included), i configured it to use pxelinux.0, and inside pxelinux.cfg I added the memtest86 img, like in the wiki. |
| 20:51.57 | whizter_ | inside my server there's an option to specify a "boot filesize (in 512 byte blocks)" is this an important settingß |
| 20:52.26 | ScytheBlade1 | I'd recommend using a different TFTP server |
| 20:52.31 | whizter_ | why? |
| 20:52.43 | whizter_ | what's your recommendation on windows? the built-in one? |
| 20:52.50 | ScytheBlade1 | On windows server, yes actually |
| 20:52.59 | whizter_ | using xp pro here |
| 20:53.05 | *** join/##pxe copilot_ (i=copilot@70.142.205.16) |
| 20:53.23 | ScytheBlade1 | TFTP errors are caused by one of two things |
| 20:53.26 | ScytheBlade1 | 1) Crappy TFTP servers |
| 20:53.32 | ScytheBlade1 | 2) Buggy PXE NIC ROMs |
| 20:54.33 | whizter_ | it's an intel pxe 2.0 thing on my mainboard (using the onboard LAN) |
| 20:55.04 | ScytheBlade1 | So to update it, you'd need to update your BIOS |
| 20:55.18 | whizter_ | flashed it to the newest version today |
| 20:55.59 | ScytheBlade1 | Make sure that it's contacting the correct server (wireshark is your friend) |
| 20:56.03 | ScytheBlade1 | Failing that, check your firewalls |
| 20:56.09 | ScytheBlade1 | And failing that, get a new TFTP server |
| 20:56.22 | whizter_ | but in essence I only need to specify the filename on the tftp server, and the "next server ip", where tftp is running, right? |
| 20:56.47 | whizter_ | this server has lots of options, and I don't know most of them |
| 20:56.50 | ScytheBlade1 | The latter is optional |
| 20:56.54 | whizter_ | ok |
| 20:56.56 | ScytheBlade1 | If you set the next-server IP, it'll use that |
| 20:57.03 | ScytheBlade1 | If you don't, it'll use the IP of the DHCP server |
| 20:57.17 | ScytheBlade1 | afk a while though |
| 20:57.18 | whizter_ | ok that would be the same, but I read about some bugs |
| 20:58.09 | whizter_ | I'll try another tftp server now |
| 21:12.46 | *** join/##pxe whizter (i=whizter@dslb-088-076-194-119.pools.arcor-ip.net) |
| 21:19.30 | *** join/##pxe whizter (i=whizter@dslb-088-076-211-020.pools.arcor-ip.net) |
| 22:18.03 | *** join/##pxe muh2000 (n=muh2000@unaffiliated/muh2000) |
| 22:18.52 | *** join/##pxe muh2000_ (n=muh2000@unaffiliated/muh2000) |