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


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

01:33vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving)
03:50lucascastro has left IRC (lucascastro!~lucascast@192-140-51-210.static.oncabo.net.br, Ping timeout: 240 seconds)
03:55lucascastro has joined IRC (lucascastro!~lucascast@192-140-51-210.static.oncabo.net.br)
06:27ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)
07:00eu^81-207-247-18 has joined IRC (eu^81-207-247-18!~eu^81-207@81-207-247-18.fixed.kpn.net)
07:04eu^81-207-247-18 has left IRC (eu^81-207-247-18!~eu^81-207@81-207-247-18.fixed.kpn.net, Client Quit)
14:27eu^dslb-002-202- has joined IRC (eu^dslb-002-202-!~eu^dslb-0@dslb-002-202-059-117.002.202.pools.vodafone-ip.de)
15:25eu^dslb-002-202- has left IRC (eu^dslb-002-202-!~eu^dslb-0@dslb-002-202-059-117.002.202.pools.vodafone-ip.de, Ping timeout: 250 seconds)
15:29Vercas has left IRC (Vercas!~Vercas@gateway/tor-sasl/vercas, Remote host closed the connection)
15:30Vercas has joined IRC (Vercas!~Vercas@gateway/tor-sasl/vercas)
16:18eu^dslb-002-202- has joined IRC (eu^dslb-002-202-!~eu^dslb-0@dslb-002-202-059-117.002.202.pools.vodafone-ip.de)
16:36
<eu^dslb-002-202->
I've been using LTSP on Debian for quite some time without problems - thanks to the LTSP-team.
16:36
However, some of my clients (which where running fine in the past) are not starting anymore.
16:36
A Shuttle XS36V4 ends up in kernel panic (CPU: 3 PID: 1 Comm: init Not tainted 5.10.0-0.bpo.12-amd64) and a Core i5-750 does not even reach the PXE boot menu (but hangs at "iPXE initialising devices...").
16:36
However, the LTSP-server seem to be functional since my laptop (Acer Nitro5) is PXE-booting without problems.
16:36
Does someone has an idea would might be wrong here?
16:36
----------
16:36
LTSP:   22.01-1~ubuntu18.04.1
16:36
Debian: 5.10.0-0.bpo.12-amd64
16:37
<alkisg>
Hi eu^dslb-002-202- ; how much RAM does th shuttle one have?
16:38
For the i5 client, try this: https://github.com/ltsp/ltsp/discussions/276#discussioncomment-102218
16:38
<eu^dslb-002-202->
I have to check ... I'm back in a minute ...
16:39
The shuttle has 4GB ...
16:40
<alkisg>
For the shuttle one, upload a screenshot of the kernel panic
16:41
Also if you happen to have a debian live cd etc, try to boot it with that, to see if the problem is related to ltsp or e.g. to the kernel, xorg etc
16:41
<eu^dslb-002-202->
[    6.718070] process '/usr/bin/ipconfig' started with executable stack
16:41
ipconfig: no devices to configure
16:41
ipconfig: no devices to configure
16:41
ipconfig: no devices to configure
16:41
ipconfig: no devices to configure
16:41
ipconfig: no devices to configure
16:41
[    6.734660] Kernel panic - not syncing: Attemped to kill init! exitcode=0x00000200
16:41
[    6.734667] CPU: 3 PID: 1 Comm: init Not tainted 5.10.0-0.bpo.12-amd64 #1 Debian 5.10.103-1~bpo10+1
16:41
[    6.734669] Hardware name: Shuttle Inc. XS36V4/FS36V4, BIOS 4.00 x64 09/21/2015
16:41
[    6.734671] Call Trace:
16:41
[    6.734689]  dump_stack+0x6d/0x88
16:41
[    6.734696]  panic+0x101/0x2d7
16:41
[    6.734702]  do_exit.cold.28+0xb3/0xb3
16:41
[    6.734709]  do_group_exit+0x3a/0xa0
16:41
[    6.734715]  __x64_sys_exit_group+0x14/0x20
16:41
[    6.734719]  do_syscall_64+0x33/0x80
16:41
[    6.734731]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
16:41
[    6.734737] RIP: 0033:0x7f9334dc1746
16:44
<alkisg>
This means that there's no driver for your network card; it might need some firmware; which card is it?
16:44
Boot it with a live CD and run `lspci -nn -k | grep -A3 Ethernet`
16:44
<eu^dslb-002-202->
ok, it might take some time ...
16:54
$ uname -a
16:54
Linux debian 5.10.0-10-amd64 #1 SMP Debian 5.10.84-1 (2021-12-08) x86_64 GNU/Linux
16:54
$ lspci -nn -k | grep -A3 Ethernet
16:54
02:00.2 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 0a)
16:54
    Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1297:4020]
