Hi all,

Sorry again for posting off-topic.

I have two machines: one with an Intel eepro100 and another with tg3
(don't know the exact cards, these are the linux drivers that work
with them). I want both to boot with:
PXE -> something -> linux
Up until now, "something" was pxegrub, which worked very well for me.
But it doesn't have a driver for the tg3. So I tried instead pxelinux.
My initrd is busybox-based, and I use its udhcpc. When booting with
pxegrub, it works well. With pxelinux (I tried on both machines), it
starts well, including running /usr/share/udhcpc/default.script with
the parameter "deconfig", sending a discover, receiving an offer, then
sending a request, receiving an ack, but on the second time it tries
to run the default.script (to config the iface), execve fails, with the
message:
"script /usr/share/udhcpc/default.script failed: Bad address"
I ran it manually with strace, and indeed execve fails with EFAULT.
The very same initrd works with pxegrub (on the eepro100 machine).
Is it possible that pxelinux somehow does bad things to linux's memory
initialization or something like that?
Versions:
linux 2.4.25 (also tried 2.4.24), vanilla + few patches (i2c 2.8.4,
  lm-sensors 2.8.4, linux-ntfs 2.1.6) compiled with gcc 2.95.3
busybox 1.00-pre5 (I know there's already pre8, will try)
pxelinux from syslinux 2.08 (also tried 1.62 which I had compiled)

I can send the kernel config if it can help. I can also try vanilla
kernel with no patches (none of them essential), but I really don't
think it's relevant - with pxegrub this kernel works for me on more
than 100 machines.
I know it sounds as a pxelinux bug, and that I should post there, but
I used to think that once linux is taking control of the machine, it
initializes it to some clean state, irrelevant of the bootloader.
Also, I naturally hope it will be a busybox bug, because it will be
much easier to fix. I have no idea how to even start thinking about
fixing a bug in pxelinux (an 2600+ lines assembly program, in case you
didn't know).
Any ideas?
-- 
Didi


=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to