Leolo_2: is a non UEFI machine working in this network? ie. did you try it with your Laptop? that way you could make sure it is actually EFI...
I have no expirience with Efi myself.
|05:06||lucascastro has joined IRC (firstname.lastname@example.org)|
|05:11||lucascastro has left IRC (email@example.com, Quit: Leaving)|
|06:09||Hyperbyte has left IRC (Hyperbytefirstname.lastname@example.org, Quit: leaving)|
|06:09||Hyperbyte has joined IRC (Hyperbyteemail@example.com)|
|07:42||adrianor1 has joined IRC (firstname.lastname@example.org)|
|07:43||adrianorg has left IRC (email@example.com, Ping timeout: 246 seconds)|
|07:45||Leolo_2 has left IRC (Leolo_2firstname.lastname@example.org, Ping timeout: 246 seconds)|
|07:55||ricotz has joined IRC (ricotz!~ricotz@ubuntu/member/ricotz)|
|09:06||GodFather has left IRC (GodFatheremail@example.com, Ping timeout: 250 seconds)|
|09:37||pppingme has left IRC (pppingme!~pppingme@unaffiliated/pppingme, Ping timeout: 240 seconds)|
|09:49||pppingme has joined IRC (pppingme!~pppingme@unaffiliated/pppingme)|
|10:51||enaut[m] has left IRC (enaut[m]!enautmatri@gateway/shell/matrix.org/x-hksfaoqqsyirpmfd, Remote host closed the connection)|
|11:47||Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)|
|12:20||lucascastro has joined IRC (firstname.lastname@example.org)|
|12:59||enaut[m] has joined IRC (enaut[m]!enautmatri@gateway/shell/matrix.org/x-kifhzvdtgbwgixtc)|
|14:44||vagrantc has joined IRC (vagrantc!~vagrant@unaffiliated/vagrantc)|
Hi everyone. I have a couple boxes that have built in LVDS display ports that can't be disabled in the bios. I've added xrandr commands to disable the outputs, which fixes the login screen. But after logging in the output is reenabled. Is there a way to disable these on a per-machine (mac?) basis after logging in?
added xrandr commands to lts.conf*
ubuntu 14.04 host
guess I want to add a script to the LTSP chroot /etc/X11/Xsession.d/ ?
it might be the userspace applications helpfully configuring your available monitors for you
it's an intel atom ITX board... D255MUD or something like that
already did the latest bios updates and no way to disable the flat panel display port =/
mate, gnome, kde, etc. ?
(I get what you're asking now ;) )
gnome might be configuring the monitor for each user independently
it certainly is, we have some folks running multihead and some not
and I'd like to retain that capability
it might be more a per-user configuration than per client
not that i'm saying that's what you want...
Yeah, I get what you're saying, which is unfortunate
Other than the silly LVDS issue, these boxes work fine =/
but yeah, you might have some luck writing a script for Xsession.d that checks and disables them again ... but gnome *might* just re-enable them
Yup, testing now
since gnome will run after any of your Xsession.d hooks
mwalters: you can definately disable screens permanently on a per user base in gnome... you probably have to find the way it works and change that to a "dynamic" variant...
Sure, thanks. Would be lovely on a per machine basis, since I won't know who will be getting the machine until the user's existing one breaks... at which time I'll forget to do that ;)
I just tried to find relevant entries in dconf - but failed... But what I mean to say is, that if you disable a monitor the gnome-user way (in your Xsession.d) that should make your change permanent.
might be that I dont find the entries in dconf because only one monitor is connected...
I think the settings are even on a per display, per user base... so gnome remembers the settings of this user for this beamer/monitor/...
yeah, Xsession.d script definitely doesn't work
I'll keep digging, thanks for the help
well, the script works, just not the way I want it to ;)
gnome is definitely doing a redetection
oh, I need to rebuild the image after making changes, right?
I might just be being an idiot
(I inherited this LTSP deployment and have zero experience with it ;) )
yes, also keep in mind that even though the image gets replaced, the old one still has file locks on it and uses disk space until all the clients reboot.
thanks! slowly getting it
so if you do a couple rebuilds only rebooting one client for testing you can run out of disk space pretty quick
yeah, I thought my boss said something about the clients being forced to reboot when the image is updated
(after a certain amount of time or something)
or at least a notification that they should
if it's automatic, thats new
It's probably just a notification then. I've only updated the packages and kernels in our chroots once
but for thin client, you can kill nbd and it'll take quite a long time before the clients care. fat clients will care pretty quickly
yeah, we have all thin clients
It's been a bit of a mess... a bunch of IT managers in a few years. Documentation on anything is lacking
Documentation lacking is completely normal in smaller orgs
pretty much expected
A fair comment, yes.
even when i try, I come back later and find what I wrote lacking in one way or another
|15:48||vagrantc has left IRC (vagrantc!~vagrant@unaffiliated/vagrantc, Quit: leaving)|
|16:48||lucascastro has left IRC (email@example.com, Remote host closed the connection)|
|16:48||lucascastro has joined IRC (firstname.lastname@example.org)|
|18:06||lucascastro has left IRC (email@example.com, Read error: Connection reset by peer)|
|18:06||lucascastro has joined IRC (firstname.lastname@example.org)|
|20:08||lucascastro has left IRC (email@example.com, Ping timeout: 252 seconds)|
|20:13||lucascastro has joined IRC (firstname.lastname@example.org)|
|20:23||Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Read error: Connection reset by peer)|
|20:24||Faith has joined IRC (Faith!~Paty_@unaffiliated/faith)|
|20:36||lucascastro has joined IRC (email@example.com)|
|20:44||lucas_ has joined IRC (firstname.lastname@example.org)|
|20:45||lucas_ has left IRC (email@example.com, Remote host closed the connection)|
|20:46||lucascastro has left IRC (firstname.lastname@example.org, Ping timeout: 246 seconds)|
|20:48||lucas_ has joined IRC (email@example.com)|
|21:19||Faith has left IRC (Faith!~Paty_@unaffiliated/faith, Quit: Leaving)|
|21:32||adrianorg has joined IRC (firstname.lastname@example.org)|
|21:34||adrianor1 has left IRC (email@example.com, Ping timeout: 250 seconds)|
|22:03||ricotz has left IRC (ricotz!~ricotz@ubuntu/member/ricotz, Quit: Leaving)|
|22:12||Leolo_2 has joined IRC (Leolo_2firstname.lastname@example.org)|
enaut - the same computer can boot the same kernel when in legacy mode.
"Aug 30 13:17:36 server-Beloeil4 in.tftpd: tftpd: read(ack): Connection refused"
ok, so it's a tftp problem