IRC chat logs for #ltsp on irc.libera.chat (webchat)
Channel log from 13 February 2023 (all times are UTC)
| 03:01 | wyre is now away: Auto away at Mon Feb 13 03:01:20 2023 UTC | |
| 04:31 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 04:45 | vagrantc has left IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20, Quit: leaving) | |
| 06:39 | wyre is back | |
| 06:45 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 06:47 | <Lantizia> alkisg, so it's 6:30am here and I'm back at the scene of the crime (i.e. the room with all 30 pc's) and oddly I've just accidentally booted up one of the other pc's (not one of the two you could see from epoptes yesterday, not one you had a MAC address for) as I didn't realise I'd turned it on
| |
| 06:47 | and bingo 1024x768
| |
| 06:49 | <alkisg> Lantizia: if the problem only happens in some of the PCs, then try to replace the vga cables, I've seen bad cables cause that issue
| |
| 06:50 | <Lantizia> or the extra config you added in ltsp.conf isn't needed
| |
| 06:51 | <alkisg> But the problem happened even before I added that config
| |
| 06:52 | <Lantizia> I've a hard time thinking it's the cables... remember that the edid information comes up fine
| |
| 06:52 | plus thinstation and ltsp5 with ubuntu 18.04 works fine with them
| |
| 06:53 | *something* has changed
| |
| 06:54 | got the trisquel iso written to a usb pen also... and the 'try' mode (i.e. live env) also comes up 640x480 vesa on the same machine
| |
| 06:56 | actually I got confused that is a different machine
| |
| 06:57 | so what you were dealing with yesterday *I* call pc's 2 and 3 (I know you called them pc01 and pc02... but they're not :P)
| |
| 06:57 | so pc1 comes up 1024x768 with either an ltsp boot or usb pen
| |
| 06:57 | so maybe vga cables?! that react this way ONLY when in vesa mode!?
| |
| 06:58 | <alkisg> I've seen cables cause wrong edid in some kernels, not in others
| |
| 06:58 | You can change the pc names in /etc/ltsp/ltsp.conf
| |
| 07:00 | <Lantizia> but even the log yesterday ... termbin.com/ppuw3
| |
| 07:00 | shows correct edid information
| |
| 07:01 | and that is from one of the pc's that boots up as 640x480
| |
| 07:02 | wyre is now away: Auto away at Mon Feb 13 07:02:13 2023 UTC | |
| 07:12 | <alkisg> So, lspci -nn -k | grep -A 3 VGA shows the exact same model, yet some PCs show 1024 and others 640? If so, try to exchange the monitors/cables to see if it's caused by them
| |
| 07:14 | <Lantizia> ok i'm going to swap the monitor and cable (together) from pc 1 to pc2 and see if the issue moved
| |
| 07:17 | hmm just mid-way through this swap around I'm realising that pc 1 goes through a vga kvm switch
| |
| 07:17 | so maybe that is improving things
| |
| 07:19 | <err404[m]> Lantizia: I will try trisquel_10.0.1_amd64.iso (I can test it on few differents computers, and see what I have with graphical interface)
| |
| 07:20 | <alkisg> Lantizia: vesa is non-kms. I think it might be able to pass something like vga=0x344 to force a mode in that case
| |
| 07:20 | But first do play with the cables/monitors/kvm devices to see what works and what not
| |
| 07:22 | <Lantizia> pc2 still came up 640x480 (even with the monitor/cable from pc1)
| |
| 07:22 | so I think it must be the vga kvm that pc1 has which somehow helps the pc know there are more modes
| |
| 07:23 | err404[m], alkisg, well I was thinking of re-installing the trisquel ltsp server itself... but putting the latest linux-libre (apparently possible from this repo? https://www.fsfla.org/ikiwiki/selibre/linux-libre/freesh.en.html ) on it *before* ltsp
| |
| 07:23 | if that is the default kernel on boot for the server... the ltsp in chrootless mode should use it right?
| |
| 07:23 | thus maybe the radeon driver will work
| |
| 07:24 | <alkisg> Lantizia: there's no need to reinstall just to add a kernel. You can install it, run ltsp image /, and reboot the clients to test with it, even without rebooting the server at all
| |
| 07:24 | <Lantizia> ok i'll try that first
| |
| 07:25 | will 'ltsp image /' pick up on the default kernel that the server would boot with (next time) even though it isn't running on the server?
| |
| 07:25 | actually yeah I don't see why it wouldn't
| |
| 07:25 | ignore me
| |
| 07:26 | <alkisg> Lantizia: it will put all kernels in the image, and select one of them to put in tftp. If it selects the wrong one, we can easily tell it to select the right one in ltsp kernel (which is fast)
| |
| 07:26 | So no need to worry about that part
| |
| 07:30 | <Lantizia> ok kernel linux-libre 6.1.11-gnu now installed... quite the jump up from 5.4
| |
| 07:31 | running ltsp image /
| |
| 07:32 | * Lantizia should technically be working (although I am *at work* in terms of location) but luckily no one comes in until 8am-9am | |
| 07:33 | <Lantizia> so if I suddenly stop talking you'll know why :)
| |
| 07:34 | <alkisg> No worries I have like 20 windows open with vscode, terminals, vnc, chat etc; it'll take some time before I notice :D
| |
| 07:36 | <Lantizia> well they boot with the new kernel now :)
| |
| 07:36 | but it has made zero difference lol
| |
| 07:38 | wyre is back | |
| 07:41 | <alkisg> OK now try adding vga=ask in KERNEL_PARAMETERS (and run ltsp ipxe)
| |
| 07:41 | When prompted, select a 1024x768 something mode
| |
| 07:44 | * err404[m] uploaded an image: (82KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/ZqibbCfvtvZnWJejLxsJagkM/20230213_084354_3398970099514719822.jpg > | |
| 07:44 | <err404[m]> Beautiful triskel 😃
| |
| 07:46 | <Lantizia> alkisg, what do you mean by 'when prompted?' :P
| |
| 07:46 | oh it'll ask on boot up will it
| |
| 07:46 | <err404[m]> the screen resolution seem good
| |
| 07:46 | <alkisg> Right
| |
| 08:01 | <Lantizia> well that seemed to work... i picked 'f' which was 1280x1024x16
| |
| 08:01 | and if I open 'Display' / 'Monitor Preferences' then that is the only choice too
| |
| 08:02 | and this is *not* on pc1 (the one with the kvm switch) so just normal pc->vga-cable->monitor setup
| |
| 08:08 | <alkisg> Lantizia: ok then you pass vga=0x344 to avoid the prompt
| |
| 08:08 | (or whatever other number it is; maybe vga=f will also work, not sure)
| |
| 08:12 | <Lantizia> hmm OK well I'll try a few and see how high I can go I guess
| |
| 08:12 | then write down the correct hex
| |
| 08:16 | woernie has joined IRC (woernie!~werner@p5b296c9e.dip0.t-ipconnect.de) | |
| 09:01 | alkisg_irc has left IRC (alkisg_irc!~Thunderbi@2a02:587:7456:4800:9ea2:f4ff:feb9:a8b0, *.net *.split) | |
| 09:01 | alkisg_irc has joined IRC (alkisg_irc!~Thunderbi@2a02:587:7456:4800:9ea2:f4ff:feb9:a8b0) | |
| 09:41 | wyre is now away: Auto away at Mon Feb 13 09:41:18 2023 UTC | |
| 09:43 | wyre is back | |
| 10:35 | wyre is now away: Auto away at Mon Feb 13 10:35:19 2023 UTC | |
| 10:37 | wyre is back | |
| 11:10 | <Lantizia> hmm was just reading the trisquel wikipedia page and this caught my eye (mostly because it said LTSP)... https://i.snipboard.io/vlbIpH.jpg
| |
| 11:11 | I don't think 'Trisquel LTSP classroom server' is a thing though... just likely someone who turned Trisquel *into* a classroom server... using LTSP and something called iTALC / Veyon (I'm guessing it's like epoptes?)
| |
| 11:26 | <alkisg> Yeah, we developed epoptes when italc was abandoned. Later on, the same person renamed it into veyon and started maintaining it again
| |
| 11:27 | The screenshot is from 2008; I think we started epoptes in 2009
| |
| 11:31 | tru_tru_ has joined IRC (tru_tru_!~tru@157.99.90.140) | |
| 11:31 | adrianorg_ has joined IRC (adrianorg_!~adrianorg@debian/adrianorg) | |
| 11:32 | bengoa has joined IRC (bengoa!~root@uk.bengoa.org) | |
| 11:36 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, *.net *.split) | |
| 11:36 | bengoa_ has left IRC (bengoa_!~root@uk.bengoa.org, *.net *.split) | |
| 11:36 | adrianorg has left IRC (adrianorg!~adrianorg@debian/adrianorg, *.net *.split) | |
| 11:36 | tru_tru has left IRC (tru_tru!~tru@centos/board/tru, *.net *.split) | |
| 11:42 | ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz) | |
| 12:12 | sunweaver is back | |
| 12:57 | woernie has left IRC (woernie!~werner@p5b296c9e.dip0.t-ipconnect.de, Ping timeout: 248 seconds) | |
| 13:04 | yacsa71 has joined IRC (yacsa71!~yacsa71@181.225.236.170) | |
| 13:05 | yacsa7194 has joined IRC (yacsa7194!~yacsa71@181.225.236.170) | |
| 13:13 | woernie has joined IRC (woernie!~werner@p5b296c9e.dip0.t-ipconnect.de) | |
| 13:21 | yacsa7182 has joined IRC (yacsa7182!~yacsa71@181.225.236.170) | |
| 13:21 | yacsa7182 has left IRC (yacsa7182!~yacsa71@181.225.236.170, Client Quit) | |
| 13:21 | yacsa7194 has left IRC (yacsa7194!~yacsa71@181.225.236.170, Quit: Client closed) | |
| 13:21 | yacsa71 has left IRC (yacsa71!~yacsa71@181.225.236.170, Quit: Client closed) | |
| 13:22 | yacsa71 has joined IRC (yacsa71!~yacsa71@181.225.236.170) | |
| 13:22 | <yacsa71> I have ltsp 20.04 chrootless. How can I make the user's home be the server's home?
| |
| 13:28 | <vsuojanen[m]> in my understanding it should work by default with server's home if your server is ltsp server and you have installed the pretty much same way as in the installation instructions. did you try with Ubuntu Desktop or what OS have you installed on the sever?
| |
| 13:28 | parlos has joined IRC (parlos!~pal@2001:6b0:2a:c240:aa5e:45ff:fed1:c4a1) | |
| 13:31 | <yacsa71> When I had version 10.04 it worked like this, without problems.
| |
| 13:31 | I then installed the ubuntu 22.04 version on the server with the chrootless option and once the clients turn off the information is lost
| |
| 13:35 | <vsuojanen[m]> (you don't need to install any special option to use chrootless, it's the method to maintain you clients image aka root filesystem)
| |
| 13:37 | can you paste here the apt install command you used to install ltsp package? e.x. apt install --install-recommends ltsp ltsp-binaries dnsmasq nfs-kernel-server openssh-server squashfs-tools ethtool net-tools epoptes
| |
| 13:37 | gpasswd -a administrator epoptes
| |
| 13:38 | that *gpasswd -a administrator epoptes was from the apt install part
| |
| 13:39 | sorry, that *gpasswd -a administrator epoptes was not from the apt install part
| |
| 13:39 | <yacsa71> apt install --install-recommends ltsp ltsp-binaries dnsmasq nfs-kernel-server openssh-server squashfs-tools ethtool net-tools epoptes
| |
| 13:39 | gpasswd -a administrator epoptes
| |
| 13:43 | <vsuojanen[m]> yacsa71: try this and upload here the output, then wait for someone here comments to the issue
| |
| 13:43 | https://github.com/ltsp/ltsp/discussions/723
| |
| 13:46 | so basically just boot the client and paste the output here. also if you can login check in client terminal/tty that there is the '/usr/bin/sshfs' . ls /usr/bin/sshfs
| |
| 13:47 | woernie has left IRC (woernie!~werner@p5b296c9e.dip0.t-ipconnect.de, Ping timeout: 246 seconds) | |
| 13:47 | woernie has joined IRC (woernie!~werner@p200300c56f3a82009e43a16456bf1736.dip0.t-ipconnect.de) | |
| 14:03 | parlos has left IRC (parlos!~pal@2001:6b0:2a:c240:aa5e:45ff:fed1:c4a1, Quit: Konversation terminated!) | |
| 14:24 | yacsa71 has left IRC (yacsa71!~yacsa71@181.225.236.170, Quit: Client closed) | |
| 14:36 | yacsa71 has joined IRC (yacsa71!~yacsa71@181.225.236.170) | |
| 14:38 | <alkisg> yacsa71: exactly what vsuojanen said above :)
| |
| 14:56 | <yacsa71> According to what I have read, when generating the image as chrootless
| |
| 14:56 | image is read only. and that's what happens to me
| |
| 15:13 | <vsuojanen[m]> Read again the Installation page. Yes the Image is root filesystem, read only and it should always Be read only. Home isn't in The root
| |
| 15:14 | <alkisg> yacsa71: I mean, login to a booted client, run `mount | nc termbin.com 9999`, and tell us the output
| |
| 15:20 | <yacsa71> I already solved thanks
| |
| 15:21 | <alkisg> 👍️
| |
| 15:23 | yacsa71 has left IRC (yacsa71!~yacsa71@181.225.236.170, Quit: Client closed) | |
| 15:27 | woernie has left IRC (woernie!~werner@p200300c56f3a82009e43a16456bf1736.dip0.t-ipconnect.de, Ping timeout: 260 seconds) | |
| 15:28 | sunweaver is now away: not here ... | |
| 15:29 | <vsuojanen[m]> I some time ago also tried 22.04 desktop, and hit some install problems. i did not much continue playing with it and tried the most recent Ubuntu desktop (Unity and xubuntu) it seemed to fit with ltsp better
| |
| 15:29 | <alkisg> In general I don't like Ubuntu 22.04 GNOME and I'm not testing much with it, but it should work out of the box
| |
| 15:30 | Things I don't like are that GNOME requires a recent opengl, and thus it can't run in some old PCs, and that it has more snap integrated than the other flavors
| |
| 15:30 | woernie has joined IRC (woernie!~werner@p5b296c9e.dip0.t-ipconnect.de) | |
| 15:31 | <alkisg> Ubuntu MATE is where LTSP is mostly tested
| |
| 15:34 | <vsuojanen[m]> i did not meant either that it's the ltsp packages caused problems, in general problems running the clients
| |
| 15:34 | <alkisg> Ah sure, GNOME has plenty of issues :D
| |
| 15:36 | <vsuojanen[m]> it's easier to just choose another release and desktop 😀
| |
| 16:26 | wyre is now away: Auto away at Mon Feb 13 16:26:36 2023 UTC | |
| 16:40 | tru_tru_ has left IRC (tru_tru_!~tru@157.99.90.140, Quit: leaving) | |
| 17:15 | tru_tru has joined IRC (tru_tru!~tru@centos/board/tru) | |
| 17:52 | adrianorg_ has left IRC (adrianorg_!~adrianorg@debian/adrianorg, Ping timeout: 268 seconds) | |
| 17:53 | adrianorg has joined IRC (adrianorg!~adrianorg@debian/adrianorg) | |
| 18:48 | vagrantc has joined IRC (vagrantc!~vagrant@2600:3c01:e000:21:7:77:0:20) | |
| 19:56 | <muhwalt> as someone using a wlroots desktop... gnome definitely has plenty of issues ;)
| |
| 19:56 | wyre is back | |
| 21:53 | ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving) | |