[K12OSN] Gnome-panels missing on clients
Lars Schade
lars.schade at berlin.de
Sat Mar 12 21:46:41 UTC 2011
SUCCESS, I finally got the ZBOX working with the gnome-panels visible
but have not done extensive testing to see whether absolutely everything
is functional (though it appears to be).
The problem was that the ZBOX falsely believes to be a notebook equipped
with an own LCD-screen. And that the vga-monitor I connect is only a
secondary external screen. So the key to getting the thing working is to
turn off the fictitious LCD-screen. After hours of testing I found the
following to work for me:
Add a client specific section in your lts.conf:
################
#[MAC ADDRESS]: ZBOX SD-ID10
################
[00:01:2E:BC:29:C3]
XRANDR_OUTPUT_0="VGA1 --primary"
XRANDR_MODE_0="1280x1024"
XRANDR_OUTPUT_1="LVDS1 --off"
XF86CONFIG_FILE="/etc/X11/xorg.conf.zbox"
The external VGA goes by the name VGA1 and the fictitious LCD by the
name LVDS1. So the LCD is turned off and the VGA is set as primary
device. This does the job for the login screen but the information is
somehow lost when the gnome session is started (I have no clue why).
Anyway, so you need to provide a client specific xorg.conf file. I
created one on the client by running X -configure and then modified it
to again turn off LVDS1. The file location is specified in chroot
notation, the real location is /opt/ltsp/i386/etc/X11/xorg.conf.zbox
Here is what I use:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "catalogue:/etc/X11/fontpath.d"
FontPath "built-ins"
EndSection
Section "Module"
Load "record"
Load "dbe"
Load "dri"
Load "glx"
Load "dri2"
Load "extmod"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "VGA"
Option "PreferredMode" "1280x1024"
EndSection
Section "Monitor"
Identifier "LVDS"
Option "Ignore" "true"
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
Option "monitor-VGA1" "VGA"
Option "monitor-LVDS1" "LVDS"
BusID "PCI:0:2:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "VGA"
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x1024"
EndSubSection
EndSection
The monitor, device, and screen section were adapted to do the job.
Thanks a lot to Jeff and Odin for sharing your knowledge and experience
and ideas !!!!!
Am Montag, den 07.03.2011, 19:57 -0500 schrieb Jeff Siddall:
> On 03/06/2011 12:21 PM, Lars Schade wrote:
> >> To find out what is happening on the client you need to get the
> >> Xorg.whatever.log (note that "whatever" was in my case a "1") on the
> >> client. There are a few ways to do this. I did it by setting up sshd
> >> in the chroot so I could ssh to any client. For that you need to
> >> install and enable the sshd stuff as well as set a root password in the
> >> chroot. Other alternatives are to look at the file locally by setting
> >> something like:
> >>
> >> SCREEN_02=shell
> >>
> >> in your lts.conf and then using CTRL-ALT-F2 _on the client_ to get to
> >> the shell, then do your normal CLI stuff after that.
> >
> > Tried that with partial success. I could not get a proper login prompt
> > for some reason. CTRL-ALT-F2 got me to a shell which did not accept
> > keyboard input properly. And timed out back to a login prompt where I
> > could not enter letters in a sensible fashion. I used my notebook via
> > pxe as a client (not graphics issues there, everything runs smooth) and
> > got the same strange behavior at the CTRL-ALT-F2 shell.
> >
> > So I decided to rebuild the client with Fedora-12 since that worked for
> > Jeff, i.e. ltsp-build-client --release 12. That did the job as far as
> > the CTRL-ALT-F2 shell is concerned - mostly. For some reason CTRL-ALT-F2
> > switches me right away to a root shell without prompting for a username
> > and password. Why is that, seems like a security issue?
>
> Hmmm... yeah, I recall seeing that also. Try another shell (maybe
> CTRL-ALT-F3). I think I eventually found one that I could login with.
>
> > But at least I was able to take a look at the Xorg.1.log and other
> > things on the client (the panel issue is just as previously with f13):
> >
> > kernel-2.6.32.26-175.fc12.i686
> > xorg-x11-drv-intel-2.9.1-1.fc12.i686
> >
> > The Xorg.1.log file is attached, it looks very similar to what Jeff
> > posted, here are some pieces from my file:
> >
> > ...
> >
> > (--) PCI:*(0:0:2:0) 8086:a001:8086:a001 Intel Corporation Pineview
> > Integrated Gr
> > aphics Controller rev 2, Mem @ 0xfe880000/524288, 0xd0000000/268435456,
> > 0xfe9000
> > 00/1048576, I/O @ 0x0000dc00/8, BIOS @ 0x????????/131072
> > (--) PCI: (0:0:2:1) 8086:a002:8086:a001 Intel Corporation Pineview
> > Integrated Gr
> > aphics Controller rev 2, Mem @ 0xfe780000/524288, BIOS @
> > 0x????????/65536
> >
> > ...
> >
> > (==) Matched intel for the autoconfigured driver
> > (==) Assigned the driver to the xf86ConfigLayout
> > (II) LoadModule: "intel"
> > (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
> > (II) Module intel: vendor="X.Org Foundation"
> > compiled for 1.7.0, module version = 2.9.1
> > Module class: X.Org Video Driver
> > ABI class: X.Org Video Driver, version 6.0
> > (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
> > i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G,
> > E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
> > 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
> > 4 Series, G45/G43, Q45/Q43, G41, B43, Clarkdale, Arrandale
> > (II) Primary Device is: PCI 00 at 00:02:0
> >
> > ...
> >
> > (II) intel(0): Integrated Graphics Chipset: Intel(R) Pineview G
> > (--) intel(0): Chipset: "Pineview G"
> > (II) intel(0): Output LVDS1 has no monitor section
> > (II) intel(0): Output VGA1 has no monitor section
> >
> > ... (here comes probing of the monitor)
> >
> > (II) intel(0): Output LVDS1 connected
> > (II) intel(0): Output VGA1 connected
> > (II) intel(0): Using spanning desktop for initial modes
> > (II) intel(0): Output LVDS1 using initial mode 1024x768 +0+0
> > (II) intel(0): Output VGA1 using initial mode 1280x1024 +1024+0
> >
> > ... (here comes info I cannot make sense of:)
> >
> > (II) intel(0): Setting screen physical size to 609 x 270
> > (II) intel(0): Allocate new frame buffer 2304x1024 stride 4096
> >
> > ... (and more and more probing info????)
>
> Not sure about that physical size thing. Seems very wrong for sure.
> Are you actually using both LVDS and VGA? It seems to think you are.
> Since I have not tried a multi-head on one of these I don't know how
> well that works. Maybe try connecting only one monitor and see if you
> can get that working first. After that xrandr is your friend for
> playing with other layouts.
>
> If you don't have two monitors attached then the driver is not detecting
> your monitor correctly. I have a 945GSE chipset board running CentOS
> that had problems detecting a DVI->HDMI TV correctly. I ended up coming
> up with a custom xorg.conf that forced the outputs and modes I was
> interested in. Here's how I made sure that only DVI was being used:
>
> In the Device section add something like:
>
> Option "monitor-VGA" "VGA"
> Option "monitor-LVDS" "LVDS"
> Option "monitor-TMDS-1" "DVI"
>
> And in the Monitor section add:
>
> Identifier "DVI"
>
> Then setup a screen that uses the monitor you want:
>
> Section "Screen"
> Identifier "Screen0"
> Device "Card0"
> Monitor "DVI"
> SubSection "Display"
> Viewport 0 0
> Depth 24
> Modes "1920x1080"
> EndSubSection
> EndSection
>
> Note that you may need to change the
> monitor-VGA" stuff to match the identification of your actual hardware.
>
> Maybe that is the issue you are having or maybe it is unrelated. Trial
> and error might be the only way to figure it out.
>
> > Is there info in the log file that points to a problem and thus to a
> > solution? The complete log is attached.
> >
> > If someone has ideas how to further diagnose I would appreciate.
> > Otherwise I may have to give up on this machine...
>
> I'm pretty much at the end of my abilities here. Let us know how it
> goes. Maybe someone else has some other ideas.
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
More information about the K12OSN
mailing list