If a normal PXE boot will suffice, then go to http://www.rom-o-matic.net/5.0.6/ and choose your NIC and Floppy bootable ROM image and follow the instructions for a wonderful PXE boot disk.
Jason On Wed, 2002-06-19 at 22:32, Jeremy Enos wrote: > Atish- > I think I may have seen something similar on the same cards before... I > had the same thoughts you did about replacing the initrd.gz and I tried > different dhcp clients and such... it didn't work. > I ended up replacing the kernel with a newer one that had a better driver > for the 3com card and everything worked smoothly. It was a very tough > problem because the driver appeared to be working (at least one direction), > so I didn't suspect it. > Now... if I just had the link to the site. When I was having trouble, it > was actually Sean Dague that gave me the link to find the extra kernels > available for SIS (user contributed, I think). Maybe one of the SIS folks > can chime in here? Otherwise, I'll keep searching. > > Jeremy > > At 06:55 PM 6/19/2002 -0400, Atish Chowdhury wrote: > >Hi all, > > > > I was trying oscar1.21rh72 atop RedHat 7.2. Things > >went well, till I needed my client to be booted. > >It could boot the kernel/initrd.gz all right (via PXE/ boot floppy) > >but dchlient failed to get any response back from the > >server (It could send the DHCPREQUESTS). > > > > The DHCP server was running fine, though. (I could use > >a different machine and a different dhcp client to get appropriate > >responses) I saw a previous posting on the mailing list, mentioning > >the same problem. I did make sure (as above) that the server > >is configured fine. > > > > My client node is a dual Athlon on a Tyan Thunder K7, using > >3COM's 3c59x for it's network interface. Does it pose any compatibility > >problem with the boot kernel ? ( I would rather like to believe that I am > >missing something :)) > > > > Has anyone come across this problem/know the solution ? > >Would really love to have some suggestions. > > > > On a related note, if I replace the supplied "initrd.gz" and > > "kernel" with custom ram disks (having some other working dhcp clients) > > and kernel, can I simply include the nodename.sh script in the ramdisk > > and pass control to it? Is it an acceptable workaround or does that > > script have dependencies on the ramdisk/kernel supplied with the > > distribution? > >'Appreciate some advice on this. > > > >-thanks in advance, > >Atish > > > > > > > >_________________________________________________________________ > >Chat with friends online, try MSN Messenger: http://messenger.msn.com > > > > > >---------------------------------------------------------------------------- > > Bringing you mounds of caffeinated joy > > >>> http://thinkgeek.com/sf <<< > > > >_______________________________________________ > >Oscar-users mailing list > >[EMAIL PROTECTED] > >https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > ------------------------------------------------------- > Bringing you mounds of caffeinated joy > >>> http://thinkgeek.com/sf <<< > > _______________________________________________ > Oscar-users mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/oscar-users ------------------------------------------------------- Bringing you mounds of caffeinated joy >>> http://thinkgeek.com/sf <<< _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
