IRC chat logs for #ltsp on irc.freenode.net (webchat)


Channel log from 12 March 2020   (all times are UTC)

00:00eu^811724110dynu has left IRC (eu^811724110dynu!51ac290a@81.172.41.10.dyn.user.ono.com, Remote host closed the connection)
00:29statler has left IRC (statler!~Georg@p5B30E384.dip0.t-ipconnect.de, Remote host closed the connection)
01:06GodFather__ has left IRC (GodFather__!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Quit: Ex-Chat)
01:07GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
01:24markit has left IRC (markit!~marco@mail.ammdomus.it, )
06:01statler has joined IRC (statler!~Georg@p5B30E384.dip0.t-ipconnect.de)
07:03woernie has joined IRC (woernie!~werner@pD9E8BE9E.dip0.t-ipconnect.de)
07:51vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)
08:40ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr)
09:00gdi2k has joined IRC (gdi2k!~gdi2k@58.69.160.27)
09:14
<meo>
alkisg: how would I maintain a separate kernel version over the same image for a set of clients?
09:15
<alkisg>
meo: does that other kernel receive updates?
09:16
<meo>
alkisg: no, the problem I described earlier (some clients fail mid-boot because they cant initialize the NFS) is specific to some cards in kernel 5.3.x, but works ok under 5.0.0
09:16
I will trace down exactly which cards and kernel versions but now I'd like to group the clients
09:17
<alkisg>
First of all you'll have both kernels installed. Then, you'd copy the second kernel to a different tftp dir, e.g. /srv/tftp/ltsp/special-kernel/vmlinuz,initrd.img
09:18
Then you'd symlink /srv/ltsp/images/special-kernel.img to x86_64.img
09:18
Then you'd put special KERNEL_PARAMETERS for these clients, and run ltsp ipxe
09:18
Hmm not special KERNEL_PARAMETERS, sorry, special DEFAULT_IMAGE
09:18GodFather has left IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net, Read error: Connection reset by peer)
09:19GodFather has joined IRC (GodFather!~rcc@wsip-66-210-242-210.ph.ph.cox.net)
09:19
<alkisg>
(or maybe it's just IMAGE, not DEFAULT_IMAGE, need to look it up)
09:20
It's DEFAULT_IMAGE
09:21
It's also possible to automate the "copy the second kernel" by using the KERNEL_INITRD parameter, but it's not a big deal if it's not regularly updated
09:22
<meo>
let me dig in, I remember looking in squashfs images yesterday and seeing several kernels
09:24
<alkisg>
If you need professional support over VNC to finish this in a few minutes... you know the way :)
09:30adrianor1 has joined IRC (adrianor1!~adrianorg@177.18.49.49)
09:31
<meo>
it's another physical site, I need to figure it out first
09:34adrianorg has left IRC (adrianorg!~adrianorg@177.156.231.235, Ping timeout: 265 seconds)
09:51statler has left IRC (statler!~Georg@p5B30E384.dip0.t-ipconnect.de, Remote host closed the connection)
10:04hej has left IRC (hej!~erik@69.234.36.19, Ping timeout: 265 seconds)
10:07Teridon has joined IRC (Teridon!~Teridon@dragon.teridon.com)
10:36
<meo>
alkisg: I figured out the configuration, doing a test right now
10:38
<alkisg>
Great
10:41
<meo>
huh, ipxe cant load the new image from tftp, do I need to restart it or something
10:42
oh
10:42
im stupid nvm
10:42
i just put the image to /srv/ltsp/images and expected it to work..
10:44statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
10:55
<meo>
alkisg: okay it works nicely, just need to run ltsp kernel too
10:55markit has joined IRC (markit!~marco@mail.ammdomus.it)
10:55
<meo>
I suspect in fact that I could use the same base image and just the separate kernel configured, because this is clearly a kernel problem
11:00
ok more specifically this is a rtl8111 problem introduced in 5.3
11:23
<alkisg>
meo: in my instructions above, I told you to use a symlink, i.e. the exact same image
11:23
Did we miscommunicate somehow?
11:26
<meo>
alkisg: I made a copy of the image because the working one was the .old one and I didnt want to lose it on next ltsp image
11:26
<alkisg>
You didn't need to run ltsp image at all..
11:26
But anyways, now you only maintain one image, right?
11:26
<meo>
alkisg: I know that now, this is what happens when I read too fast
11:26
alkisg: I will, now that I figured out how the kernel selection works
11:27
<alkisg>
np, as long as the best solution is found, it's ok to have a few wrong steps in the road ahead :)
11:27
<meo>
but really what I need to do here is to rebuild with realtek proprietary drivers
11:27
<alkisg>
Eh, not sure I'd trust realtek more than the kernel maintainers :D
11:27
I've read their code... :D
11:28
<meo>
the very reason I started down this road is because other realtek cards I have in that setup (non-8111) have a flaky connectivity under 5.0.0 and some of them are forced into 100Mbps mode
11:28
bear in mind these workstations are easy 10 year old
11:29* alkisg has only seen forced 100 mbps mode when there were bad cabling issues
11:29
<alkisg>
E.g. realtek there claimed to work in gigabit, and produced lots and lots of errors,
11:29
while intel there synced in 100 mbps and worked fine
11:29
<meo>
there *are* cabling issues, but in this case it's about the driver power management, I made a fresh cable by hand and ran it directly to the switch - same thing
11:29
<alkisg>
Then I fixed the wall socket and everything was fine with any adapter
11:30
OK
11:34
<markit>
alkisg: hi, private msg for you :)
11:34
<alkisg>
Hi markit, reading...
11:39section1 has joined IRC (section1!~section1@vps-1722311-x.dattaweb.com)
11:49Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
11:54Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
11:55statler has left IRC (statler!~Georg@gwrz.lohn24.de, Ping timeout: 265 seconds)
11:56Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)
12:06statler has joined IRC (statler!~Georg@gwrz.lohn24.de)
13:14markit has left IRC (markit!~marco@mail.ammdomus.it, )
14:18rwmarch has joined IRC (rwmarch!2d48d925@45.72.217.37)
17:10rwmarch has left IRC (rwmarch!2d48d925@45.72.217.37, Remote host closed the connection)
18:27vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)
19:25section1 has left IRC (section1!~section1@vps-1722311-x.dattaweb.com, Quit: Leaving)
19:55eu^host-78-144-1 has joined IRC (eu^host-78-144-1!4e908b24@host-78-144-139-36.as13285.net)
19:58eu^host-78-144-1 has left IRC (eu^host-78-144-1!4e908b24@host-78-144-139-36.as13285.net, Remote host closed the connection)
20:27adrianor1 has left IRC (adrianor1!~adrianorg@177.18.49.49, Ping timeout: 255 seconds)
20:28adrianorg has joined IRC (adrianorg!~adrianorg@177.18.49.49)
20:37jgee7 has joined IRC (jgee7!~jgee@190.159.118.121)
20:39jgee has left IRC (jgee!~jgee@190.159.118.121, Ping timeout: 255 seconds)
20:44jgee7 has left IRC (jgee7!~jgee@190.159.118.121, Ping timeout: 256 seconds)
20:51statler has left IRC (statler!~Georg@gwrz.lohn24.de, Remote host closed the connection)
20:55Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)
21:13statler has joined IRC (statler!~Georg@p5B30E384.dip0.t-ipconnect.de)
22:40woernie has left IRC (woernie!~werner@pD9E8BE9E.dip0.t-ipconnect.de, Remote host closed the connection)