Ramon Ramirez-Linan wrote: > Hi Patrick > > Sorry to contact you out of the list. > > Were you ever able to fix that issue? > > I am having exactly the same problem. > > http://www.mail-archive.com/oscar-users@lists.sourceforge.net/msg08476.html >
I did overcome that after a while. The little kernel that is used by default (I can't recall the name right now) didn't have drivers for my network interface. Thus there was no eth0 device for the second DHCP discover. The cure was to use the UYOK option. I was too scared to do this for a long time, but it turned out to be easier than I thought. By default it uses the running kernel on the Oscar server. Since my clients have the same architecture, it worked with no tweaking. Your mileage may vary. It looks to me as if everyone should use UYOK unless they have the old hardware supported by the default kernel. In the early stages I did a lot of tweaking of the contents of the files in /tftboot/pxelinux.cfg. In the end none of that was necessary; Oscar got it right. There have been some vague warnings about Centos 5.5 causing trouble with Oscar 5.1b2. I didn't see any such problems, although I did unalias rm, cp and mv in /root/.bashrc early in my struggle. By the way, I never could get my setup to pass the final installation test. After a while I gave up and let it run. So far so good. ------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd _______________________________________________ Oscar-users mailing list Oscar-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oscar-users
