Windows Server mit RIS und Knoppix

Hi,
I have a windows server with RIS (remote installation service)
I have four clients with 3 Com NICs (3c905)

I can boot over PXE to my RIS - Install Menu and then choos betwenn XP or Knoppix.

I used http://syslinux.zytor.com/ris.php
to get the bootloader (pxeloader)
but my Knoppix Image failed to start!!
It starts booting the kernel but then ends up with:

Welcome to the KNOPPIX Terminal Client!
Loading network device module(s)
found network device(s) handled by 00_crc32.o
found network device(s) handled by 00_mii.o
found network device(s) handled by 3c59x.o

/static/ifconfig: error while loading shared libraries: libc.so.6: connot open shared object file: no such file or directory
DHCP Broadcasting for IP address (1) ... pump: errir while loading shared libraries: libresolv.so.2: cannot oben shared object ...
No answer from network.
DHCP.........................................(2) ............
No answer from network
DHCp.......................................(3).... ........
no answer from network
Can't NFSmount KNOPPIX Filesystem, sorry
....

modules loaded:
3c59x
00_mii
00_crc32
nfs
lockd
sunrpc
af_packet


thx for help
with kind regards marko

Similar problem here - except I'm not using Windows RIS but rather Tftp32 and a trial version of nfsAxe.

Although my pxelinux.cfg/... file specifies both "nodhcp" and "ip= .. gateway= .. netmask= .. dns=.." and although I am using the vmlinuz & miniroot.gz files from Knoppix's own terminal server, it still appears to be attempting to DHCP. Seriously, WTF? (Instructions for PXE-booting gleamed from Here.)

These DHCP attempts are very very rapid - perhaps instant. Tftpd32 doesn't log any DHCP attempts, despite initially succeeding in issuing an address to the PXE client in the NIC and dumping vmlinuz & miniroot.gz into its RAM.

In the startup I get:
Loading network device module(s)
Found network device(s) handled by 3c59x.ko.
Found network device(s) handled by 8139too.ko.
Found network device(s) handled by eepro100.ko.
Found network device(s) handled by sis900.ko.
Found network device(s) handled by tulip.ko.

All these appear as you would expect in the "Modules loaded:" at the end of the DHCP attempts.

My client machine - which successfully boots over PXE with the CD as its main data source with full network access - is running a Via EPIA5000 motherboard with an onboard VIA NIC with integrated PXE loader.

Any help gratefully appreciated - please bear in mind I have a 'doze PC and a PC with no HDD, let alone an installation of Linux =)

Yeah.
Great.
Thanks a lot.
Would it really have been that difficult for someone to tell me I need to install a network device module for my specific NIC?? I mean, if it says "Found betwork device(s) handled by ...." you tend to assume that it has found network devices and loaded the modules for them.

Additionally, "The requested URL /wiki/Special:Search was not found on this server." So currently I'm a bit screwed.

Thanks for ALL your generous help and all the time you clearly spent trying to get this up & running.

Quote:

---

Originally Posted by madkat

Yeah.
Great.
Thanks a lot.
Would it really have been that difficult for someone to tell me I need to install a network device module for my specific NIC?? I mean, if it says "Found betwork device(s) handled by ...." you tend to assume that it has found network devices and loaded the modules for them.

Additionally, "The requested URL /wiki/Special:Search was not found on this server." So currently I'm a bit screwed.

Thanks for ALL your generous help and all the time you clearly spent trying to get this up & running.

---

Who are you arguing with? It looks like you are having a one way conversation.

That was my point!

Quote:

---

Originally Posted by madkat

That was my point!

---

Huh? You have some problems with a netboot system then in frustration create a one way argument?

Color me confused. If its any consolation, I have done a netboot extactly twice. The first time it failed. The second time it worked.

There are threads detailing network device modules.
Presumably people who post these threads, and respond to them, must be aware that what was described is a symptom of the requirement of a non-standard device module.
Presumably they must also read this thread, but for whatever reason have decided not to be helpful.
It's not an argument, and it's with the people that I'm frustrated rather than the software.

I'm sure others must have created netboot systems and failed the first time, then made it work the second time. I'm sure others must have seen the exact same messages. So why do they feel they are unable to lend a hand to others?