IRC chat logs for #ltsp on (webchat)

Channel log from 13 May 2022   (all times are UTC)

00:58lucascastro has joined IRC (lucascastro!
01:16agrosant has left IRC (agrosant!, Quit: Leaving)
05:17ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:16BrunoBinet[m] has joined IRC (BrunoBinet[m]!~bbinetmat@2001:470:69fc:105::68c6)
11:41ABIXadamjurkiewi has joined IRC (ABIXadamjurkiewi!~adamjurki@2001:470:69fc:105::f1a6)
12:28oh207 has joined IRC (oh207!~oh207@2600:1017:b4ab:baa9:e88f:455a:2786:cc66)
12:42oh207 has left IRC (oh207!~oh207@2600:1017:b4ab:baa9:e88f:455a:2786:cc66, Ping timeout: 240 seconds)
12:42oh207_ has joined IRC (oh207_!
13:00oh207 has joined IRC (oh207!
13:00oh207_ has left IRC (oh207_!, Ping timeout: 240 seconds)
13:02oh207 has left IRC (oh207!, Client Quit)
13:03oh207 has joined IRC (oh207!
13:05oh207 has left IRC (oh207!, Client Quit)
13:06oh207 has joined IRC (oh207!
13:14oh207 has left IRC (oh207!, Ping timeout: 240 seconds)
13:14oh207 has joined IRC (oh207!
13:17lucascastro has left IRC (lucascastro!, Ping timeout: 248 seconds)
13:19* ABIXadamjurkiewi uploaded an image: (3603KiB) < >
Hi, I have strange situation. Sometimes (not always, not the same computer) - it doen NOT start from Wake On Lan.
When I power off the machine, then power on, it starts without problems.
The network is simple - one router (DHCPd), one dubm switch 24 ports...
Maybe someone will have a idea, what could I check?
The picture is it from succesful wol boot? I had some months ago machines with bios power setting S4 deep enabled that prevented wol. Check the bios/uefi Power and network and startup settings in the machines
14:25woernie has left IRC (woernie!, Ping timeout: 260 seconds)
With machines/manufacturing manual
14:45woernie has joined IRC (woernie!
15:01woernie has left IRC (woernie!, Ping timeout: 248 seconds)
It is from unsuccessful - it is looks like no ip was given from dhcpd server to this machine... but this maake no sense...
I hade restart dhcpd server to make sure that there is a free ip pool. And it was the same.. sometimes some machine won't up.
The S4 is a good idea - I will check it in next week
15:45lucascastro has joined IRC (lucascastro!
15:54vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40)
16:09lucascastro has left IRC (lucascastro!, Ping timeout: 260 seconds)
16:51lucascastro has joined IRC (lucascastro!
17:27lucascastro has left IRC (lucascastro!, Remote host closed the connection)
Wake on lan is just for The server admin to send Power on remotely. If The magic Packer fails to reach client then it won't Power on at all. if there is no network or no IP offered like in the picture then it's a network issue or some other issue not related to wake on lan. Troubleshoot The network or DHCP server issue first separate from The wake on lan issue. I think The wake on lan or bios Power setting won't resolve anything to the
error in That photo.
17:43ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
17:51ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
18:28lucascastro has joined IRC (lucascastro!
18:31lucascastro has left IRC (lucascastro!, Read error: Connection reset by peer)
18:33lucascastro has joined IRC (lucascastro!
18:38lucascastro has left IRC (lucascastro!, Ping timeout: 240 seconds)
19:02lucascastro has joined IRC (lucascastro!
I would start tailing the logs on the DHCP server when the faulty client is booting to see what the server sees
19:22fottsia[m] has joined IRC (fottsia[m]!~fottsiama@2001:470:69fc:105::48bb)
I have to real reason for thinking so, but I have had hardware misinitialize itself on power-on
sometimes upgrading the firmware has fixed it
On an Intel nuc I recently had to disable ASPM, otherwise my harddrive got randomly corrupted on shutdown ¯\_ (ツ)_/¯
anyway, it's not an LTSP issue if it happens randomly
You are right updating net, audio, video controller firmware and disabling/enabling varied Power settings in uefi control can resolve random network issues. It's complicated today buyin computer
ABIX adam.jurkiewicz: you may try to overwrite /srv/tftp/ltsp/undionly.kpxe with
The default, undionly.kpxe, is using the BIOS initialization; while ipxe.pxe is doing it own initialization; some times better, some times worse; check and see
20:15ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
22:02oh207 has left IRC (oh207!, Ping timeout: 248 seconds)
23:25lucascastro has left IRC (lucascastro!, Ping timeout: 252 seconds)
23:38lucascastro has joined IRC (lucascastro!
23:52lucascastro has left IRC (lucascastro!, Ping timeout: 248 seconds)