16:54
    Kernel driver in use: r8169
16:54
    Kernel modules: r8169
16:58
<alkisg>
eu^dslb-002-202-: which method are you using, chrootless, vm or chroot?
16:58
Also, did the i5 client work with the link I gave?
16:59
<eu^dslb-002-202->
I didn't tried the link yet
17:01
I'm not sure about the method ... I just followed the manual:  apt-get install ltsp
17:01
  ltsp dnsmasq --proxy-dhcp=0
17:01
  ltsp image /
17:01
  ltsp ipxe
17:01
  ltsp nfs
17:01
  ltsp initrd
17:01
<alkisg>
OK, `ltsp image /` means that you're using the server rootfs, we call that "chrootless"
17:02
I think Debian has a realtek-firmware or something package that you might need
17:03
Try installing this one: https://packages.debian.org/bullseye/firmware-realtek
17:03
<eu^dslb-002-202->
firmware-realtek  is installed
17:04
dpkg -l | grep firmware-realtek
17:04
ii  firmware-realtek                       20190114-2                                   all          Binary firmware for Realtek wired/wifi/BT adapters
17:04
<alkisg>
Open /etc/ltsp/ltsp.conf, and under [common] put KERNEL_PARAMETERS="break=mount". Then run `sudo ltsp ipxe`. Then reboot the client; you should get a shell now
17:05
At that initramfs shell, type: ip a
17:05
Check if your adapter is listed there; if not, type `dmesg` and see notes about missing firmware etc
17:13
<eu^dslb-002-202->
ip a  only shows the loopback device lo ... I'm now looking for missing firmware
17:17
On a first quick look  (dmesg | less)  I couldn't find anything pointing to a missing firmware.
17:33
Meanwhile I tried out your link ... Core i5-750 is now booting :-)
17:47
I'm still working on the kernel panic ... and would like to save dmesg somehow.
17:48
But since  break=mount  I don't see any device to write my data on ...
18:05
<alkisg>
eu^dslb-002-202-: I would use "break=mount" in the live cd
18:05
*or usb or whatever
18:35
<eu^dslb-002-202->
I finally was able to save dmesg - should I paste it here?
18:41
<alkisg>
in a pastebin, then paste the link here
18:41
e.g. paste.debian.net
18:46
<eu^dslb-002-202->
Here is the link: https://paste.debian.net/1236584/
18:46
I used  break=mount  and run the PXE-boot ...
18:50
<alkisg>
eu^dslb-002-202-: that's when booted as an ltsp client, or from a live usb?
18:51
<eu^dslb-002-202->
as ltsp client ..
18:51
<alkisg>
I don't see any references to the network at all
18:51
(adapter)
18:52
Inside the initramfs, what happens if you run `modprobe rt8169` ?
18:52
r8169
19:05
<eu^dslb-002-202->
I had to reboot to reproduce ... here is the link https://paste.debian.net/1236586/
19:06
After modprobe the net device is running ...
19:08
ip a   shows now device   enp2s0f2
19:09
<alkisg>
That's definitely not an ltsp issue then :)
19:09
It should be possible to put it somewhere in /etc/modules to force-load the module
19:10
You'll need to google a bit about how to force-load the module
19:11
<eu^dslb-002-202->
Any idea why booting from live-cd brings the net device up without problems?
19:19
I just found that on the server there is a file /etc/modprobe.d/r8168-dkms.conf ... which probably cause the problem.
19:20
I will follow this path ... and many thanks for all your help  !!!
19:20
<alkisg>
live cd => probably because it brings the device up later on
19:21
I.e. if you put break=mount in the live cd, you'll have the same issue there too
19:26ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)
19:27eu^dslb-002-202- has left IRC (eu^dslb-002-202-!~eu^dslb-0@dslb-002-202-059-117.002.202.pools.vodafone-ip.de, Quit: Client closed)
21:52vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20)