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


Channel log from 2 December 2022   (all times are UTC)

01:50vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
03:14ltspbot has joined IRC (ltspbot!~supybot@devs.ts.sch.gr)
05:24quinox has left IRC (quinox!~quinox@ghost.qtea.nl, Quit: WeeChat 3.6)
05:28quinox has joined IRC (quinox!~quinox@ghost.qtea.nl)
07:04woernie has joined IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de)
07:22ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:32
<alkisg1>
Yey, nvme disks! ltsp image / => 2.5 minutes :)
12:59ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
13:17ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
13:32
<DouglasGiovaniOe>
hello
13:35
alkisg: Please, can you help me to try the process in the epopets, now can operate here. If you be free now
13:35
I am here
14:34
<alkisg1>
Douglas Giovani Oechsler: (1) the client has a black screen now? (2) can you see it in epoptes?
14:36
<DouglasGiovaniOe>
alkisg1: inside epopets I can login the system, only not mini pc, the boot process show at screen, but no login screen
14:37
<alkisg1>
Douglas Giovani Oechsler: can you vnc to me so that I see? Because I can't really understand what you are saying
14:37
x11vnc -connect alkisg.ltsp.org
14:37
And tell me the name of the mini pc, e.g. pc01
14:39
<DouglasGiovaniOe>
wait please
14:40
<alkisg1>
OK, note that I have about 10 minutes currently, I'll go offline after that
14:42
<DouglasGiovaniOe>
right ok
14:45
<alkisg1> "x11vnc -connect alkisg.ltsp.org" <- inside epopets?
14:45
<alkisg1>
From a graphical terminal on your server
14:45
Or this one from epoptes:
14:45
!vnc-edide
14:45
<ltspbot>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
14:49
<DouglasGiovaniOe>
ltsp9
14:50
the ltsp9 was with screen error
14:50
<alkisg1>
Ah
14:51
In ltsp9, tatiana has logged in
14:51
How did they log in if the screen had an error?
14:51
<DouglasGiovaniOe>
logged by epopets
14:52
<alkisg1>
[ 3218.396553] RIP: 0010:gen9_disable_dc_states+0x262/0x280 [i915]
14:52
[ 3218.396698] Code: 44 0f b6 e8 4c 8b 77 50 4d 85 f6 74 24 e8 66 9b e9 e5 41 89 d8 44 89 e9 4c 89 f2 48 89 c6 48 c7 c7 c8 e2 0d c1 e8 96 9e 30 e6 <0f> 0b e9 4e fe ff ff 4c 8b 37 eb d7 4c 8b 2f eb 97 e8 58 e1 3a e6
14:52
I see a xorg crash there
14:52
It's probably an issue with the graphics adapter
14:52
I need to leave now, I'll be back in 30 minutes if you want to wait
14:52
<DouglasGiovaniOe>
ok
14:53
I need to go out in 10 min to lunch time
14:53
back 1 hour
14:54
can I call you?
14:57
or no problem if you want let connected there, thank you
15:22
<alkisg1>
J4125 CPU @ 2.00GH, 8 GB RAM, 5.15.0-56-generic, 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 605 [8086:3185] (rev 06)
15:22
https://gitlab.freedesktop.org/drm/intel/-/issues/7302, i915.force_probe=56a5
15:23
https://termbin.com/qlh4 https://termbin.com/diyww
15:24
https://termbin.com/u7ebd
15:29
Douglas Giovani Oechsler: so with this client currently you are able to work from epoptes/vnc but in the local display you see a black screen, correct?
15:29
When you come back ping me
15:56
<joris>
ok alkisg1 or anyone else... to test I copied x86_64.img from the server to the hd of the client. Mate was already installed on the client, so I modified grub to boot the image... It boots, but something is wrong. It doesn't start desktop session and I even cannot login on tty
15:57
Not sure where to start to troubleshoot. Is local cache somewhere documented?
15:57
<alkisg1>
It needs ltsp.img to boot in ltsp mode
15:57
No I don't think it's documented in detail anywhere
15:58
<joris>
ah ok thanks so I just copy ltsp.img from the server also on the client?
15:58
<alkisg1>
Here's how my liveusb loads ltsp images: https://github.com/alkisg/liveusb/blob/main/grub.cfg#L168
15:59
<joris>
oh ok cool!
15:59
<alkisg1>
Copy/adjust these lines there
16:00RolandStiebel[m] has left IRC (RolandStiebel[m]!~stiebelma@2001:470:69fc:105::1:b67e, Quit: You have been kicked for being idle)
16:00
<joris>
very helpful!
16:15
<DouglasGiovaniOe>
<alkisg1> "Douglas Giovani Oechsler: so..." <- Yes, exactly
16:15
I amback
16:15
I am back
16:16
<alkisg1>
Douglas Giovani Oechsler: reconnect with vnc as the connection failed
16:16
!vnc-edide
16:16
<ltspbot>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
16:16
<DouglasGiovaniOe>
yes
16:20
<alkisg1>
Douglas Giovani Oechsler: reboot ltsp9 and see if the problem happens again now
16:20
I configured it to boot with the older -53 kernel
16:20
You're saying that this problem started after an update, right?
16:21
<DouglasGiovaniOe>
yes, correct
16:21
<alkisg1>
reboot ltsp9 and see if the problem happens again now
16:22
<DouglasGiovaniOe>
one minute
16:22oh207 has joined IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net)
16:23oh207 has left IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net, Client Quit)
16:24
<DouglasGiovaniOe>
Tatiana is starting mini pc
16:25oh207 has joined IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net)
16:28
<DouglasGiovaniOe>
no screen
16:30
<alkisg1>
[ 275.829058] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] ERROR [CONNECTOR:155:HDMI-A-1] commit wait timed out
16:31
<DouglasGiovaniOe>
maybe after upgrade system?
16:32
<alkisg1>
It sounds like a graphics drivers or kernel issue, completely unrelated to ltsp
16:32
Either that, or a sudden hardware problem :)
16:32woernie has left IRC (woernie!~werner@p5b2962ea.dip0.t-ipconnect.de, Remote host closed the connection)
16:32
<DouglasGiovaniOe>
humm
16:32
<alkisg1>
A last try with the previous image; if it doesn't work with that, then you should install a local operating system and troubleshoot there without ltsp
16:33
<DouglasGiovaniOe>
ahhh yes
16:34
<alkisg1>
It works now?
16:35
<DouglasGiovaniOe>
let me see
16:37vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40)
16:38
<DouglasGiovaniOe>
let me do the question: Can be server hardware problem or mini pc hardware?
16:38
<alkisg1>
Did it work now? Someone rebooted it
16:38
<DouglasGiovaniOe>
no screen
16:39
so someone reboot it
16:39
<alkisg1>
Now it didn't have any errors in the logs
16:39
Are you sure there was no screen now?
16:39
Try to boot it again and see
16:41
Now it has errors in the logs
16:41
And someone rebooted it again :)
16:42
The server hardware is fine
16:42
<DouglasGiovaniOe>
yes after you ask to reboot
16:43
no screen again
16:46
<alkisg1>
Do you have another PC with the same hardware?
16:46
<DouglasGiovaniOe>
no
16:47
<alkisg1>
OK let's wait for ltsp image to finish, and test with the newer kernel. Ping me when ltsp image finishes.
16:48
<DouglasGiovaniOe>
right
16:56
alkisg: finished
17:02
<alkisg1>
Douglas Giovani Oechsler: I already rebooted the clent. Does it work now?
17:05
<DouglasGiovaniOe>
wait
17:06
no screen again
17:06
<alkisg1>
Someone logged in
17:06
Did you use epoptes to log in?
17:07
also someone rebooted it before we could see the logs
17:07
<DouglasGiovaniOe>
have screen epopets up ask login
17:07
I think you ask to login
17:08
<alkisg1>
I asked "does it work now?"
17:08
If you use epoptes to control the client we don't learn anything
17:08
The point is to see if the screen is blank or not
17:08
Also do not reboot it because we can't see the logs. I'll reboot it when needed.
17:08
<DouglasGiovaniOe>
the screen is black
17:09
no reeboot now
17:10
so, can control it please, I will only see and do what do you want
17:11
<alkisg1>
Now I'm testing to disable the intel driver and use vesa
17:11
<DouglasGiovaniOe>
right
17:14
<alkisg1>
Now ask them if the screen is black
17:14
<DouglasGiovaniOe>
yes get screeen
17:14
<alkisg1>
OK so the problem is the graphics driver
17:15* DouglasGiovaniOe uploaded an image: (143KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/QbDInOncokHLFWUrgKXfznSj/WhatsApp%20Image%202022-12-02%20at%2014.14.17.jpeg >
17:15
<alkisg1>
It is not related to LTSP. You can use it with the VESA driver like it is now. To solve it properly, you need to file a bug report or hire a technicial to troubleshoot the graphics issues for you
17:15
<DouglasGiovaniOe>
the client
17:15
<alkisg1>
Now it will be slower than normal
17:16
<DouglasGiovaniOe>
and not make upgrade?
17:17
<alkisg1>
You can upgrade normally. I made the change in ltsp.conf, it's not affected by upgrades.
17:19
<DouglasGiovaniOe>
can be not good driver video onboard on server?
17:20
<alkisg1>
No
17:20
This is about the graphics driver for the pc09 client. The server is not involved in this.
17:22
<DouglasGiovaniOe>
Alkis
17:22
now other client stay without screen! Jesus
17:23
or ask to guy to restart
17:23
<alkisg1>
Which other client? Yes, tell them to restart that other client.
17:23
<DouglasGiovaniOe>
right
17:23
wait please
17:23
alkisg1: owww, bad product so
17:24
<alkisg1>
Bad linux. Not bad hardware.
17:25
<DouglasGiovaniOe>
the other client reboot but not screen
17:25
alkisg1: what do you think the best Linux for Ltsp?
17:26
<alkisg1>
There is only one Linux. I'm talking about the kernel, not the distribution.
17:26
The Linux kernel 5.15.0.50 worked for you, then the next kernels didn't work for you.
17:28
<DouglasGiovaniOe>
so the way is not update kernel when all works well
17:29
<alkisg1>
No, because then you'll get security problems and you'll get hacked
17:33
<DouglasGiovaniOe>
alkisg: can you see about the other client, now other no screen
17:33
<alkisg1>
Douglas Giovani Oechsler: vnc got disconnected, do connect again
17:33
!vnc-edide
17:33
<ltspbot>
vnc-edide: To share your screen with me, open Epoptes → Help menu → Remote support → Host: srv1-dide.ioa.sch.gr, and click the Connect button
17:33
<DouglasGiovaniOe>
now other problems with pc09 no click mouse amd pc07 no screen
17:34
<alkisg1>
[ 89.553870] snd_hda_intel 0000:00:0e.0: Cannot probe codecs, giving up
17:34
[ 100.530748] UBSAN: shift-out-of-bounds in /build/linux-hwe-5.15-jemPrJ/linux-hwe-5.15-5.15.0/drivers/net/wireless/broadcom/brcm80211/brcmsmac/phy/phy_cmn.c:2511:27
17:37
Douglas Giovani Oechsler: are you saying that the screen in ltsp7 is black now?
17:37
<DouglasGiovaniOe>
yes
17:38
<alkisg1>
How many clients do you have in total?
17:38
<DouglasGiovaniOe>
only 2
17:38
<alkisg1>
You're using LTSP for just 2 clients?
17:38
<DouglasGiovaniOe>
yes
17:39
<alkisg1>
I thought you were mentioning a lot of vlans and subnets on github
17:40
<DouglasGiovaniOe>
alkisg1: This place with 2 clients is sister's office
17:40
<alkisg1>
Is the screen black now too?
17:40
<DouglasGiovaniOe>
The other place in on the city hall
17:41
where I work
17:41
<alkisg1>
OK! Does ltsp7 have a black screen now?
17:42
<DouglasGiovaniOe>
alkisg1: no
17:42
<alkisg1>
OK, let's reboot both PCs and make sure they both work now
17:42
Then don't touch them for a while :D
17:43
<DouglasGiovaniOe>
only show boot client but not screen login
17:43
<alkisg1>
I put your previous image back
17:43
So if it worked 5 hours ago and it's not working now, I don't know what it means
17:44
-rw-r--r-- 1 root root 5007896576 nov 30 13:42 x86_64.img
17:44
The image is 2 days old, it's the one you had
17:47
<DouglasGiovaniOe>
the old image works perfect for pc07 but not pc09, so I am trying to do work, but, the true is after update and upgrade xubuntu starts erros
17:47
<alkisg1>
Now we have the old image and you say that pc07 doesn't work
17:47
Anyway. All these issues are not related to LTSP. I put your old image back, so it's like you had it yesterday without changes from me.
17:48
I suggest that you do not use LTSP for these 2 clients, because they have many problems, and LTSP is making things difficult for you.
17:48
If you install Ubuntu in a local disk without LTSP, you'll be able to go to e.g. #ubuntu and ask for help, now with LTSP troubleshooting gets complicated.
17:48
<DouglasGiovaniOe>
Ltsp was working there 2 years whitout issues
17:49
<alkisg1>
Yes, it's not a problem with ltsp. LTSP still works without issues.
17:49
The problem is in Linux. It started now. And you cannot troubleshoot easily because of LTSP.
17:50
Anyway, I put your old image back, so things are now the same as they were yesterday. I close VNC. Good luck!
17:57alkisg has left IRC (alkisg!~Thunderbi@srv1-dide.ioa.sch.gr, Quit: alkisg)
18:05alkisg has joined IRC (alkisg!~Thunderbi@2a02:587:744e:8500:c24a:ff:fe02:bc1e)
18:07alkisg_web has joined IRC (alkisg_web!~alkisg_we@2a02:587:744e:8500:c24a:ff:fe02:bc1e)
18:08alkisg is now known as alkisg_irc
18:10
<DouglasGiovaniOe>
right
18:10
thank you
18:10
<alkisg1>
👍️
18:15
<DouglasGiovaniOe>
We go switch to other distro, from 2022. Because since October it starts show some problems, before this, all was working nice.
18:16
<alkisg1>
All distributions use Linux, so will have the same problems
18:16
You need to read what the Linux kernel is. It's the same for all distributions.
18:17
<DouglasGiovaniOe>
yes I know about, only "construction" are different, all are linux yes
18:18alkisg1 is now known as alkisg
18:19alkisg_web has left IRC (alkisg_web!~alkisg_we@2a02:587:744e:8500:c24a:ff:fe02:bc1e, Quit: Client closed)
18:55oh207 has left IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net, Ping timeout: 265 seconds)
20:02vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:40, Quit: leaving)
20:20oh207 has joined IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net)
22:03vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)
22:39ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
23:54oh207 has left IRC (oh207!~oh207@pool-72-69-11-48.nycmny.fios.verizon.net, Ping timeout: 260 seconds)