View previous topic :: View next topic |
Author |
Message |
zooty n00b
Joined: 26 Jan 2003 Posts: 6
|
Posted: Sun May 18, 2003 3:40 am Post subject: My old lady and ltsp |
|
|
My wife is bugging me about her desktop.
Specs Dell P4 256K 128 MB Rambus Ram 3c905c-tx nic usb mouse dell quiet keyboard
Gentoo LTSP Server
Duron 1.3 (OCed to ~1450) 512 MB DDR intel nic (eepro100) MS intellimouse on WD 4.3 GB scsi drive
I boot up the ltsp client with a etherboot disk (5.0.9) it loads the kernel, gets a preliminary address and then when it goes to
"Running dhclient"
Hangs for a while and then kernel panic
Says that this is usually a problem with the dhclient-eth0.info, or incorrect drivers.
A couple of questions:
1. Where do i start looking for ways to fix this. I've already checked /etc/dhcpc/dhclient-eth0.info, /etc/dhcp/dhcpd.conf.
2. When linuxrc runs, it loads up a eepro100 driver. . . could this be a problem with the dchclient? And if so, how do I change the default behavior so that it loads whatever the host computer's floppy disk tells it to load?
Also, on the ltsp docs page, it lists (around #17) that this might be a problem with the NFS file system and no root directory in it. I've chect opt/ltsp/i386 and it has a full root directory. I recompiled my kernel down to NFS client and Server protocol 2.
Please help me so my old lady can finally use linux without having to commit to it if she doesn't want to. |
|
Back to top |
|
|
Kap n00b
Joined: 29 Aug 2002 Posts: 23 Location: Lima, Peru
|
Posted: Sun May 18, 2003 4:22 am Post subject: |
|
|
Quote: | 2. When linuxrc runs, it loads up a eepro100 driver. . . could this be a problem with the dchclient? And if so, how do I change the default behavior so that it loads whatever the host computer's floppy disk tells it to load? |
sure, this is a problem.
you have to have a kernel for the client, different from the one used for the server. I don't know the specifics of LTSP, but the dhcp server should point to kernel file; make sure it's an apropiate kernel.
you can also put a kernel on a floppy drive and boot from there. this kernel would have to either copy an initrd from the server or mount a root nfs directory. |
|
Back to top |
|
|
zooty n00b
Joined: 26 Jan 2003 Posts: 6
|
Posted: Sun May 18, 2003 4:40 am Post subject: |
|
|
Thanks for the info about #2. Do you know which file I need to edit to stop the host from accessing the server's ethernet module?
I've looked through my dhcp* and dhclient* *.conf files and found nothing yet that could indicate to me where the host is accessing this file. The ltsp kernel has a whole list of drivers and I emerged it, so I assumed that it was emerged with either support for ALL net modules available, or no net modules and that it dynamically loaded the module on boot up. . . |
|
Back to top |
|
|
zooty n00b
Joined: 26 Jan 2003 Posts: 6
|
Posted: Fri May 23, 2003 6:20 am Post subject: |
|
|
Alright. Figured out why it was loading eepro . . . the ltsp SERVER has detected the second NIC on my CLIENT. (the client setup had 2 nics, one built in, 3com and one extra intel) It now loads the proper driver and then requests that I find the root directory. I imagine that the kernel at least loads part of the way as the floppy would have no idea about the intel NIC in my comptuer. That would have to come from the server. I receive the initial ip address, and I imagine that i also would receive the second ip address. I just need to know where to look to set the proper root directory. Any help out there would be appreciated. |
|
Back to top |
|
|
|