On Tue, 15 Jan 2002, [EMAIL PROTECTED] wrote:
> Andy,
>
> the dhcpd.info file is written by the dhcp CLIENT that is
> running on the workstation, as part of the initrd.
>
> You can grab the ltsp_initrd_kit and look in /linuxrc to
> see where that all begins.
>
> The lack of the dhcpcd-eth0.info file indicates that the
> dhcp reply probably wasn't received from the dhcp server.
>
> It could be that the network interface wasn't configured
> properly, once the NIC module was loaded. It would
> be interesting to run tcpdump and watch that indeed
> you see the dhcpd request/reply take place, where the workstation
> gets its IP address and the name of the kernel to download.
> (which is obviously happening). Then, the tftp of
> the kernel, then another dhcp request/reply should take
> place.
You are, of course, right.
I am doing this for a Compaq Deskpro 575, that has an onboard NIC
AMD 79c970, that the pcnet32 driver thinks it supports but does not.
I therefore added in a 3c509 card, and added (to *my* DHCP server)
the DHCP server option option-129 below.
host ws004 {
hardware ethernet 00:60:97:1a:31:3d;
fixed-address 192.168.0.4;
filename "/lts/vmlinuz-2.4.9-ltsp-1";
option option-128 e4:45:74:68:00:00; #This is NOT a MAC address
option option-129 "NIC=3c509";
}
What is happening is that the kernel boots (via rom-o-matic 3c509 boot
floppy), finds the onboard card, and fails to get a DHCP reply.
I went into the Compaq BIOS, and disabled the device, but the
Linux kernel PCI probe is too clever for that ..
pcnet32_probe_pci: found device xx.xx
I disabled interrupts, put the card at a funny address .. to no avail.
So, my question now - can I pass option-129 from a Microsoft DHCP server ?
I think not, as my friendly WinNT sysadmin can only set global
options, nothing specific on a per MAC address basis.
I could pull pcnet32 support from the boot kernel, but that would
defeat the object of having a building-wide ltsp setup ..
Thanks for your help.
Cheers, Andy!
> On Tue, 15 Jan 2002, Andy Rabagliati wrote:
>
> > Folks,
> >
> > I have ltsp 2.09pre4 installed.
> >
> > I am aware it is not the latest one, but the changelog does not
> > appear to address my issue - perhaps you can help.
> >
> > The system works just dandy when my NFS server is the same machine
> > as my DHCP server. I do this with a dedicated ethernet card on my server.
> >
> > However, I wish to spread the gospel further afield :-)
> >
> > Our building has a single LAN environment, with almost all machines
> > being of the Windows variety ..
> >
> > In particular, the DHCP server for the LAN is WindowsNT. I have worked
> > with the Windows sysadmin, and have successfully arranged their server
> > to hand off to mine for the bootp requests - yaaaay.
> >
> > My client boots, gets an IP from WinNT, gets the bootp server (and filename ?)
> > from WinNT, and I can see the bootp request come in on my machine,
> > a kernel served, booted ..
> >
> > blah blah
> > Running /linuxrc
> > ..
> > Running dhclient
> >
> > ERROR! No dhcpcd-eth0.info file. Could be a problem with DHCP.
> >
> > Kernel panic:
> >
> > Investigations show that dhcpcd-eth0.info is written by the DHCP server,
> > which is elsewhere entirely.
> >
> > Thoughts ? Resolution ? Will upgrading solve my problem ?
> >
> > Which script should I be looking at ?
> >
> > Cheers, Andy!
> >
> >
> > _____________________________________________________________________
> > Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> > For additional LTSP help, try #ltsp channel on irc.openprojects.net
> >
>
>
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.openprojects.net
>
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net