[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Problems booting a 486DX4-100



On Mon, 30 Dec 2002 09:52:23 +0000, you wrote:

> Hello Henning,
> 
> Two things that may help.
> 
> Have you created an entry for this workstation in your dhcp.conf AND
> lts.conf files?

Both setup. Yes.

> Is the NIC a PCI nic?

Yes.

> If so you may have to create a custom image from Rom-O-Matic. 

Yes, tried the rtl8139 as well as the clone-rtl8139.
Both stops with the same errors on the screen and in the log:

> Dec 30 19:38:42 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:38:42 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0
> Dec 30 19:38:42 pruhest dhcpd: DHCPREQUEST for 192.168.0.2 (192.168.0.254) from 00:c0:df:06:80:11 via eth0
> Dec 30 19:38:42 pruhest dhcpd: DHCPACK on 192.168.0.2 to 00:c0:df:06:80:11 via eth0

>From here it goes wron on the screen

> Dec 30 19:38:50 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:38:50 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0
> Dec 30 19:38:53 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:38:53 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:01 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:01 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:18 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:18 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:35 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:35 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:48 pruhest dhcpd: DHCPDISCOVER from 00:c0:df:06:80:11 via eth0
> Dec 30 19:39:48 pruhest dhcpd: DHCPOFFER on 192.168.0.2 to 00:c0:df:06:80:11 via eth0

And here the Kernel panic message show on the client.

> Older
> machines didn't implement PCI very well, and you have to force this in
> the rom image. 
> 
> I found this out when working on some older Compaq Deskpros (P133). So
> if they weren't implementing PCI correctly I suspect the 486 won't
> either.

To me it looks as if the problem is not in the boot-image, but in the
kernel sent to the client during boot, as it startup ok, but fails
later when trying to get it to communcate with the NIC.

But even though, it dhclient gives the correct info about NIC-type /
mac-addr etc, but is not able to get the resonse form the server. The
clients states that its a RTL8139, but the actual chip says RTL8139C,
but I guess that's not a problem ;-)

> I've covered this on list several times before. A google search on PCI
> and K12LTSP will probably dig up the relevant messages.

I haven't been able to find anything, sorry.

Do you have any hints on what should/could be done?


-- 
Venlig hilsen / Best regards
	Henning

 _H_P_C_o_n_s_u_l_t_    http://www.hpc.dk
 Skoletoften 9, Blans   http://www.turnsys.dk
 DK - 6400 Soenderborg





[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]